I’ve published a human.json file (inspired by @neatnik).

[shellsharks@shellsharks.social]

I’ve published a human.json file (inspired by @neatnik). You can see the file here…

https://shellsharks.com/.well-known/human.json

The origin for human.json can be read about here: https://codeberg.org/robida/human.json

To start I only have Adam and @mttaggart in there but would love to vouch for some other actual humans! If you have a website, with content that is not AI slop, I know you in some way from the web/Fedi, and would like for me to “vouch” for your site in my human.json file, let me know and I’d be happy to do so!

[mttaggart@infosec.exchange]

@shellsharks @neatnik Yo, this looks shockingly like what I'm attempting with Ringspace!

[shellsharks@shellsharks.social]

@mttaggart @neatnik This is *exactly* what I was thinking too. I was reading through the ringspace docs recently actually (finally, I know), so when I was reading the human.json spec this is the first thing I thought of. I like the truly decentralized approach to human.json but as you mention in the ringspace spec, this leave a lot to “trust” with less technical guardrails in place ‍️.

[winterknight1337@infosec.exchange]

@shellsharks @mttaggart @neatnik

Wonder if I could put content in well known on ghost.

[mttaggart@infosec.exchange]

@winterknight1337 @shellsharks @neatnik If self-hosting, probably? If nothing else, a webserver route handler would do the trick. This was one of the tradeoffs I considered in Ringspace. This all could have been done via DNS, similar to DIDs. Ultimately I decided I cared more about folks with access to their web root than I did folks with control of a domain name.