Oddbean new post about login | logout one point oh only, I have some beautiful parsing logic to try to guess at 1.0 support since the nip hasn't been merged yet:
```
export const hasNegentropy = (url: string) => {
const p = relaysByUrl.get().get(url)?.profile
if (p?.supported_nips?.includes(77)) return true
if (p?.software?.includes('strfry') && !p?.version?.match(/^0\./)) return true
return false
}
``` i recentlyish have full negentropy for any non-auth nostr1 v0.9.6-7
What what what? 👀
negentropy 👀😅
Wen negentropy? #askingforafriend
well, its on by default for non auth relays.. its just version 0.9.6 (so negentropy clients have to be version aware..) upgrade to 1.0 will happen at some point just havent gotten there quite yet.
I have a non auth relay. How do I control this?
on a public relay, the notes are public. since negentropy is a more efficient way to get the notes i havent seen a reason to turn it into an option. (scrapers are pulling the data already without it). i think clients may all use negentropy in the future. it is an option server side, if you feel strongly about it i can turn it off for your relay(s) and consider making it a UI option in the future. there was a bug in the rt proxy config that i did not realize was preventing negentropy, so i fixed it about a month ago..
I meant, how can I use it to pull notes from other relays onto theforest, instead of the faucet?
ohhhh 😁 i do have sync support, similar to stream, from any other (same version negentropy 0.9.6) ..