Notices tagged with activitypub, page 5
-
#AndStatus v.37.00 is available in the Open Beta testing channel http://status.hackerposse.com/url/15142 "Merging actors of Users from different Social Networks. New Interactions timeline" 1. Actors having the same WebFingerId (e.g. "http://status.hackerposse.com/url/6715") in different social networks are merged logically. This allows AndStatus to show you in one timeline act…
-
Currently I'm refactoring User-related part of #AndStatus data model using recent amendments of #ActivityPub specification, which I initiated: distinction between a User (a real life person or an organisation...), Accounts of this user in concrete instances (Servers) of the global social network, and an Actor - the entity, which is actually present in Activities of the Activit…
-
Exciting news: thanks to all the hard work from a team including @MediaGoblin founder Chris Webber @dustyweb, #ActivityPub has finally been made an official W3C recommended standard! https://u.fsf.org/2g6
-
On activities in #Twitter. Is Twitter heading to #ActivityPub also?!
...I checked via Twitter's web interface: I do see the message favorited...
and you know, Twitter shows, at least in web interface, your "Like Activity". I need to investigate, maybe #AndStatus will be able to receive such some day... https://loadaverage.org/attachment/4018314
-
If I were to describe #activitypub as "SMTP over HTTP using arbitrarily extended JSON", would I be very off? @cwebber
-
@silverwizard wrote: "AndStatus is an Android app for OStatus clients"
This is wrong. #OStatus is a server-to-server protocol, #AndStatus connects to servers using server-to-client protocols. This is why AndStatus doesn't know and doesn't depend on OStatus protocol.
Moreover, #Mastodon 's client-to-server protocol is still based on outdated Twitter like API, not on #ActivityPub, unfortunately.
@jackyalcine
-
@silverwizard wrote: "AndStatus is an Android app for OStatus clients"
This is wrong. #OStatus is a server-to-server protocol, #AndStatus connects to servers using server-to-client protocols. This is why AndStatus doesn't know and doesn't depend on OStatus protocol.
Moreover, #Mastodon 's client-to-server protocol is still based on outdated Twitter like API, not on #ActivityPub, unfortunately.
@jackyalcine
-
@6gain I know about this problem. Will fix as soon as I complete current large changes, which I'm doing (moving to #ActivityPub data model)
-
@jark Reviewing and improving #ActivityPub specification is not about coding/programming. It's about analysis and modeling. But my experience shows that it's hard to notice problems and mistakes in such documents, until you don't try to start actually using it in practise, in this case - starting to implement some application using this specification OR starting to adapt this …
-
@jark Reviewing and improving #ActivityPub specification is not about coding/programming. It's about analysis and modeling. But my experience shows that it's hard to notice problems and mistakes in such documents, until you don't try to start actually using it in practise, in this case - starting to implement some application using this specification OR starting to adapt this …
-
@cwebber@octodon.social The same for me: Only implementing now domain model of #ActivityPub /#ActivityStreams in my #AndStatus application I became deep enough aware of the specs' advantages and shortcomings... so I initiated another round of the spec fixes. Sorry that not months ago...
@bea @teascade @neon
-
@cwebber@octodon.social The same for me: Only implementing now domain model of #ActivityPub /#ActivityStreams in my #AndStatus application I became deep enough aware of the specs' advantages and shortcomings... so I initiated another round of the spec fixes. Sorry that not months ago...
@bea @teascade @neon
-
@cwebber@octodon.social Thank you for reply to the #ActivityPub issue at http://status.hackerposse.com/url/16270 I followed the discussion there plus copying my follow-up below: 1. Let's go step by step. Explicitly stating that Actors and Users are different entities is a good way forward. BTW the confusing phrase "users are represented as "actors" here" should also be changed…
-
@cwebber@octodon.social Thank you for reply to the #ActivityPub issue at http://status.hackerposse.com/url/16270 I followed the discussion there plus copying my follow-up below: 1. Let's go step by step. Explicitly stating that Actors and Users are different entities is a good way forward. BTW the confusing phrase "users are represented as "actors" here" should also be changed…
-
@mike@macgirvin.com I agree that #ActivityStreams2 is well designed. Maybe this is exactly because its ideas are actively tested in practice for several years in http://status.hackerposse.com/url/3385. Confusion of Actors and Users of servers in the #ActivityPub I regard as a conceptual mistake that should be fixed _now_. So I proposed concrete additions to the spec in this is…
-
@mike@macgirvin.com I agree that #ActivityStreams2 is well designed. Maybe this is exactly because its ideas are actively tested in practice for several years in http://status.hackerposse.com/url/3385. Confusion of Actors and Users of servers in the #ActivityPub I regard as a conceptual mistake that should be fixed _now_. So I proposed concrete additions to the spec in this is…
-
@zoowar This is exactly what I propose in this #ActivityPub specification bug report: https://github.com/w3c/activitypub/issues/260
Separation of Actors (e.g. a Person) from Users of servers (user accounts) even on a conceptual (domain model level). Please support this fix!
@mike @cwebber
-
@mike@macgirvin.com What do you this is a better alternative to #ActivityPub? Or maybe something concrete could be changed in its current version to make it better?
-
@mike@macgirvin.com What do you this is a better alternative to #ActivityPub? Or maybe something concrete could be changed in its current version to make it better?
AndStatus
Free Software Foundation
MMN-o ✅⃠
AndStatus@Quitter.no
Yuri Volkov
All Hacker Poesy content and data are available under the 