[Groxx]

I'm far from an ActivityPub or Mastodon expert, to be clear - I've just been lurking at the periphery of json-ld and its more-than-a-little-insane spec. It wouldn't surprise me at all if there were literally zero json-ld-compliant systems in the entire ActivityPub universe, even if you ignore stuff like validating remote schemas.

As it stands though: pleasantly readable code! I got curious and explored around a bit and it's all remarkably simple. Maybe it needs more error handling or auth or something and it'll grow before it's "ready", but it's nice to see something simple occasionally. You can probably keep a lot of those simple-structure assumptions if you frame your incoming requests to look like the common structure you're using now, if you can find a library that handles that for you: https://www.w3.org/TR/json-ld11-framing/ (which is a lot of text to say "it's a templating system")

[ckolderup]

yeah, I'm a professional software developer in my day job and a lot of times the thing that stops me from getting anything done in my side projects is over-engineering or using the kinds of best practices that I have picked up over my years of working on large teams with data that has to be carefully maintained/preserved. So when I started this I tried to just take the approach of "just make it work first". I'm glad you found it pretty readable! The fact that there's so little error-checking and rigor in general has definitely burned me a lot in the run-up to feeling able to share things, though. It's a real double-edged sword, especially in a language as weakly typed as Javascript (which is also not my first choice of language, but targeting Glitch for deploying this was ideal for spinning up test instances, and that's their main platform)