@licho #Mastodon 3.x and #Pleroma 2x no longer speak the #OStatus federation protocol. !GNUsocial 2.0 will add the #ActivityPub federation protocol, so ask your admin to be ready to upgrade soon.
@diogo Thank you for your explanation. Now I really see a page on the loadaverage site that tells its server version. And #AndStatus still successfully connects to the server (I'm writing to you using it). This means that the authentication problem that I reported is caused by a configuration of a concrete server, and not by the latest version of #GnuSocial :-)
Using a chance to talk with you, I hope that you will find time for Client-to-Server #ActivityPub API also. I'm extending support of that API in AndStatus, and already see that not only #Pleroma, but even some #Mastodon sites begin to implement some parts of the API, allowing a Client app to request information directly from its sources, without a need to duplicate it. E.g. Notes by an Actor may be requested from the Actor's profile (from the Actor's outbox) at his site, and not from the server, at which the User of the Client app has an account...
If I get TME* this week, I'll set up a #Friendica instance for !fnetworks ... membership is only available to people with currently active Federati accounts.
I was going to set up #Pleroma, but the PleromaFE interface has too much #JavaScript / #JabbaShit piled up ... It causes my browsers to repeatedly pop up warnings about a hung script.
@coolboymew I heard recently that #AndStatus doesn't work properly with Pleroma as with "Mastodon type" social network. Didn't investigate this... But since last year #Pleroma is adding #ActivityPub #C2S (Client to Server) interface, and AndStatus has basic support for this type, checked and tested with Pleroma team! See https://github.com/andstatus/andstatus/issues/499 @dielan @thefaico@quitter.se
@dude Hmm. This complicates the plan to add a #Pleroma instance for !FNetworks before we upgrade to !gnusocial 2.0. I'm not really interested in hosting incompatible services (one reason why planned #Diaspora and #Pump.io instances were abandoned).
@guizzy It's the way all these things work. I've seen loads of resurrected threads on #Pleroma and #Mastodon as well as #GNUSocial when someone deletes their account. Their home instance sends out deletes for every individual post they ever made, which modifies the conversations those posts were part of.
@tom79 I think user's confusion is caused by widely advertised "#ActivityPub support", which in reality for almost all servers (except for #Pleroma, as I know) means server to server communication only. Pleroma is the first Social Network that implemented at least minimal set of features, allowing ActivityPub Client applications to connect to it. @z428 @thefaico
@nepfag @moonman @ayy that’s actually a good solution for FreezePeach and SeaLion, if there were active users left. Put up a #Pleroma in a subdomain and ask interested users to create their accounts from scratch.
In the meantime, maybe campaign for missing features, such as groups, or a more Twitter-like front end, to be added.
@lanodan It's OK for #Mastodon and #Pleroma to use in their UI "summary" property only. Especially taking into account that Mastodon actually doesn't have Title/Subject of a "toot" but "CW" only (Content Warning) that fits into semantics of #ActivityPub's "summary" better than into "name". Above decision shouldn't influence the "name" property, one of basic properties of #ActivityPub vocabulary.
Regarding current usage: Pump.io uses both "name" and "summary" properties since its creation in 2013, and they live together without problems.