#cwcharacterlimitmeta — Public Fediverse posts

@Chao-c'

Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.

This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.

(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.

Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.

As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.

I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).

Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.

But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.

From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.

The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.

On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.

At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.

As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously?

Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.

Hubzilla is almost as much an omni-federational monster as Friendica.

• It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
• It used to have optional StatusNet support which is how Mastodon federated with it immediately.
• It can optionally federate with diaspora*; Mastodon can't do that.
• It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
• It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
• It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
• It still has an optional built-in XMPP client; Mastodon doesn't have that.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.

If the latter, I'll gladly prove you wrong.

I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.

Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.

Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.

And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta

@Chao-c'

Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.

This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.

(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.

Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.

As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.

I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).

Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.

But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.

From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.

The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.

On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.

At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.

As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously?

Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.

Hubzilla is almost as much an omni-federational monster as Friendica.

• It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
• It used to have optional StatusNet support which is how Mastodon federated with it immediately.
• It can optionally federate with diaspora*; Mastodon can't do that.
• It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
• It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
• It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
• It still has an optional built-in XMPP client; Mastodon doesn't have that.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.

If the latter, I'll gladly prove you wrong.

I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.

Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.

Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.

And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta

@Chao-c'

Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.

This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.

(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.

Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.

As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.

I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).

Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.

But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.

From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.

The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.

On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.

At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.

As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously?

Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.

Hubzilla is almost as much an omni-federational monster as Friendica.

• It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
• It used to have optional StatusNet support which is how Mastodon federated with it immediately.
• It can optionally federate with diaspora*; Mastodon can't do that.
• It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
• It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
• It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
• It still has an optional built-in XMPP client; Mastodon doesn't have that.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.

If the latter, I'll gladly prove you wrong.

I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.

Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.

Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.

And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta

@Chao-c'

Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.

This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.

(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.

Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.

As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.

I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).

Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.

But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.

From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.

The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.

On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.

At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.

As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously?

Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.

Hubzilla is almost as much an omni-federational monster as Friendica.

• It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
• It used to have optional StatusNet support which is how Mastodon federated with it immediately.
• It can optionally federate with diaspora*; Mastodon can't do that.
• It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
• It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
• It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
• It still has an optional built-in XMPP client; Mastodon doesn't have that.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.

If the latter, I'll gladly prove you wrong.

I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.

Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.

Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.

And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta

@Chao-c'

Friendica is missing polls altogether and the stunt with language auto-detection is damaging built-in translation feature in Mastodon.

Mastodon has no concept of enclosed conversations which is damaging threaded conversations at least on Hubzilla, (streams) and Forte, as they were created by Mike Macgirvin for Mistpark (now Friendica) in 2010. Mastodon has no chance whatsoever to implement FEP-171b "Conversation Containers" because it lacks even the bare basics.

This is the very reason why Mike Macgirvin (creator of Friendica and Hubzilla and still maintainer of (streams) and Forte) has introduced yet another server-wide anti-Mastodon countermeasure named FedUp to both (streams) and Forte. Its effect is that it blocks all Fediverse server software that doesn't understand enclosed, one-post-several-comments conversations and the principle of all comments always going directly to the original poster who then forwards them to all other participants in the conversation.

(streams) and Forte already have the server-wide User Agent Filter that can block entire Fediverse server applications by their user channel. It was created and mostly marketed as a way of blocking Threads without a URL list, without constantly having to add new URLs to a list because Threads changed its URLs. But it's just as capable at entirely blocking all present and future Mastodon servers, and Mike even describes it as such.

Also, want to know the reason why Mike still keeps Nomad-based (streams) alive in spite of also having ActivityPub-based Forte with almost feature parity? It's because ActivityPub is optional on (streams) at channel level. The ActivityPub switch can be used as a last-resort anti-Mastodon countermeasure even though its side-effects are tremendous. The most important (streams) group, a support group, by the way, used to have ActivityPub off with the very purpose of keeping obnoxious Mastodon users out. It only turned ActivityPub on when it also became the unofficial support group for Forte.

As I've said elsewhere: It isn't Mastodon that's the ActivityPub reference implementation of ActivityPub with everything that's different being broken. Mike Macgirvin has built all his ActivityPub implementations by the book, and so have Hubzilla developers Mario Vavti and Harald Eilertsen, two months before Mastodon itself had ActivityPub support. In the meantime, Mastodon's developers deliberately and intentionally break compatibility with the rest of the Fediverse to fool Mastodon users like you into considering the non-Mastodon Fediverse broken.

I would also appreciate longer HTML files as kind of "media attachments" and not body of the post. The main problem is perhaps that Mastodon chose to ignore the post title field altogether and does not allow markup in post body (but there is entire huge fork called Glitch, which supports markup, but perhaps markup is what you want in longer texts, kind of attachments - but not short on-wall posts?)

The solution for this would lie in the dichotomy between Note-type objects (tweets are supposed to be this) and Article-type objects (longer posts are supposed to be this).

Mastodon supports both in a way. But it only renders Note-type objects. Even then, it still throws away the title and all attached images except for the first four. Its HTML sanitiser removes half of the text formatting, including embedded images. As for Article-type objects, it shows them as a small "toot" with the title and a link to the original. Only recently, probably also under pressure from commercial players like Ghost, Mastodon added the summary which it otherwise uses as the CW field.

But this is highly inconvenient. Hardly any Mastodon user can be bothered to click or tap the link to the original. They don't understand that there's a Fediverse post behind that link, much less that if they comment on the "toot" with the link, they comment on the post behind the link itself. Besides, what's behind the link won't show up on their Mastodon interface. Instead, if they're on a phone, their browser will open.

From this stems a debate that's as old as Mastodon's participation in the Fediverse. A prime example of culture clash.

The developers and users of Friendica, Hubzilla, (streams) and Forte want Mastodon as well as all its apps to fully render all their contents in the timeline. Including the title, including all text formatting, including as many embedded images as there are, as images actually embedded within the text, of course. The very same thing happens where they are. It's normal for them. It's the standard for them. It's part of their culture. What Mastodon does on their Note-type objects is crippling and defacing, and what Mastodon does on their Article-type objects is silencing to the point of wholesale censorship of several competitors.

On the other hand, the Mastodon devs refuse to add full HTML rich text rendering to Mastodon, and the Mastodon users don't want it anyway. In fact, many Mastodon users are highly disturbed by there being "toots" that are longer than 500 characters, and some are disturbed by there being any text formatting (displaying support for which was only introduced in October, 2022 with Mastodon 4.0, by the way). Their culture is that of purist microblogging in plain text with no more than 500 characters. It's already too much what Mastodon and its apps show already now. Thousands upon thousands of Mastodon users would go and block each and every server that sends anything over 500 characters if they knew that this is an option.

At the same time, hardly anyone on Mastodon even takes into consideration that whatever "long posts" come from has something like a culture of its own in the first place. It can't be culture if it isn't Mastodon's.

As I mentioned in the previous answer, Hubzilla just does too many things differently and focuses on experience of local users of instance - not on federated interoperability.

Seriously?

Hubzilla has had full-blown nomadic identity since almost four years before Mastodon came out.

Hubzilla is almost as much an omni-federational monster as Friendica.

• It has optional ActivityPub support, unlike Mastodon almost strictly by the official W3C specification, and it has had ActivityPub support before Mastodon had it.
• It used to have optional StatusNet support which is how Mastodon federated with it immediately.
• It can optionally federate with diaspora*; Mastodon can't do that.
• It can optionally federate via ActivityPump, the protocol that replaced StatusNet on Identi.ca; Mastodon can't do that.
• It can optionally cross-post to Dreamwidth, Libertree, LiveJournal and WordPress. It has been able to do either years before WordPress got its ActivityPub plug-in. Mastodon can't do either.
• It still has the optional technology to bidirectionally connect to 𝕏; Mastodon doesn't have that.
• It still has an optional built-in XMPP client; Mastodon doesn't have that.

Mastodon is simply lights years ahead.

I sincerely hope that you only mean that Mastodon is ahead of others in terms of easy on-boarding of clueless newbies. And not that Mastodon is generally ahead of Hubzilla technologically and in features.

If the latter, I'll gladly prove you wrong.

I would prefer moderation to be more collective responsibility, so posts can receive perhaps kind of negative points, and people can choose to join shared blocklists and so, instead of relying of some superhero capabilites of moderators (which I don't have).

The problem with this is blind faith in those who maintain the blocklists.

Big blocklists tend to be automatically generated from smaller blocklists, letting everything from each one of these blocklists in, only weeding out double entries, if at all. Single persons have unlimited power over who is allowed to interact with thousands upon thousands of Mastodon servers and who isn't.

Now imagine that someone who maintains a popular blocklist is too disturbed by non-Mastodon content. It's too long, it doesn't follow Mastodon guidelines, it goes against Mastodon's culture, so it has to go. And then they start adding every single server URL from which obvious non-Mastodon content comes to their blocklist. Or they even use a script to harvest FediDB and Fediverse Observer for URLs of servers of certain non-Mastodon Fediverse applications and automatically add them to their blocklist.

And all of a sudden, almost entire non-Mastodon Fediverse server applications are completely blocked from thousands upon thousands of Mastodon servers just because they aren't Mastodon, just because they don't act like Mastodon. Essentially, just because one individual wants the Fediverse to be only Mastodon "again" (which it never was).

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Mastodon #MastodonCentricity #MastodonNormativity #Friendica #Hubzilla #Streams #(streams) #Forte #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Conversations #FEP_171b #ConversationContainers #Blocklist #Blocklists #BlocklistMeta #CWBlocklistMeta

@william ⁂ maggos In this regard, Mastodon has only got one major advantage: It has an official app.

Phone users used to see Twitter as a phone app that they loaded from their app store. Mastodon is the only *blogging thing in the Fediverse that they can load from their app store.

This is one reason why just about all Mastodon newbies use the official app and why they're on mastodon.social (it's the default in the official app, and since they don't know what this setting does, they leave it on default).

Mastodon even gets away with an official app that's far from good, much less fully features. All the newbies don't have anything to compare with. If Mastodon is a phone app to them, then the official app's feature set is Mastodon's feature set. If a feature isn't implemented in the official app, then Mastodon doesn't have it. I dare say that well over 80% of all Mastodon users have never in their lives used Mastodon's Web UI.

If someone takes the step and moves from the official Mastodon app to Ivory or Mona or IceCubes or Tusky or Fedilab or something like this, it's almost always the first time in their lives that they use an online service through an app that has a different name than the online service. Many people couldn't even imagine doing that.

This means that if Friendica and Hubzilla want to be more successful, growing beyond Mike's old "if you build it, they'll come" credo and advertising more isn't sufficient. People must be able to load Friendica/Hubzilla onto their phones from their app store. This requires an official app named "Friendica"/"Hubzilla" with a native, up-to-date iOS UI in the Apple App Store and one with a native, up-to-date Android UI in the Google Play Store. The existence of an official phone app in the Apple App Store and the Google Play Store is essential for being considered existent in the first place.

A commonplace attitude on Friendica and even more so on Hubzilla is that both can be installed as a PWA. But seriously, 99.9% of all phone users don't even know that PWAs exist. They don't know what that is. Not to mention that they expect and demand a native mobile UI in the style of their phone OS and not a generic Web UI.

Now, what would this app have to look like?

If the advantages of Friendica and Hubzilla over Mastodon are to be emphasised and underlined, and if this app is to become people's one and only daily driver UI, it will have to be fully featured. Minus the settings for the Web UI (e.g. the theme settings and the PDL editor on Hubzilla), minus stuff that you'll never need if you only ever use the phone app and never the server UI (e.g. Webpages on Hubzilla), but otherwise fully featured. This would also demonstrate just how vastly more powerful Friendica and Hubzilla are than Mastodon.

The obvious downside is that such an app would be a feature monster. Bigger and more feature-laden than any Android e-mail app or OpenStreetMap editor.

There has been some talk about building an official Hubzilla phone app. Some Hubzilla users have proposed an app that only offers the very basics. However, their idea behind this is not to make the app easier for newbies to use, but to make it easier for the developers to build. They're often still stuck in the early 2010s when phone apps for websites were considered gimmicks. They think that people will only use the app when they're out and about, and when they're back home, they'll sit down behind their computers and use the Web interface. Thus, phone apps only need the most basic features implemented.

But 2026 is not 2011. The huge majority of Mastodon users only use Mastodon through a phone app. Even when they're at home. As I've said: If the app doesn't have a feature, the whole product doesn't have the feature, regardless of whether or not the feature is implemented in the server backend and even in the Web frontend.

Besides, even Friendica's basic features that you'll need all the time are a lot. Hubzilla's basic features that you'll need all the time are even more numerous.

Shall people be limited to posting in public when they're on a phone because the phone app doesn't have any permission settings?

Shall people be limited to posting to their contacts when they're on a phone because someone decided that support for groups would make the phone app too complex?

Shall people wait until they're home, and they've got some time to fire up a computer, open a Web browser and log onto the Web interface to accept connection requests because the phone app doesn't have any connection settings? What if they don't have a computer?

Let's face it, social networking itself is a complex thing. And I mean actual social networking. Not misusing glorified SMS as a social network. Real social networking. Facebook-level social networking. Google+-level social networking. MySpace-level social networking.

Thus, a social networking phone app with all features necessary for real social networking has to be complex. This isn't a Friendica/Hubzilla issue. Don't believe that the official Facebook apps are simple.

This is also why so many prefer 𝕏 over Facebook. Facebook is complex. Facebook isn't just register, follow, post. 𝕏 is much more simple. 𝕏 is glorified SMS. 𝕏 is literally just register, follow, tweet. Facebook is rocket science whereas 𝕏 is for dumb-dumbs.

And it's because Mastodon is so lacking that it's for dumb-dumbs by Fediverse standards. In fact, if you don't read those panicky "it's too complicated because you have to know what a server is" posts, if you just load the app and create an account, Mastodon, through the official app, is for dumb-dumbs by all standards.

However, those who actually are on Facebook are willing to put up with something more complex. They need something more complex than glorified SMS for dumb-dumbs. They need the extra features that Facebook has that 𝕏 doesn't, even if these are the very features that deny Facebook the "for dumb-dumbs" attribute.

Send them to Mastodon, and they'll be irritated and even repelled because this feature isn't there, and that feature isn't there, and that feature is cut down beyond recognition, and they can't find any interesting people (not because Mastodon is decentralised, and the interesting people are on other servers, but because Mastodon's directory sucks arse in comparison with Facebook's), and what's with that stupid character limit?

On Friendica and Hubzilla, this feature and that feature have been there for longer than Mastodon itself, that feature is even more powerful than on Facebook proper, interesting people are being shoved into their faces once they've filled out their profile, even more so once they've got some connections, and there is no character limit worth speaking of.

But as long as Friendica and Hubzilla don't have official, fully daily-driveable phone apps named "Friendica" and "Hubzilla" respectively, they simply don't exist.

Granted, there's another obstacle. Many Mastodon users say the Fediverse needs a Facebook alternative. If you tell them about Friendica and its descendants, some will be very thankful because they've genuinely never heard of any of these.

Others will tell you that they know Friendica and maybe even Hubzilla. But they also say that none of these are Facebook alternatives. For when they say, "alternative," what they really mean is, "1:1 clone, just with a different name and decentralised and with ActivityPub and without spying and without the recent enshittification and without the evil CEO, otherwise absolutely identical."

One big aspect of this is that, as they say, the Fediverse needs an alternative to Facebook Groups. Friendica groups are exactly that because they were designed to be exactly that. Hubzilla forums, (streams) groups, Forte groups, all just that. But according to these people, they don't count because they aren't handled in precisely the same way as Facebook groups. Facebook groups aren't separate accounts. And different equals bad.

What really has me shake my head is that those who want a 1:1 Facebook clone continue to use Mastodon as a Facebook alternative. Even though Friendica and its family are vastly closer to Facebook regardless. Even though Mastodon not only doesn't have groups at all, but it doesn't even have any support for external groups. Is shouting into the void with a bunch of hashtags and hoping the right people will hear you really that much better than a Friendica group or a Hubzilla forum or maybe a PieFed community?

By the way: Just how faithful a Twitter clone is Mastodon really, seeing as Misskey and the Forkeys have the odd Twitter feature that Mastodon still lacks, seeing as even Mastodon gradually becomes more complex than 𝕏, much more so than when-it-still-was-good Twitter?

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Misskey #Forkey #Forkeys #PieFed #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #App #PhoneApp #iPhoneApp #iOSApp #AndroidApp #SocialNetwork #SocialNetworking #Twitter #𝕏 #Facebook #FacebookGroups

@william ⁂ maggos In this regard, Mastodon has only got one major advantage: It has an official app.

Phone users used to see Twitter as a phone app that they loaded from their app store. Mastodon is the only *blogging thing in the Fediverse that they can load from their app store.

This is one reason why just about all Mastodon newbies use the official app and why they're on mastodon.social (it's the default in the official app, and since they don't know what this setting does, they leave it on default).

Mastodon even gets away with an official app that's far from good, much less fully features. All the newbies don't have anything to compare with. If Mastodon is a phone app to them, then the official app's feature set is Mastodon's feature set. If a feature isn't implemented in the official app, then Mastodon doesn't have it. I dare say that well over 80% of all Mastodon users have never in their lives used Mastodon's Web UI.

If someone takes the step and moves from the official Mastodon app to Ivory or Mona or IceCubes or Tusky or Fedilab or something like this, it's almost always the first time in their lives that they use an online service through an app that has a different name than the online service. Many people couldn't even imagine doing that.

This means that if Friendica and Hubzilla want to be more successful, growing beyond Mike's old "if you build it, they'll come" credo and advertising more isn't sufficient. People must be able to load Friendica/Hubzilla onto their phones from their app store. This requires an official app named "Friendica"/"Hubzilla" with a native, up-to-date iOS UI in the Apple App Store and one with a native, up-to-date Android UI in the Google Play Store. The existence of an official phone app in the Apple App Store and the Google Play Store is essential for being considered existent in the first place.

A commonplace attitude on Friendica and even more so on Hubzilla is that both can be installed as a PWA. But seriously, 99.9% of all phone users don't even know that PWAs exist. They don't know what that is. Not to mention that they expect and demand a native mobile UI in the style of their phone OS and not a generic Web UI.

Now, what would this app have to look like?

If the advantages of Friendica and Hubzilla over Mastodon are to be emphasised and underlined, and if this app is to become people's one and only daily driver UI, it will have to be fully featured. Minus the settings for the Web UI (e.g. the theme settings and the PDL editor on Hubzilla), minus stuff that you'll never need if you only ever use the phone app and never the server UI (e.g. Webpages on Hubzilla), but otherwise fully featured. This would also demonstrate just how vastly more powerful Friendica and Hubzilla are than Mastodon.

The obvious downside is that such an app would be a feature monster. Bigger and more feature-laden than any Android e-mail app or OpenStreetMap editor.

There has been some talk about building an official Hubzilla phone app. Some Hubzilla users have proposed an app that only offers the very basics. However, their idea behind this is not to make the app easier for newbies to use, but to make it easier for the developers to build. They're often still stuck in the early 2010s when phone apps for websites were considered gimmicks. They think that people will only use the app when they're out and about, and when they're back home, they'll sit down behind their computers and use the Web interface. Thus, phone apps only need the most basic features implemented.

But 2026 is not 2011. The huge majority of Mastodon users only use Mastodon through a phone app. Even when they're at home. As I've said: If the app doesn't have a feature, the whole product doesn't have the feature, regardless of whether or not the feature is implemented in the server backend and even in the Web frontend.

Besides, even Friendica's basic features that you'll need all the time are a lot. Hubzilla's basic features that you'll need all the time are even more numerous.

Shall people be limited to posting in public when they're on a phone because the phone app doesn't have any permission settings?

Shall people be limited to posting to their contacts when they're on a phone because someone decided that support for groups would make the phone app too complex?

Shall people wait until they're home, and they've got some time to fire up a computer, open a Web browser and log onto the Web interface to accept connection requests because the phone app doesn't have any connection settings? What if they don't have a computer?

Let's face it, social networking itself is a complex thing. And I mean actual social networking. Not misusing glorified SMS as a social network. Real social networking. Facebook-level social networking. Google+-level social networking. MySpace-level social networking.

Thus, a social networking phone app with all features necessary for real social networking has to be complex. This isn't a Friendica/Hubzilla issue. Don't believe that the official Facebook apps are simple.

This is also why so many prefer 𝕏 over Facebook. Facebook is complex. Facebook isn't just register, follow, post. 𝕏 is much more simple. 𝕏 is glorified SMS. 𝕏 is literally just register, follow, tweet. Facebook is rocket science whereas 𝕏 is for dumb-dumbs.

And it's because Mastodon is so lacking that it's for dumb-dumbs by Fediverse standards. In fact, if you don't read those panicky "it's too complicated because you have to know what a server is" posts, if you just load the app and create an account, Mastodon, through the official app, is for dumb-dumbs by all standards.

However, those who actually are on Facebook are willing to put up with something more complex. They need something more complex than glorified SMS for dumb-dumbs. They need the extra features that Facebook has that 𝕏 doesn't, even if these are the very features that deny Facebook the "for dumb-dumbs" attribute.

Send them to Mastodon, and they'll be irritated and even repelled because this feature isn't there, and that feature isn't there, and that feature is cut down beyond recognition, and they can't find any interesting people (not because Mastodon is decentralised, and the interesting people are on other servers, but because Mastodon's directory sucks arse in comparison with Facebook's), and what's with that stupid character limit?

On Friendica and Hubzilla, this feature and that feature have been there for longer than Mastodon itself, that feature is even more powerful than on Facebook proper, interesting people are being shoved into their faces once they've filled out their profile, even more so once they've got some connections, and there is no character limit worth speaking of.

But as long as Friendica and Hubzilla don't have official, fully daily-driveable phone apps named "Friendica" and "Hubzilla" respectively, they simply don't exist.

Granted, there's another obstacle. Many Mastodon users say the Fediverse needs a Facebook alternative. If you tell them about Friendica and its descendants, some will be very thankful because they've genuinely never heard of any of these.

Others will tell you that they know Friendica and maybe even Hubzilla. But they also say that none of these are Facebook alternatives. For when they say, "alternative," what they really mean is, "1:1 clone, just with a different name and decentralised and with ActivityPub and without spying and without the recent enshittification and without the evil CEO, otherwise absolutely identical."

One big aspect of this is that, as they say, the Fediverse needs an alternative to Facebook Groups. Friendica groups are exactly that because they were designed to be exactly that. Hubzilla forums, (streams) groups, Forte groups, all just that. But according to these people, they don't count because they aren't handled in precisely the same way as Facebook groups. Facebook groups aren't separate accounts. And different equals bad.

What really has me shake my head is that those who want a 1:1 Facebook clone continue to use Mastodon as a Facebook alternative. Even though Friendica and its family are vastly closer to Facebook regardless. Even though Mastodon not only doesn't have groups at all, but it doesn't even have any support for external groups. Is shouting into the void with a bunch of hashtags and hoping the right people will hear you really that much better than a Friendica group or a Hubzilla forum or maybe a PieFed community?

By the way: Just how faithful a Twitter clone is Mastodon really, seeing as Misskey and the Forkeys have the odd Twitter feature that Mastodon still lacks, seeing as even Mastodon gradually becomes more complex than 𝕏, much more so than when-it-still-was-good Twitter?

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Misskey #Forkey #Forkeys #PieFed #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #App #PhoneApp #iPhoneApp #iOSApp #AndroidApp #SocialNetwork #SocialNetworking #Twitter #𝕏 #Facebook #FacebookGroups

@william ⁂ maggos In this regard, Mastodon has only got one major advantage: It has an official app.

Phone users used to see Twitter as a phone app that they loaded from their app store. Mastodon is the only *blogging thing in the Fediverse that they can load from their app store.

This is one reason why just about all Mastodon newbies use the official app and why they're on mastodon.social (it's the default in the official app, and since they don't know what this setting does, they leave it on default).

Mastodon even gets away with an official app that's far from good, much less fully features. All the newbies don't have anything to compare with. If Mastodon is a phone app to them, then the official app's feature set is Mastodon's feature set. If a feature isn't implemented in the official app, then Mastodon doesn't have it. I dare say that well over 80% of all Mastodon users have never in their lives used Mastodon's Web UI.

If someone takes the step and moves from the official Mastodon app to Ivory or Mona or IceCubes or Tusky or Fedilab or something like this, it's almost always the first time in their lives that they use an online service through an app that has a different name than the online service. Many people couldn't even imagine doing that.

This means that if Friendica and Hubzilla want to be more successful, growing beyond Mike's old "if you build it, they'll come" credo and advertising more isn't sufficient. People must be able to load Friendica/Hubzilla onto their phones from their app store. This requires an official app named "Friendica"/"Hubzilla" with a native, up-to-date iOS UI in the Apple App Store and one with a native, up-to-date Android UI in the Google Play Store. The existence of an official phone app in the Apple App Store and the Google Play Store is essential for being considered existent in the first place.

A commonplace attitude on Friendica and even more so on Hubzilla is that both can be installed as a PWA. But seriously, 99.9% of all phone users don't even know that PWAs exist. They don't know what that is. Not to mention that they expect and demand a native mobile UI in the style of their phone OS and not a generic Web UI.

Now, what would this app have to look like?

If the advantages of Friendica and Hubzilla over Mastodon are to be emphasised and underlined, and if this app is to become people's one and only daily driver UI, it will have to be fully featured. Minus the settings for the Web UI (e.g. the theme settings and the PDL editor on Hubzilla), minus stuff that you'll never need if you only ever use the phone app and never the server UI (e.g. Webpages on Hubzilla), but otherwise fully featured. This would also demonstrate just how vastly more powerful Friendica and Hubzilla are than Mastodon.

The obvious downside is that such an app would be a feature monster. Bigger and more feature-laden than any Android e-mail app or OpenStreetMap editor.

There has been some talk about building an official Hubzilla phone app. Some Hubzilla users have proposed an app that only offers the very basics. However, their idea behind this is not to make the app easier for newbies to use, but to make it easier for the developers to build. They're often still stuck in the early 2010s when phone apps for websites were considered gimmicks. They think that people will only use the app when they're out and about, and when they're back home, they'll sit down behind their computers and use the Web interface. Thus, phone apps only need the most basic features implemented.

But 2026 is not 2011. The huge majority of Mastodon users only use Mastodon through a phone app. Even when they're at home. As I've said: If the app doesn't have a feature, the whole product doesn't have the feature, regardless of whether or not the feature is implemented in the server backend and even in the Web frontend.

Besides, even Friendica's basic features that you'll need all the time are a lot. Hubzilla's basic features that you'll need all the time are even more numerous.

Shall people be limited to posting in public when they're on a phone because the phone app doesn't have any permission settings?

Shall people be limited to posting to their contacts when they're on a phone because someone decided that support for groups would make the phone app too complex?

Shall people wait until they're home, and they've got some time to fire up a computer, open a Web browser and log onto the Web interface to accept connection requests because the phone app doesn't have any connection settings? What if they don't have a computer?

Let's face it, social networking itself is a complex thing. And I mean actual social networking. Not misusing glorified SMS as a social network. Real social networking. Facebook-level social networking. Google+-level social networking. MySpace-level social networking.

Thus, a social networking phone app with all features necessary for real social networking has to be complex. This isn't a Friendica/Hubzilla issue. Don't believe that the official Facebook apps are simple.

This is also why so many prefer 𝕏 over Facebook. Facebook is complex. Facebook isn't just register, follow, post. 𝕏 is much more simple. 𝕏 is glorified SMS. 𝕏 is literally just register, follow, tweet. Facebook is rocket science whereas 𝕏 is for dumb-dumbs.

And it's because Mastodon is so lacking that it's for dumb-dumbs by Fediverse standards. In fact, if you don't read those panicky "it's too complicated because you have to know what a server is" posts, if you just load the app and create an account, Mastodon, through the official app, is for dumb-dumbs by all standards.

However, those who actually are on Facebook are willing to put up with something more complex. They need something more complex than glorified SMS for dumb-dumbs. They need the extra features that Facebook has that 𝕏 doesn't, even if these are the very features that deny Facebook the "for dumb-dumbs" attribute.

Send them to Mastodon, and they'll be irritated and even repelled because this feature isn't there, and that feature isn't there, and that feature is cut down beyond recognition, and they can't find any interesting people (not because Mastodon is decentralised, and the interesting people are on other servers, but because Mastodon's directory sucks arse in comparison with Facebook's), and what's with that stupid character limit?

On Friendica and Hubzilla, this feature and that feature have been there for longer than Mastodon itself, that feature is even more powerful than on Facebook proper, interesting people are being shoved into their faces once they've filled out their profile, even more so once they've got some connections, and there is no character limit worth speaking of.

But as long as Friendica and Hubzilla don't have official, fully daily-driveable phone apps named "Friendica" and "Hubzilla" respectively, they simply don't exist.

Granted, there's another obstacle. Many Mastodon users say the Fediverse needs a Facebook alternative. If you tell them about Friendica and its descendants, some will be very thankful because they've genuinely never heard of any of these.

Others will tell you that they know Friendica and maybe even Hubzilla. But they also say that none of these are Facebook alternatives. For when they say, "alternative," what they really mean is, "1:1 clone, just with a different name and decentralised and with ActivityPub and without spying and without the recent enshittification and without the evil CEO, otherwise absolutely identical."

One big aspect of this is that, as they say, the Fediverse needs an alternative to Facebook Groups. Friendica groups are exactly that because they were designed to be exactly that. Hubzilla forums, (streams) groups, Forte groups, all just that. But according to these people, they don't count because they aren't handled in precisely the same way as Facebook groups. Facebook groups aren't separate accounts. And different equals bad.

What really has me shake my head is that those who want a 1:1 Facebook clone continue to use Mastodon as a Facebook alternative. Even though Friendica and its family are vastly closer to Facebook regardless. Even though Mastodon not only doesn't have groups at all, but it doesn't even have any support for external groups. Is shouting into the void with a bunch of hashtags and hoping the right people will hear you really that much better than a Friendica group or a Hubzilla forum or maybe a PieFed community?

By the way: Just how faithful a Twitter clone is Mastodon really, seeing as Misskey and the Forkeys have the odd Twitter feature that Mastodon still lacks, seeing as even Mastodon gradually becomes more complex than 𝕏, much more so than when-it-still-was-good Twitter?

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Misskey #Forkey #Forkeys #PieFed #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #App #PhoneApp #iPhoneApp #iOSApp #AndroidApp #SocialNetwork #SocialNetworking #Twitter #𝕏 #Facebook #FacebookGroups

@william ⁂ maggos In this regard, Mastodon has only got one major advantage: It has an official app.

Phone users used to see Twitter as a phone app that they loaded from their app store. Mastodon is the only *blogging thing in the Fediverse that they can load from their app store.

This is one reason why just about all Mastodon newbies use the official app and why they're on mastodon.social (it's the default in the official app, and since they don't know what this setting does, they leave it on default).

Mastodon even gets away with an official app that's far from good, much less fully features. All the newbies don't have anything to compare with. If Mastodon is a phone app to them, then the official app's feature set is Mastodon's feature set. If a feature isn't implemented in the official app, then Mastodon doesn't have it. I dare say that well over 80% of all Mastodon users have never in their lives used Mastodon's Web UI.

If someone takes the step and moves from the official Mastodon app to Ivory or Mona or IceCubes or Tusky or Fedilab or something like this, it's almost always the first time in their lives that they use an online service through an app that has a different name than the online service. Many people couldn't even imagine doing that.

This means that if Friendica and Hubzilla want to be more successful, growing beyond Mike's old "if you build it, they'll come" credo and advertising more isn't sufficient. People must be able to load Friendica/Hubzilla onto their phones from their app store. This requires an official app named "Friendica"/"Hubzilla" with a native, up-to-date iOS UI in the Apple App Store and one with a native, up-to-date Android UI in the Google Play Store. The existence of an official phone app in the Apple App Store and the Google Play Store is essential for being considered existent in the first place.

A commonplace attitude on Friendica and even more so on Hubzilla is that both can be installed as a PWA. But seriously, 99.9% of all phone users don't even know that PWAs exist. They don't know what that is. Not to mention that they expect and demand a native mobile UI in the style of their phone OS and not a generic Web UI.

Now, what would this app have to look like?

If the advantages of Friendica and Hubzilla over Mastodon are to be emphasised and underlined, and if this app is to become people's one and only daily driver UI, it will have to be fully featured. Minus the settings for the Web UI (e.g. the theme settings and the PDL editor on Hubzilla), minus stuff that you'll never need if you only ever use the phone app and never the server UI (e.g. Webpages on Hubzilla), but otherwise fully featured. This would also demonstrate just how vastly more powerful Friendica and Hubzilla are than Mastodon.

The obvious downside is that such an app would be a feature monster. Bigger and more feature-laden than any Android e-mail app or OpenStreetMap editor.

There has been some talk about building an official Hubzilla phone app. Some Hubzilla users have proposed an app that only offers the very basics. However, their idea behind this is not to make the app easier for newbies to use, but to make it easier for the developers to build. They're often still stuck in the early 2010s when phone apps for websites were considered gimmicks. They think that people will only use the app when they're out and about, and when they're back home, they'll sit down behind their computers and use the Web interface. Thus, phone apps only need the most basic features implemented.

But 2026 is not 2011. The huge majority of Mastodon users only use Mastodon through a phone app. Even when they're at home. As I've said: If the app doesn't have a feature, the whole product doesn't have the feature, regardless of whether or not the feature is implemented in the server backend and even in the Web frontend.

Besides, even Friendica's basic features that you'll need all the time are a lot. Hubzilla's basic features that you'll need all the time are even more numerous.

Shall people be limited to posting in public when they're on a phone because the phone app doesn't have any permission settings?

Shall people be limited to posting to their contacts when they're on a phone because someone decided that support for groups would make the phone app too complex?

Shall people wait until they're home, and they've got some time to fire up a computer, open a Web browser and log onto the Web interface to accept connection requests because the phone app doesn't have any connection settings? What if they don't have a computer?

Let's face it, social networking itself is a complex thing. And I mean actual social networking. Not misusing glorified SMS as a social network. Real social networking. Facebook-level social networking. Google+-level social networking. MySpace-level social networking.

Thus, a social networking phone app with all features necessary for real social networking has to be complex. This isn't a Friendica/Hubzilla issue. Don't believe that the official Facebook apps are simple.

This is also why so many prefer 𝕏 over Facebook. Facebook is complex. Facebook isn't just register, follow, post. 𝕏 is much more simple. 𝕏 is glorified SMS. 𝕏 is literally just register, follow, tweet. Facebook is rocket science whereas 𝕏 is for dumb-dumbs.

And it's because Mastodon is so lacking that it's for dumb-dumbs by Fediverse standards. In fact, if you don't read those panicky "it's too complicated because you have to know what a server is" posts, if you just load the app and create an account, Mastodon, through the official app, is for dumb-dumbs by all standards.

However, those who actually are on Facebook are willing to put up with something more complex. They need something more complex than glorified SMS for dumb-dumbs. They need the extra features that Facebook has that 𝕏 doesn't, even if these are the very features that deny Facebook the "for dumb-dumbs" attribute.

Send them to Mastodon, and they'll be irritated and even repelled because this feature isn't there, and that feature isn't there, and that feature is cut down beyond recognition, and they can't find any interesting people (not because Mastodon is decentralised, and the interesting people are on other servers, but because Mastodon's directory sucks arse in comparison with Facebook's), and what's with that stupid character limit?

On Friendica and Hubzilla, this feature and that feature have been there for longer than Mastodon itself, that feature is even more powerful than on Facebook proper, interesting people are being shoved into their faces once they've filled out their profile, even more so once they've got some connections, and there is no character limit worth speaking of.

But as long as Friendica and Hubzilla don't have official, fully daily-driveable phone apps named "Friendica" and "Hubzilla" respectively, they simply don't exist.

Granted, there's another obstacle. Many Mastodon users say the Fediverse needs a Facebook alternative. If you tell them about Friendica and its descendants, some will be very thankful because they've genuinely never heard of any of these.

Others will tell you that they know Friendica and maybe even Hubzilla. But they also say that none of these are Facebook alternatives. For when they say, "alternative," what they really mean is, "1:1 clone, just with a different name and decentralised and with ActivityPub and without spying and without the recent enshittification and without the evil CEO, otherwise absolutely identical."

One big aspect of this is that, as they say, the Fediverse needs an alternative to Facebook Groups. Friendica groups are exactly that because they were designed to be exactly that. Hubzilla forums, (streams) groups, Forte groups, all just that. But according to these people, they don't count because they aren't handled in precisely the same way as Facebook groups. Facebook groups aren't separate accounts. And different equals bad.

What really has me shake my head is that those who want a 1:1 Facebook clone continue to use Mastodon as a Facebook alternative. Even though Friendica and its family are vastly closer to Facebook regardless. Even though Mastodon not only doesn't have groups at all, but it doesn't even have any support for external groups. Is shouting into the void with a bunch of hashtags and hoping the right people will hear you really that much better than a Friendica group or a Hubzilla forum or maybe a PieFed community?

By the way: Just how faithful a Twitter clone is Mastodon really, seeing as Misskey and the Forkeys have the odd Twitter feature that Mastodon still lacks, seeing as even Mastodon gradually becomes more complex than 𝕏, much more so than when-it-still-was-good Twitter?

#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #Misskey #Forkey #Forkeys #PieFed #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #App #PhoneApp #iPhoneApp #iOSApp #AndroidApp #SocialNetwork #SocialNetworking #Twitter #𝕏 #Facebook #FacebookGroups