@arlon@capirock#GTS suporta MarkDown, #Friendica suporta também [#ironia e olha que não é um sistema maduro 😄], #Hubzilla também! Mastodon (a menina dos olhos do fediverso) será um dos últimos a suportar esse característica 😄
O ideal é você testar os dois! O #Friendica como disse @veroandi é mais direto ao ponto, mais simples sem ser capado (não tem limite de caracteres, por exemplo) ele só não suporta (e não sinto falta) enquetes (fazer e responder)...
Hey, pessoal que entende português. Este aqui é um apelo sério - há mais de um ano entrei cm tudo no #Fediverse, e do meu modo de usar a internet como sempre, fui testando tudo o que podia: softwares, pontes, app de 3o .#mastodon#lemmy#bluesky#akkoma#piefed#Pixelfed#Friendica ... Etc, etc, etc ... Estou precisando de alguém que me ajude a terminar as configurações da instância #Friendica my-placesocial e tenho ainda questões de interoperabilidade que não tenho como resolver sozinho. Não sou programador e não sei usar o Github. Alguém poderia me ajudar? Podemos combinar um valor legal pra ambos! Gosto muito do fediverso . Espero tocar alguém 🙃
6 out of 9 implementations accept any @context value. But Mastodon, Hollo and Friendica reject activity entirely if https://www.w3.org/ns/activitystreams is not included in @context. Mastodon probably does this for no reason, but what about #Friendica and #Hollo?
I know a lot of you still think of the #Fediverse as just “Mastodon”.
But it’s far more than that. There’s an entire ecosystem of federated message boards that’s already proven popular: #Piefed, #NodeBB, #Lemmy, #Mbin, and #Discourse.
Even the classics like #Friendica and #Hubzilla have solid forum features baked in.
If you’re only here for the microblogging, you’re missing a key piece. Communities built around interests are something #Twitter never offered, and #Bluesky still doesn’t.
So if you’re looking to replace your #Facebook Groups, the Fediverse already has you covered.
They're those who either are commercial or looking for professional/commercial users or both. Flipboard. Automattic (WordPress). Ghost. These kinds.
They know themselves. They know each other. And they know Mastodon. And that's it.
None of them has ever heard of Pleroma or Akkoma.
None of them has ever heard of Misskey or the Forkeys.
None of them has ever heard of Mitra.
None of them has ever heard of GoToSocial.
None of them has ever heard of Hollo.
None of them has ever heard of Friendica, Hubzilla, (streams) or Forte, even though Friendica and Hubzilla are both older than Mastodon. And apparently, neither has @Helge. But then again, Friendica and its nomadic, security-enhanced descendants are being overlooked by almost everyone. That's why there's always on-going work for features to be "introduced to the Fediverse" which Friendica has had for a decade and a half.
Granted, the HTML support on Friendica, Hubzilla, (streams) and Forte can be summarised with "yes". But elaborate tables that show what either of them supports how would be very useful.
Also, granted, everything I've mentioned above (normally) uses something else than HTML for formatting in the frontend. For example, Misskey and all Forkeys use MFM ("Misskey-Flavoured Markdown"). Friendica uses extended BBcode with the option to use Markdown instead. Hubzilla uses even more extended BBcode. (streams) and Forte can use the same even more extended BBcode and Markdown and HTML at the same time within the same post, although not all markup languages support all features.
@tiagojferreira o fato dele ser um cliente genérico para activitypub talvez explique que ele não seja otimizado para o mastodon, em específico. Para o #Friendica, eu me acostumei bem a interface do mesmo, embora não seja meu cliente mobile predileto.
@Strypey The main reason devs haven't wanted to use the C2S API in the AP spec is network effect. Clients devs don't want to use it because Mastodon doesn't, and servers devs don't want to use it because their services wouldn't work with all the clients following the Mastodon API. It's actually tempting to imagine a vicious circle here: If almost everything has the Mastodon client API implemented, it isn't worth developing dedicated client apps that also cover other servers' extra features.
Instead, the reason why all kinds of server applications have the Mastodon client API implemented is because they absolutely need some phone apps that work with them. Just look around the Fediverse. Almost everyone is exclusively on phones nowadays. And especially iPhone users wouldn't touch a Web browser with a 10-foot barge pole if they don't absolutely have to, so expecting them to use the Web UI means you're stuck in a bubble or a time where smartphones are still a gimmick.
That's why even Friendica has implemented the Mastodon client API. I mean, Mastodon and Friendica are very different, and the Mastodon client API only covers a small fraction of what Friendica can do. It actually doesn't cover some critical everyday features.
At the same time, there's little to no incentive for those who can develop mobile apps to make apps for anything that isn't Mastodon. Many start working on Fediverse apps at a point when they still believe the Fediverse is only Mastodon. Or if they don't, at least they've never heard of Pleroma and its family, Misskey and its family, Friendica and its family (where Hubzilla would require a wholly different app than Friendica, and (streams) and Forte would require a wholly different app than both) etc. Or they genuinely think that developing the umpteenth iPhone app for Mastodon is worth the effort more than developing the first stable dedicated iPhone app for Friendica. It's a miracle that stuff like Aria for the *key family exists.
It seems like of all the server apps that don't do *blogging (purist long-form blogging stuff like WriteFreely excluded), Hubzilla, (streams) and Forte are the only ones that don't have the Mastodon client API implemented. And I can't see them do it. For one, their devs steer clear of all proprietary, non-standard Mastodon technology. But other than that, these three are even less like Mastodon than Friendica, and they work even less like Mastodon. Even using a Mastodon app for stuff like basic posting is out of question because it pretty much requires access to the per-post permission settings, something that Mastodon doesn't have implemented, and therefore, neither do the apps for it.
Now, Hubzilla, (streams) and Forte can be installed as so-called Progressive Web Apps. But only Hubzilla veterans ever do that, and that's for three reasons: One, next to nobody has ever heard of the very concept of PWAs. Two, all that people know is installing apps from the Apple App Store and the Google Play Store. And three, people want native mobile interfaces in the style of whatever phone they use. It doesn't matter how well the Web UIs of these three adapt to mobile screens, especially since 90% of all phone users have totally forgotten that you can rotate a phone sideways.
Hubzilla actually has its own client API, and I think (streams) and forte have their own one, too. But nobody has ever even only tried to build a native mobile app for either of them. Hubzilla's devs even have to admit that they don't know how well Hubzilla's client API works because there has literally never been a sufficiently-featured counterpart to test it against. All there is is an extremely basic Android app built by one of them that's available as a download somewhere, and all it can do is send very basic posts, I think, even only at your default settings. It's just a proof of concept.
@admins@developers@helpers What is the consensus on adding relays in #friendica, do they actually help #federation, do they reduce it, speed it up, slow it down, increase it, as a concept I understand it as say #hamradio relays, it allows your reach to go further, but since my instance is federated, how much further do relays actually deliver my posts, and again does it actually help to have them? I have tried a few, with mixed results and I am rather baffled by their existence and usability in relation to my instance, any clear answers would be appreciated.
Embed this noticetux (tux@anonsys.net)'s status on Monday, 23-Jun-2025 15:40:55 JST
tuxAnkündigung bzgl. Neuregistrierungen auf anonsys.net: Lange habe ich mich dagegen gewährt, aber die Spamanmeldungen hier auf dieser Instanz nehmen in letzter Zeit immer mehr zu. Auffälligerweise habe zum größten Teil dieser Spamregistrierungen eine Mailadresse von Google. Aus diesem Grund habe ich mich letztendlich doch entschlossen, für anonsys.net Mailadressen von gmail für die Registrierung zu schließen bzw. zu verweigern. Diese Maßnahme greift ab sofort. Sorry Leute, aber mir ist meine Zeit zu schade, um den ganzen Schrott manuell zu pflegen. #anonsys.net#Friendica#Fediverse#Google#gmail
Today marks a really special occasion: I’ll be speaking at #JDLL in Lyon as part of the #YunoHost presentation… discussing how I use their amazing #selfhosting tools for #DigitalSovereignty.