X.KOJIRA.IO
Timeline

Cody

[email protected]
npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl
I don't really understand why even reactions need a client tag 😂 Seems like Nostr users aren't too concerned about privacy.
https://blossom.jumble.social/86b8eb6ad6baa00856234525f66…
nevent1qvzqqqqqqyp…
Hi everyone! I’d like to share PsstPsst, a messaging app I’ve been working on over the past three months through vibe coding.

https://psstpsst.chat

It’s intended for staying in touch with friends and family, and supports iOS, Android, macOS, Linux, and Windows. Releases are currently available for all platforms except iOS.

I haven’t had a chance to test the Linux and Windows builds myself yet. If you try either and run into any problems, I’d really appreciate hearing about them.

PsstPsst is built on NIP-17 with NIP-4e, which separates encryption keys from identity keys. This means it isn’t compatible with most existing Nostr clients.

You don’t need to think of it as a Nostr DM app, though. I’ve tried to keep Nostr terminology out of the app and make it approachable on its own. My hope is that people can generate a fresh key and use it with their friends and family.

Why NIP-4e?

With a separate encryption key, the app doesn’t need to repeatedly request encryption and decryption operations from your identity key. This makes it possible to use the app with a bunker remote signer.

Encryption keys can be rotated periodically, so a leaked key won’t expose your entire message history.

A few things I’d like to add over time:

- Small group chats, likely limited to 10 people or fewer. NIP-17 isn’t well suited to large groups, and small circles feel like a good fit for the app’s focus.
- Voice and video calls.
- A built-in browser for napps.
- Communication without an internet connection, using FIPS.

There’s still plenty to improve, but I hope some of you might find it useful. If you feel like giving it a try, I’d be grateful for any feedback or bug reports. Thanks for taking a look!

https://blossom.jumble.social/b5761bc7a6986333d27efc67dd9…
https://blossom.jumble.social/3526e1e7ff49132877a230378af…
I’m just using it for coding. Even in a 5-hour window I usually only use about 30% of the usage limit. Might just be something like nationality/region-based restrictions lol.
I think the problem is that fiatjaf replied with kind 1111. After that, everyone replying to that comment also ended up posting kind 1111 events, so clients that don’t support kind 1111 can’t display those replies properly.

nevent1qvzqqqqy2up…
Using blossom.band returns a 415 unsupported media type error.

What kind of identifier are you looking for? I’d be happy to add support for it in Jumble.
I really couldn’t fetch metadata for those users. npub1gcxzte5zlkncx…, how did you manage to get them?
Caching ten events per user does sound like a clean and elegant way to make this work.
Honestly, it’s a really useful view, but Jumble might struggle to fully take advantage of it. You probably won’t be able to fetch notes from all follows anyway, since the browser won’t let you maintain that many relay connections at once. And after that, any further relay connections tend to fail. Damn browser limitations.
Haha, I promise that won’t happen, I mainly use the web version myself too. :MEOWDY:
No worries, both versions share the same codebase. The Electron version is just a thin wrapper around the web app.
It’ll still be browser first. The Electron app is just an option for people who like browsing the following feed. Right now the experience there in Jumble isn’t great.

For users like me who don’t really use the following feed, I rarely run into relay connection issues, so I’ll keep using it in the browser.

As for Electron, based on my limited understanding, its security model is quite similar to a browser’s, with things like sandboxing and process isolation.
My guess is that most of what you’re running into is due to the browser’s WebSocket connection limits. Jumble really isn’t well suited for browsing the following feed right now.

You might notice that after loading the following feed, actions like posting, reposting, or reacting start failing with relay connection errors. That’s the browser hitting its limit on concurrent connections.

I’ve been working on packaging Jumble as an Electron app to get around these browser limitations. That should improve things quite a bit.
What’s the difference between "Pulse" and "24h Pulse"? 🤔
Does "Pulse" load all recent events from your follows? I feel like that might run into some performance issues.
Yeah, just putting your Signal/Whisper/TG/... in your bio is probably better lol
NIP-4e is mainly about separating the encryption key from the user key and enabling cross-client synchronization of that encryption key. Jumble builds on top of NIP-4e and uses the encryption key to implement NIP-17.
Plain NIP-17 on its own isn’t a good fit for Jumble, because many Jumble users rely on bunker remote signers, and the experience would be pretty poor.
Chat is currently being tested on https://beta.jumble.social . It uses NIP-4e (https://github.com/nostr-protocol/nips/pull/1647), where the encryption key is separated from the user key, which works better for users with a bunker remote signer. However, it’s only compatible with Coop for now.
Got it, I’ll note this down.

This nsite is just for testing. In the future I’ll likely use a dedicated key to publish Jumble’s nsite and automate the process. At that point I’ll also sign and publish an "app listing" event to 44billion at the same time.
I completely understand your concerns.

You’re absolutely right, and I’ve already made optimizations as you described. Logged-in users can continue using Jumble as themselves regardless of whether bunker is connected properly. However, there might still be issues when it comes to signing events. That said, the experience is much improved compared to before
Thanks for the feedback! I’ve made some optimizations, though I’m not entirely sure if they’ll resolve your issue.

Bunker remote signing isn’t very stable in browsers, especially when there are many relay connections. The browser may block new connections, which can cause the login state to appear inconsistent or get stuck spinning.

If you’re using Jumble on a desktop browser, using a browser extension signer may provide a more stable experience.
That’s still content they chose to publish, so of course it won’t be hidden from the timeline. What it does is prevent your notifications tab from being polluted, so you don’t miss important notifications because of all the noise.
I get what you’re asking for, and I understand the desire for that level of control. That said, the benefit of this feature doesn’t really feel worth the cost to me.

If it’s just a single note, it won’t stay in your timeline for long anyway—it’ll quickly get pushed out by newer content. But once you add a “hide this specific note” feature, every note would need to be checked against a list of notes you’ve chosen to hide before being shown. Sure, there are ways to optimize this, but the question is: is it really worth it?

That hidden-notes list would also keep growing over time. You might be disciplined and keep it small, but other users probably won’t, and that complexity adds up fast.
The purpose of “hide indirect” is to deal with hell threads, that is, to hide replies from other users to the note shown in your screenshot.

As for the case you mentioned:
* If the account is just spam, you can easily filter it out using the trust filter.
* If it’s a normal account but you personally find them annoying and don’t want to see their content, you can simply mute them.
Click ‘hide indirect’ in the top-right corner.

https://nostr.media/f8b1b20740a8a10be80c5a61017347754388b…
When Jumble receives an error that starts with `auth-required`, it will automatically trigger authentication. From your screenshot, though, search.nos.today is returning an error that starts with `block:`, so the auto-auth flow never gets triggered, haha
> Então, para eu ler todas as bobagens do nostr, coloco 100%, ou deixo em 0%, como está?

0%
It can be slower when you first use it, as many things need to load. After some time, once the necessary cache is built up, it should feel faster. Of course, it also depends on the device's performance and network speed.
older →