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.

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/

That’s a bit strange 🤣 Does Blossom Primal actually apply different rules for different devices? I honestly don’t know either

I can see your profile picture, haha 🤣

Got it 🫡

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

#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

Usually you don’t need to change anything. Replies are sent to your write relays and the other person’s read relays. If both of you have sensible relay setups, it should just work.

That’s strange, on my side, undo and redo both work normally on macOS with Firefox

I’ll adjust the detection logic a bit later 🫡