it didn't restore your profile very well, i can't see it on my relays currently (nostr.wine nostr.land)

yes, this "replaceable events" thing in the protocol needs some work IMO

the hamster wheels will tick over duly thinking about this because i'm not happy with this part of the protocol, i think that "replaceable" should mean that the old versions are retained and there needs to be a way to request old versions

yeah, funny thing... in the code i work from it's horribly written, i've fixed most of it but finding a solution for this versioning issue would be cool af

Reply to this note

Please Login to reply.

Discussion

🤔 I wonder if that's because I no longer write to those two relays... Do you use any others?

It should use blaster to send it to any relay that will listen. Either that is down or relays have blocked mutiny's blaster instance

i use relay.primal.net also, and run my own relay.mleku.online

oh i see your update now, back to the old

no, i only use what i pay for, it's a moral thing with me

the replaceable events thing in my current project the implementation is nasty and imo, racy (as in, changes can fail to propagate properly) because it isn't built as a "newest version" instead of "replace when changed" model

i'm gonna go hard on this one, really grateful to you to trigger me to think about it and realise the model that exists is wrong

keep all versions, return teh newest unless you request old...

much better model than "replaceable" because that is such a temporally nebulous concept

This was always meant to be a temporary fix as it has a fundamental floor in that it required users to regularly log on to it.

There seems to be a trend of clients running a local relay, which gathers and backups events. I heard nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s discuss saving backups of profile events locally through this and nostrdb.