@hongminhee @thisismissem @PuercoPop
For your information, I recently opened an issue to track current #ActivityPub C2S implementations.
This is the list thus far:
#ActivityPods
#Epicyon
#Onepage.pub
#Pleroma
#RDFPub
#Vocata
#FedBOX
#Mitra
#streams
#forte
https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130
Client-side #AndStatus is a well-known attempt to implement it:
My (and @codecraft 's) #TaganakNet #RDF server in #Rust has reached a milestone: It can load its own config from an RDF data source (much like slapd's cn=config backend), and uses its own ORM-like derive-macro-based structs for it 🎉!
(like here: https://codeberg.org/Taganak/brgy/src/commit/501b4b0fad721c3ce9ca325715c298734877518a/src/config.rs#L64)
Now we can start implementing useful #LinkedData things on top of it (#Vocata, at some point).
With #Firefish being EOLed and the matter of account migration and the tight coupling of identity, server, platform and (default) interface coming back to the front I am reminded of one of the many reasons why I haven't started self-hosting yet. We seriously need stronger decoupling. Building everything on top of something like #Vocata would really help in this sense. (Pity that Vocata hasn't seen too much activity in the last year.)
Added #Viverse, #Wafrn, @awakari, #Vocata and #Loforo icons to #FediverseIconography at https://fediverse.wake.st
Are there already some examples of how #vocata is used in fediverse applications?
/
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.
@blake have you seen #vocata yet?
https://codeberg.org/vocata/
#Vocata is purely an ActivityPub server, so Fediverse client/servers can be separated. Very interesting project that could develop new ways of engaging with the Fediverse (the possibility of this sort of thing is what makes the Fediverse so much more interesting than any platform…)
https://codeberg.org/Vocata/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
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.”
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
The more I read the #ActivityPub spec the more I see it as an extension of #email and #Usenet protocols. By this I mean I have the feeling that it would be possible to roundtrip e.g. email through AP “losslessly”. Which opens interesting possibilities when considering the development of platform-agnostic AP servers like #Vocata
https://codeberg.org/Vocata/vocata
Now I'm dreaming of a client that handles emails, news and AP …
