mariusor , 8 days ago to random

My project that converts #SourceHut wiki repositories into static websites is finally getting to the point where it works quite well.

I've integrated it into my flow for the #GoActivityPub documentation and it looks decent (in my biased opinion), the docs themselves are not great, but I'll do another pass over them before we release a v1 of the library.

https://go-activitypub.federated.id

mariusor , 25 days ago to random

After much faffing about, I have implemented the dynamic #OAuth2 client creation for #GoActivityPub services using the Client ID Metadata Document[1] that's been proposed as a replacement(?) for RFC7591 (Dynamic Client Registration Protocol).

The changes are in both the Authorization service and in the BOX #ActivityPub client to server helper.

[1] https://datatracker.ietf.org/doc/draft-ietf-oauth-client-id-metadata-document/

#CIMD

mariusor , 1 month ago to random

For people interested in #ActivityPub #C2S (client to server), the #GoActivityPub services have gained the ability to dynamically register OAuth2 clients based on RFC7591.

The easiest to test is the ONI project that can be directly run without much setup: https://git.sr.ht/~mariusor/oni

mariusor , 2 months ago to random

#ActivityPub client to server is severely impaired by "authorized fetch" because usually before building an Activity to send to an Actor's outbox, one would want to validate some of the IRIs they operate on.

For example, I want to build a Follow request for a remote actor (represented by an IRI or webfinger resource). My client won't allow me to add this random IRI as the Object of the Follow and just send it, it wants to dereference it and make sure it's a valid Actor.

However when authorized fetch is enabled on that actor's instance, this dereference will fail, because the client can't generate a valid HTTP Signature for its request. :(

mariusor , 2 months ago to random

I forgot how tedious it is to chase code coverage when writing tests.

However this was part of the reason that made me include the "boring" parts of building a robust library into the goals set for the #nlnet grant.

So after a couple of days of work I finally got the first of the storage backends for the #GoActivityPub library go past 80% test coverage.

I hope I can reuse some of the test logic in the other backends, as they need to perform identically.

#go #ActivityPub #fedidev

mariusor , 3 months ago to random

Need a palate cleanser after the past weeks where I worked furiously on storage backends for #GoActivityPub fixing tests and building a conformance suite.

I think I'll try my hand at a static site generator. It would also be part of #NLNet sponsored work, but only tangentially so, as it would form the base for generating the documentation wiki for the library.

#activitypub #dev

mariusor , 3 months ago to random

After starting the work on the conformance suite for the #GoActivityPub storage backends I, of course, got the nasty surprise that none of the existing ones are actually passing all the tests. :D

#ActivityPub

mariusor , 3 months ago to random

Well, after an initial failure, my #NLNet grant application for #GoActivityPub has been accepted under the NGI0 Commons Fund. 💪

This means that for the next months my main focus will be fully on making #ActivityPub in the #Go programming language easier for other developers.

If you're one of them, reach out, I want to know what you struggle with and how I can help with that.

https://nlnet.nl/thema/NGI0CommonsFund.html#:~:text=GoActivityPub%20%E2%80%94%20Help%20people%20develop%20Fediverse%20software%20in%20Go