#activitypubdev — Public Fediverse posts

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

#ActivityPubDev #fedidev #httpsig

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

#ActivityPubDev #fedidev #httpsig

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

#ActivityPubDev #fedidev #httpsig

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

#ActivityPubDev #fedidev #httpsig

I've started working on generating RFC9421 compatible HTTP-Signatures in #GoActivityPub about a week and a half ago, but it felt more like a month.

Writing tests for the client module took the bulk of this time and it was a proper slog. We did manage to increase code coverage from under 20% to 80% plus.

This makes it a bit harder to migrate to a new API when the future version 1 of the library will be tagged, but the changes I have planned shouldn't be insurmountable.

Now I just need to implement the verification, and I'll be done with what is a very large milestone for the library. :goose_hacker:

#ActivityPubDev #fedidev #httpsig

Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

#fediverse #activityPub #activityPubDev

Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

#fediverse #activityPub #activityPubDev

Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

#fediverse #activityPub #activityPubDev

Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

#fediverse #activityPub #activityPubDev

Does anyone know of Mastodon servers that use outbound RFC9421 HTTP-Signatures ?

According to the release notes, version 4.5 should have it enabled by default for outgoing requests using the double knocking mechanism, but so far I haven't seen any request containing them...

#fediverse #activityPub #activityPubDev

@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

@julian regarding #FEP7888 the as:context property is non-functional, so an array of contexts is allowed. do you accept that or do you throw an http 500 ;-) and do you know if others can hanlde an context array ? #activitypub #activitypubdev

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

If you're trying to dereference all RDF namespaces found in the #ActivityStreams JSON-LD document you must first download the internet.

Now downloading google.com...

#ActivityPub #ActivityPubDev

• The authorize command respects $HTTPS_PROXY, but the post command doesn't. I had to change this to get it to talk to services on my test network.
• It doesn't send an OAuth state parameter; the OAuth server library I'm using complains about this so I fixed it.

• The authorize command respects $HTTPS_PROXY, but the post command doesn't. I had to change this to get it to talk to services on my test network.
• It doesn't send an OAuth state parameter; the OAuth server library I'm using complains about this so I fixed it.

• The authorize command respects $HTTPS_PROXY, but the post command doesn't. I had to change this to get it to talk to services on my test network.
• It doesn't send an OAuth state parameter; the OAuth server library I'm using complains about this so I fixed it.

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""
   |                                                              ^

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""
   |                                                              ^

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""
   |                                                              ^

If you are having problems with other software in the Fediverse ecosystem, try…idk, talking to the devs? They're right there. Or even block the software from your instance entirely.

Don't be a fucking dick.

Writing documentation was good for #GoActivityPub.

It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.

I've fixed a couple of issues in this way these past days.

https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object

#ActivityPub #ActivityPubDev

Writing documentation was good for #GoActivityPub.

It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.

I've fixed a couple of issues in this way these past days.

https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object

#ActivityPub #ActivityPubDev

Writing documentation was good for #GoActivityPub.

It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.

I've fixed a couple of issues in this way these past days.

https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object

#ActivityPub #ActivityPubDev

Writing documentation was good for #GoActivityPub.

It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.

I've fixed a couple of issues in this way these past days.

https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object

#ActivityPub #ActivityPubDev

Writing documentation was good for #GoActivityPub.

It gives me the opportunity to go through some user scenarios for the tools I'm documenting and make sure that they work the way I'm describing.

I've fixed a couple of issues in this way these past days.

https://man.sr.ht/~mariusor/go-activitypub/go-ap/pitfalls.md#changing-the-type-of-an-object

#ActivityPub #ActivityPubDev

For the past couple of days I've been hard at work writing documentation in the attempt to decrease the friction for developers that try #GoActivityPub for their applications.

I am of a mind to pay some #Go developers in the near future to do a weekend's worth of programming into trying to use the library in projects, so we can iron out potential issues with the use of the library itself and the documentation.

Anyone interested?

#go #ActivityPub #ActivityPubDev #fediverse

For the past couple of days I've been hard at work writing documentation in the attempt to decrease the friction for developers that try #GoActivityPub for their applications.

I am of a mind to pay some #Go developers in the near future to do a weekend's worth of programming into trying to use the library in projects, so we can iron out potential issues with the use of the library itself and the documentation.

Anyone interested?

#go #ActivityPub #ActivityPubDev #fediverse

For the past couple of days I've been hard at work writing documentation in the attempt to decrease the friction for developers that try #GoActivityPub for their applications.

I am of a mind to pay some #Go developers in the near future to do a weekend's worth of programming into trying to use the library in projects, so we can iron out potential issues with the use of the library itself and the documentation.

Anyone interested?

#go #ActivityPub #ActivityPubDev #fediverse

For the past couple of days I've been hard at work writing documentation in the attempt to decrease the friction for developers that try #GoActivityPub for their applications.

I am of a mind to pay some #Go developers in the near future to do a weekend's worth of programming into trying to use the library in projects, so we can iron out potential issues with the use of the library itself and the documentation.

Anyone interested?

#go #ActivityPub #ActivityPubDev #fediverse

For the past couple of days I've been hard at work writing documentation in the attempt to decrease the friction for developers that try #GoActivityPub for their applications.

I am of a mind to pay some #Go developers in the near future to do a weekend's worth of programming into trying to use the library in projects, so we can iron out potential issues with the use of the library itself and the documentation.

Anyone interested?

#go #ActivityPub #ActivityPubDev #fediverse

Is anyone aware of a FEP for that?

#ActivityPub #ActivityPubDev #FEP

Is anyone aware of a FEP for that?

#ActivityPub #ActivityPubDev #FEP

Is anyone aware of a FEP for that?

#ActivityPub #ActivityPubDev #FEP

Is anyone aware of a FEP for that?

#ActivityPub #ActivityPubDev #FEP

Is anyone aware of a FEP for that?

#ActivityPub #ActivityPubDev #FEP

I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

#ActivityPub #fedidev #ActivityPubDev

I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

#ActivityPub #fedidev #ActivityPubDev

I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

#ActivityPub #fedidev #ActivityPubDev

I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

#ActivityPub #fedidev #ActivityPubDev

I just realized that the default specifications for ActivityPub/ActivityStreams do not have a way to perform an update on an object's ID. (ie, moving it from example.com/1 -> example.com/2)

An Update activity does not allow ID updates because it would lose the reference to the original one. (It can be massaged by using an Origin property, but I don't like that).

Another option would be to use a Move activity (which is defined as moving objects between collections), where the Origin property is the object itself instead of a collection. (I like this behaviour better, as it requires less divergence from the spec)

#ActivityPub #fedidev #ActivityPubDev