EDIT: no, I don't sympathize with nazis (neither I sympathize with those who call everyone nazi when they're losing an argument ;)
this post was submitted on 02 Sep 2023
594 points (69.4% liked)
Memes
45725 readers
1155 users here now
Rules:
- Be civil and nice.
- Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This post assumes that a meaningful amount of defed instances are caused by simple lack of agreement. Often, it's an orthogonal matter - it boils down to instance A actually understanding something about the userbase of instance B and saying "I'm not dealing with this shit, it'll make the instance worse for its own users". For example: the typical user of B might be disingenuous, or preach immoral prescriptions, behave like a chimp, or be a bloody stupid piece of trash that should've stayed in Reddit to avoid smearing its stupidity everywhere here.
Are instance admins too eager to pull the trigger for defed? Perhaps, in some cases; specially because it handles groups of users instead of individuals. But those cases are better addressed through actual examples, not through a meme talking on generic grounds.
The cool part is, if your instance admin starts doing stuff you don't like, you can super easily just go to a different one, or even go about hosting your own that you control and decide who to federate with
Well, once they fix the whole "each instance copies the media from other instances automatically" thing. I'd love to self-host a vanity instance if I didn't have to either worry about CSAM or just nuke the entire pict-rs facility via script.
...actually I wonder if that's an option on kbin. Even if the Mastodon interoperability is a bit wonky right now I like the platform working with both services on ActivityPub (thus why I'm here).
Fix?.... Look at the Lemmy code base.
This is a feature not a bug.
Making it mandatory and something you can't opt out of is not acceptable. "Work as a knockoff as a CDN" shouldn't be a requirement of running a vanity instance. That's a barrier to entry without much benefit.
Just run an allow-list?..
From what I understand, that's difficult to do, and even if done it prevents the inline loading of images from those other instances at all.
Hopefully it'll be academic before long anyway. The CSAM attack lit a fire under the devs and changing this is now one of their highest priorities.
Yup. As a side effect: admins that are too eager to pull the trigger might get their own users pissed, and they'll eventually leave. So a successful admin needs to make sure that the defed is the best for his userbase.
Thanks for a cool-headed comment!