Updates tagged with activitypub on Rainbow Dash Network!
andstatus: #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's status on Saturday, 23-May-20 15:17:50 UTC
#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: 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 https://loadaverage.org/notice/19107669
andstatus's status on Sunday, 26-Apr-20 10:18:21 UTC
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…
lnxw37a1: @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.
lnxw37a1's status on Monday, 13-Apr-20 17:49:33 UTC
@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.
andstatus: @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
andstatus's status on Monday, 06-Apr-20 16:24:35 UTC
@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
andstatus: @roka It works! Thank you for noticing #ActivityPub support.
andstatus's status on Thursday, 26-Mar-20 18:00:00 UTC
@roka It works! Thank you for noticing #ActivityPub support.
andstatus: @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
andstatus's status on Tuesday, 04-Feb-20 05:41:27 UTC
@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
andstatus: 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
andstatus's status on Thursday, 05-Dec-19 16:52:04 UTC
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
andstatus: 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
andstatus's status on Thursday, 28-Nov-19 14:36:19 UTC
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
andstatus: 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
andstatus's status on Sunday, 10-Nov-19 15:34:06 UTC
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
rozzin: #ActivityPub dev calls me "tonedeaf" when I ask if #Mastodon's scoping or takedowns amount to #DRM, then goes on to refer to relatively trivial crap like "people on the Internet retelling stories that someone wishes he could just un-post" as "#nazis burning people". #irony #sigh
rozzin's status on Saturday, 19-Oct-19 05:43:15 UTC
#ActivityPub dev calls me "tonedeaf" when I ask if #Mastodon's scoping or takedowns amount to #DRM, then goes on to refer to relatively trivial crap like "people on the Internet retelling stories that someone wishes he could just un-post" as "#nazis burning people". #irony #sigh
andstatus: RT @andstatus @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 :-)
andstatus's status on Wednesday, 14-Aug-19 12:12:14 UTC
RT @andstatus @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 :-)
andstatus: @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 :-)
andstatus's status on Wednesday, 14-Aug-19 05:32:45 UTC
@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 :-)
andstatus: RT @andstatus @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
andstatus's status on Monday, 12-Aug-19 19:47:21 UTC
RT @andstatus @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
andstatus: @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
andstatus's status on Monday, 12-Aug-19 18:17:03 UTC
@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
andstatus: @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
andstatus's status on Thursday, 01-Aug-19 05:57:53 UTC
@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
andstatus: RT @andstatus @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 @danie10 @dansup @ConnyDuck @Gargron
andstatus's status on Tuesday, 25-Jun-19 19:48:13 UTC
RT @andstatus @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 @danie10 @dansup @ConnyDuck @Gargron
andstatus: @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...
andstatus's status on Tuesday, 18-Jun-19 13:45:55 UTC
@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...
andstatus: RT @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 @kaniini @AndStatus
andstatus's status on Monday, 03-Jun-19 09:33:24 UTC
RT @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 @kaniini @AndStatus
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/AndStatusThe real power for a User comes with several accounts at different servers.@SubwayTooter @tom79@mastodon.social @kaniini @AndStatus
andstatus's status on Saturday, 01-Jun-19 18:28:48 UTC
@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
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
andstatus's status on Monday, 20-May-19 15:36:01 UTC
@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
andstatus: @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
andstatus's status on Monday, 20-May-19 15:35:10 UTC
@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
andstatus: @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 @danie10 @dansup @ConnyDuck @Gargron
andstatus's status on Monday, 15-Apr-19 16:02:16 UTC
@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 @danie10 @dansup @ConnyDuck @Gargron
andstatus: @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
andstatus's status on Tuesday, 02-Apr-19 17:43:59 UTC
@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
andstatus: RT @andstatus @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.
andstatus's status on Thursday, 21-Mar-19 15:58:12 UTC
RT @andstatus @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.
andstatus: @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.
andstatus's status on Thursday, 21-Mar-19 15:50:01 UTC
@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.
andstatus: @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
andstatus's status on Sunday, 10-Mar-19 18:28:43 UTC
@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
andstatus: RT @yvolk @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
andstatus's status on Friday, 22-Feb-19 02:50:32 UTC
RT @yvolk @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
yvolk: @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
yvolk's status on Thursday, 21-Feb-19 18:33:46 UTC
@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
mmn: @cwebber Don't worry, I'm on the team that thinks #ActivityPub should NOT have private messages! .D
mmn's status on Monday, 18-Feb-19 18:54:02 UTC
@cwebber Don't worry, I'm on the team that thinks #ActivityPub should NOT have private messages! .D
andstatus: 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
andstatus's status on Sunday, 17-Feb-19 15:34:05 UTC
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
andstatus: @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.
andstatus's status on Thursday, 14-Feb-19 06:15:38 UTC
@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.
andstatus: Discussion of the #ActivityPub Note's "name" property usage and it's processing by Pleroma. Main attention is on the Client to Server interactions that are being implemented in #AndStatus. I feel that we mixing two different use cases here: 1. An ActivityPub property, to which a Note's Subject/Title is placed, when entered via Pleroma web UI. I understood about this point. 2. Delivery / sending to other servers a Note, which came from a client application or from another server and which has the "name" property. I assume that if incoming Note has the "name" property, Pleroma doesn't delete that property, but sends it to recipients with the same value. ?! https://git.pleroma.social/pleroma/pleroma/issues/635
andstatus's status on Thursday, 14-Feb-19 05:40:18 UTC
Discussion of the #ActivityPub Note's "name" property usage and it's processing by Pleroma. Main attention is on the Client to Server interactions that are being implemented in #AndStatus. I feel that we mixing two different use cases here: 1. An ActivityPub property, to which a Note's Subject/Title is placed, when entered via Pleroma web UI. I understood about this point. 2. Delivery / sending to other servers a Note, which came from a client application or from another server and which has the "name" property. I assume that if incoming Note has the "name" property, Pleroma doesn't delete that property, but sends it to recipients with the same value. ?! https://git.pleroma.social/pleroma/pleroma/issues/635
andstatus: @rysiek Maybe it's the right time to start building (or completing implementation of) #ActivityPub compatible client to server API and not waste time on improvements of Mastodon's custom API ?! @dfeyer @kaniini @maryjane
andstatus's status on Thursday, 31-Jan-19 15:59:37 UTC
@rysiek Maybe it's the right time to start building (or completing implementation of) #ActivityPub compatible client to server API and not waste time on improvements of Mastodon's custom API ?! @dfeyer @kaniini @maryjane
andstatus: @kaniini Thank you, after several attempts I figured out the correct full URL for the "whoami" API endpoint: https://pleroma.site/users/AndStatus/inbox - and I got JSON response. Will parse it and return to You to move further, if you don't mind :-) However, this URL, looking like an actor's inbox, is conceptually incorrect for the "whoami" call as even #ActivityPub spec says: "The inbox is discovered through the inbox property of an actor's profile". This is why the "whoami" call should be the same for every user, and not the "inbox" of a concrete user/actor. I think :-) This is "whoami" call where the authenticated Actor receives his/her profile information, including URLs of endpoints! ?!
andstatus's status on Thursday, 31-Jan-19 04:36:31 UTC
@kaniini Thank you, after several attempts I figured out the correct full URL for the "whoami" API endpoint: https://pleroma.site/users/AndStatus/inbox - and I got JSON response. Will parse it and return to You to move further, if you don't mind :-) However, this URL, looking like an actor's inbox, is conceptually incorrect for the "whoami" call as even #ActivityPub spec says: "The inbox is discovered through the inbox property of an actor's profile". This is why the "whoami" call should be the same for every user, and not the "inbox" of a concrete user/actor. I think :-) This is "whoami" call where the authenticated Actor receives his/her profile information, including URLs of endpoints! ?!
andstatus: @kaniini I'm testing client to server #ActivityPub implementation of #Pleroma So far I cannot even complete user authorization step and get the authenticated Actor's endpoints (whoami / verify credentials...) at #Pleroma , because I don't know URL of the API point, see https://github.com/andstatus/andstatus/issues/499#issuecomment-457942709 Could anybody help me? @mmn
andstatus's status on Wednesday, 30-Jan-19 15:55:20 UTC
@kaniini I'm testing client to server #ActivityPub implementation of #Pleroma So far I cannot even complete user authorization step and get the authenticated Actor's endpoints (whoami / verify credentials...) at #Pleroma , because I don't know URL of the API point, see https://github.com/andstatus/andstatus/issues/499#issuecomment-457942709 Could anybody help me? @mmn
andstatus: #AndStatus Android client is ready for integration/developer's testing of the "client to server" #ActivityPub protocol. I created an alpha build of AndStatus for server developer, which allows to use AndStatus as a manual Server API testing tool. In order to move forward, past authorisation step, I need an account on a server that successfully authenticates/authorises a User. Servers that I'm aware of, didn't automate/implement the Client registration/User authorisation steps yet... More details and discussion are here: https://github.com/andstatus/andstatus/issues/499
andstatus's status on Saturday, 26-Jan-19 13:08:40 UTC
#AndStatus Android client is ready for integration/developer's testing of the "client to server" #ActivityPub protocol. I created an alpha build of AndStatus for server developer, which allows to use AndStatus as a manual Server API testing tool. In order to move forward, past authorisation step, I need an account on a server that successfully authenticates/authorises a User. Servers that I'm aware of, didn't automate/implement the Client registration/User authorisation steps yet... More details and discussion are here: https://github.com/andstatus/andstatus/issues/499
andstatus: @dpwiz I didn't send HTML-formatted notes to GNU Social via #AndStatus yet :-) Looks like I need to either find a way to tell a server that a note ("notice") has text/html media type, or revert to the plain text sending for GNU Social. BTW text/html is the default media type for #ActivityPub content.
andstatus's status on Wednesday, 05-Dec-18 11:15:56 UTC
@dpwiz I didn't send HTML-formatted notes to GNU Social via #AndStatus yet :-) Looks like I need to either find a way to tell a server that a note ("notice") has text/html media type, or revert to the plain text sending for GNU Social. BTW text/html is the default media type for #ActivityPub content.
andstatus: @autogestion A month or two ago I visited the https://test.activitypub.rocks site and at last found out, which exactly features are REQUIRED for a client app to formally declare its support of #ActivityPub. I've added "Client discovers the URL of a user's outbox from their profile" already, working on other features. What's most important is that internal data model of #AndStatus is already compatible with #ActivityPub, I hope :-) The only hard part to implement is compatible OAUTH (AndStatus supports two variants of OAuth, but it looks like I will need the third for ActivityPub...) After completion of the REQUIRED features I will create the new "ActivityPub" Social Network Type (in addition to the three existing) and will start actual testing... Unfortunately, I don't see any working _real_ (not a toy) server with Client to Server layer support, where I could register as a user and test my client app ;-( ?!
andstatus's status on Wednesday, 14-Nov-18 19:25:50 UTC
@autogestion A month or two ago I visited the https://test.activitypub.rocks site and at last found out, which exactly features are REQUIRED for a client app to formally declare its support of #ActivityPub. I've added "Client discovers the URL of a user's outbox from their profile" already, working on other features. What's most important is that internal data model of #AndStatus is already compatible with #ActivityPub, I hope :-) The only hard part to implement is compatible OAUTH (AndStatus supports two variants of OAuth, but it looks like I will need the third for ActivityPub...) After completion of the REQUIRED features I will create the new "ActivityPub" Social Network Type (in addition to the three existing) and will start actual testing... Unfortunately, I don't see any working _real_ (not a toy) server with Client to Server layer support, where I could register as a user and test my client app ;-( ?!
andstatus: @aldobelus I know about problems with #notifications, please read my reply to you 5 days ago about my own investigation of possible causes, including about "there is nothing new". Unfortunately, due to the Twitter-like approach in a server to client communication taken by GNU Social many years ago and even by Mastodon recently, notes and activities that look the same for a human eye, are represented as different by each server. This is the main cause of users' confusions seeing notifications about the same activities. Hoping that the networks will eventually implement #ActivityPub "client to server layer" spec that resolves this deficiency, I plan to improve Notifications in #AndStatus even in the presence of such unavoidable duplicates... And another note: Looking for Notifications improvements, please make sure that you have AndStatus v.43.02 installed, see https://github.com/andstatus/andstatus/issues/456
andstatus's status on Tuesday, 13-Nov-18 15:33:46 UTC
@aldobelus I know about problems with #notifications, please read my reply to you 5 days ago about my own investigation of possible causes, including about "there is nothing new". Unfortunately, due to the Twitter-like approach in a server to client communication taken by GNU Social many years ago and even by Mastodon recently, notes and activities that look the same for a human eye, are represented as different by each server. This is the main cause of users' confusions seeing notifications about the same activities. Hoping that the networks will eventually implement #ActivityPub "client to server layer" spec that resolves this deficiency, I plan to improve Notifications in #AndStatus even in the presence of such unavoidable duplicates... And another note: Looking for Notifications improvements, please make sure that you have AndStatus v.43.02 installed, see https://github.com/andstatus/andstatus/issues/456
andstatus: RT @yvolk Note - Client to server #ActivityPub layer for #Pump.io ?! @alex@pump.strugee.net @evan@identi.ca Hello pals! Looking at the Pump.io's GitHub site https://github.com/pump-io/pump.io I see some discussions regarding #ActivityPub support, but I couldn't figure out if you are implementing client to server layer of #ActivityPub ?! If yes, what's the status of this work? I want to make #AndStatus Android app an ActivityPub client, but I need at least one server that supports this in order to test my implementation, naturally :-) -- yvolk@identi.ca URL: https://identi.ca/yvolk/note/ab2wuiDPTYOQBjupeSmYRA
andstatus's status on Saturday, 27-Oct-18 13:29:07 UTC
RT @yvolk Note - Client to server #ActivityPub layer for #Pump.io ?! @alex@pump.strugee.net @evan@identi.ca Hello pals! Looking at the Pump.io's GitHub site https://github.com/pump-io/pump.io I see some discussions regarding #ActivityPub support, but I couldn't figure out if you are implementing client to server layer of #ActivityPub ?! If yes, what's the status of this work? I want to make #AndStatus Android app an ActivityPub client, but I need at least one server that supports this in order to test my implementation, naturally :-) -- yvolk@identi.ca URL: https://identi.ca/yvolk/note/ab2wuiDPTYOQBjupeSmYRA
yvolk: Note - Client to server #ActivityPub layer for #Pump.io ?! @alex@pump.strugee.net @evan@identi.ca Hello pals! Looking at the Pump.io's GitHub site https://github.com/pump-io/pump.io I see some discussions regarding #ActivityPub support, but I couldn't figure out if you are implementing client to server layer of #ActivityPub ?! If yes, what's the status of this work? I want to make #AndStatus Android app an ActivityPub client, but I need at least one server that supports this in order to test my implementation, naturally :-) -- yvolk@identi.ca URL: https://identi.ca/yvolk/note/ab2wuiDPTYOQBjupeSmYRA
yvolk's status on Saturday, 27-Oct-18 13:25:54 UTC
Note - Client to server #ActivityPub layer for #Pump.io ?! @alex@pump.strugee.net @evan@identi.ca Hello pals! Looking at the Pump.io's GitHub site https://github.com/pump-io/pump.io I see some discussions regarding #ActivityPub support, but I couldn't figure out if you are implementing client to server layer of #ActivityPub ?! If yes, what's the status of this work? I want to make #AndStatus Android app an ActivityPub client, but I need at least one server that supports this in order to test my implementation, naturally :-) -- yvolk@identi.ca URL: https://identi.ca/yvolk/note/ab2wuiDPTYOQBjupeSmYRA
andstatus: @dansup Any progress on #ActivityPub client to server implementation for #GnuSocial? Maybe you know that someone else is doing this?
andstatus's status on Saturday, 27-Oct-18 13:09:01 UTC
@dansup Any progress on #ActivityPub client to server implementation for #GnuSocial? Maybe you know that someone else is doing this?
moonman: RT @test5 BTW: I can guarantee that #Friendica will include #ActivityPub by the end of the year, since this comment here is posted via AP with Friendica ????The code needs cleanup and yet not everything is coded, but it is working well so far.
moonman's status on Sunday, 23-Sep-18 21:00:22 UTC
RT @test5 BTW: I can guarantee that #Friendica will include #ActivityPub by the end of the year, since this comment here is posted via AP with Friendica ????The code needs cleanup and yet not everything is coded, but it is working well so far.
test5: BTW: I can guarantee that #Friendica will include #ActivityPub by the end of the year, since this comment here is posted via AP with Friendica ???? The code needs cleanup and yet not everything is coded, but it is working well so far.
test5's status on Sunday, 23-Sep-18 20:49:23 UTC
BTW: I can guarantee that #Friendica will include #ActivityPub by the end of the year, since this comment here is posted via AP with Friendica ???? The code needs cleanup and yet not everything is coded, but it is working well so far.
thegoldwater: RT @matt Still working on sending the `Accept` activity back after receiving a `Follow` on @write_as. If I don't sign the request Mastodon rejects it.I'm reading that there's no official authentication method in the #ActivityPub spec, but that HTTP Signatures should be enough, but also that I might need Linked Data Signatures for things that'll get passed around (like posts). Will see.I'm now looking at #Plume and Mastodon's code to figure out what data to send. #federation
thegoldwater's status on Saturday, 23-Jun-18 23:30:26 UTC
RT @matt Still working on sending the `Accept` activity back after receiving a `Follow` on @write_as. If I don't sign the request Mastodon rejects it.I'm reading that there's no official authentication method in the #ActivityPub spec, but that HTTP Signatures should be enough, but also that I might need Linked Data Signatures for things that'll get passed around (like posts). Will see.I'm now looking at #Plume and Mastodon's code to figure out what data to send. #federation
matt: Still working on sending the `Accept` activity back after receiving a `Follow` on @write_as. If I don't sign the request Mastodon rejects it.I'm reading that there's no official authentication method in the #ActivityPub spec, but that HTTP Signatures should be enough, but also that I might need Linked Data Signatures for things that'll get passed around (like posts). Will see.I'm now looking at #Plume and Mastodon's code to figure out what data to send. #federation
matt's status on Saturday, 23-Jun-18 23:15:17 UTC
Still working on sending the `Accept` activity back after receiving a `Follow` on @write_as. If I don't sign the request Mastodon rejects it. I'm reading that there's no official authentication method in the #ActivityPub spec, but that HTTP Signatures should be enough, but also that I might need Linked Data Signatures for things that'll get passed around (like posts). Will see. I'm now looking at #Plume and Mastodon's code to figure out what data to send. #federation
andstatus: RT @andstatus @gdorn ...We need to adopt some syntax to tell the application that substring search should be used. #ActivityPub doesn't mention any query syntax. So in order to filter by a part of URL I think that Twitter's "premium" :-) syntax could be used, e.g.: contains:loadaverage.org or even: contains://loadaverage.org/ - in order to avoid matching with longer domain names (see https://developer.twitter.com/en/docs/tweets/rules-and-filtering/overview/premium-operators.html ) ?!
andstatus's status on Thursday, 21-Jun-18 09:04:30 UTC
RT @andstatus @gdorn ...We need to adopt some syntax to tell the application that substring search should be used. #ActivityPub doesn't mention any query syntax. So in order to filter by a part of URL I think that Twitter's "premium" :-) syntax could be used, e.g.: contains:loadaverage.org or even: contains://loadaverage.org/ - in order to avoid matching with longer domain names (see https://developer.twitter.com/en/docs/tweets/rules-and-filtering/overview/premium-operators.html ) ?!
andstatus: @gdorn ...We need to adopt some syntax to tell the application that substring search should be used. #ActivityPub doesn't mention any query syntax. So in order to filter by a part of URL I think that Twitter's "premium" :-) syntax could be used, e.g.:contains:loadaverage.orgor even:contains://loadaverage.org/- in order to avoid matching with longer domain names(see https://developer.twitter.com/en/docs/tweets/rules-and-filtering/overview/premium-operators.html )?!
andstatus's status on Thursday, 21-Jun-18 07:54:53 UTC
@gdorn ...We need to adopt some syntax to tell the application that substring search should be used. #ActivityPub doesn't mention any query syntax. So in order to filter by a part of URL I think that Twitter's "premium" :-) syntax could be used, e.g.: contains:loadaverage.org or even: contains://loadaverage.org/ - in order to avoid matching with longer domain names (see https://developer.twitter.com/en/docs/tweets/rules-and-filtering/overview/premium-operators.html ) ?!