7e83d - 3y
🌽 23'000 sat bounty: Write a feature request for robosats to notify makers through private message on nostr. (Just writing the feature request, no coding needed.) Do this by creating a new issue on github in the robosats repository and add your npub to the end of the feature request as proof (alternative you can add your npub to your github user bio, then you don't need to add it in the feature request). Then send me an 3k invoice over private message or public reply to this message, as you wish. ➕❓ Does anyone add more sats to this bounty? If yes: reply your bounty offer as reply to this note. 🧡 Maybe something for the brave #plebchain plebs? 👀 (The nostr notification system would be similar to the current current 3rd party notification system over telegram, see here: https://github.com/Reckless-Satoshi/robosats/issues/48 ) ℹ️ This note is an updated version of note1dqs9eumj28uc7pda7ezwxzrpqqj3j5jc0cvkjaz23jsj9p2k8evs39xkuk due to the generous addition of 20'000 sats to the bounty from #[0] (see note12k3qrdyaxx6u78tnt7gngrs2xs0sxdgj9dmpe8z408jhqm9gpskshz8cra ).
12022 - 3y
lnbc1p373g2dpp5kf7j9kwm5yd4n92f48srekvzxdkpzmdtj0c88gfxsrn8qlm5hzpqdqu2askcmr9wssx7e3q2dshgmmndp5scqzpgxqyz5vqsp5xrwwtnpavtmxskhacryf5cv8wlfevlghmq0fywvu4h6p63ncz3ts9qyyssqy5zva5ngypcjapqvhuyjnna3u38d0vn65wtascxyk62dfy9vrf8r7vf8y7zg7hd62lkl4psg7kjx7wl2c9ks6059n7upt87xax8t2ncqss6u9n
0f563 - 3y
Here's a start for anyone interested! **Is your feature request related to a problem? Please describe.** Currently, makers need to keep a browser tab open to know when their order has been taken in RoboSats. If a taker is found, the browser will play a tone to notify the maker. This works well on desktop, but it is not practical on mobile devices where the screen turns off and the sound notification never plays. **Describe the solution you'd like** Implement a Nostr private message notification system using [NIP-04](https://github.com/nostr-protocol/nips/blob/master/04.md) for makers that works similar to the current third-party notification system over Telegram. Users would receive a direct message via their Nostr pubkey once their order has been taken.
Thank you for the initial work! 🧡 I'd love to add: "The message receiver can be specified by npub and the sending nsec will be generated by random every time. Furthermore a small (between 0-30 seconds) random time delay between taking the offer and sending the nostr note should be added to avoid doxing because of timing analyses." ❓ Im not totaly sure about how the npub and nsec thing should be handled. Do you have another privacy friendly approach or thoughts about this? For example i could think of forced random nsec AND random npub receiver (for which robosata displays the nsec). Then nobody would come to the idea to use their main nostr identity but have to use one client with these burner nsec's to receive notifications. However this approach gets complicated if an user wants to have multiple offers open as a maker at the same time.
👏 Bounty has been granted to #[3] for this feature request: https://github.com/Reckless-Satoshi/robosats/issues/363 @ #[3] : Can you confirm as reply to this note that this is your work? I'll then Zap you the bounty attached to your reply note. 🙌
e7e08 - 3y
👍 Confirm. Thank you!
Bounty Zapped. Thank you very much for your work #[4] . 🧡
Hey #[3] : I've mixed some of your thoughts into the actual feature request from #[4] , which has beenpublished today on github: https://github.com/Reckless-Satoshi/robosats/issues/363
Received. Thank YOU for the bounty and your patience!
This was a good practice for lowering my time preference. 😆
But I failed finally and high time preference made me offer to publish the feature request on your behalf. 🤦
Never used Phoenix myself due to my aversion of AQUIN. 🤔 Reckless satoshi (dev of Robosats) used Blixt for most of Robosats testing and development and from my point of view Blixt is super easy and robust, except for the need of Google account for channeldb backup and no self hosted option like Nextcloud in Breeze. But manual channeldb is possible with Blixt. Maybe someone should code and PR to fix this flaw (https://github.com/hsjoberg/blixt-wallet/issues/366)? 🧡 Herewith, I set out a bounty of 20k for the PR which merges, since I just paid out my previous 23k bounty about robosats ( #[3] ) thanks to #[6] .
