toot.lgbt went out of their way to scrape this instance in order to issue a #fediblock against it, effectively working as a bad-actor to sabotage the domain.
This is (currently) a single-user instance, the timeline isn't public, and toot.lgbt (plus, all the instances they hang out with) were already blocked via /etc/hosts, meaning federation/communication to/from my server and theirs was impossible---they never saw, nor would have ever seen, any content from this instance (and vice-versa) past the point they were local-host loop-backed via /etc/hosts. Meaning, they purposely went out, and actively sought means of, retrieving content herein (to get upset over and then cry #fediblock).
If this isn't an example of maliciousness then I don't know what is. These Mastodon instances are a terroristic blight upon the Fediverse.
@silverpill > The ability to block outgoing requests will be added later. Let me know if this is important.
Blocking outgoing requests is important to me since most of those instances I have "blocked" were meant to block outgoing requests, primarily, vs. incoming. Because most of those instances are known bad-actor #fediblock bandwagon instances who get off on dog-piling and sabotaging other instances for the most minor of transgressions or ideological heresy. I've found it best practice to simply block those instances outright from the outset so that no federation takes place and one remains entirely off their "radar"---everyone's happy. One doesn't receive activities from them (they've nothing I want to see or hear) and the don't receive any activities from you (they've noting to complain about or disparage and attack you over). Otherwise, they'll go out of their way to look for problems and will then publicly crucify your instance and you'll end up on a list from which hundreds of instances will blindly follow. @mischievoustomato
This is their view of fsebugoutzone.org. There's a lot of interesting information in there. They've got, for example, `"processing_status": "completed"`, but they never launched any successful requests as far as I can tell. (I will have to look through the logs again.) They have `"connections": "33435"`, and this appears to be the peer count. They are using instances.social for the `thumbnail_proxy`, maybe that's where they got the list of instances. They have 16,795 on the list, and all of them have `"processing_status": "completed"`, so the queue is probably stored somewhere else.
{ "_id": { "$oid": "673f10ac2aa5fd2484163e28" }, "id": "6628f572b42b8088be06b2fb", "name": "fsebugoutzone.org", "added_at": "2024-04-24T12:05:06.281Z", "updated_at": "2024-11-21T10:02:14.842Z", "checked_at": "2024-11-21T10:02:14.842Z", "uptime": { "$numberInt": "1" }, "up": true, "dead": false, "version": null, "ipv6": false, "https_score": { "$numberInt": "10" }, "https_rank": "E ", "obs_score": { "$numberInt": "70" }, "obs_rank": "B ", "users": "1733", "statuses": "2072037", "connections": "33435", "open_registrations": false, "info": { "short_description": null, "full_description": "FSE temporary bugout zone until the new code is ready, but mostly a development instance, so it will not run like regular FSE: closed registrations (but if you had an account, your old username/password will work), I will shoot anything that annoys me while I am hacking (and if you are hoping for a warning shot, please do not annoy me until ammo prices drop), etc. Lots of things will be broken periodically because this is a development instance. Direct complaints to your friendly local anarchist @p, or if you are a total dick, just #fediblock us based on rumors/assumptions without trying to reach out, just like you did with FSE! Full explanation here: https://blog.freespeechextremist.com/blog/update-and-roadmap.html", "topic": "Free Speech Extremist", "languages": [], "other_languages_accepted": true, "federates_with": "all", "prohibited_content": [], "categories": [] }, "thumbnail": "/instance/thumbnail.jpeg", "thumbnail_proxy": "https://camo.instances.social/6079b328d69223bfa89de4e89dbfa2a691fbefdc/2f696e7374616e63652f7468756d626e61696c2e6a706567", "active_users": null, "email": "fedi@freespeechextremist.com", "admin": null, "loadtime": { "$date": { "$numberLong": "1732161080203" } }, "processing_status": "completed" },
Report to the instance's admin as well, as their "federation policy" states:This instance is intending to be a good neighbor to all instances in the Fediverse. We will work with remote admins to resolve any disputes between remote and local users, do not hesitate to reach out to the administrator (@kroner@seal.cafe).Emphasis mine.
2nd mod from asbestos dot cafe drops the "N" word.
1 screenshot shows their poor taste (also marked as sensitive, because of the nature of the photo) and the other, once again, shows it is a mod of that instance (server).
When the mods of asbestos dot cafe drops the "N" word, Fedi Block is the solution. 1 Screenshot shows their poor taste (marked sensitive, because of the nature of the photo), and the other shows they're one of the mods.