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
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.)
GoToSocial has a JSON-LD namespace:
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.
Continued my experiments with #Fedify and #ActivityPub yesterday and I think I’m confused.
I was trying to make an extension for an Object, and if I understand #JsonLd, the context property contains the definition of any extra property added. I see e.g. the activity streams ns resolves to a nice JSON LD that contains all the properties, but the mastodon one doesn’t resolve to anything? Is it not necessary?
In the next version (v0.14.0) of #Fedify, the performance of the Object.toJsonLd() method will be dramatically (~3k ×) faster. This is expected to improve the overall performance of Fedify apps!
The JSON-LD processor ended up being #Fedify's bottleneck, so I'm in the process of fixing Fedify to generate JSON-LD without the proper JSON-LD processor.