Notices tagged with activitypub
-
#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 -
AndStatus v.55.01 Beta with "ActivityPub Client to Server improvements". Download from: https://github.com/andstatus/andstatus/issues/456 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 A…
-
@sl #Mastodon version 3.x and later (and #Pleroma version 2.x and later) does not use #OStatus as a federation protocol, so they broke federation with #GNUSocial. There's a little more work to do before the release of GS v.2.0, which adds #ActivityPub support.
-
@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...
@colegota @xrevan86 -
@roka It works!
Thank you for noticing #ActivityPub support. -
@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 -
Testing group name autocompletion in #GnuSocial using #AndStatus
!gnusocial
It works already.
Not very impressive yet, because there is NO WAY (yet?!) to get actual metadata for remote groups (actual unique ID, avatar ...)
But adding internal app's infrastructure for Groups support is much more important. It could be used e.g. in #ActivityPub
Where are you, #ActivityPub #C2S (client to server protocol) developers?
@kaniini @lanodan@queer.hacktivis.me @xrevan86 https://loadaverage.org/attachment/5792570 -
On adding Group / List support to #AndStatus
Oh, I see that #GNUSocial development is going on: https://notabug.org/diogo/gnu-social
#ActivityPub Server-to-Server support is being added (and I saw a report that it was successfully tested some days ago...)
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...
So I'm moving on adding Group support to #AndStatus (whatever it will be actually...) https://loadaverage.org/attachment/5785458 -
And now in v.52.01I successfully sent and received two images via #ActivityPub #C2S thanks to @lanodan
@AndStatus@queer.hacktivis.me https://loadaverage.org/attachment/5768075 -
@rmbl Oh, I see that I was confused a bit about terminology. The "Group" notion in #ActivityPub is about a group of Actors (people etc.), but we are talking here about a named "Collection" of notes/activities.
But actually GNU Social calls such collections "Groups" :-)
I'm creating descriptions and comparisons of Groups/Lists notions in different types of social networks, supported by #AndStatus, here: https://github.com/andstatus/andstatus/issues/248#issuecomment-219826572
No, I don't use IRC. That way of communication is in another Universe for me :-) -
@rmbl Oh, I see that I was confused a bit about terminology. The "Group" notion in #ActivityPub is about a group of Actors (people etc.), but we are talking here about a named "Collection" of notes/activities.
But actually GNU Social calls such collections "Groups" :-)
I'm creating descriptions and comparisons of Groups/Lists notions in different types of social networks, supported by #AndStatus, here: https://github.com/andstatus/andstatus/issues/248#issuecomment-219826572
No, I don't use IRC. That way of communication is in another Universe for me :-) -
@rmbl Sometimes I need the same, and I also feel that it is inconvenient to keep "unread" all notifications in order not to forget one of them.
Recently I started implementation of Group/Lists support in #AndStatus. And I see that creation of some personal "ToDo" group and adding any note/ activity to that group could help in such cases. Unfortunately AFAIK only #ActivityPub supports such actions, meaning that such custom groups of notes could be automatically synced between User's devices or even shared... Moreover, each "Social network" in #AndStatus logically should have its own group...
So it seems that I will start from some device-local groups (like tags...) that can be easily viewed...
@fedilab -
@rmbl Sometimes I need the same, and I also feel that it is inconvenient to keep "unread" all notifications in order not to forget one of them.
Recently I started implementation of Group/Lists support in #AndStatus. And I see that creation of some personal "ToDo" group and adding any note/ activity to that group could help in such cases. Unfortunately AFAIK only #ActivityPub supports such actions, meaning that such custom groups of notes could be automatically synced between User's devices or even shared... Moreover, each "Social network" in #AndStatus logically should have its own group...
So it seems that I will start from some device-local groups (like tags...) that can be easily viewed...
@fedilab -
@moonman There are two dimentions in the support of different protocols of Social networks, which I'm facing during development :
1. Implementation of different API calls and parsing responses of every API of every supported protocol.
I cope with this problem simply by implementing only some of available APIs (features)...
2. Trying to adapt internal data/actions model so that it could fit into conceptual differencies of different systems. This is a lot more time consuming and difficult to do right. In #AndStatus we started ten years ago with Twitter-like model. For the last two years I'm gradually converting it into #ActivityPub based model...
@astheroth @dragnucs -
@FuzboleroXV I think that #NomadicIdentity is primarily about moving your identity _between_ accounts and corresponding hosts/providers. Being able to access several "nomadic identities" via one account is a byproduct for me, not so important.
Main point here though is separation between a User (person or organization...), an Account and the "identity" (called an Actor in #ActivityPub). -
@colegota In short: Notifications section in #AndStatus settings lists some other things; not timelines.
Longer answer:
"Unread notifications" timeline includes activities: "create(post) note", "announce (retweet/repost/reblog) note", etc. which were recognized by AndStatus app as belonging to at least one of checked "Notification event types". No matter how the activity was received for some of them (e.g. for mentions)
but one-to-one for others: "Home timeline" notification corresponds to the Home API timeline for all Twitter-like APIs (i.e. Twitter, GNU Social and Mastodon) and Inbox API timeline for #ActivityPub client to server API.
Meaning of some AndStatus Timelines are changing over time. E.g. even for me it's unclear yet, if "Unread notifications" timeline notifies "the account" (as it was implemented quite long ago) or it should rather notify My Actor who happens to be linked to an account on some server... I clarify this for myself also, and make corresponding changes in the app... -
@mariusor Yes, I'm dreaming about real #ActivityPub service including Client to Server protocol.
And this already comes true step by step, see https://github.com/andstatus/andstatus/issues/499 and my posts via ActivityPub C2S https://pleroma.site/users/AndStatus
The real power for a User comes with several accounts at different servers.
@SubwayTooter @tom79@mastodon.social @kaniini @AndStatus -
@mariusor Yes, I'm dreaming about real #ActivityPub service including Client to Server protocol.
And this already comes true step by step, see https://github.com/andstatus/andstatus/issues/499 and my posts via ActivityPub C2S https://pleroma.site/users/AndStatus
The real power for a User comes with several accounts at different servers.
@SubwayTooter @tom79@mastodon.social @kaniini @AndStatus -
@dansup Last summer I hoped that #ActivityPub Client to Server API for GGU Social will be created. But this didn't happen, unfortunately...
BTW The work on the #AndStatus client side is going on, testing with #Pleroma only so far, see https://github.com/andstatus/andstatus/issues/499
@up201705417@loadaverage.org @sim @dude @lnxw37a2 @alcinnz @lain @xrevan86 -
@dansup Last summer I hoped that #ActivityPub Client to Server API for GG& Social will be created. But this didn't happen, unfortunately...
BTW The work on the #AndStatus client side is going on, testing with #Pleroma only so far, see https://github.com/andstatus/andstatus/issues/499
@up201705417@loadaverage.org @sim @dude @lnxw37a2 @alcinnz @lain @xrevan86 -
@FuzboleroXV I think that #NomadicIdentity is primarily about moving your identity _between_ accounts and corresponding hosts/providers. Being able to access several "nomadic identities" via one account is a byproduct for me, not so important.
Main point here though is separation between a User (person or organization...), an Account and the "identity" (called an Actor in #ActivityPub). -
@tom79 This is about testing #friendica instance using #ActivityPub Client to Server protocol of #AndStatus https://github.com/andstatus/andstatus/issues/499
The error occurs during client registration.
Actually I don't even know if Friendica supports this at all:-)
@z428 -
@z428 As you may see from the discussion it the GitHub issue, the first and maybe the most undefined step in the #ActivityPub #C2S specification is authentication and whoami (account verification/discovery) steps. We agreed on concrete steps and endpoints with pleroma.site developer, but the same probably won't work out of the box with other systems.
Anyway, I'm open to collaboration and aim at creation of really unified API, compliant with ActivityPub C2S. -
@z428 As you may see from the discussion it the GitHub issue, the first and maybe the most undefined step in the #ActivityPub #C2S specification is authentication and whoami (account verification/discovery) steps. We agreed on concrete steps and endpoints with pleroma.site developer, but the same probably won't work out of the box with other systems.
Anyway, I'm open to collaboration and aim at creation of really unified API, compliant with ActivityPub C2S. -
@lanodan @amiloradovsky @kit_ty_kate Yes, #AndStatus really has minimal #ActivityPub Client-to-Server implementation that works with pleroma.site. You can even play with this...
For more details, including current state of this implementation and problems/questions please see https://github.com/andstatus/andstatus/issues/499
@kaniini https://loadaverage.org/attachment/5083546 -
@emacsen I mentioned WebFingerId not as a part of WebFinger protocol, but only as an artificially created identifier, helping to figure out the same actors via old-style (Twitter-like...) client APIs (which don't provide globally unique identifiers of actors (users...)).
As we're currently are figuring out, how to use #ActivityPub C2S protocol in the real world :-) I see that WebfingerId isn't really needed in ActivityPub API: Actor's profile has enough information to know both username and hostname of an actor (what constitutes WebFingerId).
I think that you will be interested to read our discussion on this here: https://github.com/andstatus/andstatus/issues/499
@cwebber @thefaico @eliotberriot -
@emacsen I mentioned WebFingerId not as a part of WebFinger protocol, but only as an artificially created identifier, helping to figure out the same actors via old-style (Twitter-like...) client APIs (which don't provide globally unique identifiers of actors (users...)).
As we're currently are figuring out, how to use #ActivityPub C2S protocol in the real world :-) I see that WebfingerId isn't really needed in ActivityPub API: Actor's profile has enough information to know both username and hostname of an actor (what constitutes WebFingerId).
I think that you will be interested to read our discussion on this here: https://github.com/andstatus/andstatus/issues/499
@cwebber @thefaico @eliotberriot -
@cwebber Don't worry, I'm on the team that thinks #ActivityPub should NOT have private messages! .D
-
I made the simplest implementation of #ActivityPub C2S protocol in #AndStatus, allowing me to log into pleroma.site, read home timeline and get other user's info (i.e. read the Actor's profile based on his "id").
But I've got an error response from pleroma.site server on an attempt to send a Note, so I created another bug report in pleroma issues tracker: https://git.pleroma.social/pleroma/pleroma/issues/650
Alpha build of AndStatus is attached to this comment: https://github.com/andstatus/andstatus/issues/499#issue-389014088 , source code is available in the repository. https://loadaverage.org/attachment/5020018
