Okay let me try to reproduce it with your relay in local, I'll keep you updated
indeed, a code search shows it's this. whew
nostr:nprofile1qqsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqpzamhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9ua2vh28, it appears that pokey has a really tight reconnection or request loop when it encounters an auth challenge.. 30+req/second.
do you know how this could be happening?
Mmmm this might be related to the latests changes nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck ?? - nostr:nprofile1qqs8eseg5zxak2hal8umuaa7laxgxjyll9uhyxp86c522shn9gj8crspz9mhxue69uhkummnw3ezuamfdejj7qgjwaehxw309ahx7um5wgerztnrdakj7qgwwaehxw309ahx7uewd3hkctc58hv2s are you able to say if the reason is an invalid auth?
I just make nostr connections work on Robosats Android App through Tor, not even I can believe it.
I'm fully unleashed now to start implementing nostr tools on Robosats LFG
Awesome. I just confirmed its not possible, you can only add 3 buttons.
Here is the roadmap for Pokey:
- Optionally use built-in Tor engine
- Multi-account
- Mute button and mute lists for users and threads
- Last 20 notifications view (this can be replaced by the topics on this thread)
I think you can't. I was thinking on a configuration on the app where you set the default snooze time, maybe?
Please, anything you see on the app that can be improved will be extremely welcomed. I'm good with coding, but sucks with UI/UX 😓
Amazing thanks for the mockups!!
What a novel idea
Almost like a pager back in the day
nostr:nprofile1qqsxg45ph8gx0vdrvtzta6xal7v86frx6jvstsnvhrlvtehmwwh4epqpzamhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6tcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9nhwden5te0v4jx2m3wdehhxarj9ekxzmny9ua2vh28 I'm messing about with a hardware version of pokey I'll share more when I have something worthy to share
Awesome! Keep me into the loop!
Actually Pokey also seems like an interesting solution if you decide to *not* install any other Nostr app on your phone: just get the notification without getting trapped, and put off any activity until when you are at your PC.
nostr:npub1v3tgrwwsv7c6xckyhm5dmluc05jxd4yeqhpxew87chn0kua0tjzqc6yvjh maybe you could think about some specific features for this use case, for example the possibility to pin a notification and snoze it, ora add a short note.
I have on the roadmap to be compatible with existing user/thread mute lists.
About snoozing, I never considered that 🤔 so you meant to have an action to receive again the notification after 10 min? I also have in roadmap to display on the app latest 20 notifications in case you accidentally discarded one.
Every coordinator is an independent server hosting their own orders, and if you want to know the orders hosted by coordinator X you need to do a call to its API (actually 2). There are 4 active coordinators today, but nothing stops that number to be 100. You can see the API method doesn't scale up if you want to see the global orders book.
With nostr, every coordinator runs its own relay on a way that continuously synchronizes with the rest, so all relays hosts all active orders. On this sceneraio a client only requires to connect to 2-3 random coordinator relays to have access to the entire global book.
Robots are disposable and every robot can have its own unique npub
In the other hand, if you use your primate npub, you loose the exact same privacy against your coordinators than using Telegram notifications. For everyone else listening, they will only see that you received a gift wrapped event (NIP-59), with no extra meta data.
Future featutes: If your Robot has an npub (generated or manually associated) and coordinators start publishing gift wrapped notifications to that npub, you can even use nostr:nprofile1qqst4dr6ttrw6s28squnwwuj5vsvsly33h7r4nsuzz3f8nf3wjsmk9cpz4mhxue69uhkummnw3ezummcw3ezuer9wchs9pfmqv to receive Robosats orders updates.
Interoperability at its finest.
You can test now Nostr global order book on Robosats by enabling the option in the configuration tab.
For now it's only available in web, I'll be working on the mobile app for the next release.
New Robosats release v0.7.2-alpha
First step to client Nostrification!
*What's New*
- Nostr order books
- Recovery robot form improved
- Fast generate robot -> fast generate order
- Many small bug fixes
- Add coordinator Alias to invoice description
https://github.com/RoboSats/robosats/releases/tag/v0.7.2-alpha
Rhat is qeird that notification shouldn't be sticky, it's not defined like that and not behaving like that in my Grapheme, can you try disabling the "Relays Connection" notification?
We got the idea to use nostr Zaps to allow everyone to audit the donations Robosats coordinators send to the development fund with every successful order.
Altogether, with user's coordinators rating, aims to reduce the amount of trust required to use Robosats from any angle to the minimum, more info: https://github.com/RoboSats/robosats/issues/1097
And the next Robosats release will allow users to use nostr to display the global order book, way faster load!