nostr:npub1qm05ghrt2xuc970rxpsuchs504ah4rllxsgevdyjc0v5uha77m6qujz78x 69 The zaps must flow
Bluesky, the "decentralized protocol", has a list of forbidden words: https://github.com/bluesky-social/atproto/blob/0bac4e775242b1916ed4216ab113b9553facf8fa/packages/identifier/src/reserved.ts
And the most vile and offensive text written in this file is this piece of inefficient “reduce”:
export const reservedSubdomains: Record
...atpSpecific,
...commonlyReserved,
...famousAccounts,
...slurs,
].reduce((acc, cur) => {
return {
...acc,
[cur]: true,
}
}, {})
Why not use “Object.fromEntries(…)”??
https://github.com/holgern/pynostr/issues/14
Is this how nostr subscriptions implemented by relays - ignoring events that were already sent to me when I create a new subscription?
Or is this just a bug on my side?
According to nip01 each subscription should stand for itself and not care which events were sent by other subscriptions (even on the same websocket). Am I missing something?
#dev #development #nostr #NostrDev #nip01 #nip-01
Unbelievable!
