this post was submitted on 07 Jan 2026
230 points (96.4% liked)

Android

20953 readers
22 users here now

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

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] habitualTartare@lemmy.world 38 points 4 days ago* (last edited 4 days ago) (2 children)

Snapshot of comments in those posts. Mostly just governance drama.

From the new fork https://web.archive.org/web/20260107095954/https://www.reddit.com/r/Piracy/comments/1q1we4e/the_revanced_situation_is_crazy_a_new_project/

From ReVanced side

A major contributor submitted a big core change (fingerprint/patcher internals). Maintainers pushed back hard on design and maintainability. The contributor felt stonewalled, got personal, and eventually left. After leaving, they forked the project, copied large chunks of code, squashed commits, stripped contributor history, and allegedly violated GPLv3 rules by changing licensing and attribution. That’s the heart of the dispute.

From there, both sides started accusing each other of bad faith, harassment, threats, ego, gatekeeping, you name it. A small group rallied around the fork and started saying “ReVanced is dead” which… yeah, that’s the part that caused panic. -- AI generated summary of a 40~ pg document that someone from ReVance uploaded

Basically the contributor proposed a major redesign to the patcher’s fingerprint system that worked short term but papered over deeper limitations. The maintainers saw it as a band-aid approach that would lock in technical debt and cause long term maintenance problems, so after extensive review they rejected it and pushed for a more fundamental solution instead. The contributor took that personally, issued merge-or-else ultimatums, then left. After leaving, they copied large parts of the code into a new repo, rewrote history to remove attribution, changed licensing in ways that likely violate GPLv3, and went public claiming ReVanced was “hostile” or “dead”. ... For context, the fingerprint system is how ReVanced finds the right parts of YouTube’s code to modify even as YouTube updates and shuffles things around. Inefficient or overly abstract changes increase the chance of things breaking later. The contributor wanted a quick duct-tape style fix, the maintainers wanted a proper redesign, and it all spiraled from there.

[–] LiveLM@lemmy.zip 33 points 4 days ago

governance drama

Truly the FOSS project killer

[–] CosmicTurtle0@lemmy.dbzer0.com 28 points 4 days ago (1 children)

Thank you for the summary. I don't have a dog in the fight myself. (I use NewPipe) But I'm an FOSS advocate.

Stripping attribution....that's a GPL violation and that itself is enough to terminate the license. The dates of repo creation and commit dates should be enough to prove causality.

It's not like the fork couldn't have stood on its own. Like...wtf was the contributor thinking removing the attribution would do?

[–] khorovodoved@lemmy.zip 1 points 2 days ago

The funny part is that there was no attribution to beging with.