Cody

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

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

Got it 🫡

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?

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

Thanks for the feedback! Fixed now

Supported now

I’ll let AI take a look and try to track it down. Honestly I have no idea where the problem is haha.

I intentionally left this unhandled, hoping other clients will remember to add the nostr: prefix to avoid unnecessary protocol bloat. https://github.com/CodyTseng/jumble/issues/154#issuecomme…

I think that’s because you set a localhost relay. Almost all of Jumble’s code runs directly on your device. I don’t collect any data at all, I don’t even know how many people are using Jumble, so there’s nothing to worry about 🫂

yoga #catstr