home.social

#fedimeta — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #fedimeta, aggregated by home.social.

  1. @sb  the chippy-choppy There won't be many left. Depending on how staunchly and extremely anti-AI you and (aspiring) server admins are, there won't be any left. Because it's technically impossible to set up a Fediverse server with absolutely no AI code underneath whatsoever.

    The Linux mainline kernel itself contains AI code now. It's officially allowed as long as it's disclosed as such. Thus, you will have to avoid literally all servers running on Linux.

    https://docs.kernel.org/process/coding-assistants.html

    https://www.neowin.net/news/linus-torvalds-declares-massive-ai-fueled-code-surges-as-the-new-normal-for-linux/

    NetBSD has very strict rules regarding AI-generated code. But it doesn't rule AI-generated code out out of principle because it's AI-generated; it only wants to be safe that nothing that's actually GPL-licensed is slipped in. So, if you're an 100%, ultra-hardcode anti-AI extremist, avoid what few servers run on NetBSD.

    https://www.netbsd.org/developers/commit-guidelines.html

    OpenBSD contains AI-generated code, too. And it has no official stance regarding it. So servers running on OpenBSD are taboo, too.

    https://www.osnews.com/story/144935/openbsd-and-slopcode-raindrop-to-a-torrent/

    FreeBSD has no stance on AI whatsoever that I could find. However, apparently, the FreeBSD community loves to integrate Claude Code into their systems for automation purposes:

    https://aumont.fr/posts/claude-code-freebsd/

    https://discoverbsd.com/p/8a7660c31b

    But you'll also have to look at the userland, the Web server, the database driver etc.

    MariaDB allows AI code. You can safely assume that all MySQL databases on Web servers out there are actually powered by MariaDB.

    https://mariadb.org/governance/governance-ai-policy/

    Oracle MySQL can integrate AI, so it's safe to assume it contains AI-generated code.

    https://blogs.oracle.com/mysql/announcing-mysql-ai

    PostgreSQL probably allows AI code, too. There are even tools for it.

    https://github.com/timescale/pg-aiguide

    SQLite is very popular amongst AI users while not having any rules on AI-generated code. Assume it to be tainted.

    This leaves you with only one choice: Self-hosting a personal, single-user snac2 server because snac2 doesn't need any database whatsoever. In fact, snac2 is staunchly against AI. And it runs on NetBSD.

    https://codeberg.org/grunfink/snac2

    But then there's the Web server. Apache may allow AI-generated code if it has been reviewed and made sure that it does not contain anything that's incompatible with the Apache-2.0 license.

    https://www.apache.org/legal/generative-tooling.html

    nginx welcomes AI and advertises itself as ready for AI, and it takes no anti-AI-code stance. It's most likely already tainted.

    https://www.f5.com/de_de/products/nginx.

    This basically leaves you with no Web server guaranteed to be 100% free from AI-generated code to run snac2 on. But that doesn't matter because it's impossible to build a Web server devoid of any AI code to install snac2 on.

    By the way: Mastodon itself explicitly allows AI code if it's disclosed as such, and if its contributor understands it.

    https://github.com/mastodon/.github/blob/main/AI_POLICY.md

    In other words, next to all Mastodon servers are running
    • AI-generated Mastodon code
    • on an AI-generated Web server
    • with an AI-generated database driver
    • on an AI-generated operating system kernel

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Linux #FreeBSD #OpenBSD #NetBSD #Apache #nginx #MySQL #MariaDB #PostgreSQL #SQLite #Mastodon #snac2 #AI #LLM #LLMs #GenAI #NoAI #AntiAI #AntiLLM
  2. @sb  the chippy-choppy There won't be many left. Depending on how staunchly and extremely anti-AI you and (aspiring) server admins are, there won't be any left. Because it's technically impossible to set up a Fediverse server with absolutely no AI code underneath whatsoever.

    The Linux mainline kernel itself contains AI code now. It's officially allowed as long as it's disclosed as such. Thus, you will have to avoid literally all servers running on Linux.

    https://docs.kernel.org/process/coding-assistants.html

    https://www.neowin.net/news/linus-torvalds-declares-massive-ai-fueled-code-surges-as-the-new-normal-for-linux/

    NetBSD has very strict rules regarding AI-generated code. But it doesn't rule AI-generated code out out of principle because it's AI-generated; it only wants to be safe that nothing that's actually GPL-licensed is slipped in. So, if you're an 100%, ultra-hardcode anti-AI extremist, avoid what few servers run on NetBSD.

    https://www.netbsd.org/developers/commit-guidelines.html

    OpenBSD contains AI-generated code, too. And it has no official stance regarding it. So servers running on OpenBSD are taboo, too.

    https://www.osnews.com/story/144935/openbsd-and-slopcode-raindrop-to-a-torrent/

    FreeBSD has no stance on AI whatsoever that I could find. However, apparently, the FreeBSD community loves to integrate Claude Code into their systems for automation purposes:

    https://aumont.fr/posts/claude-code-freebsd/

    https://discoverbsd.com/p/8a7660c31b

    But you'll also have to look at the userland, the Web server, the database driver etc.

    MariaDB allows AI code. You can safely assume that all MySQL databases on Web servers out there are actually powered by MariaDB.

    https://mariadb.org/governance/governance-ai-policy/

    Oracle MySQL can integrate AI, so it's safe to assume it contains AI-generated code.

    https://blogs.oracle.com/mysql/announcing-mysql-ai

    PostgreSQL probably allows AI code, too. There are even tools for it.

    https://github.com/timescale/pg-aiguide

    SQLite is very popular amongst AI users while not having any rules on AI-generated code. Assume it to be tainted.

    This leaves you with only one choice: Self-hosting a personal, single-user snac2 server because snac2 doesn't need any database whatsoever. In fact, snac2 is staunchly against AI. And it runs on NetBSD.

    https://codeberg.org/grunfink/snac2

    But then there's the Web server. Apache may allow AI-generated code if it has been reviewed and made sure that it does not contain anything that's incompatible with the Apache-2.0 license.

    https://www.apache.org/legal/generative-tooling.html

    nginx welcomes AI and advertises itself as ready for AI, and it takes no anti-AI-code stance. It's most likely already tainted.

    https://www.f5.com/de_de/products/nginx.

    This basically leaves you with no Web server guaranteed to be 100% free from AI-generated code to run snac2 on. But that doesn't matter because it's impossible to build a Web server devoid of any AI code to install snac2 on.

    By the way: Mastodon itself explicitly allows AI code if it's disclosed as such, and if its contributor understands it.

    https://github.com/mastodon/.github/blob/main/AI_POLICY.md

    In other words, next to all Mastodon servers are running
    • AI-generated Mastodon code
    • on an AI-generated Web server
    • with an AI-generated database driver
    • on an AI-generated operating system kernel

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Linux #FreeBSD #OpenBSD #NetBSD #Apache #nginx #MySQL #MariaDB #PostgreSQL #SQLite #Mastodon #snac2 #AI #LLM #LLMs #GenAI #NoAI #AntiAI #AntiLLM
  3. @sb  the chippy-choppy There won't be many left. Depending on how staunchly and extremely anti-AI you and (aspiring) server admins are, there won't be any left. Because it's technically impossible to set up a Fediverse server with absolutely no AI code underneath whatsoever.

    The Linux mainline kernel itself contains AI code now. It's officially allowed as long as it's disclosed as such. Thus, you will have to avoid literally all servers running on Linux.

    https://docs.kernel.org/process/coding-assistants.html

    https://www.neowin.net/news/linus-torvalds-declares-massive-ai-fueled-code-surges-as-the-new-normal-for-linux/

    NetBSD has very strict rules regarding AI-generated code. But it doesn't rule AI-generated code out out of principle because it's AI-generated; it only wants to be safe that nothing that's actually GPL-licensed is slipped in. So, if you're an 100%, ultra-hardcode anti-AI extremist, avoid what few servers run on NetBSD.

    https://www.netbsd.org/developers/commit-guidelines.html

    OpenBSD contains AI-generated code, too. And it has no official stance regarding it. So servers running on OpenBSD are taboo, too.

    https://www.osnews.com/story/144935/openbsd-and-slopcode-raindrop-to-a-torrent/

    FreeBSD has no stance on AI whatsoever that I could find. However, apparently, the FreeBSD community loves to integrate Claude Code into their systems for automation purposes:

    https://aumont.fr/posts/claude-code-freebsd/

    https://discoverbsd.com/p/8a7660c31b

    But you'll also have to look at the userland, the Web server, the database driver etc.

    MariaDB allows AI code. You can safely assume that all MySQL databases on Web servers out there are actually powered by MariaDB.

    https://mariadb.org/governance/governance-ai-policy/

    Oracle MySQL can integrate AI, so it's safe to assume it contains AI-generated code.

    https://blogs.oracle.com/mysql/announcing-mysql-ai

    PostgreSQL probably allows AI code, too. There are even tools for it.

    https://github.com/timescale/pg-aiguide

    SQLite is very popular amongst AI users while not having any rules on AI-generated code. Assume it to be tainted.

    This leaves you with only one choice: Self-hosting a personal, single-user snac2 server because snac2 doesn't need any database whatsoever. In fact, snac2 is staunchly against AI. And it runs on NetBSD.

    https://codeberg.org/grunfink/snac2

    But then there's the Web server. Apache may allow AI-generated code if it has been reviewed and made sure that it does not contain anything that's incompatible with the Apache-2.0 license.

    https://www.apache.org/legal/generative-tooling.html

    nginx welcomes AI and advertises itself as ready for AI, and it takes no anti-AI-code stance. It's most likely already tainted.

    https://www.f5.com/de_de/products/nginx.

    This basically leaves you with no Web server guaranteed to be 100% free from AI-generated code to run snac2 on. But that doesn't matter because it's impossible to build a Web server devoid of any AI code to install snac2 on.

    By the way: Mastodon itself explicitly allows AI code if it's disclosed as such, and if its contributor understands it.

    https://github.com/mastodon/.github/blob/main/AI_POLICY.md

    In other words, next to all Mastodon servers are running
    • AI-generated Mastodon code
    • on an AI-generated Web server
    • with an AI-generated database driver
    • on an AI-generated operating system kernel

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Linux #FreeBSD #OpenBSD #NetBSD #Apache #nginx #MySQL #MariaDB #PostgreSQL #SQLite #Mastodon #snac2 #AI #LLM #LLMs #GenAI #NoAI #AntiAI #AntiLLM
  4. @sb  the chippy-choppy There won't be many left. Depending on how staunchly and extremely anti-AI you and (aspiring) server admins are, there won't be any left. Because it's technically impossible to set up a Fediverse server with absolutely no AI code underneath whatsoever.

    The Linux mainline kernel itself contains AI code now. It's officially allowed as long as it's disclosed as such. Thus, you will have to avoid literally all servers running on Linux.

    https://docs.kernel.org/process/coding-assistants.html

    https://www.neowin.net/news/linus-torvalds-declares-massive-ai-fueled-code-surges-as-the-new-normal-for-linux/

    NetBSD has very strict rules regarding AI-generated code. But it doesn't rule AI-generated code out out of principle because it's AI-generated; it only wants to be safe that nothing that's actually GPL-licensed is slipped in. So, if you're an 100%, ultra-hardcode anti-AI extremist, avoid what few servers run on NetBSD.

    https://www.netbsd.org/developers/commit-guidelines.html

    OpenBSD contains AI-generated code, too. And it has no official stance regarding it. So servers running on OpenBSD are taboo, too.

    https://www.osnews.com/story/144935/openbsd-and-slopcode-raindrop-to-a-torrent/

    FreeBSD has no stance on AI whatsoever that I could find. However, apparently, the FreeBSD community loves to integrate Claude Code into their systems for automation purposes:

    https://aumont.fr/posts/claude-code-freebsd/

    https://discoverbsd.com/p/8a7660c31b

    But you'll also have to look at the userland, the Web server, the database driver etc.

    MariaDB allows AI code. You can safely assume that all MySQL databases on Web servers out there are actually powered by MariaDB.

    https://mariadb.org/governance/governance-ai-policy/

    Oracle MySQL can integrate AI, so it's safe to assume it contains AI-generated code.

    https://blogs.oracle.com/mysql/announcing-mysql-ai

    PostgreSQL probably allows AI code, too. There are even tools for it.

    https://github.com/timescale/pg-aiguide

    SQLite is very popular amongst AI users while not having any rules on AI-generated code. Assume it to be tainted.

    This leaves you with only one choice: Self-hosting a personal, single-user snac2 server because snac2 doesn't need any database whatsoever. In fact, snac2 is staunchly against AI. And it runs on NetBSD.

    https://codeberg.org/grunfink/snac2

    But then there's the Web server. Apache may allow AI-generated code if it has been reviewed and made sure that it does not contain anything that's incompatible with the Apache-2.0 license.

    https://www.apache.org/legal/generative-tooling.html

    nginx welcomes AI and advertises itself as ready for AI, and it takes no anti-AI-code stance. It's most likely already tainted.

    https://www.f5.com/de_de/products/nginx.

    This basically leaves you with no Web server guaranteed to be 100% free from AI-generated code to run snac2 on. But that doesn't matter because it's impossible to build a Web server devoid of any AI code to install snac2 on.

    By the way: Mastodon itself explicitly allows AI code if it's disclosed as such, and if its contributor understands it.

    https://github.com/mastodon/.github/blob/main/AI_POLICY.md

    In other words, next to all Mastodon servers are running
    • AI-generated Mastodon code
    • on an AI-generated Web server
    • with an AI-generated database driver
    • on an AI-generated operating system kernel

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Linux #FreeBSD #OpenBSD #NetBSD #Apache #nginx #MySQL #MariaDB #PostgreSQL #SQLite #Mastodon #snac2 #AI #LLM #LLMs #GenAI #NoAI #AntiAI #AntiLLM
  5. @sb  the chippy-choppy There won't be many left. Depending on how staunchly and extremely anti-AI you and (aspiring) server admins are, there won't be any left. Because it's technically impossible to set up a Fediverse server with absolutely no AI code underneath whatsoever.

    The Linux mainline kernel itself contains AI code now. It's officially allowed as long as it's disclosed as such. Thus, you will have to avoid literally all servers running on Linux.

    https://docs.kernel.org/process/coding-assistants.html

    https://www.neowin.net/news/linus-torvalds-declares-massive-ai-fueled-code-surges-as-the-new-normal-for-linux/

    NetBSD has very strict rules regarding AI-generated code. But it doesn't rule AI-generated code out out of principle because it's AI-generated; it only wants to be safe that nothing that's actually GPL-licensed is slipped in. So, if you're an 100%, ultra-hardcode anti-AI extremist, avoid what few servers run on NetBSD.

    https://www.netbsd.org/developers/commit-guidelines.html

    OpenBSD contains AI-generated code, too. And it has no official stance regarding it. So servers running on OpenBSD are taboo, too.

    https://www.osnews.com/story/144935/openbsd-and-slopcode-raindrop-to-a-torrent/

    FreeBSD has no stance on AI whatsoever that I could find. However, apparently, the FreeBSD community loves to integrate Claude Code into their systems for automation purposes:

    https://aumont.fr/posts/claude-code-freebsd/

    https://discoverbsd.com/p/8a7660c31b

    But you'll also have to look at the userland, the Web server, the database driver etc.

    MariaDB allows AI code. You can safely assume that all MySQL databases on Web servers out there are actually powered by MariaDB.

    https://mariadb.org/governance/governance-ai-policy/

    Oracle MySQL can integrate AI, so it's safe to assume it contains AI-generated code.

    https://blogs.oracle.com/mysql/announcing-mysql-ai

    PostgreSQL probably allows AI code, too. There are even tools for it.

    https://github.com/timescale/pg-aiguide

    SQLite is very popular amongst AI users while not having any rules on AI-generated code. Assume it to be tainted.

    This leaves you with only one choice: Self-hosting a personal, single-user snac2 server because snac2 doesn't need any database whatsoever. In fact, snac2 is staunchly against AI. And it runs on NetBSD.

    https://codeberg.org/grunfink/snac2

    But then there's the Web server. Apache may allow AI-generated code if it has been reviewed and made sure that it does not contain anything that's incompatible with the Apache-2.0 license.

    https://www.apache.org/legal/generative-tooling.html

    nginx welcomes AI and advertises itself as ready for AI, and it takes no anti-AI-code stance. It's most likely already tainted.

    https://www.f5.com/de_de/products/nginx.

    This basically leaves you with no Web server guaranteed to be 100% free from AI-generated code to run snac2 on. But that doesn't matter because it's impossible to build a Web server devoid of any AI code to install snac2 on.

    By the way: Mastodon itself explicitly allows AI code if it's disclosed as such, and if its contributor understands it.

    https://github.com/mastodon/.github/blob/main/AI_POLICY.md

    In other words, next to all Mastodon servers are running
    • AI-generated Mastodon code
    • on an AI-generated Web server
    • with an AI-generated database driver
    • on an AI-generated operating system kernel

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Linux #FreeBSD #OpenBSD #NetBSD #Apache #nginx #MySQL #MariaDB #PostgreSQL #SQLite #Mastodon #snac2 #AI #LLM #LLMs #GenAI #NoAI #AntiAI #AntiLLM
  6. @happyborg
    People can follow hashtags

    People on Mastodon can follow hashtags. But just because people on Mastodon can, doesn't mean people everywhere else in the Fediverse can, too.

    AFAIK, some of the minimalist microblogging server applications designed for self-hosting don't offer this feature. I'm not sure if Pleroma and Akkoma have it.

    Hubzilla, which is what I'm commenting from, definitely doesn't have this feature. And Hubzilla is anything but minimalist. It's the most powerful and versatile of all Fediverse server applications.

    Also, if you can follow hashtags, you can only follow hashtags on your home server. But if you're on a small server, hardly any messages with these hashtags wash up there in the first place. You'll miss a lot. If you're on a private, single-user server, following hashtags is completely useless because the only messages with these hashtags that reach the server are those that you receive from your own contacts anyway.

    (streams) and Forte, both being streamlined and more advanced Hubzilla descendants, can follow hashtags. But there simply aren't any big (streams) or Forte servers, especially not with lots of traffic from Mastodon. Most of the few (streams) and Forte users run their own single-user servers.

    This is also why it doesn't matter much whether snac or GoToSocial users can follow hashtags: These two are almost exclusively used as private, single-user servers because that's what they're designed for first and foremost.

    To make it short: Most Fediverse users outside the big Mastodon servers can only follow hashtags by relying on "bots" that forward posts with these hashtags which they find on e.g. mastodon.social.

    In fact, this is good for Mastodon users as well. It helps circumvent two of Mastodon's disadvantages.

    One is that it has no support for groups whatsoever (the Fediverse does have groups in case you don't know). If Mastodon users need to talk about a certain topic, they can't do so in a group about that topic. All they can do is shout into the ether with certain hashtags and hope that the right person catches their toot.

    The other one is that this is highly unlikely on Mastodon itself. On Mastodon, most content remains unseen.

    Mastodon doesn't offer a list of unread messages in the timeline, not even a counter. All that Mastodon users can do is scroll down their timeline until they either hit content that they've already seen, or until they've got no more time, or until they want no more. Anything below will remain unseen. It's sad that this counts as the default or even without alternatives in the Fediverse. And most Mastodon users follow so many accounts and channels (plus hashtags occasionally) that they can impossibly read all the messages they receive.

    Let's suppose a Mastodon user wants to talk about Hubzilla for some reason. I've seen this happen often enough. The only chance they have, not knowing that the @hubzilla exists, much less that they can join it from Mastodon, is by tooting into the void with the hashtag #Hubzilla and hoping that either one of their followers or someone somewhere out there on their followers' servers follows the hashtag #Hubzilla.

    But none of their followers comes online soon enough to scroll down to their toot. They all have tons of other content in their timelines above that toot, so they never scroll all the way down to it. If not, they simply don't know what Hubzilla is. And even if any Mastodon users follow the hashtag #Hubzilla (which I doubt), this still doesn't mean that one of them scrolls all the way down to that toot.

    And then there's me. As I've already said, I'm on Hubzilla. I can't follow hashtags directly. Instead, I "follow" the hashtag #Hubzilla by having this hashtag on the FediBuzz relay (https://relay.fedi.buzz/) as a contact. Or, in Mastodon terms, by following it. FediBuzz is not a bot server. It's a relay that server admins can connect their servers to to have more public content on their servers (if their server software supports relays, that is). Something completely normal on Mastodon, especially on small servers.

    So when someone on Mastodon toots something with #Hubzilla, I receive it as a new post. But I don't have to scroll down a timeline of unknown length to find it. I have a counter for unread messages and other unnoticed actions. It unfolds into a list of unread messages and other unnoticed actions. From there, I can get directly to that post. I will notice it. And I'll usually be able to help.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Relay #Relays
  7. @happyborg
    People can follow hashtags

    People on Mastodon can follow hashtags. But just because people on Mastodon can, doesn't mean people everywhere else in the Fediverse can, too.

    AFAIK, some of the minimalist microblogging server applications designed for self-hosting don't offer this feature. I'm not sure if Pleroma and Akkoma have it.

    Hubzilla, which is what I'm commenting from, definitely doesn't have this feature. And Hubzilla is anything but minimalist. It's the most powerful and versatile of all Fediverse server applications.

    Also, if you can follow hashtags, you can only follow hashtags on your home server. But if you're on a small server, hardly any messages with these hashtags wash up there in the first place. You'll miss a lot. If you're on a private, single-user server, following hashtags is completely useless because the only messages with these hashtags that reach the server are those that you receive from your own contacts anyway.

    (streams) and Forte, both being streamlined and more advanced Hubzilla descendants, can follow hashtags. But there simply aren't any big (streams) or Forte servers, especially not with lots of traffic from Mastodon. Most of the few (streams) and Forte users run their own single-user servers.

    This is also why it doesn't matter much whether snac or GoToSocial users can follow hashtags: These two are almost exclusively used as private, single-user servers because that's what they're designed for first and foremost.

    To make it short: Most Fediverse users outside the big Mastodon servers can only follow hashtags by relying on "bots" that forward posts with these hashtags which they find on e.g. mastodon.social.

    In fact, this is good for Mastodon users as well. It helps circumvent two of Mastodon's disadvantages.

    One is that it has no support for groups whatsoever (the Fediverse does have groups in case you don't know). If Mastodon users need to talk about a certain topic, they can't do so in a group about that topic. All they can do is shout into the ether with certain hashtags and hope that the right person catches their toot.

    The other one is that this is highly unlikely on Mastodon itself. On Mastodon, most content remains unseen.

    Mastodon doesn't offer a list of unread messages in the timeline, not even a counter. All that Mastodon users can do is scroll down their timeline until they either hit content that they've already seen, or until they've got no more time, or until they want no more. Anything below will remain unseen. It's sad that this counts as the default or even without alternatives in the Fediverse. And most Mastodon users follow so many accounts and channels (plus hashtags occasionally) that they can impossibly read all the messages they receive.

    Let's suppose a Mastodon user wants to talk about Hubzilla for some reason. I've seen this happen often enough. The only chance they have, not knowing that the @hubzilla exists, much less that they can join it from Mastodon, is by tooting into the void with the hashtag #Hubzilla and hoping that either one of their followers or someone somewhere out there on their followers' servers follows the hashtag #Hubzilla.

    But none of their followers comes online soon enough to scroll down to their toot. They all have tons of other content in their timelines above that toot, so they never scroll all the way down to it. If not, they simply don't know what Hubzilla is. And even if any Mastodon users follow the hashtag #Hubzilla (which I doubt), this still doesn't mean that one of them scrolls all the way down to that toot.

    And then there's me. As I've already said, I'm on Hubzilla. I can't follow hashtags directly. Instead, I "follow" the hashtag #Hubzilla by having this hashtag on the FediBuzz relay (https://relay.fedi.buzz/) as a contact. Or, in Mastodon terms, by following it. FediBuzz is not a bot server. It's a relay that server admins can connect their servers to to have more public content on their servers (if their server software supports relays, that is). Something completely normal on Mastodon, especially on small servers.

    So when someone on Mastodon toots something with #Hubzilla, I receive it as a new post. But I don't have to scroll down a timeline of unknown length to find it. I have a counter for unread messages and other unnoticed actions. It unfolds into a list of unread messages and other unnoticed actions. From there, I can get directly to that post. I will notice it. And I'll usually be able to help.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Relay #Relays
  8. @happyborg
    People can follow hashtags

    People on Mastodon can follow hashtags. But just because people on Mastodon can, doesn't mean people everywhere else in the Fediverse can, too.

    AFAIK, some of the minimalist microblogging server applications designed for self-hosting don't offer this feature. I'm not sure if Pleroma and Akkoma have it.

    Hubzilla, which is what I'm commenting from, definitely doesn't have this feature. And Hubzilla is anything but minimalist. It's the most powerful and versatile of all Fediverse server applications.

    Also, if you can follow hashtags, you can only follow hashtags on your home server. But if you're on a small server, hardly any messages with these hashtags wash up there in the first place. You'll miss a lot. If you're on a private, single-user server, following hashtags is completely useless because the only messages with these hashtags that reach the server are those that you receive from your own contacts anyway.

    (streams) and Forte, both being streamlined and more advanced Hubzilla descendants, can follow hashtags. But there simply aren't any big (streams) or Forte servers, especially not with lots of traffic from Mastodon. Most of the few (streams) and Forte users run their own single-user servers.

    This is also why it doesn't matter much whether snac or GoToSocial users can follow hashtags: These two are almost exclusively used as private, single-user servers because that's what they're designed for first and foremost.

    To make it short: Most Fediverse users outside the big Mastodon servers can only follow hashtags by relying on "bots" that forward posts with these hashtags which they find on e.g. mastodon.social.

    In fact, this is good for Mastodon users as well. It helps circumvent two of Mastodon's disadvantages.

    One is that it has no support for groups whatsoever (the Fediverse does have groups in case you don't know). If Mastodon users need to talk about a certain topic, they can't do so in a group about that topic. All they can do is shout into the ether with certain hashtags and hope that the right person catches their toot.

    The other one is that this is highly unlikely on Mastodon itself. On Mastodon, most content remains unseen.

    Mastodon doesn't offer a list of unread messages in the timeline, not even a counter. All that Mastodon users can do is scroll down their timeline until they either hit content that they've already seen, or until they've got no more time, or until they want no more. Anything below will remain unseen. It's sad that this counts as the default or even without alternatives in the Fediverse. And most Mastodon users follow so many accounts and channels (plus hashtags occasionally) that they can impossibly read all the messages they receive.

    Let's suppose a Mastodon user wants to talk about Hubzilla for some reason. I've seen this happen often enough. The only chance they have, not knowing that the @hubzilla exists, much less that they can join it from Mastodon, is by tooting into the void with the hashtag #Hubzilla and hoping that either one of their followers or someone somewhere out there on their followers' servers follows the hashtag #Hubzilla.

    But none of their followers comes online soon enough to scroll down to their toot. They all have tons of other content in their timelines above that toot, so they never scroll all the way down to it. If not, they simply don't know what Hubzilla is. And even if any Mastodon users follow the hashtag #Hubzilla (which I doubt), this still doesn't mean that one of them scrolls all the way down to that toot.

    And then there's me. As I've already said, I'm on Hubzilla. I can't follow hashtags directly. Instead, I "follow" the hashtag #Hubzilla by having this hashtag on the FediBuzz relay (https://relay.fedi.buzz/) as a contact. Or, in Mastodon terms, by following it. FediBuzz is not a bot server. It's a relay that server admins can connect their servers to to have more public content on their servers (if their server software supports relays, that is). Something completely normal on Mastodon, especially on small servers.

    So when someone on Mastodon toots something with #Hubzilla, I receive it as a new post. But I don't have to scroll down a timeline of unknown length to find it. I have a counter for unread messages and other unnoticed actions. It unfolds into a list of unread messages and other unnoticed actions. From there, I can get directly to that post. I will notice it. And I'll usually be able to help.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Relay #Relays
  9. @happyborg
    People can follow hashtags

    People on Mastodon can follow hashtags. But just because people on Mastodon can, doesn't mean people everywhere else in the Fediverse can, too.

    AFAIK, some of the minimalist microblogging server applications designed for self-hosting don't offer this feature. I'm not sure if Pleroma and Akkoma have it.

    Hubzilla, which is what I'm commenting from, definitely doesn't have this feature. And Hubzilla is anything but minimalist. It's the most powerful and versatile of all Fediverse server applications.

    Also, if you can follow hashtags, you can only follow hashtags on your home server. But if you're on a small server, hardly any messages with these hashtags wash up there in the first place. You'll miss a lot. If you're on a private, single-user server, following hashtags is completely useless because the only messages with these hashtags that reach the server are those that you receive from your own contacts anyway.

    (streams) and Forte, both being streamlined and more advanced Hubzilla descendants, can follow hashtags. But there simply aren't any big (streams) or Forte servers, especially not with lots of traffic from Mastodon. Most of the few (streams) and Forte users run their own single-user servers.

    This is also why it doesn't matter much whether snac or GoToSocial users can follow hashtags: These two are almost exclusively used as private, single-user servers because that's what they're designed for first and foremost.

    To make it short: Most Fediverse users outside the big Mastodon servers can only follow hashtags by relying on "bots" that forward posts with these hashtags which they find on e.g. mastodon.social.

    In fact, this is good for Mastodon users as well. It helps circumvent two of Mastodon's disadvantages.

    One is that it has no support for groups whatsoever (the Fediverse does have groups in case you don't know). If Mastodon users need to talk about a certain topic, they can't do so in a group about that topic. All they can do is shout into the ether with certain hashtags and hope that the right person catches their toot.

    The other one is that this is highly unlikely on Mastodon itself. On Mastodon, most content remains unseen.

    Mastodon doesn't offer a list of unread messages in the timeline, not even a counter. All that Mastodon users can do is scroll down their timeline until they either hit content that they've already seen, or until they've got no more time, or until they want no more. Anything below will remain unseen. It's sad that this counts as the default or even without alternatives in the Fediverse. And most Mastodon users follow so many accounts and channels (plus hashtags occasionally) that they can impossibly read all the messages they receive.

    Let's suppose a Mastodon user wants to talk about Hubzilla for some reason. I've seen this happen often enough. The only chance they have, not knowing that the @hubzilla exists, much less that they can join it from Mastodon, is by tooting into the void with the hashtag #Hubzilla and hoping that either one of their followers or someone somewhere out there on their followers' servers follows the hashtag #Hubzilla.

    But none of their followers comes online soon enough to scroll down to their toot. They all have tons of other content in their timelines above that toot, so they never scroll all the way down to it. If not, they simply don't know what Hubzilla is. And even if any Mastodon users follow the hashtag #Hubzilla (which I doubt), this still doesn't mean that one of them scrolls all the way down to that toot.

    And then there's me. As I've already said, I'm on Hubzilla. I can't follow hashtags directly. Instead, I "follow" the hashtag #Hubzilla by having this hashtag on the FediBuzz relay (https://relay.fedi.buzz/) as a contact. Or, in Mastodon terms, by following it. FediBuzz is not a bot server. It's a relay that server admins can connect their servers to to have more public content on their servers (if their server software supports relays, that is). Something completely normal on Mastodon, especially on small servers.

    So when someone on Mastodon toots something with #Hubzilla, I receive it as a new post. But I don't have to scroll down a timeline of unknown length to find it. I have a counter for unread messages and other unnoticed actions. It unfolds into a list of unread messages and other unnoticed actions. From there, I can get directly to that post. I will notice it. And I'll usually be able to help.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Relay #Relays
  10. @happyborg
    People can follow hashtags

    People on Mastodon can follow hashtags. But just because people on Mastodon can, doesn't mean people everywhere else in the Fediverse can, too.

    AFAIK, some of the minimalist microblogging server applications designed for self-hosting don't offer this feature. I'm not sure if Pleroma and Akkoma have it.

    Hubzilla, which is what I'm commenting from, definitely doesn't have this feature. And Hubzilla is anything but minimalist. It's the most powerful and versatile of all Fediverse server applications.

    Also, if you can follow hashtags, you can only follow hashtags on your home server. But if you're on a small server, hardly any messages with these hashtags wash up there in the first place. You'll miss a lot. If you're on a private, single-user server, following hashtags is completely useless because the only messages with these hashtags that reach the server are those that you receive from your own contacts anyway.

    (streams) and Forte, both being streamlined and more advanced Hubzilla descendants, can follow hashtags. But there simply aren't any big (streams) or Forte servers, especially not with lots of traffic from Mastodon. Most of the few (streams) and Forte users run their own single-user servers.

    This is also why it doesn't matter much whether snac or GoToSocial users can follow hashtags: These two are almost exclusively used as private, single-user servers because that's what they're designed for first and foremost.

    To make it short: Most Fediverse users outside the big Mastodon servers can only follow hashtags by relying on "bots" that forward posts with these hashtags which they find on e.g. mastodon.social.

    In fact, this is good for Mastodon users as well. It helps circumvent two of Mastodon's disadvantages.

    One is that it has no support for groups whatsoever (the Fediverse does have groups in case you don't know). If Mastodon users need to talk about a certain topic, they can't do so in a group about that topic. All they can do is shout into the ether with certain hashtags and hope that the right person catches their toot.

    The other one is that this is highly unlikely on Mastodon itself. On Mastodon, most content remains unseen.

    Mastodon doesn't offer a list of unread messages in the timeline, not even a counter. All that Mastodon users can do is scroll down their timeline until they either hit content that they've already seen, or until they've got no more time, or until they want no more. Anything below will remain unseen. It's sad that this counts as the default or even without alternatives in the Fediverse. And most Mastodon users follow so many accounts and channels (plus hashtags occasionally) that they can impossibly read all the messages they receive.

    Let's suppose a Mastodon user wants to talk about Hubzilla for some reason. I've seen this happen often enough. The only chance they have, not knowing that the @hubzilla exists, much less that they can join it from Mastodon, is by tooting into the void with the hashtag #Hubzilla and hoping that either one of their followers or someone somewhere out there on their followers' servers follows the hashtag #Hubzilla.

    But none of their followers comes online soon enough to scroll down to their toot. They all have tons of other content in their timelines above that toot, so they never scroll all the way down to it. If not, they simply don't know what Hubzilla is. And even if any Mastodon users follow the hashtag #Hubzilla (which I doubt), this still doesn't mean that one of them scrolls all the way down to that toot.

    And then there's me. As I've already said, I'm on Hubzilla. I can't follow hashtags directly. Instead, I "follow" the hashtag #Hubzilla by having this hashtag on the FediBuzz relay (https://relay.fedi.buzz/) as a contact. Or, in Mastodon terms, by following it. FediBuzz is not a bot server. It's a relay that server admins can connect their servers to to have more public content on their servers (if their server software supports relays, that is). Something completely normal on Mastodon, especially on small servers.

    So when someone on Mastodon toots something with #Hubzilla, I receive it as a new post. But I don't have to scroll down a timeline of unknown length to find it. I have a counter for unread messages and other unnoticed actions. It unfolds into a list of unread messages and other unnoticed actions. From there, I can get directly to that post. I will notice it. And I'll usually be able to help.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta #Relay #Relays
  11. @Alexander Goeres 𒀯 @everton137 Whether they've adopted Mastodon's culture. And whether they follow all of Mastodon's largely unwritten rules to a tee.

    Regardless of whether or not they're actually on Mastodon after all.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #MastodonCulture #MastodonHOA #MastodonCentricity #MastodonNormativity
  12. @Alexander Goeres 𒀯 @everton137 Whether they've adopted Mastodon's culture. And whether they follow all of Mastodon's largely unwritten rules to a tee.

    Regardless of whether or not they're actually on Mastodon after all.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #MastodonCulture #MastodonHOA #MastodonCentricity #MastodonNormativity
  13. @Alexander Goeres 𒀯 @everton137 Whether they've adopted Mastodon's culture. And whether they follow all of Mastodon's largely unwritten rules to a tee.

    Regardless of whether or not they're actually on Mastodon after all.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #MastodonCulture #MastodonHOA #MastodonCentricity #MastodonNormativity
  14. @Alexander Goeres 𒀯 @everton137 Whether they've adopted Mastodon's culture. And whether they follow all of Mastodon's largely unwritten rules to a tee.

    Regardless of whether or not they're actually on Mastodon after all.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #MastodonCulture #MastodonHOA #MastodonCentricity #MastodonNormativity
  15. @Alexander Goeres 𒀯 @everton137 Whether they've adopted Mastodon's culture. And whether they follow all of Mastodon's largely unwritten rules to a tee.

    Regardless of whether or not they're actually on Mastodon after all.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #MastodonCulture #MastodonHOA #MastodonCentricity #MastodonNormativity
  16. @silverpill @🫧 Social coding commons @Rimu @elle And this has to say something.

    After all, Mastodon is far from a by-the-book implementation. Mastodon's ActivityPub implementation is influenced by two things. One, the legacy compatibility decisions from a time when Mastodon had two base protocols, OStatus and ActivityPub, and it had to make ActivityPub work like OStatus. Two, Mastodon's willingness to combat the Fediverse and eventually EEE it rather than embracing it.

    Let me put it this way: At least for the longest time, Mastodon has tried hard to be incompatible with large parts of the Fediverse, at least with those parts that don't appear like add-ons to Mastodon (like PeerTube or Pixelfed).

    And it has reached its goal: Almost all of those on Mastodon who do know that the Fediverse is more than Mastodon think that Mastodon still is the reference implementation of ActivityPub, and everything that doesn't work exactly like Mastodon, or that causes friction when interacting with Mastodon, is broken. That's one way to get rid of competition: Make it look bad to your own users.

    Entire features, some of which are backed by FEPs, are bad from a Mastodon point of view. For example, enclosed threaded conversations with one post and otherwise comments, as can be found all over the Fediverse from Friendica and its descendants to the whole Threadiverse, are bad because they're so different from Mastodon's threads loosely tied together from toots and more toots. And there's an FEP for them: FEP-171b "Conversation Containers".

    This has gotten so bad especially since the big Twitter exodus from 2022 that developers no longer implement ActivityPub; to quote a diaspora* developer, they "implement Mastodon". They build their stuff hard against Mastodon with little to no regards for actual ActivityPub and with little to no regards for the rest of the Fediverse.

    Even Mike Macgirvin, formerly the staunchest Mastodon critic under the sun, has given in. He has added a per-post switch to (streams) and Forte which lets you choose between starting an enclosed conversation as per FEP-171b that Mastodon doesn't properly understand and starting a Mastodon-style loose thread that Mastodon understands.

    I mean, what kind of "decentralised" Fediverse is it if the W3C is powerless, if the SWICG is effectively powerless, if the other devs are powerless, too, because it's Gargron and his Mastodon developers who are the one and only authority that defines how the Fediverse has to be built? And when Mastodon decides to re-invent the wheel once more, the whole rest of the Fediverse has to throw away its existing wheels and implement Mastodon's not even necessarily better wheels?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #Mastodon #MastodonCentricity #MastodonNormativity
  17. @silverpill @🫧 Social coding commons @Rimu @elle And this has to say something.

    After all, Mastodon is far from a by-the-book implementation. Mastodon's ActivityPub implementation is influenced by two things. One, the legacy compatibility decisions from a time when Mastodon had two base protocols, OStatus and ActivityPub, and it had to make ActivityPub work like OStatus. Two, Mastodon's willingness to combat the Fediverse and eventually EEE it rather than embracing it.

    Let me put it this way: At least for the longest time, Mastodon has tried hard to be incompatible with large parts of the Fediverse, at least with those parts that don't appear like add-ons to Mastodon (like PeerTube or Pixelfed).

    And it has reached its goal: Almost all of those on Mastodon who do know that the Fediverse is more than Mastodon think that Mastodon still is the reference implementation of ActivityPub, and everything that doesn't work exactly like Mastodon, or that causes friction when interacting with Mastodon, is broken. That's one way to get rid of competition: Make it look bad to your own users.

    Entire features, some of which are backed by FEPs, are bad from a Mastodon point of view. For example, enclosed threaded conversations with one post and otherwise comments, as can be found all over the Fediverse from Friendica and its descendants to the whole Threadiverse, are bad because they're so different from Mastodon's threads loosely tied together from toots and more toots. And there's an FEP for them: FEP-171b "Conversation Containers".

    This has gotten so bad especially since the big Twitter exodus from 2022 that developers no longer implement ActivityPub; to quote a diaspora* developer, they "implement Mastodon". They build their stuff hard against Mastodon with little to no regards for actual ActivityPub and with little to no regards for the rest of the Fediverse.

    Even Mike Macgirvin, formerly the staunchest Mastodon critic under the sun, has given in. He has added a per-post switch to (streams) and Forte which lets you choose between starting an enclosed conversation as per FEP-171b that Mastodon doesn't properly understand and starting a Mastodon-style loose thread that Mastodon understands.

    I mean, what kind of "decentralised" Fediverse is it if the W3C is powerless, if the SWICG is effectively powerless, if the other devs are powerless, too, because it's Gargron and his Mastodon developers who are the one and only authority that defines how the Fediverse has to be built? And when Mastodon decides to re-invent the wheel once more, the whole rest of the Fediverse has to throw away its existing wheels and implement Mastodon's not even necessarily better wheels?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #Mastodon #MastodonCentricity #MastodonNormativity
  18. @silverpill @🫧 Social coding commons @Rimu @elle And this has to say something.

    After all, Mastodon is far from a by-the-book implementation. Mastodon's ActivityPub implementation is influenced by two things. One, the legacy compatibility decisions from a time when Mastodon had two base protocols, OStatus and ActivityPub, and it had to make ActivityPub work like OStatus. Two, Mastodon's willingness to combat the Fediverse and eventually EEE it rather than embracing it.

    Let me put it this way: At least for the longest time, Mastodon has tried hard to be incompatible with large parts of the Fediverse, at least with those parts that don't appear like add-ons to Mastodon (like PeerTube or Pixelfed).

    And it has reached its goal: Almost all of those on Mastodon who do know that the Fediverse is more than Mastodon think that Mastodon still is the reference implementation of ActivityPub, and everything that doesn't work exactly like Mastodon, or that causes friction when interacting with Mastodon, is broken. That's one way to get rid of competition: Make it look bad to your own users.

    Entire features, some of which are backed by FEPs, are bad from a Mastodon point of view. For example, enclosed threaded conversations with one post and otherwise comments, as can be found all over the Fediverse from Friendica and its descendants to the whole Threadiverse, are bad because they're so different from Mastodon's threads loosely tied together from toots and more toots. And there's an FEP for them: FEP-171b "Conversation Containers".

    This has gotten so bad especially since the big Twitter exodus from 2022 that developers no longer implement ActivityPub; to quote a diaspora* developer, they "implement Mastodon". They build their stuff hard against Mastodon with little to no regards for actual ActivityPub and with little to no regards for the rest of the Fediverse.

    Even Mike Macgirvin, formerly the staunchest Mastodon critic under the sun, has given in. He has added a per-post switch to (streams) and Forte which lets you choose between starting an enclosed conversation as per FEP-171b that Mastodon doesn't properly understand and starting a Mastodon-style loose thread that Mastodon understands.

    I mean, what kind of "decentralised" Fediverse is it if the W3C is powerless, if the SWICG is effectively powerless, if the other devs are powerless, too, because it's Gargron and his Mastodon developers who are the one and only authority that defines how the Fediverse has to be built? And when Mastodon decides to re-invent the wheel once more, the whole rest of the Fediverse has to throw away its existing wheels and implement Mastodon's not even necessarily better wheels?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #Mastodon #MastodonCentricity #MastodonNormativity
  19. @silverpill @🫧 Social coding commons @Rimu @elle And this has to say something.

    After all, Mastodon is far from a by-the-book implementation. Mastodon's ActivityPub implementation is influenced by two things. One, the legacy compatibility decisions from a time when Mastodon had two base protocols, OStatus and ActivityPub, and it had to make ActivityPub work like OStatus. Two, Mastodon's willingness to combat the Fediverse and eventually EEE it rather than embracing it.

    Let me put it this way: At least for the longest time, Mastodon has tried hard to be incompatible with large parts of the Fediverse, at least with those parts that don't appear like add-ons to Mastodon (like PeerTube or Pixelfed).

    And it has reached its goal: Almost all of those on Mastodon who do know that the Fediverse is more than Mastodon think that Mastodon still is the reference implementation of ActivityPub, and everything that doesn't work exactly like Mastodon, or that causes friction when interacting with Mastodon, is broken. That's one way to get rid of competition: Make it look bad to your own users.

    Entire features, some of which are backed by FEPs, are bad from a Mastodon point of view. For example, enclosed threaded conversations with one post and otherwise comments, as can be found all over the Fediverse from Friendica and its descendants to the whole Threadiverse, are bad because they're so different from Mastodon's threads loosely tied together from toots and more toots. And there's an FEP for them: FEP-171b "Conversation Containers".

    This has gotten so bad especially since the big Twitter exodus from 2022 that developers no longer implement ActivityPub; to quote a diaspora* developer, they "implement Mastodon". They build their stuff hard against Mastodon with little to no regards for actual ActivityPub and with little to no regards for the rest of the Fediverse.

    Even Mike Macgirvin, formerly the staunchest Mastodon critic under the sun, has given in. He has added a per-post switch to (streams) and Forte which lets you choose between starting an enclosed conversation as per FEP-171b that Mastodon doesn't properly understand and starting a Mastodon-style loose thread that Mastodon understands.

    I mean, what kind of "decentralised" Fediverse is it if the W3C is powerless, if the SWICG is effectively powerless, if the other devs are powerless, too, because it's Gargron and his Mastodon developers who are the one and only authority that defines how the Fediverse has to be built? And when Mastodon decides to re-invent the wheel once more, the whole rest of the Fediverse has to throw away its existing wheels and implement Mastodon's not even necessarily better wheels?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #Mastodon #MastodonCentricity #MastodonNormativity
  20. @silverpill @🫧 Social coding commons @Rimu @elle And this has to say something.

    After all, Mastodon is far from a by-the-book implementation. Mastodon's ActivityPub implementation is influenced by two things. One, the legacy compatibility decisions from a time when Mastodon had two base protocols, OStatus and ActivityPub, and it had to make ActivityPub work like OStatus. Two, Mastodon's willingness to combat the Fediverse and eventually EEE it rather than embracing it.

    Let me put it this way: At least for the longest time, Mastodon has tried hard to be incompatible with large parts of the Fediverse, at least with those parts that don't appear like add-ons to Mastodon (like PeerTube or Pixelfed).

    And it has reached its goal: Almost all of those on Mastodon who do know that the Fediverse is more than Mastodon think that Mastodon still is the reference implementation of ActivityPub, and everything that doesn't work exactly like Mastodon, or that causes friction when interacting with Mastodon, is broken. That's one way to get rid of competition: Make it look bad to your own users.

    Entire features, some of which are backed by FEPs, are bad from a Mastodon point of view. For example, enclosed threaded conversations with one post and otherwise comments, as can be found all over the Fediverse from Friendica and its descendants to the whole Threadiverse, are bad because they're so different from Mastodon's threads loosely tied together from toots and more toots. And there's an FEP for them: FEP-171b "Conversation Containers".

    This has gotten so bad especially since the big Twitter exodus from 2022 that developers no longer implement ActivityPub; to quote a diaspora* developer, they "implement Mastodon". They build their stuff hard against Mastodon with little to no regards for actual ActivityPub and with little to no regards for the rest of the Fediverse.

    Even Mike Macgirvin, formerly the staunchest Mastodon critic under the sun, has given in. He has added a per-post switch to (streams) and Forte which lets you choose between starting an enclosed conversation as per FEP-171b that Mastodon doesn't properly understand and starting a Mastodon-style loose thread that Mastodon understands.

    I mean, what kind of "decentralised" Fediverse is it if the W3C is powerless, if the SWICG is effectively powerless, if the other devs are powerless, too, because it's Gargron and his Mastodon developers who are the one and only authority that defines how the Fediverse has to be built? And when Mastodon decides to re-invent the wheel once more, the whole rest of the Fediverse has to throw away its existing wheels and implement Mastodon's not even necessarily better wheels?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #ActivityPub #Mastodon #MastodonCentricity #MastodonNormativity
  21. @silverpill @🫧 Social coding commons @Rimu @elle I guess I can accurately estimate on which side Mastodon is standing. Even though Mastodon can be considered "real ActivityPub" and "implemented".

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
  22. @silverpill @🫧 Social coding commons @Rimu @elle I guess I can accurately estimate on which side Mastodon is standing. Even though Mastodon can be considered "real ActivityPub" and "implemented".

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
  23. @silverpill @🫧 Social coding commons @Rimu @elle I guess I can accurately estimate on which side Mastodon is standing. Even though Mastodon can be considered "real ActivityPub" and "implemented".

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
  24. @silverpill @🫧 Social coding commons @Rimu @elle I guess I can accurately estimate on which side Mastodon is standing. Even though Mastodon can be considered "real ActivityPub" and "implemented".

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
  25. @silverpill @🫧 Social coding commons @Rimu @elle I guess I can accurately estimate on which side Mastodon is standing. Even though Mastodon can be considered "real ActivityPub" and "implemented".

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #ActivityPub
  26. CW: DI.DAY September 2026: Tanz durch die Instanzen; CW: lang (fast 1200 Zeichen), Fediverse-Meta, Fediverse-über-Mastodon-hinaus-Meta, Quote-Post
    Hat von euch Nicht-Mastodon-Fediverse-Leuten, bei denen BigBlueButton geht, jemand Sonntag von 16 bis 18 Uhr Zeit?

    RE: https://rz-social.de/@gal1le0/117185573856020567

    #Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #DI.Day #DigitalIndependenceDay
  27. CW: DI.DAY September 2026: Tanz durch die Instanzen; CW: lang (fast 1200 Zeichen), Fediverse-Meta, Fediverse-über-Mastodon-hinaus-Meta, Quote-Post
    Hat von euch Nicht-Mastodon-Fediverse-Leuten, bei denen BigBlueButton geht, jemand Sonntag von 16 bis 18 Uhr Zeit?

    RE: https://rz-social.de/@gal1le0/117185573856020567

    #Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #DI.Day #DigitalIndependenceDay
  28. CW: DI.DAY September 2026: Tanz durch die Instanzen; CW: lang (fast 1200 Zeichen), Fediverse-Meta, Fediverse-über-Mastodon-hinaus-Meta, Quote-Post
    Hat von euch Nicht-Mastodon-Fediverse-Leuten, bei denen BigBlueButton geht, jemand Sonntag von 16 bis 18 Uhr Zeit?

    RE: https://rz-social.de/@gal1le0/117185573856020567

    #Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #DI.Day #DigitalIndependenceDay
  29. CW: DI.DAY September 2026: Tanz durch die Instanzen; CW: lang (fast 1200 Zeichen), Fediverse-Meta, Fediverse-über-Mastodon-hinaus-Meta, Quote-Post
    Hat von euch Nicht-Mastodon-Fediverse-Leuten, bei denen BigBlueButton geht, jemand Sonntag von 16 bis 18 Uhr Zeit?

    RE: https://rz-social.de/@gal1le0/117185573856020567

    #Long #LongPost #CWLong #CWLongPost #LangerPost #CWLangerPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #DI.Day #DigitalIndependenceDay
  30. I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).

    The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.

    This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)

    #Mampuku #Netflix #FediMeta

  31. I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).

    The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.

    This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)

    #Mampuku #Netflix #FediMeta

  32. I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).

    The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.

    This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)

    #Mampuku #Netflix #FediMeta

  33. I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).

    The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.

    This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)

    #Mampuku #Netflix #FediMeta

  34. I'm watching Mampuku on Netflix (15 minute episodes, so much better than the description makes it out to be).

    The main character's husband is an inventor. What drives him is the desire to create things that make people happy and make their lives better. They are lovely people to hang out with as I watch the series.

    This is a mindset I want to see more of in the world. (And explains yet another reason why I love the company here on Fedi.)

    #Mampuku #Netflix #FediMeta

  35. Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
    #Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
    #fedimeta

  36. Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
    #Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
    #fedimeta

  37. Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
    #Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
    #fedimeta

  38. Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
    #Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
    #fedimeta

  39. Ich habe mit tatsächlich gestern Gedanken darüber gemacht. Man muss #Hashtags auch gemäßigt benutzen. Nutzt man zu viele, wirkt es attention-seeking, nutzt man zu wenige, wird man nicht gefunden. Außerdem erreicht man auf manchen Instanzen schnell die Längenbegrenzung. Dann gibt es oft noch für ein Thema mehrere Hashtags (schreibt man jetzt 26 oder 2026?), und so füllt sich der Post.
    #Mastodon (WebUI) zeigt Hashtags am Ende des Posts wenigstens kleiner an, damit sie weniger stören.
    #fedimeta