KoalaSat

Still true nostr:nevent1qvzqqqqqqypzqs6jx7xlm8z49m7qxgp7cr8z3pjj40c0z5ue4vrgz5sk46p64xwgqydhwumn8ghj7mn0wd68ytnnv968xarjv9kxjcfwvdhk6tcppemhxue69uhkummn9ekx7mp0qqstyn0hhhy8a4zu8zyeapsxgfyk7w49ykt6kdeddvsxxnezgw3g79c2ddejd

The Bitcoin market is whatever is happening in https://p2p.band

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what's the new way of doing `HttpClientManager.setDefaultProxy(getTorKmpObject().proxy)` with the new version of quartz?

nostr:nprofile1qqszfrv3m6acxyqy4ghuega2n74rntkrfg9sp4pmse94vul56gnul8cpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs33xu96 for Raspberry Pi: WIP

Interoperability is not negotiable

nostr:nprofile1qqs8y6s7ycwvv36xwn5zsh3e2xemkyumaxnh85dv7jwus6xmscdpcygpz9mhxue69uhkummnw3ezumrpdejz76jympz seems like the sever ran by zapstore-cli to sign with NIP-07 can't detect nos2x-fox, any clue?

Yes, you can receive now Robosats notifications on #Amethyst or @Pokey But these events are only available in Coordinator's relays, which are only exposed through Tor.

Nostr notifications ready for nostr:nprofile1qqsyx53h3h7ec4fwlspjq0kqec5gv54t7rc48xdtq6q4y94wsw4fnjqprdmhxue69uhkummnw3ezuumpw3ehgunpd35kztnrdakj7qghwaehxw309aex2mrp0yhrq7rrdpshgtnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uhgml9t' next release. Every Robot will deterministically generate their own nsec and Coordinators will send NIP-17 messages the same way they do for Telegram. Web and Android clients will fetch for them and display in their own notifications center. No more 5 minutes queries, notifications are instant 🚀

Thanks everybody for the feedback, I think I fixed all errors reported, please give it another try 🥰 https://github.com/RoboSats/robosats/releases/tag/v0.8.1-test Notifications are implemented BUT are not going to work cause that requites Coordinators to upgrade WARNING This version will overwrite any previous version. Make sure you backed up all your robot tokens.