This is because in Preview mode, clicking the image opens the Lightbox, and closing the Lightbox also ends up closing the editor modal. I haven’t figured out a good way to fix that yet, so I disabled all click interactions in Preview mode as a workaround.

If you know how to solve it, a PR would be very welcome :)

Just remember to keep it updated regularly 🫡

Your current setup looks fine to me 👍

Thanks for the details 🫡

When browsing the follow feed, Jumble currently only uses the first four write relays set by a user. Unfortunately, none of the first four relays she configured contained her posts, and they also seem to be unreachable.

Jumble clearly needs a smarter strategy here, such as skipping invalid or unresponsive relays. I’ll spend some time improving this in the future.

May I ask which user and which post you’re referring to? That would help a lot with troubleshooting. 💜

In theory, as long as the post was published to their write relays, Jumble should be able to fetch it.

Because it’s currently just a Nostr event kind-based filter, as indicated below (kinds 21, 22, 34235, 34236). As a result, videos published as kind 1 events also get filtered out.

I understand this is quite unfriendly from a user perspective, and I’ll look for a way to improve it.

Could you share the exact filter configuration you’re using, and which specific notes are being filtered out incorrectly? 💜

I think so too, it might be a network issue.

Give the latest version of Jumble a try 🫡

Yes, if an edit is implemented as a special kind of quote and is still a kind-1 event, then it would indeed be more compatible than Amethyst’s approach. However, it would also make the already complex semantics of kind-1 events even more complicated.

There’s an ongoing discussion about editing here, which you might want to check out: https://github.com/nostr-protocol/nips/pull/1090

The feature itself is quite controversial. Personally, I’m not in favor of editable notes at the moment. I consider them harmful overall, even if an "edited" marker is added.

The main issue is that many other clients can’t display this information. On those clients, users would only see the unedited content.

I get why many users want an edit feature, but I don’t want to implement something that’s essentially self-deceptive. Users should be clearly aware that once something is signed, it’s immutable.

An "edit" in practice is just publishing another event that says what you changed. Not all clients support this, and I’m worried users might assume everyone only sees the edited version. I think adding clarifications via replies is a better approach, since that’s visible to everyone across all clients.