Open source DRM is still DRM
Android
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
Rules
-
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.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
this old initiative could help: browsers
This older initiative can help: Pay cash for everything
this older initiative can help: dont pay
Right? Why put all these apps with extra trackers on your shit anyway?
This is what I used to do until my bank stopped supporting Zelle on the mobile website.
GrapheneOS is not a fan of this.
Jeez. They really don't. And, I guess they shouldn't. Their stance is that device certification shouldn't be necessary in the first place which I agree with considering this is not done for computers (don't do this tech bro shitheads).
Grapheneos are also against allowing users root access, which is fine on PCs.
Are they, or are they against GrapheneOS itself supporting it?
Those are different. GrapheneOS exists to be security-hardened and usually should choose security over utility where there's a conflict.
They arebgwnweally against root, as it "breaks security" in their mind.
Nevermind that all systems, everywhere, have root for some account/some account is root.
It breaks their sandboxing model, which limits the impact of malicious/compromised apps.
To be clear, I'm not arguing against root here. I daily a rooted phone, and I believe if it's impossible to get root on something, it isn't really yours. You can get root on GrapheneOS; they just discourage it because they're strongly focused on security.
They're right. If a bug in AdAway, which needs root to write /etc/hosts caused it to fetch and execute malicious code, the malware could do anything I can do to my device. The scenario is plausible; it routinely fetches blocklists, and I imagine a sophisticated enough attacker could compromise the delivery mechanism.
I don't worry about that scenario because it's unlikely that kind of attacker will target me. GrapheneOS is meant for people who do have to worry about that kind of thing.
At this point it's like an unwritten rule of the internet that every GrapheneOS account comment chain will eventually regress into cooker conspiracy theories about other privacy ROM projects. And I still have no idea why Micay has started lumping iodé in with them, because I have been following that project closely for many years and no one there gives a shit about GrapheneOS. As in, they literally do not talk about Graphene (or any other projects, for that matter). They never compare themselves to GrapheneOS, on security or anything else. It's the most bizarre, one-sided internet war.
Because that dude is nuts. He does a disservice to graphene PR anytime he speaks.
The Graphene devs and user base behave like a cult
And I still have no idea why Micay has started lumping iodé in with them, because I have been following that project closely for many years and no one there gives a shit about GrapheneOS.
I don't know, but it seems to me that you might have a rather good guess as to why right there.
As in, they literally do not talk about Graphene (or any other projects, for that matter).
???????????????
It's quite common for people to feel hurt when they feel ignored.
As much as I enjoy GrapheneOS, when I hit that part of the chain, I close out. I’m tired of hearing how has attacked GrapheneOS. They used to @ everyone in matrix for it asking for backup, which is why I’m not in their rooms now.
Namely,
Having a European version of the Play Integrity which permits people to use insecure products from specific European companies participating in it while disallowing using arbitrary hardware or software is the opposite of a solution. It's more of the same anti-competitive garbage.
Hate to say it but he's probably right.
Yeah whatever. They are their own bubble.
They're not wrong though
They are if banks don’t allow their apps to be functional on grapheneos.
I have never had an issue with banking apps so long as exploit compatibility mode is enabled for them.
I appreciate the effort but my banking apps still rely on 2FA through SMS. They aren't interested in implementing a technology that is more secure or even one that is different than what they have already, especially for a fraction of a fraction of a fraction of their user base.
I appreciate the effort but my banking apps still rely on 2FA through SMS.
And you trust them with your money!?!
Fair point but I am not going to do all my shopping exclusively out of catalogs and mail in my payment with cash.
Its a shitty situation but short of government regulation (ha) nothing is going to change.
Are there no other banks in your area?...
Yes and as far as I can tell, they all have that as their system. Also the changing of the password every quarter which has proven to actually decrease password security and increase password reuse.
I should say, if anyone knows a bank with proper modern online security protocols I am willing to listen.
I should say, if anyone knows a bank with proper modern online security protocols I am willing to listen.
I'm personally quite fond of Wise.
Seriously, this shit should be illegal already