/
As I've mentioned elsewhere, I have some hope that #Vocata by @Natureshadow <https://codeberg.org/Vocata/vocata> may become a building block for Fediverse platforms not affected by this limitation, but I think that most importantly would be to see a mindset change by Fediverse platform developers, and seeing where development efforts go to, I'm not too sure we're going to see it anytime soon.

Interesting…#activitypub

Vocata/vocata: Vocabulary-Agnostic Transport Agent - #vocata

https://codeberg.org/Vocata/vocata

@blake have you seen #vocata yet?
https://codeberg.org/vocata/

@evan Interesting. I would have thought the opposite would be more common. #Vocata allows Add/Remove to collections that are public or "owned" by the activity's actor. So a remote actor would only be able to modify local public collections. I plan to experiment with implementing Mastodon-style "lists" with local private collections, updated by a local actor via C2S. The "list" collections would be used to maintain custom "timeline" collections exposed through the actor's "streams" field.

@aaronwinstonsmith #Vocata sta venendo sviluppato per produrre un server agnostico, che è il primo passo in questa direzione perché se il server ti sminchia i contenuti non c'è client agnostico che tenga

@lrhodes why even have separate domains. A single server can manage all, the only differences are client side. #Vocata looks like a promising building block in that direction

Interesting #ActivityPub concept via @wenzel and @lrhodes:

“#Vocata is a vocabulary-agnostic ActivityPub server. That means that, in contrast to other server software on the Fediverse, Vocata does not limit what types of content can be handled by it, and how it is presented to users.”

https://codeberg.org/Vocata/vocata

@oblomov thanks for sharing about #vocata that looks really interesting, as I always found it weird having my Fediverse identity linked to a particular service (Mastodon, Pixelfed or something else).

If so, it would be good for platforms to start moving towards it (possibly initially supporting it side-by-side with the existing APIs). If not, it would be good for the C2S protocol to be improved (and/or better specified, if it's a problem of underspecification), so it could be adopted as above.

So, #askFedi question: are there platforms that support the C2S protocol too? Maybe #GoToSocial or #Vocata? How's that working out?

11/11

@foxxtrot @thomasjwebb @sgf @mattblaze

This is actually something I've been thinking about for a while. I have a longish writeup about this here
https://sociale.network/@oblomov/110199093300206184 (but see also the referenced meta-instance idea). #GoToSocial <https://gotosocial.org/>, #Streams <https://codeberg.org/streams/streams> and even more so #Vocata <https://codeberg.org/Vocata/vocata> are maturing as building blocks that would be useful in avoiding stream fragmentation while still allowing type-specific presentation in clients.

1/n

TIL there's another graph-aware #ActivityPub server besides #Vocata:

https://gitlab.com/linkedopenactors/rdf-pub