#activitypubdev

5 posts · Last used 3d

Boosted by @fedicat@pc.cafe
Requesting final comments on FEP-61cf: The OpenWebAuth Protocol I wrote FEP-61cf: The OpenWebAuth Protocol almost three years ago and I think it's time to mark it as FINAL. I think there's enough detail in there for anyone who wants to interoperate with Hubzilla etc. I used it as a reference while writing my own implementation and it seemed to do the trick - though I can't be entirely sure that I wasn't relying on memory to some extent. Originally I wanted to figure out how OpenWebAuth authenticates/authorizes media fetches, but it turns out that this was done by a more-or-less completely separate mechanism, which I don't think needs to be described here. There has also been a bit of discussion about a possible "next generation" OpenWebAuth protocol, but if this ever goes anywhere, it can be described in a new FEP. So - does anyone have any final comments on this FEP? Has anyone (other than me) tried to implement it? Even if it's just a half-finished sketch rather than a proper implementation, it would still be good to hear any feedback anyone might have. If there's nothing substantial then I'll aim to set this to FINAL about two weeks from now. #ActivityPubDev #FediDev #FEP #Hubzilla #Streams #Forte
0
0
1
0
When I started the work on ActivityPub projects I fully embraced Maslow's Hammer adage. I wanted as much as possible in my services to go through the #ActivityPub vocabulary and I fully embraced the client to server API. But there are elements of a web application that require custom functionality no matter what, say changing a password. So for those I just added the capability of running commands through ssh. :goose_hacker:#ActivityPubDev #fedidev
5
5
3
0
I'm surprised at how many issues my new integration tests are finding. I already had an integration testsuite, but the way the #fedbox application was run was not in full isolation, and I expect some of the setup steps I had included don't really exist on a fresh install. We now build a fresh container image, start it up, provision it with mock data, and then run tests, but only through mechanisms that are available to a prospective server operator: CLI commands executed through SSH, and ActivityPub client to server operations. #fedidev #activityPubDev #activitypub
3
6
4
0
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
7
5
1
0