Signed in
Identity here is Hugging Face's. This registry holds no password and has nothing to sign up for; signing in makes a record at the identity service behind this site, which is how a submission is known to be yours and is the whole of what an account means here. Reading this site needs none of it: browsing, comparing, following a pin and downloading an artifact are anonymous and stay that way.
Hugging Face will ask whether to let this registry read who you are: your opaque subject id, the handle you hold at this moment, and the organizations it says you belong to. It is not asked for write access to anything, and it is not asked for your email.
Signing in writes no submission and publishes nothing. The session lives in this tab and closing it ends it. Whether to send anything is a separate press, further down, after you have read what it would send.
Reading what Hugging Face says about this account.
What Hugging Face said, and when it said it
- handle
- subject
- read at
Nothing rechecks any of this, so nothing here will ever claim you belong to an organization now. People join and leave; a membership read once and held forever goes stale quietly while still looking like a fact. Checking again means signing in again, which is a second reading beside the first rather than over it.
One JSON file. It is the evidence a namespace claim is made from, and it carries no token.
Submit a direction
Your namespace is , which is the handle Hugging Face reported when you signed in. There is no field for it and no default to type over. What that makes impossible: publishing under a pseudonym, under a lab name you hold no account for, or into one namespace shared by several people who each sign in as themselves.
A submission is a pointer to bytes a stranger can fetch. If your repository is private, the section below will publish the one file to your own account, with your permission, and then fill in the pin.
The file is not at a public URL yet
This registry can put one file in , your own account, in a new public repository, and then fill in the repository, the commit and the path above. The bytes go to your account and never to this project's, which is a different column in the schema and a different question.
Hugging Face will ask you for one more permission at that point and not before: creating repositories for this app, which cannot reach any other repository you own. The token is used for that upload and is not stored, logged or written anywhere.
A new one, under your namespace. An existing one stops the offer rather than being written into.
The same string the client will fetch by, so it is also the path recorded on the row.
It is read in this tab and sent to Hugging Face. It does not reach this site, which has nowhere to receive it.
Something is absent and you want to say why
An absence is a positive statement with a reason, never an omission and never an error. One line per field, as field: your sentence. The field name is any string; it is not checked against a list.
A field cannot carry both a value above and a reason for having none. That is two claims about one field, and the author's rebuild refuses it rather than picking one.
Your submission
Nothing has been sent yet. This is the record. Read it, then send it.
Sending puts this record and three columns beside it in a holding table: the account, the subject and the handle, all three taken from your signed session by the database rather than from anything above. So a submission cannot claim to be from somebody it is not. The copy is for you; it is not needed for anything and nothing here depends on your keeping it.
Reading it later fetches the bytes at the pin, checks them against what this record says, writes the row and rebuilds the site. The shape, the dtype, the norm and the digest are read off the bytes on that machine rather than computed here, because one thing in this project reads bytes and a second implementation of it is the failure this repository has hit most often. A pin nobody can fetch is refused there, with the reason.
Received
- received at
- row
- stamped handle
- stamped subject
Those four are what the database wrote, read back off its answer rather than off what this page sent. The handle and the subject beside them are the ones your session carries; the record above carries the browser's own copy of both, and where the two disagree the stamped ones are the ones the author reads.
There is no way to edit or withdraw this from here, on purpose: a submission is a statement somebody made at a time, and a correction is another submission. Mail the author if you need one removed.
What this page is not
It is not an account. It is not a queue, and nothing here is reviewed, ranked, counted or ordered. It keeps no cookie and writes down no token. The one thing it writes is the submission you send, and nobody else can read it. A namespace takes any number of claimants, and two people claiming one name render as two claims with their dates rather than as a conflict anybody here resolves.