17
205
Fork
You've already forked human.json
6

Extension: Allow trusting sites without human.json #39

Open
opened 2026年03月24日 15:38:54 +01:00 by kytta · 3 comments

I've been using the extension for a few days, and it's been very nice. However, I was hoping for the extension to be a sort of "vouch manager" for my human.json.

Basically, the workflow I imagine:

  1. I visit some website
  2. I am sure the owner of that website is a human, so I trust them
  3. I keep browsing the web and collecting URLs
  4. Periodically, I export the human.json and push it to my website's root to update my own vouches.

Right now, the step 2 does not work if the site I'm visiting does not define a human.json file. I just can't click the button and have to add them myself.

I guess this makes sense: After all, what path should I trust when visiting a subpage. Do you have ideas on how this could be implemented? Maybe a text field to add generic URLs to the "trust store"?

I've been using the extension for a few days, and it's been very nice. However, I was hoping for the extension to be a sort of "vouch manager" for my human.json. Basically, the workflow I imagine: 1. I visit some website 2. I am sure the owner of that website is a human, so I trust them 3. I keep browsing the web and collecting URLs 4. Periodically, I export the human.json and push it to my website's root to update my own vouches. Right now, the step 2 does not work if the site I'm visiting does not define a human.json file. I just can't click the button and have to add them myself. I guess this makes sense: After all, what path should I trust when visiting a subpage. Do you have ideas on how this could be implemented? Maybe a text field to add generic URLs to the "trust store"?

I think we could add a "Trust Anyway" button when the website doesn't have a human.json, and give the user the option to edit the URL before trusting? For example:

  1. I visit https://alice.example.com/posts/2026/01/01/hello-world.
  2. There's no rel="human-json" in the page.
  3. I see in the extension: "Not participating in human.json", and the button "Trust Site Anyway".
  4. A modal pops up with the full URL, and I can shorten it to, say, https://alice.example.com/posts/.
I think we could add a "Trust Anyway" button when the website doesn't have a `human.json`, and give the user the option to edit the URL before trusting? For example: 1. I visit https://alice.example.com/posts/2026/01/01/hello-world. 2. There's no `rel="human-json"` in the page. 3. I see in the extension: "Not participating in human.json", and the button "Trust Site Anyway". 4. A modal pops up with the full URL, and I can shorten it to, say, https://alice.example.com/posts/.

Can't this already be done by adding it to your own human.json? I suppose not everyone has a website, so maybe it would be better to be able to produce one's own human.json within the extension (and then optionally export this so we can distribute it via our own websites).

Can't this already be done by adding it to your own `human.json`? I suppose not everyone has a website, so maybe it would be better to be able to produce one's own `human.json` within the extension (and then optionally export this so we can distribute it via our own websites).
Author
Copy link

@addisoncrump wrote in #39 (comment):

Can't this already be done by adding it to your own human.json?

Yes, but my ultimate goal is to not have to do it. I want to have a GUI for my JSON file :D

@addisoncrump wrote in https://codeberg.org/robida/human.json/issues/39#issuecomment-12061719: > Can't this already be done by adding it to your own `human.json`? Yes, but my ultimate goal is to not have to do it. I want to have a GUI for my JSON file :D
robida added this to the v0.2.0 milestone 2026年04月05日 00:25:57 +02:00
Sign in to join this conversation.
No Branch/Tag specified
main
spec-0.2.0
crawler
No results found.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
robida/human.json#39
Reference in a new issue
robida/human.json
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?