Yes, but I exprssed myself unclear: Zaps don't provide more attentiin from the npubs which follow me, the Zapper of a note. Whereas reposting does.
❌ I didn't wanted to be this a reply in this thread. 🤦
😫 Since I starded Zapping, Tor latency became a pain. I barely remember the good old Zap free -- latency felt free days. 🙇
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] .
😫 Since I starded Zapping, Tor latency became a pain. I barely remember the good old Zap free -- latency felt free days. 🙇
❇️ Adding an alternative payout condition for this bounty:
➡️ Implement automated write channeldb backup into local folder whenever the channeldb changes ⬅️
Inspired by #[3] 's note #[1]
ℹ️Manual saving the backup file to the device is possible with Blixt already.
This is my thought as well, every time I come across a Nextcloud integration. Why not just leave the sync provider to the user and do automated write in folder when the channeldb changes. Would open doors for easier syncs like Synchting and all the others beside Nextcloud.
✅ Added your idea as eligible bounty payout condition.
This is the corresponding github issue: https://github.com/hsjoberg/blixt-wallet/issues/366
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] .
🌽 20k sats bounty for enhancing Blixt wallet with a function to backup to nextcloud.
🧡 Any Zaps to this note will be added to the bounty pool.
🕯 I am going to post the bounty sum in the github issue at block height 778700 (~ 5 days from now). Possible to front run any non Nostriches to get the bounty as well as to top up the bounty for the fame of nostr in the eyes of the users lookig at the issue on github . 🧡
#plebchain #bounty #blixt #noncustodial #wallet #lightning
ℹ️ root note for this bounty:
#[0]
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] .
Upgrade your friends onto nostr and inform them then.
Consider using Blixt wallet as your LN wallet replacement. Non-custodiall, non "vendor lock in" for channels (aka routing fees) like Breez and Phoenix, no channel setup fees other than the actual on chain fees and as easy as Phoenix and Breez. Android and iOS compatible.
This was a good practice for lowering my time preference. 😆
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.
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
👏 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. 🙌
#[2]
👏 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. 🙌