![browser page, address showing "http://0.0.0.0:8080/.well-known/webfinger?resource=acct:user@example.com&rel=google.com&rel=blah.net", content is only "Webfinger request made about acct:user@example.com with rels [google.com, blah.net]"](https://media.tech.lgbt/media_attachments/files/113/306/601/222/900/021/original/d16756a84012ece6.png "browser page, address showing \"http://0.0.0.0:8080/.well-known/webfinger?resource=acct:user@example.com&rel=google.com&rel=blah.net\", content is only \"Webfinger request made about acct:user@example.com with rels [google.com, blah.net]\"")
And on that note --- I'm ditching #ActivityPub proper.
That is, actually parsing JsonLD.
I'm working months on getting it to work. I've now got a runnable thing within 5 minutes.
Protocols are made to make implementation easier. When the protocol makes it harder, why bother?
@laxla I'm still holding hope that I'll find that sweet spot in which the encoding/decoding will be easy to do, and all the other JSON-LD functionality can be adjacent to it. Your words are not giving me hope though. :(
@mariusor I seriously tried. A big part of it is KotlinX Serialization needing a 2.0. But ADHD just doesn't let me continue work on something so tedious and fruitless.