Notices tagged with activitypub, page 10

This is the sort of stuff #ActivityPub is supposed to be good at, but it's still pleasantly surprising when it works. It probably won't take the place of my RSS reader any time soon, though being able to comment on blog posts via the Mastodon UI would be an improvement...

@z428 @charlag the same issues applies to DMs, outside of Mastodon there's no ironclad guarantee they won't be federated as normal posts in #ActivityPub networks. The UI would need to make it clear that the post was only guaranteed to self-destruct on the instance it was posted on. As Mike says though, this is a solved problem in #Zot networks
@lightone

@RangerMauve really? Isn't metadata part of the file being torrented? I guess it depends what you mean by "metadata". Also, since comments are federated using #ActivityPub, there ought to be a way for #PeerTube to make sure any comment on a given video appears everyone that video is mirrored. But I guess that won't help unless the torrent client used to open the #MagnetLink supports AP.

Installing #Nextcloud, because one day I hope to provide tech support to a client, Nextcloud to Nextcloud, via #ActivityPub. This is fun!

@Michcioperz this is an intriguing idea. Have you looked at the ways the #IndieWeb folks are experimenting with #ActivityPub? Eg #P3K
https://indieweb.org/p3k

@musicman my understanding is that it's intended to be a free code replacement for #GrooveShark (thus the name), federated via #ActivityPub, but @funkwhale may want to correct me on that.

I'm keen to start mirroring the #Disintermedia blog on one of the new #ActivityPub compatible blogging apps. Can anyone make any recommendations for which app(s) to try first, and which hosts are stable, and planning to stick around for a while?

@bhaugen it's not really important at the level of standards and protocols. #ActivityPub doesn't care if an instance has a single user or millions, for example. But it does matter when it comes to how we think about #UX, admin interfaces, moderation structures and rules and how they're set, portability of accounts, deployment and provisioning, financial arrangements, legal structures; ie where the mechanics of digita tech meet the dance of human *organization*.

... Does the #ActivityPub Server<->Client spec, which no one implements, have a better (read:basically any) way of handling different aspects than any single client does?

Or is that just a rough-spot for, like, everyone.

@LWFlouisa @LPS it's like each instance 'votes' by making its own decision and blocking or not blocking. The aggregate of all those 'votes' determines how much of the fediverse any given instance can federate with. Nobody can stop an instance from existing, or publishing over the #OpenWeb and #ActivityPub. All they can decide is whether or not their instance is listening. #FreeSpeech is respected, but also #FreeAssociation, which necessarily includes a right to disassociate.

@Alonealastalovedalongthe @codesections ae, this is why I think it's sad that Mike's work on #NomadicIdentity wasn't included in #ActivityPub. This is a solved problem, yet the standards process failed to make use of the solution :-( It will probably take another generation of dev for this to be addressed.

@codesections @Alonealastalovedalongthe also
> you're always free to pick up and move to a different one.

... needs clarification that this requires starting from scratch with no followers. Proper server>server migration is an unsolved problem in #OStatus and #ActivityPub apps, and is likely to remain so for the foreseeable future (unlike #Zot app like #Hubzilla that have #NomadicIdentity)

@pfefferle just stumbled across your #ActivityPub plug-in for #WordPress. Great stuff!
https://wordpress.org/plugins/activitypub/