2026-09-15T19:54:43Z https://nostr.now Five https://nostr.now/npub16p8v7varqwjes5hak6q7mz6pygqm4pwc6gve4mrned3xs8tz42gq7kfhdw https://nostr.build/i/nostr.build_544c76d01261e8ab387b69261ba0e62e63858188beef76d2f3999822176655f2.png https://nostr.build/i/nostr.build_544c76d01261e8ab387b69261ba0e62e63858188beef76d2f3999822176655f2.png https://nostr.now/nevent1qqsqqqyxgag9vxf9ws0vlpugxk8u4cuhtfh6fmeyez7jny5tudflkcszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqpfmq7v Join us this week if you&#39;re a builder or a fan of freedom tech:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqsqqqxz0vhvp23a07mvzdu5wq73nrf2ss2j7f9x9fp6psenfr2dqcszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqmunfvc" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…nfvc</a></span> </div> BudaBit demo days rebooted!<br/>An hour of interactive presentations and discussion about freedom tech!<br/><br/>Present your project, get feedback and discuss with builders and freedom tech enthusiasts!<br/><br/>Apply for a spot to present or just join conversation:<br/><a href="https://budabit.club/c/naddr1qvzqqqramcpzqz5wewjgdrqnu85ye3wttrqzc87s3qxeuk3955zsa6t2mzskd47gqyv8wumn8ghj7un9d3shjtnzw4jxzcnfwshxxmr4vgqyqvrp8pjkxcnpxsurvwrrxyek2vt98q6xxce4vd3r2wrrxqexxvtxvscrswpsvsuk2dtpxg6kzdfsx5cx2efexeskgwrpxymrvephvvuqvnlda2/calendar/286afe2e77241788f3730ef983bf6a9bb8acda4bd46168fb3db8493050a0e241">https://budabit.club/c/naddr1qvzqqqramcpzqz5wewjgdrqnu85ye3wttrqzc87s3qxeuk3955zsa6t2mzskd47gqyv8wumn8ghj7un9d3shjtnzw4jxzcnfwshxxmr4vgqyqvrp8pjkxcnpxsurvwrrxyek2vt98q6xxce4vd3r2wrrxqexxvtxvscrswpsvsuk2dtpxg6kzdfsx5cx2efexeskgwrpxymrvephvvuqvnlda2/calendar/286afe2e77241788f3730ef983bf6a9bb8acda4bd46168fb3db8493050a0e241</a> </blockquote> 2026-10-26T09:24:17Z https://nostr.now/nevent1qqsqqqpwptcpkaltkw5m4j23dd2tnmhe2nhejgn0kya8z8pclu7zg7szyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq6lvjq3 Sharing our work more often works magic: <br/>We have to present to other builders and must listen to potential users so we are on the hook.<br/><br/>This makes us build and explain better. Something you should master in the age of AI. <br/><br/>Join demo days to hone your skills and get inpired:<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqsqqqxz0vhvp23a07mvzdu5wq73nrf2ss2j7f9x9fp6psenfr2dqcszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqmunfvc" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…nfvc</a></span> </div> BudaBit demo days rebooted!<br/>An hour of interactive presentations and discussion about freedom tech!<br/><br/>Present your project, get feedback and discuss with builders and freedom tech enthusiasts!<br/><br/>Apply for a spot to present or just join conversation:<br/><a href="https://budabit.club/c/naddr1qvzqqqramcpzqz5wewjgdrqnu85ye3wttrqzc87s3qxeuk3955zsa6t2mzskd47gqyv8wumn8ghj7un9d3shjtnzw4jxzcnfwshxxmr4vgqyqvrp8pjkxcnpxsurvwrrxyek2vt98q6xxce4vd3r2wrrxqexxvtxvscrswpsvsuk2dtpxg6kzdfsx5cx2efexeskgwrpxymrvephvvuqvnlda2/calendar/286afe2e77241788f3730ef983bf6a9bb8acda4bd46168fb3db8493050a0e241">https://budabit.club/c/naddr1qvzqqqramcpzqz5wewjgdrqnu85ye3wttrqzc87s3qxeuk3955zsa6t2mzskd47gqyv8wumn8ghj7un9d3shjtnzw4jxzcnfwshxxmr4vgqyqvrp8pjkxcnpxsurvwrrxyek2vt98q6xxce4vd3r2wrrxqexxvtxvscrswpsvsuk2dtpxg6kzdfsx5cx2efexeskgwrpxymrvephvvuqvnlda2/calendar/286afe2e77241788f3730ef983bf6a9bb8acda4bd46168fb3db8493050a0e241</a> </blockquote> 2026-10-23T07:44:02Z https://nostr.now/nevent1qqsqqqzhvsfgs94nrvh4l63wppcattq97tue4uersnd25cfeyvcczpqzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq8epgws In reply to <a href='/nevent1qqsgujlhhran3u8dy3d2qh0e7rp3gfuqwph0dzeqaj6zws97zqeyavspp4mhxue69uhkummn9ekx7mqefalk3'>nevent1q…alk3</a><br/>_________________________<br/><br/>Very well put.<br/>I&#39;d add my 2 sats:<br/>Communities solve discovery and onboarding (trust entry point) along with social rotation of keys (trust fallback).<br/>The hard part will be thr real work to bootstrap the communities.<br/><br/> Now that clankers do the grind to code it all up, we must do the social grind to get the people.<br/><br/>Glad you&#39;re out there doing this 2026-10-22T15:00:15Z https://nostr.now/nevent1qqsqqqxz0vhvp23a07mvzdu5wq73nrf2ss2j7f9x9fp6psenfr2dqcszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqmunfvc BudaBit demo days rebooted!<br/>An hour of interactive presentations and discussion about freedom tech!<br/><br/>Present your project, get feedback and discuss with builders and freedom tech enthusiasts!<br/><br/>Apply for a spot to present or just join conversation:<br/><a href="https://budabit.club/c/naddr1qvzqqqramcpzqz5wewjgdrqnu85ye3wttrqzc87s3qxeuk3955zsa6t2mzskd47gqyv8wumn8ghj7un9d3shjtnzw4jxzcnfwshxxmr4vgqyqvrp8pjkxcnpxsurvwrrxyek2vt98q6xxce4vd3r2wrrxqexxvtxvscrswpsvsuk2dtpxg6kzdfsx5cx2efexeskgwrpxymrvephvvuqvnlda2/calendar/286afe2e77241788f3730ef983bf6a9bb8acda4bd46168fb3db8493050a0e241">https://budabit.club/c/naddr1qvzqqqramcpzqz5wewjgdrqnu85ye3wttrqzc87s3qxeuk3955zsa6t2mzskd47gqyv8wumn8ghj7un9d3shjtnzw4jxzcnfwshxxmr4vgqyqvrp8pjkxcnpxsurvwrrxyek2vt98q6xxce4vd3r2wrrxqexxvtxvscrswpsvsuk2dtpxg6kzdfsx5cx2efexeskgwrpxymrvephvvuqvnlda2/calendar/286afe2e77241788f3730ef983bf6a9bb8acda4bd46168fb3db8493050a0e241</a> 2026-10-22T12:20:27Z https://nostr.now/nevent1qqsqqqrzp72mp0dmy9n9d5g5k269q2empwxv8uw2n59cwa545ltr8qqzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqk2u4t6 In reply to <a href='/nevent1qqsqqqqg0e0zujke9vxe46j8u5xheys4dgqytpa76p06rjasvul6kkcpp4mhxue69uhkummn9ekx7mq9280em'>nevent1q…80em</a><br/>_________________________<br/><br/>The only question is whether we can find the solutions with the right tradeoffs before falling back to politics completely.<br/><br/>Bitcoin brought adaptive proof of work based money, nostr gives us the simplest primitives for sovereign identity and independently verifiable data. <br/><br/>These protocols let us design freedom oriented, natural, human-scale systems. 2026-10-06T07:21:47Z https://nostr.now/nevent1qqsqqqqg0e0zujke9vxe46j8u5xheys4dgqytpa76p06rjasvul6kkczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqgthlw0 Hard coordinaton problems in digital space should always fall back to a solution in meatspace, there will not be a time where we completely let machines decide everything for us I hope.<br/><blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqsqqqppf64d3vrqu4646zr58npy6aaezmczrztaspxgja2qd7dx8lqprpmhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmntqyxhwumn8ghj7mn0wvhxcmmvqyt8wumn8ghj7un9d3shjtnswf5k6ctv9ehx2aqzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqezn5z7" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…n5z7</a></span> </div> The problem with append only state is that remember: <br/>From the other partie's perspective who only sees your signed event, delegated signing is key rotation. <br/><br/>For your idea to work you must (as you mention) introduce an append only tracker of your key states.<br/>This is the exact point where you introduce a strict ordering burden on Nostr verification since now everyone must take a roundtrip:<br/>"Do I know this key? This could be xyz's subkey/delegated key so let's look up the original to verify the real identity" and this must be done each event.<br/><br/>And if you leak the subkey it's even worse, now you have to introduce even more extra roundtrips and edge cases where a client must look up the history of revocations with each and every event verification process. <br/><br/>So a delegation process producing a different signature will not work practically in my opinion.<br/><br/>The delegated signing process must produce the same signature as the original key.<br/>This is what FROST solves. Your nsec is sharded and you define in the key ceremony what kind of quorum you will use. <br/>Let's say 2/3. Now you keep one on a server, one on your phone and one just in cold storage (for now).<br/>If the server or the phone is compromised you get the 3rd shard and never trust the compromised one again. These tools exist already you can experiment with them. <br/><br/>The burden / complexity is now on you instead of the whole network to make sure that the compromised shard is being handled (you cannot revoke it) but realistically you can drop it, and use the other 2 or even add further keys to the quorum, making it practically 2 of 4 etc. <br/>Note that adapter signatures could be used differently but Frost has additional benefits. <br/><br/>AtProto (Bluesky) solves this by introducing a trusted so called PLC server that tracks key rotations. You cannot practically run your own equivalent because that's hardcoded into each client solving the consistency / roundtrip problem I described above. It's that theoretical thing that doesn't work in practice, and they acknowledge that. <br/><br/>All in all UX can go a long way so a co-signer FROST setup can be quite convenient to use with the right tooling, and services.<br/><br/>And if all breaks we always fall back to meatspace, there will never be a perfect solution, that's alright I think. Bitcoin can be hardforked even with overwhelming consensus.<br/>Note that key rotation is essentially just that:<br/>You want the whole world to overwhelmingly accept that the state of your identity changed. That is an oracle problem and Bitcoin handles it the same way:<br/>Leaves it open. <br/>That's why altcoins exist.<br/>You fork an identity that's your alt identity. I don't have to accept but I cannot exclude others to accept it and enforce it practically. <br/>The difference is that rotation of your identity will not affects global trade so it will be alright. </blockquote> 2026-10-06T07:14:42Z https://nostr.now/nevent1qqsqqq96k2njfxzft7lkqunakq7qjhgzkuqw5t2j9pkdlypgrc280nszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqad5ne3 In reply to <a href='/nevent1qqs9qgkealqklqajp4cvtqehh2wwdsqpq8uy9vukhsk8tpkedv6p8hspp4mhxue69uhkummn9ekx7mqvc5mz7'>nevent1q…5mz7</a><br/>_________________________<br/><br/>By the way you can create a sign in with google experience today with frost fiatjaf had a demo I think.<br/><br/>You can run a bunker signer for your mom, or later when ppl have much at stake there will be professional co-signing services. 2026-10-01T15:22:18Z https://nostr.now/nevent1qqsqqqppf64d3vrqu4646zr58npy6aaezmczrztaspxgja2qd7dx8lqzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqjasst0 In reply to <a href='/nevent1qqsr2ka7fuaga3m5ymh70afzxyewuedxrtp75rdgglk2qdcd7yznvgqpp4mhxue69uhkummn9ekx7mqd2k3ju'>nevent1q…k3ju</a><br/>_________________________<br/><br/>The problem with append only state is that remember: <br/>From the other partie&#39;s perspective who only sees your signed event, delegated signing is key rotation. <br/><br/>For your idea to work you must (as you mention) introduce an append only tracker of your key states.<br/>This is the exact point where you introduce a strict ordering burden on Nostr verification since now everyone must take a roundtrip:<br/>&#34;Do I know this key? This could be xyz&#39;s subkey/delegated key so let&#39;s look up the original to verify the real identity&#34; and this must be done each event.<br/><br/>And if you leak the subkey it&#39;s even worse, now you have to introduce even more extra roundtrips and edge cases where a client must look up the history of revocations with each and every event verification process. <br/><br/>So a delegation process producing a different signature will not work practically in my opinion.<br/><br/>The delegated signing process must produce the same signature as the original key.<br/>This is what FROST solves. Your nsec is sharded and you define in the key ceremony what kind of quorum you will use. <br/>Let&#39;s say 2/3. Now you keep one on a server, one on your phone and one just in cold storage (for now).<br/>If the server or the phone is compromised you get the 3rd shard and never trust the compromised one again. These tools exist already you can experiment with them. <br/><br/>The burden / complexity is now on you instead of the whole network to make sure that the compromised shard is being handled (you cannot revoke it) but realistically you can drop it, and use the other 2 or even add further keys to the quorum, making it practically 2 of 4 etc. <br/>Note that adapter signatures could be used differently but Frost has additional benefits. <br/><br/>AtProto (Bluesky) solves this by introducing a trusted so called PLC server that tracks key rotations. You cannot practically run your own equivalent because that&#39;s hardcoded into each client solving the consistency / roundtrip problem I described above. It&#39;s that theoretical thing that doesn&#39;t work in practice, and they acknowledge that. <br/><br/>All in all UX can go a long way so a co-signer FROST setup can be quite convenient to use with the right tooling, and services.<br/><br/>And if all breaks we always fall back to meatspace, there will never be a perfect solution, that&#39;s alright I think. Bitcoin can be hardforked even with overwhelming consensus.<br/>Note that key rotation is essentially just that:<br/>You want the whole world to overwhelmingly accept that the state of your identity changed. That is an oracle problem and Bitcoin handles it the same way:<br/>Leaves it open. <br/>That&#39;s why altcoins exist.<br/>You fork an identity that&#39;s your alt identity. I don&#39;t have to accept but I cannot exclude others to accept it and enforce it practically. <br/>The difference is that rotation of your identity will not affects global trade so it will be alright. 2026-10-01T15:15:58Z https://nostr.now/nevent1qqsqqqy4smav9grzkrnagg695nhxpzj87p9dj6hdzed974xvkjh6drqzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqz5txqw In reply to <a href='/nevent1qqswgt0d4t9tsky9v8v55lnznczvuv05nrsp8ehd8sgde2yagpz8v2gpzdmhxue69uhkzmr8duh82arcduhx7mn9vn7jdy'>nevent1q…7jdy</a><br/>_________________________<br/><br/>So I guess you considered #Frost if you have been thinking about this for a long time but you haven&#39;t mentioned it. Why?<br/><br/>Key rotation on the nsec level will hardly be a thing unless there&#39;s some cryptographic breakthrough because it would centralize the protocol, see PLC in atprotocol and such.<br/>You basically must centralize key lineage tracking to a trusted party but that just doesn&#39;t go well in a distributed system.<br/><br/>Frost shard-based signing UX can be very stable and fairly revocable, it&#39;s just not yet spread so much. <br/><br/>Social rotation is the other way, it&#39;s been talked about many times. It is a viable alternative in a network like nostr, especially if communities get more popular.<br/><br/>The reason why there&#39;s not too much anxiety over this is just the fact that there&#39;s not yet enough demand I think for nostr in general.<br/><br/>We&#39;re building things out and if there&#39;s real pressure in the future from economically relevant users accruing, at some point it&#39;s gonna be figured out. 2026-09-25T17:33:22Z https://nostr.now/nevent1qqsqqqxv2xxc4060nfjxjcgp974eycg4tnwc5tlzref0088mgxmv9yczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqpyxqqe Throwback:<br/><video controls width="100%" class="max-h-[90vh] bg-neutral-300 dark:bg-zinc-700"><source src="https://v.nostr.build/5B2y.mp4"></video> 2026-08-02T04:34:45Z https://nostr.now/nevent1qqsqqqqqcy2a837wuycm6pa9yexhvxuj6pwnrfew3j48lqe222c39sgzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqed8gc7 In reply to <a href='/nevent1qqs28ejp5e7htr3v8gdsc3qm8e0737tt9mwhvr60ut37m3pxsghv3cspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgf36m6g'>nevent1q…6m6g</a><br/>_________________________<br/><br/>Do you think Spark and Ark require comparable fees to exit unilaterally? Have you seen a similar study for Ark?<br/><br/>This data liveness requirement is painful but I think comparable to the pain of expiring VTXOs in Ark. There you already always have the state to publish for the unilateral exit but you (wallet or watchtower) must monitor the expiry deadlines.<br/><br/>Of course the other thing is that ark operators are less trusted since they cannot conspire to steal funds.<br/>However I still love Spark because at the end of the day operators don&#39;t have enormous liquidity requirements and this will make a big difference in adoption. <br/><br/>Also in Ark has that constant periodical refresh from user wallets, that doesn&#39;t look good to me. I don&#39;t necessarily open my wallets every month and this is going to be a problem when a lot of users realize this (or have to pay extra for a refresher service).<br/><br/>All in all love the innovation of the L2 space 2026-07-09T05:13:26Z https://nostr.now/nevent1qqsqqqzqtf7v0r5k6xx0zg3vce3uereyfp4sdrhmezwal4m9hltxvkczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqgnjzwm In reply to <a href='/nevent1qqsd5g6cm6ex77cxrt6vj44zdhwd5t3rhkttluxzzlvfkavkvdg3v3gpp4mhxue69uhkummn9ekx7mqf9k24w'>nevent1q…k24w</a><br/>_________________________<br/><br/>BudaBit.club has fine-grained client side enforced moderation features. <br/>However, I understand currently you guys want a tried and tested grug brain solution. <br/><br/>Would love any feedback though! If you get the time, it&#39;s just a few minutes to create a test group.<br/><br/>Nostr is easy to hack on so custom solutions can be built relatively simply. You wouldn&#39;t be married to forgejo as a platform and make people use dozens of accounts to talk about bitcoin and do basic collaboration.<br/><br/>I know IRC and old forums have their vintage charms but we can have open solutions with good ux today using nostr. Even moderation becomes easier since nostr keys can be used in multiple places so you have more context to work with. AI issues also become much more tenable this way. <br/><br/>Anyway wish you guys success with the migration process! 2026-06-23T08:44:04Z https://nostr.now/nevent1qqsqqq92qzlj9xmrkrkrwq0vwnvrasxf4vcsezjhgwl4ctqhyztj6rszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqkngc80 In reply to <a href='/nevent1qqs20qddkkv6qnft8nk7s8gsmhtfhgluvsqptqw63w0wj27fcawvglgpzpmhxue69uhkummnw3ezumrpdejqk5hr75'>nevent1q…hr75</a><br/>_________________________<br/><br/>- Getting the right phone is not trivial. Product descriptions suck mostly and it is quite important in this case<br/>- I got through installation fairly easily being a dev but there are many people who would not. Jargon heavy explanations and lots of custom steps depending on the platform of the machine it&#39;s installed from. Some trusted distributor should sell pre-installed devices if not yet the case. <br/>- Google pay and wallet does not work. I know why that is, fiat is painful <br/>- For some reason google account login does not trigger for me<br/>- Contacts had to be manually exported and imported<br/>- Signal can be a hassle to migrate from manual backup. Generally less user friendly migration and linking to other devices compared to captured instant messaging apps<br/>- Many settings are not clear what they do and I don&#39;t think most people need &#39;hardened memory allocator&#39; or such settings. They should be behind an advanced mode<br/>- Also &#34;xyz app used play integrity api&#34; doesn&#39;t mean anything to most users, I would expose that differently<br/>- Great variability in experience depending on how private and secure someone wants to be. For me iVPN blocked all network connections when VPN was off. I switched off because gmaps would not load directions while on VPN. The number of such hard to troubleshoot issues will grow as we march towards apps and services heavily relying on captured infra<br/>Storage scopes are a good idea but I find it hard to fine tune all apps and then debug yet another set of issues due to apps nowadays asking for too many perms. Sad reality.<br/>- Silent link and esims also hard to deal with but most people won&#39;t go there I guess<br/><br/>These came to mind 2026-06-22T14:13:27Z https://nostr.now/nevent1qqsqqqytm9l50fsdfc5r323axgk4d4flhmmwsj2f66dlydtvk3akffczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqgd9a8c Gradually then...<br/><br/> <img src="https://blossom.primal.net/4248342f43411f6b24c9841171d3e84cdd089102b279e26b71b31f82cec9d6bd.jpg"> <br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqsr6tj32zrfn7v0pu4aheaytdnnc6rluepq73ndc2tdjzus34gat9qytmrj5" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>matt</span> (<span class="italic">nprofile…mrj5</span>)</a></span> many have moved to forgejo / Codeberg for the forge and CI e.g. Zig and Ghostty I think. Nostr-git should work better for a public facing open project though, at least in the long run.<br/><br/>If you want to experiment with a moderated social development experience I am keen to hear feedback on #BudaBit :<br/><a href="https://budabit.org">https://budabit.org</a><br/><br/>We plan to roll out CI over nostr soon, each community providing for their members for free or for ecash.<br/>Then releases signed with nostr keys. <br/><br/>#gitvianostr 2026-06-21T16:48:45Z https://nostr.now/nevent1qqsqqq8xs5dv3yhftyp2r2yy7x4z6j3qw9ssut4qvsa7jsfsdjzswgszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqf2kpc6 <img src="https://blossom.primal.net/1998ac02bf840640b3851d4b824d0aa5f3978489a64b9310538cbfe3711a5f1a.jpg"> <br/><br/><a href="https://keepandroidopen.org/">https://keepandroidopen.org/</a> 2026-06-09T12:28:48Z https://nostr.now/nevent1qqs07mzgj3jdmrax02c7njx4ec28u08hwu87fem3m59gxsfyhr7894qzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqdmncm7 Nip17 only works if ecash stamps proliferate. Otherwise it is trivial to spam relays into oblivion with giftwraps. <br/><br/>As I said before: you pay (ecash, or by self hosting) or trust (eg web of trust relay, uncle jim, group relay). <br/><br/>No other way I see around this.<br/><br/>Also it is worth putting DMs in context:<br/>- Is it for a p2p marketplace?<br/>- A dissident / freedom-fighter group?<br/>- A developer community?<br/>- A group for random cat-memes? <br/>- One-to-one, few-to-few or many-to-many? <br/><br/>Don&#39;t think black and white, and don&#39;t think that one spec rules all. It almost never is the case. 2026-04-16T09:32:01Z https://nostr.now/nevent1qqstevn3muugrwzj3fuml92pfmvaz9r64h9ewytv0yqye5df9fvfsdczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq70s7fq In reply to <a href='/nevent1qqst8uamd96fqjasg27qcjp68pnl2tjysd0y00u4tsecy3dfttpdlaswge2sf'>nevent1q…e2sf</a><br/>_________________________<br/><br/>You can&#39;t just change already signed data to conform to new standards. Once it&#39;s signed you must &#34;for ever&#34;maintain backward compatibility for that old data. 2026-04-12T17:59:06Z https://nostr.now/nevent1qqsp23devqcww0gd62k2qsry3usky3f5evvltakjysqhhzp57dl9tjszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq6rvkfq Get your demos ready!<blockquote class="border-l-05rem border-l-strongpink border-solid"><div class="-ml-4 bg-gradient-to-r from-gray-100 dark:from-zinc-800 to-transparent mr-0 mt-0 mb-4 pl-4 pr-2 py-2">quoting <br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Article"><a itemprop="url" href="/nevent1qqs2cs8capmdyz2599na3vvzr6v56x5wd9mwxvc0w842fjz382nlchszyq9gajays6xp8c0gfnzukkxq9s0apzqdnedztfg9pm5k4k9pvmtusqcyqqqqqqghvd3nw" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1">nevent1q…d3nw</a></span> </div> #BudaBit Demo Day!<br/>Showcase your awesome work in Freedom tech again!<br/>Date: 02/18 15:30 UTC - 16:30<br/>Apply with your demo:<br/><a href="https://budabit.club">https://budabit.club</a><br/><br/>BudaBit: Learn. Share. Connect. </blockquote> 2026-02-12T17:27:23Z https://nostr.now/nevent1qqstkxyn26e748d0wg0slrypqqqzv3ml9g9760dkq99w8cx8qspfnmczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq3dyddx <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqswfa547pdmqkerzf2uen3agudc67wxffjmenqpge3dylc006fppyspp4mhxue69uhkummn9ekx7mqpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qa3xytq" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>merryoscar</span> (<span class="italic">nprofile…xytq</span>)</a></span> fountain subs are buggy.<br/>You say sub from $5 (5.530 sats) which is then converted to $55.30 incorrectly and that amount is calculated in sats (61.162) .<br/><br/>This is a serious bug fix it soon.<br/> <img src="https://i.nostr.build/Zo6MKhhFM1jWNc3F.jpg"> <br/> <img src="https://i.nostr.build/57pLFYapNwFOqGtt.jpg"> 2025-12-13T08:02:12Z https://nostr.now/nevent1qqsta43apyff86e3s83g92d95zspdhmzs7qanc2v836jj0h8fcnncyczyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqupc3gm In reply to <a href='/nevent1qqsxv6qlfegqx2vhwy7r0xt5p3qlmfm4dr5achwacv09v2w8mv8te7cg2rszs'>nevent1q…rszs</a><br/>_________________________<br/><br/>Full Grasp support coming to BudaBit soon, the primitives are already implemented.<br/><br/>1. What we struggled with is the creation flow where we first post the repo announcement then the newly created git repo, but that must be done with an arbitrary sleep(X ms) wait time so that&#39;s not really ideal.<br/><br/>You guys have ideas to improve this flow?<br/><br/>2. I think it this was discussed before but want to get a fresh opinion of yall: Unified grasp api for file browsing and perhaps diffs and really data-heavy ops? Cloning repos via git smart http can still be a fallback but this would benefit performance a lot. Blossom has an api as well so I guess this would make sense, especially in a browser context.<br/><br/><span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>fiatjaf</span> (<span class="italic">nprofile…xuyp</span>)</a></span> <span itemprop="mentions" itemscope itemtype="https://schema.org/Person"><a itemprop="url" href="/nprofile1qqs2qzx779ted7af5rt04vzw3l2hpzfgtk0a2pw6t2plaz4d2734vngpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsq3camnwvaz7tmgv9mx2m3wv3skucm0demkz7tyv4mzucm0d5p6s74j" class="bg-lavender dark:prose:text-neutral-50 dark:text-neutral-50 dark:bg-garnet px-1"><span>DanConwayDev</span> (<span class="italic">nprofile…s74j</span>)</a></span> 2025-11-27T14:20:09Z https://nostr.now/nevent1qqswwyxeayn6jcjxlk3m7kkya9v4y8vtfwuja67tap2er9eq82hu5tgzyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq64rx4e Dev story time: How SatShoot ended up using partial #outbox model:<br/><br/>Using NIP65 relay lists to decentralize discovery looks like a fantastic concept at first...<br/><br/>And then you realize that most things taken to extremes ends up in the complete opposite way you intended.<br/><br/>This is true for the outbox model. You want decentralization. Maybe you convinced a lot of people to publish outbox relay lists (BIG maybe), so far so good. Still, you ended up with an app that connects to hundreds of relays **and keeps those connections alive**.<br/><br/>Problems:<br/>- app uses a lot of data<br/>- app will make your phone run flat in no time<br/>- app likely gets heavily resource constrained by the OS when user switches away, relay conns are killed<br/>- app code has tremendous added complexity (perhaps the worst of all!)<br/><br/>So what this effectively ends up doing is:<br/>- only native apps will be able to handle this kind of load, maybe only desktop apps<br/>- only people with close-to unlimited data plans will be able to use your app<br/>- very few people will be able to understand your code, if any (including you)<br/><br/>So you ended up introducing all these centralizing dynamics, while users don&#39;t even understand or appreciate why you did it. And of course it all still relies on purplepages to fetch the initial lists, right? ;)<br/><br/>I had a better idea (communities are even better but until they come online this is my approach):<br/><br/>1. Use explicit relays by default, let normal users set explicit relays, and superusers set outbox too<br/><br/>2. Publishing is simple since it is targeted: you just publish to explicit relays + outbox (or inbox of target if it&#39;s a reaction to sth or mentioning someone)<br/><br/>3. You calculate optimal relays and fetch all relevant events ONE time, on a user-triggered &#34;Decentralized Discovery&#34;. This should explain what&#39;s happening and why it&#39;s super cool.<br/><br/>4. Show the progress and at the end, add top relays to the pool for that session<br/><br/>5. User thinks &#34;This is cool, I&#39;m doing the Decentralized Discovery, Nostr Rocks!&#34; and you did not have to keep all those connections and constantly keep score and all that. Just do it once.<br/><br/>This is now implemented in SatShoot:<br/><video controls width="100%" class="max-h-[90vh] bg-neutral-300 dark:bg-zinc-700"><source src="https://v.nostr.build/8bZAOIjVjsCf41pm.mp4"></video><br/><br/>Opinions? 2025-10-20T16:30:34Z https://nostr.now/nevent1qqs05ztaaj7m7mfg6ks3y6mgse4ww8rdvpn0vz6za2fnzpph253j57czyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fqkqrfcj In reply to <a href='/nevent1qqs2u69k5t0p7gms5fggwepsaxxdulfmvjqpdh7c720a4mx5ppfexdcqr3m9h'>nevent1q…3m9h</a><br/>_________________________<br/><br/>I&#39;m not looking for an authority to form opinions, and I encourage you to do the same.<br/>Explaining how bitcoin incentives will play out using bayesian methods is a fools errand in my book:<br/>- How do we know the rate of lost coins in the future, or the ratio of fees in the reward? Extrapolate from the past? There&#39;s no reason to accept that logic<br/><br/>- How do we know that miners need this extra subsidy, when other crypto currencies have never even come close to being adopted as money, and bitcoin is also far from it?<br/><br/>&#34;...academic analysis has found that in this condition [only fees in the reward] block generation is unstable.&#34; - So they claim to know how this would work, even though there&#39;s absolutely no way to know this.<br/><br/>&#34;The fact is, economic volatility dwarfs the effect of small amounts of inflation. Even a 0.5% inflation rate over 50 years only leads to a 22% drop&#34;<br/>*Only*. Really? Who says that&#39;s so low? This line of reasoning looks like taken directly from a Keynesian textbook. And taking bitcoin&#39;s current volatility as an example is just a blatant error at least, disingenuous at worst.<br/><br/>I&#39;m all for good explanations, but this is a weak one, because I can substitute these arbitrary numbers and angles with any others that suit my needs. It&#39;s statistical cosmetics.<br/><br/>The future of bitcoin and mining is fundamentally unpredictable because humans are. Therefore, I like explanations based on first principles but no amount of statistical trickery will do any good in this matter.<br/><br/>I respect Peter Todd. But this is nothing but a &#34;nice excuse to use some mildly interesting math, in the end it’s totally pedantic.&#34;<br/><br/>Austrian economics teaches you a lot on these matters, can recommend those instead. 2025-05-03T10:56:39Z https://nostr.now/nevent1qqsxxx6sql6ehtkmvnk8y9kakp39nqfv74v6kz5juxl87hfls2vk5dszyrgyanen5vp6txzjlkmgrmvtgy3qrw59mrfpnxhvw09ky6qav24fq886ya2 In reply to <a href='/nevent1qqsvs0mes40a5f6ykhe4vqawjdtn3mga89977tlqyv3hdz6jl90t8dgszrdn7'>nevent1q…rdn7</a><br/>_________________________<br/><br/>Sorry, but this is bogus.<br/>Trying to describe what will happen to bitcoin with Bayesian probabilities leads to really bad conclusions. This is what Keynesians try to do in fiat economics textbooks.<br/><br/>It doesn&#39;t even scratch the surface of reality. 2025-05-03T10:00:16Z