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

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

Second problem is related to how my implementations of #GoActivityPub handle OAuth clients presences already, by using fully compatible ActivityPub actors which exist at the URL which forms the Client ID.

So now I have a conflict where the same ID needs to be at the same time an ActivityPub Actor and a OAuth Metadata document.

This should be trivially solvable with different content types for the two documents but there are the following problems: one, the specification doesn't tell us which content-type the OAuth metadata should use, and two, how many servers would actually use it?

2/2

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

@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. :)

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

After mostly wasting the past couple of days on adding a rudimentary client side search function to the new static documentation website of #GoActivityPub I'm back in the land of increasing code coverage.

Like I said before, I've never really had to dedicate explicit time to this activity specifically and I'm annoyed at how time consuming and tedious it gets when you want to increase the numbers from ~70% to ~80%.

Those last few percentages are hard to come by.

#unit-testing

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

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

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

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

On this topic, calling all #Go #developers interested in lending a hand.

I have two major goals for increasing the unit-test coverage in the individual packages that #GoActivityPub is comprised of.

These are tasks that are very accessible even for people new to the #ActivityPub spec and I would prefer to support new developers that want to give it a try than wait until I have time to do them myself.

The only requirement I have is that if you want to help, you already have some public Go projects that I can have a look at.

Point of contact is on this email (after you "deobfuscate" it): goap＠federated·id

#Go #Golang #developers #helpwanted #NLNet #ngi0

On this topic, calling all #Go #developers interested in lending a hand.

I have two major goals for increasing the unit-test coverage in the individual packages that #GoActivityPub is comprised of.

These are tasks that are very accessible even for people new to the #ActivityPub spec and I would prefer to support new developers that want to give it a try than wait until I have time to do them myself.

The only requirement I have is that if you want to help, you already have some public Go projects that I can have a look at.

Point of contact is on this email (after you "deobfuscate" it): goap＠federated·id

#Go #Golang #developers #helpwanted #NLNet #ngi0

Congratulations to the newest batch of @NGIZero fediverse ⁂ projects to receive grants! Seeing that 20% of the 29 projects in this round are #fediverse projects is exciting:
#Flohmarkt (https://nlnet.nl/project/Flohmarkt)
#Hubzilla (https://nlnet.nl/project/Hubzilla-Superblock)
#GoToSocial (https://nlnet.nl/project/GoToSocial-1.0)
#Drupal ​(@drupal, @swentel https://nlnet.nl/project/Drupal-AP-recipes)
#Mirlo (@mirlo https://nlnet.nl/project/Mirlo)
#GoActivityPub (@mariusor https://nlnet.nl/project/GoActivityPub)

Here's the announcement https://mastodon.xyz/@NGIZero/115384471765057337

Congratulations to the newest batch of @NGIZero fediverse ⁂ projects to receive grants! Seeing that 20% of the 29 projects in this round are #fediverse projects is exciting:
#Flohmarkt (https://nlnet.nl/project/Flohmarkt)
#Hubzilla (https://nlnet.nl/project/Hubzilla-Superblock)
#GoToSocial (https://nlnet.nl/project/GoToSocial-1.0)
#Drupal ​(@drupal, @swentel https://nlnet.nl/project/Drupal-AP-recipes)
#Mirlo (@mirlo https://nlnet.nl/project/Mirlo)
#GoActivityPub (@mariusor https://nlnet.nl/project/GoActivityPub)

Here's the announcement https://mastodon.xyz/@NGIZero/115384471765057337

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