@ 6868de52:42418e63

自分が僕のことをなんで否定するのかよくわかんない 自分のことを高く評価してる。周囲の理解に努力してない けど、いつも気にしてる 自分の限界に気づくのが怖い？ 周りに理解されないことに価値を見出し、意図的に理解されないようにしてるんじゃないのか 周りに影響され、自分は変わっていくんです 変わらないもの。変わっちゃいけないもの。 変わっちゃいけないものは、学問への尊敬。これが生きる目的だってこと。 変わらないものは、美少女への嗜好、世界の全てへの優しさ、屁理屈の論理が好きなこと。 で、理解されたいのか。されるべきなのか。 されるべきとは？あーそうだよ、されたいしされるべきなんだ！ そっか、じゃあ理解したいのか。するべきなのか。 するべきだよ。ネットワーク的にも、心理的にも。 したくは、ないかな。その決定権は常に僕の手元にほしい。 関われる限界を知ることになるから。 自分のことは知らなくてもいい。制御できればいい。愛してるし。 でもこうやって心情を整理してるんだけどね。まー限界はありますよ。

@ c9badfea:610f861a

1. Install PocketPal (it's free and open source)
2. Launch the app, open the menu, and navigate to Models
3. Download one or more models (e.g. Phi, Llama, Qwen)
4. Once downloaded, tap Load to start chatting

ℹ️ Experiment with different models and their quantizations (Q4, Q6, Q8, etc.) to find the most suitable one

@ d61f3bc5:0da6ef4a

I remember the first gathering of Nostr devs two years ago in Costa Rica. We were all psyched because Nostr appeared to solve the problem of self-sovereign online identity and decentralized publishing. The protocol seemed well-suited for textual content, but it wasn't really designed to handle binary files, like images or video.

The Problem

When I publish a note that contains an image link, the note itself is resilient thanks to Nostr, but if the hosting service disappears or takes my image down, my note will be broken forever. We need a way to publish binary data without relying on a single hosting provider.

We were discussing how there really was no reliable solution to this problem even outside of Nostr. Peer-to-peer attempts like IPFS simply didn't work; they were hopelessly slow and unreliable in practice. Torrents worked for popular files like movies, but couldn't be relied on for general file hosting.

Awesome Blossom

A year later, I attended the Sovereign Engineering demo day in Madeira, organized by Pablo and Gigi. Many projects were presented over a three hour demo session that day, but one really stood out for me.

Introduced by hzrd149 and Stu Bowman, Blossom blew my mind because it showed how we can solve complex problems easily by simply relying on the fact that Nostr exists. Having an open user directory, with the corresponding social graph and web of trust is an incredible building block.

Since we can easily look up any user on Nostr and read their profile metadata, we can just get them to simply tell us where their files are stored. This, combined with hash-based addressing (borrowed from IPFS), is all we need to solve our problem.

How Blossom Works

The Blossom protocol (Blobs Stored Simply on Mediaservers) is formally defined in a series of BUDs (Blossom Upgrade Documents). Yes, Blossom is the most well-branded protocol in the history of protocols. Feel free to refer to the spec for details, but I will provide a high level explanation here.

The main idea behind Blossom can be summarized in three points:

1. Users specify which media server(s) they use via their public Blossom settings published on Nostr;
2. All files are uniquely addressable via hashes;
3. If an app fails to load a file from the original URL, it simply goes to get it from the server(s) specified in the user's Blossom settings.

Just like Nostr itself, the Blossom protocol is dead-simple and it works!

Let's use this image as an example:

If you look at the URL for this image, you will notice that it looks like this:

blossom.primal.net/c1aa63f983a44185d039092912bfb7f33adcf63ed3cae371ebe6905da5f688d0.jpg

All Blossom URLs follow this format:

[server]/[file-hash].[extension]

The file hash is important because it uniquely identifies the file in question. Apps can use it to verify that the file they received is exactly the file they requested. It also gives us the ability to reliably get the same file from a different server.

Nostr users declare which media server(s) they use by publishing their Blossom settings. If I store my files on Server A, and they get removed, I can simply upload them to Server B, update my public Blossom settings, and all Blossom-capable apps will be able to find them at the new location. All my existing notes will continue to display media content without any issues.

Blossom Mirroring

Let's face it, re-uploading files to another server after they got removed from the original server is not the best user experience. Most people wouldn't have the backups of all the files, and/or the desire to do this work.

This is where Blossom's mirroring feature comes handy. In addition to the primary media server, a Blossom user can set one one or more mirror servers. Under this setup, every time a file is uploaded to the primary server the Nostr app issues a mirror request to the primary server, directing it to copy the file to all the specified mirrors. This way there is always a copy of all content on multiple servers and in case the primary becomes unavailable, Blossom-capable apps will automatically start loading from the mirror.

Mirrors are really easy to setup (you can do it in two clicks in Primal) and this arrangement ensures robust media handling without any central points of failure. Note that you can use professional media hosting services side by side with self-hosted backup servers that anyone can run at home.

Using Blossom Within Primal

Blossom is natively integrated into the entire Primal stack and enabled by default. If you are using Primal 2.2 or later, you don't need to do anything to enable Blossom, all your media uploads are blossoming already.

To enhance user privacy, all Primal apps use the "/media" endpoint per BUD-05, which strips all metadata from uploaded files before they are saved and optionally mirrored to other Blossom servers, per user settings. You can use any Blossom server as your primary media server in Primal, as well as setup any number of mirrors:

## Conclusion

For such a simple protocol, Blossom gives us three major benefits:

1. Verifiable authenticity. All Nostr notes are always signed by the note author. With Blossom, the signed note includes a unique hash for each referenced media file, making it impossible to falsify a media file and maliciously ascribe it to the note author.
2. File hosting redundancy. Having multiple live copies of referenced media files (via Blossom mirroring) greatly increases the resiliency of media content published on Nostr.
3. Censorship resistance. Blossom enables us to seamlessly switch media hosting providers in case of censorship.

Thanks for reading; and enjoy! 🌸

@ 6538925e:571e55c3

It’s been a little while since we released a major design update, so we’re really excited to get this new version of the app into your hands. Here’s a breakdown of all the main updates included in Fountain 1.2:

#### Library Design Update

• New content-type filters at the top of the page make it easier to navigate between podcasts and music in your library.

• Recently Played is now the default view in your library, so it’s easier to jump back into podcasts you’ve already started.

• The Music filter now makes it easier to find saved tracks and albums, and it also gives you a list of all the artists whose music you’ve saved.

• We’ve refreshed the design of the content cards to make it easier to see how much time is remaining on episodes you’ve already started.

#### Content Pages Design Update

• All of the different content pages have undergone an extensive redesign, including shows, episodes, artists, albums, tracks, clips and playlists

• We’ve replaced the tab layout we were using on the content pages with one scrollable page, making it easier to access features like chapters and tracklists

• We’ve sanitised the formatting of show notes too, and if there is no activity for a given episode, we now display the expanded show notes

#### Episode Summaries

Ever looked at a 4-hour Lex Fridman episode and wished you could just read a high-level summary? We certainly have, so we did something about it.

• Every episode page now has a Summary button above the show notes.

• Simply pay 500 sats to unlock a summary, or upgrade to Fountain Premium for $2.99/month to enjoy unlimited summaries.

• Summaries and transcripts now come as a bundle — two for the price of one!

• Thanks to major improvements, they’re now faster, cheaper, and more accurate than ever before.

#### Playback Improvements

We’ve completely rebuilt our audio engine from the ground up. Playback is now more robust and reliable — especially for music. Here are some of the key enhancements in Fountain 1.2:

• Tracks now load and play instantly when tapped.

• When playing a collection of tracks (e.g. from an artist, album, or playlist), you can now skip seamlessly between them.

• We’ve replaced the scrollable player page with full-screen modals to make it easier to access show notes, comments, transcripts, chapters, tracklists, and your queue.

• The new Smart Resume feature rewinds the episode by 5 seconds when you hit pause, so you don’t miss a beat.

• You can now skip forward or backward by 60 seconds for faster navigation through episodes.

Other Bug Fixes & Improvements

• Rebuilt payment stats for more complete and reliable transaction records.

• Refreshed the design of the Settings pages for better usability.

• Added new episode notification preferences in Settings.

• Fixed several playback issues that were causing crashes or freezes.

• Updated lock screen display and controls for livestreams.

• Fixed issue where the next item in the queue paused unexpectedly.

• Resolved playback stuttering on Android during livestreams.

• Fixed disappearing playback controls on the lock screen.

• Fixed playback speed not updating correctly.

• Resolved issue where played episodes couldn’t be replayed.

• Fixed playback not resuming correctly when listening in the car.

• Synced car playback position with the device.

• Fixed persistent car display refresh issue.

• Fixed volume control via car controls.

• Resolved issue with headphone controls after playing a transcript.

• Fixed disappearing metadata on the lock screen.

• Fixed bug where downloaded episodes stopped in airplane mode but showed as playing.

---

We would love to hear how you’re finding Fountain 1.2. Please submit your thoughts and feedback via the main menu in the app and we will take it on board as we continue to improve the app.

If you want to help test new features out before they get released, you can join Fountain Beta on Telegram. All iOS and Android users welcome.

@ 6a6be47b:3e74e3e1

Hi frens, you may or may not have noticed I’ve been MIA for about three weeks. I wanted to take a moment to explain where I’ve been, and why I stepped back for a bit.

At the start of the year, I was determined to make the most of it-and I still am. I’ve been pouring myself into several projects, especially my painting, which has really taken off. I’m so grateful for your support; none of this would be possible without you. But here’s where things got tricky. I started feeling like I had to “earn” every moment of rest, and that mindset snowballed. My health took a hit, and then one of my other projects completely derailed.

The stress piled up, and I felt like I was on the verge of burning out.

Don’t get me wrong-I’ve always welcomed change, even when it’s tough. And this time was no exception. The project I’d been working on for months took a 180, and all that effort seemed to go down the drain. I was frustrated, but I kept pushing, even though I was running on fumes. By the time I “earned” a break, I was too exhausted to enjoy it.

I managed to post a piece about Holy Week on my blog (which I’m really proud of-check it out if you haven’t!), but after that, I was done. I realized I needed to stop, not just for a day, but for a real break. When I finally took a few days off with my husband, it was clear how much I needed it. I was burned out, plain and simple. Now, I’m still putting myself back together. Mentally, I feel drained, but I’m stronger than I was a few weeks ago. I know I’m lucky and privileged to be able to take this time, and I’m grateful for the perspective it’s given me. I also r realize that this isn’t just a “me” thing-most people have been here at some point. We keep going until there’s nothing left, then wonder why we feel like empty shells.

I’ll be back to drawing soon (knock on wood-don’t want to jinx it!). In the meantime, take care of yourselves, and godspeed.

@ c9badfea:610f861a

1. Install Kiwix (it's free and open source)
2. Download ZIM files from the Kiwix Library (you will find complete offline versions of Wikipedia, Stack Overflow, Bitcoin Wiki, DevDocs and many more)
3. Open the downloaded ZIM files within the Kiwix app

ℹ️ You can also package any website using either Kiwix Zimit (online tool) or the Zimit Docker Container (for technical users)

ℹ️ .zim is the file format used for packaged websites

@ 91d8dece:3453543b

https://drewztools.com/ flash USDT Are you tired of the long wait times and excessive fees associated with traditional cryptocurrency transactions? Look no further! Flash USDT from @drewztooolz is here to ease the way you send and receive crypto. Experience lightning-fast transfers, total anonymity, and zero fees with this state-of-the-art service. This flash last in the wallet for 90 t0 360 days before it disappears . Just so you know this coin is tradeable , swappable and transferable to many wallet type Flash USDT is not just another crypto tool; it’s a game-changer for anyone involved in cryptocurrency trading, particularly for OTC traders, P2P dealmakers, and cold wallet testers. Here’s why you should consider making it a part of your crypto toolkit: 🔥 Instant Transfers With Flash USDT, you can send high-value USDT to any wallet in under 60 seconds. Imagine the convenience of having your funds appear instantly without the typical delay caused by blockchain confirmations. Still have questions? Reach out via Telegram for 1-on-1 support. Our team is ready to assist you with anything you need! https://drewztools.com/ 💬 @drewztooolz 📲+1 (770) 666–2531

@ 6e64b83c:94102ee8

Nostr-static is a powerful static site generator that transforms long-form Nostr content into beautiful, standalone websites. It makes your content accessible to everyone, even those not using Nostr clients. For more information check out my previous blog post How to Create a Blog Out of Nostr Long-Form Articles

What's New in Version 0.7?

RSS and Atom Feeds

Version 0.7 brings comprehensive feed support with both RSS and Atom formats. The system automatically generates feeds for your main content, individual profiles, and tag-specific pages. These feeds are seamlessly integrated into your site's header, making them easily discoverable by feed readers and content aggregators.

This feature bridges the gap between Nostr and traditional web publishing, allowing your content to reach readers who prefer feed readers or automated content distribution systems.

Smart Content Discovery

The new tag discovery system enhances your readers' experience by automatically finding and recommending relevant articles from the Nostr network. It works by:

1. Analyzing the tags in your articles
2. Fetching popular articles from Nostr that share these tags
3. Using configurable weights to rank these articles based on:
4. Engagement metrics (reactions, reposts, replies)
5. Zap statistics (amount, unique zappers, average zap size)
6. Content quality signals (report penalties)

This creates a dynamic "Recommended Articles" section that helps readers discover more content they might be interested in, all while staying within the Nostr ecosystem.

See the new features yourself by visiting our demo at: https://blog.nostrize.me

@ 5ffa0470:9c3e760a

@ 90c656ff:9383fd4e

In recent years, Bitcoin has often been compared to gold, earning the nickname “digital gold.” This comparison arises because both forms of value share key characteristics, such as scarcity, durability, and global acceptance. However, Bitcoin also represents a technological innovation that redefines the concept of money and investment, standing out as a modern and efficient alternative to physical gold.

One of the main reasons Bitcoin is compared to gold is its programmed scarcity. While gold is a naturally limited resource whose supply depends on mining, Bitcoin has a maximum cap of 21 million units, defined in its code. This cap protects Bitcoin from inflation, unlike traditional currencies that can be created without limit by central banks.

This scarcity gives Bitcoin lasting value, similar to gold, as the limited supply helps preserve purchasing power over time. As demand for Bitcoin grows, its reduced availability reinforces its role as a store of value.

Another feature that brings Bitcoin closer to gold is durability. While gold is resistant to corrosion and can be stored for centuries, Bitcoin is a digital asset protected by advanced cryptography and stored on the blockchain. An immutable and decentralized ledger.

Moreover, Bitcoin is far easier to transport than gold. Moving physical gold involves high costs and security risks, making transport particularly difficult for international transactions. Bitcoin, on the other hand, can be sent digitally anywhere in the world in minutes, with low fees and no intermediaries. This technological advantage makes Bitcoin more effective in a globalized and digital world.

Security is another trait that Bitcoin and gold share. Gold is difficult to counterfeit, making it a reliable store of value. Similarly, Bitcoin uses cryptographic protocols that ensure secure transactions and protect against fraud.

In addition, all Bitcoin transactions are recorded on the blockchain, offering a level of transparency that physical gold does not provide. Anyone can review transactions on the network, increasing trust and traceability.

Historically, gold has been used as a hedge against inflation and economic crises. During times of instability, investors turn to gold as a way to preserve their wealth. Bitcoin is emerging as a digital alternative with the same purpose.

In countries with high inflation or political instability, Bitcoin has been used as a safeguard against the devaluation of local currencies. Its decentralized nature prevents governments from directly confiscating or controlling the asset, providing greater financial freedom to users.

Despite its similarities with gold, Bitcoin still faces challenges. Its volatility is much higher, which can cause short-term uncertainty. However, many experts argue that this volatility is typical of new assets and tends to decrease over time as adoption grows and the market matures.

Another challenge is regulation. While gold is globally recognized as a financial asset, Bitcoin still faces resistance from governments and financial institutions, which seek ways to control and regulate it.

In summary, Bitcoin - often called "digital gold" - offers a new form of value that combines the best characteristics of gold with the efficiency and innovation of digital technology. Its programmed scarcity, cryptographic security, portability, and resistance to censorship make it a viable alternative for preserving wealth and conducting transactions in the modern world.

Despite its volatility, Bitcoin is establishing itself as both a store of value and a hedge against economic crises. As such, it represents not just an evolution of the financial system but also a symbol of the shift toward a decentralized and global digital economy.

Thank you very much for reading this far. I hope everything is well with you, and sending a big hug from your favorite Bitcoiner maximalist from Madeira. Long live freedom!

@ 7460b7fd:4fc4e74b

PR 32359：取消 OP_RETURN 字节限制提案深入分析

提案概述及代码变更内容

提案背景与意图：比特币核心当前对交易中的 OP_RETURN 输出（数据载体输出）有严格限制：默认最多允许单个 OP_RETURN 输出，且其 scriptPubKey 大小不超过 83 字节（约80字节数据加上OP_RETURN和Pushdata前缀）groups.google.com。这一标准规则旨在轻度阻碍链上存储大量任意数据，鼓励将非金融数据以“更无害”的方式存入链上（比如用OP_RETURN而非可花费的UTXO输出）groups.google.com。然而随着时间推移，这一限制并未阻止用户将数据写入区块链，反而促使开发者设计各种变通方案绕过限制。例如，近期 Citrea Clementine 协议（闪电网络相关项目）因为OP_RETURN容量不足，而改用不可花费的Taproot输出来存储所需数据groups.google.com。这样的做法导致大量小额UTXO留存在UTXO集，对全节点造成负担，被视为比使用OP_RETURN更有害的副作用github.com。基于此背景，Bitcoin Core 开发者 Peter Todd（与 Chaincode 实验室的 Antoine Poinsot 等人）提出了 PR #32359，意在解除OP_RETURN的字节大小限制，以消除这种“适得其反”的限制策略groups.google.comgithub.com。

**代码变更要点：**该PR主要修改了与标准交易校验和策略配置相关的代码，包括移除 script/standard.cpp 中对OP_RETURN输出大小和数量的检查，以及删除策略配置选项 -datacarrier 和 -datacarriersizegithub.com。具体而言：

• 取消OP_RETURN大小限制：删除了判断OP_RETURN数据长度是否超过 MAX_OP_RETURN_RELAY（83字节）的标准性检查。此后，交易中的OP_RETURN输出脚本长度将不再被固定上限限制，只要满足区块重量等共识规则即可（理论上可嵌入远大于83字节的数据）github.comgroups.google.com。PR说明中明确提到移除了这些限制的执行代码github.com。相应地，-datacarriersize 配置参数被删除，因为其存在意义（设置OP_RETURN字节上限）已不复存在github.com。此前 -datacarriersize 默认为83，当用户调高该值时节点可接受更大数据载体输出；而现在代码中已无此参数，节点将无条件接受任意大小的OP_RETURN输出。

• 移除OP_RETURN输出数量限制：原先比特币核心默认策略还规定每笔交易最多只有一个OP_RETURN输出是标准的，多于一个即视为非标准交易（拒绝中继）bitcoin.stackexchange.com。该PR同样意在取消此“任意”限制groups.google.com。修改中移除了对 nDataOut（OP_RETURN输出计数）的检查，即允许一笔交易包含多个OP_RETURN输出而仍被视作标准交易。之前的代码若检测到 nDataOut > 1 会返回“multi-op-return”的拒绝原因github.com；PR删除了这一段逻辑，相应的功能测试也更新或移除了对“multi-op-return”非标准原因的断言github.com。

• 保留标准形式要求：值得注意的是，OP_RETURN输出的形式要求仍保留。PR描述中强调“数据载体输出的形式仍保持标准化：脚本以单个 OP_RETURN 开头，后跟任意数量的数据推字节；不允许非数据类的其他脚本操作码”github.com。也就是说，虽然大小和数量限制解除了，但OP_RETURN脚本内容只能是纯数据，不能夹带其他执行opcode。这保证了这些输出依然是“不可花费”的纯数据输出，不会改变它们对UTXO集的影响（不会增加UTXO）。

综上，PR #32359 的核心改动在策略层面放宽了对 OP_RETURN 的限制，删除了相关配置和检查，使节点默认接受任意大小、任意数量的 OP_RETURN 数据输出。同时维持其基本形式（OP_RETURN+数据）以确保此变更不会引入其它类型的非标准交易格式。

改动层级：策略规则 vs 共识规则

该提案属于策略层（policy-level）的更改，而非共识层规则的更改。也就是说，它影响的是节点对交易的_中继、存储和打包_策略，而不改变交易或区块在链上的有效性判定。OP_RETURN字节上限和数量限制从一开始就是标准性约束（Standardness），并非比特币共识协议的一部分groups.google.com。因此，移除这些限制不会导致旧节点与新节点产生区块共识分歧。具体理由如下：

• 无共识规则变动：原有的83字节上限只是节点默认_拒绝转发/挖矿_超限交易的规则，但如果矿工强行将超83字节的OP_RETURN交易打包进区块，所有遵循共识规则的节点（包括未升级的旧节点）依然会接受该区块。因为共识层并没有“OP_RETURN大小不得超过83字节”的规定github.com。正如开发者所指出的，现行的OP_RETURN限制属于“standardness rules”，其约束可以被轻易绕过，并不影响交易的最终有效性github.com。Peter Todd 在评论中强调，为真正禁止链上发布任意数据，必须修改比特币的共识协议，而这在现实中几乎不可能实施github.com。

• **旧节点兼容性：**由于没有引入新的脚本opcode或共识验证规则，旧版本节点即使不升级，仍然会承认包含大OP_RETURN输出的区块为有效。换言之，不存在分叉风险。旧节点唯一的区别是仍会按照老策略拒绝中继此类交易，但一旦交易被打包进区块，它们仍会接受github.com。正因如此，这一提议不会引发硬分叉，只是改变默认策略。

• **策略可自行定制：**另外，正如PR作者所言，这纯粹是默认策略的调整，用户依然可以选择运行修改版的软件继续实施先前的限制。例如，Peter Todd提到有替代实现（如 Bitcoin Knots）可以继续强制这些限制github.com。因此，这并非要“强制”所有节点解除限制，而是主流软件默认策略的演进。

需要澄清的是，有反对者担心解除限制可能扩大攻击面（下文详述），但这些都是针对节点资源和网络层面的影响，而非共识层安全性问题。总的来看，PR #32359 是策略层改进，与先前如RBF默认开启、逐渐弱化非标准交易限制等改变类似，其出发点在于网络行为而非协议规则本身。

对闪电网络节点和交易验证的影响

对链上验证的影响：由于这是策略层变更，交易和区块的验证规则并未改变，因此运行旧版本 Bitcoin Core 的闪电网络节点在共识上不会出现任何问题。闪电网络全节点通常依赖比特币全节点来跟踪链上交易，它们关心的是交易确认和共识有效性。解除OP_RETURN限制并不会使旧节点拒绝新区块，因而不会造成闪电通道关闭交易或HTLC交易在旧节点上验签失败等情况。换句话说，不升级Bitcoin Core软件的LN节点仍可正常参与链上共识，无需担心链上交易验证兼容性。

对节点中继和资源的影响：主要影响在于网络传播和资源占用。如果闪电网络节点所连接的Bitcoin Core没有升级，它将不会中继或存储那些含有超大OP_RETURN的未确认交易（因为旧版本视之为非标准交易）。这可能导致未升级节点的内存池与升级节点不一致：某些在新版节点中合法存在的交易，在旧版中被拒之门外。不过这通常不影响闪电网络的运行，因为闪电通道相关交易本身不会包含OP_RETURN数据输出。此外，当这些交易被矿工打包进区块后，旧节点依然会接收到区块并处理。所以，即便LN节点的后端Bitcoin Core未升级，最坏情形只是它在交易未打包时可能感知不到这些“大数据”交易，但这通常无碍于闪电网络功能（闪电网络主要关心的是通道交易的确认情况）。

升级的好处和必要性：从闪电网络生态来看，放宽OP_RETURN限制反而可能带来一些正面作用。正如前述，已有闪电网络周边项目因为83字节限制不足，转而使用不可花费输出存储数据groups.google.com。例如 Antoine Poinsot 在邮件列表中提到的 Clementine 协议，将某些watchtower挑战数据存进Taproot输出，因为OP_RETURN容量不够groups.google.com。解除限制后，此类应用完全可以改用更友好的OP_RETURN输出来存储数据，不再制造永久占据UTXO集的“垃圾”UTXOgithub.com。因此，闪电网络的watchtower、跨链桥等组件若需要在链上写入证据数据，将可直接利用更大的OP_RETURN输出，网络整体效率和健壮性都会提升。

需要注意的是，如果PR最终被合并并广泛部署，闪电网络节点运营者应该升级其Bitcoin Core后端以跟上新的默认策略。升级后，其节点将和大多数网络节点一样中继和接受大OP_RETURN交易，确保自己的内存池和网络同步，不会漏掉一些潜在相关交易（尽管目前来看，这些交易对LN通道本身并无直接关联）。总之，从兼容性看不升级没有致命问题，但从网络参与度和功能上看，升级是有益的。

潜在的间接影响：反对者提出，解除限制可能导致区块和内存池充斥更多任意数据，从而推高链上手续费、影响闪电通道关闭时所需的手续费估计。例如，如果大量大OP_RETURN交易占据区块空间，链上拥堵加剧，LN通道关闭需要支付更高费用才能及时确认。这其实是一般性拥堵问题，并非LN特有的兼容性问题。支持者则认为，这正是自由市场作用的体现，使用链上空间就该竞争付费github.com。无论如何，闪电网络作为二层方案，其优势在于减少链上交互频率，链上手续费市场的变化对LN有影响但不改变其运行逻辑。LN节点只需确保其Bitcoin Core正常运行、及时跟上链上状态即可。

开发者讨论焦点：支持与反对观点

PR #32359 在开发者社区引发了激烈讨论，支持者和反对者针锋相对，各自提出了有力的论据。以下总结双方主要观点：

• 支持方观点：

• 当前限制无效且适得其反：支持者强调83字节上限并未阻止人们在链上存数据，反而促使更有害的行为。Peter Todd指出，很多协议改用不可花费UTXO或在scriptsig中藏数据来绕过OP_RETURN限制，结果增加了UTXO集膨胀，这是限制OP_RETURN带来的反效果github.com。与其如此，不如移除限制，让数据都写入可被丢弃的OP_RETURN输出，避免UTXO污染github.comgithub.com。正如一位支持者所言：“与其让尘埃UTXO永远留在UTXO集合，不如使用可证明不可花费的输出（OP_RETURN）”github.com。

• **限制易被绕过，增添维护负担：**由于有些矿工或服务商（如MARA Slipstream私有广播）本就接受大OP_RETURN交易，这一限制对有心者来说形同虚设github.com。同时，存在维护这个限制的代码和配置选项，增加了节点实现复杂度。Todd认为，与其让Bitcoin Core承担维护“低效甚至有害”的限制，不如干脆取消，有需要的人可以使用其他软件实现自己的政策github.com。他提到有替代的Bitcoin Knots节点可自行过滤“垃圾”交易，但没必要要求Bitcoin Core默认坚持这些无效限制github.com。

• 尊重自由市场，拥抱链上数据用例：部分支持者从理念上认为，比特币区块空间的使用应交由手续费市场决定，而不应由节点软件做人为限制。著名开发者 Jameson Lopp 表示，是时候承认“有人就是想用比特币做数据锚定”，我们应当提供更优方式满足这种需求，而不是一味阻碍github.com。他认为用户既然愿意付费存数据，就说明这种行为对他们有价值，矿工也有动力处理；网络层不应进行过度的“父爱”式管制github.com。对于反对者所称“大数据交易会挤占区块、抬高手续费”，Lopp直言“这本来就是区块空间市场运作方式”，愿付高费者得以优先确认，无可厚非github.com。

• 统一与简化策略：还有支持者指出，既然限制容易绕过且逐渐没人遵守，那保留它只会造成节点之间策略不一致，反而增加网络复杂性。通过取消限制，所有核心节点一致地接受任意大小OP_RETURN，可避免因为策略差异导致的网络孤块或中继不畅（尽管共识不受影响，但策略不一致会带来一些网络层问题）。同时删除相关配置项，意味着简化用户配置，减少困惑和误用。Peter Todd在回应保留配置选项的建议时提到，Bitcoin Core在Full-RBF功能上也曾移除过用户可选项，直接默认启用，因为现实证明矿工最终都会朝盈利的方向调整策略，节点自行设置反而无济于事github.com。他以RBF为例：在Core开启默认Full-RBF之前，矿工几乎已经100%自行采用了RBF策略，因此保留开关意义不大github.com。类比来看，数据交易也是如此：如果有利可图，矿工终会打包，无论节点是否选择不转发。

• 反对方观点：

• 去除限制会放松对垃圾交易的防线：反对者担心，一旦解除OP_RETURN限制，链上将出现更多纯粹存储数据的“垃圾”交易，给网络带来DoS攻击和资源消耗风险。开发者 BrazyDevelopment 详细描述了可能被加剧的攻击向量github.com：首先，“Flood-and-Loot”攻击——攻击者构造带有巨大OP_RETURN数据的低价值交易（符合共识规则，多笔交易可达数MB数据），疯狂填充各节点的内存池。github.com这样会占满节点内存和带宽，延迟正常交易的传播和确认，并推高手续费竞争。github.com虽然节点有maxmempool大小限制和最低中继费率等机制，但这些机制基于常规交易行为调校，面对异常海量的数据交易可能捉襟见肘github.com。其次，“RBF替换循环”攻击——攻击者可以利用无需额外费用的RBF替换，不断发布和替换包含大OP_RETURN的数据交易，在内存池中反复占据空间却不被确认，从而扰乱手续费市场和内存池秩序github.com。反对者认为，移除大小上限将使上述攻击更廉价、更容易实施github.com。他们主张即便要放宽，也应设定一个“高但合理”的上限（例如100KB），或在内存池压力大时动态调整限制，以保护较小资源节点的运行github.com。

• 用户丧失自定义策略的权利：一些开发者反对彻底删掉 -datacarrier 和 -datacarriersize 选项。他们认为即使大势所趋是接受更多数据，也应保留用户自主选择的空间。正如开发者 BitcoinMechanic 所言：“矿工接受大数据交易不代表用户就不能选择自己的内存池装些什么”github.com。目前用户可以通过配置将-datacarrier设为0（不中继OP_RETURN交易）或者调低-datacarriersize来严格限制自己节点的策略。直接去除这些选项，会让那些出于各种考虑（如运营受限资源节点、防范垃圾数据）的用户失去控制权。从这个角度看，反对者认为限制应该由用户 opt-in 地解除，而不是一刀切放开。开发者 Retropex 也表示：“如果矿工想要更大的数据载体交易，他们完全可以自行调整这些设置…没有理由剥夺矿工和节点运营者做选择的权利”github.com。

• 此改动非必要且不符合部分用户利益：有反对意见认为当前83字节其实已经能覆盖绝大多数合理应用需求，更大的数据上链并非比特币设计初衷。他们担心放开限制会鼓励把比特币区块链当作任意数据存储层，偏离“点对点电子现金”主线，可能带来长期的链膨胀问题。这一阵营有人将此争议上升为理念之争：是坚持比特币作为金融交易为主，还是开放成为通用数据区块链？有评论形容这场拉锯“有点类似2017年的扩容之争”，虽然本质不同（一个是共识层区块大小辩论，一个是策略层数据使用辩论），但双方观点分歧同样明显99bitcoins.com99bitcoins.com。一些反对者（如Luke Dashjr等）长期主张减少非必要的数据上链，此次更是明确 Concept NACK。Luke-Jr 认为，其实完全可以通过引入地址格式变化等办法来识别并限制存数据的交易，而不需要动用共识层改动github.com（虽然他也承认这会非常激进和不现实，但以此反驳“除了改共识无计可施”的观点）。总之，反对者倾向于维持现状：代码里已有的限制无需移除，至少不应在无压倒性共识下贸然改变github.com。

• 社区共识不足：许多开发者在GitHub上给出了“Concept NACK”（概念上不支持）的评价。一位参与者感叹：“又来？两年前讨论过的理由现在依然适用”github.com。在PR的Review日志中，可以看到反对此提案的活跃贡献者数量明显多于支持者github.com。例如，反对阵营包括 Luke-Jr、BitcoinMechanic、CryptoGuida、1ma 等众多开发者和社区成员，而支持此提案的核心开发者相对少一些（包括Jameson Lopp、Sjöors、Sergio Demian Lerner等）github.com。这种意见分裂显示出社区对取消OP_RETURN限制尚未达成广泛共识。一些反对者还担忧这么大的改动可能引发社区矛盾，甚至有人夸张地提到可能出现新的链分叉风险99bitcoins.com99bitcoins.com（虽然实际上由于不涉及共识，硬分叉风险很小，但社区内部分歧确实存在）。

综上，支持者聚焦于提高链上效率、顺应实际需求和减轻UTXO负担，认为解除限制利大于弊；而反对者强调网络稳健、安全和用户自主，担心轻易放开会招致滥用和攻击。双方在GitHub上的讨论异常热烈，很多评论获得了数十个👍或👎表态，可见整个社区对此议题的关注度之高github.comgithub.com。

PR当前状态及后续展望

截至目前（2025年5月初），PR #32359 仍处于开放讨论阶段，并未被合并。鉴于该提案在概念上收到了众多 NACK，缺乏开发者间的明确共识，短期内合并的可能性不大。GitHub 上的自动统计显示，给予“Concept NACK”的评审者数量显著超过“Concept ACK”的数量github.com。这表明在Bitcoin Core维护者看来，社区对是否采纳此改动存在明显分歧。按照 Bitcoin Core 一贯的谨慎作风，当一个提案存在较大争议时，通常会被搁置或要求进一步修改、讨论，而不会仓促合并。

目前，该PR正等待进一步的评审和讨论。有开发者提出了替代方案或折中思路。例如，Bitcoin Core维护者 instagibbs 提交了相关的 PR #32406，提议仅取消默认的OP_RETURN大小上限（等效于将-datacarriersize默认提高到极大），但保留配置选项，从而在不牺牲用户选择权的情况下实现功能开放github.com。这表明部分反对者并非完全拒绝放宽限制，而是希望以更温和的方式推进。PR #32359 与这些提案互相冲突，需要协调出统一的方案github.com。另外，也有开发者建议在测试网上模拟大OP_RETURN交易的攻击场景，以评估风险、说服怀疑者github.com。

审议状态总结：综合来看，PR #32359 尚未接近合并，更谈不上被正式接受进入下一个Bitcoin Core版本。它既没有被关闭（拒绝），也没有快速进入最终review/merge阶段，而是停留在激烈讨论中。目前Bitcoin Core的维护者并未给出明确的合并时间表，反而是在鼓励社区充分讨论其利弊。未来的走向可能有几种：要么提案经过修改（例如保留配置项、增加安全机制等）逐渐赢得共识后合并，要么维持搁置等待更明确的社区信号。此外，不排除开发者转而采用渐进路线——例如先在测试网络取消限制试验，或先提高上限值而非彻底移除，以观察效果。也有可能此提案最终会因共识不足而长期悬而不决。

总之，OP_RETURN字节限制之争体现了比特币开发中策略层决策的审慎和平衡：需要在创新开放与稳健保守之间找到折衷。PR #32359 所引发的讨论仍在持续，它的意义在于促使社区重新审视链上数据存储的策略取舍。无论最终结果如何，这一讨论本身对比特币的发展具有积极意义，因为它让开发者和社区更加清晰地权衡了比特币作为数据载体和价值载体的定位。我们将持续关注该提案的进展，以及围绕它所展开的进一步测试和论证。github.comgroups.google.com

引用来源：

• Bitcoin Core PR #32359 提案内容github.comgithub.com及开发者讨论（Peter Todd评论github.comgithub.com等）

• Bitcoin Dev 邮件列表讨论帖：《Relax OP_RETURN standardness restrictions》groups.google.comgroups.google.com

• GitHub 开发者评论摘录：支持意见（Jameson Loppgithub.com等）与反对意见（BitcoinMechanicgithub.com、BrazyDevelopmentgithub.com等）

• Bitcoin Core PR 评论自动统计（Concept ACK/NACK 汇总）github.com

@ 56cd780f:cbde8b29

[Test3] Trying to show subtitle

Is it actually called “summary”?

@ 56cd780f:cbde8b29

A few weeks ago, I ran into an old friend at a coffee shop. We hadn’t spoken in years, and within five minutes, she said something I’ve heard countless times:

“I just feel like I’m so behind.”

Behind who? Behind what?

There’s this idea—quiet, nagging, oddly universal—that we’re all somehow in a race we didn’t sign up for. That we’re supposed to have hit certain milestones by certain ages. That if we’re not married, promoted, rich, settled, happy (and photogenic) by 30 or 40 or pick your poison, then we’ve failed some invisible test.

Where did this come from?

Some of it’s cultural, obviously. Social media compresses timelines. You’re 27, doom-scrolling, and suddenly someone from high school just IPO’d their startup and got engaged in Rome. Another just bought a house with a kitchen island the size of a small country. You wonder if you missed a memo.

But beneath that, there’s something deeper. A belief that life is linear. That it should look like a staircase: school, job, marriage, house, kids, success. But real life? It’s a squiggle. A mess. A beautiful disaster.

Here’s the truth: You’re not behind. There’s no schedule. There’s only your path, and the courage it takes to stay on it—even when it looks wildly different from everyone else’s.

I say this as someone who has taken the “scenic route.” I changed careers in my 30s. I moved cities on a hunch. I dropped things that looked great on paper because they felt wrong in my gut. I’ve had seasons of momentum and seasons of stuckness. Both were necessary.

“Catching up” assumes there’s a fixed destination. But what if there isn’t? What if the point isn’t arrival, but presence? Progress that feels real, not performative?

If you need a permission slip to stop comparing, let this be it.

You’re not late. You’re not early.
You’re right on time.

@ 56cd780f:cbde8b29

There’s something sacred about morning air — the way it carries just enough chill to remind you you’re alive, without pushing you back inside. I’ve been starting my days on the balcony lately. Not because it’s glamorous (it isn’t), or because I have a routine (I don’t), but because it’s the only space in my apartment that feels both open and still.

This morning I made coffee with too much cinnamon and curled up with a blanket that’s seen better days. I watched the city slowly wake up — one barking dog, two joggers, and the clatter of a recycling truck below. It’s odd how these tiny patterns become a kind of comfort.

I used to think that slowing down meant falling behind. But here, perched on the third floor with my feet on cold concrete and the sky just starting to blush, I feel like I’m exactly where I’m supposed to be.

If you’re reading this, maybe you needed that reminder too.

— Natalie

@ c9badfea:610f861a

1. Create

bash git bundle create backup.bundle --all

2. Verify

bash git bundle verify backup.bundle

3. Restore

bash git clone backup.bundle

ℹ️ Feel free to change the backup.bundle file name

@ 41959693:3888319c

Die Schnelllebigkeit der Moderne tilgt in unserer Wahrnehmung die zeitlichen Abstände von Ereignissen. Es bleibt kaum Gelegenheit ein Thema im Rückspiegel zu erfassen, zu durchdenken, zu rezipieren – schon buhlt der nächste Augenblick um Aufmerksamkeit.

Mögen an die Leipziger Buchmesse Ende März mittlerweile nur noch Visitenkarten und Selfies oder manch signiertes Exemplar im Buchregal erinnern; es lohnt sich doch, die größte deutsche Besuchermesse der Buchbranche nun rückblickend zu betrachten. Gerade da ihr Event-Charakter von Jahr zu Jahr zunimmt, ist die Frage reizvoll, welche beständigen Themen dort wie präsentiert wurden, in diesem Fall natürlich „Frieden“.

An allen vier Messetagen hielt ich die Augen auf, wo sich Autoren, Verlage und allgemeine die Institutionen der Branche dazu äußerten. Vorgreifend muss gesagt werden, dass Krieg und Frieden heute nicht mehr zwingend primäre Themen sind, sondern oft begleitend mitbehandelt werden. Für Zerstörung und Elend scheint dabei immer die große Bühne bereitet zu werden; einvernehmliche Koexistenz wird gewöhnlich mit leiser Klaviatur gespielt. Dennoch fand ich vier Bücher, welche direkt das Thema ansprachen:

• Die norwegische Soziologin und Publizistin Linn Stalsberg stellte ihr Werk „War is contempt for life. An essay on peace“ (ISBN: 978-8282262736, Res Publica, 2024) vor, in welchem sie auf all die Menschen eingeht, die für Pazifismus, Gewaltlosigkeit und Anti-Militarismus einstehen. Ihrer Meinung nach haben wir unzählige Berichte über Kriegs-, kaum jedoch Geschichten von Friedenshelden. Die deutsche Ausgabe soll im schweizerischen Kommode-Verlag im September diesen Jahres erscheinen.

• „Die Evolution der Gewalt. Warum wir Frieden wollen, aber Kriege führen“, geschrieben von Kai Michel, Harald Meller und Carel van Schaik, wurde für den Preis der Leipziger Buchmesse in der Kategorie Sachbuch/Essayistik nominiert. Die Autoren vertreten u. a. die Thesen, dass Krieg kein essentieller Gesellschaftsprozess ist, wie es einige geflügelte Worte oder ideologische Äußerungen vermuten lassen – und, dass die Erfolge der Bellizisten nur 1 % der Weltgeschichte ausmachen (ISBN: 978-3423284387, dtv, 2024).

• Der Publizist und taz-Redakteur Pascal Beucker gibt mit „Pazifismus – ein Irrweg?“ (ISBN 978-3170434325, Kohlhammer, 2024) eine Übersicht über die Geschichte des Pazifismus, geht auf in Vergessenheit geratene Hintergründe der einzelnen Motivationen und Bewegungen ein und wagt Zukunftsprognosen über die Erfolgschancen gewaltloser Auseinandersetzungen.

• Neben den Sachbüchern fand sich auch ein Vertreter aus dem Bereich der Belletristik: Rüdiger Heins und Michael Landgraf gaben eine Anthologie mit Friedenstexten, Prosa und Lyrik, heraus: „365 Tage Frieden“ (ISBN: 978-3930758951 Edition Maya, 2025), verspricht der Titel, für den zahlreiche Autoren auf ganz unterschiedliche Art und Weise träumten, sich erinnerten, uns mahnten und weiterhin hoffen.

Ansonsten fanden sich viele kleinere Veranstaltungsformate und Verlage, welche ihr Scherflein beitragen wollten, dabei aber sehr unscharf blieben und beispielsweise im Forum Offene Gesellschaft u. a. Grenzoffenheit, Toleranz und Inklusion behandelten. Inwieweit diese, in jüngster Vergangenheit doch recht stark medial forcierten Themen die zentrale Friedensfrage ergründen und stützen, ist vermutlich Auslegungssache.

Unsere Definition von Frieden mag nicht sonderlich scharf sein; jeder zieht darin andere Grenzen und wird sich situativ nach eigenem Gusto verhalten. Dennoch bewegt uns eine Grundschwingung, führt uns ein Sehnen in eine höhere, gemeinsame Richtung. Diese Erkenntnis ist es wert, durch den Lauf der Geschichte bewahrt zu werden, durch aktuelle Zeugnisse ebenso wie durch die Gedanken derer, die vor uns waren.

---

Ich habe beschlossen diese Bücher für Sie, werte Leser, in den nächsten Wochen nach und nach zu rezensieren.

---

Dieser Beitrag wurde mit dem Pareto-Client geschrieben.

Not yet on Nostr and want the full experience? Easy onboarding via Start.

Artikel findet man auch auf Telegram unter:

https://t.me/pareto_artikel

https://t.me/friedenstaube_artikel