#blocklist — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #blocklist, aggregated by home.social.
-
Weekly block list report: 3,549 entries; 3,521 valid / 28 invalid; 2 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,549 entries; 3,521 valid / 28 invalid; 2 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,539 entries; 3,517 valid / 22 invalid; 0 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,539 entries; 3,517 valid / 22 invalid; 0 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Jetzt habe ich hoffentlich Ruhe vor bestimmten penetranten Werbeanrufern...
-
Jetzt habe ich hoffentlich Ruhe vor bestimmten penetranten Werbeanrufern...
-
A new addition to the #HPT #AI #Blocklist was created yesterday. HPT-partial-DevTools-AI-List
It lists, in #HOSTS file format, 3rd Party Tools and resources used by #developers of apps, add-ins, and embedded modules or scripts, where they provide an additional or alternate connection URL that negates using an AI/LLM provider's well known URL for blocking. Essentially, they become a 'middleman' for data processing and reroute tasks through their own, or others, domains
-
A new addition to the #HPT #AI #Blocklist was created yesterday. HPT-partial-DevTools-AI-List
It lists, in #HOSTS file format, 3rd Party Tools and resources used by #developers of apps, add-ins, and embedded modules or scripts, where they provide an additional or alternate connection URL that negates using an AI/LLM provider's well known URL for blocking. Essentially, they become a 'middleman' for data processing and reroute tasks through their own, or others, domains
-
@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 -
Weekly block list report: 3,538 entries; 3,513 valid / 25 invalid; 4 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,538 entries; 3,513 valid / 25 invalid; 4 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Der komplette Server ist ein MAGA-Paradies: @noauthority.social
#FediBlock #Blocklist -
Weekly block list report: 3,540 entries; 3,512 valid / 28 invalid; 3 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,540 entries; 3,512 valid / 28 invalid; 3 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
The #LG [1] privacy / security debacle - where merely plugging in one of their monitors *silently* installs a spyware/adware application with system-level #privileges [2] and sets it to auto-start, also silently - reminded me of a question I've wondered about.
The last version of Windows that I ran was Win98, so I'm rather out-of-date on my knowledge. It now supports #cryptographically signing programs [3] so you can #authenticate the source. I gather things distributed by the Microsoft store are all signed this way, but also #software distributed independently by larger companies.
So my questions are:
a) are programs from different companies signed with those companies' keys? Or is everything signed with a #Microsoft key so you can't differentiate between sources?
b) can users blocklist particular #signing #keys? Or are these solely for Microsoft's benefit and only they can decide what keys are acceptable?Because if I was a #Windows user now, I would definitely want to #blocklist LG's signing key.
[1] Am I the only one who used to sell their stuff when they used their full name?
[2] Only with #Windows, natch.
[3] I'll start calling programs "apps" when I'm dead, thanks.
#LuckyGoldstar #adware #spyware #untrustworthy #UntrustedSoftware
-
Spam-Anrufer von "digitaler Geschäftsleitung Deutschland" für #instagram , #facebook , #meta :
+4924198090247Die Nummer kann in Eure BlockList!
-
Block-Tipp des Tages:
Der gesamte Bereich @detroitriotcity.com (zum Vergleich@[email protected])
:antifa:
#FediBlock #Blocklist -
Это набор DNS-блоклистов от мейнтейнера (hagezi) с чисткой, дедупликацией и собственными дополнениями поверх десятков источников. Обновляется автоматически.
Пять уровней агрессивности: Light (166k), Normal (341k), Pro (479k), Pro++ (564k), Ultimate (673k).
Базовая безопасность (https://cdn.jsdelivr.net/gh/hagezi/dns-blocklists@latest/hosts/pro.txt).
Комплексная безопасность = Базовая + полный TIF (https://cdn.jsdelivr.net/gh/hagezi/dns-blocklists@latest/hosts/tif.txt). Потребляет много RAM.Каждый уровень компилируется и валидируется отдельно. В репо есть слои разрешений типа allow_light-ultimate.txt - домены, вычищаемые из всех уровней включая Fake и TIF, allow_light-normal.txt - разблокировка только для мягких уровней, чтобы Light/Normal не ломали ничего, и т. д.
Списки проверяются на 10000 сайтов из Cisco Umbrella Top 1M:
- загрузка страниц,
- корректность отображения,
- работа навигации, изображений, видео. -
Weekly block list report: 3,542 entries; 3,517 valid / 25 invalid; 3 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
The latest update to my Comment #Blocklist for #WordPress features over 65,000 terms, phrases, and other bits of text string persnicketiness to keep your site as spam free as possible.
-
My burner email blocklist blocked me
https://benjamin.piouffle.com/blog/burner-email-blocklists/
Comments: https://news.ycombinator.com/item?id=48846941
#HackerNews #burneremail #blocklist #cybersecurity #privacy #onlineidentity
-
Weekly block list report: 3,536 entries; 3,518 valid / 18 invalid; 1 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Auch im Fediverse, speziell bei Mastodon, verbreiten sich ja so die einen oder anderen Spamschleudern. Gibt es eine Sammlung von Instanzen die bekannt dafür sind und im Vorwege schonmal blockiert werden sollten, bevor man das erste Mal in den Genuss ihrer Verbreitung von Müll kommt?
#blocklist #spam #mastodon #instanzen #vorschlag #hilfe #mastoadmin #moderation
-
Weekly block list report: 3,535 entries; 3,512 valid / 23 invalid; 2 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,527 entries; 3,505 valid / 22 invalid; 3 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
List of #spam #phoneNumber I've blocked yesterday
+1 (937) 293-0279
+1 (937) 582-1476
+1 (937) 551-0747 -
List of #spam #phoneNumber I've blocked today
+1 (937) 980-7147
+1 (937) 743-4308
+1 (937) 809-8056
+1 (937) 500-5356 -
List of #spam #phoneNumber I've blocked today
+1 (937) 351-6877
+1 (937) 375-0177
+1 (937) 390-1804
+1 (937) 401-6798
+1 (937) 439-1485 -
Blockempfehlung für den kompletten Server: @clew.lol
Gerne teilen, um den kompletten Mist abzukoppeln.
#Blocklist -
Weekly block list report: 3,535 entries; 3,504 valid / 31 invalid; 13 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,540 entries; 3,505 valid / 35 invalid; 5 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php
-
Weekly block list report: 3,541 entries; 3,506 valid / 35 invalid; 4 deleted #ads #adblocking #blocklist #trackers #pglblocklistreport
List URL: https://pgl.yoyo.org/as/serverlist.php