Mauve 👁💜 @mauve@mastodon.mauve.moe

@rra @cblgh Oh I think you're missing the `Content-Type` header indicating the body is JSON

@rra sadly the client API is still a WIP but my colleague should be getting to it next week ish. I'll see if I can get a lil somethin done before then though.

technically it should be possible to do it witg curl, you just need to do the digest calculation and signing stuff with openssl or similar. Sadly I don't have ready examples of it cause we did it in js.

Here's how we do it so far: https://github.com/hyphacoop/social.distributed.press/blob/initial/src/server/apsystem.ts#L129

@reconbot I've been working on this for a while. https://blog.mauve.moe/posts/distributed-press-social-inbox

Tl;dr we figured out how to get the ap static bits working and made a minimal server just for the inbox portion

@rra @site Hmm are you self hosting your inbox instance? We have swagger docs generated at /v1/docs

Sadly swagger doesn't have the HTTP auth stuff built in so we don't have an out of the box UI yet.

We use the http signature spec for authentication so you shoukd sign yout request with the private key corresponding to your actor's public key: https://docs.joinmastodon.org/spec/security/#http

Still think it'd be useful to exted the #ActivityPub client-server spec with some sort of standard for "searching" through your messages.

IMO this will be crucial for making clients that can be interoperable between implementations (which I think is important for user agency!)

https://www.w3.org/TR/activitypub/#inbox

@pevohr Ah! We're putting in some last minute changes that might be breaking apis but I'm hoping to tag 1.0 within a week or two. Main thing right now is indexing replies so you can pull them into your post metadata.

It should be *mostly* stable :P

@mcollina Honestly I think your work back then is what set me on the path to making my own DBs. 🙇

@yeti@emacs.ch @badtuple Hell yeah. That's kinda what I've been wanting in @agregore

I actually support rendering gemtext loaded from *any* protocol (along with markdown, etc).

been thinking of making a new minimal markup for GUIs and WASM for interactivity.

@thomasreggi Yeah it's rough that the most "standard" js is for talking to external services rather than adding extra ones the way people do with Apache and the such. I guess one could plug node into a CGI script though :P

Personally I'm aiming to reduce the use of webservers in the first place and to rely more on static site publishing and client side rendering.