Subnostr

Why can't we add more than one profile picture and banner?

Is it not possible to keep the previous pictures and banners?

#asknostr

Reply to this note

Please Login to reply.

Discussion

You mean like a photo album for your profile pic ?

Yup

Interesting idea. Would you be the only one who could change it or whoever comes to your profile could browse through it ?

I would like the swipping version. Just like telegram.

I did not know you could do this on telegram 👀

You can do pretty much anything there

Do you need a premium account for that ?

Of course #nostr has this unique feature that I can see my old banner in #Iris and my new banner in #amethyst 😬

Are you using the same relays on both apps ?

Probably not the all set.

Could be what’s creating the discrepancy

The Daniel 🖖 2y ago

Like Facebook does? Probably needs a NIP to allow something like that.

highperfocused ⚡ 2y ago

Clients could also load older pictures if the relay is sending this data. But in NIP-1 (kind: 0) there is defined:

A relay may delete older events once it gets a new one for the same pubkey.

highperfocused ⚡ 2y ago

https://github.com/nostr-protocol/nips/blob/master/01.md

highperfocused ⚡ 2y ago

But it is possible.

Can we call it the sad Nip or "gone with the NIP" ?

highperfocused ⚡ 2y ago

Well I think a lot of relays also sending older kind: 0 events. So it's up to the clients how to show it. I think this would be quite easy to implement

I think " why would you want to change the trivial fun things that people are already used to from the legacy social media?"

highperfocused ⚡ 2y ago

Maybe I will add this feature to beta.nostrid.online soon

highperfocused ⚡ 2y ago

When I get some free time for it :)

<old>cypherhoodlum 2y ago

When you modify your profile in any way a Nostr event is created where all profile details are squashed together in a single JSON block. To make profile pic albums possible:

1. Relays should not delete old profile change events so that Nostr clients could parse the older profile pic urls from the old JSON blocks. This is pretty wasteful but would work.

OR

2. Profile pics should be its own NIP where the user can publish only the new set of urls without other profile details. This would work but it would also fragment profile handling making it more complex.