It's live, Fevela now lets you react only with the standard + (rendered as a heart); consequently it counts only positive reactions in the count, and the row of different emoji is gone. Anyway, in the details tab you can still see all the single reactions, including negative ones. A simpler interface and a little push to engage more during the interaction by sharing a more personal comment (where you can include any emojis you like, as many as you want!). View quoted note →

I'm wondering how notifications should work in NIP-29 groups. If events are submitted only to the designed relay, users cannot be notified of any reply/mention/etc without having a running NIP-29 client, connected to that specific relay; this is clearly a quite annoying limitation. For example Pokey cannot manage this kind of notifications. Publishing also to the user's read relays is an option; a client that fetches those events and know the NIP-29 spec, can try to fetch the context and show it, or at least explain the nature of the notification (or simply ignore them, of course). But I suppose it's not the suggested way since it creates some chaos, and above all for private groups it exposes content and dox the presence of the user in the group itself; both of these things must clearly be avoided. Maybe we can broadcast to read relays only when the group is public/open, never for closed groups. I would avoid any "encrypted notification ping" (e.g. via NIP-44), it's a mess. @hodlbod @fiatjaf @verbiricha any thoughts?

> Be kind to community CDNs and other users This is a really important point to globally improve the Nostr experience for everyone, and especially for newcomers. Clients should take responsibility and pay more attention to (offer to) optimize the media they upload, starting from profiles photos, which are often excessively large. Let's call it #nostriquette View quoted note →

The Tiny UDP Cannon: An Android VPN Bypass

The Tiny UDP Cannon: An Android VPN Bypass

An unprivileged Android app can leak the user

@MetropleX [GrapheneOS] ⚡🟣 @Final does this also apply to GrapheneOS?

#Chronicle v0.6.0 suffers a weird bug related to negentropy and after a few days it slows down. I need to investigate the issue but in the meantime to alleviate the problem negentropy is gated behind NIP-42 auth by default, you can switch it off using NEGENTROPY_AUTH env or disable negentropy entirely via NEGENTROPY. Upgrade to v0.6.1 from

GitHub

Release v0.6.1 · dtonon/chronicle

Manage negentropy NIP-42 auth using the NEGENTROPY_AUTH env Disable negentropy using NEGENTROPY env

KISS good UX View quoted note →