This whole Damus relay #theNuking thing, got me thinking. Why not have some relays that are space limited?
say 50gb, the notes get stored in a nuking que destorying the okdest notes asap when space limit is reached.
View quoted note →
Login to reply
Replies (9)
From time to time I consider my own relay and I think “short term” storage of notes to be sufficient for most use cases. This would be the kind of thing I would do.
Short term storage is in some sense more natural for more conversational stuff. Like talking to people irl, are generally a short storage event.
Btw, for huge relays another idea would be a similar que system; but counted in notes per npub. aka free storage 1k notes per npub the delete the oldest.
These would be caching relays, which is a good idea for a speedy and responsive UX. The most boosted, quoted, commented notes would be on the most relays and would increase response times when needed. Sounds like a good idea.
Yes! Good point! Boosts, quotes and interactions provide redundancy. An interesting perspective, with a sort of "marketplace" for what's to store & protect :)
Yup, for larger media, video and audio, this could be even more signifigant and help with load balancing and bandwidth.
This situation reminds me of that time the #kafka queue grew to 150GB and stayed there. I said, "I thought this thing was a queue!" and the boss replied, "If you never delete anything, a queue is just more storage!"
FINO: First In, Never Out!
love the parody name; kafka-queue xD
It's a real piece of free software (if you didn't already know; my irony detector is sometimes impaired).
The inspiration for the name is ironically unironic: 'Jay Kreps chose to name the software after the author Franz Kafka because it is "a system optimized for writing", and he liked Kafka's work.'
Apache Kafka - Wikipedia
ahhh, interesting. I thought it was a joke first. Thanks for the article link. Might look further into this, it seems useful for a nostr relay. :)