Got it, thanks for the heads-up. I’ll check what’s going on.

Jumble currently only subscribes to gift wrap events whose p tag contains the user’s pubkey, since some relays only allow subscribing to gift wraps that mention you. But when Jumble builds a gift wrap event, it mentions both the user’s public key and the encryption public key. I remember Coop does it this way too

Cool!

I didn’t quite follow what you were talking about.

Looks like I need to add some logging.

I'm not sure what happened either haha. I didn't get any unsafe warning on my end.

Got it 🫡

Jumble only supports NIP-4e. If those are NIP-4e gift wrap events, then there might be a bug preventing them from showing up.

There’ve been more and more AI bot replies in the feed, and most of them use Markdown. So I already made a bit of a compromise a while ago. But I don’t want Markdown to make the feed look messy, with all sorts of font sizes and inconsistent styling, so I’ve only added very basic support for it. # Heading 1 ## Heading 2 ### Heading 3 This is **bold** text, this is *italic* text, and this is ~~strikethrough~~ text. - Item one - Item two - Item three 1. First 2. Second 3. Third > This is a blockquote. `inline code` [Jumble](https://jumble.social)

My certificate shouldn’t be expired. Is your device’s date and time set correctly?

I’m not sure why, but I can’t view that video. I just tried it myself and was able to share the encryption key successfully.

No idea what caused that, but I’ll note it down for now.

Supported now

Alright, I really need to dig into what’s causing this.

Only the encryption and decryption use a separate key. The recipient is the same as in NIP-17. https://github.com/nostr-protocol/nips/blob/per-device-keys/4e.md

Do you see the same issue in a regular browser as well?