What is the motivation for encouraging LitePub implementors to "supply a locally hosted version of the LitePub JSON-LD Context"?
Is it just for people using full-out JSON-LD parsers?
Won't this create problems for people using parsers that do NOT go download and interpret context-URIs? And instead just hard-code the vocabulary in their code?
#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #JSONLD #LitePub
I wish Mastodon handled ActivityStreams "type":"Video" as well as "type":"Note" with a Video attachment.
They could be rendered the same. But they (currently) aren't.
#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #Mastodon
Interesting. PeerTube content (in their "application/activity+json") can be Markdown.
(Reference: curl -H 'Accept: application/activity+json' https://tube.archworks.co/videos/watch/7d1d5c2f-6d13-48d0-addd-ea99e9e9c967 )
#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #JSONLD #MarkDown #PeerTube
It seems to be common now to put JSON-LD in the HTML source code.
ActivityPub and ActivityStreams files (application/activity+json) are JSON-LD files.
You could put ActivityPub and ActivityStreams in the HTML source code.
#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #HTML #JSONLD
I wish Mastodon handled ActivityStreams "type":"Video" as well as "type":"Note" with a Video attachment.
They could be rendered the same. But they (currently) aren't.
#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #Mastodon
I'm looking for your opinions from the developers of the fediverse.
A common HTML web page can contain related links via the <link> tag. I would like to do the same for Activity Streams objects, for example:
{
"@context": "https://www.w3.org/ns/activitystreams",
"id": "https://writings.hongminhee.org/ap/2024/12/a-year-with-the-fediverse.json",
"type": "Article",
"name": "A year with the fediverse",
"content": "2024 was truly a year where I was deeply immersed in the fediverse. …",
"url": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/",
"attachment": [
{
"type": "Link",
"rel": "alternate",
"hreflang": "ko",
"href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ko-hang-kr.html",
"mediaType": "text/html"
},
{
"type": "Link",
"rel": "alternate",
"hreflang": "ja",
"href": "https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ja.html",
"mediaType": "text/html"
}
]
}
Do you think this makes sense, and would it be appropriate to put Link objects in the attachment?
#ActivityPub #activitystreams but version 3 and semantically/syntactically/whatever more correct
1/
I like the Actor-Model.
A friend who is a Scala programmer introduced it to me.
I used it when programming in — Erlang and Scala. Later, I implemented the Actor-Model in Go. I even implemented Erlang's supervision-tree in Go.
ActivityPub is maybe better understood through the lens of the Actor-Model — rather than a HTTP REST API.
However —
#ActivityPub #ActivityStreams #ActorModel #DeSo #Fediverse #FediDevs
As I mentioned before — I think the Fediverse version of Follow-Packs / Starter-Packs should be some type of ActivityPub / ActivityStreams object.
It could look a lot like the "following" and "followers" URLs look.
RE: https://mastodon.social/@reiver/113629444566451650
#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #FollowPack #FollowPacks #JSONLD #StarterPack #StarterPacks
1/
There are now multiple efforts to create a Fediverse version of Follow-Packs / Starter-Packs.
❦
A starter-pack gives you a collection of people and other users to follow
They help new users find people to follow — so they don't have an empty home-feed. But they also help existing users find more people to follow.
🧵
#ActivityPub #ActivityStreams #ATmosphere #ATProto #ATProtocol #Bluesky #DeSo #FediDevs #Fediverse #FollowPack #FollowPacks #JONSLD #SocialMedia #StarterPack #StarterPacks
Someone created a list of all the JSON-LD properties used in the Fediverse:
(I haven't tried confirming the accuracy of this list. But, it is interesting.)
How much Fediverse software can read the expanded form of JSON-LD?
Or are they making hard-coded assumptions about what the JSON names will be?
I.e.,:
"indexable" : true
Versus:
"http;//joinmastodon·org/ns#indexable" : true
In some ways, I think it might have been "better" if the Fediverse didn't use JSON-LD and instead just used URLs as key names.
I.e., if it didn't use the "＠context" stuff.
"＠context" adds a certain type of complexity.
There are a lot of different types in the ActivityStreams Vocabulary.
https://www.w3.org/TR/activitystreams-vocabulary/
But because Mastodon only supports 8 of them (with only 2 of them being supported properly), there is "pressure" on other Fediverse software to restrict themselves to these 8.
https://docs.joinmastodon.org/spec/activitypub/#payloads
Because they want to be compatible with Mastodon.
The ActivityPub Client-Server API
https://www.w3.org/TR/activitypub/#client-to-server-interactions
#introduction
I am an open data access (#ODBC, #JDBC, and #HTTP), integration (#DataVirtualization), and data management (#DBMS and/or #KnowledgeGraph) technologist, enthusiast, and entrepreneur.
I am passionate about open standards for #GenAI, #AI, #Identity #Authenticity, #SocialMedia (#ActivityPub & #ActivityStreams), and data de-silo-fication initiatives (e.g. #SemanticWeb, #LODCloud, #LinkedData, #RWW, and #SmallData).
I don't like any kind of silo!