highperfocused/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2025-09-27 20:16:57 +02:00
Code Issues Packages Projects Releases Wiki Activity

clean up B0. (#2039)

Browse Source
This commit is contained in:
AsaiToshiya
2025-08-23 08:20:13 +09:00
committed by GitHub
parent 84e0b44f93
commit 3f4c696f24
1 changed files with 7 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
B0.md
View File

@@ -6,31 +6,23 @@ Web Bookmarking
`draft` `optional`
This NIP defines `kind:39701` (an _addressable event_) for a URI as a web bookmark which uses the HTTP (Hypertext transfer protocol) scheme.
These web bookmark events are _addressable_ and deletable per [NIP-09](09.md).
### Editability
Web bookmarks are meant to be editable, so they should include a `d` tag with an identifier for the bookmark. Clients should take care to only publish and read these events from relays that implement that. If they don't do that they should also take care to hide old versions of the same bookmark they may receive.
This NIP defines `kind:39701` for a URI as editable web bookmark which uses the HTTP scheme.
### Format
The format uses an _addressable event_ of `kind:39701`.
The format uses `kind:39701`.
The `.content` of these events should be a detailed description of the web bookmark. It is required but can be an empty string.
The `.content` should be a detailed description of the web bookmark. It can be an empty string.
The `d` tag is required.
The `d` tag is just their URL without the scheme, which is always and everywhere assumed to be `https://` or `http://`.
In this way web bookmarks events can be queried by the `d` tag by clients, which is just their URL without the scheme, which is always and everywhere assumed to be `https://` or `http://`.
The querystring and the hash must be removed entirely, unless their requirement is explicitly stated either by the user or by some hardcoded list of URLs that rely on querystrings for basic routing provided by the client.
In this way web bookmarks events can be queried by the `d` tag by clients.
### Metadata
For the date of the last update the `.created_at` field should be used. For "tags"/"hashtags" (i.e. topics about which the event might be of relevance) the `t` tag should be used.
Other metadata fields can be added as tags to the event as necessary.
Metadata fields can be added as tags to the event as necessary.
* `"t"`, for "tags"/"hashtags" (i.e. topics about which the event might be of relevance)
* `"published_at"`, for the timestamp in unix seconds (stringified) of the first time the bookmark was published
* `"title"`, title about bookmark and can be used as a attribute for the HTML link element