marius
mastodon 4.7.3Mostly a programmer.
Implementing #ActivityPub in the #Go programming language.
Current projects:
* #GoActivityPub - a library to use ActivityPub in Go.
* #FedBOX - a generic ActivityPub service supporting the client to server API.
* #brutalinks - a link aggregator inspired by (old) reddit, hacker news and lobste.rs built on top of FedBOX.
* #oni - a single user ActivityPub server with minimal fuss.
Jolla Phone 2 & Sailfish OS: A Real Third Option
@julian for the implementors of Go ActivityPub applications that need RFC9421 signatures, it's important to note that it's not FedBOX that provides the functionality, but two modules in the GoActivityPub library:
- the client module[1] wraps the signing of activities.
- the auth module[2] wraps the verification functionality.
Also for lower level use, there's the underlying module being wrapped by GoActivityPub: dadrus/httpsig [3]
[1] https://github.com/go-ap/client [2] https://github.com/go-ap/auth [3] https://github.com/dadrus/httpsig
Fed@hongminhee@hollo.social
@hongminhee@hollo.social like I mentioned in a thread where Evan and Reiver were talking about this, I think having a mediaUpload that has a very similar behaviour to an inbox/outbox, but with one small details is a bad API.
I would prefer there's either a two step process: upload media first, use resulting token in an object create, or use the outbox with for the binary data upload directly... The first one seems saner to me.
it's incumbent on you to make the case for it.
@evan@cosocial.ca I was sure I managed to do that. :D
And so far, I don't think you provided me with any counter-factual arguments that I didn't address.
- It doesn't include addressing,
As always it's the Clients that are responsible for addressing, therefore the second step should cover it, if the user/client chooses to perform it.
- What happens if the client doesn't post the
Createactivity?
Whatever the server desires: cleanup after a while, keeping the media, etc. Why do you think it's relevant for the specification itself?
ActivityPub, to my reading, is not about how to store content, but about how to distribute content. So after it was uploaded, it's no longer the concern of the spec, unless operated further through other ActivityPub requests.