cody
Cody Tseng

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-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 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 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: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 09:36:02

- reply

Updated in beta.

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-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-03-31 15:00:10

- reply

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

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-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:21:33

- reply

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

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 01:31:34

- reply

Welcome! 👏

2025-03-25 16:03:20

- reply

That's awesome to hear!

2025-03-25 15:59:06

- reply

You can try the relays developed by @npub1utx…50e8
https://github.com/bitvora

2025-03-25 15:49:55

- reply

Enjoy it!

2025-03-25 15:49:35

- reply

Glad to hear this!

2025-03-25 15:17:16

- reply

Any computer will work!

2025-03-25 15:15:05

- reply

You're welcome! Feel free to reach out if you need any help.

2025-03-25 15:05:19

- reply

Thanks 🫂

2025-03-25 14:53:01

If you care about your data and want to truly own it, you should run your own relay.
If you're not a developer, nostr-relay-tray is perfect for you. Just grab an old computer, install it, and let it run quietly in the corner of your room. It’s simple.
Download nostr-relay-tray today and take control of your data!
1. Download the appropriate installer from https://github.com/CodyTseng/nostr-relay-tray/releases and install it.
2. Open nostr-relay-tray.
3. Go to "Proxy", and toggle the switch.
4. Add the public address to your relay list.
5. To prevent receiving spam events, enable WoT (Web of Trust) under "WoT & PoW".
https://image.nostr.build/362334d4b3b0e5c9902937688deb5368dccc3de64ee47f97eef3556e2983285c.png
https://image.nostr.build/7829071140d32f764f67c10476449a4ebe176d6a5673d063d779999eb5b6fa0e.png

2025-03-25 14:40:16

- reply

Nice club

2025-03-25 06:33:29

- reply

Having more people run their own relays is crucial for a decentralized network. Thank you so much for making a video about this project! 🫡

2025-03-25 01:13:50

- reply

Glad you like it!

2025-03-23 14:41:28

- reply

#nevent1q…k4ph

2025-03-23 14:35:49

🚀 nostr-relay-tray v2.0.0 Released!
What's new?
- 🌐 One-Click Public Access – Easily expose your relay to the internet.
- 🔧 Improved Event Filtering – More precise control over which events to accept or reject.
- 🗑️ Conditional Event Deletion – Remove events based on specific conditions.
Own your relay, own your events!
1. Download the appropriate installer from https://github.com/CodyTseng/nostr-relay-tray/releases and install it.
2. Open nostr-relay-tray.
3. Go to Proxy -> Connect to Proxy, and toggle the switch.
4. Add the public address to your relay list.
5. To prevent receiving spam events, enable WoT (Web of Trust) under WoT & PoW.
#nostr #relay #devstr #grownostr #freedom
https://image.nostr.build/362334d4b3b0e5c9902937688deb5368dccc3de64ee47f97eef3556e2983285c.png

2025-03-23 02:27:18

- reply

There will be a major update for nostr-relay-tray next week 😊

2025-03-19 15:54:21

- reply

给 nostr-relay-tray 集成了一键代理的功能，可以轻松暴露到公网上，不仅限于局域网

2025-03-19 14:55:32

The easiest way to run a public #nostr #relay? 👀
wss://proxy.nostr-relay.app/ae30ba2372ced6c1960d49c0266fdd3e07cea52b1bf378fdb684aee6363dec46
https://image.nostr.build/e7e1ed6a1cf7bbd37677ae7b4ae78bf375e90b6a15cc01374358b4221d4805e4.png

2025-03-19 14:00:29

- reply

Got it! 🫡

2025-03-19 13:59:58

- reply

It's quite difficult for me to perfectly mix kind 1 and kind 20 notes together. This leads to some confusion when people use Jumble, for example:
- Why can't I see kind 1 notes in the pictures tab?
- Why can I choose between "normal note" and "picture note" when posting? Isn't "normal note" also capable of uploading images?

2025-03-18 15:18:49

- reply

I haven’t figured out how to implement auth yet. The web of trust can be implemented by the relay.

2025-03-18 13:08:14

- reply

Pigeon consists of two parts:
- pigeon_nest: A reverse proxy service deployed on a server.
- pigeon: A local client that forwards messages between the local relay and pigeon_nest.
Pigeon communicates with pigeon_nest via websocket. Upon connection, it performs a NIP-42 auth and uses the pubkey as the relay address. I've already deployed pigeon_nest on my server, you can compile pigeon and give it a try: https://github.com/CodyTseng/pigeon/tree/master/pigeon
Here's my local relay:
wss://proxy.nostr-relay.app/4de3d1195084605b44638f816d1e787ee984e1751001a659396466173c787bb9
I also see this project having potential as a paid service, similar to ngrok

2025-03-18 06:18:26

- reply

0xchat 是咋实现的🤔

2025-03-18 01:25:42

- reply

🤣

2025-03-17 14:01:53

- reply

Thanks! It might be a bug, haha. I’ll keep an eye on it.

2025-03-17 04:27:27

- reply

Looking forward to your return! This bug is relatively simple, maybe I can create a PR to fix it.

2025-03-17 03:05:10

- reply

This issue is caused by calling `relay.auth()` twice in quick succession. Since both auth events were signed within the same second, they are identical. Looking at the nostr-tools source code, I found that this prevents the first `relay.auth()` call from ever returning.
I'll find a way to avoid consecutive calls to `relay.auth()`, but it might be better to modify nostr-tools to handle this properly.
https://github.com/nbd-wtf/nostr-tools/blob/9a612e59a254fd2fb54127073051ac47031858d1/abstract-relay.ts#L251

2025-03-16 15:15:26

- reply

Got it, I’ll fix it as soon as possible.

2025-03-15 17:25:12

Big thanks for adding the Italian translation to Jumble! 🇮🇹🚀
#nevent1q…xww3

2025-03-15 14:54:59

- reply

The encrypted part is stored in `content`, while the unencrypted part is in `tags`—these are two separate lists. Clients should merge both lists when using them, but they are stored separately on the relay.
As I mentioned earlier, Jumble will allow users to choose whether they want to mute someone publicly or privately in the future.

2025-03-15 14:35:44

- reply

Clients should merge both encrypted and unencrypted mute lists. Jumble already does this. So if you mute some users on a client that doesn't support encrypted mute list, they will also be hidden on Jumble. In the future, I will allow users to choose whether they want to mute a user publicly or privately.
Public mutes help the entire network identify bad accounts and assist relays in filtering unnecessary events. Private mutes help protect user privacy, for example, I might just not want to see someone's posts but don't want to hurt their feelings. Both types of mute lists need to coexist.

2025-03-15 14:09:43

- reply

I'll try to fully hide muted notes, but it might take some time since I'm working on another project right now.
Btw, the mute list set through jumble is encrypted.

2025-03-15 03:44:51

- reply

Could you please delay the database clearing time a bit? 🥹

2025-03-14 07:44:01

- reply

nip19 without the `nostr:` prefix will be displayed as plain text.

2025-03-14 07:00:42

- reply

Before publishing, Jumble now automatically adds the `nostr:` prefix if it's missing.

2025-03-13 10:19:04

- reply

🥹

2025-03-12 14:39:19

- reply

If someone doesn't post frequently, their posts might be harder for others to discover with this strategy 🤔

2025-03-12 13:22:06

- reply

That's exactly what I'm planning next. First, I'll remove relay sets and put all saved relays into a single set to simplify relay management and allow viewing others' saved relays. After that, I'll focus on improving the following feed.
Do you have any suggestions for the following feed? Most people still use a few large relays for writing, so it seems difficult to avoid sending requests with a large number of pubkeys to some relays 🤔

2025-03-12 13:04:23

- reply

The road of exploration is never easy 🫡

2025-03-12 10:20:35

- reply

Thanks for the kind words about Jumble! However, there’s still a lot of room for improvement.
Nostrudel is a fantastic client, and I often learn from its source code. It’s more of an explorer of Nostr, experimenting with different things for other clients. We definitely need these kinds of explorers.

2025-03-12 08:43:38

- reply

Thanks 🫂 Hope we can pinpoint the root cause soon.

2025-03-12 01:33:03

- reply

I couldn't reproduce this issue 😂 Could you record a video? Maybe I can spot some other details from it.

2025-03-11 15:39:32

- reply

Reply events might easily exceed 8 indexable tags since jumble adds all the event IDs from the current thread 🤔