Thread

Replies (44)

jellyfish uses immortal as it's software. we have 2 layer of protection for this issue which help us to stop double processing of an event, stop rewriting of deleted and vanished events. 1. a redis bloom filter which keep track of all events seen by relay. so if someone send an already processed event, we will reject immediately. so, a deleted event is a event that were processed in past! 2. we don't delete a record on mongo db, we update it and remove all fields of it except its id. so it's basically just a nonsense hash. when someone try to write it again, (if we lost redis data for any reason.) we don't write duplicate ids on database and write operation will fail. you can take a look at code:
As with everything it is a multitude of small things that influence my decisions… but: On the surface I’d say I wasn’t able to find ways of using it that fit my needs/wants. I seek creative collaborations I guess. I enjoyed my time on stemstr but that β€œdied”. I don’t see media being taken seriously yet. The echo chambers I fell into have a tendency of rubbing me the wrong way. On the deeper side Nostr made me understand that my fascination with Bitcoin has more to do with Game Theory than Cryptography. There are no incentives on Nostr to play fair. Not for the relays, not for the clients, not for the users. Add to that the hypocrisy of major players in this space, shouting that V4V is the only way all while signing investment contracts for clients and media players. Monetization has to be sorted out. Sats have to flow and being redistributed constantly to participants and infrastructure. image