Notices tagged with activitypub, page 3
-
"The worst thing I see (and this is really really bad) is that if Eugen/Gargron sends a restricted post to his 74000 followers and you decide to reply to it, your server is going to have to fetch the actor record for every one of those 74000 followers to find their inbox address and then send out 74000 copies of your reply.
On our side of the federation, if you want to have 74000 followers, it's only you who needs to pony up the resources to support that..."
-
"The worst thing I see (and this is really really bad) is that if Eugen/Gargron sends a restricted post to his 74000 followers and you decide to reply to it, your server is going to have to fetch the actor record for every one of those 74000 followers to find their inbox address and then send out 74000 copies of your reply.
On our side of the federation, if you want to have 74000 followers, it's only you who needs to pony up the resources to support that..."
-
@eloquence More maintainers is always desirable! Though it's not like they're lining up, as far as I'm aware of .)
I'd say the state is usable, unlikely to go through major changes (in functionality, but adaptation for #ActivityPub for delivering would be great - but things like federated pseudoprivate messaging or such scoping is unlikely to be implemented since there's no guaranteed way to keep confidentiality). -
@lightone the other #Rust app is #Rustodon by @er1n, an #ActivityPub implementation
https://github.com/rustodon/rustodon -
@wolf480pl @thog wouldn't it be great if #LuggageMark was a standardized protocol within #ActivityPub?
-
Dear #Mastodon, #PeerTube and #FunkWhale, could any of you produce an #ActivityPub 101 tutorial? Like :
- respond something like this to .well-known/webfinger (I know that webfinger is involved but I don't know a thing about it)
- in the user page, include this, that
- here's how to publish users profile
- here's how to declare endpoints to receive activityStream message
- etc(just trying here to guess things people need to implement to federate)
-
Dear #Mastodon, #PeerTube and #FunkWhale, could any of you produce an #ActivityPub 101 tutorial? Like :
- respond something like this to .well-known/webfinger (I know that webfinger is involved but I don't know a thing about it)
- in the user page, include this, that
- here's how to publish users profile
- here's how to declare endpoints to receive activityStream message
- etc(just trying here to guess things people need to implement to federate)
-
My new article about #Funkwhale is out! It's basically like a federated Grooveshark or Soundcloud. The main dev is working on bringing #ActivityPub to it.
-
My new article about #Funkwhale is out! It's basically like a federated Grooveshark or Soundcloud. The main dev is working on bringing #ActivityPub to it.
-
@pskosinski yeah, Mike had a change of heart on #ActivityPub, see:
https://medium.com/we-distribute/got-zot-mike-macgirvin-45287601ff19 -
@amiloradovsky "This toot (reply to own reply, a follow-up) didn't contain any mentions by default (feature?)" Yes, this is done deliberately :-)
Regarding CW (Note name in #ActivityPub terms) - I'm testing this now for #Mastodon and #Pump.io and plan to release...
The keyboard doesn't disapper, when switching or screen rotation, if Note editor is active.
I mentioned "business users" in a context of users' need in "intuitive" UI, not about #AndStatus in particular :-) -
@hamishcampbell none of them are federated yet AFAIK, but I know @cwebber is intending to implement #ActivityPub in #MediaGoblin
-
@rysiek @deadsuperhero similarly, if the #fediverse grows massively, due to #MediaGoblin and others implementing #ActivityPub ...
-
@amiloradovsky "This toot (reply to own reply, a follow-up) didn't contain any mentions by default (feature?)" Yes, this is done deliberately :-)
Regarding CW (Note name in #ActivityPub terms) - I'm testing this now for #Mastodon and #Pump.io and plan to release...
The keyboard doesn't disapper, when switching or screen rotation, if Note editor is active.
I mentioned "business users" in a context of users' need in "intuitive" UI, not about #AndStatus in particular :-) -
@lnxw48a1 Seven hours to fully complete upgrade? - Your device is really slow... but you are lucky: I spent at least 200 hours developing v.36 and 37 of #AndStatus, so having v.37 installed on my devices took me a lot more efforts :-)
Seriously, since last summer internal data model of AndStatus was mostly redesigned (inspired by #ActivityPub) in order to open a way for future major improvements. No wonder that these changes affected most of the application's features.
I tried to allow existing users (including you) to preserve existing data and not simply tell them that the new version requires uninstall of a previous one (that way I would save a manweek or two of my time). But after upgrade you may need to adjust something yourself (e.g. Manage timelines). If you don't want to bother with settings, just reinstall AndStatus and see it running much faster. Of couse :-)
@mcscx -
Pleroma — A lightweight federated server and client for microblogging services like #Mastodon and #GNUSocial, supporting both #OStatus and #ActivityPub
-
Pleroma — A lightweight federated server and client for microblogging services like #Mastodon and #GNUSocial, supporting both #OStatus and #ActivityPub
-
New #disintermedia blog post (first proper one for 2018); 'Could Web Forums Be Federated With #ActivityPub?'
http://qttr.at/22qk -
#AndStatus v.37.00 is available in the Open Beta testing channel https://github.com/andstatus/andstatus/issues/456
"Merging actors of Users from different Social Networks. New Interactions timeline"
1. Actors having the same WebFingerId (e.g. "andstatus@loadaverage.org") in different social networks are merged logically. This allows AndStatus to show you in one timeline activities of one actor, downloaded via different instances. This is especially needed for GNU Social and Mastodon.
Please note that for Pump.io this feature is provided for years, because all Pump.io instances use the same actorID (WebFingerId) for the same actor.
2. Mentions timeline is replaced by Interactions, which shows not only "mentions" and replies, but also likes, reposts and followers. Basically "Interactions" timeline shows all interactions of other users with us (our actors) whereas "Notifications" timeline shows us only those interactions, which we preferred to be notified about in Settings > Notifications, plus unsent notes.
3. Names of things in the User interface (mostly) changed according to the #ActivityPub Recommendations. In particular, now we use the word "note" for tweets/toots/notices.
And the words "Actor" and "User" have different meanings (In ActivityPub, a user is represented by "actors" via the user's accounts on servers. User's accounts on different servers correspond to different actors.) Most of Timelines in AndStatus show Activities now instead of Notes. https://loadaverage.org/attachment/4102974 -
#AndStatus v.37.00 is available in the Open Beta testing channel https://github.com/andstatus/andstatus/issues/456
"Merging actors of Users from different Social Networks. New Interactions timeline"
1. Actors having the same WebFingerId (e.g. "andstatus@loadaverage.org") in different social networks are merged logically. This allows AndStatus to show you in one timeline activities of one actor, downloaded via different instances. This is especially needed for GNU Social and Mastodon.
Please note that for Pump.io this feature is provided for years, because all Pump.io instances use the same actorID (WebFingerId) for the same actor.
2. Mentions timeline is replaced by Interactions, which shows not only "mentions" and replies, but also likes, reposts and followers. Basically "Interactions" timeline shows all interactions of other users with us (our actors) whereas "Notifications" timeline shows us only those interactions, which we preferred to be notified about in Settings > Notifications, plus unsent notes.
3. Names of things in the User interface (mostly) changed according to the #ActivityPub Recommendations. In particular, now we use the word "note" for tweets/toots/notices.
And the words "Actor" and "User" have different meanings (In ActivityPub, a user is represented by "actors" via the user's accounts on servers. User's accounts on different servers correspond to different actors.) Most of Timelines in AndStatus show Activities now instead of Notes. https://loadaverage.org/attachment/4102974 -
@tobias I presume it's an instance of #MediaDrop does it support federation w/ #ActivityPub or P2P scaling with #WebTorrent like #PeerTube?
-
Really interesting deep dive on the #ActivityPub spec by Dennis Schubert of #Diaspora. Worth reading.
http://schub.io/blog/2018/02/01/activitypub-one-protocol-to-rule-them-all.html
-
Really interesting deep dive on the #ActivityPub spec by Dennis Schubert of #Diaspora. Worth reading.
http://schub.io/blog/2018/02/01/activitypub-one-protocol-to-rule-them-all.html
-
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 -
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 -
Welcome to Diaspora Updates. This channel serves as a monitoring bot for everything related to the Diaspora project. It sources multiple feeds to produce a linear timeline related to Git Commits, Community Forum discussions, and project posts from the blog and HQ account.
This initiative is by no means official to the Diaspora project in any way; We Distribute runs automated channels intended to serve as a communication bridge. Occasionally updates referring to this channel may be made for questions about curation.
This channel can be subscribed to via #ActivityPub, #Ostatus, #Diaspora, and #Zot. Anyone is encouraged to comment on statuses and engage with the community. -
Welcome to Diaspora Updates. This channel serves as a monitoring bot for everything related to the Diaspora project. It sources multiple feeds to produce a linear timeline related to Git Commits, Community Forum discussions, and project posts from the blog and HQ account.
This initiative is by no means official to the Diaspora project in any way; We Distribute runs automated channels intended to serve as a communication bridge. Occasionally updates referring to this channel may be made for questions about curation.
This channel can be subscribed to via #ActivityPub, #Ostatus, #Diaspora, and #Zot. Anyone is encouraged to comment on statuses and engage with the community. -
If I were to describe #activitypub as "SMTP over HTTP using arbitrarily extended JSON", would I be very off? @cwebber
-
@sonyam pump.io has private messaging, followers-only posting, federated identity so you can run around on other servers and comment using your home id, the API is lightweight and very consistent and understandable in comparison with GS+Qvitter (I hear), and it's the basis for the Next Big Thing, #activitypub.
pump.io was built in a few months by one guy though, and GS was built in a couple of years by several full-time people, so there are still quirks in the (actually intentionally) limited web UI. pump.io works best with a client.
@andstatus does a decent job. I'm not going to complain, because I still didn't file those bugs since last I complained, so the buck is with me. It's mostly about message formatting, other than that it's an awesome client for both GS and pump. -
@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
