cody
Cody Tseng

New Feature: #Jumble now supports viewing conversations between you and another user.
https://image.nostr.build/99114e9847720d5f5eb5c318ed2d3ae68db379cf64743e1d391e86c309a57ed4.jpg

2025-04-15 14:30:43

- reply

Received 🫡

2025-04-15 14:11:50

- reply

Waiting for the iOS version.

2025-04-15 09:56:08

- reply

I've tried it, but it doesn't work, haha
https://image.nostr.build/ec1800c812610dc337c0471801b7a314e1afa7178e7762dffdc3a666d92a1ba9.png

2025-04-15 03:29:46

- reply

I guess you're using a extension that supports multiple accounts. The actual npub used for posting depends on which npub's private key the signer is using to sign the post. Perhaps I should add an alert dialog when the npub used for posting doesn't match the one displayed on Jumble.

2025-04-15 02:08:45

- reply

native ios app is impossible 🌝 because publishing on the app store requires my personal information.

2025-04-15 02:00:35

- reply

Try jumble.social and add it to your home screen. I bet you'll like it.

2025-04-14 15:27:05

- reply

If it's like GitHub with just a few fixed emojis, then it can be done really quickly, hahaha.

2025-04-14 15:01:19

- reply

It might be because I don't have design drafts, design guidelines, or coding standards. So contributors didn't know what the standards were. I didn't know either, I just kept trying until I was satisfied. There's quite a big difference between front-end and back-end projects.

2025-04-14 14:49:05

- reply

Actually, I rewrote almost everything, but his codes helped me finish it quickly.

2025-04-14 01:04:14

- reply

I kind of know what he's talking about, but his understanding is wrong. Simply put, everyone belongs to a certain city. You can go to any city to live and work. But if you don't belong to that city, you'll lack some benefits and rights, like in aspects such as healthcare, education, and house-buying. When you meet certain conditions, you can change the city you belong to, and the conditions vary from city to city. But in recent years, the gap in benefits and rights between these two types of identities has been gradually narrowing. So this system doesn't hold much significance anymore, and it's just a matter of time before it gets abolished.

2025-04-13 14:46:41

- reply

It’s a very interesting attempt 🫡

2025-04-13 14:36:10

- reply

What kind of event is this?

2025-04-13 14:08:46

- reply

🤝如果能吃到的话

2025-04-13 12:56:25

- reply

Alright

2025-04-13 12:46:02

- reply

不翻本来也不好用，慢得要死🤣

2025-04-13 02:52:01

- reply

I really loved this feature, which is why I built danmakustr. On Japanese and Chinese video platforms, every video is filled with danmaku, you get to see how others feel at the exact same moment in the video. It’s like watching together with a crowd.
However, when there aren’t many users, most of the time users only see their own bullet comments, which is very boring. This causes users to lose interest in sending bullet comments, and as a result, the number of bullet comments never increases. So, I’ve decided to stop maintaining this project, haha.

2025-04-12 06:53:21

- reply

The latest version has integrated a reverse proxy service.
https://image.nostr.build/8ded577e961e8e9bd7aae24151bdd0b902a4e64a9bf64b9739a366b9691c8b29.png

2025-04-12 03:12:52

- reply

It looks like a great project! However, Jumble isn't planning to support event kinds other than kind:1 for now. We can support displaying and linking to other clients in repost and embedded notes, similar to how we currently handle long-form content.

2025-04-07 09:46:51

- reply

I'll update the regex, it should definitely allow underscores "_"

2025-04-07 03:53:38

- reply

That's great!

2025-04-06 14:11:01

- reply

My relay does not support NIP-29

2025-04-06 12:26:10

- reply

Nice!

2025-04-06 03:52:49

- reply

That’s true for now. However, I’m confident that various relays will emerge in the future. First, I need to perfect features like relay browsing and discovery to pave the way for their arrival. It would be a pity if someone wanted to operate an interesting relay but couldn't find a client to browse with.

2025-04-06 03:36:44

- reply

It’s due to caching. It will be refresh once the cache expires after some time. Generally, users don’t frequently modify the relays they use, nor should they. So, caching is reasonable.
Since I don't have the cached data for him, what I'm seeing on my end is correct.
https://image.nostr.build/cd8e16eb7634973b5e09f31ff3a10a99c4e4a3af699a6bc3f96a8163b40aaeae.png

2025-04-06 03:23:05

- reply

You’re right! I’m still figuring out a solution. Moreover, it seems that many relays don’t accept protected events. I’m not sure how to distinguish between those that do and those that don’t.

2025-04-06 03:19:26

- reply

The purpose of this list is to save some relays favorited by users, such as algo relay, lockbox, 23GMT, and so on. It’s similar to browser bookmarks, facilitating browsing on Jumble.

2025-04-06 03:14:08

- reply

Nice to meet you, too

2025-04-05 16:49:27

Now you can view the relays favorited by the people you follow! #jumble
https://image.nostr.build/3a15d8ec0ceeadd534d26ecd6aabf05c4c852e956af3a295560e39f58a7249be.png

2025-04-05 14:43:21

- reply

Because many people have reported that the global feed contained a lot of porn content, I decided to remove it. However, you can create your own global feed in the settings. Previously, I was using wss://relay.damus.io and wss://nos.lol as the relays for the global feed.

2025-04-05 12:25:29

- reply

We can try using only read relays to subscribe notifications. If too many people report not receiving notifications, I might roll it back. Some clients don't send events to the mentioned person's read relays, which is quite frustrating.

2025-04-05 08:22:07

- reply

Glad to hear this!

2025-04-05 07:33:02

I will break your relay sets in #Jumble, I hope you won’t be upset. It’s for a better experience in the future.

2025-04-05 06:33:10

- reply

error: failed to authenticate 🤣

2025-04-05 04:55:22

I've seen a lot of people discussing #hellthread. Can anyone briefly tell me what it is? #asknostr

2025-04-05 03:28:15

- reply

Haha, only simple issues can be fixed that quickly!

2025-04-05 03:26:38

- reply

Because many people haven’t properly set up their inbox/outbox, I took the liberty of adding a few relays in some cases 🤣

2025-04-05 03:23:06

- reply

You're right, thanks for the feedback! It's been fixed. 🫡

2025-04-04 08:49:24

- reply

The following feed is fetched from the outbox relays set by the users being followed. It’s possible that some relays configured by users are returning results that don’t meet the filter. I will perform further validation on the results returned by the relays.

2025-04-04 08:35:46

- reply

No, take a closer look. The relay sends AUTH when the connection is established. The AUTH after OK is sent by the client.

2025-04-03 14:37:09

- reply

The error occurs if the note is not posted successfully within 4.4 seconds. Try a few more times, the network might be unstable.

2025-04-03 14:21:36

- reply

Sounds cool! I'd love to create such a platform. However, I'm still trying to figure out under what conditions the bounties would be released, who would release them, and where the bounty would be locked.

2025-04-03 14:14:19

- reply

Congratulations! 🎉

2025-04-03 14:08:18

- reply

This error should occur during the post process. I guess you have already seen the uploaded image in the preview, so the image should have been uploaded successfully. However, posting the note failed. Right?

2025-04-03 14:01:18

- reply

This looks great 🔥

2025-04-03 13:42:40

- reply

Perhaps I need to support different media upload services and Blossom as soon as possible.

2025-04-03 13:37:40

- reply

I will keep an eye on this issue. If you discover more details, feel free to share them with me, as it will help me identify the problem more quickly.

2025-04-03 13:34:08

- reply

This makes sense because when posting, the extension's signing method is called directly without checking whether the extension's account matches the current account.

2025-04-03 10:22:28

- reply

That sounds terrible! I have no idea since I haven't encountered this issue. Could you tell me which browser you were using? On mobile or desktop?

2025-04-03 10:02:14

- reply

Okay, it's been updated.

2025-04-03 09:46:06

- reply

Sure, I'll find time to take a look.

2025-04-03 09:36:02

- reply

Updated in beta.

2025-04-03 09:35:08

- reply

Can you tell me what browser and extension you're using? I'll see if I can reproduce the issue.
Also, just to make sure I understand correctly, do you mean a login dialog appeared even though you were already logged in?

2025-04-03 09:19:01

- reply

Which login method?

2025-04-03 05:56:46

- reply

If you choose the Following feed, it works like a traditional client and will only show posts from the people you follow. If you choose the relay set, it will display all posts from the relay.

2025-04-03 05:49:26

- reply

Sounds feasible. What protocol will you use for broadcasting?

2025-04-02 12:41:08

- reply

Jumble was developed from scratch using nostr-tools, but in many aspects, it was inspired by nostrudel. That's because I'm also a fan of nostrudel.

2025-04-02 12:37:09

- reply

A really different way of thinking. What I had in mind was using it to share the feeds of certain users.
It can be quite useful for people who value privacy. I'll rethink the priority of this feature.

2025-04-02 11:50:11

- reply

But I like this feature, so it might be added in the future. 🫂

2025-04-01 01:28:48

- reply

Haha, this makes me unable to see your replies in the notifications.

2025-04-01 01:27:25

- reply

I have removed the colon, and as long as the returned reason starts with "auth-required", it will proceed with authentication. You can try again, and it's best to log the WebSocket communication for troubleshooting.

2025-04-01 01:18:26

- reply

Thank you! Feel free to reach out to me anytime if you encounter any issues.

2025-03-31 15:00:10

- reply

What confuses me is why this note wasn't sent to my read relays

2025-03-31 14:58:44

- reply

Yes, pokey can listen to this special event, and when it receives the event, it can clear the push notifications

2025-03-31 14:33:14

- reply

If Jumble receives ["OK", false, "auth-required: xxxxx"], it will authenticate and retry sending. Maybe the issue is that the response is missing a colon? hahaha, I can remove the colon check.

2025-03-31 14:25:13

- reply

like this:
{
"kind": 30078,
"tags": [["d", "seen_notifications_at"]],
"content": "",
"created_at": 1743430990,
}

2025-03-31 14:22:38

- reply

Jumble is not currently using the 30078 event. I prefer to define a special d tag, and the event's created_at represents the time of the read notification.

2025-03-31 13:44:43

- reply

In theory, a kind 30078 event can be used to store the time of reading notifications and publish it. Other applications can subscribe to this event and perform some processing. I'm not very familiar with Android, so I'm not sure if this is possible.

2025-03-31 01:38:09

- reply

Feel free to reach out if you run into any issues. Hope you enjoy using it!

2025-03-30 04:39:11

- reply

To be able to connect to fewer relays, I excluded some relays based on certain rules, but it doesn't seem to be working well, haha. fiatjaf also set up other write relays, but they were excluded by my algorithm.

2025-03-30 04:36:54

- reply

There should be, but I haven't used it. We can ask GPT 🌝

2025-03-29 13:23:08

- reply

Yes, currently auth only occurs when an "auth-required:" reason is received.

2025-03-29 02:50:07

- reply

Leave it to the professional clients. Try habla.news

2025-03-28 13:28:27

- reply

I couldn't agree more with your idea. This is one of the reasons why I developed nostr-relay-tray and jumble. nostr-relay-tray can now enable non-developers to run a personal relay easily, and it can be accessed from the Internet without any configuration. The next version will support automatically pulling events from people you follow. Then nostr-relay-tray will become the personal caching relay you mentioned. And it can be browsed easily with jumble.

2025-03-28 10:28:18

- reply

If I'm following 1000 people, and each person only posts notes to their own personal relay, I would need to connect to 1000 relays to get my following feed.

2025-03-28 07:43:29

- reply

Clients like Jumble and others that use the outbox model to fetch the following feed will do this.

2025-03-28 02:52:42

- reply

I really appreciate your feedback as well!

2025-03-28 02:15:07

- reply

The more relays you use, the slower operations like posting, liking, following, etc., might get. However, using a dozen or so relays doesn't actually slow things down that much, haha.
The main issue lies in the fact that people who follow you are unlikely to use all of your write relays to query your events. Since they follow many other people as well, most of the time, only the first few relays are meaningful.

2025-03-28 01:47:59

- reply

Sorry, Jumble currently only sends to the first five write relays. I'll consider increasing the limit.

2025-03-28 01:45:29

- reply

Got it, I'll consider adding some guidance where appropriate.

2025-03-28 01:21:33

- reply

I don't know why it's very slow on Safari.

2025-03-27 15:41:23

- reply

One feature has been completed.
#nevent1q…3dmj

2025-03-27 15:05:57

- reply

Thanks 🫂

2025-03-27 14:58:33

https://jumble.social has now adopted the #outbox model to retrieve the following feed.
It might not be as fast as before, but it will ensure that no updates from people you follow are missed.
#nostr #grownostr #devstr
(Additionally, when using Safari, the following feed is still retrieved through read relays.)

2025-03-27 08:56:01

- reply

Yes, the next version will include the feature to automatically pull events from public relays.
If your local relay automatically pull events from the outbox relays of people you follow, combined with using Jumble browsing. The following feed will load very fast and save bandwidth.

2025-03-27 02:50:34

- reply

I plan to use a new kind 10012 event to store favorited relays and pointers to relay sets. I'll try to upgrade without affecting existing data. https://github.com/nostr-protocol/nips/pull/1848

2025-03-27 02:35:55

- reply

The relay sets feature is currently being restructured. Once the restructuring is complete, it will support automatic synchronization and simplify the process of managing and favoriting relays.

2025-03-27 01:15:08

- reply

Received

2025-03-26 06:58:47

- reply

Your support is the motivation that keeps me going.

2025-03-26 06:57:04

- reply

Will this instance update synchronously?

2025-03-26 06:54:47

- reply

I tried using your npub on Firefox, and it seems to work fine 🤔. I'll keep an eye on this issue and see if anyone else encounters it.
Feel free to reach out anytime if you encounter any issues. I'll respond whenever I see them. 🫂
https://image.nostr.build/6be710e38bb4148e6ed5a2a37c25f72c577b2cd4980b12795faf219dae595bb8.png

2025-03-26 06:30:30

- reply

Do you mean you couldn't open this page? https://jumble.social/profile-editor

2025-03-26 06:20:55

- reply

I'm really sorry about this! I'll modify the default relays right away.

2025-03-26 06:19:14

- reply

I have no idea where the problem is. I've only encountered this issue on Safari, especially when using the beta version of Jumble. The beta version is testing the outbox model for the following feed, which requires loading a large amount of data at the start. In short, Safari is garbage. 🥹

2025-03-26 03:59:18

- reply

更新一下版本吧 🌝 还在不断优化中

2025-03-26 01:34:42

- reply

Feel free to report any bugs anytime!

2025-03-26 01:31:34

- reply

Welcome! 👏

2025-03-26 01:30:50

- reply

You can export your events from coracle.social , and then import it into nostr-relay-tray. You can also use https://github.com/jiftechnify/nosdump to download your events.