I sometimes use it with Roo Code / VSCode.
bitchat 1.2.0 (purple) shipping to testflight tonight.
this enables mutual favorites to automatically switch to a nostr-based transport when one of them leaves the mesh. only for private messages for now using NIP-17.
basically people can bitchat in person, favorite each other at that time, and then can continue the conversation if internet is available through nostr, from any distance. no need to input a npub or know anything about nostr. it just works.
https://github.com/permissionlesstech/bitchat/pull/358
Is there intention to add the reverse feature too? (for nostr people who already know each other's npubs but want to use bitchat for messaging going forward)
nostr:npub15jcgp02275uw5rsrql7w57gnx6su400dx72gnr7795t565jm4rmqru44hx have you considered adding some markets pertaining to activation of various bitcoin soft-fork/upgrade proposals? Something like "will bitcoin activate ctv+csfs (or equivalent) by jan 1, 2027?"
maybe we should bitcoin+nostr+mcp this hashcash thing https://github.com/TecharoHQ/anubis but make it so that the challenge string (provided by a spam-deterring site operator) is actually the components of a prospective bitcoin block header.
If the operator is too lazy to run their own bitcoin node to construct the block template, then they can grab one from a service like mempool.space
From the visitor's perspective it is the same (they must complete the pow challenge), but at least this way every website operator can also be a solo miner.
happy to see that you are also thinking about these sorts of things! Did you look into things like [cjdns](https://github.com/cjdelisle/cjdns/) or [this](https://github.com/yggdrasil-network/yggdrasil-go) ?
answering my own question: https://stats.nostr.band/
anyone have a current estimate of the total number of unique nostr events happening per second on average across the network?
This is really interesting and exciting to see. What about embedding the nostr event id in a fresh bitcoin block template and then grinding on the actual blockheader instead of the nostr event? It is solo mining, and the block template could put various relays, charities, or whoever as recipients in the coinbase output.
actually, clicking "unfollow" on a few of them seemed to get rid of all except 1 of them.
nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk Is it a bug that when I go to my profile in iris.to and click "follows," it shows me that I am following myself 20 times?
I have been meaning to look into Fedimint, but have not yet had a chance. Would be very curious to know your take if you look into it.
fwiw, you may want to check out raspiblitz too. As for wallets on your node, since your node is hosting it, you could use something web-based like LNBits too.
nevermind, I mis-read. I see who he follows and (obviously) I know who I currently follow (it's on the right pane of my branle client). Please ignore this. Sorry for the unnecessary mentions! #[0] !
why is it that when I (using branle) click on somebody's profile like #[0] I can see who #[0] follows, but when I click on my own profile I cannot?
Regardless, great to see experiments like this happening.
Thanks! I will sign up and stack some sats then!
do you have a link? I cannot seem to find the post on there about UBI
Is anybody working on a pay-via-lightning nostr relay with inbound email address mapped to nostr pubkey (delivered via direct message on nostr)? Outbound email could be charged at higher rates to avoid spammers. Might not even need outbound service at all though.
yes, it is fixed now. Thanks!
Got it. Now it makes sense why your bot posted something about a recent bitcoin block having 78 bits of nostr difficulty. I thought for some reason you were actually mining on the bitcoin block header, but you were just re-interpreting its hash in this way. Thanks for clarifying.