Doug Hoyte

Last Notes

2026-04-10 13:05:21 UTC

- reply

I think clients must be written to handle the case of individual relays missing/deleting data. If you're low on disk-space, not much choice!
You could have some kind of heuristics that delete unneeded notes, and keep the important ones (whatever that is for your use-case).

2026-03-19 17:43:52 UTC

- reply

This is the first I'm hearing of it. Can you please point me to any more details? I don't see anything related to negentropy in the commits you referenced.

2024-12-20 19:44:48 UTC

- reply

Yep looks like the same approach to me.

2024-09-13 19:33:28 UTC

- reply

NIP-77 I believe is still a draft/work-in-progress, so I don't know the final form yet.
I think fiatjaf's intent was just to standardise the nostr integration, rather than negentropy as a whole. I guess this is similar to how JSON/SHA256/secp256k/etc are not themselves specified in NIPs, but instead external specifications are referred to. That said, the negentropy spec is relatively straightforward and there are already at least 5 implementations (and I know of some more in development too): https://github.com/hoytech/negentropy/tree/master?tab=readme-ov-file#definitions
> It also doesn’t seem to cover the actual sending of events in either direction (after the sets have been reconciled).
True, but by design this is out-of-scope of the negentropy protocol. Negentropy just performs a set reconciliation so the client knows which IDs it has and/or needs. It is then up to it to decide what to do. Currently `strfry sync` will post events it has with regular EVENT messages, and/or download events it needs with regular REQ messages.
However, there are a lot of other possibilities. If a client is only interested in uploading (or downloading), it may only do one of those actions. In fact it may just store those IDs and fetch them later, or through some other relay or mechanism. Alternatively, if a client doesn't actually care about the event contents and is only trying to compute an aggregate "reaction count" across relays, it may never actually download the events, and purely use negentropy for de-duplication purposes.

2023-09-29 13:19:39 UTC

- reply

FWIW I agree with you. Right now the front page is really boring. I have some ideas and I'm working on it!

2023-06-09 19:03:00 UTC

- reply

Hi! Yeah, sorry, the sync support has been broken for a little while. However, this is now fixed in the `next` branch and very soon there will be a 1.0.0 release with this included.