Notices tagged with activitypub, page 25
-
Adonay Felipe Nogueira (adfeno@quitter.se)'s status on Wednesday, 07-Feb-2018 13:01:59 UTC 
Adonay Felipe Nogueira
pt-BR: Migrei para http://qttr.at/21xn por este ter #ActivityPub: http://qttr.at/21qh -
Jorge (soloojos@squeet.me)'s status on Thursday, 25-Jan-2018 16:00:45 UTC 
Jorge
♲ @Nextcloud News (unofficial) (ncnews@libranet.de): ActivityPub: the new standard for decentralized networks
Today, the World Wide Web gained a new standard: ActivityPub. https://www.w3.org/TR/activitypub/ The recommendation has been published by the responsible W3C workgroup after 3 years of work, started in no small part by Christopher Lemmer Webber, founder of the Mediagoblin project. Nextcloud uses ActivityPub, implementing it to handle Activity federation between servers, crucial for our Global Scale architecture. https://nextcloud.com/globalscaleAnd indeed, you may already be using ActivityPub now without realizing it.
–Christopher Lemmer WebberNextcloud and ActivityPub
Nextcloud implements ActivityPup to inform users about changes to their files, new calendar and so on between users on different Nextcloud servers since Nextcloud 12. This makes ActivityPup part of what makes Nextcloud Global Scale work! https://nextcloud.com/globalscale
The Activity app which implements ActivityPub will continue to be improved, as its role has expanded over the years to inform users about a lot of things beyond file changes. Its core developer, Joas, blogged earlier about his todo list for the year, https://www.schilljs.com/2018/01/10/nextcloud-2018.html including changes to the Activity App.
Illustration of how ActivityPub works from W3.orgWhat is ActivityPub
The origins of ActivityPub trace back to microblogging technology StatusNet, the former Laconia which was first widely implemented at identi.ca. Identi.ca has since migrated to pump.io, the successor to OStatus and the protocol it implements is essentially the base of ActivityPub. Evan Prodromou, the original author of Laconia and pump.io, designed the new protocol to use Activity Streams for commands and transfer data via a simple REST inbox API. The best place to get started to learn more about the protocol is on the W3.org website. https://www.w3.org/TR/activitypub/#Overview
Christopher Lemmer Webber wrote a guest post https://www.fsf.org/blogs/community/victory-for-libre-networks-activitypub-is-now-a-w3c-recommended-standard on the Free Software Foundation blog explaining some history and features of the protocol. It provides a server-server protocol for federation and a client-server protocol for users to connect to a server. The core idea of ActivityPub is to bring together decentralized social networks, gaining critical user mass while keeping data on separate servers.
The popular Twitter alternative Mastodon is a prominent user, same goes for Mediagoblin which aims more at sharing photos and videos. And, then, Nextcloud of course!- - - - - -
https://nextcloud.com/blog/activitypub-the-new-standard-for-decentralized-networks/ https://www.w3.org/TR/activitypub/
#nextcloud #activitypub -
Falgn0n The Wizard 🔮 (falgn0n@social.librenet.co.za)'s status on Thursday, 25-Jan-2018 14:09:25 UTC 
Falgn0n The Wizard 🔮
👍 When they start throwing around phrases like "the new standard" ... 👍
https://nextcloud.com/blog/activitypub-the-new-standard-for-decentralized-networks/
-
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 25-Jan-2018 06:05:55 UTC 
AndStatus
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 ActivityPub protocol.
Very helpful clarifications, allowing me to express clearly relations between different things inside the application. For example, now I'm working towards creation of views on a User across all networks, logically merging Actors of this User.
As a result, at the first step you will see e.g. actions/messages by andstatus@quitter.no Actor as actions by ONE Actor, even if you see these actions via several Servers, e.g. via mastodon.social and via GnuSocial.no, as on the attached screenshot.
The next step will be to merge Actors of one User into one view. E.g. set andstatus@loadaverage.org and andstatus@mastodon.social Actors as _one_ User. This cannot be done automatically due to current limitation of the #ActivityPub specification, but at least can be done manually for selected Users that you follow via their Actors in different networks... https://loadaverage.org/attachment/4021406 -
Free Software Foundation (fsf@status.fsf.org)'s status on Wednesday, 24-Jan-2018 16:23:07 UTC 
Free Software Foundation
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 -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 23-Jan-2018 18:35:27 UTC
AndStatus
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 -
chocobozzz@framapiaf.org's status on Tuesday, 16-Jan-2018 10:09:02 UTC 
Chocobozzz
#PeerTube and #Mastodon communication demonstration!
2018 will be fun :)
https://peertube.cpy.re/videos/watch/da2b08d4-a242-4170-b32a-4ec8cbdca701
-
futureBoyfriend (deadsuperhero@social.nasqueron.org)'s status on Tuesday, 28-Nov-2017 21:17:27 UTC 
futureBoyfriend
Want to see a decentralized video hosting site?! I sure do! Check out this run-down of #PeerTube, an awesome new video platform that supports #ActivityPub
Thanks to @Chocobozzz for developing such a great piece of software. It's really cool to see where this is going!
-
spla :senyera: :vim: (spla@mastodont.cat)'s status on Tuesday, 28-Nov-2017 09:05:13 UTC 
spla :senyera: :vim:
@paulfree14 @koldo nice, #ActivityPub rule the #internet @Framasoft
-
AndStatus@Quitter.no (andstatus@quitter.no)'s status on Thursday, 09-Nov-2017 15:57:02 UTC 
AndStatus@Quitter.no
@silverwizard For connections to #GNUSocial, #Mastodon and #Twitter - #AndStatus uses similar “Twitter-like" protocols.
For connections to #PumpIo - #ActivityPub - like protocol. -
AndStatus@Quitter.no (andstatus@quitter.no)'s status on Thursday, 09-Nov-2017 13:39:11 UTC
AndStatus@Quitter.no
@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 -
Danyl Strype (strypey@quitter.se)'s status on Monday, 30-Oct-2017 06:05:00 UTC 
Danyl Strype
@randomascii you don't need an account on an instance to follow someone on it, as long as it federates using #OStatus or #ActivityPub -
AndStatus (andstatus@loadaverage.org)'s status on Tuesday, 17-Oct-2017 19:31:57 UTC
AndStatus
@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) -
Yuri Volkov (yvolk@loadaverage.org)'s status on Tuesday, 17-Oct-2017 05:46:12 UTC 
Yuri Volkov
@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 specification, as an Analyst, for some concrete application. This way you will read every phrase, some of them - many times...
@mike @verius @clacke @cwebber -
Yuri Volkov (yvolk@loadaverage.org)'s status on Thursday, 12-Oct-2017 06:57:54 UTC
Yuri Volkov
@cwebber@octodon.social Thank you for reply to the #ActivityPub issue at https://github.com/w3c/activitypub/issues/260
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 to "users are mapped to actors" with addition, how (you suggested wording...)
Where can we see current draft for review how it looks now? You are too quick to state that the issue is resolved :-)
2. Let's check if the statement is valid:
* ""user" is technically an entity outside the protocol"
2.1 First of all the term is used tens times in the document, which describes the protocol: https://www.w3.org/TR/activitypub/
2.2. The term "user" is used for two different things, actually:
* for "natural person from a real world"
* and for "user's account at a Servetr" (my interpretation).
The second meaning is definitely "inside protocol". Just look at these phrases, from many available, for example:
* "This protocol permits a client to act on behalf of a user."
* "Client to server interaction takes place through clients posting Activities to a user's outbox"
My conclusion is that a User in the second meaning "user's account at a Server" is definitely a part of the protocol description.
3. As now we agreed on separation of an Actor from a User, let's look again, what we read in the document.
3.1 You know: there are many places, where the word user(s) should be replaced with a word Actor(s), e.g. here {again, one of many examples):
* "The Follow activity is used to subscribe to the activities of another user."
Attributes of a User are presented as attributes of an Actor in examples... -
Yuri Volkov (yvolk@loadaverage.org)'s status on Monday, 09-Oct-2017 05:48:29 UTC
Yuri Volkov
@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 pump.io. 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 issue: https://github.com/w3c/activitypub/issues/260
Not many responses so far :-( -
AndStatus (andstatus@loadaverage.org)'s status on Thursday, 05-Oct-2017 03:33:08 UTC
AndStatus
@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 -
zoowar (zoowar@indy.im)'s status on Wednesday, 04-Oct-2017 21:25:05 UTC 
zoowar
Something that separates identity, message distribution, and message content. An earlier criticism of #ActivityPub by @mike was quite reasonable. The one in this thread suggests he has a drinking problem. -
AndStatus (andstatus@loadaverage.org)'s status on Wednesday, 04-Oct-2017 20:28:37 UTC
AndStatus
@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? -
Yuri Volkov (yvolk@loadaverage.org)'s status on Sunday, 01-Oct-2017 05:04:45 UTC
Yuri Volkov
I filed a bug for #ActivityPub, which is exactly about Person's freedom to choose (and actually, change) an instance/server of a global social network without loosing his/her identity, including historical data.
Moving from one instance of a federation to another is a normal case, just like having user accounts at several servers. And #ActivityPub specification should explicitly allow this.
See https://github.com/w3c/activitypub/issues/260
@fuzboleroxv @citizenphnix
@cwebber @gargron @deadsuperhero @mmn @lnxw48a1
All Bobinas P4G content and data are available under the 
