blob: cfca357fa23cc48ce0b7005b499a502ae236ed8b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
# NIPS to implement
- NIP-2 for follow lists
- NIP-25 for reactions (with content), kind 7. kind 17 with content
- NIP-17 for private DMs
https://github.com/nostr-protocol/nips/blob/master/17.md
- NIP-10 for mentions and replies ("marked e tags")
- NIP-18 for Quotes and RTs
- NIP-57 lightning zaps
- NIP-51 lists?
- NIP-22 replies?
# Relay discovery
https://nostr.watch/
# Tag specs
https://nostr-nips.com/#standardized-tags
- 'e' for event,
- 'p' for people,
- 't' for hashtag
- 'r' for relays
- 'd' for identifier # wtf?
- 'm' for mime type
- 'a' for event coordinates
- 'g' for geohash
# Things to note
- We put the nostr pubkey at the hash field of the trill-post
- No signatures
# TODO
- Default keypair that of groundwire comet?
lol forget the frontend make it work for Primal
# WTFs
- ~It appears relays ignore you if you pass more than 11 authors on a filter~
- Turns out the pubkeys were wrong because we were not padding the hex strings to 64 chars. fixed now
- Relay send a notice if too many concurrent REQs
# Hard stuff
It's hard to sync with the Nostr relays. We can fetch a bunch of posts and that's fine but then we want to fetch other data related to those posts, say the authors metadata or reactions or whatever. So we do it in bulk, but when? Nostr data keeps trickling in if we're subscribed through the shim.
|
