Advertising instance capabilities via nodeinfo
Technical Discussion
1
Posts
1
Posters
0
Views
-
Instance software is constantly evolving and adding new features. Wouldn't it be good if there was a way for other instances to discover what features yours can handle, to determine how they will communicate?
One way to do this could be to add the FEPs, etc that an instance supports to the nodeinfo response that it serves. Possibly as a protocol, a service or just in the metadata part.
Where would make the most sense? Or is there another mechanism apart from nodeinfo entirely?
Gli ultimi otto messaggi ricevuti dalla Federazione
-
Instance software is constantly evolving and adding new features. Wouldn't it be good if there was a way for other instances to discover what features yours can handle, to determine how they will communicate?
One way to do this could be to add the FEPs, etc that an instance supports to the nodeinfo response that it serves. Possibly as a protocol, a service or just in the metadata part.
Where would make the most sense? Or is there another mechanism apart from nodeinfo entirely?
-
@douwe core concept: accounts are hosted separately from apps, so one account logs you in everywhere.
All data is stored in your account, and different apps can re-use types of data (called Lexicons).
Here’s a second view of the bookmarks I linked above, in a different app https://margin.at/bmann.ca/collection/3m5u77miiyf2h
Apps can be quite simple, because functions are spread across different parts of the architecture.
Feel free to ask more! My atproto account is bridged here @bmann.ca
-
@douwe heya!
Here are some #atproto resources both architecture & conceptual https://semble.so/profile/bmann.ca/collections/3m5u77miiyf2h
My own Beyond Microblogging talk is a bit dated but will give you examples and a crash course https://bmannconsulting.com/notes/beyond-microblogging-atproto/
-
@brettm@swarm.coiloptic.org Could I see the problematic JSON-LD document?
-
Medea is just JSON not JSON-LD but it seems to process some JSON-LD just fine, eg Snac and Mastodon-generated stuff. Looking at Iceshrimp and they seem to throw in a lot of extra cruft:
[] all over the place,
escaped double quotes,
a bunch of litepub and misskey stuff
eeerp many JSON parses take one look and say "I ain't reading all that" 🙂
CC: @hongminhee@hollo.social
-
@brettm@swarm.coiloptic.org yes! Ask @hongminhee@hollo.social
I'm guessing Medea is a JSON-LD processor?
Min hee has been working on some of these workarounds 😝
-
So I am using Scheme's Medea library to parse ActivityPub posts. It can process Mastodon and Snac just fine. But does not like some others, eg Iceshrimp.
I guess I will write a function to re-format the Iceshrimp json-ld so Medea likes it ... anyone know of examples or blog posts that have discussed this? To save me staring at the dreaded json-ld for so long...
Other Scheme libraries have the same problem with Iceshrimp posts. IDK if they may also have some issues with Misskey, Sharkey, Honk, etc etc, haven't got around to testing those yet.
#ActivityPub
-
@silverpill@mitra.social Oh, it seems to ignore the proof part.
