home.social

#permissions — Public Fediverse posts

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

fetched live
  1. The Right Content, the Right Partner, the Right Deal – Frankfurt Rights

    Working to support the international rights business throughout the year, the Frankfurt Rights platform assists with rights discovery, contacts and licensing activity year-round, and even automates smaller transactions. 
    The post The Right Content, the Right Partner, the Right Deal – Frankfurt Rights appeared first on Publishing Perspectives.
    publishingperspectives.com/202

    #FrankfurtRights #FrankfurterBuchmesse #InstantPermissions #Permissions #Rights

  2. The Right Content, the Right Partner, the Right Deal – Frankfurt Rights

    Working to support the international rights business throughout the year, the Frankfurt Rights platform assists with rights discovery, contacts and licensing activity year-round, and even automates smaller transactions. 
    The post The Right Content, the Right Partner, the Right Deal – Frankfurt Rights appeared first on Publishing Perspectives.
    publishingperspectives.com/202

    #FrankfurtRights #FrankfurterBuchmesse #InstantPermissions #Permissions #Rights

  3. The Right Content, the Right Partner, the Right Deal – Frankfurt Rights

    Working to support the international rights business throughout the year, the Frankfurt Rights platform assists with rights discovery, contacts and licensing activity year-round, and even automates smaller transactions. 
    The post The Right Content, the Right Partner, the Right Deal – Frankfurt Rights appeared first on Publishing Perspectives.
    publishingperspectives.com/202

    #FrankfurtRights #FrankfurterBuchmesse #InstantPermissions #Permissions #Rights

  4. The Right Content, the Right Partner, the Right Deal – Frankfurt Rights

    Working to support the international rights business throughout the year, the Frankfurt Rights platform assists with rights discovery, contacts and licensing activity year-round, and even automates smaller transactions. 
    The post The Right Content, the Right Partner, the Right Deal – Frankfurt Rights appeared first on Publishing Perspectives.
    publishingperspectives.com/202

    #FrankfurtRights #FrankfurterBuchmesse #InstantPermissions #Permissions #Rights

  5. Warum sagt mir keiner, dass bei #Signal es mittlerweile möglich ist Gruppen zu beenden?! (Ich der*die die Gruppe verlassen hat und jedes Mal einen neuen Admin ausgewählt hat) Und warum hat mir niemand gesagt, dass es mittlerweile möglich ist, das Admins in Gruppen kürzlich eingegangene Nachrichten für alle löschen kann?!

    #signalapp #groups #permissions

  6. С 14 августа Claude Code стартует в авторежиме: что лежит в его рулбуке

    С 14 августа Claude Code будет запускать новые сессии на Pro, Max и Team в auto mode: вместо диалога «разрешить/запретить» каждую команду оценивает отдельный классификатор. Коротко о том, что печатает команда claude auto-mode defaults (60 149 символов правил, 65 запретов, тринадцать из двадцати полей окружения пустые), какие ваши правила прав продолжают работать поверх классификатора, что на самом деле стоит за цифрой 13,6% из пересказов и был ли у этой фичи откат в прошлых версиях. Читать дальше →

    habr.com/ru/articles/1068658/

    #Claude_Code #Anthropic #AIагенты #информационная_безопасность #permissions #LLM #DevOps

  7. С 14 августа Claude Code стартует в авторежиме: что лежит в его рулбуке

    С 14 августа Claude Code будет запускать новые сессии на Pro, Max и Team в auto mode: вместо диалога «разрешить/запретить» каждую команду оценивает отдельный классификатор. Коротко о том, что печатает команда claude auto-mode defaults (60 149 символов правил, 65 запретов, тринадцать из двадцати полей окружения пустые), какие ваши правила прав продолжают работать поверх классификатора, что на самом деле стоит за цифрой 13,6% из пересказов и был ли у этой фичи откат в прошлых версиях. Читать дальше →

    habr.com/ru/articles/1068658/

    #Claude_Code #Anthropic #AIагенты #информационная_безопасность #permissions #LLM #DevOps

  8. С 14 августа Claude Code стартует в авторежиме: что лежит в его рулбуке

    С 14 августа Claude Code будет запускать новые сессии на Pro, Max и Team в auto mode: вместо диалога «разрешить/запретить» каждую команду оценивает отдельный классификатор. Коротко о том, что печатает команда claude auto-mode defaults (60 149 символов правил, 65 запретов, тринадцать из двадцати полей окружения пустые), какие ваши правила прав продолжают работать поверх классификатора, что на самом деле стоит за цифрой 13,6% из пересказов и был ли у этой фичи откат в прошлых версиях. Читать дальше →

    habr.com/ru/articles/1068658/

    #Claude_Code #Anthropic #AIагенты #информационная_безопасность #permissions #LLM #DevOps

  9. 🔒 Ghid CyberPanel: Totul despre Linux ACL (Access Control Lists) și permisiunile avansate de fișiere!

    Sistemul tradițional de permisiuni din Linux (bazat pe Owner, Group și Others cu drepturi de Read/Write/Execute) este adesea prea limitativ pentru medii de lucru complexe sau servere multi-utilizator. Ghidul CyberPanel explică modul în care ACL (Access Control Lists) oferă un control granular și flexibil asupra fișierelor și directoarelor.

    ✨ De ce ai nevoie de Linux ACL?

    În modelul clasic POSIX, un fișier poate avea atribuit un singur utilizator proprietar și un singur grup. Dacă vrei să oferi permisiuni specifice de citire sau scriere unui al doilea utilizator (fără a-l adăuga în grupul principal sau fără a oferi acces tuturor celorlalți utilizatori din sistem), permisiunile standard devin insuficiente.

    Linux ACL rezolvă această problemă permițând atribuirea de drepturi individuale pentru oricâți utilizatori sau grupuri specifice pe un singur fișier sau director.

    🛠️ Comenzile fundamentale pentru gestionarea ACL:

    getfacl — Vizualizarea permisiunilor detaliate:
    Afișează lista completă de control al accesului pentru un fișier sau director.

    Bash
    getfacl fisier.txt
    setfacl — Modificarea permisiunilor ACL:
    • Adăugare permisiuni pentru un utilizator specific:

    Bash
    setfacl -m u:alex:rw fisier.txt
    • Adăugare permisiuni pentru un grup specific:

    Bash
    setfacl -m g:echipa_dev:rwx fisier.txt
    • Ștergerea unei reguli ACL specifice:

    Bash
    setfacl -x u:alex fisier.txt
    • Ștergerea tuturor regulilor ACL extinse:

    Bash
    setfacl -b fisier.txt
    📂 Permisiuni Implicite (Default ACLs) pe Directoare:

    Una dintre cele mai puternice funcționalități ACL este setarea de permisiuni implicite pe un folder. Orice fișier sau sub-director creat ulterior în interiorul acelui folder va moșteni automat regulile ACL definite:

    Bash
    setfacl -d -m g:echipa_dev:rwx /var/www/proiect
    💡 Cum recunoști un fișier configurat cu ACL?

    Atunci când listezi fișierele din terminal folosind comanda ls -l, fișierele care au reguli ACL active vor afișa un simbol + la sfârșitul șirului clasic de permisiuni (ex: -rw-rwxr--+).

    Un instrument esențial pentru orice administrator de sistem (SysAdmin) care gestionează servere de găzduire web, stocări partajate (Samba/NFS) sau proiecte colaborative pe Linux! 🚀

    #Linux #SysAdmin #ACL #LinuxACL #CyberPanel #Permissions #Security #OpenSource #TechNews

  10. @Mitch Conner @silverpill Exactly this exists on Hubzilla, (streams) and Forte. With even more options, actually. Hubzilla calls them "privacy groups", (streams) and Forte call them "access lists".

    Now it comes: You can not only post to one specific such group/list. You can also post to several ones. Or to any combination of privacy groups/access lists and single contacts.

    Better yet: You can even exclude single contacts or the members of certain privacy groups/access lists. You can post to the members of privacy groups Foo and Bar, except if they're also in privacy group Baz, and except for Alice, and in addition, you can post to Bob and Carol.

    In addition, Hubzilla, (streams) and Forte don't just define who receives the post. They don't simply flag it a DM either. They flag it "restricted" and only grant the recipients permission to read the post, read any comments and interact with anything in the conversation. In practice, this also means that those who have these permissions can not only interact with the original poster, but just as well with each other, because it isn't a DM.

    Anything that doesn't understand these permissions, e.g. Mastodon, do understand it as a DM. This limits their possibilities to interact, but it's the safe way.

    And yet, Hubzilla, (streams) and Forte still have private and/or secret groups with moderation (like Facebook groups) on top of all this. (streams) and Forte even optionally have two levels of non-moderator users.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups #PrivateGroups #Permissions #PrivacyGroups #AccessLists
  11. @Mitch Conner @silverpill Exactly this exists on Hubzilla, (streams) and Forte. With even more options, actually. Hubzilla calls them "privacy groups", (streams) and Forte call them "access lists".

    Now it comes: You can not only post to one specific such group/list. You can also post to several ones. Or to any combination of privacy groups/access lists and single contacts.

    Better yet: You can even exclude single contacts or the members of certain privacy groups/access lists. You can post to the members of privacy groups Foo and Bar, except if they're also in privacy group Baz, and except for Alice, and in addition, you can post to Bob and Carol.

    In addition, Hubzilla, (streams) and Forte don't just define who receives the post. They don't simply flag it a DM either. They flag it "restricted" and only grant the recipients permission to read the post, read any comments and interact with anything in the conversation. In practice, this also means that those who have these permissions can not only interact with the original poster, but just as well with each other, because it isn't a DM.

    Anything that doesn't understand these permissions, e.g. Mastodon, do understand it as a DM. This limits their possibilities to interact, but it's the safe way.

    And yet, Hubzilla, (streams) and Forte still have private and/or secret groups with moderation (like Facebook groups) on top of all this. (streams) and Forte even optionally have two levels of non-moderator users.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups #PrivateGroups #Permissions #PrivacyGroups #AccessLists
  12. @Mitch Conner @silverpill Exactly this exists on Hubzilla, (streams) and Forte. With even more options, actually. Hubzilla calls them "privacy groups", (streams) and Forte call them "access lists".

    Now it comes: You can not only post to one specific such group/list. You can also post to several ones. Or to any combination of privacy groups/access lists and single contacts.

    Better yet: You can even exclude single contacts or the members of certain privacy groups/access lists. You can post to the members of privacy groups Foo and Bar, except if they're also in privacy group Baz, and except for Alice, and in addition, you can post to Bob and Carol.

    In addition, Hubzilla, (streams) and Forte don't just define who receives the post. They don't simply flag it a DM either. They flag it "restricted" and only grant the recipients permission to read the post, read any comments and interact with anything in the conversation. In practice, this also means that those who have these permissions can not only interact with the original poster, but just as well with each other, because it isn't a DM.

    Anything that doesn't understand these permissions, e.g. Mastodon, do understand it as a DM. This limits their possibilities to interact, but it's the safe way.

    And yet, Hubzilla, (streams) and Forte still have private and/or secret groups with moderation (like Facebook groups) on top of all this. (streams) and Forte even optionally have two levels of non-moderator users.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups #PrivateGroups #Permissions #PrivacyGroups #AccessLists
  13. @Mitch Conner @silverpill Exactly this exists on Hubzilla, (streams) and Forte. With even more options, actually. Hubzilla calls them "privacy groups", (streams) and Forte call them "access lists".

    Now it comes: You can not only post to one specific such group/list. You can also post to several ones. Or to any combination of privacy groups/access lists and single contacts.

    Better yet: You can even exclude single contacts or the members of certain privacy groups/access lists. You can post to the members of privacy groups Foo and Bar, except if they're also in privacy group Baz, and except for Alice, and in addition, you can post to Bob and Carol.

    In addition, Hubzilla, (streams) and Forte don't just define who receives the post. They don't simply flag it a DM either. They flag it "restricted" and only grant the recipients permission to read the post, read any comments and interact with anything in the conversation. In practice, this also means that those who have these permissions can not only interact with the original poster, but just as well with each other, because it isn't a DM.

    Anything that doesn't understand these permissions, e.g. Mastodon, do understand it as a DM. This limits their possibilities to interact, but it's the safe way.

    And yet, Hubzilla, (streams) and Forte still have private and/or secret groups with moderation (like Facebook groups) on top of all this. (streams) and Forte even optionally have two levels of non-moderator users.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Streams #(streams) #Forte #Groups #FediGroups #FediverseGroups #PrivateGroups #Permissions #PrivacyGroups #AccessLists
  14. @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
  15. @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
  16. @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
  17. @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
  18. @Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.

    There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.

    I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).

    But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.

    Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.

    By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.

    In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.

    Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.

    No.

    Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)

    All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.

    I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.

    It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.

    They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.

    They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!

    If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.

    They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.

    There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).

    And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.

    First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.

    Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.

    Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?

    Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).

    Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.

    Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.

    Where are all these things? In the Fediverse, no less? Where are they?

    I'll tell you where they are.

    Friendica. Hubzilla. (streams). Forte.

    The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.

    Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.

    He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.

    Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.

    He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.

    Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.

    Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.

    One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.

    Lastly, he made it possible for third parties to add extra features by implementing an add-on system.

    I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.

    And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.

    Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.

    Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.

    Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.

    Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.

    Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.

    If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.

    I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.

    As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.

    If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.

    You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.

    You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.

    You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.

    You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.

    If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.

    Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.

    Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.

    Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.

    If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity
  19. @Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.

    There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.

    I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).

    But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.

    Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.

    By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.

    In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.

    Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.

    No.

    Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)

    All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.

    I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.

    It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.

    They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.

    They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!

    If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.

    They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.

    There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).

    And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.

    First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.

    Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.

    Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?

    Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).

    Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.

    Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.

    Where are all these things? In the Fediverse, no less? Where are they?

    I'll tell you where they are.

    Friendica. Hubzilla. (streams). Forte.

    The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.

    Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.

    He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.

    Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.

    He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.

    Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.

    Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.

    One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.

    Lastly, he made it possible for third parties to add extra features by implementing an add-on system.

    I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.

    And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.

    Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.

    Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.

    Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.

    Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.

    Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.

    If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.

    I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.

    As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.

    If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.

    You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.

    You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.

    You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.

    You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.

    If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.

    Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.

    Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.

    Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.

    If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity
  20. @Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.

    There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.

    I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).

    But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.

    Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.

    By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.

    In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.

    Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.

    No.

    Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)

    All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.

    I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.

    It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.

    They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.

    They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!

    If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.

    They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.

    There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).

    And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.

    First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.

    Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.

    Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?

    Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).

    Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.

    Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.

    Where are all these things? In the Fediverse, no less? Where are they?

    I'll tell you where they are.

    Friendica. Hubzilla. (streams). Forte.

    The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.

    Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.

    He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.

    Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.

    He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.

    Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.

    Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.

    One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.

    Lastly, he made it possible for third parties to add extra features by implementing an add-on system.

    I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.

    And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.

    Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.

    Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.

    Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.

    Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.

    Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.

    If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.

    I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.

    As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.

    If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.

    You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.

    You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.

    You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.

    You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.

    If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.

    Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.

    Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.

    Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.

    If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity
  21. @Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.

    There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.

    I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).

    But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.

    Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.

    By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.

    In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.

    Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.

    No.

    Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)

    All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.

    I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.

    It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.

    They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.

    They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!

    If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.

    They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.

    There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).

    And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.

    First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.

    Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.

    Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?

    Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).

    Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.

    Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.

    Where are all these things? In the Fediverse, no less? Where are they?

    I'll tell you where they are.

    Friendica. Hubzilla. (streams). Forte.

    The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.

    Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.

    He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.

    Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.

    He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.

    Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.

    Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.

    One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.

    Lastly, he made it possible for third parties to add extra features by implementing an add-on system.

    I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.

    And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.

    Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.

    Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.

    Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.

    Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.

    Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.

    If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.

    I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.

    As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.

    If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.

    You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.

    You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.

    You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.

    You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.

    If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.

    Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.

    Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.

    Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.

    If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity
  22. @Truth & Answers Let me be honest: Mastodon isn't the right thing to rely on for this.

    There are two common misconceptions on Mastodon about Mastodon. The first one is that Mastodon is the only free, non-commercial, non-corporate, decentralised social anything. Once Mastodon users are over this, they still think Mastodon is the best free, non-commercial, non-corporate, decentralised social anything.

    I've seen Mastodon being advertised by users as a Fediverse alternative to literally everything, including Reddit (because, like, you can communicate, right?) and even YouTube (because, like, you can upload videos, right?).

    But again, let me be honest: The only thing that Mastodon can hope to be an alternative to is 𝕏. Because it's a Twitter clone. A purist Twitter clone whose developers intentionally reject feature requests because the requested features don't fit into their image of purist, minimalist, old-school, original-gangsta microblogging. They want to keep Mastodon a slightly more glorified SMS than 𝕏.

    Mastodon isn't even the only microblogging server application in the Fediverse. It isn't even the best at that. 80-90% of Mastodon's users don't and probably will never realise that Mastodon is an intentionally crippled resource hog. Many believe that Mastodon is the fully-featured be-all, end-all of social networking.

    By the way, even the Mastodon developers claim that Mastodon is fully featured. I've had a Mastodon dev try hard to convince me that Mastodon is fully featured although I've told him that I'm on Hubzilla. He essentially tried to tell me that Mastodon has every last feature that Hubzilla has plus even more on top.

    In reality, Mastodon isn't the fully-featured be-all, end-all of social networking. It isn't even a social network. It's social media, just like 𝕏 is social media. It's designed for pumping out content and being followed because it's designed as a Twitter-like microblogging application. And it isn't even the best at microblogging.

    Almost everyone on Mastodon is fully convinced that Mastodon has to be the best. After all, it's the biggest. It's what everyone chose.

    No.

    Mastodon is the biggest because everyone who wants to leave 𝕏 or Threads or Bluesky is railroaded to Mastodon. It's the biggest because all the newbies are only told about Mastodon. It's the biggest because none of the newbies even learn upon on-boarding that other 𝕏 alternatives exist in the Fediverse, that anything else exists in the Fediverse other than Mastodon. It's the biggest because mainstream media, tech media and even Fediverse activists only ever talk about Mastodon, Mastodon, Mastodon. (Granted, it's also the biggest because it's the only one with an official phone app in the Apple App Store and the Google Play Store. Even though that app sucks.)

    All these Mastodon users who claim that Mastodon is the best choice don't realise that they themselves did, in fact, not choose Mastodon. They didn't know they had a choice. All they were told about was Mastodon. Seriously, if they'd had a choice, they'd probably be on Sharkey now and not on Mastodon.

    I've read what people had to say who moved from Friendica to Misskey. Or to now defunct Calckey/Firefish. Or to Sharkey. Or to Akkoma. All these are microblogging server applications in the Fediverse. But none of them are intentionally crippled to stay close to Twitter, at least not to such a degree as Mastodon.

    It was nothing short of eye-opening to them. Only by daily-driving something else than Mastodon did they realise what the non-Mastodon Fediverse can be like. And how crippled Mastodon actually is. That Mastodon is far from being the absolute pinnacle in decentralised social media.

    They no longer had only 500 characters. They had thousands of characters. They would have had thousands of characters on every server running that software without having to ask around which one has more than 500 characters. It felt like a restraint being removed which they had never considered a restraint, at least not that much of it.

    They saw text formatting which they considered technologically absolutely impossible in the Fediverse when they were on Mastodon. In fact, they had considered text formatting entirely impossible while on Mastodon until they had come across the first message from outside with text formatting. Actual text formatting, not Unicode trickery. Now they suddenly saw a lot of the stuff that Mastodon's HTML sanitiser removes. And they themselves could use it!

    If they were on one of the *keys, they no longer had a timeline of single-message piecemeal. For the first time ever, they experienced what it's like to have something else than single-message piecemeal. Namely entire conversations right in front of them, right away. Without having to dig for them first.

    They had features which they had always wished the Fediverse may introduce. They never knew that the Fediverse does have these features, only Mastodon doesn't. They had features that were completely unimagiable to them in the Fediverse.

    There are users who have moved from Mastodon to something "minimalist" and lightweight like snac or GoToSocial, often on self-hosted, single-user, private servers. Even they suddenly had features they didn't have on Mastodon. Mind you, while not missing a single Mastodon feature (except maybe for a built-in Web UI).

    And that's just the microblogging side of the Fediverse. None of this is actual social networking. You know, what Facebook does.

    First of all, if it's about following and being followed, it's social media. A social network doesn't have followers. In case you don't know, Facebook doesn't have followers. It has "friends". Bidirectional connections. Not 𝕏/Mastodon-like mutuals which are two connections, one in each direction, but one connection that goes both ways.

    Besides, there are even more important social networking features missing from the microblogging side of the Fediverse.

    Where are the contact suggestions? Where does Mastodon suggest new contacts based on how many contacts you have in common with them? Where does Mastodon suggest new contacts based on what profile information you have in common with them?

    Oh, right, the latter is impossible because Mastodon doesn't have profile fields with defined purposes. In fact, where are these? Every good social network has them! But Mastodon only gives you four all-purpose profile fields (just like Mastodon only gives you four of everything, four file attachments, four options in polls...).

    Where is the list of unread posts, unread comments and other unnoticed actions? How are you to make sure you really catch everything your friends do? Because you can't do that if all you have is a timeline to scroll through until you no longer see new stuff. If you manage to scroll down that far. And only absolute newbies can do that on Mastodon because they hardly follow anyone.

    Where are groups? Seriously, I've lost count of how many times Mastodon users said "the Fediverse" must introduce something like Facebook Groups. The huge majority of Mastodon users is fully convinced that the Fediverse does not have groups in any shape or form because Mastodon doesn't have them.

    Where are all these things? In the Fediverse, no less? Where are they?

    I'll tell you where they are.

    Friendica. Hubzilla. (streams). Forte.

    The actual social networking side of the Fediverse (although Hubzilla is more like a social CMS or a "social Swiss army knife" that you can also use as a Facebook-like social networking application). I mean, I've already explained that Friendica was created in 2010 as a Facebook alternative. Not a faithful Facebook clone, though, but better than Facebook.

    Mike Macgirvin took over from Facebook what social networks really need. And Farmville isn't that, and spying on your users and passing that data on to the NSA and selling it to the highest bidder isn't that, so he didn't take over that. He didn't want to build a clone that also adopts the bad sides just to be as close to the original as possible.

    He took over the detailed profiles with profile fields with dedicated purposes. He took over profile privacy settings. In general, he took over a lot of privacy features. He took over advanced user discovery and connection suggestions. He took over bidirectional connections, only without that silly name "friends". He took over groups with moderation, only that a group on Friendica is just another account with a special automated reposter. He took over enclosed threaded conversations with one post at the top and otherwise only comments. He took over a "timeline" of full conversations as the default. He took over the event calendar. And so forth.

    Instead, he added useful stuff on top. He gave Friendica all the posting features to make it fully capable of long-form blogging with all bells and whistles. No character limit (except for in the database, but I think that was over 65,000 back in the day already). All HTML text formatting features (only that Friendica only used BBcode back then; now it can optionally also use Markdown). A post/thread title. Summaries. Embedded images and other media with no limit in number. He even added a spoiler tag like in forums that can hide parts of a message.

    He took care of privacy beyond what Facebook had to offer. He introduced a permissions system. Friendica got multiple profile per account, only one of which is public, so that you can show different sides of yourself to different connections.

    Now, if you want to embed images or other media in your messages, you have to store them somewhere. And not everyone could be expected to set up a little file space somewhere. So he built a file space into Friendica, one that can even be used as a Dropbox alternative, all the way to restricted access to certain directories.

    Mike also added a content warning system that automatically generates content warnings on the reader's side, based on a keyword list. If you need something behind content warnings, add the keywords to the list, and you'll have the respective content warnings, but the next user receiving the self-same post or comment does not have these content warnings if they don't need them.

    One important part of what makes Friendica Friendica is being able to connect to a whole lot of stuff. For example, Friendica could federate with StatusNet via the OStatus protocol from the get-go; this is also how it immediately federated with Mastodon when the latter was launched. Mastodon generates an RSS feed, something that many users don't know. Friendica not only generates an Atom feed, but it can subscribe to feeds. Friendica can "federate" with e-mail. Over time, more and more connection features were added, including Tumblr, Twitter (!), Facebook (only for a few years before Facebook crippled it) and a WordPress cross-poster.

    Lastly, he made it possible for third parties to add extra features by implementing an add-on system.

    I dare those who are fully convinced that Mastodon is the best Facebook alternative possible to use Friendica for a year. Not only dip one toe in to the water, but use it as their one and only daily driver for everything they've used Mastodon for. Not scratching the surface and using it like Twitter while ignoring any and all features the Twitter they remember didn't have, but going all in. In fact, I dare those who are fully convinced that Mastodon is perfect and fully-featured to do the same.

    And then there's Hubzilla. It came to exist by Mike forking Friendica in 2011, then forking that fork the same year, then rewriting that fork of a fork in 2012, then repurposing, rebranding, repositioning and greatly expanding it in 2015. Long story.

    Hubzilla adds even more stuff on top. Most importantly, it introduced nomadic identity (https://joinfediverse.wiki/Nomadic_identity) in 2012.

    Hubzilla, or its 2012 prototype form named Red, became the first decentralised social software that uncoupled the identity from the login. This was necessary for nomadic identity, but it also introduced the option to have multiple independent identities, basically what's an account elsewhere, on the same account, the same login. This makes sense, given the many different roles and purposes a Hubzilla channel can have. The big advantage over having multiple separate accounts is that you can switch between the channels on your account without logging out and back in.

    Hubzilla, or its 2012 prototype form named Red, got an even more advanced and fine-grained permissions system. Hubzilla has 17 individual permissions on three levels, channel level, contact level, content level. At channel level, each one has seven or eight permission options to choose from, depending on whether or not it makes sense to give a permission to everyone on the Internet.

    Mike added optional features to Hubzilla that were previously unseen on social anything, features that you'd rather expect from a CMS and maybe not even from that. Non-federating long-form articles. Planning cards that are based on these articles. Wikis that can be formatted with BBcode or Markdown. Webpages that can be formatted with BBcode, Markdown or HTML, that can include dynamic content from elsewhere on the channel, and that can add extra content to the channel pages.

    Hubzilla can even act as groupware. It has a CalDAV calendar server; the event calendar can double as a crude UI for the CalDAV calendars. It has an optional CardDAV addressbook server. Its built-in file storage can be accessed via WebDAV, so you theoretically even have some cloud file space you can mount as a network drive. Rather recently, there was even a way found to tie Collabora Office into Hubzilla.

    If you should ever read about Bonfire: Bonfire is Hubzilla ordered from Wish.com. Whatever Bonfire promises to have or to introduce has been available as a rock-solid stable feature on Hubzilla for over a decade. Bonfire only gets away with what it's trying to do because nobody knows Hubzilla.

    I think it's safe to say that those who "chose" Mastodon didn't choose it over the rest of the Fediverse because it's better. They "chose" it because they didn't even know they have a choice.

    As for your post, the technology for redeveloping socialising is there. And it certainly isn't Mastodon, and it never will be Mastodon. Mastodon can't be that due to its design philosophy, due to it being a Twitter clone, due to its own developers intentionally crippling it.

    If you want to move on from 1-way interaction, you have to move on from 1-way connections. Move on from Twitter followers to Facebook friends.

    You have to offer better options for the users than shouting into the void, attaching a bunch of hashtags and hoping that some of their followers or someone who is following one of the hashtags happens to be bothered to scroll down their timeline far enough.

    You have to make sure that people don't miss content due to basic design and philosophy decisions. You have to make sure that people don't miss content because they simply never know that this content is there in the first place, because they can't scroll down far enough their timelines until they reach that content. You need something else than a timeline of single messages to scroll down with the user not having an idea just how far down that timeline goes. You have to tell the user how much unread content there is, what it is, where it is, and take the user directly to that unread content.

    You have to stop presenting content to users as a long list of single posts and more single posts with only tiny details telling them that these posts are, in fact, part of a longer conversation which they don't see. Where they have to click or tap themselves through various UI pages to see that post in its context. Users must see the whole conversation Right. Off. The bat.

    You need groups. Not kluged onto something that had no group support whatsoever two seconds earlier, not intentionally crippled, not crippled by the technology they're built upon, not intentionally re-invented to be incompatible with whatever already exists (and this is how Mastodon would do them). But fully functional, on an appropriate base, interoperable, user-moderated, optionally private, optionally hiding from directories.

    If you want to go "social", you really have to go social. You have to go Facebook, not Twitter.

    Users must find other users based on common interests. Or users living close to them. Or users with lots of contacts in common with them. Not by being on the same local/regional server of the same server about a certain topic. Not by searching for hashtags in the main profile text. But by examining specialised profile fields and the contacts.

    Users must have such users suggested to them as new connections. Users must have such users at the top of their directory. This is how Facebook does it. And this is one thing that Facebook has always done right.

    Again, Mastodon will never offer any of this. But that doesn't mean that you'll have to compromise and lower your expectations. Because you don't have to. There are server applications in the Fediverse, fully federated with Mastodon, that offer literally all of that. They exist right now. And some of them have existed for longer than Mastodon.

    If you need something better than today's Mastodon, stop wishing for a better Mastodon. Instead, use something that's better and more appropriate for the job than Mastodon right now. For it exists right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Fediverse #Mastodon #MastodonFediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Permission #Permissions #Groups #FediverseGroups #FediGroups #NomadicIdentity #MastodonCentricity #MastodonNormativity
  23. Permissions are the backbone of Linux security. Know these cold:

    Add a user to a group: usermod -aG groupname username
    Check what groups a user belongs to: groups username
    Change file ownership: chown user:group filename

    "Just chmod 777 it" is not a permissions strategy. It's a cry for help.
    #Linux #SysAdmin #Permissions #TechTip #TechTipThursday

  24. Permissions are the backbone of Linux security. Know these cold:

    Add a user to a group: usermod -aG groupname username
    Check what groups a user belongs to: groups username
    Change file ownership: chown user:group filename

    "Just chmod 777 it" is not a permissions strategy. It's a cry for help.
    #Linux #SysAdmin #Permissions #TechTip #TechTipThursday

  25. Permissions are the backbone of Linux security. Know these cold:

    Add a user to a group: usermod -aG groupname username
    Check what groups a user belongs to: groups username
    Change file ownership: chown user:group filename

    "Just chmod 777 it" is not a permissions strategy. It's a cry for help.
    #Linux #SysAdmin #Permissions #TechTip #TechTipThursday

  26. Permissions are the backbone of Linux security. Know these cold:

    Add a user to a group: usermod -aG groupname username
    Check what groups a user belongs to: groups username
    Change file ownership: chown user:group filename

    "Just chmod 777 it" is not a permissions strategy. It's a cry for help.
    #Linux #SysAdmin #Permissions #TechTip #TechTipThursday

  27. Permissions are the backbone of Linux security. Know these cold:

    Add a user to a group: usermod -aG groupname username
    Check what groups a user belongs to: groups username
    Change file ownership: chown user:group filename

    "Just chmod 777 it" is not a permissions strategy. It's a cry for help.
    #Linux #SysAdmin #Permissions #TechTip #TechTipThursday

  28. Linux folks, question:

    I setup a common directory under `/home` (`/home/common`) with `root:common` ownership and 775 permissions. I'd like the group to be set automatically to `common` whether I write the file or someone else does, so I think using `chmod -R 2775` would achieve that. Is there a way I can similarly automatically set the ownership to `root`? Or do I manually have to do that each time I add new files/directories?

    #AskFedi #Linux #Debian #Permissions

  29. Linux folks, question:

    I setup a common directory under `/home` (`/home/common`) with `root:common` ownership and 775 permissions. I'd like the group to be set automatically to `common` whether I write the file or someone else does, so I think using `chmod -R 2775` would achieve that. Is there a way I can similarly automatically set the ownership to `root`? Or do I manually have to do that each time I add new files/directories?

    #AskFedi #Linux #Debian #Permissions

  30. Linux folks, question:

    I setup a common directory under `/home` (`/home/common`) with `root:common` ownership and 775 permissions. I'd like the group to be set automatically to `common` whether I write the file or someone else does, so I think using `chmod -R 2775` would achieve that. Is there a way I can similarly automatically set the ownership to `root`? Or do I manually have to do that each time I add new files/directories?

    #AskFedi #Linux #Debian #Permissions

  31. Linux folks, question:

    I setup a common directory under `/home` (`/home/common`) with `root:common` ownership and 775 permissions. I'd like the group to be set automatically to `common` whether I write the file or someone else does, so I think using `chmod -R 2775` would achieve that. Is there a way I can similarly automatically set the ownership to `root`? Or do I manually have to do that each time I add new files/directories?

    #AskFedi #Linux #Debian #Permissions

  32. Linux folks, question:

    I setup a common directory under `/home` (`/home/common`) with `root:common` ownership and 775 permissions. I'd like the group to be set automatically to `common` whether I write the file or someone else does, so I think using `chmod -R 2775` would achieve that. Is there a way I can similarly automatically set the ownership to `root`? Or do I manually have to do that each time I add new files/directories?

    #AskFedi #Linux #Debian #Permissions

  33. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  34. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  35. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  36. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  37. @Pawlicker About "reply gating": This, or something similar, has been a standard feature at least on Hubzilla, (streams) and Forte from the get-go, i.e. from their respective creation on. Hubzilla has had it since 2012. All three rely heavily on permissions for anything and everything. They can make themselves and each other hide the reply button. When someone wants to comment from Mastodon or something else that doesn't understand these permissions, these three simply reject unpermitted comments before they even reach the inbox.

    On Hubzilla, the channel-wide permission to comment also includes a permission to like or dislike something. I can generally allow
    • only myself
    • only certain contacts
    • only my contacts
    • only my contacts plus those with an unapproved contact request
    • anyone on the same Hubzilla hub as me
    • anyone on Hubzilla (strangely, this does exclude (streams) channels)
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account
    to comment on my posts.

    In addition, I can turn comments on and off for specific posts. Mind you, if it's a reply, it isn't a post, it's a comment, and I've got no control over it.

    On (streams) and Forte, the channel-wide permission to comment is uncoupled from the permission to like or dislike. The channel-wide options are
    • only myself plus certain contacts
    • only my contacts
    • anyone in the Fediverse
    • anyone anywhere on the Web, even without a Fediverse account

    On top of that, I can generally allow comments only for a certain number of days.

    Again, I can turn comments on and off for specific posts. But I can also only allow my contacts to comment on specific posts, and I can define until when comments are allowed on specific posts.

    In all three cases, I can even choose to preview technically unpermitted comments and then decide whether I allow or reject them, one by one.

    In other words, where I am (I'm commenting from Hubzilla), this not only has been available for longer than Mastodon has even existed, but it's deeply engrained into the culture.

    About "quote gating": Friendica, Hubzilla, (streams) and Forte have all always (in Friendica's case, since 2010) had both actual quotes like on bulletin-board forums (remember the 2000s when forums were all the rage?) and Twitter-quote-tweet-style quote-posts (which literally were the only way for them to share content before they adopted Twitter-retweet-style forwarding).

    The former obviously only works in comments. Whether or not it's allowed is defined by whether or not comments are allowed.

    The latter doesn't have any permission setting, not even on Hubzilla, (streams) and Forte with the most advanced permissions systems in the whole Fediverse. That's because their inventor says that it's technologically impossible to keep people from forwarding or sharing your content in separate posts.

    If you disallow actual quote-posts, people can still copy-paste the content of your post into a new post. Unlike when you're actually being quote-posted, you won't even notice unless they mention you. Mind you, while an estimated 60% of all Mastodon users are on iPhones, and another estimated 39% are on Android phones, 100% of all Hubzilla, (streams) and Forte users are on desktop or laptop computers where copy-paste is easy-peasy. It's pretty much impossible to disallow copy-paste, and even if it was, people would resort to screenshots.

    You don't want people to quote-post your stuff? Then don't make it public. Once it's public, it's out there, and anyone can do with it whatever they please.

    Nobody really misses an actual permission for quote-posts. That's also because Hubzilla, (streams) and Forte aren't primarily a home for Twitter refugees. In fact, neither of them can even understand the ruckus about quote-posts on Mastodon, and neither can Friendica users. Hardly any of them have been on Twitter at any point in the 2020s. There's no influence of Twitter culture anywhere to be found.

    The typical path into Hubzilla is not Twitter > Musk buys Twitter > Mastodon > Hubzilla. Not even Twitter > Musk buys Twitter > Mastodon > Friendica > Hubzilla. It's Facebook > diaspora* > Friendica > Hubzilla. Or Facebook > Google+ > diaspora* > Friendica > Hubzilla. The typical path into (streams) is the same, but one step further beyond Hubzilla. The typical path into Forte is the same as into (streams), but another step further beyond (streams).

    About the iPhone: Whether or not the iPhone is a status symbol depends on where you are.

    In the USA, the iPhone is the Levi's jeans of phones. It's the Ford F-150 of phones. The allegedly all-American American phone. Most importantly, it's what everyone has.

    Over here in Germany, the iPhone is the higher-class Mercedes-Benz of phones. The iPhone 15 Pro is the 2026 Mercedes-Benz-AMG E 53 of phones. The iPhone 15 Pro Max is the 2026 Mercedes-Benz-AMG S 63 E Performance of phones, slammed suspensions, standing on polished 22" Lexani wheels, muffler cut-outs always open. In American terms, it's the 2026 Cadillac Escalade-V of phones, gold-foiled, with air-ride, standing on gold-plated 26" Bellagio spinnaz. The phone made for peacocking in rap music video clips. It's the Rolex of phones. For women, it's the genuine Prada or Fendi or Louis Vuitton handbag of phones.

    Well, and then there's the iPhone 4S with the cracked screen. It's the 1995 Mercedes-Benz E-Class of phones. Old, worn out, four-banger engine, often rusty as hell, may have been stolen at some point, but it's cheap. And most importantly, it's still a Benz, and it's a real Benz as opposed to "Baby Benz" C-Class and smaller. The Benz for those who need a Benz to show their folks how much of a winner they are, but who can't really afford one.

    Over here, the Samsung Galaxy S is the VW Golf of phones. The Americans' Ford F-150 of phones. It's what everyone has. It's the no-brainer that you buy when you don't know what to buy, so you buy what everyone buys. Still, it's expensive for what it does. But all the other brands are akin to "cheap imports" from, what, France or Italy or Japan or Korea or Romania.

    The choice of the hardcore nerds in the homeland of Chaos Computer Club and Chaos Communication Congress is never something that can only run stock Android. It's an iPhone even less. They rather buy a Google Pixel, and the first thing they do is root it immediately and install GrapheneOS. Or if they refuse to buy something from Google and/or run a Google OS (de-Googled or not), they acquire a Sony Experia, root it and install SailfishOS. Or they go straight for a Fairphone or even the new Jolla Phone or something like that. I'm pretty sure many want a true successor to the Nokia N900.

    If Google locks Android down, these nerds won't flock to Apple. Some may switch to SailfishOS which, on officially supported phones, has the Aliendalvik compatibility layer for Android apps, but only with F-Droid and neither with the Google Play Store proper nor with Micro-G. Many more will go entirely elsewhere like PostmarketOS or PureOS, also seeing as SailfishOS is payware that's half proprietary and closed-source. Or they'll forgo mobile phones entirely or keep old phones alive for as long as they can.

    About iOS apps: I guess the notion that the Fediverse equals Mastodon, something that the majorty of Mastodon users believe, is particularly wide-spread among iPhone users. And if it isn't only Mastodon, it doesn't extend beyond Mastodon, Pixelfed and PeerTube. Excluding Pixelfed and PeerTube, if Mastodon can't do it, the Fediverse as a whole can't. I mean, on top of the fact that apps made for Mastodon generally only support Mastodon features because the Mastodon Client API only supports Mastodon features, and the Mastodon Client API is all that these apps understand.

    It's particularly bad for Friendica users. If they're on Android, they may opt for a Mastodon app. There are several Android apps for Mastodon that have been reported to work with Friendica. Or they may want to try one of the dedicated Friendica apps which are at various levels of unfinished. Or they may choose the middle-ground and use Fedilab.

    But if they're on an iPhone, they'll discover that literally not even a single Mastodon iOS app works with Friendica. There is no Fedilab. And the iOS version of RaccoonForFriendica requires Test Flight, and it's probably even more incomplete than the Android version.

    In general, iPhone apps are rarely developed for the same reasons as Android apps. Most Android Fediverse apps are open-source and under a free license, and they're also or exclusively available on F-Droid. They're developed by FLOSS enthusiasts/idealists. However, these people don't develop for iOS. That's because the Apple App Store is inherently hostile towards free software, and it's completely incompatible with all versions of the GNU General Public License.

    Also, as you've already pointed out, you absolutely need a Mac to develop iOS apps. But if someone releases FLOSS apps on F-Droid, you can bet they're running GNU/Linux at home (more often Arch or a derivative than you may think), and they won't touch any corporate-made, closed-source OS with a 10-foot barge pole. They may even steer clear of anything where Novell, Red Hat or Canonical is involved.

    With hobbyist FLOSS enthusiasts out of the way of developing iPhone apps, this is only ever done by those who do it for money. Or fame and social status (same reason why they always have a fairly new iPhone). Or both. But then they discovered that the Fediverse, to them at least, is a hive of radical leftist tech nerds whom you can't impress with expensive bling-bling from big American gigacorps. They failed to gather the umpteen thousand followers they wanted. So they left for greener pastures: Bluesky. Or they even went back to their hundreds of thousands of followers on 𝕏. Doing so, they also abandoned their iPhone app development.

    By the way, none of this affects Hubzilla, (streams) and Forte. For starters, just like Friendica, all four can be installed as Progressive Web Apps. However, at least in the case of these three, there is no alternative to the Web interface whatsoever. There's an old Android app for Hubzilla named Nomad, but it's only available on F-Droid, it hasn't been worked on since December, 2019, it only runs on older Android versions and Aliendalvik, and it's only a wrapper for the Web interface anyway. For (streams) and Forte, there's zilch.

    There has been some talk about developing a native mobile Hubzilla app. It's kind of difficult, though. Generally, Hubzilla users use Hubzilla on desktop OS's. They can't imagine people daily-driving phones as their main or only end-user devices, so they think that a Hubzilla app only needs the features one would need when out and about because everyone will go back to their desktop or laptop computers anyway when they're back home.

    In reality, many users of the Hubzilla app will only use that app. They won't use Hubzilla's Web interface in a browser. They won't use it on a desktop or laptop computer either, usually because they simply don't have one. They'll resort to that app for everything. In fact, they'll perceive Hubzilla as a phone app rather than a Fediverse server application. This means that a Hubzilla mobile app will inevitably have to cover all of Hubzilla's features except those that really don't make sense in a phone app (e.g. the PDL editor). But a fully-featured Hubzilla app would be so complex, it'd make infamous K-9 Mail pale in comparison.

    Licensing is the least problem here. Hubzilla and Forte are released under the MIT license, (streams) was released into the public domain. So I guess putting an app for either of them under the MIT license would be an option, one that's fairly compatible with the Apple App Store even. It's just that this app would be bound to be an absolute monster.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Friendica #Hubzilla #Streams #(streams) #Forte #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #QuotePostDebate #QuoteTootDebate #ReplyControl #Permissions #MastodonApp #MastodonApps #FediverseApp #FediverseApps #iOS #iOSApp #iOSApps #iPhone #iPhoneApp #iPhoneApps #Android #AndroidApp #AndroidApps
  38. CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  39. CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  40. CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  41. CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  42. CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
  43. Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.

    Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.

    But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.

    And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.

    And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".

    These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.

    But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.

    #marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code

  44. Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.

    Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.

    But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.

    And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.

    And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".

    These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.

    But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.

    #marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code

  45. Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.

    Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.

    But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.

    And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.

    And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".

    These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.

    But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.

    #marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code

  46. Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.

    Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.

    But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.

    And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.

    And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".

    These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.

    But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.

    #marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code

  47. Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.

    Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.

    But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.

    And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.

    And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".

    These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.

    But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.

    #marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code

  48. But wait, there's more: Even if a Hubzilla channel, upon confirming your follow request, "follows" you back, it doesn't necessarily actually follow you back, as in, let your toots and boosts in.

    Chances are that the Hubzilla channel uses its permissions system to keep your toots and boosts out. Replies are allowed. DMs are allowed. But anything that isn't either is kept out.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #Contacts
  49. But wait, there's more: Even if a Hubzilla channel, upon confirming your follow request, "follows" you back, it doesn't necessarily actually follow you back, as in, let your toots and boosts in.

    Chances are that the Hubzilla channel uses its permissions system to keep your toots and boosts out. Replies are allowed. DMs are allowed. But anything that isn't either is kept out.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #Contacts
  50. But wait, there's more: Even if a Hubzilla channel, upon confirming your follow request, "follows" you back, it doesn't necessarily actually follow you back, as in, let your toots and boosts in.

    Chances are that the Hubzilla channel uses its permissions system to keep your toots and boosts out. Replies are allowed. DMs are allowed. But anything that isn't either is kept out.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #Contacts
  51. But wait, there's more: Even if a Hubzilla channel, upon confirming your follow request, "follows" you back, it doesn't necessarily actually follow you back, as in, let your toots and boosts in.

    Chances are that the Hubzilla channel uses its permissions system to keep your toots and boosts out. Replies are allowed. DMs are allowed. But anything that isn't either is kept out.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #Contacts