@ashten@Drand@natalie And looking in the logs I don't think I even want to block that IP because it's pretty much evidence against bullshit.
- A ton of requests to /users/lanodan so just the profile. By ton I mean multiple times a second and multiple times an hour, kind of thing that would be a banning offense - 9 requests to /objects/ (ActivityPub posts data for Pleroma) so pretty much nothing - Only on the 2023-11-28 they grabbed /api/v1/timelines/public (MastodonAPI) with mastodonpy as User-Agent (everything else uses Python-urllib/3.9), without authentication on my instance you'd get only my public posts, I post unlisted by default so it's only some replies (like this one) - They also scrapped parts of my blog, with URLs ending in </a> and %3C/a%3E do you even HTML?
@lanodan@natalie@ashten@Drand just btw wanted to point out: 1) I make a throwaway instance and user that just says BEEP BOOP NOW ARCHVIING, follow like 5 instance admins from it, there's a *massive* fediblock campaign and related domains appear on "tier 0" blocklists years after the domain expired 2) I make a tool that makes a single request that's indistinguishable from a web browser, there's a *massive* fediblock campaign and the FBI appears at my house
and finally....
3) this guy literally bogs down and causes performance issues for server admins, absolutely *nothing* on #fediblock.
Anywhere I make an account, the admins are harassed for "harbouuuuuuuring" me. Something tells me techhub has gotten zero (0) complaints about this dude.
iptables -A INPUT -m iprange --src-range 18.0.0.0-18.31.255.255 -j DROP iptables -A INPUT -m iprange --src-range 128.30.0.0-128.31.255.255 -j DROP iptables -A INPUT -m iprange --src-range 128.52.0.0-28.52.255.255 -j DROP iptables -A INPUT -m iprange --src-range 129.55.0.0-129.55.255.255 -j DROP iptables -A INPUT -m iprange --src-range 192.52.61.0-192.52.66.255 -j DROP iptables -A INPUT -m iprange --src-range 198.125.160.0-198.125.163.255 -j DROP iptables -A INPUT -m iprange --src-range 198.125.176.0-198.125.191.255 -j DROP
@burner@jeff@natalie@Drand Litterally why I told someone to ping abuse@mit.edu as this is the kind of shit that's going to hurt their connectivity at one point.
@jeff@natalie@lanodan@ashten I would say "federated moderation" is a thing: we send reports between servers, post things on tags like fediblock, have conversations over the network about what we are doing about what... It's not like every server is 100% independent in terms of enforcing rules and all that, and of course we all have to come to agreements about what we're willing to put up with from each other before limiting or blocking.
@Raccoon@jeff@natalie@ashten Moderation on the fediverse seems to be done those ways: - Ad-hoc: Admin saw one of those callout posts like FediBlock does, dedicated to act on it. (hashtags themselves not being really federated, they're just tags on posts, for example you can't follow them) - Reports: Maybe the only thing federated, except it's just messages and not actions - TheBadSpace, dzuk blocklist, …: Centralised, a self-crowned King says this server has to be blocked, they're also much worse than email DNSBLs as one simply doesn't gets removed
For me federated moderation would be more like Usenet control messages where an admin sends what they're blocking/removing/… in a standard format and other admins are free to do the same thing or not.
@jeff@burner@natalie@Drand They can, but they should be made aware of what's happening in their network and consequences of it. Imagine mit's fediverse server being effectively unreachable to like 20+% of the fediverse because of this. Or possibly even beyond the fediverse.
@lanodan@natalie@ashten@Raccoon right, it's mix of normative non normative control messages and angry posts. if only people read up on usenet before repeating it