Nostr Archives

#Jumble keeps evolving 🌱 Here’s what’s new in the last 2 months 👇 - Support publishing highlights - Special follow feed - Emoji packs store - Redesigned threads for easier browsing - Filter content by user reputation across feed, threads, and notifications - Mute words - Hide indirect notifications to avoid hell threads - Smarter relay pool management & faster loading - Optimized onboarding for new users - Fixed various bugs and improved overall experience Huge thanks to everyone giving feedback, contributing, or supporting Jumble 💜 More exciting features coming soon 🚀 #nostr #devstr

💬 25 replies

Replies (25)

Cody43d ago

It’s in development. It’s based on NIP-4e, which isn’t compatible with most clients yet, but I think it’s a better fit for Jumble.

0000 sats

Cody43d ago

That branch is entirely AI-generated code. It implements the basic functionality, but it has a lot of issues. I found it pretty painful to work on, so I’ve been focusing on other things lately, DM will need to be delayed for a while. :doge:

0000 sats

Cody43d ago

A big part of why I’ve always been resistant to NIP-17 is the UX: unless the user fully agrees to all decryption requests, the app basically becomes unusable. You just keep getting spammed with decryption permission pop-ups over and over again.

0000 sats

cloud fodder43d ago

which in turn eventually causes the signer extension to lock up permanently and you have to re-install it 😭 I still use my terminal UI app (flightless2) as a daily driver for nip17, works great, only connects to DM relays, native/golang but no GUI required so you can run it on any terminal. Since I wrote it, I trust it with my key 🐧#bonus

0000 sats

Cody43d ago

The code on GitHub is pretty old at this point, I’ve made a lot of local changes that I haven’t pushed yet, so it’s not very useful as a reference. You’re probably better off looking directly at NIP-4e instead. https://github.com/nostr-protocol/nips/pull/1647

0000 sats

Cody43d ago

I think there may be a bit of a misunderstanding about my concern. What I want is to be able to see and approve every single decryption request a client makes. With DM-capable clients today, that’s basically impossible in practice. That’s why I think NIP-4e is necessary: it separates the keys used for DMs from the user’s main key. My main key may be used to encrypt other data, and I don’t want to grant a client the ability to decrypt everything just so I can use DMs, even if most clients are well-intentioned and won’t do anything malicious.

0000 sats

Cody43d ago

Most users don’t even care where their private key lives. What we should be doing is finding a balance. If it were just about interaction, there are plenty of easy ways to implement that.

0000 sats

Cody43d ago

It just caches messages that have already been decrypted. Anything that hasn’t been decrypted yet still needs to be decrypted one by one with your key.

0000 sats

FLASH35d ago

I use @Jumble today for my work.

0000 sats

FLASH35d ago

A minor issue I encountered during my day: Jumble does not accept videos that are too large (even though mine is barely 2 minutes long). I have to struggle with the file size to get it through, which is a pain. @Jumble @Cody But good interface.

0000 sats

FLASH35d ago

Secondly, when you select an emoji, the page closes, and if you want two, you have to click on the emoji tab again. It's a shame that it doesn't stay open. @Cody @Jumble

0000 sats

FLASH35d ago

Thirdly, my profile picture is not visible on Jumble, and other accounts are affected too. Maybe it's because it was uploaded on Primal, I don't know. @Cody @Jumble

0000 sats

Jumble35d ago

You can change the media upload service to one that suits you better in Settings → Post Settings.

0000 sats

FLASH35d ago

Okay, I understand. The photo isn't displayed on a PC browser, but there's no problem on mobile! The same goes for Blossom Primal, My videos aren't displayed on a web browser, but there's no problem on mobile! @Jumble @Cody

0000 sats

Jumble35d ago

I can see your profile picture, haha 🤣

0000 sats

FLASH35d ago

Thank you for your quick response. I appreciate that you've done a great job. I appreciate your platform in many ways. Regarding my photo, I have this one.

0000 sats

Jumble35d ago

Jumble itself doesn’t impose a file size limit — the limit you’re hitting comes from the media upload service you’re using. If you’re used to Primal’s setup, you can switch to Blossom and set the endpoint to: https://blossom.primal.net/

0000 sats

FLASH34d ago

As soon as I switch to Blossom Primal, I can't even add a photo to my notes. PS: The difference between Jumble on mobile and on PC can be verified by anyone. I myself used different web browsers to verify my statements. @Jumble @Cody

0000 sats

Jumble34d ago

Jumble uses the same codebase on both mobile and desktop. I haven’t run into the issue you’re describing, and no other users have reported it so far, so it might be something specific to your setup. Could you let me know which browsers you’re using on each device? That would help me look into it.

0000 sats