Notices tagged with activitypub, page 8

Hey fediverse admins, have you made sure your instance is being counted by https://the-federation.info/ ? I love being able to respond with that stats site URL when people say "nobody uses federated social networks" elsewhere on the web :) It now counts nodes running any one of 36 server apps, across 9 federation protocols, including #OStatus, and #ActivityPub, reporting about 2 1/2 million users.

@clacke @dansup will 2019 be the year of the #ActivityPub-ready #GNUsocial? ;-P

@LWFlouisa that's a little bit misleading. MG instance aren't actually part of the fediverse yet AFAIK. @cwebber might be able to share more up-to-date news on the prospects of MG implementing #ActivityPub and joining the fed.
@joshim

@joshim it depends what you want to use it for. The main differences are;
* #MediaGoblin supports any type of media, including audio, photos, documents, slideshows, and so on. #PeerTube is just for videos.
* MG instances are stand-alone. You can only find media via searching on the instance its hosted on or a web search. PT supports #ActivityPub, so your videos can be found via searching on other instances, and #WebTorrent, so if one of your videos goes viral, it won't #SlashDot your instance ;)

@0x1C3B00DA I've just been learning more about #Feneas (Federated Network Association) today. I really like the vision by @cj to use #ActivityPub to create a federated protocol forge for specifying AP extensions. It's a genius solution, and a brilliant example of #dogfooding to boot ;)
https://cjslep.com/c/blog/an-activitypub-philosophy
@bob

Implementing #ActivityPub in some form, would allow Diaspora users to connect with about 3 times as many users as they can using only the Diaspora protocol standard. That's with a number of apps/ instances not yet rolling out AP support that's in the works. Regardless of how good the Diaspora UI might be for existing users, denying them such a massively increased network reach is poor #UX design.

♲ @heluecht@pirati.ca: I wrote an answer to Dennis post schub.io/blog/2018/02/01/activ… about #ActivityPub feneas.org/activitypub-well-it…

However, his comparison with #XMPP is mind-blogging. Yes, the #XMPPFoundation has developed a good process for formalizing extensions to the base standard (#XEPs). Yes, this is something #ActivityPub folks could learn from. But the XMPP spec was first published in 2004. The final AP 1.0 standard was only published last year, give it time!

Here's the "final" comment on #ActivityPub by the informal spokesperson on inter-operationg from the #Diaspora project:
https://schub.io/blog/2019/01/13/activitypub-final-thoughts-one-year-later.html

Imagine a comms #UX, where I could choose a contact, choose a rough message length (say, short, medium, or long), and the software would give me an appropriate compose UI for that length of message, and poll the receiver's comms app to determine what protocol they prefer to receive each length of message on. Eg. I could set my app to tell senders I want to receive short messages by SMS, medium ones by #ActivityPub, and long ones by email.