mirror of https://github.com/hzrd149/blossom.git
Revert "BUD-03: Implement 'fallback' tag"
This reverts commit cc159819bfeb4ae70b234307588faeb89d118925.
This commit is contained in:
parent
6d1c6f793d
commit
329d8a69e9
14
buds/03.md
14
buds/03.md
|
@ -4,13 +4,10 @@
|
|||
|
||||
`draft` `optional`
|
||||
|
||||
Defines a replaceable event using `kind:10063` to advertise the blossom servers a user uses to host their blobs, or to retrieve others' blobs if the original source is not available.
|
||||
Defines a replaceable event using `kind:10063` to advertise the blossom servers a user uses to host their blobs.
|
||||
|
||||
The event MUST include at least one `server` tag containing the full server URL including the `http://` or `https://`.
|
||||
|
||||
The `fallback` tag is optional, it has the same structure of the `server` tag.
|
||||
It is used to identify a server where the user expects to find others' blobs if the original source is not available and the author doesn't offer alternative working locations using their own server list.
|
||||
|
||||
The order of these tags is important and should be arranged with the users most "reliable" or "trusted" servers being first.
|
||||
|
||||
The `.content` field is not used.
|
||||
|
@ -25,7 +22,6 @@ The `.content` field is not used.
|
|||
"tags": [
|
||||
["server", "https://cdn.self.hosted"],
|
||||
["server", "https://cdn.satellite.earth"]
|
||||
["fallback", "https://backup.my-server.com"]
|
||||
],
|
||||
"sig": "cc5efa74f59e80622c77cacf4dd62076bcb7581b45e9acff471e7963a1f4d8b3406adab5ee1ac9673487480e57d20e523428e60ffcc7e7a904ac882cfccfc653"
|
||||
}
|
||||
|
@ -56,8 +52,6 @@ In all the following examples, the hash `b1674191a88ec5cdd733e4240a81803105dc412
|
|||
|
||||
In the context of nostr events, clients SHOULD use the author's server list when looking for blobs that are no longer available at the original URL.
|
||||
|
||||
If the author's list is not available or the blobs are not retrievable, client SHOULD fallback on the user's `fallback` hosts and try to retrieve blobs from them.
|
||||
|
||||
Take the following event as an example
|
||||
|
||||
```json
|
||||
|
@ -76,9 +70,7 @@ Once the client discovers that the URL `https://cdn.broken-domain.com/b1674191a8
|
|||
|
||||
1. Get the SHA256 hash from the URL
|
||||
2. Look for the authors server list `kind:10063`
|
||||
3. If found, attempt to retrieve the blob from each `server` listed started with the first
|
||||
4. If not found, the client SHOULD look for the user server list `kind:10063`
|
||||
5. If found, and if at least one `fallback` tag is present, attempt to retrieve the blob from each `fallback` listed started with the first
|
||||
6. If not found, the client MAY fallback to using a well-known popular blossom server to retrieve the blob
|
||||
3. If found, Attempt to retrieve the blob from each `server` listed started with the first
|
||||
4. If not found, the client MAY fallback to using a well-known popular blossom server to retrieve the blob
|
||||
|
||||
This ensures clients can quickly find missing blobs using the users list of trusted servers.
|
||||
|
|
Loading…
Reference in New Issue