Now more than ever I wish #ActivityPub captured emotional feedback and platforms had emotional filters. This post made me feel… // Only show emotions 5 and higher. We could echo chamber awakening itself. #Lightworker
In addition there's an easy way to check, too. Just look at the handle of this mention right here: @canary
Is it @ correct.webfinger-canary.fietkau.software then everything works on your instance. But if it is @ wrong.webfinger-canary.fietkau.software then you're affected by this.
reminder to anyone that owns any #ActivityPub or #fediverse capable anything to disable the cloudflare proxy and/or anti-spam service. both of those seem to be causing problems with cross-instance communications, as @domo has found
12.09.2025 22:23 item (@item@hub.netzgemeinde.eu) @Rob Ricci I guess if a Fediverse actor uses ActivityPub, regardless of whether or not it's that actor's base protocol, that actor should count.
Still, there are various issues and open questions as @Feral Thoughts has already pointed out.
Of course, one question is, where does the Fediverse end? Especially if the definition of Fediverse is "Mastodon and whatever connects to it"?
Hubzilla is not based on ActivityPub. Its creator (who now maintains (streams) and Forte) says it's based on Nomad whereas its maintainers insist that Hubzilla's base protocol is still named Zot. Anyway, it does support ActivityPub. However, like almost all non-nomadic protocols and connectors, ActivityPub support is an add-on that's optional and off by default on new channels. At hub level, ActivityPub is still optional, but on by default when you set up a new hub.
This can mean three things:
Either Hubzilla is not part of the Fediverse because its base protocol is not ActivityPub. Even if it does (optionally) speak ActivityPub.
Or Hubzilla is part of the Fediverse because it does support ActivityPub.
Or Hubzilla is not part of the Fediverse because ActivityPub is not activated by default.
Or Hubzilla is not part of the Fediverse because ActivityPub is not part of the core.
Or only those hubs that have ActivityPub on are part of the Fediverse. However, I guess almost all hubs have ActivityPub on, except maybe for a few private, single-user hubs.
Or Hubzilla is really sitting on the edge, and only those channels that have ActivityPub on are part of the Fediverse. I could literally join and leave the Fediverse by activating or deactivating one add-on.
But if Hubzilla is not part of the Fediverse, am I even allowed to communicate with you all?
(streams) is a bit different. It's based on Nomad and not on ActivityPub. But ActivityPub is part of the core and no longer an add-on, and it's on by default both at server level and at channel level. ActivityPub can still be deactivated both at channel level and at server level.
Forte is identical to (streams), except that it's based on ActivityPub, support for Nomad has been removed, it has a name, it has a brand, it's a project, it's MIT-licensed, and it has nodeinfo (which is intentionally absent from (streams)).
But these two have another "nefarious" feature plus one more that has yet to be rolled out to the release branch, both of which may put them on the edge of the Fediverse.
One, at server level, is the "Uafilter" which is short for "User Agent Filter". It can filter out entire Fediverse server applications by user agent. Its main purpose is to keep Threads out without having to enter new URLs or IP addresses into a filter all the time. However, it's not only capable of locking out the entirety of Mastodon in one fell swoop with no collateral damage, but that's also explicitly a secondary purpose.
The other one, also at server level and currently only available in dev, is "FedUp" which is short for "Federate Upstream". When activated, it only allows federation with servers that provide managed threaded conversations. In other words, it locks out all microblogging servers.
If the Fediverse is defined as "Mastodon and whatever connects to it", these two are features that'd lock at least certain (streams) and Forte servers out of the Fediverse because they are disconnected from all of Mastodon in one way or another.
I've experimented with third-party websites to promote my book, but I figure, 99% of my engagement and feedback has been on the #fediverse.
So I've made a website for "Where the Roots are Long: The Lord of the Rings and the Modern Environmentalist Movement": https://derek.caelin.cloud/roots/
12.09.2025 13:55 daltux (@daltux@snac.daltux.net) Não é preciso haver uma "página de perfil" para que o ator tenha suas atividades acompanhadas por outro. Ao menos em implementações mais genéricas do protocolo #ActivityPub, como no #SNAC: com cada publicação, este apresenta um botão que possibilita acompanhar ou parar de acompanhar as atividades do ator.
Não entendi qual seria o dano de manter a disponibilidade do conteúdo por esse protocolo, ainda que não funcione exatamente como tenha imaginado antes.
É realmente necessário ter ampla audiência para mantê-lo ligado? RSS tem público suficiente para justificar isso? Nessa lógica, não teria certeza nem se o esforço de manter conteúdo na Web aberta seria suficiente, atualmente. A busca pela máxima audiência acaba aumentando o potencial de nos rendermos à #BigTech.
A concentração no servidor mastodon.social também é, infelizmente, uma maneira não saudável de reforçar seu domínio da Federação em torno do ActivityPub, gerando uma "instância" grande demais para ser eventualmente desfederada, bem como de seu software específico perante o protocolo. Sugerimos que migrem para algum servidor entre tantos geridos por pessoas brasileiras. Sintam-se convidades para #Ayom, tanto para microblogue Mastodon quanto para o Lemmy.
Enfim, se a decisão de retirar o blogue for definitiva, lamentamos desde já que não teremos mais uma fonte direta de excelente conteúdo em meio às demais atividades que acompanhamos por aqui.