Lmst

@mamund thank you. I will also give the linked article on agentic systems a read.

Note that #ActivityPub here on the #fediverse has this need to discover and introspect the capabilities of actor endpoints on the network.

This entirely missing. With #ActivityStreams #LinkedData endlessly versatile, a player on the fediverse can freely invent their own flavours on-the-fly, introducing protocol decay and makes #interoperability harder.

Whack-a-mole driven development to moving targets ensues.

It's annoying that most of the ambiguity in #ActivityPub / #ActivityStreams is a direct result of the squishiness of json, and the transport medium being almost literally anything else would have made it a nonissue

let's demo this with a simple case. say you want to `tag` something that is a `Movie` described by schema.org. the `Movie` declares that it has an `actor` who performed in it.

this is redefining the term `actor` as defined at the top-level by #activitystreams -- where `actor` means who performed an `Activity`, not who performed in a `Movie`.

if the activitystreams context was protected, then this would be a fatal error for any #jsonld validator. you cannot be sure which `actor` was meant!

3/?

say you have a generic property whose range is relatively unbounded -- a grab-bag where anything goes. something like how `attachment` or `tag` are used in #activitystreams. using multiple contexts at the top-level introduces a potential conflict in terms. you could reconcile any conflicts with a custom context, but that prevents reuse / understanding a more well-known context.

unfortunately, due to context propagation, terms defined earlier on can "leak" into the naively merged subgraph.

2/?

I've read the #ActivityStreams spec a few times now and the O'Reilly ActivityPub book chapter on it. I could be missing something here, but polymorphism in data is my least favourite thing ever. Is it a link as a string? Is it a link as an object? Is it an object? Is it a mix of all them in an array? The terms object and link are confusingly overloaded too.

I expect the authors put a lot of thought into it, so I'm going to assume I am the problem here and look into JSON-LD again. Maybe there's a simple ways to parse and produce these documents.

The idea of using AS for an app's domain model doesn't appeal to me at all. Much rather marshal to it.

@normis jo vēlējos izaicinājumu. Saprast, uztaisīt un lietot. Un #ActivityStreams vai #ActivityPub ir tikai papildinājumi, tam ko patiesībā taisu - savu aplikāciju ministarteri blogam, rēķiniem, you name it...

Pārstāju te tik bieži rakstīt, jo gribēju uzrakstīt savu Twitteri/Mastadonu. Bet vēlme to padarīt vairāk kā "make it simple, make it work", ir jau aizgājusi kāda ntā iterācija. Beigās (pagaidām) ir parasta pierakstu web aplikācija bez skaistās daļas, tikai #API (jā, #APIfirst piekritējs) un izdzēsu visu #ActivityPub un #ActivityStreams... jo tie izrādās ir vienkārši. Tagad jāpārtaisa vecāka vibe-coded "skaistā" #ReactJS puse. Un tad mobile + desktop. Un tad... :)

5/

So, not just Decentralized Social (DeSo), but instead —

Decentralized Social (DeSo), Federated Social (FeSo), Localized Social (LoSo)

The goal is 'social' that is simultaneously — 'Decentralized', 'Federated', and 'Localized', all at the same time.

RE: https://mastodon.social/@reiver/114551725757671167

#ActivityPub #ActivityStreams #Decentralization #DeSo #Federation #FeSo #Fediverse #governance #Localization #LoSo

4/

Federation is the word we use to describe that act of bringing together and connecting these separate Decentralized, Localized communities.

This is where protocols such as ActivityPub, ActivityStreams, etc come into play.

Federation is a voluntary choice.
But, so too is Defederation, if desired.

#ActivityPub #ActivityStreams #Decentralization #DeSo #Federation #FeSo #Fediverse #governance #Localization #LoSo

https://www.w3.org/TR/activitystreams-vocabulary/#dfn-prev

Why is it ok for example 100 to have a string as the value of the "prev" property when it is constrained to be a CollectionPage | Link ?

#ActivityStreams

Taisīt #ActivityPub / #ActivityStreams aplikāciju nemaz nav tik viegli, ja dokumentācija/specifikācija ir tāda "vaļīga". Piem., Vai šis lauks A var saturēt HTML - definitely maybe.

iespējams, uzrakstīju savu "bloga" dzini. Nācās gan noņemt pagaidām visas #ActivityPub / #ActivityStreams iespējas (extra fīčas), bet, kad būs atpakaļ, būs kaut kas startp #WordPress un #Mastodon ar #Pixelfed iespējām. Un ja nebūs slinkums, saderīgs ar #Bluesky :)

Iespējams. Konteinerizēts #PoC strādā uz mana datora :D

Tagad tiksi nenoslinkot un pabeigt, jo patiesībā ir veidots pēc WordPress līdzības, lai var modulāri papildināt (pluginu sistēma), piem., pārrakstīt manu esošo rēķinu sistēmu.

After toiling away at this for a few months, I'm releasing two new Go projects for the fediverse today:

longdistance, a JSON-LD processor.
pana, an ActivityStreams library built on longdistance.

I built these projects with the hope to make it easier for folks to get started building on the fediverse themselves. You can read a bit about this on my blog.

(If you happen to have computer touchers in your followers, I would appreciate a boost.)

#golang #LinkedData #ActivityStreams

A reasonable ActivityPub / ActivityStreams API to schedule something to be posted in the future might be — to HTTP POST something to an account's outbox with the `published` field set to a date-time in the future.

#ActivityPub #ActivityStreams #DeSo #FediDev #FediDevs #Fediverse