#blocklists — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #blocklists, aggregated by home.social.
-
My first #opensource security tool written in #rust is getting there. In small steps forward 💪
It aims to learn from requests on a web server (or a bunch of servers) and then have it taking decisive actions. Think of it like blocking AI crawlers or misbehaving clients. The idea is to combine it with #nginx as a starter. Mostly self-learning with the option to influence what gets blocked. Not only by IP. Optionally to be combined with #blocklists on a higher level, such as a firewall.
-
My first #opensource security tool written in #rust is getting there. In small steps forward 💪
It aims to learn from requests on a web server (or a bunch of servers) and then have it taking decisive actions. Think of it like blocking AI crawlers or misbehaving clients. The idea is to combine it with #nginx as a starter. Mostly self-learning with the option to influence what gets blocked. Not only by IP. Optionally to be combined with #blocklists on a higher level, such as a firewall.
-
My first #opensource security tool written in #rust is getting there. In small steps forward 💪
It aims to learn from requests on a web server (or a bunch of servers) and then have it taking decisive actions. Think of it like blocking AI crawlers or misbehaving clients. The idea is to combine it with #nginx as a starter. Mostly self-learning with the option to influence what gets blocked. Not only by IP. Optionally to be combined with #blocklists on a higher level, such as a firewall.
-
My first #opensource security tool written in #rust is getting there. In small steps forward 💪
It aims to learn from requests on a web server (or a bunch of servers) and then have it taking decisive actions. Think of it like blocking AI crawlers or misbehaving clients. The idea is to combine it with #nginx as a starter. Mostly self-learning with the option to influence what gets blocked. Not only by IP. Optionally to be combined with #blocklists on a higher level, such as a firewall.
-
My first #opensource security tool written in #rust is getting there. In small steps forward 💪
It aims to learn from requests on a web server (or a bunch of servers) and then have it taking decisive actions. Think of it like blocking AI crawlers or misbehaving clients. The idea is to combine it with #nginx as a starter. Mostly self-learning with the option to influence what gets blocked. Not only by IP. Optionally to be combined with #blocklists on a higher level, such as a firewall.
-
A NL-based scanner is sweeping #Reticulum using many IPs across a range to touch public RNS transport node on #port4242 . It is drive-by port-scanning, not peering, with up to 5 ephemeral inbound flows, a few hundred bytes each, no sustained links. Same IPs also hit web 80/443 & #Radicle #port8776 #AbuseIPDB is 100 #IDS #firewall Is there a run and forget mesh/distributed IP #blocklist tool to both harvest & share IPv4 (and IPv6) #blocklists? A "bot reaper agent"? A tidy web would be ace.
-
A NL-based scanner is sweeping #Reticulum using many IPs across a range to touch public RNS transport node on #port4242 . It is drive-by port-scanning, not peering, with up to 5 ephemeral inbound flows, a few hundred bytes each, no sustained links. Same IPs also hit web 80/443 & #Radicle #port8776 #AbuseIPDB is 100 #IDS #firewall Is there a run and forget mesh/distributed IP #blocklist tool to both harvest & share IPv4 (and IPv6) #blocklists? A "bot reaper agent"? A tidy web would be ace.
-
A NL-based scanner is sweeping #Reticulum using many IPs across a range to touch public RNS transport node on #port4242 . It is drive-by port-scanning, not peering, with up to 5 ephemeral inbound flows, a few hundred bytes each, no sustained links. Same IPs also hit web 80/443 & #Radicle #port8776 #AbuseIPDB is 100 #IDS #firewall Is there a run and forget mesh/distributed IP #blocklist tool to both harvest & share IPv4 (and IPv6) #blocklists? A "bot reaper agent"? A tidy web would be ace.
-
A NL-based scanner is sweeping #Reticulum using many IPs across a range to touch public RNS transport node on #port4242 . It is drive-by port-scanning, not peering, with up to 5 ephemeral inbound flows, a few hundred bytes each, no sustained links. Same IPs also hit web 80/443 & #Radicle #port8776 #AbuseIPDB is 100 #IDS #firewall Is there a run and forget mesh/distributed IP #blocklist tool to both harvest & share IPv4 (and IPv6) #blocklists? A "bot reaper agent"? A tidy web would be ace.
-
A NL-based scanner is sweeping #Reticulum using many IPs across a range to touch public RNS transport node on #port4242 . It is drive-by port-scanning, not peering, with up to 5 ephemeral inbound flows, a few hundred bytes each, no sustained links. Same IPs also hit web 80/443 & #Radicle #port8776 #AbuseIPDB is 100 #IDS #firewall Is there a run and forget mesh/distributed IP #blocklist tool to both harvest & share IPv4 (and IPv6) #blocklists? A "bot reaper agent"? A tidy web would be ace.
-
Pour celles et ceux que ça pourrait intéresser :
https://des-listes-de-blocage.pour-configurer.des.services/
Bon ça a été créé en 1h, la peinture est pas fraîche.
-
Pour celles et ceux que ça pourrait intéresser :
https://des-listes-de-blocage.pour-configurer.des.services/
Bon ça a été créé en 1h, la peinture est pas fraîche.
-
Pour celles et ceux que ça pourrait intéresser :
https://des-listes-de-blocage.pour-configurer.des.services/
Bon ça a été créé en 1h, la peinture est pas fraîche.
-
It's funny, defecting from the anti AI camp got me on dozens of #blocklists but barely increased the folks blocking me.
-
@Chao-c'Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.
Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)
The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.
Seriously?
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.- It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
- It used to have optional StatusNet support which is how Mastodon federated with it immediately.
- It can optionally federate with diaspora*; Mastodon can't do that.
- It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
- It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
- It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
- It still has an optional built-in XMPP client; Mastodon doesn't have that.
Mastodon is simply lights years ahead.
I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).
The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta -
@Chao-c'Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.
Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)
The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.
Seriously?
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.- It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
- It used to have optional StatusNet support which is how Mastodon federated with it immediately.
- It can optionally federate with diaspora*; Mastodon can't do that.
- It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
- It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
- It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
- It still has an optional built-in XMPP client; Mastodon doesn't have that.
Mastodon is simply lights years ahead.
I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).
The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta -
@Chao-c'Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.
Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)
The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.
Seriously?
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.- It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
- It used to have optional StatusNet support which is how Mastodon federated with it immediately.
- It can optionally federate with diaspora*; Mastodon can't do that.
- It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
- It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
- It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
- It still has an optional built-in XMPP client; Mastodon doesn't have that.
Mastodon is simply lights years ahead.
I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).
The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta -
@Chao-c'Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.
Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)
The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.
Seriously?
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.- It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
- It used to have optional StatusNet support which is how Mastodon federated with it immediately.
- It can optionally federate with diaspora*; Mastodon can't do that.
- It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
- It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
- It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
- It still has an optional built-in XMPP client; Mastodon doesn't have that.
Mastodon is simply lights years ahead.
I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).
The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta -
@Chao-c'Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.
Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.
This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.
(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.
Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.
As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)
The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).
Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.
But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.
From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.
The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.
On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.
At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.
Seriously?
Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.
Hubzilla is almost as much an omni-federational monster as Friendica.- It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
- It used to have optional StatusNet support which is how Mastodon federated with it immediately.
- It can optionally federate with diaspora*; Mastodon can't do that.
- It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
- It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
- It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
- It still has an optional built-in XMPP client; Mastodon doesn't have that.
Mastodon is simply lights years ahead.
I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.
If the latter, I'll gladly prove you wrong.I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).
The problem with this is blind faith in those who maintain the blocklists.
Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.
Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.
And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta -
If you want to avoid Israeli online resources and supporters of Israeli apartheid, genocide, and wars, here’s a maintained community blocklist for the AWAGAM blocker (no affiliation):
https://gitlab.com/ehud48/blocklist/-/raw/main/blocklist.json blocks 3 TLDs, 191 domains, and 366 URLs.
Import in the AWAGAM extension—and consider proposing edits or forking to extend the list (happy to feature your own blocklist, too)!
-
If you want to avoid Israeli online resources and supporters of Israeli apartheid, genocide, and wars, here’s a maintained community blocklist for the AWAGAM blocker (no affiliation):
https://gitlab.com/ehud48/blocklist/-/raw/main/blocklist.json blocks 3 TLDs, 191 domains, and 366 URLs.
Import in the AWAGAM extension—and consider proposing edits or forking to extend the list (happy to feature your own blocklist, too)!
-
If you want to avoid Israeli online resources and supporters of Israeli apartheid, genocide, and wars, here’s a maintained community blocklist for the AWAGAM blocker (no affiliation):
https://gitlab.com/ehud48/blocklist/-/raw/main/blocklist.json blocks 3 TLDs, 191 domains, and 366 URLs.
Import in the AWAGAM extension—and consider proposing edits or forking to extend the list (happy to feature your own blocklist, too)!
-
If you want to avoid Israeli online resources and supporters of Israeli apartheid, genocide, and wars, here’s a maintained community blocklist for the AWAGAM blocker (no affiliation):
https://gitlab.com/ehud48/blocklist/-/raw/main/blocklist.json blocks 3 TLDs, 191 domains, and 366 URLs.
Import in the AWAGAM extension—and consider proposing edits or forking to extend the list (happy to feature your own blocklist, too)!
-
If you want to avoid Israeli online resources and supporters of Israeli apartheid, genocide, and wars, here’s a maintained community blocklist for the AWAGAM blocker (no affiliation):
https://gitlab.com/ehud48/blocklist/-/raw/main/blocklist.json blocks 3 TLDs, 191 domains, and 366 URLs.
Import in the AWAGAM extension—and consider proposing edits or forking to extend the list (happy to feature your own blocklist, too)!
-
Have the topics of shared blocklists and shared content labellers been discussed at a past FediForum? I'd like to review the notes if so.
-
Have the topics of shared blocklists and shared content labellers been discussed at a past FediForum? I'd like to review the notes if so.
-
Have the topics of shared blocklists and shared content labellers been discussed at a past FediForum? I'd like to review the notes if so.
-
Have the topics of shared blocklists and shared content labellers been discussed at a past FediForum? I'd like to review the notes if so.
-
The Community Blocklist blocks a lot. But the Threat Forecast Blocklist goes further:
📊 ~50% more attackers blocked
📊 1:40 prevention ratio
📊 Built from your own attack patternsAvailable for the CrowdSec Console Premium plan, and still one of the most powerful ways to reduce noise before it starts.
Learn more 👉 https://crowdsec.net/blog/threat-forecast-blocklist-release
-
The Community Blocklist blocks a lot. But the Threat Forecast Blocklist goes further:
📊 ~50% more attackers blocked
📊 1:40 prevention ratio
📊 Built from your own attack patternsAvailable for the CrowdSec Console Premium plan, and still one of the most powerful ways to reduce noise before it starts.
Learn more 👉 https://crowdsec.net/blog/threat-forecast-blocklist-release
-
The Community Blocklist blocks a lot. But the Threat Forecast Blocklist goes further:
📊 ~50% more attackers blocked
📊 1:40 prevention ratio
📊 Built from your own attack patternsAvailable for the CrowdSec Console Premium plan, and still one of the most powerful ways to reduce noise before it starts.
Learn more 👉 https://crowdsec.net/blog/threat-forecast-blocklist-release
-
The Community Blocklist blocks a lot. But the Threat Forecast Blocklist goes further:
📊 ~50% more attackers blocked
📊 1:40 prevention ratio
📊 Built from your own attack patternsAvailable for the CrowdSec Console Premium plan, and still one of the most powerful ways to reduce noise before it starts.
Learn more 👉 https://crowdsec.net/blog/threat-forecast-blocklist-release
-
Bluesky is An Ontological Space for Sadomasochism, Trolling, & Schadenfreude
So, during the initial exodus from Twitter after it became X following Elon Musk’s purchase, many people left but kept their accounts, purposefully to bully, surveil, antagonize, and troll others. People—including me—moved to Bluesky, Mastodon, or both, and used their Twitter accounts purely for harassment and similar behavior. Essentially, X became the place you went to act like a dumpster fire. Because most people within occult niches are highly toxic, I tend to not only block them but also block anyone they follow for reasons I’m about to explain.
I really only use that account to criticize occulture, post nudes, or share YouTube videos. Since I’m aware of fed posting, I avoid commenting on political topics or anarchist discourse on the Clearnet. Keep that in mind. If you scroll through my profile, you’ll see me poking fun at chaotes, posting nudes, gushing about or complaining about my husband, sharing dating horror story YouTube videos, or pet grooming videos. If you look at my likes, you’ll only see gay porn, mathematics papers, engineering papers, etc. There’s no mention of anything political, especially genocides.
There was a person I’d never interacted with who was part of a starter pack for occultists. I blocked them. Then I woke up this morning to find I was added to this list:
Chomsky Honks
Genocide apologist posting cringe from a Starbucks as it burns down around themSo, with all that in mind, these occultists I’ve never interacted with added me to a list. I am neither invested in Bluesky nor strongly connected to their network, primarily because I block almost everyone on it and don’t ever look at any feeds whatsoever, including the Home, followers, or Discover feeds. Therefore, the posts I do interact with are from pockets of people way outside my network. It’s kind of like driving to the bathhouse in Atlanta from a small town in Bubbafuck, Georgia, because everyone in your small town is garbage. Same idea, ontologically.
Honestly, I don’t care, because I’ve mostly moved back to Mastodon and blog more.
What they’ve done is implicitly a form of defamation, because they feel slighted and justified in defaming someone they don’t know, simply because a stranger they’ve never spoken to blocked them. I tend to do a basic block on anyone who blocks me, because if you’ve decided you don’t want to see me, there’s probably no good-faith reason for us to engage in the future. It’s likely there’s some malicious intent later on. As you can see with this, I was correct.
So, in order for them to know I blocked them, they had to continuously check who had blocked them, and they believe people who block them should be punished through bullying. Since the description of the list doesn’t fit me, they retaliated out of malice. The idea behind these cliques is pretty simple: they feel threatened by anyone who rejects their normative statements because it means they are being rejected, and they view any form of dissent as an existential threat. As a result, they believe people who reject them, set boundaries, or dissent from the consensus of their culture need to be punished, and the AT protocol provides convenient tools for brigading. Ironically, these people are anti-fascist yet have a very Christian-like evangelical way of viewing the world. The lack of insight is pretty funny.
I’m the child of cult leaders and members with Cluster B personalities, so I’m not clutching my pearls, especially since I’m already set up elsewhere outside of Bluesky. They do not have the means to impose significant consequences on me, so I find it amusing. I genuinely find it funny how they eat each other. I’m not calling anyone to action—I’m just enjoying the fire.
This person wasn’t aware of who I was. We never interacted, and being added to a list that defames me happened directly after I blocked them without any prior interaction. I saw their account from the firehose and wasn’t algorithmically presented with it, meaning we’re not even in the same clique. Now, if they had said something like “spams hashtags, trolls, makes alts,” that would make sense.
When you look at it for what it is, they wanted to defame, disparage, and brigade—punitive actions because they interpreted a boundary as hostile. This is projection, as they are weaponizing a mechanism to enforce boundaries. Do I care? No. I’m just pointing out how it turned its predecessor, X, into what it is now. It became a place for people to harass others, not a space for genuine, good-faith discussions, connections, or even debates. That is not my interpretation.
Well, to anyone who knows, you might ask: Did they block you because you have a particular reputation? No. I am a Web 1.0 mage, so the networks I’m known in have roots and associations in the old forums. The occulture people who have fixated on me for years go all the way back to Wizard Forums, the psionics forums, the unsolved mystery forums, etc., from the early 2000s. If you’re a circa 2016 social media influencer mage, you probably wouldn’t know me—primarily because the moment I see you, I’ll block you. There’s also a moderation block list just for me and my alts.
This behavior is typical of the culture on Bluesky, so much so that it’s a common complaint people now have—many no longer view block lists as legitimate moderation tools. People are being advised to be skeptical of lists with a large number of people.
Oh, I’m not playing the victim here. I don’t care, because I could easily get back at them. I’m infamously vindictive and petty. More importantly, it supports my point and vindicates me. I’m not signaling victimhood; rather, I’m pointing out a culture, albeit one I participate in. Tying this back to my initial point: part of what signaled the death of Twitter as a serious forum and its transformation into X was the bullying. A while ago, I did a phylogenetic memetic analysis that basically showed how the culture on Bluesky is highly derivative of image boards. But don’t you bully and troll people? Yes, yes, I do – on Bluesky, and the lack of moderation and culture enable it. That’s my point.
Bluesky is an accelerationist and reactionary platform that gives you the tools to surveil and harass people. The developers of Bluesky and the AT Protocol have explicitly said they are technological accelerationists and libertarians. I’m not virtue signaling here; rather, I am saying Bluesky is a reactionary platform, so its culture should be understood as performative, hostile, and adversarial—not cooperative or collaborative. Just like Twitter. You can’t do what I do on Bluesky on the fediverse, because the culture won’t allow it.
You saw this type of behavior on Tumblr, where the population carrying the memetics of that culture migrated to Twitter and now Bluesky. Essentially, Bluesky became a place where malice, bullying, and hostile behavior became so normalized that I’m not even upset about lists being weaponized like this. For example, I’m not posting this on Bluesky, and I, myself, have bullied people on Bluesky. But I behave myself on Mastodon. I am using myself as an example. The trolling is happening on Bluesky. The thoughtful posts are happening on Mastodon. The blog this will be posted on is federated, so this is being posted to the fediverse.
That’s what happened to Twitter. It started normalizing hostile, toxic behavior, so that people left the platform and only returned to Twitter for schadenfreude. I have my own WordPress fediverse instance. I am just on Bluesky for the schadenfreude.
-
Bluesky is An Ontological Space for Sadomasochism, Trolling, & Schadenfreude
So, during the initial exodus from Twitter after it became X following Elon Musk’s purchase, many people left but kept their accounts, purposefully to bully, surveil, antagonize, and troll others. People—including me—moved to Bluesky, Mastodon, or both, and used their Twitter accounts purely for harassment and similar behavior. Essentially, X became the place you went to act like a dumpster fire. Because most people within occult niches are highly toxic, I tend to not only block them but also block anyone they follow for reasons I’m about to explain.
I really only use that account to criticize occulture, post nudes, or share YouTube videos. Since I’m aware of fed posting, I avoid commenting on political topics or anarchist discourse on the Clearnet. Keep that in mind. If you scroll through my profile, you’ll see me poking fun at chaotes, posting nudes, gushing about or complaining about my husband, sharing dating horror story YouTube videos, or pet grooming videos. If you look at my likes, you’ll only see gay porn, mathematics papers, engineering papers, etc. There’s no mention of anything political, especially genocides.
There was a person I’d never interacted with who was part of a starter pack for occultists. I blocked them. Then I woke up this morning to find I was added to this list:
Chomsky Honks
Genocide apologist posting cringe from a Starbucks as it burns down around themSo, with all that in mind, these occultists I’ve never interacted with added me to a list. I am neither invested in Bluesky nor strongly connected to their network, primarily because I block almost everyone on it and don’t ever look at any feeds whatsoever, including the Home, followers, or Discover feeds. Therefore, the posts I do interact with are from pockets of people way outside my network. It’s kind of like driving to the bathhouse in Atlanta from a small town in Bubbafuck, Georgia, because everyone in your small town is garbage. Same idea, ontologically.
Honestly, I don’t care, because I’ve mostly moved back to Mastodon and blog more.
What they’ve done is implicitly a form of defamation, because they feel slighted and justified in defaming someone they don’t know, simply because a stranger they’ve never spoken to blocked them. I tend to do a basic block on anyone who blocks me, because if you’ve decided you don’t want to see me, there’s probably no good-faith reason for us to engage in the future. It’s likely there’s some malicious intent later on. As you can see with this, I was correct.
So, in order for them to know I blocked them, they had to continuously check who had blocked them, and they believe people who block them should be punished through bullying. Since the description of the list doesn’t fit me, they retaliated out of malice. The idea behind these cliques is pretty simple: they feel threatened by anyone who rejects their normative statements because it means they are being rejected, and they view any form of dissent as an existential threat. As a result, they believe people who reject them, set boundaries, or dissent from the consensus of their culture need to be punished, and the AT protocol provides convenient tools for brigading. Ironically, these people are anti-fascist yet have a very Christian-like evangelical way of viewing the world. The lack of insight is pretty funny.
I’m the child of cult leaders and members with Cluster B personalities, so I’m not clutching my pearls, especially since I’m already set up elsewhere outside of Bluesky. They do not have the means to impose significant consequences on me, so I find it amusing. I genuinely find it funny how they eat each other. I’m not calling anyone to action—I’m just enjoying the fire.
This person wasn’t aware of who I was. We never interacted, and being added to a list that defames me happened directly after I blocked them without any prior interaction. I saw their account from the firehose and wasn’t algorithmically presented with it, meaning we’re not even in the same clique. Now, if they had said something like “spams hashtags, trolls, makes alts,” that would make sense.
When you look at it for what it is, they wanted to defame, disparage, and brigade—punitive actions because they interpreted a boundary as hostile. This is projection, as they are weaponizing a mechanism to enforce boundaries. Do I care? No. I’m just pointing out how it turned its predecessor, X, into what it is now. It became a place for people to harass others, not a space for genuine, good-faith discussions, connections, or even debates. That is not my interpretation.
Well, to anyone who knows, you might ask: Did they block you because you have a particular reputation? No. I am a Web 1.0 mage, so the networks I’m known in have roots and associations in the old forums. The occulture people who have fixated on me for years go all the way back to Wizard Forums, the psionics forums, the unsolved mystery forums, etc., from the early 2000s. If you’re a circa 2016 social media influencer mage, you probably wouldn’t know me—primarily because the moment I see you, I’ll block you. There’s also a moderation block list just for me and my alts.
This behavior is typical of the culture on Bluesky, so much so that it’s a common complaint people now have—many no longer view block lists as legitimate moderation tools. People are being advised to be skeptical of lists with a large number of people.
Oh, I’m not playing the victim here. I don’t care, because I could easily get back at them. I’m infamously vindictive and petty. More importantly, it supports my point and vindicates me. I’m not signaling victimhood; rather, I’m pointing out a culture, albeit one I participate in. Tying this back to my initial point: part of what signaled the death of Twitter as a serious forum and its transformation into X was the bullying. A while ago, I did a phylogenetic memetic analysis that basically showed how the culture on Bluesky is highly derivative of image boards. But don’t you bully and troll people? Yes, yes, I do – on Bluesky, and the lack of moderation and culture enable it. That’s my point.
Bluesky is an accelerationist and reactionary platform that gives you the tools to surveil and harass people. The developers of Bluesky and the AT Protocol have explicitly said they are technological accelerationists and libertarians. I’m not virtue signaling here; rather, I am saying Bluesky is a reactionary platform, so its culture should be understood as performative, hostile, and adversarial—not cooperative or collaborative. Just like Twitter. You can’t do what I do on Bluesky on the fediverse, because the culture won’t allow it.
You saw this type of behavior on Tumblr, where the population carrying the memetics of that culture migrated to Twitter and now Bluesky. Essentially, Bluesky became a place where malice, bullying, and hostile behavior became so normalized that I’m not even upset about lists being weaponized like this. For example, I’m not posting this on Bluesky, and I, myself, have bullied people on Bluesky. But I behave myself on Mastodon. I am using myself as an example. The trolling is happening on Bluesky. The thoughtful posts are happening on Mastodon. The blog this will be posted on is federated, so this is being posted to the fediverse.
That’s what happened to Twitter. It started normalizing hostile, toxic behavior, so that people left the platform and only returned to Twitter for schadenfreude. I have my own WordPress fediverse instance. I am just on Bluesky for the schadenfreude.
-
CW: Content Warning: Fediblock, Politics, USPol
The Speakeasy has voted to pre-emptively defederate all known United States federal government domains due to their status as a rogue state, their wanton rights violations, their bigotry, and their use of official government channels for authoritarian propaganda.
In the interest of being good fedi citizens, we have shared our blocklist (split into six parts for ease of management; the list is 1300 entries long) at: https://speakeasy.bardicperspiration.com/blocklists.html
We exempted local and state sites; we may create a list for those later for those interested.
You are free to use or edit this as you like.
If you are going to use the bloclklist, please do make sure that your members understand that this is not a security fix. If the federal government wants to scrape public posts, it can do so pretty easily. This may prevent some future propaganda from showing up in someone's feed but honestly, it's meant to call out egregiously horrifying behavior by a state actor, not as a security measure.
We see this as a small action to show the world where we stand, in a way that we control, and we hope our fedi allies join us in our small act of protest.
-
CW: Content Warning: Fediblock, Politics, USPol
The Speakeasy has voted to pre-emptively defederate all known United States federal government domains due to their status as a rogue state, their wanton rights violations, their bigotry, and their use of official government channels for authoritarian propaganda.
In the interest of being good fedi citizens, we have shared our blocklist (split into six parts for ease of management; the list is 1300 entries long) at: https://speakeasy.bardicperspiration.com/blocklists.html
We exemopted local and state sites; we may create a list for those later for those interested.
You are free to use or edit this as you like.
If you are going to use the bloclklist, please do make sure that your members understand that this is not a security fix. If the federal government wants to scrape public posts, it can do so pretty easily. This may prevent some future propaganda from showing up in someone's feed but honestly, it's meant to call out egregiously horrifying behavior by a state actor, not as a security measure.
We see this as a small action to show the world where we stand, in a way that we control, and we hope our fedi allies join us in our small act of protest.
-
CW: Content Warning: Fediblock, Politics, USPol
The Speakeasy has voted to pre-emptively defederate all known United States federal government domains due to their status as a rogue state, their wanton rights violations, their bigotry, and their use of official government channels for authoritarian propaganda.
In the interest of being good fedi citizens, we have shared our blocklist (split into six parts for ease of management; the list is 1300 entries long) at: https://speakeasy.bardicperspiration.com/blocklists.html
We exempted local and state sites; we may create a list for those later for those interested.
You are free to use or edit this as you like.
If you are going to use the bloclklist, please do make sure that your members understand that this is not a security fix. If the federal government wants to scrape public posts, it can do so pretty easily. This may prevent some future propaganda from showing up in someone's feed but honestly, it's meant to call out egregiously horrifying behavior by a state actor, not as a security measure.
We see this as a small action to show the world where we stand, in a way that we control, and we hope our fedi allies join us in our small act of protest.
-
CW: Content Warning: Fediblock, Politics, USPol
The Speakeasy has voted to pre-emptively defederate all known United States federal government domains due to their status as a rogue state, their wanton rights violations, their bigotry, and their use of official government channels for authoritarian propaganda.
In the interest of being good fedi citizens, we have shared our blocklist (split into six parts for ease of management; the list is 1300 entries long) at: https://speakeasy.bardicperspiration.com/blocklists.html
We exempted local and state sites; we may create a list for those later for those interested.
You are free to use or edit this as you like.
If you are going to use the bloclklist, please do make sure that your members understand that this is not a security fix. If the federal government wants to scrape public posts, it can do so pretty easily. This may prevent some future propaganda from showing up in someone's feed but honestly, it's meant to call out egregiously horrifying behavior by a state actor, not as a security measure.
We see this as a small action to show the world where we stand, in a way that we control, and we hope our fedi allies join us in our small act of protest.
-
CW: Content Warning: Fediblock, Politics, USPol
The Speakeasy has voted to pre-emptively defederate all known United States federal government domains due to their status as a rogue state, their wanton rights violations, their bigotry, and their use of official government channels for authoritarian propaganda.
In the interest of being good fedi citizens, we have shared our blocklist (split into six parts for ease of management; the list is 1300 entries long) at: https://speakeasy.bardicperspiration.com/blocklists.html
We exemopted local and state sites; we may create a list for those later for those interested.
You are free to use or edit this as you like.
If you are going to use the bloclklist, please do make sure that your members understand that this is not a security fix. If the federal government wants to scrape public posts, it can do so pretty easily. This may prevent some future propaganda from showing up in someone's feed but honestly, it's meant to call out egregiously horrifying behavior by a state actor, not as a security measure.
We see this as a small action to show the world where we stand, in a way that we control, and we hope our fedi allies join us in our small act of protest.
-
The update you have been waiting for:
"Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off?" https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
now has the complete 2025 data in place. #openbsd #spamd #greytrapping #spam #antispam #cybercrime #spamtraps #blocklists
-
The update you have been waiting for:
"Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off?" https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
now has the complete 2025 data in place. #openbsd #spamd #greytrapping #spam #antispam #cybercrime #spamtraps #blocklists
-
The update you have been waiting for:
"Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off?" https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
now has the complete 2025 data in place. #openbsd #spamd #greytrapping #spam #antispam #cybercrime #spamtraps #blocklists
-
The update you have been waiting for:
"Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off?" https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
now has the complete 2025 data in place. #openbsd #spamd #greytrapping #spam #antispam #cybercrime #spamtraps #blocklists
-
The update you have been waiting for:
"Eighteen Years of Greytrapping - Is the Weirdness Finally Paying Off?" https://nxdomain.no/~peter/eighteen_years_of_greytrapping.html (tracked https://bsdly.blogspot.com/2025/08/eighteen-years-of-greytrapping-is.html)
now has the complete 2025 data in place. #openbsd #spamd #greytrapping #spam #antispam #cybercrime #spamtraps #blocklists
-
@mattblaze I love my keyword filters or #blocklists. Some people or hashtags I follow also post and contain things I don't care about at all. Nothing outrageous, imo, my two main lists block lots of sports and as much generated slop as I can block😋
Sometimes things are not caught and I'm happy to add to my lists, while keeping up to speed on everything else these good people talk about.
The bestest thing is that the others can enjoy discussing, for example, sports to their heart's content ☺️
-
@mattblaze I love my keyword filters or #blocklists. Some people or hashtags I follow also post and contain things I don't care about at all. Nothing outrageous, imo, my two main lists block lots of sports and as much generated slop as I can block😋
Sometimes things are not caught and I'm happy to add to my lists, while keeping up to speed on everything else these good people talk about.
The bestest thing is that the others can enjoy discussing, for example, sports to their heart's content ☺️
-
@mattblaze I love my keyword filters or #blocklists. Some people or hashtags I follow also post and contain things I don't care about at all. Nothing outrageous, imo, my two main lists block lots of sports and as much generated slop as I can block😋
Sometimes things are not caught and I'm happy to add to my lists, while keeping up to speed on everything else these good people talk about.
The bestest thing is that the others can enjoy discussing, for example, sports to their heart's content ☺️
-
@mattblaze I love my keyword filters or #blocklists. Some people or hashtags I follow also post and contain things I don't care about at all. Nothing outrageous, imo, my two main lists block lots of sports and as much generated slop as I can block😋
Sometimes things are not caught and I'm happy to add to my lists, while keeping up to speed on everything else these good people talk about.
The bestest thing is that the others can enjoy discussing, for example, sports to their heart's content ☺️
-
@mattblaze I love my keyword filters or #blocklists. Some people or hashtags I follow also post and contain things I don't care about at all. Nothing outrageous, imo, my two main lists block lots of sports and as much generated slop as I can block😋
Sometimes things are not caught and I'm happy to add to my lists, while keeping up to speed on everything else these good people talk about.
The bestest thing is that the others can enjoy discussing, for example, sports to their heart's content ☺️
-
#Fediverse #Blocklists: #Moderation in Noncapitalist #SocialMedia
> the paper explores how fediverse blocklist developers attempt to mitigate the problems of lists while also generating knowledge about content moderation@rwg York University
2025-09-20: https://www.triple-c.at/index.php/tripleC/article/view/1556
#SciComm #WissKomm #FediModeration #CulturalStudies #SocialScience #SocialMedia #ContentModeration
-
#Fediverse #Blocklists: #Moderation in Noncapitalist #SocialMedia
> the paper explores how fediverse blocklist developers attempt to mitigate the problems of lists while also generating knowledge about content moderation@aram York University
2025-09-20: https://www.triple-c.at/index.php/tripleC/article/view/1556
#SciComm #WissKomm #FediModeration #CulturalStudies #SocialScience #SocialMedia #ContentModeration
-
#Fediverse #Blocklists: #Moderation in Noncapitalist #SocialMedia
> the paper explores how fediverse blocklist developers attempt to mitigate the problems of lists while also generating knowledge about content moderation@rwg York University
2025-09-20: https://www.triple-c.at/index.php/tripleC/article/view/1556
#SciComm #WissKomm #FediModeration #CulturalStudies #SocialScience #SocialMedia #ContentModeration
-
#Fediverse #Blocklists: #Moderation in Noncapitalist #SocialMedia
> the paper explores how fediverse blocklist developers attempt to mitigate the problems of lists while also generating knowledge about content moderation@aram York University
2025-09-20: https://www.triple-c.at/index.php/tripleC/article/view/1556
#SciComm #WissKomm #FediModeration #CulturalStudies #SocialScience #SocialMedia #ContentModeration
-
#Fediverse #Blocklists: #Moderation in Noncapitalist #SocialMedia
> the paper explores how fediverse blocklist developers attempt to mitigate the problems of lists while also generating knowledge about content moderation@aram York University
2025-09-20: https://www.triple-c.at/index.php/tripleC/article/view/1556
#SciComm #WissKomm #FediModeration #CulturalStudies #SocialScience #SocialMedia #ContentModeration
-
Stop mass exploitation attempts before they reach your perimeter with #CrowdSecBlocklists.
🔹 What makes CrowdSec Blocklists unique?
- Real-time protection powered by a global community of defenders 🌍
- Up to 80% reduction in security alert volume
- 5% daily rotation of malicious IPs for up-to-date coverage
- 36% of aggressive IPs remain unknown to any other vendor for at least a week
- On average, we’re 7–60 days ahead in detecting malicious IPs compared to other blocklists
- 16% of these IPs stay undiscovered by others for 15–20 daysPreemptively block malicious IPs, and stay ahead of attackers.
👉 Learn more: http://crowdsec.net/blocklists
-
Stop mass exploitation attempts before they reach your perimeter with #CrowdSecBlocklists.
🔹 What makes CrowdSec Blocklists unique?
- Real-time protection powered by a global community of defenders 🌍
- Up to 80% reduction in security alert volume
- 5% daily rotation of malicious IPs for up-to-date coverage
- 36% of aggressive IPs remain unknown to any other vendor for at least a week
- On average, we’re 7–60 days ahead in detecting malicious IPs compared to other blocklists
- 16% of these IPs stay undiscovered by others for 15–20 daysPreemptively block malicious IPs, and stay ahead of attackers.
👉 Learn more: http://crowdsec.net/blocklists
-
Stop mass exploitation attempts before they reach your perimeter with #CrowdSecBlocklists.
🔹 What makes CrowdSec Blocklists unique?
- Real-time protection powered by a global community of defenders 🌍
- Up to 80% reduction in security alert volume
- 5% daily rotation of malicious IPs for up-to-date coverage
- 36% of aggressive IPs remain unknown to any other vendor for at least a week
- On average, we’re 7–60 days ahead in detecting malicious IPs compared to other blocklists
- 16% of these IPs stay undiscovered by others for 15–20 daysPreemptively block malicious IPs, and stay ahead of attackers.
👉 Learn more: http://crowdsec.net/blocklists
-
Stop mass exploitation attempts before they reach your perimeter with #CrowdSecBlocklists.
🔹 What makes CrowdSec Blocklists unique?
- Real-time protection powered by a global community of defenders 🌍
- Up to 80% reduction in security alert volume
- 5% daily rotation of malicious IPs for up-to-date coverage
- 36% of aggressive IPs remain unknown to any other vendor for at least a week
- On average, we’re 7–60 days ahead in detecting malicious IPs compared to other blocklists
- 16% of these IPs stay undiscovered by others for 15–20 daysPreemptively block malicious IPs, and stay ahead of attackers.
👉 Learn more: http://crowdsec.net/blocklists
-
@Roni Rolle Laukkarinen That's probably safer, more reliable and more sensible than those Fediverse blocklists that are compiled by easily triggered snowflakes who have never understood the Fediverse beyond Mastodon, and that are barely or not at all curated.
#FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Blocklist #Blocklists #BlockListMeta #CWBlocklistMeta -
#moderation is a shit job. always was, always will be. it's a human problem, no tech can dispel the chore. someone always has to be there, moderating
of course tooling can help immensely. the tooling shifts and manages the chore. that shift can be in good ways. also maybe unintentional bad ways
you know all this
i'm just laying it out so i can say:
on #bluesky, and on #mastodon, as you say, #blocklists create new terrible problems
i'm saying this tooling shift is a bad idea