Mastodawn

Inspired by the flurry of activity around human.json, I've added one to my personal site: https://coreysnipes.com/human.json

If we know each other here, and you'd like to be added to my vouch list, reply here or send me a message.

Thanks to @neil for sharing his shell script. Super handy for adding an entry from the command line:
https://mastodon.neilzone.co.uk/@neil/116302477331818581

And here's the backstory on human.json: https://codeberg.org/robida/human.json

Show thread

Corey Snipes 🌱3d ago

I posted my process for adding a human.json file in the #publii static website CMS, in case that is useful to others. https://coreysnipes.com/add-a-humanjson-file-to-a-publii-website.html

Add a 'human.json' file to a Publii Website

I use Publii for website content management. This week, inspired by the flurry of activity around the new human.json protocol, I decided to add it to my website. Here’s the process I followed. I'm currently editing the human.json file by hand, which you'll need to do as well. Stepping through... Make list somewhere convenient. Start with a couple of websites that you know and trust. Don't forget to include the leading 'https://'. At the time of writing, this is required…

coreysnipes.com

Show thread

Ed Davies 20h ago

@coreysnipes Yours is the third human.json file I've looked at. It's also the third not to be served with the Access-Control-Allow-Origin: * header which the protocol requires.

I'm not sure but I think it's required to allow the plug-ins to fetch the file from your site when they're running because the user is reading another site which references yours.

Show thread

Corey Snipes 🌱20h ago

@edavies Ah, thank you for the tip. My personal site is on shared hosting, and my options for setting headers on individual files are limited. I'm guessing others may be in the same boat.

Show thread

Ed Davies 13h ago

@coreysnipes I see your site is served by LiteSpeed. I hadn't previously heard of that and my knowledge is limited to the first paragraph of its Wikipedia entry but that does say:

The software uses the same configuration format as Apache HTTP Server and is compatible with most Apache features.

It depends, I think, on how your server is set up but you may be able to put a .htaccess file in a suitable directory. When I first looked at @neil 's file it was directly in the root of his site ('/human.json') but later I saw that he had put it in a subdirectory ('/human/human.json'). I assume that's so that he can put the .htaccess file there and not set the header on other files.

The actual line needed in the .htaccess file would be:

Header add Access-Control-Allow-Origin "*"

OTOH, your host might not process .htaccess files within your directories in which case you'd need a better one.

Show thread