@ 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

@ 2063cd79:57bd1320

Für diejenigen, die mich nicht kennen: Ich bin Hal Finney. Ich machte meine ersten Schritte mit Kryptographie, in dem ich an einer frühen Version von PGP arbeitete, in enger Zusammenarbeit mit Phil Zimmermann. Als Phil beschloss, die PGP Corporation zu gründen, war ich einer der ersten, die er einstellte. Ich habe bis zu meiner Pensionierung an PGP gearbeitet. Zeitgleich fing ich an, mich bei den Cypherpunks zu engagieren. Neben anderen Aktivitäten betrieb ich den ersten kryptographisch basierten anonymen Remailer. Springen wir ans Ende des Jahres 2008 und der Ankündigung von Bitcoin. Ich habe bemerkt, dass Krypto-Graubärte (ich war Mitte 50) dazu neigen, zynisch zu werden. Ich war eher idealistisch; ich habe Kryptographie immer geliebt, das Mysterium und das Paradoxe daran. Als Satoshi Bitcoin in der Kryptographie-Mailingliste ankündigte, wurde er bestenfalls skeptisch aufgenommen. Kryptographen haben schon zu viele großartige Pläne von ahnungslosen Anfängern gesehen. Sie neigen zu überhasteten Reaktionen. Ich war positiver eingestellt. Ich hatte mich schon lange für kryptografische Zahlungssysteme interessiert. Außerdem hatte ich das Glück, sowohl Wei Dai als auch Nick Szabo kennenzulernen und ausgiebig mit ihnen zu korrespondieren, von denen allgemein bekannt ist, dass sie Ideen entwickelt haben, die mit Hilfe von Bitcoin verwirklicht werden sollten. Ich hatte einen Versuch unternommen, meine eigene, auf Proof-of-Work basierende Währung namens RPOW zu schaffen. Daher fand ich Bitcoin faszinierend. Als Satoshi die erste Version der Software ankündigte, schnappte ich sie mir sofort. Ich glaube, ich war die erste Person neben Satoshi, die Bitcoin laufen ließ. Ich habe Block 70 oder so gemined und ich war der Empfänger der ersten Bitcoin-Transaktion, als Satoshi mir zehn Coins als Test schickte. In den nächsten Tagen führte ich eine E-Mail-Konversation mit Satoshi, in der ich hauptsächlich Fehler meldete, die er dann beseitigte. Heute ist die wahre Identität von Satoshi ein Rätsel. Aber damals dachte ich, ich hätte es mit einem jungen Mann japanischer Abstammung zu tun, der sehr intelligent und aufrichtig war. Ich hatte das Glück, im Laufe meines Lebens viele brillante Menschen kennenzulernen, daher erkenne ich die Zeichen. Nach ein paar Tagen lief Bitcoin ziemlich stabil, also ließ ich es laufen. Das waren die Tage, als die Difficulty 1 war und man Blöcke mit dem CPU finden konnte, nicht einmal mit einem GPU. In den nächsten Tagen habe ich mehrere Blöcke gemined. Aber ich schaltete es ab, weil mein Computer zu heiß wurde und mich das Lüftergeräusch störte. Im Nachhinein wünschte ich, ich hätte länger durchgehalten, aber andererseits hatte ich außerordentliches Glück, dass ich am Anfang dabei war. Das ist so eine halb volles, halb leeres Glas Sache Das nächste Mal, dass ich von Bitcoin hörte, war Ende 2010, als ich überrascht feststellte, dass es nicht nur immer noch existierte, sondern bitcoins tatsächlich einen Geldwert hatten. Ich entstaubte meine alte Wallet und war erleichtert, als ich feststellte, dass meine bitcoins noch darin waren. Als der Preis auf eine echte Summe kletterte, transferierte ich die Coins in eine Offline-Wallet, wo sie hoffentlich für meine Erben etwas wert sein werden. Apropos Erben: 2009 erlebte ich eine Überraschung, als bei mir plötzlich eine tödliche Krankheit diagnostiziert wurde. Zu Beginn des Jahres war ich in der besten Verfassung meines Lebens, ich hatte viel Gewicht verloren und mit dem Langstreckenlauf begonnen. Ich war mehrere Halbmarathons gelaufen und hatte begonnen, für einen vollen Marathon zu trainieren. Ich hatte mich zu Läufen über 20 Meilen hochgearbeitet und dachte, ich hätte alles im Griff. Doch dann ging alles schief. Mein Körper begann zu versagen. Ich sprach undeutlich, verlor die Kraft in meinen Händen und meine Beine erholten sich nur langsam. Im August 2009 erhielt ich die Diagnose ALS, auch Lou-Gehrig-Krankheit genannt, nach dem berühmten Baseballspieler, der daran erkrankt war. ALS ist eine Krankheit, die Motoneuronen abtötet, die Signale vom Gehirn an die Muskeln weiterleiten. Sie verursacht zunächst Schwäche und dann allmählich zunehmende Lähmungen. Die Krankheit verläuft in der Regel innerhalb von 2 bis 5 Jahren tödlich. Meine Symptome waren zunächst gering und ich konnte weiterarbeiten, aber Müdigkeit und Stimmprobleme zwangen mich Anfang 2011, in den Ruhestand zu gehen. Seitdem ist die Krankheit unaufhaltsam fortgeschritten. Heute bin ich im Wesentlichen gelähmt. Ich werde durch einen Schlauch ernährt, und meine Atmung wird durch einen weiteren Schlauch unterstützt. Ich bediene den Computer mit einem kommerziellen Eyetracker-System. Es ist auch mit einem Sprachsynthesizer ausgestattet, so dass dies jetzt meine Stimme ist. Ich verbringe den ganzen Tag in meinem Elektrorollstuhl. Ich habe eine Schnittstelle mit einem Arduino entwickelt, so dass ich die Position meines Rollstuhls mit meinen Augen einstellen kann. Es war eine Umstellung, aber mein Leben ist nicht allzu schlimm. Ich kann immer noch lesen, Musik hören, fernsehen und Filme schauen. Vor kurzem habe ich entdeckt, dass ich sogar Code schreiben kann. Es geht sehr langsam, wahrscheinlich 50 Mal langsamer als vorher. Aber ich liebe das Programmieren immer noch, und es gibt mir Ziele. Derzeit arbeite ich an etwas, das Mike Hearn vorgeschlagen hat, nämlich die Sicherheitsfunktionen moderner Prozessoren, die „Trusted Computing“ unterstützen, zu nutzen, um Bitcoin-Wallets zu härten. Es ist fast fertig zur Veröffentlichung. Ich muss nur noch die Dokumentation erstellen. Und natürlich sind die Kursschwankungen von Bitcoin für mich unterhaltsam. Ich habe einen Anteil an dem Spiel. Aber ich bin durch Glück zu meinen bitcoins gekommen, ohne dass ich etwas dafür kann. Ich habe den Crash von 2011 miterlebt. Ich habe es also schon einmal erlebt. Einfach kommen, einfach gehen. Das ist meine Geschichte. Ich habe insgesamt ziemlich viel Glück. Selbst mit der ALS ist mein Leben sehr zufriedenstellend. Aber meine Lebenserwartung ist begrenzt. Diese Diskussionen über die Vererbung von bitcoins sind mehr als nur von akademischem Interesse. Meine bitcoins befinden sich in unserem Bankschließfach, und mein Sohn und meine Tochter sind technisch versiert. Ich denke, sie sind sicher genug. Ich bin mit meinem Erbe zufrieden. 

@ dbe0605a:f8fd5b2c

Originally posted on Nostr: https://highlighter.com/a/naddr1qvzqqqr4gupzpklqvpdfcuch9wkh2gary7erd4275jmrf6qw0z5sz0dhj8u06kevqyvhwumn8ghj7urjv4kkjatd9ec8y6tdv9kzumn9wshszxrhwden5te0ve5kcar9wghxummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszythwden5te0dehhxarj9emkjmn99uqzqjn0d9hz6argv5k57ur9dck5y6t5vdhkjm3df4shqtt5xduxz6tsrdmw7l  I care deeply about bitcoin adoption and ability to use bitcoin with all features of money — saving, spending, earning. We're entering an age where more and more people realise "hodl never spend" meme is hindering bitcoin adoption. More and more of use want to use bitcoin in everyday life, because we're living on it and because it's superior in every aspect. It's also incredibly fun to use it for payments. For money to thrive, it needs to circulate. Spending bitcoin orangepills merchants, their families and people around them — with each bitcoiner coming to a shop and paying with bitcoin, it's a point of contact that can trigger a train of though that later may fruit into action — "_Why are they so interested in bitcoin, what's actually so special about it?_" "_Hmm, maybe this time I will not exchange it for fiat immediately?_" Global merchant adoption grows, every day new business around the world decide to start accepting bitcoin payments. Circular economies are blooming on all continents, where people live in a new, experimental, orange coin paradigm. Companies and projects like Blink, Bitcoin Jungle, Plan B, Orange Pill App do an amazing job in facilitating this — providing great wallets, tools & services for merchants, and finally onboarding merchants themself. They also often support circular economies financially or in other ways. This is very valuable and makes the road to hyperbitcoinization a tad shorter. But there is one thing those companies are doing wrong — they're using their own, proprietary maps that display only merchants using their own wallets or POS software. I'd like to now list a few reasons why those great projects should migrate their maps into an open source, bitcoin map that is BTC Map. ## Open source, stupid [BTCmap](https://btcmap.org/) is open source, built on OpenStreetMaps, open to both developers contributions but also for map taggers (called [shadowy supertaggers](https://www.openstreetmap.org/)). Anyone can contribute, even If you don't code. Anyone can verify merchants or add new merchants to the map. BTC Map team developed [a neat system of verifications](https://btcmap.org/verify-location) that just works better than anything before or any alternative maps today.  ## Many apps, one map BTC Map is integrated inside a dozen of wallets and apps, to name a few: Wallet of Satoshi, Coinos, Bitlocal, Fedi or Aqua. It's a public good that any bitcoin product can use and grow it's network effect.  ## Uniting mappers' work BTC Map does not discriminate bitcoin merchants, that means all the merchants from proprietary maps are being mapped by taggers to BTC Map. By mapping on a closed source, proprietary map, the same merchant is mapped two times, usually by two different people — it's duplicating the same work without any bringing any benefit to both projects. Using BTC Map also brings you way more people verifying If those merchants actually still accept bitcoin, making it easier to have an up-to-date database of actual adoption. ## More bitcoin spent at your merchants When you have a business focused on spending bitcoin and onboarding merchants, you want as much bitcoin spent there as possible. If a bitcoiner coming to the area does not use your own map but some other map, they can be completely unaware that they can let their sats flow to your merchants. If we all use one merchants database, this problem disappears and more sats will flow. Why wouldn't you want your merchants displayed in dozens of other apps, completely for free? ## OpenStreetMap map is just better  Take a look at the image above: It's [La Pirraya](https://btcmap.org/community/bitcoin-la-pirraya), a small sleepy island town in El Salvador with a circular economy being facilitated by Bitcoin Beach. Even though Blink has many more merchants compared to BTC Map, when I visited it a few months ago I could find them. Not because they do not exist, but because the map does not show any roads and it was very hard to locate them in a dense network of narrow streets of La Pirraya. BTC Map allows you to turn multiple versions of satellite maps views, making it way easier to find your point of interest. Pins also indicate what kind of business it is, where in Blink all the pins are the same and you need to click each to find out what it is. Even then not always it's clear, since Blink only displays names, while BTC Map tells you type of the merchant, and very often shows you working hours, phone numbers, website, social links, etc. ## Excellent community tools BTC Map is focusing providing tools for communities to maintain their merchants map. [Each community has it's own page](https://btcmap.org/communities) with own links to community website or socials, displays a list of all the merchants, shows community stats, displays merchants that were not verified for a long time, and more. It even allows to "boost" merchants to make them more visible on the map and on the list. It's perfect tooling both for communities and businesses onboarding merchants to their software.  ## Easy integration & configuration Integrating BTC Map on your website or app is easy. It's just [a few lines of code of iframe](https://arc.net/l/quote/vrdudfnn) to embed the map, but you can also use [BTC Map API](https://arc.net/l/quote/sybkpvcu) for more custom integration. Do you to display, eg. you can display only merchants from your community? No problem, you can do that. Since it's all open source, you can configure it in many ways that will suit your needs. ## Kudos I'd like to thank projects that understood all above and integrated BTC Map already. Those are Coinos, Wallet of Satoshi, Pouch, Bolt Card, BitLocal, Fedi, Decouvre Bitcoin, Osmo, Bitcoin Rocks!, Lipa, Spirit of Satoshi, Blockstream, Satlantis, Aqua Wallet and Adopting Bitcoin ## Encouragement & an offer I'll end that with encouragement to projects that use their own maps, but haven't embraced BTC Map yet. Those are Blink, Bitcoin Jungle, Plan B, Osmo, Athena, Orange Pill App, Inbitcoin (I probably missed some, tag them!). You are doing great work, but let's join forces and paint the world orange together! From here I would like to offer help in tagging your merchants on BTC Map. Just reach me out, and me and other supertaggers will do the work. Let the sats flow! originally posted at https://stacker.news/items/888088

@ 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/888083

@ c4b5369a:b812dbd6

As promised in my last article: nostr:naddr1qvzqqqr4gupzp394x6dfmvn69cduj7e9l2jgvtvle7n5w5rtrunjlr6tx6up9k7kqq2k6ernff9hw3tyd3y453rdtph5uvm6942kzuw08y0 In this one we will dive into how exactly an unidirectional payments channel powered ecash mint system would be implemented, using the tech available today! So if you haven't read that article yet, give it a read! I first intended to write a longwinded article, explaining each part of the system. But then I realized that I would need some visualization to get the message across in a more digestable way. This lead me to create a slide deck, and as I started to design the slides it became more and more clear that the information is easier shown with visualizations, than written down. I will try to give a summary as best as I can in this article, but I urge you, to please go visit the slide deck too, for the best experience: ----------- ### [TAKE ME TO THE SLIDE DECK!](https://uni-chan.gandlaf.com/) ----------- ### Intro In this article we will go over how we can build unidirectional payment channels on Bitcoin. Then we will take a look into how Cashu ecash mints work, and how we can use unidirectional payment channels to change the dynamics between ecash users and the mint. Before we start, let me also give credits to nostr:npub1htnhsay5dmq3r72tukdw72pduzfdcja0yylcajuvnc2uklkhxp8qnz3qac for comming up with the idea, to nostr:npub148jz5r9xujcjpqygk69yl4jqwjqmzgrqly26plktfjy8g4t7xaysj9xhgp for providing an idea for non-expiring unidirectional channels, and nostr:npub1yrnuj56rnen08zp2h9h7p74ghgjx6ma39spmpj6w9hzxywutevsst7k5cx unconference for hosting an event where these ideas could be discussed and flourish. ### Building unidirectional payment channels If you've read the previous article, you already know what unidirectional payment channels are. There are actually a coupple different ways to implement them, but they all do have a few things in common: 1. The `sender` can only send 2. The `Receiver` can only receive 3. They are VERY simple Way simpler than the duplex channels like we are using in the lightning network today, at least. Of course, duplex channels are being deployed on LN for a reason. They are very versatile and don't have these annoying limitations that the unidirectional payment channels have. They do however have a few drawbacks: 1. Peers have liveness requirements (or they might forfeit their funds) 2. Peers must backup their state after each transaction (if they don't they might forfeit their funds) 3. It is a pretty complex system This article is not meant to discredit duplex channels. I think they are great. I just also think that in some use-cases, their requirements are too high and the system too complex. But anyway, let's see what kind of channels we can build! #### Spillman/CLTV-Channel The Spillman channel idea has been around for a long time. It's even explained in Tadge Dryjas [Presentation](https://www.youtube.com/watch?v=Hzv9WuqIzA0&t=1969s) on Payment channels and the lightning network from back in the day. I compiled a list of some of the most important propperties of them in the slide below:  Great! Now that we know their properties, let's take a look at how we can create such a channel ([Slides](https://uni-chan.gandlaf.com/#/11)):  We start out by the `sender` creating a `funding TX`. The `sender` doesn't broadcast the transaction though. If he does, he might get locked into a multisig with the `receiver` without an unilateral exit path. Instead the `sender` also creates a `refund TX` spending the outputs of the yet unsigned `funding TX`. The `refund TX` is timelocked, and can only be broadcast after 1 month. Both `sender` and `receiver` can sign this `refund TX` without any risks. Once `sender` receives the signed `refund TX`, he can broadcast the `funding TX` and open the channel. The `sender` can now update the channel state, by pre-signing update transactions and sending them over to the `receiver`. Being a one-way channel, this can be done in a single message. It is very simple. There is no need for invalidating old states, since the `sender` does not hold any signed `update TXs` it is impossible for the `sender` to broadcast an old state. The `receiver` only cares about the latest state anyways, since that is the state where he gets the most money. He can basically delete any old states. The only thing the `receiver` needs to make sure of, is broadcasting the latest `update TX` before the `refund TX's` timelock expires. Otherwise, the `sender` might take the whole channel balance back to himself. This seems to be already a pretty useful construct, due to its simplicity. But we can make it even more simple!  This setup works basically the same way as the previous one, but instead of having a refund transaction, we build the `timelock` spend path directly into the `funding TX` This allows the `sender` to have an unilateral exit right from the start, and he can broadcast the `funding TX` without communicating with the `receiver`. In the worst case, the receiver rejects the channel, and the sender can get his money back after the timelock on the output has expired. Everything else basically works in the same way as in the example above. The beauty about this channel construct is in its simplicity. The drawbacks are obvious, but they do offer some nice properties that might be useful in certain cases.  One of the major drawbacks of the `Spillman-style channels` (apart from being unidirectional) is that they expire. This expiry comes with the neat property that neither of the party has to watch the chain for channel closures, and the `sender` can operate the channel with zero additional state, apart from his private keys. But they do expire. And this can make them quite inflexible. It might work in some contexts, but not so much in others, where time needs to be more flexible. This is where `Roose-Childs triggered channels` come into play. #### Roose-Childs triggered channel (I gave it that name, named after nostr:npub148jz5r9xujcjpqygk69yl4jqwjqmzgrqly26plktfjy8g4t7xaysj9xhgp and nostr:npub1htnhsay5dmq3r72tukdw72pduzfdcja0yylcajuvnc2uklkhxp8qnz3qac . If someone knows if this idea has been around before under a different name, please let us know!) `Roose-Childs triggered channels` were an idea developed by Steven and Luke at the nostr:npub1yrnuj56rnen08zp2h9h7p74ghgjx6ma39spmpj6w9hzxywutevsst7k5cx unconference. They essentially remove the channel expiry limitation in return for introducing the need for the `sender` to create a channel backup at the time of channel creation, and for the `receiver` the need to watch the chain for trigger transactions closing the channel.  They also allow for splicing funds, which can be important for a channel without expiry, allowing the `sender` to top-up liquidity once it runs out, or for the `receiver` taking out liquidity from the channel to deploy the funds elsewhere. Now, let's see how we can build them!  The `funding TX` actually looks the same as in the first example, and similarly it gets created, but not signed by the `sender`. Then, sender and receiver both sign the `trigger TX`. The `trigger TX` is at the heart of this scheme. It allows both `sender` and `receiver` to unilaterally exit the channel by broadcasting it (more on that in a bit). Once the `trigger TX` is signed and returned to the `sender`, the sender can confidently sign and boradcast the `funding TX` and open the channel. The `trigger TX` remains off-chain though. Now, to update the channel, the `sender` can pre-sign transactions in similar fashion to the examples above, but this time, spending the outputs of the unbroadcasted `trigger TX`. This way, both parties can exit the channel at any time. If the `receiver` wants to exit, he simply boradcasts the `trigger TX` and immediately spends its outputs using the latest `update TX`. If the `sender` wants to exit he will broadcast the `trigger TX` and basically force the `receivers` hand. Either, the `receiver` will broadcast the latest `update TX`, or the `sender` will be able to claim the entire channel balance after the timelock expired.  We can also simplify the `receiver's` exit path, by the `sender` pre-signing an additional transaction `R exit TX` for each update. this way, the `receiver` only needs to broadcast one transaction instead of two.  As we've mentioned before, there are some different trade-offs for `Roose-Childs triggered channels`. We introduce some minimal state and liveness requirements, but gain more flexibility.  #### Ecash to fill in the gaps (I will assume that the reader knows how ecash mints work. If not, please go check the [slides](https://uni-chan.gandlaf.com/#/43) where I go through an explanation) Essentially, we are trying to get a lightning like experience, without all the lightning complexities and requirements. One big issue with ecash, is that it is fully custodial. If we can offset that risk by holding most of the funds in a self custodial channel, we can have a reasonable trade-off between usability and self custody.  In a system like that, we would essentially turn the banking model onto its head. Where in a traditional bank, the majority of the funds are held in the banks custody, and the user only withdraws into his custody what he needs to transact, in our model the user would hold most funds in his own custody.  If you ask me, this approach makes way more sense. Instead of a custodian, we have turned the "bank" into a service provider. Let's take a look at how it would work in a more practical sense:  The `ecash user` would open an unidirectional payment channel to the `mint`, using one of his on-chain UTXOs. This allows him then to commit incrementally funds into the mints custody, only the amounts for his transactional needs. The mint offers connectivity to the lightning network an handles state and liveness as a service provider. The `ecash user`, can remain offline at all times, and his channel funds will always be safe. The mint can only ever claim the balance in the channel via the `update TXs`. The `mint` can of course still decide to no longer redeem any ecash, at which point they would have basically stolen the `ecash user's` transactional balance. At that point, it would probably be best for the `ecash user` to close his channel, and no longer interact or trust this `mint`. Here are some of the most important points of this system summarized:  And that is basically it! I hope you enjoyed this breakdown of Unidirectional payment channel enabled Ecash mints! If you did, consider leaving me a zap. Also do let me know if this type of breakdown helps you understand a new topic well. I am considering doing similar breakdowns on other systems, such as ARK, Lightning or Statechains, if there is a lot of interest, and it helps people, I'll do it! Pleas also let me know what you think about the `unidirectional channel - ecash mint` idea in the comments. It's kind of a new idea, an it probably has flaws, or things that we haven't thought about yet. I'd love to discuss it with you! I'll leave you with this final slide:  Cheers, Gandlaf

@ 89ccea93:df4e00b7

To whom it may concern, I'm beginning to realize that the monero users I interact with on #nostr are NOT on stacker news. Okay, fair enough. So I'm putting out the call for any monero technical users to write in ~monero territory on stacker news. Currently the cost to post is 100 sats. I as the owner of the territory will zap new posts 1000 sats as a thank you for joining stacker news to contribute to my nascent territory. This aligns with SN' interests of growth, and my interests as a territory owner so I'm not forced to archive it at the end of the month due to inactivity. Cheers! Expatriotic (almost signed off with my real name lol, NICE TRY FEDS!) originally posted at https://stacker.news/items/888012

@ 2e8970de:63345c7a

Hi there, wanted to share some inspiration For a few months now I have been following Tyron Shi. He makes absolutely gorgeous moody photography    Also really cinematic video  It has been a huge inspiration for me since normally I'm not that much of a street photographer and don't deviate my color grading too much from natural. Next time I'm on vacation to a bigger city I will try my hand at an album inspired by this. So, if you like it, give this genius a follow: https://tyronshi.com/ https://x.com/tyron_shi originally posted at https://stacker.news/items/887632

@ 5d4b6c8d:8a1c1ee3

Here are today's picks (there are a ton of them today) 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. For a hypothetical 1k-ish wager on each match, distribute your sats as follows: | Outcome 1 | Outcome 2 | Outcome 3 | Bet 1 | Bet 2 | Bet 3 | |--------------|-------------|--------------|-------|-------|-------| | Torino| AC Milan| Draw | 269| 476| 278| | Inter Milan| Genoa| Draw | 765| 71| 156| | Como| Napoli| Draw | 256| 464| 294| | Cagliari| Juventus| Draw | 213| 556| 267| | Balogna| AC Milan| Draw | 348| 407| 303| | Valencia| Atletico Madrid| Draw | 208| 550| 270| | Sevilla| Real Mallorca| Draw | 464| 253| 313| | Real Sociedad| Leganes| Draw | 636| 133| 267| | Real Madrid| Girona| Draw | 760| 105| 167| | Las Palmas| Barcelona| Draw | 105| 750| 164| | RB Leipzig| Heidenheim| Draw | 688| 143| 196| | FC Bayern| Eintracht Frankfurt| Draw | 786| 91| 133| | Dortmund| Union Berlin| Draw | 621| 182| 231| | Arsenal| West Ham| Draw | 763| 77| 167| | Aston Villa| Chelsea| Draw | 364| 392| 266| | Chelsea| Southampton| Draw | 818| 67| 143| | Everton| Man United| Draw | 333| 381| 303| | Ipswich| Tottenham| Draw | 286| 476| 256| | Liverpool| Newcastle| Draw | 652| 161| 217| | Man City| Liverpool| Draw | 348| 421| 256| | Man United| Ipswich| Draw | 636| 167| 227| | Newcastle| Nottingham Forest| Draw | 541| 235| 250| | Tottenham| Man City| Draw | 222| 594| 222| | Nottingham Forest| Arsenal| Draw | 200| 579| 244| I'll be curious to see how @Coinsreporter does with his modified RBOA. On the most recently completed set of RBOA, I made 6k sats on 43k wagered, so it was a nice bounce back. I still haven't precisely identified where the threshold is, but it might be worth skipping any of these with a "time weight multiplier" lower than 90. ---------- A note of caution about Freebitcoin: they recorded the wrong outcome for last week's Bills vs Ravens game and as of yet have not corrected it. I recall one other instance of something similar happening, so proceed with caution. This RBOA strategy is largely immune from that problem, but be aware of it when just betting on one outcome. originally posted at https://stacker.news/items/887548

@ 5d4b6c8d:8a1c1ee3

After gorging on Valentine's leftovers (cc: @realBitcoinDog), I did stop eating or drinking pretty early in the afternoon. Then just as I was about to sit down for coffee this morning, I was informed that my wife was out of the soymilk she likes with her coffee. So, a little trip to the store prolonged the fast further. 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: TBD (19 dry) originally posted at https://stacker.news/items/887459

@ 2e8970de:63345c7a

  https://x.com/ChadNauseam/status/1890889465322786878 originally posted at https://stacker.news/items/887373

@ 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/880985/r/AG) are some of the items stackers recently spent and #zap #sats on. originally posted at https://stacker.news/items/887305

@ 42342239:1d80db24

Almost 150 years ago, the British newspaper editor William Thomas Stead wrote that "the editorial pen is a [sceptre of power](https://archive.org/details/GovernmentByJournalismWilliamThomasStead), compared with which the sceptre of many a monarch is but a gilded lath". He had begun to regard journalism as something more than just conveying information - **the journalist or editor could become a ruler.** Times had certainly changed compared to a few hundred years earlier. Before [Gutenberg's invention of the printing press](https://underorion.se/en/posts/gutenberg/), it was mainly the church that controlled the dissemination of information in Europe, but when Stead put pen to paper, this control had shifted to newspapers, schools, and universities. Eventually, technologies like radio and TV entered the scene, but the power dynamics remained asymmetrical - only a few could send information to the many. However, with the emergence of the internet, and especially with the spread of social media, a significant change followed. Instead of only a few being able to send information to the many, many could send to many. Almost anyone could now create their own newspaper, radio, or TV channel. **The power over information dissemination was decentralised.** [Ten years ago](https://www.di.se/ditv/rikets-affarer-medierna-ar-splittrade/), Roberta Alenius, who was then press secretary for Sweden's Prime Minister Fredrik Reinfeldt of the Moderate Party, shared her experiences with Social Democratic and Moderate Party internet activists on social media. She reported that social media played a significant role in how news "comes out" and is shaped, and that **journalism was now downstream of social media**. [Five years later](https://www.nato.int/cps/en/natohq/opinions_166392.htm), NATO's then-Secretary-General Jens Stoltenberg said that "NATO must be prepared for both conventional and hybrid threats: **from tanks to tweets**." This finally underscores the importance of social media. Elon Musk, who took over X (formerly Twitter) in 2022, has claimed that "it's absolutely fundamental and transformative that the people actually get to decide the news and narrative and what's important," and that [citizen journalism is the future](https://x.com/elonmusk/status/1870485116474278240). While his platform allows most expressions - for better or worse - the reach of messages is instead limited ("[freedom of speech does not mean freedom of reach](https://www.youtube.com/shorts/R9TuhTz0vmo) "). X has also opened its recommendation algorithm to the outside world by making it open-source. Although this is a welcome step, the fact remains that **it's impossible to know which code is actually used** and what adjustments are made by humans or algorithms. William Thomas Stead's "sceptre of power", which has wandered from the church to newspaper and TV editorial offices, and now to citizens according to Elon Musk, risks being transferred to algorithms' opaque methods? Instead of talking about "toxic algorithms" and TikTok bans, like the so many do today, we should ask ourselves more fundamental questions. What happens when algorithms are no longer objective (how can they ever be?), but instead become tools for shaping our reality? **Perhaps our greatest challenge today is not deciding who should govern the information landscape, but instead recognising that no one is up to the task** - not even well-ventilated computers.

@ 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/887243

@ deba271e:36005655

Buying groceries with bitcoin rocks! I have been using bitcoin to buy food and stuff in Uvita over the last two months and what a wonderful experience that has been. There are so many places that accept. I went to the local farmers market literally every time it was open (twice a week) to buy veggies, meat, spices, juice, coffee and even clothes. You pay with bitcoin at every stand, payment fully settled sometimes [under 1 second](nostr:note1fxew6skuhayt8v2tpdh907l5tqy0aqkyx8k4x9qpuvd00kj62xjs99d8sy). I used bitcoin definitely more than I used fiat.  *What is in the basket is what I bought with bitcoin* As is my nature (and nostr [job description](nostr:npub1m6azw8j5wanm6mvwa367anjkzhdnz7srkpl5tyf5kql8ydsq2e2sa7h78d)), I was complaining about the UX to the folks involved across multiple companies/groups here in Uvita, with some issues already fixed and some new features/ideas being worked on. Overall the people working on these projects are amazing. This was so much fun and I hope the folks don't hate me for giving them [feedback](nostr:naddr1qvzqqqr4gupzph46yu09gam8h4kcamr4am89v9wmx9aq8vrlgkgnfvp7wgmqq4j4qqxnzdenxvurgwpjxgmnqwf5wu65zl), [feedback](nostr:note12lxe9qjefyl4uqksx97q0lnq33tghe3fhxldzut0g2rfvpmln4psqj90qe), [feedback](nostr:note1ue96mtfdnpth0msqxxx6ead4w7farnt3h4aysk53rk8cw6gjurjqz6mlwx) - I always tried to make it as actionable as possible (also I'm hard to argue with when I'm right :P). My focus has always been on getting more merchants onboarded, getting more people to accept bitcoin, but after a couple weeks in Uvita I realized that at this point the problem here is the opposite. **People are not paying with bitcoin**. I talked to many of the sellers, asked them how many people pay, how often. And in reality it's fairly rare for them. In the restaurants they only have a couple times per day when someone pays with bitcoin. At the market only around 10% of people pay with bitcoin, while 95% of the sellers accept. That made me feel a bit sad and surprised. This is a buyer education problem, not a seller problem.  *Only a small portion of the folks in the picture will pay with bitcoin…* The word of mouth approach is (imo) a solid strategy to onboard merchants, but it doesn't work for ephemeral tourists. As an example consider a "family with young kids coming for 3 days". This family doesn't have many chances to receive word of mouth. They come from elsewhere, they don't make many connections or interactions with locals. Sidenote: Physical bitcoin office works like a charm! I would have not guessed that, but I witnessed it being the spot where people meet, where merchants come to ask questions, where new folks ask how to get onboarded. The Bitcoin Jungle team did an amazing job here. If you are starting a circular economy in some town and already have some office space - consider making it into a "Bitcoin Office" (even if your business isn't exactly bitcoin). It will bring you visitors, great friends, bitcoiners will come hang out, etc. #### Tourist education We can assume that in "touristy" areas the restaurants, markets and shops will be mainly visited by tourists, so the solution here is tourist education. Now think about the journey that tourists go through - they come to the area in a car, maybe stop for lunch/dinner and then they check in at their hotel/casa. The next day they go to the local grocery store/market to get supplies and then do touristy stuff - go surfing, beach, hike, drive somewhere, chill, pool, drinks, etc. The main touch points for where paying with bitcoin could be introduced are: - when entering the town, - at the restaurant, - at the place they check in (hotel, casa), - in the grocery store/market, - in whatever they use to find attractions, - the tour guides, drivers and other folks working in the tourism sector. Here are couple ideas to make the situation better: - **Printed brochure at merchants and hotels/casas:** a little printed brochure with the same content available at every merchant - so when someone asks about bitcoin, they can just hand this brochure to them. Doesn't need any technical background or price talk - literally "You can pay with bitcoin here. You need a bitcoin wallet, here's QR to get it. Then you need to get bitcoin, here are the options. Then just pay by scanning the QRs that sellers show you" when you tell them "pagar con bitcoin por favor". - **Billboard when entering Uvita:** There could be a nice billboard when entering Uvita saying something like "Pay with Bitcoin in Uvita! Welcome to Bitcoin Jungle" and maybe add a link to bitcoinjungle.app and WhatsApp number. - **A billboard at the market:** a nice printed billboard on the side of the market that shows QR for how to download BitcoinJungle wallet (and some US available wallet), how to get initial sats on it (e.g. ask a specific person at the market, install Strike…). - **Discounts:** One thing that always attracts an eye is seeing some discount. This could be e.g. included in the brochure - "5% discount when you pay with bitcoin", or "pay with bitcoin, get XYZ for free". Someone may suggest wording "paying with fiat = extra 5% fee", but just from a psychological standpoint that is imo less effective.  *And of course having bitcoin signs "SE ACEPTA AQUI" helps…* Good luck! nout Originally posted at https://stacker.news/items/887222/r/nout

@ 9f0bbd5b:779b33f6

The next time you see your doctor and get a blood draw (you are doing this every year, yes?) be sure to request that your testosterone levels be tested. Testosterone is measured as Ng/dL. Ng/dL stands for nanograms per deciliter, which is a unit of measurement used to express the concentration of substances, such as hormones, in the blood. It indicates how many nanograms of a substance are present in one deciliter of blood. Since the 1960s-70s (the first time data was collected on a large scale), average testosterone levels have been cut nearly in half. You can draw any number of conclusions, when you compare this with the state of our society.  [Source](https://testosteronedecline.com/testosterone-levels-100-years-ago/) Sedentary lifestyles, processed foods, lack of exercise, sunshine, and sex ... all these things contribute to the feminization of the men in our society. Studies have shown that higher testosterone results in better rational decision making. Currently, average testosterone levels are lower than they have ever been.  [Source](https://www.health.com/chart-of-testosterone-levels-by-age-8743223#toc-testosterone-levels-by-age) **How to raise testosterone:** - Eat real food (beef, veg, dairy, fruit) - Stop drinking soda, etc - Get sunshine - Get rid of your gut - Exercise regularly originally posted at https://stacker.news/items/887187

@ 9e69e420:d12360c2

Ukraine's President Volodymyr Zelensky called for an "army of Europe" to defend against Russian threats, emphasizing that the US may not continue its traditional support for Europe. Speaking at the Munich Security Conference, he warned against peace deals made without Ukraine's involvement. US Vice President JD Vance echoed this sentiment, urging Europe to enhance its defense efforts. Zelensky stated, "I really believe the time has come - the armed forces of Europe must be created." He highlighted changing dynamics in US-Europe relations and noted that "the old days are over" regarding American support. Despite discussions around NATO, Zelensky stated he wouldn't rule out NATO membership for Ukraine.

@ 5d4b6c8d:8a1c1ee3

"Admit it. Sometimes you just need a big strong man." -Xander Harris Buffy fans should appreciate that reference. It's one of my favorite lines to quote around the house, whenever my wife needs help opening jars. Today, I said it to my daughter when she tried to open the orange juice herself, which earned a side-eye from the wife. It also led me to think about a possible research hypothesis. ## Idea I've heard that grip strength has been declining in men, to the point where there's barely a difference anymore between men and women. Is it possible that something as seemingly trivial as not being any more able to open jars, is reducing the rate of relationship formation? This was one area where men have historically been able to clearly demonstrate some value. ## Empirical difficulties I have no idea what the data looks like on either side of this question (grip strength or relationship formation), so I can't say much about specific data problems. However, there is definitely going to be an issue with "the dreaded third thing". In particular, I'm concerned with how to isolate the impact of grip strength decline from other effects of testosterone decline. Ideally, we'd be able to do a longitudinal study of men, where their grip strengths and testosterone levels are recorded, as well as their relationship status over time. Since there's no chance of doing that study, the best hope would be to put together some population level numbers over time and see if relationship formation rates still have a correlation with grip strength, after controlling for average testosterone levels. ----- I hope you enjoyed this half-baked idea. I mentioned to @denlillaapan that it might be fun to share ideas like this on SN. In all likelihood, no one will ever take these ideas any further, but they still might prompt fun discussions. originally posted at https://stacker.news/items/886699

@ 5d4b6c8d:8a1c1ee3

Much to @realBitcoinDog's chagrin, we did eat out for Valentine's Day. Well, actually, we got some take out, but it definitely wasn't very healthy. However, we did eat fairly early, so it didn't mess up my fasting. ## Reflections Even though I had been regularly fasting before February, this Fast February exercise has improved the habit and led to some noticeable outcomes. The first couple of days, I was kind of snacky. Because of the fiscal fast element of Fast February, I had to snack on whatever was around the house already. That turned out to be the "wrong" type of applesauce that our daughter refuses to eat. After those first few days, though, I really haven't been very snacky. In fact, my general appetite is noticeably lower. The most pronounced non-appetite related effect has been more vivid dreams (or at least more memorable dreams). On the con side, I have felt a little stiffer and have been stretching more often to alleviate muscle tension. ## 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: TBD (16 dry) originally posted at https://stacker.news/items/886640

@ 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/886437

@ fd208ee8:0fd927c1

E-cash are coupons or tokens for Bitcoin, or Bitcoin debt notes that the mint issues. The e-cash states, essentially, "IoU 2900 sats". They're redeemable for Bitcoin on Lightning (hard money), and therefore can be used as cash (softer money), so long as the mint has a good reputation. That means that they're less fungible than Lightning because the e-cash from one mint can be more or less valuable than the e-cash from another. If a mint is buggy, offline, or disappears, then the e-cash is unreedemable. It also means that e-cash is more anonymous than Lightning, and that the sender and receiver's wallets don't need to be online, to transact. Nutzaps now add the possibility of parking transactions one level farther out, on a relay. The same relays that cannot keep npub profiles and follow lists consistent will now do monetary transactions. What we then have is * a **transaction on a relay** that triggers * a **transaction on a mint** that triggers * a **transaction on Lightning** that triggers * a **transaction on Bitcoin**. Which means that every relay that stores the nuts is part of a wildcat banking system. Which is fine, but relay operators should consider whether they wish to carry the associated risks and liabilities. They should also be aware that they should implement the appropriate features in their relay, such as expiration tags (nuts rot after 2 weeks), and to make sure that only expired nuts are deleted. There will be plenty of specialized relays for this, so don't feel pressured to join in, and research the topic carefully, for yourself. https://github.com/nostr-protocol/nips/blob/master/60.md https://github.com/nostr-protocol/nips/blob/master/61.md

@ 57d1a264:69f1fee1

The lead dev @gandlaf21 from [brrr.gandlaf.com](https://brrr.gandlaf.com) (https://github.com/gandlafbtc/cashu-brrr) reached out to me with an idea: a design contest for ecash paper note templates. Brrr is a paper note ecash generator that lets you easily create and print ecash in the form of bank-style paper notes. We're thinking of putting up 150k sats as a prize pool to make it fun. I think this could be a fun opportunity for the Bitcoin Design Community. I’m happy to lead it, but I’d love to get your thoughts. Here are a couple of directions I think it could take: Could this fit into the next Designathon? Maybe we create a dedicated track for it with a side bounty or prize for the best note design. Or should we keep it separate and run it as a standalone contest, promoting it as a unique, one-off event? What do you guys think? originally posted at https://stacker.news/items/886379

@ 57d1a264:69f1fee1

 🧐 Who is the main character of 100,000 sats?! 📋 Checklist I hope BitcoinSocialLayer will be well recognized when conducting BSL activities at home and abroad. ✅ Photo 1 is a list of participating organizations for the Chiang Mai conference sats 'n' facts. When viewed by a third party, BSL is an abbreviation, so additional explanation is needed, but the spelling BSL does not come to mind. ✅ It may be helpful to refer to the sponsor lists on the pages of other Bitcoin conferences or meetups, such as the Tokyo Conference in Photo 2, to help you write your draft. * In addition to AI, Photoshop, and Illustrator, you can also use PPT or images in PNG format. - Please create a logo that fits the name Bitcoin Social Layer: - Key words: Bitcoin, expert, service, South Korea - Prize: 100,000 sat - Submission: bitcoinsociallayer@gmail.com - Logo high-resolution original file, logo description - Period: until midnight on February 28th. - All legal and commercial rights of the winning logo will be transferred to BSL (copyright transfer agreement will be signed and trademark registration will be processed) - Plagiarized and other copyright infringing logos may be disqualified. - Depending on the results, there may be no winner. In this case, we will continue to use the existing logo. Source: https://x.com/BTCSocialLayer/status/1888887772083335519  originally posted at https://stacker.news/items/886369

@ 0fa80bd3:ea7325de

#intro The Russian state made me a Bitcoiner. In 1991, it devalued my grandmother's hard-earned savings. She worked tirelessly in the kitchen of a dining car on the Moscow–Warsaw route. Everything she had saved for my sister and me to attend university vanished overnight. This story is similar to what many experienced, including Wences Casares. The pain and injustice of that time became my first lessons about the fragility of systems and the value of genuine, incorruptible assets, forever changing my perception of money and my trust in government promises. In 2014, I was living in Moscow, running a trading business, and frequently traveling to China. One day, I learned about the Cypriot banking crisis and the possibility of moving money through some strange thing called Bitcoin. At the time, I didn’t give it much thought. Returning to the idea six months later, as a business-oriented geek, I eagerly began studying the topic and soon dove into it seriously. I spent half a year reading articles on a local online journal, BitNovosti, actively participating in discussions, and eventually joined the editorial team as a translator. That’s how I learned about whitepapers, decentralization, mining, cryptographic keys, and colored coins. About Satoshi Nakamoto, Silk Road, Mt. Gox, and BitcoinTalk. Over time, I befriended the journal’s owner and, leveraging my management experience, later became an editor. I was drawn to the crypto-anarchist stance and commitment to decentralization principles. We wrote about the economic, historical, and social preconditions for Bitcoin’s emergence, and it was during this time that I fully embraced the idea. It got to the point where I sold my apartment and, during the market's downturn, bought 50 bitcoins, just after the peak price of $1,200 per coin. That marked the beginning of my first crypto winter. As an editor, I organized workflows, managed translators, developed a YouTube channel, and attended conferences in Russia and Ukraine. That’s how I learned about Wences Casares and even wrote a piece about him. I also met Mikhail Chobanyan (Ukrainian exchange Kuna), Alexander Ivanov (Waves project), Konstantin Lomashuk (Lido project), and, of course, Vitalik Buterin. It was a time of complete immersion, 24/7, and boundless hope. After moving to the United States, I expected the industry to grow rapidly, attended events, but the introduction of BitLicense froze the industry for eight years. By 2017, it became clear that the industry was shifting toward gambling and creating tokens for the sake of tokens. I dismissed this idea as unsustainable. Then came a new crypto spring with the hype around beautiful NFTs – CryptoPunks and apes. I made another attempt – we worked on a series called Digital Nomad Country Club, aimed at creating a global project. The proceeds from selling images were intended to fund the development of business tools for people worldwide. However, internal disagreements within the team prevented us from completing the project. With Trump’s arrival in 2025, hope was reignited. I decided that it was time to create a project that society desperately needed. As someone passionate about history, I understood that destroying what exists was not the solution, but leaving everything as it was also felt unacceptable. You can’t destroy the system, as the fiery crypto-anarchist voices claimed. With an analytical mindset (IQ 130) and a deep understanding of the freest societies, I realized what was missing—not only in Russia or the United States but globally—a Bitcoin-native system for tracking debts and financial interactions. This could return control of money to ordinary people and create horizontal connections parallel to state systems. My goal was to create, if not a Bitcoin killer app, then at least to lay its foundation. At the inauguration event in New York, I rediscovered the Nostr project. I realized it was not only technologically simple and already quite popular but also perfectly aligned with my vision. For the past month and a half, using insights and experience gained since 2014, I’ve been working full-time on this project.

@ 9e69e420:d12360c2

Vice President J.D. Vance addressed the Munich Security Conference, criticizing European leaders for undermining free speech and traditional values. He claimed that the biggest threat to Europe is not from external enemies but from internal challenges. Vance condemned the arrest of a British man for praying near an abortion clinic and accused European politicians of censorship. He urged leaders to combat illegal immigration and questioned their democratic practices. “There is a new sheriff in town,” he said, referring to President Trump. Vance's remarks were unexpected, as many anticipated discussions on security or Ukraine. His speech emphasized the need for Europe to share the defense burden to ensure stability and security.

@ 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. It is valentine's so let's get all gooey and soft, let's feel good and loved up. If the world was ending, I'd wanna be next to you. https://youtu.be/kPa7bsKwL-c?si=XbAaVfCHLZw6_0n6 Talk Music. Share Tracks. Zap Sats. Let's go! originally posted at https://stacker.news/items/885888

@ 9e69e420:d12360c2

A Russian drone attack has struck the radiation shelter at Chernobyl, according to Ukrainian President Volodymyr Zelensky. The strike caused a fire, but it has since been extinguished, and radiation levels remain stable. The International Atomic Energy Agency (IAEA) confirmed that no casualties occurred and that monitoring continues. Rafael Mariano Grossi, IAEA's director general, emphasized the need for caution. Chernobyl, site of the 1986 nuclear disaster, contains a protective shield costing $1.6 billion. Disaster prevention remains a priority as the conflict unfolds. The incident occurred shortly before the meeting of world powers at the Munich Security Conference in Germany.

@ 09fbf8f3:fa3d60f0

> 功能很简单的网站，无广告、无任何付费项目，漫画全部免费。 荤素搭配。 唯一的缺点就是有点慢，看了下网站使用的是cloudflare网站加速，国内效果差了一点，加个🪜就好了。 关键词mycomic 官网：[https://mycomic.com](https://mycomic.com) 

@ 57d1a264:69f1fee1

Organized by Figma, Config is happening May 6-8 in San Francisco—here's a first look at our 2025 lineup.  [Register for Config 2025](https://config.figma.com/san-francisco/register/) At Config 2025, we’re bringing together the designers and builders shaping tech’s next chapter. They’ll share a vision for building tools and experiences that are human-centered, intentional, and meet the needs of an accelerating future.  [Register now](https://config.figma.com/san-francisco/register/) to guarantee your spot in San Francisco! Virtual registration is also open, and always free. Join us in San Francisco or virtually. ### $799 - In person Moscone Center, San Francisco, California Purchasing an in-person ticket will also give you virtual access to our livestreams. [Select in person](https://reg.config.figma.com/flow/figma/config2025/in-person/login) ### $0 Virtual Livestream Online Free - Limit one ticket per attendee. [Select virtual](https://reg.config.figma.com/flow/figma/config2025/virtual/login) - - - Or [keep reading](https://www.figma.com/blog/meet-the-makers-defining-techs-next-chapter/?utm_campaign=021325+-+Invite&utm_content=021325+-+Invite) for the full Config 2025 sneak peek originally posted at https://stacker.news/items/885616

@ 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/885591

@ 57d1a264:69f1fee1

 ### a practical intro to contributing to FOSS for product people, and other non-devs So you want to contribute to FOSS, but don’t know where to start. There are many paths to FOSS, but you must find your own. Here’s some advice based on personal experience to help you get started. ### 0\. Find your motivation FOSS requires a lot of giving, and better aligns with those that are missionaries, as opposed to the mercenaries. Perhaps you are unfulfilled in your fiat job, maybe you are currently unemployed, or perhaps you are excited about a particular bitcoin project. Why you’re exploring contributing to FOSS, is a question that only you can answer.  Are you a missionary? ### 1\. Discover what excites you So you’ve found motivation and have a list of various FOSS projects you could contribute to. This is the equivalent of the “I need a job” stage and you’re figuring out where to apply. It’s time to narrow it down. What are you excited about? A multi-year pilgrimage of learning how to contribute to Bitcoin Core? A lightning wallet, perhaps? Free speech Nostr? A hardware signing device? Or maybe finding a FOSS projects that is not “Bitcoin” in name, but happens to support Bitcoin, and Lightning. A great first step is to take some time and explore the Bitcoin Design Community ([https://bitcoin.design/](https://bitcoin.design/)) to discover FOSS projects.  Are you excited anon? ### 2\. Identify the skills you have or want to develop Chances are that if you follow the Bitcoin Product Community, you’re skills are in Product Management, Product Marketing, and/or Project Management. But contributing to a bitcoin project requires contributors with skills of many backgrounds such as marketing, documentation, community building, and more. What’s important to know is that most FOSS teams start with a motivated developer, who then may attract other devs. But many of them may not advertise that they need non-developer help such as a PM. Therein lies the opportunity for you as an eager bitcoin contributor. See what the needs of a project are and see if you can fill in those gaps with your skills. It may be as simple as coordinating meetings for the team. But doing the “dirty work”, or the work no one else wants to do, is exactly the way you can make an immediate impact to a FOSS project. In fact, this is why members of the Bitcoin Product Community affectionately refer to product managers as “[janitors](https://medium.com/all-things-product-management/product-manager-you-are-664d83ee702e)”! ### 3\. Make a list of projects Now that you have narrowed down your FOSS search, it is time to start building a list of, and evaluating various FOSS products. Some questions you can ask yourself: Is the project active? Is it a new project? How many team members are there? How many are devs? Is there already a PM? Is there a need for multiple PMs? Is there designer participation? What is the pace of development? Is there enough development activity for this to satisfy your want to contribute? Is there opportunity for a PM? Github is the defacto standard for FOSS products. Check the activity. Read up on issues. See who is contributing PRs, and creating issues. Check if there is a Github Project instance. It’s OK, and best for you to check out out multiple FOSS projects concurrently to see which team is the best fit for both parties. ### 4\. Use the thing(s)! Another thing you can do to help you choose a project is to use the thing! Download the OS. Run the software. Use it. As you’re interacting with the product, some things you can ask yourself are: What do you love about the product? What can be improved? Are there bugs? Jot down your notes. Take screenshots. Do screen recordings. Document your experience. Create a video onboarding walkthrough, or a feature tutorial. What you are actually doing is documentation and this will be useful for the project, even if you don’t decide to actively contribute. As you use the thing, take note of how you’re reacting to it. Are you getting more or less excited? Are you more or less confident in contributing to the project? ### 5\. Find out where the team works Another factor to consider is to figure out where the team works. By now you have already explored their github to collect your FOSS intelligence. Now check nostr, twitter, telegram, or whatever other comms tools the team might be using. Some teams may have calls, and call recordings. Consider listening in to a recording, and/or joining a call to check the team dynamics. As you do, assess whether you might be a good culture fit. Also see where there might be some gaps in their workflow that you can help improve. ### 6\. Start small Once you found a project that interests and excites you enough. It’s time to roll up your sleeves and get involved by starting small. One easy place to start is to go through the github issues list. Some examples of issues in dev heavy teams are e extremely technical bug reports. For FOSS products with an active user base, there might be “customer” centric feature requests. Start by logging the bug(s) you found. Examine issues, and fill in the blanks if there are unclearly defined reports & requests. You don’t have to ask for permission to contribute. That said, evaluate team dynamics and who owns what role so you are not stepping on anyone’s toes. You are there to help. Also take note of how your help is received. It may take time for you to build up your credibility. Don’t throw in the towel on the first week. Keep finding ways to add value. ### 7\. Show up consistently Keep contributing in small things day in and day out. As you do so, communicate with the team to ramp up your learning, and also start building rapport, and your reputation. You may not have time or opportunity to contribute full-time. With the state of asynchronous communication tools in 2023, you can flexibly contribute when you have time. An exception to the asynchronous communication may be team meetings. As you continue to show up consistently, you will build up your FOSS proof-of-work, and reputation. This will show FOSS devs, and contributors that you bring value. ### 8\. Find and meet the “customer” Find, and interact with the project’s users a.k.a “customers”. What do they care about? What are their pain points? What needs are customers using the product for? Become the “voice of the customer” to the dev heavy team. Is there a conference where your team is presenting, and customers present? These are invaluable opportunities to observe the customer’s behavior, and also to help answer questions, and troubleshoot on the spot. ### 9\. Increase your involvement After some time starting small and working on bugs, you may eventually find yourself submitting feature requests. Maybe there is an opportunity to create user flows, or mockups. As you consistently contribute, continue seeking more responsibility. Maybe you offer to facilitate and lead the next team call. Maybe you try creating a roadmap and backlog from scratch. Maybe you host a product & design thinking session. Maybe you will level up and learn how to check out a dev’s PR in a yet-to-released branch. No matter what you do, be sure to always bring value to the project.  Testing an unreleased Damus branch checked out on XCode ### 10\. Prune, Commit, Repeat Congratulations! By now you’ve been doing a “trial run” with several projects. It’s time to focus and choose one(s) that you can commit to. As you contribute to the project on an ongoing basis, continuously reevaluate if there is opportunity for you to increase your contributions. If you feel that you’ve maxed that out, it may be time to look for a different FOSS product to contribute to. Perhaps a complementary product to your initial one. As you embark on this journey, it can be exhilarating at times and in other times thankless. To find a community of peers, and perhaps a mentor check in with the Bitcoin Product Community [Discord](https://discord.gg/Ztvwn8fycA), and introduce yourself. The beauty of open source is people are willing to help FOSS products, and to answer your questions. [https://youtu.be/ZUgQPR6ecuo](https://youtu.be/ZUgQPR6ecuo)“FOSS is the way” - Rockstar dev, @ Advancing Bitcoin Conference London 2023. The author thanks Rockstar for inspiration, and guidance through my FOSS journey. As you continue to sweep the FOSS floors with your product [mop](https://medium.com/all-things-product-management/product-manager-you-are-664d83ee702e), remember that you are contributing to the mission that you believe in. You are working in the open, with even less authority than a PM at a company might have, and as a result leveling up. You build up your reputation in FOSS, and you show others your capabilities in the FOSS world (and also prospective employers, and co-founders) by doing. Hopefully this helps you get started. Reach out to [elsat on nostr](https://njump.me/npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5) if you have questions about the FOSS journey, and join the Bitcoin Product Community Discord. Posted on @YakiHonne by @elsat Source: https://yakihonne.com/article/nevent1qqswn2mdwcfscsvv8cfc8scmcfpy0urnf0xgh0dxrvav583y85mkryspz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzq96n3hp2vfmf6z2y8uvvxl97xk86kkalnqghx4p25lzl79c76a7yjfa8zs originally posted at https://stacker.news/items/885573

@ 57d1a264:69f1fee1

Volt Wallet is designed to make Bitcoin and Lightning transactions simple, secure, and accessible for users of all experience levels. With the increasing popularity of the Lightning Network, Volt Wallet provides an easy, user-friendly interface for sending and receiving payments while also incorporating educational elements, such as quizzes and tutorial videos, to promote a better understanding of Bitcoin and Lightning payments.                    - - - Source: https://www.behance.net/gallery/217868517/Volt-A-Bitcoin-Lighting-Wallet-for-beginners originally posted at https://stacker.news/items/885569

@ 9e69e420:d12360c2

Robert F. Kennedy Jr. has been confirmed as the next Secretary of Health and Human Services with a Senate vote of 52-48. Senator Mitch McConnell opposed the confirmation. Kennedy's nomination faced hurdles but gained support from the Senate Finance Committee. During the confirmation hearing, Senator Rand Paul criticized the oversimplification of vaccine discussions. He stated, "Discussion over vaccines is so oversimplified and dumbed down." Kennedy asserted his support for vaccines like measles and polio, promising not to discourage vaccinations as HHS Secretary. Previously, he switched from the Democratic Party to run as an independent and endorsed Trump

@ 89ccea93:df4e00b7

**[Original Post](https://expatriotic.me/grapheneos/)** ## Core Philosophy 1. **Privacy ≠ Optional**: Prevents mass data collection by design 2. **Security > Convenience**: Sacrifices "smart" features for exploit resistance 3. **Transparency**: Every line of code [auditable](https://github.com/GrapheneOS) 4. **Device Sanity**: Removes 2M+ lines of Google telemetry code 5. **Proactive Hardening**: Replaces reactive "vulnerability whack-a-mole" with systemic memory safety improvements. 73% of Android CVEs prevented via Scudo++ allocator and Rust integration. 6. **Hardware Paradox**: Uses Google Pixels *because* of their Titan M2 secure enclave (physically separate from main CPU, Verified Boot with user-defined root of trust, Firmware-level MAC randomization (prevents Wi-Fi tracking)). 7. **Support Superiority**: GrapheneOS support for Pixel phones is 2 years longer Google's. > *"We're eliminating entire vulnerability classes - not just patching holes."* ## **History** * Born in **2014** as **CopperheadOS** * **2016**: First Pixel support (Google's hardware + de-Googled OS) * Rebranded in **2019** after a developer split. Focuses exclusively on Pixel phones. * **2021**: **Scudo++** with quarantines (NSA-grade exploit mitigation) * **2023**: Full Rust integration (prevents buffer overflows in core OS) * **2023**: Controversial lead dev, Daniel Micay, stepped down but remains director * **2024**: Quantum-resistant encryption prototypes > *"Our Auditor app detects hardware tampering better than Apple's T2 chip."* ## **Installation** * **Minimum**: Pixel 4a * **Recommended**: Pixel 7a (5-year update guarantee) * **Backup data first**: unlocking bootloader wipes device ### **Beginners: Web Installer** 1. Enable OEM Unlock: `Settings → About → Tap Build Number 7x → Developer Options → OEM Unlocking` 2. Visit [grapheneos.org/install](https://grapheneos.org/install) 3. Connect phone → Follow prompts (20 minutes) ### **Advanced: CLI install** * Full CLI guide: [grapheneos.org/install/cli](https://grapheneos.org/install/cli) (8 minutes) >*"We're proving iPhones aren't the only secure option - just better marketed."* ### **Post-Install Checklist** [ ] Deny all "convenience" permissions [ ] Enable Sensors Off toggle [ ] Install Auditor app [ ] Sensors Killswitch: `Quick Settings → Toggle Off` [ ] Network Restrictions: ```markdown Settings → Network & Internet → Firewall - Enable per-connection MAC randomization - Block local network discovery ``` [ ] Auditor Validation: Daily automated checks against Google's hardware certs ## Setting up ### **Priority Sources** 1. **Accrescent** (Pre-installed) - Molly (Signal fork) - Aves Gallery (EXIF stripping) - AppVerifier (APK validation) 2. **Obtainium** ([GitHub](https://github.com/ImranR98/Obtainium)) ```markdown 1. Search "[App] GitHub releases" 2. Copy releases page URL 3. Paste into Obtainium → Auto-updates enabled ``` - *Example*: NewPipe → `https://github.com/TeamNewPipe/NewPipe/releases` 3. **Google Play** (Last Resort) - Use separate profile - Burner account: Fake name + **NO phone number** ## FOSS Apps * Accrescent - Privacy-focused app store * Aegis - 2FA authenticator * Amethyst - Nostr decentralized social client * AndBible - Offline Bible study * Antennapod - Podcast manager * AppVerifier - APK signature validation * Ashigaru - Bitcoin wallet with Ricochet * Aves Gallery - Gallery with EXIF stripping * Brave - Anti-fingerprinting browser * Easy Noise - Offline white noise generator * Easy Note - Minimalist notes * Envoy - Bitcoin wallet * IronFox - Hardened Firefox fork * KeePassDX - Offline password manager * Léon - URL tracking stripper * LocalSend - AirDrop alternative * Material Files - File manager * Molly - Signal fork with local encyption * Monero.com - Official Monero wallet * NetGuard - No-root firewall * NewPipe - YouTube client with SponsorBlock * Nextcloud - Self-hosted cloud suite * OpenKeychain - PGP encryption * Organic Maps - Offline navigation * Orbot - Tor proxy * Proton Drive - E2E encrypted storage * Proton Mail - Zero-access email * RedReader - Privacy-first Reddit client * Simple Calendar Pro - Telemetry-free calendar * Telegram FOSS - Decentralized messaging * Tor Browser - Onion-routed browsing * Twidere - Twitter/Fediverse client * Tuta - Encrypted email * Tuta Calendar - Encrypted calendar * Vanadium - Hardened Chromium * Zeus - Bitcoin Lightning node > _"Your phone is a corporate surveillance device that happens to make calls. GrapheneOS removes the spyware OS while keeping the secure hardware."_ ## **Silent.Link eSIM: Anonymous Connectivity** **No Phone Number Required** Visit [Silent.Link](https://silent.link) → Select data plus eSIM plan (with NO phone number). ```I've used this successfully in many countries. It even gives me unfettered and free internet in China. Be sure to pick the telecom company based on what they charge per GB of data. The difference can be 100x!``` ## Support the Project: - **Donate**: [grapheneos.org/donate](https://grapheneos.org/donate) - **Community**: [grapheneos.org/contact](https://grapheneos.org/contact) >*"GrapheneOS isn't about becoming a privacy expert overnight. It's about systematically removing corporate surveillance hooks - one app, one permission, one profile at a time."* ## Moar Halp * **[Side Of Burritos](https://www.youtube.com/playlist?list=PLHvdaysg3bMyYwJAcxbFUY9YqKKC0Dtrd)** * **[Hated One interview with GrapheneOS dev Gabe](https://www.youtube.com/watch?v=WkQ_OCzuLNg)** originally posted at https://stacker.news/items/884965