Subnostr

finity

127d3bf58ca32e44b8eb8521900f27da0a75c77e8b06090c127805d6466f416f

This is an anonymous parody / comedy account operated by multiple contributors. All content is intended for satirical, humorous, and provocative purposes only and should not be interpreted as factual statements, endorsements, or representations of real events, persons, or opinions. Views expressed herein do not reflect those of any verified account owner, associated individuals, or entities. Any resemblance to actual persons, living or dead, or actual events is purely coincidental and unintentional. No offense, harm, or libel is intended, and this account disclaims any liability for misinterpretations or unintended consequences arising from its content. If the content offends you, please feel free to report / block / mute as you see fit.

bitcoin.org

Replying to

Vitor Pamplona

Nostr's main goal for 2025:

Figure out if we prefer single pubkey in all of our apps and thus a single main follow list, single notification feed for everything, single key to send DMs OR if we prefer owning multiple pubkeys, one for each app, so that follows, notifications, profile info can all be separate per app.

There are pros and cons in each. And any solution between those two gets really complicated.

For instance,

- If we use multiple keys, one per app, our DMs will also be on a "per-app" basis and senders for the DM wouldn't know which app you are still using to send you a DM. We would need to declare which key everybody should use for DMs with us.

- If we use just one key, we need to move away from our main follow list event so that each app can have their own follows and all sub-root event kinds (zaps, boosts, reactions, replies, reports, edits, etc) MUST also include the event kind of the root event so that each app can have their own notifications. Since it's impossible to require full compliance from ALL clients, it's likely that some notifications won't show up where they should.

- If we use multiple keys, friends of one app might not be readily available when @-tagging on a separate app. We can try to link all the keys so that Clients can always check information in the other keys to bring up to you, maybe as a fall back mode. But wouldn't that in the long term just create the same one-key for everything system?

Who knows...