If you don't know which relays to use as read relays, you can try this new feature. #jumble #devstr
https://jumble.social/relay-settings#mailbox
Discussion
That's a great feature. Way to go.
New to NOSTR, hadnβt yet figured out what a read relay was used for. This is incredibly helpful and will be utilized by this guy soon!
You have any advice when it comes to choosing the best, most trustworthy ones for privacy purposes? That is, without simply using your own relay.
If you are just getting started with Nostr, don't think too much. Just use a few large relays first, such as wss://relay.damus.io, wss://nos.lol, etc.
Just enjoy it first. π«‘
Exactly! For the average joe's, thinking about relays and stuffs would just make things complicated for them. They can just start #Nostring instead .
I don't think there's supposedly any best relay. You can just use what nostr:nprofile1qqsgzfdez8ksa9xmuvqg5zly3nl9e5xqkpvj8nllj9aw06ra4pqq3qcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0dehhxarj94ex2mrp0yhxzurs9uqsuamnwvaz7tmwdaejumr0dshstm459s recommended. These are pretty good relays. And trustworthy, too.
I'd recommend, instead of thinking about which relays to use, think about which client suits you best.
Because there are a couple of clients now. Try every one of them and see which one you like and start using that.
Or, maybe explore all of them. You can always change clients and your social graph will transfer between the clients too. So don't worry and explore #Nostr. And use hashtags. And explore hashtags too. You might want to start with #introductions, #AskNostr, #Nostr, etc.
On the web anytime I refresh it logs me out, is this a known issue or maybe something on my side?
May I ask what browser and login method you are using? More than you have encountered this problem, but I haven't found the reason yet because I haven't encountered this problem. π€£
Still happens for me. Every. Time. Unfortunately.
π What browser and login method are you using?
I'm using Nostr Connect on Google Chrome. Shall I try using another browser?
I'm also using Chrome π€
Are you using any extension or nsec.app?
I mainly use extension and nsec. The latency of remote signer is a bit high for me.
Are you using from desktop? I'm talking about desktop though.
Yes, I haven't encountered this problem on either the desktop or mobile device.
That's weird. It just keeps happening to me. I also heard nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 facing this issue, too. Wish I could help you debug or reproduce it.
It might be helpful if you could record the screen. π€ Or I'll add some logs tomorrow and then ask you to try again.
Now I need to sleep π΄ GN π€
Here's the screen record, if it helps. You can take your sleep and get on it tomorrow.
https://video.nostr.build/f80fdf51c44b251790135e80c528e9ae912e0b4a41f19e8728c8f6df71f8d7ad.mp4
Receivedπ«‘ I'll take a close look tomorrow.
Sure. Good night.
Tested with #Firefox. Same issue persists. So the issue is not for the browser.
Changed the extension from Nostr Connect to nos2x. But the issue persists. So, it's not the extensions, either. So what it could be? What's causing the issue? The issue persists in both Chrome and Firefox and with both Nostr Connect and nos2x.
Thank you very much for the information you provided! I reproduced this issue using Firefox + nos2x. Then I found that the extension was not loaded when jumble was initialized, which led to jumble not logging in. It has been fixed in the latest version. You can give it a try.
Thank you. I'll give it a try and let you know. Great job.
nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl Awesome! You've squashed the bug. Now the signed-in state persists across the browser sessions, or even after refreshing the browser tab. Thank you.
One more thing: you might want to implement a feature that would pop up profiles/accounts after typing @ as it does on other social media while tagging someone, and even on other #Nostr clients. By default, pressing @ could pop up the most frequently mentioned profiles, or it could do nothing. Upon pressing a single letter, it should pop up profiles matching that letter/character. Upon pressing the second, it should refine the matches and so on. Is this feature on your pipeline? This would increase the usability of #Jumble even more.
This is indeed a very important feature, but it's really not easy to implement. I still need some time. π«‘
Take your time. Also, the same thing for searches. While searching for something, if the characters match, the relevant profile should pop up. Consider it, too. This would make life easy for the users.
Keep up the good work.
I agree, I even created an issue about this on Jumble github repository.
Okay, I'm sharing my screen record. Give me a minute.
Sure! Chorme on a Macbook, logging in via nos2x.
Same problem here, Chromium + nos2x/bunker
He said he fixed the problem. Are you still reproducing?
Refresh to get the new version and have a try again?
So, I'm WAY out of my depth here. I can tell you're trying to be helpful to us noobs, but I just jumped into this world yesterday. Is there a good place to just figure out the terminology, so that I may actually have the capacity to learn?
For new users, you just need to enjoy it and don't need to care about these. π€
Nostr is a protocol, or a set of rules about how the apps built-on this rule should communicate. It's not an app by itself. But as a protocol, it lets other clients/apps build on it.
Apps (clients) can be developed based on this Nostr protocol. The beauty is, these clients can communicate between them. So, it's like the email. Email has protocols different protocol that makes it work. And different apps or clients, like Gmail, Yahoo Mail, etc. that can communicate among them.
Nostr is just like that. But unlike the email, Nostr protocol allows you to build any type of clients. So you can have alternative to Facebook, Twitter, Instagram, TikTok here on Nostr. Primal, Damus, Amethyst, etc. are Nostr clients that are more geared towards microblogging, primarily. More like alternative to X (formerly, Twitter). We already have an alternative to Instagram and it's called Olas. We have alternative to Medium, or for long-form content, and for that you can use Habla, Yakihonne, etc. We have clients/apps for podcasts, music, etc. We have an alternative to Reddit, hacker news, etc. And it's just the start.
Good thing is, you can use your same identity to sign in to these apps. And your followers and other social graph will transfer between the apps. You can use all the apps/clients at the same time. You can't use the same profile across Facebook, Twitter and others. But here on Nostr, you can.
About relays: relays are what stores and serves your data. When you're reading something, e.g. others posts, photos, etc. using a client/app, it's fetching them from the relay set you're using. And the same goes for when you're writing something or publishing. Relays are just servers. But instead of one centralized servers, you have many here. And you have the freedom to choose the relays here. So, in case one relay bans you, or doesn't want to host your content, you can always use another one. Or multiple others.
So, these are everything, I guess, you need to know for now. Don't worry about terminology. Just explore #Nostr and interact with people. Be yourself. You can use your real name here, or stay anonymous. You can have more than one profile, but that's not needed here, as you can use the same profile for signing in to all the clients built on the #Nostr protocol. Use hashtags frequently. Search for people, hashtags, And enjoy Nostr.
How does the Following feed work? It looks like it's making one big REQ to relay.damus.io for everybody that I follow.
Yes, it's that rough π€£ But for now, I don't want to spend too much time on the following feed. As a newcomer in frontend development, I feel that I have written many bugs. I need to spend some time fixing them. π«
