#AndStatus v.56.09 (326) released. "Show numbers of likes, replies and reblogs for a Note 1. Show numbers of likes, replies and reblogs for Mastodon; likes and retweets for Twitter. Added similar to #ActivityPub #C2S, hope the same counters will be supported there also. 2. Added Actors's name ("Real name") as a separate field to Actor's profile. Created landscape layout for Actor's profile. https://loadaverage.org/attachment/5933715
https://github.com/friendica/friendica/issues/8642 #Friendica Someone that is familiar with #Diaspora is writing a new socnet based on #ActivityPub, wishes to change other #Fediverse software to follow Diaspora's model (viewer's server hijacks hashtags so the #hashtag search points to the viewer's home server, not the original poster's home server). The model that has been followed by almost all federated socnets for over a decade is that hashtag search links are inserted by the poster's server and point back there.
IMO, a remote server changing the links is sketchy as heck*, but if they added local hashtag links in a separate area outside the post itself, that's acceptable. Or if they followed the #Pump.io idea of keeping hashtags completely separate from the basic server, then an external server (e.g. ragtag\.io) would be called to index and link the tag during the posting process, and searches would be performed based on results from the tag server.
Anyway, I can't be bothered logging into Github to comment, but maybe @heluecht and other Friendica devs will see this and take this into consideration.
* Remote servers editing the contents of one's posts is about as sketchy as it gets. There are rare occasions where that may be acceptable (i.e., to insert NSFW tags / image hiding on posts from instances where untagged NSFW content originates), but editing content to hijack hashtag search is about as questionable as one could get.
1. This release was focused on supporting new and improved #ActivityPub features that appeared both in #Pleroma and, surprisingly, in #Mastodon also. You can really start experimenting with ActivityPub social network type if you have an account at Pleroma site with latest v.2.x Pleroma builds... Posting with image attachments works.
2. Mastodon (not AndStatus!) doesn't give you enough features to switch client connection to ActivityPub simply because Home timeline and posting via ActivityPub connection is not supported yet (corresponding pages give 404 Not found error). But you can see our own posts on Mastodon servers and navigate to other Actors and their post via them (you can see profiles of other Actors and see their posts...). You can even play with Mastodon as an "ActivityPub" type Social network in AndStatus today! But prepare to see empty Home timeline and to be read-only there for now. Switch to "Sent" timeline and see your Actor's posts, see other actors and their posts similarly... These new Mastodon improvements make me very optimistic about the future of ActivityPub in client apps across all server platforms.
3. Some important fixes, including more Avatars and Images will be shown.
4. More convenience for developers. Logging of network level messages (including response headers) improved. Even file names with responses are much clearer now, e.g. 2020-04-25-03-34-51-663_social.tulsa.ok.us-oauth_register_client_response.json or 2020-04-25-03-35-02-235_mastodon.technology-get_actor_response.json (real names from my log). Remember that logs are stored for 10 days and can be optionally included in a Backup!
@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...
@strypey @clacke #ActivityPub support is already in the #GNU_Social (2.0.0-dev) codebase that many instances currently use, it just isn't working so well (from what I can tell, Mastodon signatures don't verify). They're working on fixing that
I thought #OCAP was going to save us from ourselves and the non-private no-security* protocol that #ActivityPub turned out to be. I feel like I did when I discovered that there was no Santa Claus.
* There's optional easily subverted stuff like HTTP Signatures, but nothing in the core of AP.
@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
Moreover, looking into the source code I found the first-hand info about the system's API . And although the code, related to Groups support, didn't change for the last six years :-) https://notabug.org/diogo/gnu-social/src/nightly/actions/apitimelinegroup.php , it works and I could actually retrieve the group's timeline at loadaverage.org
The unusual "!groupname" syntax to address a group is not a big problem...
We just turned on ActivityPub support at socialhome.network to get more users to test it and thus speed up fixing the remaining issues and bringing better compatibility across other #Fediverse platforms.
PLEASE NOTE, this are a bit alpha still, so in the master branch by default ActivityPub support is off. It can be turned on by setting the environment variable SOCIALHOME_ACTIVITYPUB_ALPHA=True.
1. SharedInbox is dead (look out for MultiBox and OcapsPub)
2. Strong interest to explore Object Capabilities as a way to secure social introductions, power delegation and transitivity, and to develop effective cooperation tools that prevent abuse in the #Fediverse