4 ms·
Similar to an email service. You rely on the node operators to manage it.
by kitotik 8y ago
Similar to an email service. You rely on the node operators to manage it.
- theamk 8y agoSo delegate this all to a few large blacklists (spamhaus)? And block all residential users by default?
- StudentStuff 8y agoGenerally not, proactive blocking or silencing is reserved for instances that host illicit content like child porn or hate speech. Inter-moderator communication happens between your instance admin/democracy (or whatever structure your instance uses) and other instances. Traditional tools like muting a user, silencing an instance (if they're spamming up the Federated Timeline on other instances, like Humblr.social does) and blocking (if the mods are total shit) can still be used. Small instances are the bulk of the content, so you aren't about to block them. Large instances like Mastodon.social are generally blocked tho (if your admin/democracy cares about a vibrant Fediverse).
- IshKebab 8y agoThat sounds like it only works because spammers aren't really trying yet.
- StudentStuff 8y agoMalicious actors definitely try to spam and data mine the fediverse, but their accounts get disabled by the local instance admin, and when they try evading that by spinning up a few instances on their own domains to hide their spam or follow bots behind, those instances generally get blocked by instances that see said spam toots or spam followers.
- MrEldritch 8y agoIt'll probably end up "solved" in a similar way to email span being "solved" - if global spam starts to become a problem, you'll have big blocklists of spammy instances and general suspicion towards federating with any new instance that doesn't look sufficiently trustworthy.
- pjc50 8y ago> Large instances like Mastodon.social are generally blocked tho (if your admin/democracy cares about a vibrant Fediverse). Ah, so you achieve vibrancy by .. blocking a large number of the users?
- deleted 8y ago[deleted]
- MrEldritch 8y agoHonestly, I think this is the wrong way of looking at things. The Fediverse isn't really like a single social network that's shattered amongst many instances ... it's more like a bunch of individual, separate hangouts, in the vein of classic forums and IRC chatrooms and fandom websites, which have the ability to talk to each other and share stuff if they want. It's not so much about "blocking" mastodon.social as not choosing to link up with it - because your instance is a specific community, and actual human social relations thrive when they can choose who they're hanging out with. So you choose to talk to other smaller, more diverse communities that you can actually get to know a good chunk of the people in them, instead of just drinking straight from the firehose that is a big instance. Federating with another instance is basically two groups of people deciding to hang out together, effectively merging. Federating with mastodon.social means, effectively, merging your community with mastodon.social ... which means submerging it beneath the mass of mastodon.social's much greater activity. A vibrant Mastodon isn't a more-obtuse recreation of the Twitter experience. Twitter is already Twitter. It's about fostering all the things that Twitter isn't - personal and Dunbar-scaled and locally moderated and diverse.
- xwvvvvwx 8y agoThis sounds awesome. How do I find these smaller and more diverse communities?
- koheripbal 8y agoI think it's sad that we cannot figure out a way to have LARGE federated communities that remain functional.
- zaarn 8y agoI don't think mastodon.social is generally blocked, atleast not the instances I federate with block it. Might be your particular corner of the fediverse, I prefer to have as much reach as possible.
- kiriakasis 8y agoThere can also be spam servers that publish blacklists like with emails
- AnIdiotOnTheNet 8y agoYeah, and look how well it works in the email world.