this post was submitted on 25 Oct 2024
55 points (91.0% liked)
Ye Power Trippin' Bastards
322 readers
3 users here now
This is a community in the spirit of "Am I The Asshole" where people can post their own bans from lemmy or reddit or whatever and get some feedback from others whether the ban was justified or not.
Sometimes one just wants to be able to challenge the arguments some mod made and this could be the place for that.
Rules
- Post only about bans or other sanctions from mod(s).
- Provide the cause of the sanction (e.g. the text of the comment).
- Provide the reason given by the mods for the sanction.
- Don't use private communications to prove your point. We can't verify them and they can be faked easily.
- Don't deobfuscate mod names from the modlog with admin powers.
- Don't harass mods or brigade comms. Don't word your posts in a way that would trigger such harassment and brigades.
- Do not downvote posts if you think they deserved it. Use the comment votes (see below) for that.
- You can post about power trippin' in any social media, not just lemmy. Feel free to post about reddit or a forum etc.
Expect to receive feedback about your posts, they might even be negative.
Make sure you follow this instance's code of conduct. In other words we won't allow bellyaching about being sanctioned for hate speech or bigotry.
Some acronyms you might see.
- PTB - Power-Tripping Bastard: The commenter agrees with you this was a PTB mod.
- YDI - You Deserved It: The commenter thinks you deserved that mod action.
- BPR - Bait-Provoked Reaction: That mod probably overreacted in charged situation, or due to being baited.
- CLM - Clueless mod: The mod probably just doesn't understand how their software works.
Relevant comms
founded 3 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
There is a also another way, I saw someone suggesting that a person could contact a remote instance's admins and have their accounts and data removed from the instance. Essentially requesting a ban.
The big drawback to all but one of the methods listed above is that they are false-assurance or cosmetic/curation blocks, not functional blocks. And with some of the more problematic instances out there, false-assurance is almost worse than nothing at all. With your posts and comments removed from your instance you'll never receive replies or attacks from users on that instance, they'll just never see your content anymore.
That's why admins need to defederate it more often. If Lemmy.world alone gave them the boot it would slash their userbase in those communities significantly. It's very likely that the moderators there would move or a large amount of other users would move. They're not going to though unless they have to, and making it easier by keeping the door open only slows that down from happening.
I would say every reason since the nature of open-source code means you can fork it and use it how ever you want. Especially given that many people are contributors. I say if you want complete control and don't want to hear complaints about your code and platform don't license as GPL and make contributors waive their IP ownership to the devs when contributing code. They didn't do any of this though.
Sublinks is looking very promising as a replacement for Lemmy not only is it written in a more well known language than Rust it's also aiming to have more features while remaining mostly compatible with the Lemmy API.
I don't know how you would force compliance with a different instance though, especially if it is not located in the EU.
In the end we can only control ourselves - e.g. note I'm writing this from a PieFed account:-). But yes Sublinks is a very exciting development as well, though I have not heard any developments for many months when it was mentioned that it was not stable yet.
And yes someone could fork the Lemmy codebase. Many instances including Lemmy.cafe and Tesseract on dubvee.org have done exactly that, though unlike Mbin (since Kbin is now defunct) they don't want to get too far ahead of the main branch so that they can still receive future updates easier, whereas PieFed and Sublinks and Mbin are each entirely separate projects from Lemmy to begin with, though they are interoperable with those federated communities which is awesome 😎.
If you're in the US and they're in the US or countries that have copyright treaties you can request removal under DMCA since you own your posts and comment content. And if you don't agree to their TOS or licensing it's a kind of a grey area for them. Still not completely foolproof since if Instance admins are willing to go further than you're willing to go (i.e. not complying without a lawsuit), you can't really do much about it.
Yeah especially because Rust is much harder to contribute to. Once Sublinks gets off the ground I feel like there will be more people eager and willing to contribute code. I'm hoping that it's still going since there would be great benefit in this project being an option.
I believe Programming.dev does it too, they call it Pangora though they're currently restructuring it to be a fork of Sublinks so they haven't worked on it much at the moment. Also Tesseract is an alternate frontend of the Lemmy software, not a different software. It does improve Lemmy greatly though.
So what will make Sublinks better than e.g. PieFed? Or Mbin for that matter? All 3 of these I thought used Python rather than Rust, as Lemmy does.
I think the main benefit is Lemmy API compatibility and the fact that it's compatible with Lemmy's database structure. Meaning that an instance could choose to migrate from Lemmy to Sublinks. When it comes to any other software they can't really. They'd have to start from scratch as a platform.
Ah, thank you. I'm not 100% certain that's entirely a positive, but indeed it makes sense why e.g. Tesseract on dubvee.org would want to eye using that, when it comes out.
Whereas Mbin provides more cross-platform compatibility with Mastodon, and PieFed with other similar integrations, e.g. PixelFed and upcoming Loops underneath that.