Another OpenAPI tool crashes and burns
General Discussion
3
Posts
2
Posters
23
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 -
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 #BangHeadHereTwo things:
-
If there was an OpenAPI test suite, this should be included. If not, someone, not me, should work on getting this fixed.
-
Use
application/activity+jsonas almost everyone else and this problem disappears.
-
-
Two things:
-
If there was an OpenAPI test suite, this should be included. If not, someone, not me, should work on getting this fixed.
-
Use
application/activity+jsonas almost everyone else and this problem disappears.
@Helge I suppose it's my own stupid fault for trying to actually follow the spec, rather than just pointing to it as an excuse for any interoperability problems. ;) -
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@macgirvin that's interesting, I hadn't thought of using punycode. Like @edent@mastodon.social my exposure to it was strictly limited to domains (and even then only to counter domain spoofing)
-
@edent@mastodon.social -- It's also used for the username component of email addresses iirc; as these are originally also specified as 7-bit US-ASCII. So I convert local usernames with idn. Just something I did out of habit really. You can use UTF-8 if you want, so I'm only saying that punycode seems to federate better based on my experience. We tested this with a bunch of fediverse software at the time and it just worked. We'll accept either.
-
@macgirvin
I thought Punycode was only for domain names. Are you saying you also use it for the user part?
-
@edent@mastodon.social -- I've just tested and that account also works fine with Hubzilla. I will mention that your implementation in this case uses url-encoded usernames while ours uses punycode. They should be able to interact just fine, but the fact that there are multiple ways to arrive at a solution could cause a bit of confusion for implementers.
You'll need to use punycode if you wish to federate with the diaspora protocol or email or any other projects or protocols which restrict the character set for usernames. So it might end up being a more flexible solution in the long run and should work fine with every other fediverse project today. ASCII-restricted software will just use the xn-- name; and all their links and buttons should work fine.
Url-encoding should also work, but perhaps not so universally and easily as punycode; as witnessed by the number of issues documented in this thread.
-
-
@jandi
Yes, that would really help. I will set the priority in the Weblate project for the part used to understand tags inside messages. Thank you for your continuous support on projects :)
-
@edent@mastodon.social -- Just looked again... this was first introduced as a hidden feature in redmatrix around 2013-2014, and so may also be available currently in Hubzilla (behind the "system.unicode_usernames" feature toggle). There were some major changes in 2019 that to my knowledge weren't ever backported. I think these only applied to local usernames and not remote usernames, but the functionality in hubzilla still might need to be verified.
-
The map combines community reports from the #Fediverse and shelters and veterinaries from #OpenStreetMap loaded in real time as you zoom in.
PawFed is built to be a community project, not a one person effort. There will be many ways to contribute beyond posting reports.
If you find the project useful, don't hesitate to share it. Thank you. (3/3)
