Another OpenAPI tool crashes and burns
Technical Discussion
1
Posts
1
Posters
14
Views
-
Just over a year after Go's OpenAPI generator let me down, the #ActivityPub Content-Type causes the same problem again, this time in Python:
Is it really that unusual to include parameters in MIME types like this? I'm sure I've seen them all over the place.example_client/api/default/put_object.py:34:62: SyntaxError: Simple statements must be separated by newlines or semicolons
|
33 | _kwargs["json"] = _body
34 | headers["Content-Type"] = "application/ld+json; profile="https://www.w3.org/ns/activitystreams""
| ^
Or am I venturing off the beaten track by trying to be explicit about them in myopenapi.ymlfile?
#ActivityPubDev #BangHeadHere
Gli ultimi otto messaggi ricevuti dalla Federazione
-
That would work!
-
Well, there's this FEP which does something similar...
https://codeberg.org/fediverse/fep/src/branch/main/fep/844e/fep-844e.md
-
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 😝
