332
Darth Rule
(lemmy.nz)
Context: https://keepandroidopen.org/
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Sep 2026
332 points (99.7% liked)
196
6847 readers
2255 users here now
Community Rules
You must post before you leave
Be nice. Assume others have good intent (within reason).
Block or ignore posts, comments, and users that irritate you in some way rather than engaging. Report if they are actually breaking community rules.
Use content warnings and/or mark as NSFW when appropriate. Most posts with content warnings likely need to be marked NSFW.
Most 196 posts are memes, shitposts, cute images, or even just recent things that happened, etc. There is no real theme, but try to avoid posts that are very inflammatory, offensive, very low quality, or very "off topic".
Bigotry is not allowed, this includes (but is not limited to): Homophobia, Transphobia, Racism, Sexism, Abelism, Classism, or discrimination based on things like Ethnicity, Nationality, Language, or Religion.
Avoid shilling for corporations, posting advertisements, or promoting exploitation of workers.
Proselytization, support, or defense of authoritarianism is not welcome. This includes but is not limited to: imperialism, nationalism, genocide denial, ethnic or racial supremacy, fascism, Nazism, Marxism-Leninism, Maoism, etc.
Avoid AI generated content.
Avoid misinformation.
Avoid incomprehensible posts.
No threats or personal attacks.
No spam.
Moderator Guidelines
Moderator Guidelines
- Don’t be mean to users. Be gentle or neutral.
- Most moderator actions which have a modlog message should include your username.
- When in doubt about whether or not a user is problematic, send them a DM.
- Don’t waste time debating/arguing with problematic users.
- Assume the best, but don’t tolerate sealioning/just asking questions/concern trolling.
- Ask another mod to take over cases you struggle with, if you get tired, or when things get personal.
- Ask the other mods for advice when things get complicated.
- Share everything you do in the mod matrix, both so several mods aren't unknowingly handling the same issues, but also so you can receive feedback on what you intend to do.
- Don't rush mod actions. If a case doesn't need to be handled right away, consider taking a short break before getting to it. This is to say, cool down and make room for feedback.
- Don’t perform too much moderation in the comments, except if you want a verdict to be public or to ask people to dial a convo down/stop. Single comment warnings are okay.
- Send users concise DMs about verdicts about them, such as bans etc, except in cases where it is clear we don’t want them at all, such as obvious transphobes. No need to notify someone they haven’t been banned of course.
- Explain to a user why their behavior is problematic and how it is distressing others rather than engage with whatever they are saying. Ask them to avoid this in the future and send them packing if they do not comply.
- First warn users, then temp ban them, then finally perma ban them when they break the rules or act inappropriately. Skip steps if necessary.
- Use neutral statements like “this statement can be considered transphobic” rather than “you are being transphobic”.
- No large decisions or actions without community input (polls or meta posts f.ex.).
- Large internal decisions (such as ousting a mod) might require a vote, needing more than 50% of the votes to pass. Also consider asking the community for feedback.
- Remember you are a voluntary moderator. You don’t get paid. Take a break when you need one. Perhaps ask another moderator to step in if necessary.
founded 2 years ago
MODERATORS
Custom ROMs, such as CalyxOS, are based on AOSP. Per their own website(which lambasts Google and highlights Samsung for some reason):
By using a Custom ROM, and from developers contributing to the AOSP, they are supporting Google, agreeing to Google, and helping Google further their ends. Yes, your experience may differ from stockdroid, but if you think you are away from Google, Calyx admits in that one line that despite their platitudes, they are still beholden to Google. If Google restricts access to AOSP, which they can as they are who grants access in the first place, congrats, it becomes the high waters or a dead project.
uhh no, that's technically not correct. google can not "restrict access to AOSP". nobody can "restrict access" to an open source project. (at least not read/use access, if that's what you're talking about. they can exclude you from contributing your own code changes; for which case forks are the way to go)
They can restrict access to the current form of the Source as they are the Arbiters of who can obtain the Source. When I went to try to get the most recent AOSP some time ago, one of the requirements was agreeing to Google. All projects that stem out of the AOSP agreed to the terms Google laid out for the access to the AOSP. It is only "open source," insofar as Google allowing one to access it. It is akin to a park that is free to access, so long as you pay the toll booth at the authorized road to get there.