@mariusor woot!
Technical Discussion
12
Posts
5
Posters
0
Views
-
@smallcircles thank you Arnold. :)
-
@smallcircles thank you Arnold. :)
The codeberg issue is kind of still an ugly scratch pad rn. The thing awaits a follow-up where stuff is more organized and easier to drill down into. Proper docs eventually.
A first step may be to name the discrete and granular building blocks that one should focus on when starting out on an #ActivityPub client-to-server adventure quest. Give them consistent names. And then to map all the various projects to that as a MDN-like who-supports-what table.
-
The codeberg issue is kind of still an ugly scratch pad rn. The thing awaits a follow-up where stuff is more organized and easier to drill down into. Proper docs eventually.
A first step may be to name the discrete and granular building blocks that one should focus on when starting out on an #ActivityPub client-to-server adventure quest. Give them consistent names. And then to map all the various projects to that as a MDN-like who-supports-what table.
@smallcircles GoActivityPub servers support following things for Client to Server:
* Accessing objects and collections
* Filtering the collections through query parameters (eg. ?type=Create)* Support for OAuth2 actor endpoints information and authorization
* Support for .well-known information (webfinger and now, OAuth2 client registration)* ACLs for accessing them based on recipients list - this includes collection filtering of individual items
* ACL principal extraction from OAuth2 Bearer token (or from HTTP-Signature)* Outbox Activity validation & processing (which I think is the main one :D)
-
@smallcircles GoActivityPub servers support following things for Client to Server:
* Accessing objects and collections
* Filtering the collections through query parameters (eg. ?type=Create)* Support for OAuth2 actor endpoints information and authorization
* Support for .well-known information (webfinger and now, OAuth2 client registration)* ACLs for accessing them based on recipients list - this includes collection filtering of individual items
* ACL principal extraction from OAuth2 Bearer token (or from HTTP-Signature)* Outbox Activity validation & processing (which I think is the main one :D)
( @smallcircles in case you wanted a starting point )
-
( @smallcircles in case you wanted a starting point )
@mariusor wonderful, thank you. It is updated on codeberg now :)
-
@mariusor wonderful, thank you. It is updated on codeberg now :)
@smallcircles sometime in the future I'll have a bit more explanations about the different things to incorporate in the #GoActivityPub documentation.
I'll try to remember to ping you. :)
-
@mariusor this is great, I'm looking forward to testing this 🔥
-
@mariusor this is great, I'm looking forward to testing this 🔥
When you do, feel free to ping me with questions (here or on the mailing list).
-
@mariusor nice!
-
@mariusor did you implement the oauth metadata endpoint also? Can clients discover the registration endpoint easily?
-
I'd generally discourage RFC7591 in decentralized systems due to the fact that it creates client sprawl (this is currently a problem with Mastodon's client registration mechanism, which is why we created CIMDs) — every client in RFC7591 is a distinct client, with its own
client_idandclient_secret, which can make client management interfaces difficult to implement (e.g., every time you login on a mobile device or SPA, you'll get a brand newclient_id). CIMDs solve this by anchoring client metadata to a URI, and using that URI as theclient_id.If you need to test clients using CIMDs in development, there is cimd-service however, it's currently targeting the AT Protocol ecosystem (so has a few specifics that at present there that would not necessarily make sense of ActivityPub)
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
I think the wrapping in <p> is just plain good practice because otherwise rendered content could be injected somewhere resulting in invalid HTML.
Not that browsers ever reject bad HTML anyway heh</p>
-
>Can you explain what goes on in mitra?
When mediaType is text/markdown, the entire content is wrapped in a <p> tag. This was done for compatibility with PeerTube. I think <p> was needed to create a space between the title (name) and the content, since title is prepended to content in Mitra (also a compatibility hack -- for Mastodon API clients).
-
I'd generally discourage RFC7591 in decentralized systems due to the fact that it creates client sprawl (this is currently a problem with Mastodon's client registration mechanism, which is why we created CIMDs) — every client in RFC7591 is a distinct client, with its own client_id and client_secret, which can make client management interfaces difficult to implement (e.g., every time you login on a mobile device or SPA, you'll get a brand new client_id). CIMDs solve this by anchoring client metadata to a URI, and using that URI as the client_id.
If you need to test clients using CIMDs in development, there is cimd-service however, it's currently targeting the AT Protocol ecosystem (so has a few specifics that at present there that would not necessarily make sense of ActivityPub)
-
Speaking of handling markdown. I created funfedi.dev Media Types a while ago (and just added it to the navigation). I lost interest when I saw that nobody properly handled the mediaType attribute of a note. Not that I know what I expected.
Can you explain what goes on in mitra? When mediaType is text/markdown. It changes __bold__ to <p>__bold__</p>, otherwise no paragraph tags. I'm pretty sure, I was once told to use __ for bold and * for emphasize. So my markdown should be good.
Full example ... input activity -> mitra api response
Final note: I am not sure what I would want a proper data format to do. I find the solution of W3C ActivityPub (not W3C ActivityStreams) proposes of putting HTML in content and adding source with the original, from which the HTML was generated ok. Of course, this leaves the existence of the summary and name field superfluous.
-
@reiver@mastodon.social add in NodeBB as well. Markdown first, and probably HTML too, although it will probably be sanitized to death on the way out.
-
@mariusor that's too bad. All I have left is mussels, French fries, large-scale bureaucracy, and peeing statues.
-
@reiver #WriteFreely uses Markdown by default too, but of course sends out HTML to the fediverse
-
@reiver Markdown or its subset is supported by almost every platform except Mastodon.
But PeerTube is the only software I know that puts markdown in content instead of HTML.
