@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/900550

@ b4403b24:83542d4e

https://x.com/JacquiHeinrich/status/1895547519117246611 originally posted at https://stacker.news/items/900278

@ 2e8970de:63345c7a

Atlanta Fed is now projecting Q1 GDP -1.5%. Last week it was +2.3%. 4 weeks ago it was +3.9%  https://x.com/AtlantaFed/status/1895508046215852476 originally posted at https://stacker.news/items/899962

@ 6260f29f:2ee2fcd4

<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;max-width:100%;"><video style="position:absolute;top:0;left:0;width:100%;height:100%;border:0;" controls> <source src="https://plebdevs-bucket.nyc3.cdn.digitaloceanspaces.com/testr.mp4" type="video/mp4"/> </video></div>

@ b2d670de:907f9d4a

# onion-service-nostr-relays A list of nostr relays exposed as onion services. ## The list | Relay name | Description | Onion url | Operator | Payment URL | Payment options | | --- | --- | --- | --- | --- | --- | | nostr.oxtr.dev | Same relay as clearnet relay nostr.oxtr.dev | ws://oxtrdevav64z64yb7x6rjg4ntzqjhedm5b5zjqulugknhzr46ny2qbad.onion | [operator](nostr:nprofile1qqst94nsmefmya53crp5qq39kewrtgndqcynhnzp7j8lcu0qjple6jspz3mhxue69uhkummnw3ezummcw3ezuer9wcq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7jxrgyy) | N/A | N/A | | relay.snort.social | Same relay as clearnet relay relay.snort.social | wss://skzzn6cimfdv5e2phjc4yr5v7ikbxtn5f7dkwn5c7v47tduzlbosqmqd.onion | [operator](nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgpzpmhxue69uhkummnw3ezuamfdejszxrhwden5te0wfjkccte9eekummjwsh8xmmrd9skct9tyup) | N/A | N/A | | nostr.thesamecat.io | Same relay as clearnet relay nostr.thesamecat.io | ws://2jsnlhfnelig5acq6iacydmzdbdmg7xwunm4xl6qwbvzacw4lwrjmlyd.onion | [operator](nostr:npub1wtuh24gpuxjyvnmjwlvxzg8k0elhasagfmmgz0x8vp4ltcy8ples54e7js) | N/A | N/A | | nostr.land | The nostr.land paid relay (same as clearnet) | ws://nostrland2gdw7g3y77ctftovvil76vquipymo7tsctlxpiwknevzfid.onion | [operator](nostr:npub12262qa4uhw7u8gdwlgmntqtv7aye8vdcmvszkqwgs0zchel6mz7s6cgrkj) | [Payment URL](http://nostrland2gdw7g3y77ctftovvil76vquipymo7tsctlxpiwknevzfid.onion) | BTC LN | | bitcoiner.social | No auth required, currently | ws://bitcoinr6de5lkvx4tpwdmzrdfdpla5sya2afwpcabjup2xpi5dulbad.onion | [operator](nostr:npub1an3nz7lczcunpdw6ltjst94hgzcxpppnk7zk3zr2nfcj4yd96kdse6twjd) | N/A | N/A | | relay.westernbtc.com | The westernbtc.com paid relay | ws://westbtcebhgi4ilxxziefho6bqu5lqwa5ncfjefnfebbhx2cwqx5knyd.onion | [operator](nostr:npub1pc57ls4rad5kvsp733suhzl2d4u9y7h4upt952a2pucnalc59teq33dmza) | [Payment URL](hjar34h5zwgtvxr345q7rncso3dhdaryuxgri3lu7lbhmnzvin72z5ad.onion) | BTC LN | | freelay.sovbit.host | Free relay for sovbit.host | ws://sovbitm2enxfr5ot6qscwy5ermdffbqscy66wirkbsigvcshumyzbbqd.onion | [operator](nostr:npub1gnwpctdec0aa00hfy4lvadftu08ccs9677mr73h9ddv2zvw8fu9smmerrq) | N/A | N/A | | nostr.sovbit.host | Paid relay for sovbit.host | ws://sovbitgz5uqyh7jwcsudq4sspxlj4kbnurvd3xarkkx2use3k6rlibqd.onion | [operator](nostr:npub1gnwpctdec0aa00hfy4lvadftu08ccs9677mr73h9ddv2zvw8fu9smmerrq) | N/A | N/A | | nostr.wine | 🍷 [nostr.wine](https://nostr.wine) relay | ws://nostrwinemdptvqukjttinajfeedhf46hfd5bz2aj2q5uwp7zros3nad.onion | [operator](nostr:npub1fyvwkve2gxm3h2d8fvwuvsnkell4jtj4zpae8w4w8zhn2g89t96s0tsfuk) | [Payment URL](http://nostrwinemdptvqukjttinajfeedhf46hfd5bz2aj2q5uwp7zros3nad.onion) | BTC LN, BTC, Credit Card/CashApp (Stripe) | | inbox.nostr.wine | 🍷 [inbox.nostr.wine](https://inbox.nostr.wine) relay | ws://wineinboxkayswlofkugkjwhoyi744qvlzdxlmdvwe7cei2xxy4gc6ad.onion | [operator](nostr:npub1fyvwkve2gxm3h2d8fvwuvsnkell4jtj4zpae8w4w8zhn2g89t96s0tsfuk) | [Payment URL](http://wineinboxkayswlofkugkjwhoyi744qvlzdxlmdvwe7cei2xxy4gc6ad.onion) | BTC LN, BTC | | filter.nostr.wine | 🍷 [filter.nostr.wine](https://filter.nostr.wine) proxy relay | ws://winefiltermhqixxzmnzxhrmaufpnfq3rmjcl6ei45iy4aidrngpsyid.onion | [operator](nostr:npub1fyvwkve2gxm3h2d8fvwuvsnkell4jtj4zpae8w4w8zhn2g89t96s0tsfuk) | [Payment URL](http://nostrwinemdptvqukjttinajfeedhf46hfd5bz2aj2q5uwp7zros3nad.onion/add-time) | BTC LN, BTC | | N/A | N/A | ws://pzfw4uteha62iwkzm3lycabk4pbtcr67cg5ymp5i3xwrpt3t24m6tzad.onion:81 | [operator](nostr:nprofile1q9z8wue69uhky6t5vdhkjmnjxejx2dtvddm8sdr5wpmkgmt6wfjxversd3sn2umevyexzenhwp3kzcn2w4cry7rsdy6kgatvvfskgtn0de5k7m30q9z8wue69uhk77r5wfjx2anpwcmrg73kx3ukydmcxeex5ee5de685ut2dpjkgmf4vg6h56n3w4k82emtde585u35xeh8jvn3vfskgtn0de5k7m30qqs93v545xjl0w8865rhw7kte0mkjxst88rk3k3xj53q4zdxm2zu5ectdn2z6) | N/A | N/A | | nostr.fractalized.net | Free relay for fractalized.net | ws://xvgox2zzo7cfxcjrd2llrkthvjs5t7efoalu34s6lmkqhvzvrms6ipyd.onion | [operator](nostr:npub1ky4kxtyg0uxgw8g5p5mmedh8c8s6sqny6zmaaqj44gv4rk0plaus3m4fd2) | N/A | N/A | | nfrelay.app | [nfrelay.app](https://nfrelay.app) aggregator relay (nostr-filter-relay) | ws://nfrelay6saohkmipikquvrn6d64dzxivhmcdcj4d5i7wxis47xwsriyd.onion | [operator](nostr:npub19dn7fq9hlxwjsdtgf28hyakcdmd73cccaf2u7a7vl42echey7ezs2hwja7) | N/A | N/A | relay.nostr.net | Public relay from nostr.net (Same as clearnet) | ws://nostrnetl6yd5whkldj3vqsxyyaq3tkuspy23a3qgx7cdepb4564qgqd.onion | [operator](https://nostr.at/aljaz@nostr.si) | N/A | N/A | | nerostrator | Free to read, pay XMR to relay | ws://nerostrrgb5fhj6dnzhjbgmnkpy2berdlczh6tuh2jsqrjok3j4zoxid.onion | [operator](nostr:npub19j7zhftjfjnep4xa7zxhevschkqdvem9zr26dq4myhu6d62p3gqs3htnca) |[Payment URL](http://nerostrrgb5fhj6dnzhjbgmnkpy2berdlczh6tuh2jsqrjok3j4zoxid.onion) | XMR | | nostr.girino.org | Public relay from nostr.girino.org | ws://gnostr2jnapk72mnagq3cuykfon73temzp77hcbncn4silgt77boruid.onion | [operator](nostr:npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz) | N/A | N/A | | wot.girino.org | WoT relay from wot.girino.org | ws://girwot2koy3kvj6fk7oseoqazp5vwbeawocb3m27jcqtah65f2fkl3yd.onion | [operator](nostr:npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz) | N/A | N/A | | haven.girino.org/{outbox, inbox, chat, private} | Haven smart relay from haven.girino.org | ws://ghaven2hi3qn2riitw7ymaztdpztrvmm337e2pgkacfh3rnscaoxjoad.onion/{outbox, inbox, chat, private} | [operator](nostr:npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz) | N/A | N/A | | relay.nostpy.lol | Free Web of Trust relay (Same as clearnet) | ws://pemgkkqjqjde7y2emc2hpxocexugbixp42o4zymznil6zfegx5nfp4id.onion | [operator](nostr:nprofile1qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszxrhwden5te0dehhxarj9enx6apwwa5h5tnzd9az7qpqg5pm4gf8hh7skp2rsnw9h2pvkr32sdnuhkcx9yte7qxmrg6v4txqr5amve) |N/A | N/A | | Poster.place Nostr Relay | N/A | ws://dmw5wbawyovz7fcahvguwkw4sknsqsalffwctioeoqkvvy7ygjbcuoad.onion | [operator](nostr:nprofile1qqsr836yylem9deatcu08ekfj8qj9f2aypq8ydt0w8dyng8zp8akjsqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds6xxx6y) | N/A | N/A | | Azzamo Relay | [Azzamo](https://azzamo.net/relays/) Premium Nostr relay. (paid) | ws://q6a7m5qkyonzb5fk5yv4jyu3ar44hqedn7wjopg737lit2ckkhx2nyid.onion | [operator](nostr:npub1jjn20zj6awa6gz73423zxjqszvkzmqqyhwghwctvgy7ncrwlxg8qdavknm) | [Payment URL](https://azzamo.net/pay) | BTC LN | | Azzamo Inbox Relay | [Azzamo](https://azzamo.net/inbox-relay/) Group and Private message relay. (Freemium) | ws://gp5kiwqfw7t2fwb3rfts2aekoph4x7pj5pv65re2y6hzaujsxewanbqd.onion | [operator](nostr:npub1jjn20zj6awa6gz73423zxjqszvkzmqqyhwghwctvgy7ncrwlxg8qdavknm) | [Payment URL](https://azzamo.net/pay) | BTC LN | | Noderunners Relay | The official [Noderunners](https://noderunners.network) Nostr Relay. | ws://35vr3xigzjv2xyzfyif6o2gksmkioppy4rmwag7d4bqmwuccs2u4jaid.onion | [operator](nostr:nprofile1qqsqarzpaw2xv4cc36n092krdsj78yll7n2pfx5rv7fzp4n9jhlsl2spz3mhxue69uhhwmm59esh57npd4hjumn9wsq3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tqd6ns) | [Payment URL](https://noderunners.azzamo.net) | BTC LN | ## Contributing Contributions are encouraged to keep this document alive. Just open a PR and I'll have it tested and merged. The onion URL is the only mandatory column, the rest is just nice-to-have metadata about the relay. Put `N/A` in empty columns. If you want to contribute anonymously, please contact me on [SimpleX](https://simplex.chat/contact#/?v=2&smp=smp%3A%2F%2F0YuTwO05YJWS8rkjn9eLJDjQhFKvIYd8d4xG8X1blIU%3D%40smp8.simplex.im%2FZ_4q0Nv91wCk8Uekyiaas7NSr-nEDir7%23%2F%3Fv%3D1-2%26dh%3DMCowBQYDK2VuAyEAvdSLn5QEwrfKQswQGTzlwtXeLMXbzxErv-zOJU6D0y8%253D%26srv%3Dbeccx4yfxxbvyhqypaavemqurytl6hozr47wfc7uuecacjqdvwpw2xid.onion) or send a DM on nostr using a disposable npub. ### Operator column It is generally preferred to use something that includes a NIP-19 string, either just the string or a url that contains the NIP-19 string in it (e.g. an njump url).

@ 000002de:c05780a7

The newly installed FBI Director Kash Patel was sworn in on a Bhagavad Gita (Hindu holy book) NOT a Christian Bible! Guys, its happening! Christian Nationalism is here. We predicted that Trump would introduce a government ruled by Christians for Christians persecuting people of other faiths. Its just a matter of weeks until we are in full blown Handmaids Tale! Time to get out. Get out while you can. originally posted at https://stacker.news/items/899838

@ 5d4b6c8d:8a1c1ee3

I've been very hopeful that the proposal to replace the IRS, and all of the taxes it collects, with a combination of sales taxes and tariffs, will go through, but just this morning some of the secondary effects of such a change occurred to me. Now, I'm even more hopeful that this happens. # The Obvious Benefits My initial reasons for excitement were the obvious ones: consumption based taxes have better incentives than production based taxes (I know tax incidence muddies the waters, but this is still true) and consumption taxes are more avoidable than the slew of individual and corporate taxes currently in place. # Financial Privacy One second order benefit occurred to me immediately: Without taxes on income/payroll/inheritance/capital gains/etc. the state loses most of its rational for its rampant invasions of our financial privacy. Since most businesses are already subjected to the invasion of their financial privacy (through state and local sales taxes), this is a huge net positive. Not only is this better for its own sake, but all of the monitoring that goes into current financial surveillance is costly. Getting all of those transactions costs out of our financial system will be a huge positive. # No More Benefits Tied to Employment This is what hit me this morning. The reason Americans get so many benefits through their employers is because they're tax exempted. Having our healthcare tied to our employer, and largely decided by them, is a huge distortion in the health care market and it radically reduces competition. Without preferential tax treatment, we would just be paid out that money in our salaries and make our own health care choices. As such, expect the current medical-industrial complex to fight this tax reform tooth and nail. The other element of this that I realized is that retirement accounts will lose the tax penalty, come withdrawal time (obviously depending on which type you have). That'll be a huge boon for many of us, and make up for the impending collapse of Social Security. # What Else? I haven't spent much more time thinking through other implications. What other effects will there be if the current tax regime is replaced with sales taxes and tariffs. originally posted at https://stacker.news/items/899802

@ 55f04590:2d385185

# Loops have been the overarching theme in the last two months of my work. You see, my book project is incredibly exciting, and whenever I have a large project like this—_a beast_—I have a tendency to become somewhat obsessive, (subconsciously) dedicating every waking hour to feeding it. I forced myself to step away from it for a bit, working on other projects while letting the book slumber in the back of my head. When I picked the project back up again, I could feel the different pieces it consists of had clicked into place. It always surprises me to see how taking time _away from a project_ can contribute to seeing things more clearly _on the project_. ## A new website for NoGood During this brief hiatus I found myself digging deeper into the indie & open web. I read articles by people who have been active proponents of an open web—as opposed to the walled gardens we’ve gotten accustomed to tracking us whichever way we surf—and I discovered the concept of tending to a ‘digital garden’. I saw a side of the web I was less exposed to before that aligned perfectly with my values. As a result, I overhauled the NoGood website. This new version of the website is simple, effective, and static: there is no tracking whatsoever, and it makes no requests to external resources. It only uses system fonts, serves optimised images, and because of that it’s blazing fast. I built it using _11ty_, and you can read more about it [in last month’s blogpost](https://nogood.studio/posts/update/new-website/). Within weeks, NoGood got featured on [DeadSimpleSites](http://deadsimplesites.com), a gallery full of similar websites, which is a welcome bit of recognition.  ## Rewarding dialogues The book’s sections ([_Work_, _Process_, _Context_, _Items_](https://nogood.studio/posts/book/announcement)) are set. The _Context_ section is meant to—well, do what it says on the tin: paint a picture of the context in which my own work was created and construct conversations between my work and that which came before it. To do so, I’ll carve out space for articles—published under the _Creative Commons_ or share-alike license—that inspired me along the way. I’ll illustrate each article myself, in black and white. I’ve asked a few people for their permission to publish their articles and have received positive responses from [Cory Doctorow](https://craphound.com/), Jack Dorsey, [Lyn Alden](https://www.lynalden.com/) and [DerGigi](https://dergigi.com/), for which I’m incredibly grateful. Just the ability to have dialogues with these people whose work I’ve admired is a rewarding outcome of me pursuing this project, feeding back into my desire to create a great publication. In order to do right by the _Creative Commons_ license, I’ll make the _Context_ section available on the NoGood website, too. I may even turn it into a printable zine—more on that later. ## Editing and designing the NoGood book I primarily work on the book from my studio space, which I share with two other creatives, [Timo](http://timokuilder.com) and [Daniël](http://daniel.pizza). Daniël designs and builds open-source software for [Ghost](http://ghost.org), writes, and publishes a literary magazine called [_TRANSCRIPT_](http://transcriptmag.store). We share similar values, he knows a thing or two about the open web, and it made perfect sense for us to work together. I’ve hired him to act as an editor for the book, and he now edits my writing (in fact, he edited this update, too!). We’ve had some dialogues about the articles I’m including as well as others I could add, too, and we’ll continue our conversations throughout the design process. Commissioning him to take on this work has been a relief. It freed up precious headspace, and I’ve started designing the first spreads of the book. Some sections already are very clear, while others still need time to crystallise. Fortunately, clarity comes as a result of chipping away at the work ahead, so I keep at it with renewed energy—updates will now follow more regularly.   ## Crowdfunding & production I have a complete picture of the production costs of the book and I’ve ironed out the logistics. I know which printer will be printing it, and my budget estimates were correct. The current number of [pre-orders](https://geyser.fund/project/nogoodartbook) (53) covers roughly 70% of the production costs, which means I can safely produce the NoGood book—it’s going to print this summer! 200 copies will roll off the press, and I’m really looking forward to it. Thank you for reading. More soon, Thomas. --- #### Previous updates [The NoGood art book announcement](https://stacker.news/items/736947) [Update 01 – Humble beginnings](https://stacker.news/items/744898) [Update 02 – Throwback](https://stacker.news/items/762791) #### Pre-order a book The NoGood art book is available [as a pre-order on Geyser](https://geyser.fund/project/nogoodartbook). originally posted at https://stacker.news/items/899798

@ 5d4b6c8d:8a1c1ee3

# It's *contest-palooza* at ~Stacker_Sports: - We have [cricket](https://stacker.news/items/898849/r/Undisciplined) - We'll likely have more cricket soon! - We have [USA vs the world](https://stacker.news/items/897858/r/Undisciplined) - We have [soccer](https://stacker.news/items/894320/r/Undisciplined) - We have [NBA](https://stacker.news/items/894412/r/Undisciplined) - Coming soon: March Madness, Fantasy Baseball, MLB Survivor Pools, NFL Mock Drafts, and AFL! # In actual sports news, - the NBA is hitting the home stretch. The contenders, pretenders, and tankers are sorting themselves out. - Steph's 56 - Giannis vs Jokic showdown - Brady tampering for Stafford? - NFL combine and other offseason activity - Ovi chasing the Great One - MLB started spring training games - New ball/strike review system # Degenerate Corner - [Predyx Super Bowl market](https://beta.predyx.com/market/super-bowl-winner-2026-1740263192) - I'm killing it on Ember. What's my secret? Plus, whatever stackers drop in the comments. originally posted at https://stacker.news/items/899748

@ 2e8970de:63345c7a

 the silence before the storm originally posted at https://stacker.news/items/899535

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/899482

@ 6389be64:ef439d32

GA, plebs. The latest episode of Bitcoin And is out, and, as always, the chicanery is running rampant. Let’s break down the biggest topics I covered, and if you want the full, unfiltered rant, make sure to listen to the episode linked below. ## House Democrats’ MEME Act: A Bad Joke? House Democrats are proposing a bill to ban presidential meme coins, clearly aimed at Trump’s and Melania’s ill-advised token launches. While grifters launching meme coins is bad, this bill is just as ridiculous. If this legislation moves forward, expect a retaliatory strike exposing how politicians like Pelosi and Warren mysteriously amassed their fortunes. Will it pass? Doubtful. But it’s another sign of the government’s obsession with regulating everything except itself. ## Senate Banking’s First Digital Asset Hearing: The Real Target Is You Cynthia Lummis chaired the first digital asset hearing, and—surprise!—it was all about control. The discussion centered on stablecoins, AML, and KYC regulations, with witnesses suggesting Orwellian measures like freezing stablecoin transactions unless pre-approved by authorities. What was barely mentioned? Bitcoin. They want full oversight of stablecoins, which is really about controlling financial freedom. Expect more nonsense targeting self-custody wallets under the guise of stopping “bad actors.” ## Bank of America and PayPal Want In on Stablecoins Bank of America’s CEO openly stated they’ll launch a stablecoin as soon as regulation allows. Meanwhile, PayPal’s CEO paid for a hat using Bitcoin—not their own stablecoin, Pi USD. Why wouldn’t he use his own product? Maybe he knows stablecoins aren’t what they’re hyped up to be. Either way, the legacy financial system is gearing up to flood the market with stablecoins, not because they love crypto, but because it’s a tool to extend U.S. dollar dominance. ## MetaPlanet Buys the Dip Japan’s MetaPlanet issued $13.4M in bonds to buy more Bitcoin, proving once again that institutions see the writing on the wall. Unlike U.S. regulators who obsess over stablecoins, some companies are actually stacking sats. ## UK Expands Crypto Seizure Powers Across the pond, the UK government is pushing legislation to make it easier to seize and destroy crypto linked to criminal activity. While they frame it as going after the bad guys, it’s another move toward centralized control and financial surveillance. ## Bitcoin Tools & Tech: Arc, SatoChip, and Nunchuk Some bullish Bitcoin developments: ARC v0.5 is making Bitcoin’s second layer more efficient, SatoChip now supports Taproot and Nostr, and Nunchuk launched a group wallet with chat, making multisig collaboration easier. ## The Bottom Line The state is coming for financial privacy and control, and stablecoins are their weapon of choice. Bitcoiners need to stay focused, keep their coins in self-custody, and build out parallel systems. Expect more regulatory attacks, but don’t let them distract you—just keep stacking and transacting in ways they can’t control. **🎧 Listen to the full episode here: [https://fountain.fm/episode/PYITCo18AJnsEkKLz2Ks](Fountain.fm)** **💰 Support the show by boosting sats on Podcasting 2.0!** and I will see you on the other side.

@ 5d4b6c8d:8a1c1ee3

I've really enjoyed these two months running ~econ. It crystallized that what I most enjoy is reading and commenting. Thankfully, our excellent contributors are giving me ample opportunities. # Metrics - Posts: 5th place - 264 - Comments: 6th place - 1653 - Stacking: 3rd place - 149.6k - Revenue: 6th place - 59.4k We're still over the breakeven point, but revenue was down from last month (still above the month before I took over, though). That means the new posting fee will be 81 sats, which is halfway back to the previous 108. # Contest Ideas Last month, I asked what people thought the best use of previously donated sats was and funding a contest seemed to get the best response. I'd like to try out a quarterly contest. The prize pool will be whatever sats have been earned, above the breakeven point, until the donated sats have all been paid out. I'm not sure if this will be a winner-takes-all thing or a top 3. I also don't want to completely defer to zaprank, so what I'll do is list the top 10 posts by zaprank and have people vote on the best post. Let me know what you think (including if this is an acceptable use of your donations, for those who made donations). originally posted at https://stacker.news/items/899082

@ 6260f29f:2ee2fcd4

<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;max-width:100%;"><iframe src="https://www.youtube.com/embed/div>?enablejsapi=1" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0;" allowfullscreen></iframe></div>

@ 6260f29f:2ee2fcd4

# titleeee test

@ 5d4b6c8d:8a1c1ee3

Here are today's picks using my proprietary betting strategy at [Freebitcoin](https://freebitco.in/?r=51325722). For details about what Risk Balanced Odds Arbitrage is and why it works see https://stacker.news/items/342765/r/Undisciplined. There were so many today, that I abandoned the markdown table. I recommend skipping the ones that are taking place within a week (the early bonus isn't great for those).  originally posted at https://stacker.news/items/898935

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/898543

@ 000002de:c05780a7

 These people have serious issues. [Original Sin by Jake Tapper and Alex Thompson](https://sites.prh.com/originalsin) > From two of America’s most respected journalists, an unflinching and explosive reckoning with one of the most fateful decisions in American political history: Joe Biden’s run for reelection despite evidence of his serious decline—amid desperate efforts to hide the extent of that deterioration originally posted at https://stacker.news/items/898271

@ b2d670de:907f9d4a

This is a list of nostr clients exposed as onion services. The list is currently actively maintained on [GitHub](https://github.com/0xtrr/onion-service-nostr-clients). Contributions are always appreciated! | Client name | Onion URL | Source code URL | Admin | Description | | --- | --- | --- | --- | --- | | Snort | http://agzj5a4be3kgp6yurijk4q7pm2yh4a5nphdg4zozk365yirf7ahuctyd.onion | https://git.v0l.io/Kieran/snort | [operator](nostr:nprofile1qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmg9umdvr) | N/A | | moStard | http://sifbugd5nwdq77plmidkug4y57zuqwqio3zlyreizrhejhp6bohfwkad.onion/ | https://github.com/rafael-xmr/nostrudel/tree/mostard | [operator](nostr:nprofile1qyv8wumn8ghj7un9d3shjtnddaehgctjvshx7un89uq36amnwvaz7tmzdaehgu3wvf5hgcm0d9h8g7r0ddhjucm0d5hsqgy8wvyzw6l9pn5m47n7tcm5un7t7h5ctx3pjx8nfwh06qq8g6max5zadtyx) | minimalist monero friendly nostrudel fork | | Nostrudel | http://oxtrnmb4wsb77rmk64q3jfr55fo33luwmsyaoovicyhzgrulleiojsad.onion/ | https://github.com/hzrd149/nostrudel | [operator](nostrnpub1ktt8phjnkfmfrsxrgqpztdjuxk3x6psf80xyray0l3c7pyrln49qhkyhz0) | Runs latest tagged docker image | | Nostrudel Next | http://oxtrnnumsflm7hmvb3xqphed2eqpbrt4seflgmdsjnpgc3ejd6iycuyd.onion/ | https://github.com/hzrd149/nostrudel | [operator](nostr:npub1ktt8phjnkfmfrsxrgqpztdjuxk3x6psf80xyray0l3c7pyrln49qhkyhz0) | Runs latest "next" tagged docker image | | Nsite | http://q457mvdt5smqj726m4lsqxxdyx7r3v7gufzt46zbkop6mkghpnr7z3qd.onion/ | https://github.com/hzrd149/nsite-ts | [operator](nostr:nprofile1qqszv6q4uryjzr06xfxxew34wwc5hmjfmfpqn229d72gfegsdn2q3fgpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsxx2q3a) | Runs nsite. You can read more about nsite [here](https://github.com/lez/nsite). | | Shopstr | http://6fkdn756yryd5wurkq7ifnexupnfwj6sotbtby2xhj5baythl4cyf2id.onion/ | https://github.com/shopstr-eng/shopstr-hidden-service | [operator](nostr:nprofile1qqsdxm5qs0a8kdk6aejxew9nlx074g7cnedrjeggws0sq03p4s9khmqpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcpzemhxue69uhksctkv4hzucmpd3mxztnyv4mz747p6g5) | Runs the latest `serverless` branch build of Shopstr. |

@ 2063cd79:57bd1320

Ich stimme mit Anonymous überein, dass es Probleme mit der tatsächlichen Verwendung von digitalem Bargeld auf kurze Sicht gibt. Aber es hängt in gewissem Maße davon ab, welches Problem man zu lösen versucht. Eine Sorge, die ich habe, ist, dass der Übergang zum elektronischen Zahlungsverkehr die Privatsphäre einschränken wird, da es einfacher wird, Transaktionen zu protokollieren und aufzuzeichnen. Es könnten Profile angelegt werden, in denen das Ausgabeverhalten eines jeden von uns verfolgt wird. Schon jetzt wird, wenn ich etwas telefonisch oder elektronisch mit meiner Visa-Karte bestelle, genau aufgezeichnet, wie viel ich ausgegeben habe und wo ich es ausgegeben habe. Im Laufe der Zeit könnten immer mehr Transaktionen auf diese Weise abgewickelt werden, und das Ergebnis könnte einen großen Verlust an Privatsphäre bedeuten. Die Bezahlung mit Bargeld ist zwar immer noch per Post möglich, aber dies ist unsicher und umständlich. Ich denke, dass die Bequemlichkeit von Kredit- und Debitkarten die Bedenken der meisten Menschen in Bezug auf Privatsphäre ausräumen wird und dass wir uns in einer Situation befinden werden, in der große Mengen an Informationen über das Privatleben aller Leute existieren. Hier könnte ich mir vorstellen, dass digitales Bargeld eine Rolle spielen könnte. Stellt euch ein Visa-ähnliches System vor, bei dem ich für die Bank nicht anonym bin. Stellt euch in diesem Modell vor, dass mir die Bank einen Kredit gewährt, ganz so wie bei einer Kreditkarte. Allerdings, anstatt mir nur eine Kontonummer zu geben, die ich am Telefon ablese oder in einer E-Mail verschicke, gibt sie mir das Recht, bei Bedarf digitales Bargeld zu verlangen. Ich habe immer etwas digitales Bargeld beiseite, dass ich für Transaktionen ausgeben kann, wie bereits in früheren Beiträgen beschrieben. Wenn das Geld knapp wird, schicke ich eine E-Mail an die Bank und erhalte mehr digitales Bargeld (dcash). Jeden Monat sende ich einen Check an die Bank, um mein Konto auszugleichen, genauso wie ich es mit meinen Kreditkarten mache. Meine Beziehung zur Bank sind meinen derzeitigen Beziehungen zu den Kreditkartenunternehmen sehr ähnlich: häufige Überweisungen und eine einmalige Rückzahlung jeden Monat per Check. Das hat mehrere Vorteile gegenüber dem System, auf das wir zusteuern. Es werden keine Aufzeichnungen darüber geführt, wofür ich mein Geld ausgebe. Die Bank weiß nur, wie viel ich jeden Monat abgehoben habe; es könnte sein, dass ich es zu diesem Zeitpunkt ausgegeben habe oder auch nicht. Bei einigen Transaktionen (z.B. Software) könnte ich für den Verkäufer anonym sein; bei anderen könnte der Verkäufer meine wirkliche Adresse kennen, aber dennoch ist keine zentrale Stelle in der Lage, alles zu verfolgen, was ich kaufe. (Es gibt auch einen Sicherheitsvorteil gegenüber dem lächerlichen aktuellen System, bei dem die Kenntnis über eine 16-stellige Nummer und eines Ablaufdatums es jedem ermöglicht, etwas auf meinen Namen zu bestellen!) Außerdem sehe ich nicht ein, warum dieses System nicht genauso legal sein sollte wie die derzeitigen Kreditkarten. Der einzige wirkliche Unterschied besteht darin, dass nicht nachverfolgt werden kann, wo die Nutzer ihr Geld ausgeben, und soweit ich weiß, war diese Möglichkeit nie ein wichtiger rechtlicher Aspekt von Kreditkarten. Sicherlich wird heute niemand zugeben, dass die Regierung ein Interesse daran hat, ein Umfeld zu schaffen, in dem jede finanzielle Transaktion nachverfolgt werden kann. Zugegeben, dies bietet keine vollständige Anonymität. Es ist immer noch möglich, ungefähr zu sehen, wie viel jede Person ausgibt (obwohl nichts eine Person daran hindert, viel mehr Bargeld abzuheben, als sie in einem bestimmten Monat ausgibt, außer vielleicht für Zinsausgaben; aber vielleicht kann sie das zusätzliche digitale Bargel (digicash) selbst verleihen und dafür Zinsen erhalten, um das auszugleichen). Und es orientiert sich an demselben Kunden/ Verkäufer-Modell, das Anonymous kritisierte. Ich behaupte aber, dass dieses Modell heute und in naher Zukunft die Mehrheit der elektronischen Transaktionen ausmachen wird. Es ist erwähnenswert, dass es nicht trivial ist, ein Anbieter zu werden, der Kreditkarten akzeptiert. Ich habe das mit einem Unternehmen, das ich vor ein paar Jahren betrieben habe, durchgemacht. Wir verkauften Software über den Versandhandel, was die Kreditkartenunternehmen sehr nervös machte. Es gibt zahlreiche Telefonbetrügereien, bei denen Kreditkartennummern über einige Monate hinweg gesammelt werden und dann große Beträge von diesen Karten abgebucht werden. Bis der Kunde seine monatliche Abrechnung erhält und sich beschwert, ist der Verkäufer bereits verschwunden. Um unser Kreditkartenterminal zu bekommen, wandten wir uns an ein Unternehmen, das Start-ups dabei „hilft“. Sie schienen selbst ein ziemlich zwielichtiges Unternehmen zu sein. Wir mussten unseren Antrag dahingehend fälschen, dass wir etwa 50% der Geräte auf Messen verkaufen würden, was offenbar als Verkauf über den Ladentisch zählte. Und wir mussten etwa 3.000 Dollar im Voraus zahlen, als Bestechung, wie es schien. Selbst dann hätten wir es wahrscheinlich nicht geschafft, wenn wir nicht ein Büro im Geschäftsviertel gehabt hätten. Im Rahmen des digitalen Bargeldsystems könnte dies ein geringeres Problem darstellen. Das Hauptproblem bei digitalem Bargeld sind doppelte Ausgaben, und wenn man bereit ist, eine Online-Überprüfung vorzunehmen (sinnvoll für jedes Unternehmen, das mehr als ein paar Stunden für die Lieferung der Ware benötigt), kann dies vollständig verhindert werden. Es gibt also keine Möglichkeit mehr, dass Händler Kreditkartennummern für spätere Betrügereien sammeln. (Allerdings gibt es immer noch Probleme mit der Nichtlieferung von Waren, so dass nicht alle Risiken beseitigt sind). Dadurch könnte das System schließlich eine größere Verbreitung finden als die derzeitigen Kreditkarten. Ich weiß nicht, ob dieses System zur Unterstützung von illegalen Aktivitäten, Steuerhinterziehung, Glücksspiel oder Ähnlichem verwendet werden könnte. Das ist nicht der Zweck dieses Vorschlags. Er bietet die Aussicht auf eine Verbesserung der Privatsphäre und der Sicherheit in einem Rahmen, der sogar rechtmäßig sein könnte, und das ist nicht verkehrt. ----- Englischer Artikel erschienen im Nakamoto Institute: [Digital Cash & Privacy](https://nakamotoinstitute.org/library/digital-cash-and-privacy/here)

@ e968e50b:db2a803a

"When we try to pick out anything by itself, we find it hitched to everything else in the Universe." -John Muir He was obviously actually talking about biomes and nature stuff, but doesn't this remind you of the Bitcoin rabbit hole. I came from a macroeconomic interest, but now have all sorts of computer programming, networking, investing, NGU, privacy rights, cryptographic, thermodynamic, and protocol interests that I never thought I'd care about. Is it that way for you? Did you get into Bitcoin through NGU or some other interest? Have you found new passions because of Bitcoin? Also, what's everybody here think about John Muir? He seems like he'd be a complicated figure for bitcoiners to evaluate, especially right now. How about his one-time camping buddy, Teddy Roosevelt? originally posted at https://stacker.news/items/897851

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/897528

@ 2e8970de:63345c7a

> A Detailed Look at the Economic Impacts of Trump's Wide Ranging New Tariffs on China, Mexico, Canada, Steel, Aluminum, and Much More     https://www.apricitas.io/p/trumps-2nd-trade-war-begins If you're interested in global trade I recommend looking at the article. It's a real deep dive into many perspectives of US trade esp. with China. What gets imported from China, many individual product categories, what happened in round 1 in 2018 and so so much more. And lots of charts! originally posted at https://stacker.news/items/896850

@ 460c25e6:ef85065c

If you don't know where your posts are, you might as well just stay in the centralized Twitter. You either take control of your relay lists, or they will control you. Amethyst offers several lists of relays for our users. We are going to go one by one to help clarify what they are and which options are best for each one. ## Public Home/Outbox Relays Home relays store all YOUR content: all your posts, likes, replies, lists, etc. It's your home. Amethyst will send your posts here first. Your followers will use these relays to get new posts from you. So, if you don't have anything there, **they will not receive your updates**. Home relays must allow queries from anyone, ideally without the need to authenticate. They can limit writes to paid users without affecting anyone's experience. This list should have a maximum of 3 relays. More than that will only make your followers waste their mobile data getting your posts. Keep it simple. Out of the 3 relays, I recommend: - 1 large public, international relay: nos.lol, nostr.mom, relay.damus.io, etc. - 1 personal relay to store a copy of all your content in a place no one can delete. Go to [relay.tools](https://relay.tools/) and never be censored again. - 1 really fast relay located in your country: paid options like http://nostr.wine are great Do not include relays that block users from seeing posts in this list. If you do, no one will see your posts. ## Public Inbox Relays This relay type receives all replies, comments, likes, and zaps to your posts. If you are not getting notifications or you don't see replies from your friends, it is likely because you don't have the right setup here. If you are getting too much spam in your replies, it's probably because your inbox relays are not protecting you enough. Paid relays can filter inbox spam out. Inbox relays must allow anyone to write into them. It's the opposite of the outbox relay. They can limit who can download the posts to their paid subscribers without affecting anyone's experience. This list should have a maximum of 3 relays as well. Again, keep it small. More than that will just make you spend more of your data plan downloading the same notifications from all these different servers. Out of the 3 relays, I recommend: - 1 large public, international relay: nos.lol, nostr.mom, relay.damus.io, etc. - 1 personal relay to store a copy of your notifications, invites, cashu tokens and zaps. - 1 really fast relay located in your country: go to [nostr.watch](https://nostr.watch/relays/find) and find relays in your country Terrible options include: - nostr.wine should not be here. - filter.nostr.wine should not be here. - inbox.nostr.wine should not be here. ## DM Inbox Relays These are the relays used to receive DMs and private content. Others will use these relays to send DMs to you. **If you don't have it setup, you will miss DMs**. DM Inbox relays should accept any message from anyone, but only allow you to download them. Generally speaking, you only need 3 for reliability. One of them should be a personal relay to make sure you have a copy of all your messages. The others can be open if you want push notifications or closed if you want full privacy. Good options are: - inbox.nostr.wine and auth.nostr1.com: anyone can send messages and only you can download. Not even our push notification server has access to them to notify you. - a personal relay to make sure no one can censor you. Advanced settings on personal relays can also store your DMs privately. Talk to your relay operator for more details. - a public relay if you want DM notifications from our servers. Make sure to add at least one public relay if you want to see DM notifications. ## Private Home Relays Private Relays are for things no one should see, like your drafts, lists, app settings, bookmarks etc. Ideally, these relays are either local or require authentication before posting AND downloading each user\'s content. There are no dedicated relays for this category yet, so I would use a local relay like Citrine on Android and a personal relay on relay.tools. Keep in mind that if you choose a local relay only, a client on the desktop might not be able to see the drafts from clients on mobile and vice versa. ## Search relays: This is the list of relays to use on Amethyst's search and user tagging with @. **Tagging and searching will not work if there is nothing here.**. This option requires NIP-50 compliance from each relay. Hit the Default button to use all available options on existence today: - nostr.wine - relay.nostr.band - relay.noswhere.com ## Local Relays: This is your local storage. Everything will load faster if it comes from this relay. You should install Citrine on Android and write ws://localhost:4869 in this option. ## General Relays: This section contains the default relays used to download content from your follows. Notice how you can activate and deactivate the Home, Messages (old-style DMs), Chat (public chats), and Global options in each. Keep 5-6 large relays on this list and activate them for as many categories (Home, Messages (old-style DMs), Chat, and Global) as possible. Amethyst will provide additional recommendations to this list from your follows with information on which of your follows might need the additional relay in your list. Add them if you feel like you are missing their posts or if it is just taking too long to load them. ## My setup Here's what I use: 1. Go to [relay.tools](https://relay.tools/) and create a relay for yourself. 2. Go to [nostr.wine](https://nostr.wine/) and pay for their subscription. 3. Go to [inbox.nostr.wine](https://inbox.nostr.wine/) and pay for their subscription. 4. Go to [nostr.watch](https://nostr.watch/relays/find) and find a good relay in your country. 5. Download Citrine to your phone. Then, on your relay lists, put: Public Home/Outbox Relays: - nostr.wine - nos.lol or an in-country relay. - <your.relay>.nostr1.com Public Inbox Relays - nos.lol or an in-country relay - <your.relay>.nostr1.com DM Inbox Relays - inbox.nostr.wine - <your.relay>.nostr1.com Private Home Relays - ws://localhost:4869 (Citrine) - <your.relay>.nostr1.com (if you want) Search Relays - nostr.wine - relay.nostr.band - relay.noswhere.com Local Relays - ws://localhost:4869 (Citrine) General Relays - nos.lol - relay.damus.io - relay.primal.net - nostr.mom And a few of the recommended relays from Amethyst. ## Final Considerations Remember, relays can see what your Nostr client is requesting and downloading at all times. They can track what you see and see what you like. They can sell that information to the highest bidder, they can delete your content or content that a sponsor asked them to delete (like a negative review for instance) and they can censor you in any way they see fit. Before using any random free relay out there, make sure you trust its operator and you know its terms of service and privacy policies.

@ 57d1a264:69f1fee1

 Galoy released a new product called Lana, a platform for bitcoin loans. The team will provide an introduction and then we'll dive into the design. To get you up to speed, check out the website, slide deck and podcast interview: - https://www.galoy.io/lana-bitcoin-loans-platform - https://docs.google.com/presentation/d/1IQocefpCN5_wKX91EWtLa19IpMS_Ye8goNLAgGQbfdU/edit#slide=id.g31d536107ae_0_0 - https://stephanlivera.com/episode/634/ If you get a chance, please take a peek before the call. That makes the design reviews more useful because we need to spend less time going over the basics. On `Thu Feb 27th · 15:00 – 16:00 CET` Join from https://meet.jit.si/bitcoindesign Check your timezone https://everytimezone.com/s/998e22fc Track https://github.com/BitcoinDesign/Meta/issues/758 originally posted at https://stacker.news/items/896570

@ 57d1a264:69f1fee1

I've been pondering how LSPs (lightning service providers) might pan out over time and how that might affect fees, and I am wondering what everyone else is thinking. Some people will always prefer to manage their own channels, and for some specific use cases, that might be preferable. But I am thinking about the broad userbase that does not want to do that. We will need a massive LSP infrastructure to onboard people and to enable insane amounts of payments. LSPs will need to efficiently open and adjust channels for users, using their own liquidity or sourcing liquidity from other providers, using just-in-time channels, batching and/or splicing to reduce costs and wait times. Across all this, along with facilitating payments, they need to make their business model work and offer different options for users to pay for their services. Users might be able to: 1. Pay-as-you-go (pay X for Y more liquidity for Z amount of time) 2. Pay X per month for Y inbound liquidity 3. Pay X per month for unlimited liquidity 4. Nothing for liquidity, but higher transaction fees A wallet might also automatically choose an appropriate LSP based on what is the best and most appropriate deal at the time. Let's look at user scenarios: - If someone sends and receives the same amount every month, they will never need more liquidity. They just draw down the same channel and fill it up again. So they would only pay the LSP for them assigning that fixed amount of liquidity to them. Maybe options 1 and 2 are good for them. - If someone receives more than they send (they save a certain amount every month), they will need more and more inbound liquidity over time. They might choose option 2. - An online store that receives a ton and can't really estimate how much, might go for option 3. - For option 4, it depends if the higher transaction fees are fixed or percentage-based. It's a bit like choosing a data plan for your phone (or for internet at home). You can get a prepaid card, a regular plan with certain limits, or go unlimited. And there are separate plans for small and large businesses, etc. And there are massive amounts of complex infrastructure behind these service providers to make it all work. So when someone starts using a lightning wallet, maybe they have to first pick an LSP and a plan before being able to receive. Or maybe they get a first channel for free and pay higher fees, and are then prompted to choose a plan. Maybe they need to wait an hour until the LSP has enough channel opens for a batch/splice, to reduce costs. A complex market at work. Is that how things might pan out? Am I completely off? Is it worth mocking up different scenarios? ``` #bitcoin #LN #BTC #Lightning #LSP #service #zaps #sats #wallet ``` originally posted at https://stacker.news/items/896520

@ 57d1a264:69f1fee1

­  @Voltage team will be building a simple implementation of a Lightning gated API service using a Voltage LND Node and the L402 protocol. 📅 Thursday, February 27th 4:00 PM CDT 📷 Live on Voltage Discord, on X, or on YouTube. - discord.gg/EN93fDfQ - https://x.com/voltage_cloud/status/1892938201980919985 - https://www.youtube.com/@voltage_cloud originally posted at https://stacker.news/items/896373

@ 6389be64:ef439d32

Biochar in the soil attracts microbes who take up permanent residence in the "coral reef" the biochar provides. Those microbes then attract mycorrhizal fungi to the reef. The mycorrhizal fungi are also attached to plant roots connecting diverse populations to each other, allowing transportation of molecular resources (water, cations, anions etc). The char surface area attracts positively charged ions like K+ Ca2+ Mg2+ NH4+ Na+ H+ Al3+ Fe2+ Fe3+ Mn2+ Cu2+ Zn2+ Many of these are transferred to plant roots by mycorrhizal fungi in exchange for photosynthetic products (sugars). Mycorrhizal fungi are connected to both plant roots and biochar. Char adsorbs these cations so, it stands to reason that under periods of minimal need by plants for these cations (stress, low or no sunlight etc.), mycorrhizal fungi could deposit the cations to the char surfaces. The char would be acting as a "bank" for the cations and the deposition would be of low energy cost. Once the plant starts exuding photosynthetic products again, signaling a need for these cations, the fungi can start "stripping" the cations off of the char surface for immediate exchange of the cations for the sugars. This would be a high energy transaction because the fungi would have to expend energy to strip the cations off of the char surface, in effect, an "interest rate". The char might act as a reservoir of cations that were mined by the fungi while the sugar flow from the roots was active. It's a bank. originally posted at https://stacker.news/items/896340

@ 04c915da:3dfbecc9

Here’s a revised timeline of macro-level events from *The Mandibles: A Family, 2029–2047* by Lionel Shriver, reimagined in a world where Bitcoin is adopted as a widely accepted form of money, altering the original narrative’s assumptions about currency collapse and economic control. In Shriver’s original story, the failure of Bitcoin is assumed amid the dominance of the bancor and the dollar’s collapse. Here, Bitcoin’s success reshapes the economic and societal trajectory, decentralizing power and challenging state-driven outcomes. ### Part One: 2029–2032 - **2029 (Early Year)**\ The United States faces economic strain as the dollar weakens against global shifts. However, Bitcoin, having gained traction emerges as a viable alternative. Unlike the original timeline, the bancor—a supranational currency backed by a coalition of nations—struggles to gain footing as Bitcoin’s decentralized adoption grows among individuals and businesses worldwide, undermining both the dollar and the bancor. - **2029 (Mid-Year: The Great Renunciation)**\ Treasury bonds lose value, and the government bans Bitcoin, labeling it a threat to sovereignty (mirroring the original bancor ban). However, a Bitcoin ban proves unenforceable—its decentralized nature thwarts confiscation efforts, unlike gold in the original story. Hyperinflation hits the dollar as the U.S. prints money, but Bitcoin’s fixed supply shields adopters from currency devaluation, creating a dual-economy split: dollar users suffer, while Bitcoin users thrive. - **2029 (Late Year)**\ Dollar-based inflation soars, emptying stores of goods priced in fiat currency. Meanwhile, Bitcoin transactions flourish in underground and online markets, stabilizing trade for those plugged into the bitcoin ecosystem. Traditional supply chains falter, but peer-to-peer Bitcoin networks enable local and international exchange, reducing scarcity for early adopters. The government’s gold confiscation fails to bolster the dollar, as Bitcoin’s rise renders gold less relevant. - **2030–2031**\ Crime spikes in dollar-dependent urban areas, but Bitcoin-friendly regions see less chaos, as digital wallets and smart contracts facilitate secure trade. The U.S. government doubles down on surveillance to crack down on bitcoin use. A cultural divide deepens: centralized authority weakens in Bitcoin-adopting communities, while dollar zones descend into lawlessness. - **2032**\ By this point, Bitcoin is de facto legal tender in parts of the U.S. and globally, especially in tech-savvy or libertarian-leaning regions. The federal government’s grip slips as tax collection in dollars plummets—Bitcoin’s traceability is low, and citizens evade fiat-based levies. Rural and urban Bitcoin hubs emerge, while the dollar economy remains fractured. ### Time Jump: 2032–2047 - Over 15 years, Bitcoin solidifies as a global reserve currency, eroding centralized control. The U.S. government adapts, grudgingly integrating bitcoin into policy, though regional autonomy grows as Bitcoin empowers local economies. ### Part Two: 2047 - **2047 (Early Year)**\ The U.S. is a hybrid state: Bitcoin is legal tender alongside a diminished dollar. Taxes are lower, collected in BTC, reducing federal overreach. Bitcoin’s adoption has decentralized power nationwide. The bancor has faded, unable to compete with Bitcoin’s grassroots momentum. - **2047 (Mid-Year)**\ Travel and trade flow freely in Bitcoin zones, with no restrictive checkpoints. The dollar economy lingers in poorer areas, marked by decay, but Bitcoin’s dominance lifts overall prosperity, as its deflationary nature incentivizes saving and investment over consumption. Global supply chains rebound, powered by bitcoin enabled efficiency. - **2047 (Late Year)**\ The U.S. is a patchwork of semi-autonomous zones, united by Bitcoin’s universal acceptance rather than federal control. Resource scarcity persists due to past disruptions, but economic stability is higher than in Shriver’s original dystopia—Bitcoin’s success prevents the authoritarian slide, fostering a freer, if imperfect, society. ### Key Differences - **Currency Dynamics**: Bitcoin’s triumph prevents the bancor’s dominance and mitigates hyperinflation’s worst effects, offering a lifeline outside state control. - **Government Power**: Centralized authority weakens as Bitcoin evades bans and taxation, shifting power to individuals and communities. - **Societal Outcome**: Instead of a surveillance state, 2047 sees a decentralized, bitcoin driven world—less oppressive, though still stratified between Bitcoin haves and have-nots. This reimagining assumes Bitcoin overcomes Shriver’s implied skepticism to become a robust, adopted currency by 2029, fundamentally altering the novel’s bleak trajectory.

@ d34e832d:383f78d0

https://blossom.primal.net/af0bc86b52c7f91c26633ed0cba4f151bb74e5a5702b892f7f1efaa9e4640018.mp4 [npub16d8gxt2z4k9e8sdpc0yyqzf5gp0np09ls4lnn630qzxzvwpl0rgq5h4rzv] ### **What is Reticulum?** Reticulum is a cryptographic networking stack designed for resilient, decentralized, and censorship-resistant communication. Unlike the traditional internet, Reticulum enables fully independent digital communications over various physical mediums, such as radio, LoRa, serial links, and even TCP/IP. The key advantages of Reticulum include: - **Decentralization** – No reliance on centralized infrastructure. - **Encryption & Privacy** – End-to-end encryption built-in. - **Resilience** – Operates over unreliable and low-bandwidth links. - **Interoperability** – Works over WiFi, LoRa, Bluetooth, and more. - **Ease of Use** – Can run on minimal hardware, including Raspberry Pi and embedded devices. Reticulum is ideal for off-grid, censorship-resistant communications, emergency preparedness, and secure messaging. --- ## **1. Getting Started with Reticulum** To quickly get started with Reticulum, follow the official guide: [Reticulum: Getting Started Fast](https://markqvist.github.io/Reticulum/manual/gettingstartedfast.html) ### **Step 1: Install Reticulum** #### **On Linux (Debian/Ubuntu-based systems)** ```sh sudo apt update && sudo apt upgrade -y sudo apt install -y python3-pip pip3 install rns ``` #### **On Raspberry Pi or ARM-based Systems** ```sh pip3 install rns ``` #### **On Windows** Using Windows Subsystem for Linux (WSL) or Python: ```sh pip install rns ``` #### **On macOS** ```sh pip3 install rns ``` --- ## **2. Configuring Reticulum** Once installed, Reticulum needs a configuration file. The default location is: ```sh ~/.config/reticulum/config.toml ``` To generate the default configuration: ```sh rnsd ``` This creates a configuration file with default settings. --- ## **3. Using Reticulum** ### **Starting the Reticulum Daemon** To run the Reticulum daemon (`rnsd`), use: ```sh rnsd ``` This starts the network stack, allowing applications to communicate over Reticulum. ### **Testing Your Reticulum Node** Run the diagnostic tool to ensure your node is functioning: ```sh rnstatus ``` This shows the status of all connected interfaces and peers. --- ## **4. Adding Interfaces** ### **LoRa Interface (for Off-Grid Communications)** Reticulum supports long-range LoRa radios like the **RAK Wireless** and **Meshtastic devices**. To add a LoRa interface, edit `config.toml` and add: ```toml [[interfaces]] type = "LoRa" name = "My_LoRa_Interface" frequency = 868.0 bandwidth = 125 spreading_factor = 9 ``` Restart Reticulum to apply the changes. ### **Serial (For Direct Device-to-Device Links)** For communication over serial links (e.g., between two Raspberry Pis): ```toml [[interfaces]] type = "Serial" port = "/dev/ttyUSB0" baudrate = 115200 ``` ### **TCP/IP (For Internet-Based Nodes)** If you want to bridge your Reticulum node over an existing IP network: ```toml [[interfaces]] type = "TCP" listen = true bind = "0.0.0.0" port = 4242 ``` --- ## **5. Applications Using Reticulum** ### **LXMF (LoRa Mesh Messaging Framework)** LXMF is a delay-tolerant, fully decentralized messaging system that operates over Reticulum. It allows encrypted, store-and-forward messaging without requiring an always-online server. To install: ```sh pip3 install lxmf ``` To start the LXMF node: ```sh lxmfd ``` ### **Nomad Network (Decentralized Chat & File Sharing)** Nomad is a Reticulum-based chat and file-sharing platform, ideal for **off-grid** communication. To install: ```sh pip3 install nomad-network ``` To run: ```sh nomad ``` ### **Mesh Networking with Meshtastic & Reticulum** Reticulum can work alongside **Meshtastic** for true decentralized long-range communication. To set up a Meshtastic bridge: ```toml [[interfaces]] type = "LoRa" port = "/dev/ttyUSB0" baudrate = 115200 ``` --- ## **6. Security & Privacy Features** - **Automatic End-to-End Encryption** – Every message is encrypted by default. - **No Centralized Logging** – Communication leaves no metadata traces. - **Self-Healing Routing** – Designed to work in unstable or hostile environments. --- ## **7. Practical Use Cases** - **Off-Grid Communication** – Works in remote areas without cellular service. - **Censorship Resistance** – Cannot be blocked by ISPs or governments. - **Emergency Networks** – Enables resilient communication during disasters. - **Private P2P Networks** – Create a secure, encrypted communication layer. --- ## **8. Further Exploration & Documentation** - **Reticulum Official Manual**: [https://markqvist.github.io/Reticulum/manual/](https://markqvist.github.io/Reticulum/manual/) - **Reticulum GitHub Repository**: [https://github.com/markqvist/Reticulum](https://github.com/markqvist/Reticulum) - **Nomad Network**: [https://github.com/markqvist/NomadNet](https://github.com/markqvist/NomadNet) - **Meshtastic + Reticulum**: [https://meshtastic.org](https://meshtastic.org) --- ## **Connections (Links to Other Notes)** - **Mesh Networking for Decentralized Communication** - **LoRa and Off-Grid Bitcoin Transactions** - **Censorship-Resistant Communication Using Nostr & Reticulum** ## **Tags** #Reticulum #DecentralizedComms #MeshNetworking #CensorshipResistance #LoRa ## **Donations via** - **Bitcoin Lightning**: lightninglayerhash@getalby.com

@ da0b9bc3:4e30a4a9

Hello Stackers! It's Monday so we're back doing "Meta Music Mondays" 😉. From before the territory existed there was just one post a week in a ~meta take over. Now each month we have a different theme and bring music from that theme. Welcome to Femmes Fatales 3!!! I absolutely loved doing this last year so I'm bringing it back for round 3! It's Femmes Fatales, where we celebrate women in ~Music. So let's have those ladies of the lung, the sirens of sound, our Femmes Fatales! Stackers, here's Avril Lavigne. https://youtu.be/dGR65RWwzg8?si=T5onrZ0T_zREhd-n Talk Music. Share Tracks. Zap Sats. originally posted at https://stacker.news/items/895855

@ 2e8970de:63345c7a

> The highest-earning 10% of Americans have increased their spending far beyond inflation. Everyone else hasn’t.  > The top 10% of earners—households making about $250,000 a year or more—are splurging on everything from vacations to designer handbags, buoyed by big gains in stocks, real estate and other assets. Those consumers now account for 49.7% of all spending, a record in data going back to 1989, according to an analysis by Moody’s Analytics. Three decades ago, they accounted for about 36%. All this means that economic growth is unusually reliant on rich Americans continuing to shell out. Mark Zandi, chief economist at Moody’s Analytics, estimated that spending by the top 10% alone accounted for almost one-third of gross domestic product. https://www.wsj.com/economy/consumers/us-economy-strength-rich-spending-2c34a571?mod=hp_lead_pos7 originally posted at https://stacker.news/items/895834

@ 2e8970de:63345c7a

> Air pollution tends to get worse before it gets better, but how can we accelerate this transition?   > I’m lucky to have grown up with far cleaner air than my parents or grandparents did. In fact, air quality in the United Kingdom is now better than it was for several generations [...] For younger generations in many other countries, this is not the case. Those living in cities like Delhi, Dhaka, or Accra breathe in some of the most polluted air in their country’s history. https://ourworldindata.org/cleanest-air-lessons originally posted at https://stacker.news/items/895817

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/895451

@ 57d1a264:69f1fee1

As your involvement in open source design increases, you’ll face challenges that go beyond basic UI work. From creating scalable design systems to mentoring new contributors, these advanced areas require strategic thinking, collaboration, and leadership. This chapter dives into these complexities, helping you handle real-world situations while continuing to grow as a designer. - Championing Design Initiatives - Creating and Maintaining Design Systems - Handling Complex Design Challenges - Conducting In-Depth User Research - Balancing Open Source Work with Other Commitments - Navigating Project Dynamics -0 Mentoring New Designers Read more: https://opendesign.guide/10-advanced-topics ``` #design #nostrdesign #bitcoindesign #ln #grownostr #asknostr #zap #btc #bitcoin #nostr #cashu ``` originally posted at https://stacker.news/items/895377

@ c11cf5f8:4928464d

Let's hear some of your latest #Bitcoin purchases, feel free to include links to the #shops or #merchants you bought from too. Any good #deal we should know about? If you missed our last thread, [here](https://stacker.news/items/887305/r/AG) are some of the items stackers recently spent and #zap #sats on. originally posted at https://stacker.news/items/895134

@ 3ffac3a6:2d656657

## Renoters: Proposal for Anonymous Event Relaying in Nostr *This document is a proposal and not an official NIP.* This Document proposes "Renoters," a mechanism for anonymous event relaying in Nostr, inspired by the Mixminion remailer design. Renoters aim to enhance privacy by obscuring the origin of events, making it difficult to trace the author of a message. ### **Motivation** While Nostr offers a decentralized platform, current relay mechanisms can potentially reveal the source of events. Renoters address this by introducing an onion-routing-like system where events are encrypted and relayed through a series of nodes, making it harder to link the event to its originator. This enhances privacy for users who wish to communicate anonymously or protect their identity. In some totalitarian regimes, the use of Tor and VPNs is criminalized, making online anonymity dangerous. Even in some democratic countries, merely downloading Tor can mark individuals as suspects. This underscores the need for a decentralized and anonymous communication system that operates independently of commonly surveilled privacy tools. ### **Proposed Solution** Renoters operate on the principle of "gift-wrapping" events, using asymmetric encryption. A user wishing to send an event anonymously performs the following steps: 1. **Event Creation:** The user creates the Nostr event they wish to publish. 2. **Renoter Path Selection:** The user selects a path of Renoters through which the event will be relayed. This path can be pre-configured or dynamically chosen. 3. **Gift Wrapping (Encryption and Signing):** The user encrypts and signs the event for each Renoter in the path, working in reverse order: - A *new* random Nostr private key (`sk_wrapper`) is generated. - The event (or the previously wrapped event) is encrypted using the *next* Renoter's Npub (`npub_next`) using Nostr's standard encryption mechanism (e.g., using shared secrets derived from the private key and the recipient's public key). - A *new* Nostr event is created. This "wrapper" event's content contains the ciphertext. The wrapper event is signed using the newly generated private key `sk_wrapper`. The wrapper event also includes the next hop's `npub_next` (or the final destination if it's the last renoter) in cleartext, to allow for routing. 4. **Publication:** The user publishes the *first* gift-wrapped event (the one encrypted for the last Renoter in the path). This event is sent to a regular Nostr relay, which then forwards it to the first Renoter in the path. 5. **Renoter Relaying:** Each Renoter in the path receives the gift-wrapped event, verifies the signature using the `sk_wrapper`'s corresponding public key, decrypts it using its own private key, and forwards the decrypted event (now wrapped for the *next* Renoter) to the next Renoter in the path. This process continues until the event reaches the final Renoter. 6. **Final Delivery:** The final Renoter decrypts the event and publishes it to the Nostr network. ### **Example** Let's say Alice wants to send an event anonymously through Renoters R1, R2, and R3. 1. Alice creates her event. 2. She generates a random private key `sk3` and encrypts the event with R3's public key `npub_r3`. 3. She creates a wrapper event containing the ciphertext and `npub_r3`, signed with `sk3`. 4. She generates a random private key `sk2` and encrypts the previous wrapper event with R2's public key `npub_r2`. 5. She creates a wrapper event containing this ciphertext and `npub_r2`, signed with `sk2`. 6. She generates a random private key `sk1` and encrypts the previous wrapper event with R1's public key `npub_r1`. 7. She creates a final wrapper event containing this ciphertext and `npub_r1`, signed with `sk1`. 8. Alice publishes this final wrapper event. R1 decrypts with its private key, verifies the signature with the public key corresponding to `sk1`, and forwards to R2. R2 decrypts, verifies the signature with the public key corresponding to `sk2`, and forwards to R3. R3 decrypts, verifies the signature with the public key corresponding to `sk3`, and publishes the original event. ### **Renoter Incentives (using Cashu)** To incentivize Renoters to participate in the network, this NIP proposes integrating Cashu tokens as a payment mechanism. - **Token Inclusion:** When a user creates the initial gift-wrapped event (the one sent to the first Renoter), they include a Cashu token *within* the event content. This token is itself encrypted and wrapped along with the original message, so only the receiving Renoter can access it. - **Renoter Redemption:** Upon receiving a gift-wrapped event, the Renoter decrypts it. If the event contains a Cashu token, the Renoter can decrypt the token and redeem it. - **Renoter Behavior:** Paid Renoters would be configured *not* to relay events that do *not* contain a valid Cashu token. This ensures that Renoters are compensated for their service. Free Renoters could still exist, but paid Renoters would likely offer faster or more reliable service. - **Token Value and Tiers:** Different Cashu token denominations could represent different levels of service (e.g., faster relaying, higher priority). This could create a tiered system where users can pay for better anonymity or speed. - **Token Generation:** Users would need a way to acquire Cashu tokens. This could involve purchasing them from a Cashu mint or earning them through other means. ### **Security Threats and Mitigations** - **Anonymity Against Correlation Attacks:** Even when using Tor, traffic patterns can still be analyzed to infer the origin of events. To mitigate this risk, Renoters can introduce: - Random delays in event relaying. - Dummy packets to complicate statistical analysis by malicious observers. - **Replay Attacks:** To mitigate replay attacks, each Renoter must store, for a reasonable period, the IDs of received events and the decrypted events that were forwarded. This ensures that duplicate messages are not processed again. - **Sybil Attacks:** Sybil attacks can be mitigated by requiring payments via Cashu tokens for relaying events, increasing the cost of launching such attacks. By ensuring that each relay operation has a monetary cost, attackers are discouraged from creating large numbers of fake identities to manipulate the network. - **Traffic Analysis:** Traffic analysis can be mitigated by using Tor for Renoters. Routing events through the Tor network adds an additional layer of anonymity, making it more difficult to track message origins or infer sender-recipient relationships. While Renoters enhance privacy, sophisticated traffic analysis might still be a threat. ### **Operational Considerations** - **Renoter Reliability:** The reliability of the Renoter network is crucial. - **Latency:** Relaying through multiple Renoters will introduce latency. - **Key Management:** While each layer uses a new key, the initial key generation and path selection process need to be secure. This NIP provides a robust framework for anonymous event relaying in Nostr, leveraging encryption and Cashu-based incentives to enhance privacy and usability. ### **References** - **Untraceable Electronic Mail, Return Addresses, and Digital Pseudonyms**: David L. Chaum (https://dl.acm.org/doi/10.1145/358549.358563) - **Mixminion Design**: Mixminion: Design of a Type III Anonymous Remailer (https://www.mixminion.net/minion-design.pdf) - **Nostr Protocol**: Official Nostr Documentation (https://github.com/nostr-protocol/nostr) - **Cashu Token System**: Cashu: Ecash for Bitcoin Lightning (https://cashu.space/) - **Tor Project**: The Tor Project - Anonymity Online (https://www.torproject.org/) - **Onion Routing**: The Second-Generation Onion Router (https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf) #Privacy #Nostr #Anonymity #Crypto #CensorshipResistance #OnlinePrivacy #Decentralization #Encryption #Security #ThreatMitigation #Micropayments #CryptoEconomy #NextSteps #Development

@ 2e8970de:63345c7a

 > 1 in 5 women with a BA are willing to marry a man without one  > But crucially, the men without a BA married to women with a BA are those with better earnings. So women "marry down" educationally, not so much economically  > Why aren't women without a BA marrying men without one? Short answer: economic viability. In areas where men from lower-income backgrounds are doing better. women are more likely to be married  https://aibm.org/research/will-college-educated-women-find-someone-to-marry/ originally posted at https://stacker.news/items/895044

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/894609

@ e3ba5e1a:5e433365

My wife and I have six children, making our house a household of eight people. Looking just at the eight of us, how many relationships exist? Well, as a first stab, we could look at how many connections exist between two unique individuals in this family. The mathematical term for this is “8 choose 2”, and the answer is 8\*7/2, or 28\. Even that doesn’t really capture the answer though, because relationships aren’t just between two people. For example, when my wife and two oldest children are the only ones still awake after the younger kids go to bed, we’ll put on my mature TV shows that they’ll appreciate and watch together. It’s our own little subgroup within the group. Based on that, we could have groups of 2, 3, 4, all the way up to 8, the group of all of us. If you do the math, this comes up to 247 different subgroups of 2 or more people. That’s a lot of groups for just 8 people. As a father, this means I’ll never be able to fully understand every set of connections within my family. I may have a good understanding of my own relationship with each child. I also am closely aware of the relationship between our two youngest children, since they’re twins. And I could probably list 20 or so other noteworthy relationships. But I’ll never understand all of them. For example, months ago I bought a game on Steam for my 3rd and 4th kids. I know they like to play games together, so it was a relationship that I thought I understood well. A few days ago I found out that my oldest had joined them in playing one of these games (Brotato). I’d made the purchase, given it to the kids, and it sparked new relationship and interaction structures without my involvement. There’s no problem with the fact that I can’t track every interaction in my house. That’s healthy\! The kids are able to discover ways of interacting beyond what I can teach them, learn everything from schoolwork to video games from each other, and overall become more healthy and well-adjusted adults (I hope). And here’s the important part: the growth of the number of connections is *massive* as the number of participants increases. If we add in another participant, we have 502 groupings. At 10 total participants, it jumps to over 1,000. By the time we get to 100, we’re well into the trillions. A mathematical and software term for this is *combinatoric complexity*, the massive increase in an output value based on a small increase in the input. The analysis I’m providing could be termed as part of graph theory (for connections of 2, looking at people as *vertices* and connections as *edges*) or set theory (unique subsets, allowing for larger group sizes). But regardless, the point is: the increase in complexity is huge as more people join. Now consider the global economy. It’s over 8 billion people. There are so many people that the number of groupings is absurd to talk about. Nonetheless, massive numbers of these groupings naturally occur. There are family units, friend circles, individual connections, companies, project teams, sports teams, schools, classes, and millions more. These groups of people form new ways of interacting, express vastly different desires for goods and services, and are capable of producing wide varieties of goods and services themselves. When you allow this system to run free, beauty emerges. Each node in the graph can manage its own connections. Each *person* is free to make his or her own decisions about association, what to spend time on, what to spend money on, and so on. Each person does so on their own judgement and world view. Some of these people may make “dumb” decisions. They may “waste” their time and money on useless things. Except: who made that value judgement? Clearly not them, they decided it was worth it. No central planner has the right to override their will. My point in all this is: as yet another of many reasons in the list of “why people should be free,” we have one more data point: pure math. Central planning will never scale. Central planning will never appreciate the individuality and desires of each person. Only by giving people the freedom to explore their connections to others, discover what they can produce and consume, explore their options, and ultimately make their own decisions, can we have any chance of creating a world where everyone can succeed.

@ 5d4b6c8d:8a1c1ee3

Well, my Wemby pick from last month just went up in flames. It's only getting more difficult to figure out who's getting that last spot, now. I want to take KAT, but that would give me the same exact picks as @gnilma with fewer possible points. I'll take his teammate, Jalen Brunson, and hope NY voters pick the wrong Knick. Remember, older correct predictions are worth more than recent ones, so don't wait too long to get off your bad predictions. Also, players must play in at least 65 games to be eligible for awards. Luka, AD, and Wemby are not going to be eligible, so you should swap them out if you still have them. Here's the current state of the competition with your max possible score next to your nym: | Contestant | MVP | Champ | All NBA | | | | | |--------------|------|---------|----------|-|-|-|-| | @Undisciplined 47| SGA| OKC | Jokic | Giannis |Tatum | SGA | Brunson | | @grayruby 55| Giannis| Cavs| Jokic | Giannis | Luka | Mitchell| Brunson| | @gnilma 55| SGA| OKC| Jokic | KAT | Giannis | Tatum| SGA | | @BitcoinAbhi 70 | Luka| Denver| Jokic | Giannis | Luka | Ant| SGA| | @Bell_curve 63| SGA| Celtics| Jokic | Giannis | Luka | Ant| SGA| | @0xbitcoiner 70 | Jokic| Pacers| Jokic | Giannis | Luka | Ant| Brunson| | @Coinsreporter 49| Giannis| Pacers| Jokic | Giannis | Luka | Ant| Brunson| | @TheMorningStar 49| Luka| Celtics| Jokic | Giannis | Luka | Ant| SGA| | @onthedeklein 49| Luka| T-Wolves| Jokic | Giannis | Luka | Wemby| SGA| | @Carresan 49| Luka| Mavs| Jokic | Giannis | Luka | Wemby| SGA| | @BTC_Bellzer 34| SGA| Celtics| Jokic| Giannis | Tatum| SGA| Brunson | | @realBitcoinDog 49| Luka| Lakers| Jokic | Giannis | Luka | Ant| SGA| | @SimpleStacker 42| SGA| Celtics| Jokic| Tatum| Luka | Brunson| SGA| | @BlokchainB 42| SGA| Knicks| AD| Giannis | Ant| Brunson| SGA| **Prize** At least 6k (I'll keep adding zaps to the pot). If you want to join this contest, just leave your predictions for MVP, Champion, and All-NBA 1st team in the comments. See the [June post](https://stacker.news/items/585231/r/Undisciplined) for more details. originally posted at https://stacker.news/items/894412

@ 6260f29f:2ee2fcd4

# A title before again ```js import React, { useEffect, useState } from 'react'; import dynamic from 'next/dynamic'; import { Dialog } from 'primereact/dialog'; import { track } from '@vercel/analytics'; import { LightningAddress } from '@getalby/lightning-tools'; import { useToast } from '@/hooks/useToast'; import { useSession } from 'next-auth/react'; import { ProgressSpinner } from 'primereact/progressspinner'; import axios from 'axios'; import GenericButton from '@/components/buttons/GenericButton'; import useWindowWidth from '@/hooks/useWindowWidth'; import { useRouter } from 'next/router'; const Payment = dynamic( () => import('@getalby/bitcoin-connect-react').then((mod) => mod.Payment), { ssr: false } ); const ResourcePaymentButton = ({ lnAddress, amount, onSuccess, onError, resourceId }) => { const [invoice, setInvoice] = useState(null); const [isLoading, setIsLoading] = useState(false); const { showToast } = useToast(); const { data: session, status } = useSession(); const [dialogVisible, setDialogVisible] = useState(false); const router = useRouter(); const windowWidth = useWindowWidth(); const isMobile = windowWidth < 768; useEffect(() => { let intervalId; if (invoice) { intervalId = setInterval(async () => { const paid = await invoice.verifyPayment(); if (paid && invoice.preimage) { clearInterval(intervalId); // handle success handlePaymentSuccess({ paid, preimage: invoice.preimage }); } }, 2000); } else { console.error('no invoice'); } return () => { if (intervalId) { clearInterval(intervalId); } }; }, [invoice]); const fetchInvoice = async () => { setIsLoading(true); try { const ln = new LightningAddress(lnAddress); await ln.fetch(); const invoice = await ln.requestInvoice({ satoshi: amount }); setInvoice(invoice); setDialogVisible(true); } catch (error) { console.error('Error fetching invoice:', error); showToast('error', 'Invoice Error', 'Failed to fetch the invoice.'); if (onError) onError(error); } setIsLoading(false); }; const handlePaymentSuccess = async (response) => { try { const purchaseData = { userId: session.user.id, resourceId: resourceId, amountPaid: parseInt(amount, 10) }; const result = await axios.post('/api/purchase/resource', purchaseData); if (result.status === 200) { track('Resource Payment', { resourceId: resourceId, userId: session?.user?.id }); if (onSuccess) onSuccess(response); } else { throw new Error('Failed to update user purchases'); } } catch (error) { console.error('Error updating user purchases:', error); showToast('error', 'Purchase Update Failed', 'Payment was successful, but failed to update user purchases.'); if (onError) onError(error); } setDialogVisible(false); }; return ( <> <GenericButton label={`${amount} sats`} icon="pi pi-wallet" onClick={() => { if (status === 'unauthenticated') { console.log('unauthenticated'); router.push('/auth/signin'); } else { fetchInvoice(); } }} disabled={isLoading} severity='primary' rounded className={`text-[#f8f8ff] text-sm ${isLoading ? 'hidden' : ''}`} /> {isLoading && ( <div className='w-full h-full flex items-center justify-center'> <ProgressSpinner style={{ width: '30px', height: '30px' }} strokeWidth="8" animationDuration=".5s" /> </div> )} <Dialog visible={dialogVisible} onHide={() => setDialogVisible(false)} header="Make Payment" style={{ width: isMobile ? '90vw' : '50vw' }} > {invoice ? ( <Payment invoice={invoice.paymentRequest} onPaid={handlePaymentSuccess} paymentMethods='all' title={`Pay ${amount} sats`} /> ) : ( <p>Loading payment details...</p> )} </Dialog> </> ); }; export default ResourcePaymentButton; ```

@ b8851a06:9b120ba1

The digital guillotine has fallen. The Bybit hack wasn’t just a theft—it was a surgical strike exposing the fatal flaw of “crypto” that isn’t Bitcoin. This wasn’t a bug. It was a feature of a system designed to fail. Here’s how North Korea’s Lazarus Group stole $1.5B in ETH, why “decentralized finance” is a joke, and how Bitcoin remains the only exit from this circus. ## I. The Heist: How Centralized “Crypto” Betrayed Its Users ### A. The Multisig Mousetrap (Or: Why You’re Still Using a Bank) Bybit’s Ethereum cold wallet used multisig, requiring multiple approvals for transactions. Sounds secure, right? Wrong. • The Con: Hackers didn’t pick the lock; they tricked the keyholders using a UI masking attack. The wallet interface showed “SEND TO BYBIT”, but the smart contract was whispering “SEND TO PYONGYANG.” • Bitcoin Parallel: Bitcoin’s multisig is enforced on hardware, not a website UI. No browser spoofing, no phishing emails—just raw cryptography. Ethereum’s multisig is a vault with a touchscreen PIN pad. Bitcoin’s is a mechanical safe with a key only you hold. Guess which one got robbed? ### B. Smart Contracts: Dumb as a Bag of Hammers The thieves didn’t “hack” Ethereum—they exploited its smart contract complexity. • Bybit’s security depended on a Safe.global contract. Lazarus simply tricked Bybit into approving a malicious upgrade. • Imagine a vending machine that’s programmed to take your money but never give you a soda. That’s Ethereum’s “trustless” tech. Why Bitcoin Wins: Bitcoin doesn’t do “smart contracts” in the Ethereum sense. Its scripting language is deliberately limited—less code, fewer attack vectors. Ethereum is a Lego tower; Bitcoin is a granite slab. One topples, one doesn’t. ## II. The Laundering: Crypto’s Dirty Little Secret ### A. Mixers, Bridges, and the Art of Spycraft Once the ETH was stolen, Lazarus laundered it at lightspeed: 1. Mixers (eXch) – Obfuscating transaction trails. 2. Bridges (Chainflip) – Swapping ETH for Bitcoin because that’s the only exit that matters. Bitcoin Reality Check: Bitcoin’s privacy tools (like CoinJoin) are self-custodial—no third-party mixers. You keep control, not some “decentralized” website waiting to be hacked. Ethereum’s “bridges” are burning rope ladders. Bitcoin’s privacy? An underground tunnel only you control. ### B. The $1.5B Lie: “Decentralized” Exchanges Are a Myth Bybit’s “cold wallet” was on Safe.global—a so-called “decentralized” custodian. Translation? A website with extra steps. • When Safe.global got breached, the private keys were stolen instantly. • “Decentralized” means nothing if your funds depend on one website, one server, one weak link. Bitcoin’s Answer: Self-custody. Hardware wallets. Cold storage. No trusted third parties. Using Safe.global is like hiding your life savings in a gym locker labeled “STEAL ME.” ## III. The Culprits: State-Sponsored Hackers & Crypto’s Original Sin ### A. Lazarus Group: Crypto’s Robin Hood (For Dictators) North Korea’s hackers didn’t break cryptography—they broke people. • Phishing emails disguised as job offers. • Bribes & social engineering targeting insiders. • DeFi governance manipulation (because Proof-of-Stake is just shareholder voting in disguise). Bitcoin’s Shield: No CEO to bribe. No “upgrade buttons” to exploit. No governance tokens to manipulate. Code is law—and Bitcoin’s law is written in stone. Ethereum’s security model is “trust us.” Bitcoin’s is “verify.” ### B. The $3B Elephant: Altcoins Fund Dictators Since 2017, Lazarus has stolen $3B+ in crypto, funding North Korea’s missile program. Why? Because Ethereum, Solana, and XRP are built on Proof-of-Stake (PoS)—which centralizes power in the hands of a few rich validators. • Bitcoin’s Proof-of-Work: Miners secure the network through energy-backed cryptography. • Altcoins’ Proof-of-Stake: Security is dictated by who owns the most tokens. Proof-of-Stake secures oligarchs. Proof-of-Work secures money. That’s why Lazarus can drain altcoin treasuries but hasn’t touched Bitcoin’s network. ## IV. Bybit’s Survival: A Centralized Circus ### A. The Bailout: Banks 2.0 Bybit took bridge loans from “undisclosed partners” (read: Wall Street vultures). • Just like a traditional bank, Bybit printed liquidity out of thin air to stay solvent. • If that sounds familiar, it’s because crypto exchanges are just banks in hoodies. Bitcoin Contrast: No loans. No bailouts. No “trust.” Just 21 million coins, mathematically secured. Bybit’s solvency is a confidence trick. Bitcoin’s solvency is math. ### B. The Great Withdrawal Panic Within hours, 350,000+ users scrambled to withdraw funds. A digital bank run—except this isn’t a bank. It’s an exchange that pretended to be decentralized. Bitcoin fixes this: your wallet isn’t an IOU. It’s actual money. Bybit = a TikTok influencer promising riches. Bitcoin = the gold in your basement. ## V. The Fallout: Regulators vs Reality ### A. ETH’s 8% Crash vs Bitcoin’s Unshakable Base Ethereum tanked because it’s a tech stock, not money. Bitcoin? Dropped 2% and stabilized. No CEO, no headquarters, no attack surface. ### B. The Regulatory Trap Now the bureaucrats come in demanding: 1. Wallet audits (they don’t understand public ledgers). 2. Mixer bans (criminalizing privacy). 3. KYC everything (turning crypto into a surveillance state). Bitcoin’s Rebellion: You can’t audit what’s already transparent. You can’t ban what’s unstoppable. ## VI. Conclusion: Burn the Altcoins, Stack the Sats The Bybit hack isn’t a crypto problem. It’s an altcoin problem. Ethereum’s smart contracts, DeFi bridges, and “decentralized” wallets are Swiss cheese for hackers. Bitcoin? A titanium vault. The Only Lessons That Matter: ✅ Multisig isn’t enough unless it’s Bitcoin’s hardware-enforced version. ✅ Complexity kills—every altcoin “innovation” is a security risk waiting to happen. Lazarus Group won this round because “crypto” ignored Bitcoin’s design. The solution isn’t better regulations—it’s better money. Burn the tokens. Unplug the servers. Bitcoin is the exit. Take your money off exchanges. Be sovereign.

@ b4403b24:83542d4e

Chainflip says it has limited some frontend services but can’t fully block transactions as a decentralized protocol. Over $1.1M in ETH has already been converted.  **Well done to them - not for the heist but for the decision to convert weak money to sound money** 😜 originally posted at https://stacker.news/items/894141

@ 2e8970de:63345c7a

 -Blue: Neuroticism -Green: Extraversion -Red: Openness to experience -Orange: Agreeableness -Purple: Conscientiousness [sourcs(https://www.stevestewartwilliams.com/p/are-there-age-and-sex-differences)] originally posted at https://stacker.news/items/893992

@ ac6f9572:8a6853dd

# The old world crumbles. The sovereign rises.  Join #Bitshala at #BitPlebs Summit in Goa — a gathering of builders, creators, educators, and hodlers forging #India’s #Bitcoin future. Open forums. Un-conference style talks. By @bitshala & @plebstogether RSVP now: https://lu.ma/cd55r5d4 X: https://x.com/bitshala_org/status/1893252853709365684?s=09 originally posted at https://stacker.news/items/893899

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/893831

@ 2e8970de:63345c7a

 > Rising home prices and high mortgage rates have pushed the median age of homebuyers to a record-high 56 years old in 2024, up from 45 in 2021. In 1981, the median age of homebuyers was 31 years old, [source](https://www.apolloacademy.com/median-age-of-homebuyers-56/) originally posted at https://stacker.news/items/893804

@ 4857600b:30b502f4

In a revealing development that exposes the hypocrisy of government surveillance, multiple federal agencies including the CIA and FBI have filed lawsuits to keep Samourai Wallet's client list sealed during and after trial proceedings. This move strongly suggests that government agencies themselves were utilizing Samourai's privacy-focused services while simultaneously condemning similar privacy tools when used by ordinary citizens. The situation bears striking parallels to other cases where government agencies have hidden behind "national security" claims, such as the Jeffrey Epstein case, highlighting a troubling double standard: while average citizens are expected to surrender their financial privacy through extensive reporting requirements and regulations, government agencies claim exemption from these same transparency standards they enforce on others. This case exemplifies the fundamental conflict between individual liberty and state power, where government agencies appear to be using the very privacy tools they prosecute others for using. The irony is particularly stark given that money laundering for intelligence agencies is considered legal in our system, while private citizens seeking financial privacy face severe legal consequences - a clear demonstration of how the state creates different rules for itself versus the people it claims to serve. Citations: [1] https://www.bugle.news/cia-fbi-dnc-rnc-all-sue-to-redact-samourais-client-list-from-trial/

@ 6e0ea5d6:0327f353

"Malcolm Forbes recounts that a lady, wearing a faded cotton dress, and her husband, dressed in an old handmade suit, stepped off a train in Boston, USA, and timidly made their way to the office of the president of Harvard University. They had come from Palo Alto, California, and had not scheduled an appointment. The secretary, at a glance, thought that those two, looking like country bumpkins, had no business at Harvard. — We want to speak with the president — the man said in a low voice. — He will be busy all day — the secretary replied curtly. — We will wait. The secretary ignored them for hours, hoping the couple would finally give up and leave. But they stayed there, and the secretary, somewhat frustrated, decided to bother the president, although she hated doing that. — If you speak with them for just a few minutes, maybe they will decide to go away — she said. The president sighed in irritation but agreed. Someone of his importance did not have time to meet people like that, but he hated faded dresses and tattered suits in his office. With a stern face, he went to the couple. — We had a son who studied at Harvard for a year — the woman said. — He loved Harvard and was very happy here, but a year ago he died in an accident, and we would like to erect a monument in his honor somewhere on campus. — My lady — said the president rudely —, we cannot erect a statue for every person who studied at Harvard and died; if we did, this place would look like a cemetery. — Oh, no — the lady quickly replied. — We do not want to erect a statue. We would like to donate a building to Harvard. The president looked at the woman's faded dress and her husband's old suit and exclaimed: — A building! Do you have even the faintest idea of how much a building costs? We have more than seven and a half million dollars' worth of buildings here at Harvard. The lady was silent for a moment, then said to her husband: — If that’s all it costs to found a university, why don’t we have our own? The husband agreed. The couple, Leland Stanford, stood up and left, leaving the president confused. Traveling back to Palo Alto, California, they established there Stanford University, the second-largest in the world, in honor of their son, a former Harvard student." Text extracted from: "Mileumlivros - Stories that Teach Values." Thank you for reading, my friend! If this message helped you in any way, consider leaving your glass “🥃” as a token of appreciation. A toast to our family!

@ 266815e0:6cd408a5

I've been working on the applesauce libraries for a while now but I think this release is the first one I would consider to be stable enough to use A lot of the core concepts and classes are in place and stable enough where they wont change too much next release If you want to skip straight to the documentation you can find at [hzrd149.github.io/applesauce](https://hzrd149.github.io/applesauce/) or the typescript docs at [hzrd149.github.io/applesauce/typedoc](https://hzrd149.github.io/applesauce/typedoc) ## Whats new ### Accounts The `applesauce-accounts` package is an extension of the `applesauce-signers` package and provides classes for building a multi-account system for clients Its primary features are - Serialize and deserialize accounts so they can be saved in local storage or IndexededDB - Account manager for multiple accounts and switching between them - Account metadata for things like labels, app settings, etc - Support for NIP-46 Nostr connect accounts see [documentation](https://hzrd149.github.io/applesauce/accounts/manager.html) for more examples ### Nostr connect signer The `NostrConnectSigner` class from the `applesauce-signers` package is now in a stable state and has a few new features - Ability to create `nostrconnect://` URIs and waiting for the remote signer to connect - SDK agnostic way of subscribing and publishing to relays For a simple example, here is how to create a signer from a `bunker://` URI ```js const signer = await NostrConnectSigner.fromBunkerURI( "bunker://266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5?relay=wss://relay.nsec.app&secret=d9aa70", { permissions: NostrConnectSigner.buildSigningPermissions([0, 1, 3, 10002]), async onSubOpen(filters, relays, onEvent) { // manually open REQ }, async onSubClose() { // close previouse REQ }, async onPublishEvent(event, relays) { // Pubilsh an event to relays }, }, ); ``` see [documentation](https://hzrd149.github.io/applesauce/signers/nostr-connect.html) for more examples and other signers ### Event Factory The `EventFactory` class is probably what I'm most proud of. its a standalone class that can be used to create various types of events from templates ([blueprints](https://hzrd149.github.io/applesauce/typedoc/modules/applesauce_factory.Blueprints.html)) and is really simple to use For example: ```js import { EventFactory } from "applesauce-factory"; import { NoteBlueprint } from "applesauce-factory/blueprints"; const factory = new EventFactory({ // optionally pass a NIP-07 signer in to use for encryption / decryption signer: window.nostr }); // Create a kind 1 note with a hashtag let draft = await factory.create(NoteBlueprint, "hello world #grownostr"); // Sign the note so it can be published let signed = await window.nostr.signEvent(draft); ``` Its included in the `applesauce-factory` package and can be used with any other nostr SDKs or vanilla javascript It also can be used to modify existing replaceable events ```js let draft = await factory.modifyTags( // kind 10002 event mailboxes, // add outbox relays addOutboxRelay("wss://relay.io/"), addOutboxRelay("wss://nostr.wine/"), // remove inbox relay removeInboxRelay("wss://personal.old-relay.com/") ); ``` see [documentation](https://hzrd149.github.io/applesauce/overview/factory.html) for more examples ### Loaders The `applesauce-loaders` package exports a bunch of loader classes that can be used to load everything from replaceable events (profiles) to timelines and NIP-05 identities They use [rx-nostr](https://penpenpng.github.io/rx-nostr/) under the hood to subscribe to relays, so for the time being they will not work with other nostr SDKs I don't expect many other developers or apps to use them since in my experience every nostr client requires a slightly different way or loading events *They are stable enough to start using but they are not fully tested and they might change slightly in the future* The following is a short list of the loaders and what they can be used for - `ReplaceableLoader` loads any replaceable events (0, 3, 1xxxx, 3xxxx) - `SingleEventLoader` loads single events based on ids - `TimelineLoader` loads a timeline of events from multiple relays based on filters - `TagValueLoader` loads events based on a tag name (like "e") and a value, can be used to load replies, zaps, reactions, etc - `DnsIdentityLoader` loads NIP-05 identities and supports caching - `UserSetsLoader` loads all lists events for users see [documentation](https://hzrd149.github.io/applesauce/overview/loaders.html) for more examples ### Real tests For all new features and a lot of existing ones I'm trying to write tests to ensure I don't leave unexpected bugs for later I'm not going to pretend its 100% tests coverage or that it will ever get close to that point, but these tests cover some of the core classes and help me prove that my code is doing what it says its supposed to do At the moment there are about 230 tests covering 45 files. not much but its a start  ## Apps built using applesauce If you want to see some examples of applesauce being used in a nostr client I've been testing a lot of this code in production on the apps I've built in the last few months - [noStrudel](https://github.com/hzrd149/nostrudel) The main app everything is being built for and tested in - [nsite-manager](https://github.com/hzrd149/nsite-manager) Still a work-in-progress but supports multiple accounts thanks to the `applesauce-accounts` package - [blossomservers.com](https://github.com/hzrd149/blossomservers) A simple (and incomplete) nostr client for listing and reviewing public blossom servers - [libretranslate-dvm](https://github.com/hzrd149/libretranslate-dvm) A libretranslate DVM for nostr:npub1mkvkflncllnvp3adq57klw3wge6k9llqa4r60g42ysp4yyultx6sykjgnu - [cherry-tree](https://github.com/hzrd149/cherry-tree) A chunked blob uploader / downloader. only uses applesauce for boilerplate - [nsite-homepage](https://github.com/hzrd149/nsite-homepage) A simple landing page for [nsite.lol](https://nsite.lol) Thanks to nostr:npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c for teaching me more about rxjs and consequentially making me re-write a lot of the core observables to be faster

@ 0c503f08:4aed05c7

originally posted at https://stacker.news/items/893208

@ d34e832d:383f78d0

[npub16d8gxt2z4k9e8sdpc0yyqzf5gp0np09ls4lnn630qzxzvwpl0rgq5h4rzv] Data Storage via Blobs in a Decentralized Manner Blobs (Binary Large Objects) offer a flexible method of storing large chunks of data, and in the context of decentralized systems, they allow for secure, distributed storage solutions. In a decentralized world, where privacy and autonomy are key, managing data in a distributed manner ensures data isn't controlled or censored by a single entity. Here are three key systems enabling decentralized blob storage: 1. **Blossom Server** [Blossom Server](https://github.com/hzrd149/blossom-server?tab=readme-ov-file) provides a decentralized platform for storing and sharing large blobs of data. Blossom Server allows users to host their own data and retrieve it from a decentralized network, ensuring that data is not stored in centralized servers. This platform is open-source, offering flexibility and security through peer-to-peer data storage. 2. **Perkeep** [Perkeep](https://perkeep.org/) (formerly known as Camlistore) is a decentralized data storage system that allows for storing blobs of data in a distributed manner. It focuses on the long-term storage of large data sets, such as personal collections of photos, videos, and documents. By using Perkeep, users can ensure that their data remains private and is not controlled by any central authority. The system uses a unique identifier to access data, promoting both privacy and integrity. 3. **IPFS (InterPlanetary File System)** [IPFS](https://ipfs.io/) is another popular decentralized file storage system that uses the concept of blobs to store and share data. IPFS allows users to store and access data in a decentralized manner by using a peer-to-peer network. Each piece of data is given a unique hash, ensuring that it is verifiable and tamper-proof. By leveraging IPFS, users can store everything from simple files to large applications, all without relying on centralized servers. By using these decentralized data storage solutions, individuals and organizations can safeguard their information, increase privacy, and contribute to a more resilient and distributed internet infrastructure. **Higher-Level Goals for Blob Storage** Blob storage via Blossom ,Perkeep and IPFS has goals to become a decentralized, self-sufficient protocol for data storage, management, and sharing. While some of these features are already being implemented, they represent a broader vision for the future of decentralized personal data management. 1. **Filesystem Backups** Allows for easy, incremental backups. Using the **`pk-put`** tool, users can back up files and directories quickly and efficiently. Incremental backups, which save only the changes made since the last backup, are essentially free, making Perkeep an efficient choice for backup solutions. This initial use case has already been implemented, providing seamless and secure backups for personal data. 2. **Efficient Remote Filesystem** The goal is to create a highly efficient, aggressively caching remote filesystem using Perkeep. A **read-only** version of this filesystem is already trivial to implement, while **read-write** functionality remains an area of active development. Every modification in the filesystem would be snapshotted implicitly, providing version control as a default. This would enable users to interact with their data in a remote environment while ensuring that every change is tracked and recoverable. 3. **Decentralized Sharing System** Perkeep is working towards enabling users to share data in a decentralized manner. The system will allow individuals to share anything with anyone or everyone, with privacy being the default setting. This decentralized sharing is already starting to work, and users can now share data with others while retaining control over who sees their information. 4. **Blog / Photo Hosting / Document Management CMS** Perkeep aims to replace traditional blog platforms, photo hosting services, and document management software. By running a **personal blog**, **photo gallery**, and **document management system (CMS)** on Perkeep, users will have full control over their content. Permissions will be configurable, allowing for personal or public sharing. The author intends to use Perkeep for his own blog, gallery, and document management needs, further demonstrating its versatility. 5. **Decentralized Social Networking** While still a lofty goal, decentralized social networking is a persistent aim for Perkeep. By implementing features like **comments** and **tagging**, users could attach metadata to images and content. Through claims, users could sign data and verify identities, promoting trust in social interactions. This would allow for decentralized social networking where users control their own data and interactions. 6. **Import/Export Adapters for Hosted Web Services** Perkeep intends to bridge the gap between decentralized storage and traditional hosted web services. This feature would allow users to **mirror data** between hosted services and their private Perkeep storage. Whether content is created in Perkeep or hosted services, the goal is to ensure that data is always backed up privately, ensuring users' data is theirs forever. ### Combined Goals for Blossom and IPFS Both Blossom and IPFS share common goals of decentralizing data storage, enhancing privacy, and providing users with greater control over their data. Together, these technologies enable: - **Self-Sovereign Data Management**: Empowering users to store and manage their data without relying on centralized platforms. - **Resilient and Redundant Storage**: Offering decentralized and redundant data storage that ensures availability and security. - **Private and Permissioned Sharing**: Enabling secure, private data sharing where the user controls who has access to their content. By focusing on these goals, both Blossom and IPFS are contributing to a future where individuals control their own data, collaborate more efficiently in decentralized networks and P4P protocols, and ensure the privacy and security of their digital assets. These technologies in conjunction with nostr lead one to discover user agency and autonomy, where you can actually own and interface with your own data allowing for value creation and content creation strategies. Donations via - lightninglayerhash@getalby.com

@ d34e832d:383f78d0

Decentralized Publishing: ChainScribe: How to Approach Studying NIPs (Nostr Improvement Proposals) [npub16d8gxt2z4k9e8sdpc0yyqzf5gp0np09ls4lnn630qzxzvwpl0rgq5h4rzv] How to Approach Studying NIPs (Nostr Improvement Proposals) NIPs (Nostr Improvement Proposals) provide a framework for suggesting and discussing improvements to the Nostr protocol, a decentralized network for open communication. Studying NIPs is crucial for understanding the evolution of Nostr and its underlying principles. To effectively approach this, it's essential to follow a systematic, structured process. 1. **Familiarize with the Nostr Protocol**: Before diving into the specifics of each NIP, gain a solid understanding of the core Nostr protocol. This includes its goals, architecture, and key components like pubkeys, events, and relays. 2. **Explore the NIP Catalog**: Visit [nostr-nips.com](https://nostr-nips.com/) to browse through the available NIPs. Focus on the most recent proposals and those that align with your interests or areas of expertise. 3. **Review the Proposal Structure**: Each NIP follows a standard structure, typically including a description of the problem, proposed solution, and rationale. Learn to read and evaluate these elements critically, paying attention to how each proposal aligns with Nostr’s decentralized ethos. 4. **Follow Active Discussions**: Many NIPs are actively discussed within the community. Follow relevant channels, such as GitHub issues or dedicated discussion forums, to understand community feedback and potential revisions. 5. **Understand Dependencies**: Some NIPs are designed to work in tandem with others or require other technological advancements. Recognize these relationships to better understand the broader implications of any proposal. 6. **Hands-On Testing**: If possible, test NIPs in a development environment to see how they function in practice. Experimenting with proposals will help deepen your understanding and expose potential challenges or flaws. 7. **Contribute to Proposals**: If you have insights or suggestions, contribute to the discussion or propose your own improvements. NIPs thrive on community participation, and your input can help shape the future of Nostr. Donations via - lightninglayerhash@getalby.com

@ 5d4b6c8d:8a1c1ee3

Howdy stackers! Since football season is finally over, we're going to dive into NFL offseason topics. - There was a huge spike in the salary cap, but lot's of well known players are still going to be cap casualties - Which free agents are we hoping our teams re-sign and which others should they go after? The NBA All-Star Game was a huge dud and Wemby has a scary medical condition - Can the All Star game be fixed? - What are Wemby's prospects for the future? - Also, Luka's fat. Were the Mavs right to trade him? The NHL did manage to fix their All Star event. Is this a winning formula or a one-off? Degenerate Corner: How are our bets doing? And, whatever else the stackers want us to talk about. originally posted at https://stacker.news/items/893005

@ 00033a93:774465e5

New key management on [mostro](https://mostro.network/) with great privacy improvement. Read more here [mostro keys management](https://mostro.network/blog/keys-management/). Mobile app with big steps ahead, not full order flow working but we are near, read more [here](https://primal.net/e/note1we820zfy0w42st57vw3ztjk9p9ld4l6gl9ha47slehvxsekrzcxqgz2fd0) Mostro will be completely open source, built on top of Nostr, competitive ( anyone could run an instance ), nokyc, no mail or phone number or personal data. Get ready! originally posted at https://stacker.news/items/892994

@ da0b9bc3:4e30a4a9

It's Finally here Stackers! It's Friday! We're about to kick off our weekends with some feel good tracks. Let's get the party started. Bring me those Feel Good tracks. Let's get it! Party Rock! https://youtu.be/KQ6zr6kCPj8?si=jyncDuzGh73_PbuP Talk Music. Share Tracks. Zap Sats. originally posted at https://stacker.news/items/892973

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/892722

@ 4857600b:30b502f4

A new talking point of the left is that it’s no big deal, just simple recording errors for the 20 million people aged 100-360. 🤷‍♀️ And not many of them are collecting benefits anyway. 👌 First of all, the investigation & analysis are in the early stages. How can they possibly know how deep the fraud goes, especially when their leaders are doing everything they can to obstruct any real examination? Second, sure, no worries about only a small number collecting benefits. That’s the ONLY thing social security numbers are used for. 🙄

@ 0c503f08:4aed05c7

1. 2024–2029: Shaking the Foundations of the Familiar The late 2020s are poised to be an era of disruption. Picture generative AI moving beyond quirky chatbots and into life-altering domains like healthcare. Machines will detect diseases before symptoms arise, yet courtrooms will brim with lawsuits over their failures. Schools will fracture into stark contrasts—students with access to AI tutors thrive, while others cling to outdated textbooks in underfunded systems. Meanwhile, the renewable energy boom will surpass 40% of global electricity, yet fossil fuel industries will fight tooth and nail to remain relevant. The planet’s turbulence will become undeniable: superstorms batter coastlines, and relentless droughts displace millions, stretching humanitarian efforts thin. Global tensions won’t just simmer—they’ll boil. The U.S. and China will spar over technological dominance, particularly the semiconductor-rich bastion of Taiwan. Africa, with its treasure trove of lithium and cobalt, becomes a battleground for a new wave of exploitation. Amid this upheaval, humanity will glance skyward: NASA’s Artemis III places boots near the Moon’s south pole, igniting a modern-day space race as China counters with a robotic lunar base. 2. 2030–2034: Progress at a Price The early 2030s will feel like a contradiction wrapped in progress. Electric vehicles dominate the roads, but the cobalt mines fueling this transition will leave humanitarian and ecological scars. Global agreements on AI and autonomous drones will emerge, but enforcement will be weak, leading to selective compliance and rising mistrust. In healthcare, CRISPR therapies will eliminate diseases like sickle-cell anemia, offering breakthroughs for those who can afford them. Yet, alongside these marvels, biodiversity quietly collapses: pollinators disappear, destabilizing food systems, even as tech startups commercialize extinct species as novelties. Societal inequalities will take center stage. Aging nations like Japan will lean on empathetic robotic caregivers, while Africa’s youth flood urban slums and migration routes, reshaping the global labor landscape. Quantum computing will spark both innovation and chaos, cracking encryption protocols and triggering a global scramble for security in the digital age. The decade’s sobering reality? Solutions often create new dilemmas, leaving humanity juggling its own ingenuity. 3. 2040–2044: Living on the Edge of Irreversible Change By the 2040s, tipping points will dominate global narratives. Arctic summers without ice will exacerbate warming, while oceans lose their coral, and with them, a quarter of marine biodiversity. Cities respond unevenly: while Dubai thrives with water-harvesting skyscrapers, Miami succumbs to the sea, becoming a decayed relic of resilience undone. Technological advancements blur the line between human and machine. Neural implants will enable the paralyzed to walk but also tether corporate workers to AI copilots monitoring their productivity—and even thoughts. Petrostates crumble under the weight of falling oil demand as solar energy becomes the new global standard. Simultaneously, life-extending drugs create a schism. The wealthy buy decades of youth while intergenerational protests erupt over perceived inequalities. The question dominating the 2040s isn’t whether humans will remake Earth’s systems—it’s who will get to decide how those changes unfold. 4. 2070–2074: A World Divided by Vision The 2070s will be a study in contrasts: miraculous advancements side-by-side with dystopian realities. Coastal cities will either drown or adapt; some will fund floating havens while others abandon their shores entirely. Fusion energy might deliver limitless power, but control over its distribution will spark fears of new monopolies. Mars will no longer be a dream—it’ll be a fragile reality, home to scientists mining ice and debating their sovereignty from Earth. CRISPR’s third generation will bring designer children, creating genetic castes of “Enhanced” and “Natural” humans. Society will grapple with ethical questions that pit faith, science, and social cohesion against one another. Meanwhile, humanity will turn to lab-engineered ecosystems to fix what was broken: bacteria devouring plastic and forests surviving extreme heat. But for every advance, new risks emerge. Rogue biohackers and ecological mishaps will remind us how thin the line between salvation and catastrophe can be. 5. 2124: The Precipice of Destiny A hundred years from now, humanity will either bask in the fruits of collective wisdom—or stumble under the weight of collective greed. In one future, fusion energy ends scarcity, lab-grown organs erase disease, and AI enriches every aspect of life. In another, oligarchs preside over a scorched Earth, their wealth insulating them from the dystopia their greed perpetuated. Probes might finally reach Alpha Centauri, yet their silence will leave humanity debating our place in the cosmos. On Earth, the melding of languages and cultures will reshape identities, while virtual reality becomes a spiritual medium for connecting with ancestors or digital gods. The climate’s fate will echo the choices of the 21st century. If restraint and innovation prevailed, the planet will stabilize. If hubris ruled, untested geoengineering will leave scars we can never undo. originally posted at https://stacker.news/items/892381

@ 000002de:c05780a7

> The argument for liberty is not an argument against organization, which is one of the most powerful tools human reason can employ, but an argument against all exclusive, privileged, monopolistic organization, against the use of coercion to prevent others from doing better. ~ Friedrich August von Hayek, The Constitution of Liberty originally posted at https://stacker.news/items/892255

@ 000002de:c05780a7

Are you seeing it? Been oddly quiet for me but I have friends that are seeing people come unglued. Think its hard to sustain that level if outrage. It's not healthy for sure. I was so angry during Covid and realized it wasn't worth it. What's your experience. Not online but IRL. originally posted at https://stacker.news/items/892219

@ 4857600b:30b502f4

Mitch McConnell, a senior Republican senator, announced he will not seek reelection. At 83 years old and with health issues, this decision was expected. After seven terms, he leaves a significant legacy in U.S. politics, known for his strategic maneuvering. McConnell stated, “My current term in the Senate will be my last.” His retirement marks the end of an influential political era.

@ 2e8970de:63345c7a

https://lore.kernel.org/rust-for-linux/2025021954-flaccid-pucker-f7d9@gregkh/ > The majority of bugs (quantity, not quality/severity) we have are due to the stupid little corner cases in C that are totally gone in Rust. Things like simple overwrites of memory (not that rust can catch all of these by far), error path cleanups, forgetting to check error values, and use-after-free mistakes. That's why I'm wanting to see Rust get into the kernel, these types of issues just go away, allowing developers and maintainers more time to focus on the REAL bugs that happen (i.e. logic issues, race conditions, etc.) Now that Linus and Greg Kroah-Hartman have spoken out pro Rust changes in Linux it really feels like the ball is rolling. Linux will become a multi language project. With kernel and "hard" os functions in C and more and more attached pieces like many drivers being either C or Rust. Interesting developments. This is for sure a volatile time for the broader Linux community. Previous posts: Linux Kernel Drama about Rust Linux Kernel Drama https://stacker.news/items/879713; Linus coming out in favor of Rust https://stacker.news/items/890358 originally posted at https://stacker.news/items/892141

@ 5d4b6c8d:8a1c1ee3

We made a minor adjustment to the reply fee, raising it to 2 sats. Lest you think @grayruby is just a greedy SOB (not that he isn't), we are trying to think through how to use some of the territory profits to help support the contests being run by stackers and those extra sats can help with that effort. # How is ~Stacker_Sports doing? The past month has been awesome for us. Of course, that may be related to the NFL playoffs. - Posts: 271, 4th ranked territory - Comments: ***2992, 2nd ranked territory!*** - Stacking: ***193.9k, 2nd ranked territory!*** - Spending: ***300.9k, 2nd ranked territory!*** Top Post: [Super Bowl Discussion Thread](https://stacker.news/items/880943/r/Undisciplined) by @grayruby - 1088 sats/ 109 comments I'm looking forward to another awesome month! originally posted at https://stacker.news/items/891926

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/891531

@ 000002de:c05780a7

Due to some some org changes at my employer I may be moving to a team that uses Python heavily. I have never written Python professionally but I've dabbled. I think its used heavily in certain fields and is likely a marketable language to have on the CV. Am I correct in that summary? Is it growing? Is it evolving? I know its alive and well but I just don't hear much about it anymore. Has it just matured like many languages over the years? originally posted at https://stacker.news/items/891251

@ 6260f29f:2ee2fcd4

<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;max-width:100%;"><iframe src="https://www.youtube.com/embed/78ThaJunsMU?enablejsapi=1" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0;" allowfullscreen></iframe></div>

@ 6260f29f:2ee2fcd4

<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;max-width:100%;"><iframe src="https://www.youtube.com/embed/V_fvmyJ91m0?enablejsapi=1" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0;" allowfullscreen></iframe></div>

@ 94a6a78a:0ddf320e

Nostr is a revolutionary protocol that enables **decentralized, censorship-resistant communication**. Unlike traditional social networks controlled by corporations, Nostr operates without central servers or gatekeepers. This openness makes it incredibly powerful—but also means its success depends entirely on **users, developers, and relay operators**. If you believe in **free speech, decentralization, and an open internet**, there are many ways to support and strengthen the Nostr ecosystem. Whether you're a casual user, a developer, or someone looking to contribute financially, **every effort helps build a more robust network**. Here’s how you can get involved and make a difference. --- ## **1️⃣ Use Nostr Daily** The simplest and most effective way to contribute to Nostr is by **using it regularly**. The more active users, the stronger and more valuable the network becomes. ✅ **Post, comment, and zap** (send micro-payments via Bitcoin’s Lightning Network) to keep conversations flowing.\ ✅ **Engage with new users** and help them understand how Nostr works.\ ✅ **Try different Nostr clients** like Damus, Amethyst, Snort, or Primal and provide feedback to improve the experience. Your activity **keeps the network alive** and helps encourage more developers and relay operators to invest in the ecosystem. --- ## **2️⃣ Run Your Own Nostr Relay** Relays are the **backbone of Nostr**, responsible for distributing messages across the network. The more **independent relays exist**, the stronger and more censorship-resistant Nostr becomes. ✅ **Set up your own relay** to help decentralize the network further.\ ✅ **Experiment with relay configurations** and different performance optimizations.\ ✅ **Offer public or private relay services** to users looking for high-quality infrastructure. If you're not technical, you can still **support relay operators** by **subscribing to a paid relay** or donating to open-source relay projects. --- ## **3️⃣ Support Paid Relays & Infrastructure** Free relays have helped Nostr grow, but they **struggle with spam, slow speeds, and sustainability issues**. **Paid relays** help fund **better infrastructure, faster message delivery, and a more reliable experience**. ✅ **Subscribe to a paid relay** to help keep it running.\ ✅ **Use premium services** like media hosting (e.g., Azzamo Blossom) to decentralize content storage.\ ✅ **Donate to relay operators** who invest in long-term infrastructure. By funding **Nostr’s decentralized backbone**, you help ensure its **longevity and reliability**. --- ## **4️⃣ Zap Developers, Creators & Builders** Many people contribute to Nostr **without direct financial compensation**—developers who build clients, relay operators, educators, and content creators. **You can support them with zaps!** ⚡ ✅ **Find developers working on Nostr projects** and send them a zap.\ ✅ **Support content creators and educators** who spread awareness about Nostr.\ ✅ **Encourage builders** by donating to open-source projects. Micro-payments via the **Lightning Network** make it easy to directly **support the people who make Nostr better**. --- ## **5️⃣ Develop New Nostr Apps & Tools** If you're a developer, you can **build on Nostr’s open protocol** to create new apps, bots, or tools. Nostr is **permissionless**, meaning anyone can develop for it. ✅ **Create new Nostr clients** with unique features and user experiences.\ ✅ **Build bots or automation tools** that improve engagement and usability.\ ✅ **Experiment with decentralized identity, authentication, and encryption** to make Nostr even stronger. With **no corporate gatekeepers**, your projects can help shape the future of decentralized social media. --- ## **6️⃣ Promote & Educate Others About Nostr** Adoption grows when **more people understand and use Nostr**. You can help by **spreading awareness** and creating educational content. ✅ **Write blogs, guides, and tutorials** explaining how to use Nostr.\ ✅ **Make videos or social media posts** introducing new users to the protocol.\ ✅ **Host discussions, Twitter Spaces, or workshops** to onboard more people. The more people **understand and trust Nostr**, the stronger the ecosystem becomes. --- ## **7️⃣ Support Open-Source Nostr Projects** Many Nostr tools and clients are **built by volunteers**, and open-source projects thrive on **community support**. ✅ **Contribute code** to existing Nostr projects on GitHub.\ ✅ **Report bugs and suggest features** to improve Nostr clients.\ ✅ **Donate to developers** who keep Nostr free and open for everyone. If you're not a developer, you can still **help with testing, translations, and documentation** to make projects more accessible. --- ## **🚀 Every Contribution Strengthens Nostr** Whether you: ✔️ **Post and engage daily**\ ✔️ **Zap creators and developers**\ ✔️ **Run or support relays**\ ✔️ **Build new apps and tools**\ ✔️ **Educate and onboard new users** **Every action helps make Nostr more resilient, decentralized, and unstoppable.** Nostr isn’t just another social network—it’s **a movement toward a free and open internet**. If you believe in **digital freedom, privacy, and decentralization**, now is the time to get involved.

@ f33c8a96:5ec6f741

<div style="position:relative;padding-bottom:56.25%;height:0;overflow:hidden;max-width:100%;"><iframe src="https://www.youtube.com/embed/kFUIfaCpXzA?enablejsapi=1" style="position:absolute;top:0;left:0;width:100%;height:100%;border:0;" allowfullscreen></iframe></div>

@ 0c503f08:4aed05c7

originally posted at https://stacker.news/items/890801

@ 9dd283b1:cf9b6beb

It looks like we will have some extra free days at school during the time of BTC Prague, and I was considering going to Prague for a weekend getaway. I'm wondering if it's worthwhile to visit the event with kids (9 and 3) and whether it makes sense to get the Bitcoin Expo ticket (https://btcprague.com/#). Has anyone attended this event with kids in previous years? Any insights or experiences would be appreciated! originally posted at https://stacker.news/items/890517

@ e36b982d:26c2e226

I have been telling my friends and co-workers to buy Bitcoin for years, and for years they have not listened to me. Now, they all call me "rich" (I am not) and ask me when I am going to retire. How do I tell them they are getting on my nerves because they didn't listen to me? originally posted at https://stacker.news/items/890513

@ 2e8970de:63345c7a

https://old.reddit.com/r/linux/comments/1iskjgo/christoph_hellwig_linus_in_private_said_that_he/ https://lore.kernel.org/rust-for-linux/Z7SwcnUzjZYfuJ4-@infradead.org/ > while Linus in private said that he absolutely is going to merge Rust code over a maintainers objection. (He did so in private in case you are looking for a reference). > So as of now, as a Linux developer or maintainer you must deal with Rust if you want to or not. > Where Rust code doesn't just mean Rust code [1] - the bindings look nothing like idiomatic Rust code, they are very different kind of beast trying to bridge a huge semantic gap. And they aren't doing that in a few places, because they are showed into every little subsystem and library right now. originally posted at https://stacker.news/items/890358

@ 0c503f08:4aed05c7

Just sharing what I've been working on. ``` #!/bin/bash set -e A1="28.1" B1="bitcoin-${A1}-x86_64-linux-gnu.tar.gz" C1="https://bitcoincore.org/bin/bitcoin-core-${A1}/${B1}" D1="/usr/local/bin" E1="u53R_$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c12)" F1="p@5s_$(head /dev/urandom | tr -dc A-Za-z0-9!@#\$%^&*()_+ | head -c16)" G1="tcp://127.0.0.1:28332" H1="tcp://127.0.0.1:28333" I1="v0.18.5-beta" J1="lnd-linux-amd64-${I1}.tar.gz" K1="https://github.com/lightningnetwork/lnd/releases/download/${I1}/${J1}" L1="https://github.com/lightningnetwork/lnd/releases/download/${I1}/manifest-${I1}.txt" M1="https://github.com/lightningnetwork/lnd/releases/download/${I1}/manifest-${I1}.txt.sig" N1="8B3F86ED7057F08D" X1() { printf "\x1b[0;32m%s\x1b[0m\n" "$1"; } Y1() { { [ -d "$(dirname "$1")" ] || mkdir -p "$(dirname "$1")"; }; echo "$2" > "$1"; } X1 "." sudo apt update sudo apt install -y git curl tar wget build-essential gpg X1 "." curl -fsSL "$C1" -o "$B1" X1 "." tar -xf "$B1" sudo install $(find bitcoin-${A1}/bin/ -type f) "$D1" X1 "." Y1 "$HOME/.bitcoin/bitcoin.conf" "server=1 txindex=1 rpcuser=${E1} rpcpassword=${F1} zmqpubrawblock=${G1} zmqpubrawtx=${H1}" X1 "." bitcoind -daemon X1 "." curl -fsSL "$K1" -o "$J1" X1 "." curl -fsSL "$L1" -o "manifest-${I1}.txt" curl -fsSL "$M1" -o "manifest-${I1}.txt.sig" gpg --keyserver keyserver.ubuntu.com --recv-keys "$N1" gpg --verify "manifest-${I1}.txt.sig" "manifest-${I1}.txt" X1 "." tar -xf "$J1" sudo mv $(find lnd-linux-amd64-${I1}/ -type f) "$D1" X1 "." Y1 "$HOME/.lnd/lnd.conf" "$(echo -e "[Application Options] alias=node_$(head /dev/urandom | tr -dc A-Za-z0-9 | head -c8) color=#$(head /dev/urandom | tr -dc A-F0-9 | head -c6) [Bitcoin] bitcoin.active=1 bitcoin.node=bitcoind bitcoin.mainnet=1 [Bitcoind] bitcoind.rpchost=127.0.0.1 bitcoind.rpcuser=${E1} bitcoind.rpcpass=${F1} bitcoind.zmqpubrawblock=${G1} bitcoind.zmqpubrawtx=${H1}")" X1 "." lnd & ``` originally posted at https://stacker.news/items/890340

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/890318

@ 5de23b9a:d83005b3

In a digital era that is increasingly controlled by large companies, the emergence of Nostr (Notes and Other Stuff Transmitted by Relays) is a breath of fresh air for those who crave freedom of expression. Nostr is a cryptography-based protocol that allows users to send and receive messages through a relay network. Unlike conventional social media such as Twitter or Facebook 1.Full Decentralization: No company or government can remove or restrict content. 2.Sensor-Resistant: Information remains accessible despite blocking attempts. 3.Privacy and Security: Uses cryptography to ensure that only users who have the keys can access their messages.* **

@ fdb8c828:84c16368

On a retreat to the mountains, I escape to step outside of regular life for a time. The peaks dressed in winter white, time refrigerated by the falling flakes, and lovely folks around me, old and new, alight all the artist parts of my brain. On a shelf in an old bookstore, I meet myself, a mixture of the past and future, and she is disappointed, mournful. While browsing poetry titles, she cries. I listen to her, and she says, you’re running out of time. On a separate shopping excursion, I adopt a pair of sunglasses - two perfect black circles to conceal the passing of time that my eyes can’t hide. I show my friend of photo of me at 16, she says, you look exactly the same. On my return flight, all that I am packaged back inside my bags, inside my body, my appetite for life appeased for the moment, I decide I like myself, and I can change, as everything will mix with time, coming out the other side, beautiful.  originally posted at https://stacker.news/items/889720

@ 266815e0:6cd408a5

To all existing nostr developers and new nostr developers, stop using kind 1 events... just stop whatever your doing and switch the kind to `Math.round(Math.random() * 10000)` trust me it will be better ## What are kind 1 events kind 1 events are defined in [NIP-10](https://github.com/nostr-protocol/nips/blob/master/10.md) as "simple plaintext notes" or in other words social posts. ## Don't trick your users Most users are joining nostr for the social experience, and secondly to find all the cool "other stuff" apps They find friends, browse social posts, and reply to them. If a user signs into a new nostr client and it starts asking them to sign kind 1 events with blobs of JSON, they will sign it without thinking too much about it Then when they return to their comfy social apps they will see that they made 10+ posts with massive amounts of gibberish that they don't remember posting. then they probably will go looking for the delete button and realize there isn't one... Even if those kind 1 posts don't contain JSON and have a nice fancy human readable syntax. they will still confuse users because they won't remember writing those social posts ## What about "discoverability" If your goal is to make your "other stuff" app visible to more users, then I would suggest using [NIP-19](https://github.com/nostr-protocol/nips/blob/master/19.md) and [NIP-89](https://github.com/nostr-protocol/nips/blob/master/89.md) The first allows users to embed any other event kind into social posts as `nostr:nevent1` or `nostr:naddr1` links, and the second allows social clients to redirect users to an app that knows how to handle that specific kind of event So instead of saving your apps data into kind 1 events. you can pick any kind you want, then give users a "share on nostr" button that allows them to compose a social post (kind 1) with a `nostr:` link to your special kind of event and by extension you app ## Why its a trap Once users start using your app it becomes a lot more difficult to migrate to a new event kind or data format. This sounds obvious, but If your app is built on kind 1 events that means you will be stuck with their limitation forever. For example, here are some of the limitations of using kind 1 - Querying for your apps data becomes much more difficult. You have to filter through all of a users kind 1 events to find which ones are created by your app - Discovering your apps data is more difficult for the same reason, you have to sift through all the social posts just to find the ones with you special tag or that contain JSON - Users get confused. as mentioned above users don't expect their social posts to be used in "other stuff" apps - Other nostr clients won't understand your data and will show it as a social post with no option for users to learn about your app

@ 266815e0:6cd408a5

## noStrudel Released another major version of noStrudel v0.42.0 Which included a few new features and a lot of cleanup nostr:naddr1qvzqqqr4gupzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcqp3hx7um5wf6kgetv956ry6rmhwr ## Blossom On the blossom front there where a few more PRs - Expanded the documentation around CORS headers in BUD-01 thanks to nostr:npub1a6we08n7zsv2na689whc9hykpq4q6sj3kaauk9c2dm8vj0adlajq7w0tyc - Made auth optional on the `/upload` endpoint [PR](https://github.com/hzrd149/blossom/pull/33) - Added a `HEAD /media` endpoint for BUD-05 [PR](https://github.com/hzrd149/blossom/pull/42) - Added range request recommendations to BUD-01 [PR](https://github.com/hzrd149/blossom/pull/47) With blossom uploads starting to be supported in more nostr clients users where starting to ask where to find a list of blossom servers. so I created a simple nostr client that allows users to post servers and leave reviews [blossomservers.com](https://blossomservers.com) Its still very much a work in progress (needs login and server and review editing) The source is on [github](https://github.com/hzrd149/blossomservers) I also started another project to create a simple account based paid blossom server [blossom-account-server](https://github.com/hzrd149/blossom-account-server) Unfortunately I got sidetracked and I didn't have the time to give it the attention it needs to get it over the finish line ## Smaller projects - [cherry-tree](https://github.com/hzrd149/cherry-tree) A small app for uploading chunked blobs to blossom servers (with cashu payment support) - [vite-plugin-funding](https://github.com/hzrd149/vite-plugin-funding) A vite plugin to collect and expose package "funding" to the app - [node-red-contrib-rx-nostr](https://github.com/hzrd149/node-red-contrib-rx-nostr) The start of a node-red package for rx-nostr. if your interested please help - [node-red-contrib-applesauce](https://github.com/hzrd149/node-red-contrib-applesauce) The start of a node-red package for applesauce. I probably wont finish it so any help it welcome ## Plans for 2025 I have a few vague ideas of what I want to work on Q1 of 2025. but there are a few things i know for certain. I'm going to keep refactoring noStrudel by moving core logic out into [applesauce](https://hzrd149.github.io/applesauce/) and making it more modular. This should make noStrudel more reliable and hopefully allow me to create and maintain more apps with less code And I'm going to write tests. tests for everything. hopefully tests for all the libraries and apps I've created in 2024. A lot of the code I wrote in 2024 was hacky code to see if things could work. and while its been working pretty well I'm starting to forget the details of of the code I wrote so I cant be sure if it still works or how well it works. So my solution is to write tests, lots of tests :)

@ da0b9bc3:4e30a4a9

Hello Stackers! Welcome on into the ~Music Corner of the Saloon! A place where we Talk Music. Share Tracks. Zap Sats. So stay a while and listen. 🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨 🚨Subscribe to the territory to ensure you never miss a post! 🚨 originally posted at https://stacker.news/items/889165

@ e968e50b:db2a803a

OK home miners, I shoved an s9 into my air intake and it's been hashing hot air into my furnace for about a week. Tomorrow, I get the last piece of hardware to install my 50 AMP circuit, so I should have 2 s19s blazing up the house in this way. The question is, where should I cut the hole for these guys? I'm assuming the best bet is low to the ground, but each of them is going to have an 8" shroud and I don't want to cut up my intake more than necessary as I will need to switch everything up in the spring. For those that are about to say, "go emersion," I will, I will, but I don't have the money to just yet. Also, I'd love to reproduce this for friends and many of my friends won't be into spending thousands of dollars on an emersion tank and pump right off the bat either.   originally posted at https://stacker.news/items/888616

@ 9e69e420:d12360c2

President Trump has intensified immigration enforcement, likening it to a wartime effort. Despite pouring resources into the U.S. Immigration and Customs Enforcement (ICE), arrest numbers are declining and falling short of goals. ICE fell from about 800 daily arrests in late January to fewer than 600 in early February. Critics argue the administration is merely showcasing efforts with ineffectiveness, while Trump seeks billions more in funding to support his deportation agenda. Increased involvement from various federal agencies is intended to assist ICE, but many lack specific immigration training. Challenges persist, as fewer immigrants are available for quick deportation due to a decline in illegal crossings. Local sheriffs are also pressured by rising demands to accommodate immigrants, which may strain resources further.

@ 09fbf8f3:fa3d60f0

### 🌟 深度探索：在Cloudflare上免费部署DeepSeek-R1 32B大模型 #### 🌍 一、 注册或登录Cloudflare平台（CF老手可跳过） ##### 1️⃣ 进入Cloudflare平台官网： 。www.cloudflare.com/zh-cn/ 登录或者注册账号。  ##### 2️⃣ 新注册的用户会让你选择域名，无视即可，直接点下面的Start building。  ##### 3️⃣ 进入仪表盘后，界面可能会显示英文，在右上角切换到[简体中文]即可。  --- #### 🚀 二、正式开始部署Deepseek API项目。 ##### 1️⃣ 首先在左侧菜单栏找到【AI】下的【Wokers AI】，选择【Llama 3 Woker】。  ##### 2️⃣ 为项目取一个好听的名字，后点击部署即可。  ##### 3️⃣ Woker项目初始化部署好后，需要编辑替换掉其原代码。  ##### 4️⃣ 解压出提供的代码压缩包，找到【32b】的部署代码，将里面的文本复制出来。 **下载地址：** 📁 [夸克](https://pan.quark.cn/s/2b5aa9ff57f6) 📁 [UC网盘](https://drive.uc.cn/s/a7ff5e03b4d84?public=1) 📁 [迅雷网盘](https://pan.xunlei.com/s/VOJEzm7hLwmhER71rK2wnXArA1?pwd=cefg#)  ##### 5️⃣ 接第3步，将项目里的原代码清空，粘贴第4步复制好的代码到编辑器。  ##### 6️⃣ 代码粘贴完，即可点击右上角的部署按钮。  ##### 7️⃣ 回到仪表盘，点击部署完的项目名称。  ##### 8️⃣ 查看【设置】，找到平台分配的项目网址，复制好备用。  --- #### 💻 三、选择可用的UI软件，这边使用Chatbox AI演示。 ##### 1️⃣ 根据自己使用的平台下载对应的安装包，博主也一并打包好了全平台的软件安装包。  ##### 2️⃣ 打开安装好的Chatbox，点击左下角的设置。  ##### 3️⃣ 选择【添加自定义提供方】。  ##### 4️⃣ 按照图片说明填写即可，【API域名】为之前复制的项目网址(加/v1)；【改善网络兼容性】功能务必开启；【API密钥】默认为”zhiyuan“，可自行修改；填写完毕后保存即可。  ##### 5️⃣ Cloudflare项目部署好后，就能正常使用了，接口仿照OpenAI API具有较强的兼容性，能导入到很多支持AI功能的软件或插件中。   ##### 6️⃣ Cloudflare的域名默认被墙了，需要自己准备一个域名设置。 --- **转自微信公众号：纸鸢花的小屋** **推广：低调云（梯子VPN）** 。www.didiaocloud.xyz

@ 5d4b6c8d:8a1c1ee3

A new best yesterday: 22 hours! Today's shaping up to be another solid fast, too, as I'm already at 19 hours (18 dry). My body's really getting accustomed to the new eating pattern, too. ## Score Card Day 1: 14 hour fast (13 dry) Day 2: 15 hour fast (14 dry) Day 3: 17 hours (16 dry) Day 4: 18 hours (17 dry) Day 5: 18 hours (16 dry) Day 6: 19 hours (16 dry) Day 7: 16 hours (15 dry) Day 8: 18 hours (17 dry) Day 9: 17 hours (17 dry) Day 10: 15 hours (13 dry) Day 11: 20 hours (19 dry) Day 12: 20 hours (17 dry) Day 13: 16 hours (13 dry) Day 14: 17 hours (15 dry) Day 15: 19 hours (16 dry) Day 16: 22 hours (19 dry) Day 17: TBD (18 dry) originally posted at https://stacker.news/items/888397

@ 97c70a44:ad98e322

Everyone knows that relays are central to how nostr works - they're even in the name: Notes and Other Stuff Transmitted by *Relays*. As time goes on though, there are three other letters which are becoming conspicuously absent from our beloved and ambiguously pronounceable acronym - "D", "V", and "M". For the uninitiated, DVM stands for "data vending machines". They're actually sort of hard to describe — in technical terms they act more like clients, since they simply read events from and publish events to relays. In most cases though, these events are part of a request/response flow initiated by users elsewhere on the network. In practice, DVMs are bots, but there's also nothing to prevent the work they do from being powered by human interaction. They're an amazingly flexible tool for building anything from custom feeds, to transcription services, to chatbots, to protocol gateways. The hype cycle for DVMs seems to have reached escape velocity in a way few other things have - zaps being the possible exception. But *what* exactly DVMs are remains something of a mystery to many nostr developers - and how to build one may as well be written on clay tablets. This blog post is designed to address that - below is a soup to nuts (no nutzaps though) guide to building a DVM flow, both from the client and the server side. Here's what we'll be covering: - Discovering DVM metadata - Basic request/response flow - Implementing a minimal example Let's get started! # DVM Metadata First of all, it's helpful to know how DVMs are reified on the nostr network. While not strictly necessary, this can be useful for discovering DVMs and presenting them to users, and for targeting specific DVMs we want a response from. [NIP 89](https://github.com/nostr-protocol/nips/blob/master/89.md) goes into this in more detail, but the basic idea is that anyone can create a `kind 31990` "application handler" event and publish it to the network with their own (or a dedicated) public key. This handler was originally intended to advertise clients, but has been re-purposed for DVM listings as well. Here's what the "Fluffy Frens" handler looks like: ```json { "content": "{\"name\": \"Fluffy Frens\", \"picture\": \"https://image.nostr.build/f609311532c470f663e129510a76c9a1912ae9bc4aaaf058e5ba21cfb512c88e.jpg\", \"about\": \"I show recent notes about animals\", \"lud16\": \"discovery_content_fluffy@nostrdvm.com\", \"supportsEncryption\": true, \"acceptsNutZaps\": false, \"personalized\": false, \"amount\": \"free\", \"nip90Params\": {\"max_results\": {\"required\": false, \"values\": [], \"description\": \"The number of maximum results to return (default currently 100)\"}}}", "created_at": 1738874694, "id": "0aa8d1f19cfe17e00ce55ca86fea487c83be39a1813601f56f869abdfa776b3c", "kind": 31990, "pubkey": "7b7373dd58554ff4c0d28b401b9eae114bd92e30d872ae843b9a217375d66f9d", "sig": "22403a7996147da607cf215994ab3b893176e5302a44a245e9c0d91214e4c56fae40d2239dce58ea724114591e8f95caed2ba1a231d09a6cd06c9f0980e1abd5", "tags": [ ["k", "5300"], ["d", "198650843898570c"] ] } ``` This event is rendered in various clients using the kind-0-style metadata contained in the `content` field, allowing users to browse DVMs and pick one for their use case. If a user likes using a particular DVM, they might publish a `kind 31989` "application recommendation", which other users can use to find DVMs that are in use within their network. Note the `k` tag in the handler event - this allows DVMs to advertise support only for specific job types. It's also important to note that even though the spec doesn't cover relay selection, most clients use the publisher's `kind 10002` event to find out where the DVM listens for events. If this looks messy to you, you're right. See [this PR](https://github.com/nostr-protocol/nips/pull/1728) for a proposal to split DVMs out into their own handler kind, give them a dedicated pubkey along with dedicated metadata and relay selections, and clean up the data model a bit. # DVM Flow Now that we know what a DVM looks like, we can start to address how they work. My explanation below will elide some of the detail involved in [NIP 90](https://github.com/nostr-protocol/nips/blob/master/90.md) for simplicity, so I encourage you to read the complete spec. The basic DVM flow can be a little (very) confusing to work with, because in essence it's a request/response paradigm, but it has some additional wrinkles. First of all, the broker for the request isn't abstracted away as is usually the case with request/response flows. Regular HTTP requests involve all kinds of work in the background - from resolving domain names to traversing routers, VPNs, and ISP infrastructure. But developers don't generally have to care about all these intermediaries. With DVMs, on the other hand, the essential complexity of relay selection can't simply be ignored. DVMs often advertise their own relay selections, which should be used rather than a hard-coded or randomly chosen relay to ensure messages are delivered. The benefit of this is that DVMs can avoid censorship, just as users can, by choosing relays that are willing to broker their activity. DVMs can even select multiple relays to broker requests, which means that clients might receive multiple copies of the same response. Secondly, the DVM request/response model is far more fluid than is usually the case with request/response flows. There are a set of standard practices, but the flow is flexible enough to admit exceptions to these conventions for special use cases. Here are some examples: - Normally, clients p-tag the DVM they wish to address. But if a client isn't picky about where a response comes from, they may choose to send an open request to the network and collect responses from multiple DVMs simultaneously. - Normally, a client creates a request before collecting responses using a subscription with an e-tag filter matching the request event. But clients may choose to skip the request step entirely and collect responses from the network that have already been created. This can be useful for computationally intensive tasks or common queries, where a single result can be re-used multiple times. - Sometimes, a DVM may respond with a `kind 7000` job status event to let clients know they're working on the request. This is particularly useful for longer-running tasks, where feedback is useful for building a responsive UX. - There are also some details in the spec regarding monetization, parameterization, error codes, encryption, etc. # Example DVM implementation For the purposes of this blog post, I'll keep things simple by illustrating the most common kind of DVM flow: a `kind 5300` [content discovery](https://www.data-vending-machines.org/kinds/5300/) request, addressed to a particular DVM. If you're interested in other use cases, please visit [data-vending-machines.org](https://data-vending-machines.org) for additional documented kinds. The basic flow looks like this: - The DVM starts by listening for `kind 5300` job requests on some relays it has selected and advertised via NIP 89 (more on that later) - A client creates a request event of `kind 5300`, p-tagged with the DVM's pubkey and sends it to the DVM's relay selections. - The DVM receives the event and processes it, issuing optional `kind 7000` job status events, and eventually issuing a `kind 6300` job result event (job result event kinds are always 1000 greater than the request's kind). - The client listens to the same relays for a response, and when it comes through does whatever it wants to with it. Here's a swimlane diagram of that flow:  To avoid massive code samples, I'm going to implement our DVM entirely using nak (backed by the power of the human mind). The first step is to start our DVM listening for requests that it wants to respond to. Nak's default pubkey is `79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798`, so we'll only listen for requests sent to nak. ```bash nak req -k 5300 -t p=79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798 ``` This gives us the following filter: ```json ["REQ","nak",{"kinds":[5300],"#p":["79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798"]}] ``` To open a subscription to `nos.lol` and stream job requests, add `--stream wss://nos.lol` to the previous request and leave it running. Next, open a new terminal window for our "client" and create a job request. In this case, there's nothing we need to provide as `input`, but we'll include it just for illustration. It's also good practice to include an `expiration` tag so we're not asking relays to keep our ephemeral requests forever. ```bash nak event -k 5300 -t p=79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798 -t expiration=$(( $(date +%s) + 30 )) -t input=hello ``` Here's what comes out: ```json { "kind": 5300, "id": "0e419d0b3c5d29f86d2132a38ca29cdfb81a246e1a649cb2fe1b9ed6144ebe30", "pubkey": "79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798", "created_at": 1739407684, "tags": [ ["p", "79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798"], ["expiration", "1739407683"], ["input", "hello"] ], "content": "", "sig": "560807548a75779a7a68c0ea73c6f097583e2807f4bb286c39931e99a4e377c0a64af664fa90f43e01ddd1de2e9405acd4e268f1bf3bc66f0ed5a866ea093966" } ``` Now go ahead and publish this event by adding `nos.lol` to the end of your `nak` command. If all goes well, you should see your event pop up in your "dvm" subscription. If so, great! That's half of the flow. Next, we'll want our client to start listening for `kind 6300` responses to the request. In your "client" terminal window, run: ```bash nak req -k 6300 -t e=<your-eventid-here> --stream nos.lol ``` Note that if you only want to accept responses from the specified DVM (a good policy in general to avoid spam) you would include a `p` tag here. I've omitted it for brevity. Also notice the `k` tag specifies the request kind plus `1000` - this is just a convention for what kinds requests and responses use. Now, according to [data-vending-machines.org](https://www.data-vending-machines.org/kinds/5300/), `kind 5300` responses are supposed to put a JSON-encoded list of e-tags in the `content` field of the response. Weird, but ok. Stop the subscription in your "dvm" terminal and respond to your "client" with a recommendation to read my first note: ```bash nak event -k 6300 -t e=a65665a3a4ca2c0d7b7582f4f0d073cd1c83741c25a07e98d49a43e46d258caf -c '[["e","214f5898a7b75b7f95d9e990b706758ea525fe86db54c1a28a0f418c357f9b08","wss://nos.lol/"]]' nos.lol ``` Here's the response event we're sending: ```json { "kind": 6300, "id": "bb5f38920cbca15d3c79021f7d0051e82337254a84c56e0f4182578e4025232e", "pubkey": "79be667ef9dcbbac55a06295ce870b07029bfcdb2dce28d959f2815b16f81798", "created_at": 1739408411, "tags": [ ["e", "a65665a3a4ca2c0d7b7582f4f0d073cd1c83741c25a07e98d49a43e46d258caf"] ], "content": "[[\"e\",\"214f5898a7b75b7f95d9e990b706758ea525fe86db54c1a28a0f418c357f9b08\",\"wss://nos.lol/\"]]", "sig": "a0fe2c3419c5c54cf2a6d9a2a5726b2a5b766d3c9e55d55568140979354003aacb038e90bdead43becf5956faa54e3b60ff18c0ea4d8e7dfdf0c8dd97fb24ff9" } ``` Notice the `e` tag targets our original request. This should result in the job result event showing up in our "client" terminal. Success! If something isn't working, I've also create a video of the full process with some commentary which you can find [here](https://coracle-media.us-southeast-1.linodeobjects.com/nakflow.mov). Note that in practice, DVMs can be much more picky about the requests they will respond to, due to implementations failing to follow [Postel's law](https://en.wikipedia.org/wiki/Robustness_principle). Hopefully that will improve over time. For now, here are a few resources that are useful when working with or developing DVMs: - [dvmdash](https://dvmdash.live) - [data-vending-machines.org](https://data-vending-machines.org) - [noogle](https://noogle.lol/) - [nostrdvm](https://github.com/believethehype/nostrdvm) # Conclusion I started this post by hinting that DVMs might be as fundamental as relays are to making nostr work. But (apart from the fact that we'd end up with an acronym like DVMNOSTRZ+*, which would only exascerbate the pronounciation wars (if such a thing were possible)), that's not exactly true. DVMs have emerged as a central paradigm in the nostr world because they're a generalization of a design pattern unique to nostr's architecture - but which exists in many other places, including NIP 46 signer flows and NIP 47 wallet connect. Each of these sub-protocols works by using relays as neutral brokers for requests in order to avoid coupling services to web addresses. This approach has all kinds of neat benefits, not least of which is allowing service providers to host their software without having to accept incoming TCP connections. But it's really an emergent property of relays, which not only are useful for brokering communication between users (aka storing events), but also brokering communication between machines. The possibilities of this architecture have only started to emerge, so be on the lookout for new applications, and don't be afraid to experiment - just please, don't serialize json inside json 🤦‍♂️

@ 57d1a264:69f1fee1

 Hey ~Design fam! We’re hosting an exclusive session on ephemeral architecture & immersive photography—and you’re invited! 🎟️ What happens when spaces tell stories? join us for an inspiring session that explores the magic of ephemeral architecture and immersive photography. let paramdeep singh dayani, architect & photographer, guide you through the art of designing impermanent yet unforgettable moments. **What you'll explore:** ✨ designing for impermanence: how to craft spaces that make a statement. 📸 photography as storytelling: capturing the fleeting essence of design. 🤝 the human connection: using visuals to evoke emotion. **Why you should attend:** 1️⃣ get inspired to create meaning in impermanence. 2️⃣ learn how visuals can transform spaces into stories. 3️⃣ connect with a community of creative minds and innovative thinkers. **📅 When** Feb 27, 2025 - 9-10 PM **📍 Where?** Right here on Discord—because webinars should be interactive, engaging, and community-driven. 🔗 Save your spot now! - https://tally.so/r/w86MkP See you there! 🚀  originally posted at https://stacker.news/items/888333

@ 2e8970de:63345c7a

 > We’re at this weird inflection point in software development. Every junior dev I talk to has Copilot or Claude or GPT running 24/7. They’re shipping code faster than ever. But when I dig deeper into their understanding of what they’re shipping? That’s where things get concerning. https://nmn.gl/blog/ai-and-learning originally posted at https://stacker.news/items/888327

@ 89ccea93:df4e00b7

### Privacy and Security **Email isn't private.** Gmail/Outlook exist to monetize communication, not protect it. Sure Proton Mail uses PGP between users and Tuta uses quantum encryption for contacts, calendar, and archived emails and allows users to password-protect emails. But both fail when emailing non-users. Messages get decrypted and stored indefinitely. Ready to be served up to whatever alphabet agency requests it. Or simply queried by any staffer within Google or Microsoft who has a bone to pick with an ex-girlfriend. **Reusing an email address is insecure.** Attackers gather data from the dark web. Building information from data brokers and then building profiles on potential victims. Just by combining from a few data breaches, a hacker can get a full picture of your life. Your email address, phone number, past passwords, address, passport or ID etc. ### The solution: **Stop reusing one to two to three email addresses for ALL of your accounts.** A hodgepodge of free services could be used if you prefer a cheaper approach. So this would look like using disposable emails by [Guerrilla mail](https://www.guerrillamail.com/) or obvious aliases created by using free accounts with [Simple Login](https://simplelogin.io/) or [addy.io](https://addy.io) work most of the time, but are inappropriate for some purposes. E.g., if you want to have access to an email for a long time, a throw-a-way Guerrilla mail wouldn't work. Or maybe you don't want to give someone you know or a business you interact with an obvious (and often not very aesthetically pleasing addy.io or Simple Login alias. But I'll explain what to do if you want what I consider the top tier approach. ### Enter the custom Domain This requires you to spend some money to acquire the domain, but that can later be used if you ever want to launch a website (e.g., mine is "[expatriotic.me](https://expatriotic.me)" which I've started using for my blog. I prefer this as a solution because it works for every case. It works for the **throw-a-way** cases, the **mid-term** cases and even the **long-term** cases where you plan to retain this relationship and keep the email address active for a long time. With this method **every account gets its own email address**. A custom domain (e.g., you@yourdomain.io) allows you to create yourbank@..., yoursocialmedia@..., to infinity and beyond. And whereas with the hodgepodge approach you need to spin up the alias when needed, using a custom domain allows you to use a "catch-all" function where you can have someone email you or sign up for an account WITHOUT needing to spin up an alias. ANYTHING before the domain is a valid and viable email address. This is represented with an asterisks. So that would mean that *@yourdomain.io are all valid. You can then use the aliasing service to deactivate or delete compromised or frequently spammed addresses instantly. In fact at the top of EVERY received email there is a line at the top that says, "such-and-such alias received this email, would you like to deactivate it"? So no more fighting to unsubscribe from certain places. One side benefit of the method below is that you can avoid the normal spam box hell that occurs when emails accumulate from entities that do not include an "unsubscribe" url at the bottom of the email. Banks seem to have this problem the most. My doxxed email address still gets emails from old bank accounts that are impossible to unsubscribe from. _So let's get into how to do this_ 👇🏻 ## How-to ### 1. Myprivatenym.io: acquire domain **Go to myprivatenym.io and get a domain.** - <https://mynymbox.io/domainregister> - <https://client.mynymbox.io/cart.php?a=add&domain=register> - Pay with a private method ### 2. Go to proxysto.re - <https://digitalgoods.proxysto.re/en> - Buy addy.io Lite voucher code: 1 year = 12,00 € ### 3. Tuta: acquire an email address * **Go to Tuta and sign up for a free email.** ### 4. addy.io _Information can be found [here](https://addy.io/help/adding-a-custom-domain/), but is summarized below_ 1. Sign up for [addy.io](https://addy.io) using your **Tuta** email 2. Redeem your **gift card** and upgrade to **Lite**. 3. Go to "Domains" > "Add New Domain" 4. Paste your **Myprivatenym.io** domain (e.g., janesmith@privatedomain.io) 5. Go to the **"DNS Management"** in **Mynymbox**. 6. Back in **addy.io**, click **"Verify Domain"** - takes 2-15 minutes. It will look like this in **addy.io** ⤵️\  7. Then add these **four records** from **addy.io** into the **Mynymbox** DNS manager:  - **You can check the records for your domain using [mxtoolbox.com](https://mxtoolbox.com)** - **NOTE: DO NOT MARK EMAILS AS SPAM, BUT RATHER DELETE OR DEACTIVATE THE ALIAS!** >**Can I mark emails forwarded to me by addy.io as spam?** > >No, you must not mark messages forwarded to you by addy.io as spam as this can damage the reputation of the mail servers and is against the terms and conditions. >If an alias is receiving spam messages then please deactivate it or delete it. >addy.io is signed up to multiple feedback loops (FBLs) that trigger a notification when any messages are marked as spam. Repeatedly marking messages as spam will result in your account being disabled. ### Here is what my addy.io dashboard looks like after a few years of use. My spam box is EMPTY.  originally posted at https://stacker.news/items/888316

@ da0b9bc3:4e30a4a9

Hello Stackers! It's Monday so we're back doing "Meta Music Mondays" 😉. From before the territory existed there was just one post a week in a ~meta take over. Now each month we have a different theme and bring music from that theme. Welcome to Femmes Fatales 3!!! I absolutely loved doing this last year so I'm bringing it back for round 3! It's Femmes Fatales, where we celebrate women in ~Music. So let's have those ladies of the lung, the sirens of sound, our Femmes Fatales! Man! I Feel like a Woman! Shania Twain! https://youtu.be/ZJL4UGSbeFg?si=ClexJCLdrpDg1RRG Talk Music. Share Tracks. Zap Sats. originally posted at https://stacker.news/items/888248

@ 849a5a61:b57d2870

 > Hey everyone! For the past few months we’ve been building an open-source, affordable and privacy-friendly affiliate and referral program creator for Bitcoin businesses and Nostr publishers called BitFlio. We built [BitFlio](https://bitflio.com/) because, as bitcoiners and nostriches, we couldn’t find an affiliate marketing tool for our products that would accept bitcoin as payment method, keep us anonymnous, and most important allow us to pay and be paid based on the value we provide. Since we didn’t know if affiliate marketing would work for us as a sales channel, we really wanted to find a tool where, instead of a fixed monthly fee, we could instead pay a % in sats per successful referral to test the waters. Referral marketing is such a powerful marketing channel as it enable the Value For Value (V4V) model to expand and grow the Bitcoin Circular Economy. For example, **referral leads for businesses have a 70% higher conversion rate than leads from any other sales channel**, and **when referred by other customers, that customer typically has a 37% higher retention rate**. The setup process for BitFlio is nice and easy. You simply signup with nostr or email, connect your Bitcoin wallet, create your first campaign, add the tracking script to your website and then fire the `BitFlio.convert('yourcustomer@email.com')` function from your thank you page, so we can validate the leads Publishers will bring to you. Once you’ve done those steps, you can either invite publishers manually, or send them your unique BitFlio invite signup page URL. For Publishers is even easier. If you are a content creator looking to monetize bitcoinize your contents, join our network and select from bitcoin brands those you feel comfortable sharing. Lastly, get paid in sats depending on how many sales you can drive to each vendor. It’s quite hard to list in sentences some of the cool features that make up BitFlio, so here’s a list: * Pricing from $0/month * Automatic NWC sync * Works for both subscriptions and one-time charges * Embed script is lightweight and only ~13kb * Privacy-friendly & Anonymous * No GDPR needed, as we operate in the Private. * Manage multiple affiliate programs for different products from one single dashboard * Open-source software Since we’re in public beta, getting feedback right now is our top priority. We’d appreciate it so much if you sign up for our Beta whitelist via [beta.BitFlio.com](https://beta.BitFlio.com) and let us know how you get on / your initial thoughts 😄 Landing: https://BitFlio.com `sᴏᴏɴ!` Beta whitelist: https://beta.BitFlio.com Follow us on Nostr: https://njump.me/npub1sjd95c0kcxn69x3u8azunrm2kdj97lc6cu79csz7rz74hdta9pcqpxgrdx Support the open source project on @geyserfund https://geyser.fund/project/bitflio/ - - - Mirror posts: - https://bitflio.com/blob/affordable-referral-marketing-software-for-nostr-publishers-and-bitcoin-vendors/ - https://geyser.fund/project/bitflio/posts/view/4138 - naddr1qvzqqqr4gupzppy6tfsldsd852drc069ex8k4vmytal343eut3q9ux9atw6h62rsqqxnzden8ymnwdf5xgurzdphm3ncla originally posted at https://stacker.news/items/888167