-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
> One adjustment to the protocol that seems to me like a quick win (but presumably has some technical hitch I can't see, since I don't recall anyone suggesting this) would be to not include the post's body in the “block” (in the message itself that gets hashed and signed by the next message), but rather as a “blob” (essentially an attachment) which others don't need to download in order to verify the feed.
There's nothing to prevent you from taking this route, you just sign a blob hash instead of an entire message object.
I work on an experimental SSB-like-protocol in my spare time that does exactly what you've suggested: https://github.com/evbogue/bogbook
I don't know if this makes the network forget more, but the aim is to reduce the time it takes to sync and get started.
Yes, you delete by appending a delete event:
https://github.com/nostr-protocol/nips/blob/7d792055372ce1af...
Then clients and relays SHOULD act as if the referenced event is deleted. This is different than MUST, probably because there’s no way to guarantee it happens. It’s also possibly the delete event don’t make it to everywhere that received the initial event.
Related posts
-
Ask HN: What are your favorite tiny, single purpose tools?
-
Minisign A dead simple tool to sign files and verify signatures
-
GitLab: Authentication and Signing with SSH Keys
-
Vault1317 FAQ: deniability for decentralized approach via XMPP and Nostr
-
vault1317 FAQ: cryptographic deniability for decentralized approach via federation (XMPP) and relay (Nostr)