i dont want to sound like a dick but they really should've just forked the LineageOS apps that are maintained like they did with seedvault. this feels like theyre reinventing the wheel, or NIH
Would be great if those two could play nicely. Lineage features with GOS security would be the bees knees.
I think Calyx OS would strike that balance
As a Calyx user, only kinda. A lot of the hardening done in GOS is missing from Calyx. Likewise, a lot of features in COS (firewall rules per connection type per app for instance) are missing from GOS.
They could just... work with the community and use preexisting community apps
That is not how they role I guess
The maintainers are very picky and cynical about privacy & security. For better or for worse
Not-invented-here syndrome?
When you have a unique goal and set of constraints that are not shared by most users and are actually opposed to the interests of most users and developers it’s not a good idea to try to add them into an existing general purpose project.
Part of the memory tagging support of graphene for example is that the applications need to actually support it too. You can force them to deal with it, but that causes instability and crashes.
Shouldn’t all applications support memory tagging? Well that would be nice but it makes everything slower and only a few schizoid weirdos want it. Clearly the better option is to rewrite the basic system apps that everyone expects to support all the optional security features graphene requires.
Bear in mind graphenes security competition is ios. The system applications in ios all got rewritten to support emte when apple rolled out os level support for it combined with concurrent releases of new hardware with silicon support.
They’re playing a different game than the aosp community.
You are correct, TrollAccount.
They could just add optional support upstream behind a compilation flag.
Maybe.
I think graphene is so far removed from aosp in terms of goals and strategy that would be a pretty big commitment of resources.
If you haven’t ever done upstreaming in an open source project, there’s a pretty big support commitment involved if the thing your work could be part of has insider scope than your own project.
Which is pretty much the exact situation graphene is in.
And if the graphene people are serious about security then giving aosp their (just my own hypothetical) emte enabled apps runs a good chance of providing a false sense of security to the users of those apps when not on graphene.
This isn’t hypothetical btw, I had to dig through datasheets to prove that the old pixels don’t have emte to some random commenter a week or so ago even though just the most cursory understanding of arm mte versions and release schedules would make that obvious.
The point isn’t to say people are stupid or that person was stupid, but that often people will assume the best even when it opens them up to a huge blind spot. One of the best security (and safety) practices is to make your secure component incompatible with insecure ones. That way it’s impossible for someone to point to the thick low awg nema 5-20 extension cord without acknowledging the cheater plug they used to get it into a two prong outlet with no wide neutral.
Hopefully we can get a calendar app!!
Cheers to the GOS team, doing the lord's work truly.
Etar isn't half bad. But yeah I wouldn't complain if they improve the landscape.
Calendula is FOSS and very good. I liked it so much I donated.
I really liked the UI and UX of Google Calendar and I am amazed at how Calendula offers a near identical experience. Really amazing work!
It's a big ask, but might that include the browser?
They could contribute dev time to the Servo browser project.
The already have vanadium
That's just Chromium with some removed "features", not a whole new app.
Well they can't do everything, can they?
Apparently, they plan to.
On a long enough timeline they can
THE GOAT
Excellent. Does it run on the basic Tracfone devices? otherwise, they need to get on the road to compatibility.
GrapheneOS is very picky about what phones are supported, which is why up to now only certain pixels are supported, as well as Motorola phones in the future.
I guess Motorola phone will be my next phone.
Have you seen the new one? Will be more expensive than Pixels and the design is atrocious at best.
6.8" is way too big for me. If that's the only one available, I'm good.
It's only the new $1000+ flagships
Alright, nice
From recent posts on the Fediverse I'm afraid their slopping these apps ...
What posts?
In the announcement threaded, they replied they us AI code analysis and code review tools to review security.
It still goes through a human before it's pushed to the repo. That's very different thing than "slop". Slopcode is generating the actual app code via claude or whatever and shipping it as-is.
I hate AI, absolutely. without question.
however, code reviews and security reviews are in the top 5 acceptable uses for an LLM.
why? because I can't be bothered to read the newbies 10k lines of changes for a CSS rule change.
do I review the review? absolutely! does it make any changes to the code? absolutely NOT.
Another thing to keep in mind is ai is what people are going to be using to try to find vulnerabilities in the software so using it to beat them to the punch is just good development practices.
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Stay on topic: All posts should be related to the Android OS or ecosystem.
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
No affiliate links: Posting affiliate links is not allowed.
Our Communities
Lemmy App List
Chat and More