Finally happened, the new #Amethyst update nuked the majority of my followers/follows. It's been super stable for me up to this point, growing pains are expected.
#grownostr
Discussion
hmm. im not saying it wasn't Amethyst, but i've never seen this happen with Amethyst. it could have been another client? you can try restoring your contact list by visiting metadata.nostr.com and signing in with a browser extension. alternatively, you can use citrine to restore your contacts, if you're using citrine.
I thought the same, but it just took a looooong time to populate again.
Could have been it, I added some new relays and it restored, so I'm not sure.
this is an event that i have written specific handling code literally today and yesterday to prevent happening on the relay side, after OxChat nuked my mute list
i was able to recover it because it was cached in coracle android and i modified the list and saved it and it republished it
the fix i've made with #realy is that it simply does not ever delete a specific list of event kinds like this, even when they are replaced, so the relay at least keeps a copy of the old version, which you could find with a query, haven't written the recovery stuff yet but it's there ready for it now
Is that encrypted, like app data? Cuz, someone might delete it, for privacy, when moving to a self-managed relay.
Like the idea, tho. Just wondering. Although, I guess you could just not-serve it to anyone other than the originator.
that was already done a long time back, i have a test in the kinds library that categorises sensitive data and it is used to filter subscriptions and requests from matching on it without being a relevant party with auth enabled
DMs, giftwraps, and application specific data...
https://github.com/mleku/realy/blob/dev/kind/kind.go#L45
these are events that should, with auth enabled, never be sent out to any npub without their npub appearing in the event (either author or tagged)
deleting all of your data from an old relay is another function i have plans in mind for later implementation
Like a delete-blastr, where you choose where to blast to?
oh, you are entirely out of luck if you want to know about relays that actually implement delete, as far as i know, almost none do
blasting out delete events for your entire event set would work, where it is honored, you have to gather the entire set of event IDs to do it, for good reason there is no blanket delete ability in delete events
Well, there is the NIP PR for a blanket-delete, but it's permanent.
it's a stupid idea
it's a big red button with a flimsy shield around it that malicious parties will use to harass users with when the client has a vulnerability
Well, Vitor needs it for some particular health application, for compliance. 🤷🏻♀️
compliance ™️ https://youtu.be/QP3zRBtgvJo https://youtu.be/aU3xJH2dgb0
yeah, i think GDPR or whatever acronym shit from the EUSSR
it's a nice feature but it is just a query strategy and follow that up with a set of delete events crafted from the IDs
i forgot the third one
literally three of my all time favourite music artists all converged on this one subject
i will say though, that Snog was 10 years ahead of them both, muse and combichrist only did theirs during the lockdowns, when the word was very hot
David Thrussel lives in Hellstralia where they do everything 10 years before the rest of the world, or even sooner
this track from combichrist is really more in the vein of Icon of Coil though... and i don't understand what the inverted crosses in the video are about, some hipster shit
this is again a muddled-domain architecture issue
like nip-86, this is mostly stuff that can be done with existing data structures or interfaces, or is at the level of the database or relay service provision tooling
i also have to be careful with muddling domains up, i can't emphasise enough the importance of respecting domains and not crossing the lines between them because almost all bugs and vulnerabilities come from it
this is the commit that makes the fix: https://github.com/mleku/realy/commit/40915cce13617f255d3dfab73b95fcca84c5619c
Thanks for the support nostr:nprofile1qqsr7acdvhf6we9fch94qwhpy0nza36e3tgrtkpku25ppuu80f69kfqpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7x08grv, nostr:nprofile1qqsyeqqz27jc32pgf8gynqtu90d2mxztykj94k0kmttxu37nk3lrktcpz9mhxue69uhkummnw3ezuamfdejj7qg3waehxw309ahx7um5wghxcctwvshsz9nhwden5te0d4kx26m49eex2ctv0yhxcmmv9ume3twc, nostr:nprofile1qqs06gywary09qmcp2249ztwfq3ue8wxhl2yyp3c39thzp55plvj0sgprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qguwaehxw309a6xsetrd96xzer9dshxummnw3erztnrdakj7qgmwaehxw309amksetpwshxsctswpuhgctkv4exutnrduhsw0qlr4. I think the history relay did the job and I'm back to normal.
This is all akin to black magic for me. I say some incantations, sacrifice a goat and good things happen 😂. I'm going to do some reading and experimentation over the Christmas break to stop being such a Luddite.
i'm glad you recovered your list... this happened to me before and is why i am very skeptical about trying new clients nowadays, the number of times they have nuked lists on me, and i've now added features to my own relay so worst case i can at least recover my old event from my personal relay
my case was even more obscure, my mute list got clobbered by OxChat
Yeah I've always just stuck to Amethyst after seeing people saying it had happened.
amethyst has done well because it got a lot of users and it's one of the early ones... maturity of the code is really important, it takes time to find all the bugs, and ... yeah, unfortunately, i don't want to be a tester on stuff so much after a few disturbing incidents
i have a minor advantage as a relay dev because my userbase is inherently going to be a lot smaller and i test it myself so it will be really solid by the end of this year i think, i mean, like strfry legendary crystalline
it will come the lite fork of amethyst just after the main user base asks for features everytime more and more fashion-ish...
in due course... 🐸 ⌛
that's one of the big advantages of open source... people can make "lite" versions and special purpose and whatnot
it may seem like it is quite a bit of work to whitelabel a source code but actually the refactoring involved in doing so tends to uncover hidden bugs as well, i certainly have found this in the past with my work, the more i make it reusable the more solid it becomes
