steepdawn974

Ben, this sucks but it is not as much a legal home run as you may think. There is a thing called "Störerhaftung" which means even entities who simply relay/spread "unlawful information" (aggregators, search engines etc) can made to take the site off their index. To what extemd this applies here, I asked an expert: my Kagi Research agent 😀
Section 5 and 7 particularly relevant.
[Background: whether the post the actually violates complainer's rights actually does so, is dubious. It's a high ranking politican's son who allegedly beat his wife, and uses daddy's political influence and the legal system to squash any reporting on it, and links in search engines and aggregators]
<agent response>
Here is a thorough legal assessment of this takedown notice under German law.
---
# Legal Assessment of the Takedown Notice
## 1. What the Notice Claims
The sender claims:
- A specific piece of content (a Nostr note) accessible via the aggregator's website "unlawfully identifies" them.
- The Munich Regional Court I (Landgericht München I) issued a judgment on **18 December 2025** (Case No. **26 O 13971/25**) against **Reddit**, prohibiting further dissemination of this content.
- On this basis, the aggregator must remove the content.
---
## 2. The Core Legal Problem: Judgments Only Bind the Parties (Inter Partes)
This is the most fundamental flaw in the notice.
Under German civil procedure law (**§ 322 ZPO**), the binding effect of a court judgment (*materielle Rechtskraft*) is strictly **inter partes** — it only binds the **parties to the case**. 【4】
A judgment against **Reddit** creates **no legal obligation whatsoever** for a Nostr aggregator. The aggregator:
- Was not a party to the Munich proceedings
- Was never served
- Had no opportunity to defend itself
- Cannot be bound by a judgment it had no part in
The notice is therefore **legally misleading** in implying the aggregator is bound by the Reddit ruling. Even if the case is real and the judgment valid, it is simply irrelevant to the aggregator as a matter of German procedural law.
> **Practical note:** No public record of case 26 O 13971/25 was found in any legal database. The case number format is plausible for LG München I, but its existence and content cannot be independently verified. This raises the possibility that the notice is exaggerating or misrepresenting the judgment's scope.
---
## 3. German Law on Aggregator/Search Engine Liability (*Störerhaftung*)
Since the aggregator is not bound by the Reddit judgment, the question becomes: **does the aggregator have an independent legal obligation to remove the content?**
### The Legal Framework
German law does not give search engines and aggregators a statutory safe harbor under the **Telemediengesetz (TMG)** for hyperlinks and location tools — the legislature never extended §§ 8–10 TMG to cover them. 【1】 Instead, their liability is governed by general tort law and a body of BGH case law.
Since **February 2024**, the EU **Digital Services Act (DSA)** has replaced the TMG's liability provisions. Under **DSA Art. 6**, hosting/intermediary providers are not liable for illegal third-party content if they act expeditiously upon obtaining actual knowledge of it. 【2】
### Key BGH Case Law
| Case | Ruling | Relevance |
|---|---|---|
| **BGH I ZR 259/00 – *Paperboy*** (2003) | A search/aggregation service linking to third-party content does not infringe by the act of linking alone; deep-linking is permissible | Aggregators are not primary infringers |
| **BGH VI ZR 144/11 – RSS-Feed** (2012) | Embedding an RSS feed is not "adopting" (*zu-eigen-machen*) third-party content; *Störerhaftung* requires a breach of duty of care; if content is removed promptly after a complaint, no injunction claim (*Unterlassungsanspruch*) arises | Notice-and-takedown is the operative standard |
The BGH's RSS-Feed ruling is particularly on point: an aggregator that embeds or displays third-party content **does not make that content its own**, and **Störerhaftung only arises if it fails to act after being notified** of a specific infringement. 【3】<kcite>@www.otto-schmidt.de/blog/it-recht-blog/bgh-storerhaftung-auf-dem-weg-zu-notice-and-takedown-ITBLOG0000704.html#621-626</parameter>
The BGH has also held that the liability of search engines for possibly unlawful expressions in their references should be **lowered** because of the significance of such services for freedom of expression and information. 【1】
---
## 4. The Nostr-Specific Technical Facts Are Legally Significant
The technical background you described is highly relevant:
- The content is **not hosted** by the aggregator — it lives on decentralized Nostr relays.
- The aggregator merely **indexes and displays links** to content on those relays, analogous to a search engine.
- The aggregator likely **cannot delete** the content from the Nostr network; it can only remove its own index entry or display.
Under German law, this matters because:
1. A provider that does not *host* content has **even weaker liability** than one that does.
2. The aggregator is closer to a **pure search engine** (Paperboy doctrine) than a hosting provider.
3. The aggregator is not "making the content its own" (*zu-eigen-machen*) by aggregating public relay data.
---
## 5. What the Notice *Does* Legally Accomplish
Despite its flaws, the notice is **not entirely without legal effect**:
> ⚠️ **This notice constitutes formal "knowledge" (*Kenntnis*) under German law.**
From the moment the aggregator receives this notice, it can no longer claim ignorance of the alleged infringement. Under the *Störerhaftung* doctrine and the DSA's notice-and-takedown mechanism:
- If the aggregator **fails to act** after receiving this notice, and a German court later finds the content unlawful, the aggregator **could become liable** for continued display.
- The aggregator should therefore **assess the merits** of the underlying claim (is the content actually unlawfully identifying the person under German personal rights law?).
---
## 6. Summary Assessment
| Issue | Assessment |
|---|---|
| Is the aggregator bound by the Reddit judgment? | **No.** Judgments are inter partes; the aggregator was not a party. |
| Does the aggregator host the content? | **No.** It aggregates from public Nostr relays — analogous to a search engine. |
| Is the aggregator a primary infringer? | **Very unlikely.** BGH *Paperboy* doctrine protects aggregation/linking. |
| Does the notice create any legal obligation? | **Yes, conditionally.** It triggers the notice-and-takedown mechanism. The aggregator now has knowledge and must assess the claim. |
| Is the content actually unlawful? | **Unknown — must be assessed independently.** The notice's claim that it "unlawfully identifies" the person needs to be evaluated on its merits under German *Persönlichkeitsrecht* (§§ 823, 1004 BGB). |
| Is the notice legally sound? | **Largely not.** It misrepresents the effect of the Reddit judgment on third parties and conflates hosting with aggregation. |
---
## 7. Recommended Response
The aggregator should:
1. **Not simply comply** based on the Reddit judgment alone — it has no binding force here.
2. **Independently assess** whether the content actually violates German personal rights law (*allgemeines Persönlichkeitsrecht*, §§ 823 I, 1004 BGB).
3. If the content is **clearly unlawful** (e.g., doxxing, false statements of fact), remove the index entry from the aggregator's display to avoid *Störerhaftung*.
4. If the content is **not clearly unlawful**, respond in writing that the aggregator is not bound by the Reddit judgment, is not a hosting provider, and operates as an aggregator/search engine under the BGH *Paperboy* doctrine and DSA Art. 6.
5. **Seek German legal counsel** if the plaintiff escalates, as personal rights (*Persönlichkeitsrecht*) claims in Germany can be pursued aggressively and courts can issue preliminary injunctions (*einstweilige Verfügungen*) quickly.

2026-06-03 22:09:58 CEST

- reply

Best David Hasselhoff song ever

2026-02-22 09:13:26 CET

- reply

The next round of hopium.
In reality, Agents choose predominately x402. and that means USDC on Base

2026-01-19 20:46:45 CET

- reply

Wie im 2023 erschienenen prophetischen 📖:
https://bastei-luebbe.de/Buecher/Krimis-Thriller/Abaddon/9783757700096

2026-01-18 20:06:12 CET

- reply

Yes

2026-01-18 09:20:12 CET

- reply

This exists in Europe as well. 🇵🇱
https://bitblik.app/
@nprofile…c3df

2026-01-11 21:35:26 CET

- reply

And that's great.
But that's totally unrelated to it having a bad UX. Unless you believe in some catharthic bullshit that for all good things you have to suffer

2026-01-11 20:48:03 CET

- reply

Nostr is the only social media you need a fucking manual for to have it even remotely working
#nevent1q…cnrp

2025-12-26 18:02:02 CET

- reply

Great in theory, in practice it will just be a massive centralization pressure, as only a few professional relay operator can afford to and operate a TEE + attestations.
The sober truth is:
Nostr architecture is just bad for social media-style use cases. DHT style messaging would be much better

2025-11-18 13:01:05 CET

And imagine being a Bitcoiner and celebrate this shit cuz "n0 c3nsOrsHiP"
#nevent1q…zyju

2025-10-29 19:28:37 CET

Tailscale Services looks really interesting:
Tailscale Services lets you assign stable virtual IPs (TailVIPs) to any logical resource—databases, internal APIs, even whole clusters—so you never renumber when servers move or scale.
Each service gets automatic HTTPS certs and fine-grained ACL tags, cutting both setup time and attack surface
CC @nprofile…7lnk
https://www.youtube.com/watch?v=mELAg50ljSA

2025-10-25 20:03:35 CEST

- reply

{
"code": 401,
"message": "All addresses failed: Error connecting to ln.damus.i
o: Tor server reply: general SOCKS server failure. ln.damus.io:9735
: Connection establishment: Connection refused. Error connecting to
24.84.153.116: Tor server reply: general SOCKS server failure. 24.
84.153.116:9738: Connection establishment: Connection refused. "
}

2025-10-21 06:58:11 CEST

- reply

Blitz does use Spark..

2025-09-23 21:18:45 CEST

- reply

Re 1) Frigste may he a solution (for those running a node already)
2) post-mix hygene is always as issue, amd has to be solved on the app level imho. I dont see how this can be addressed onchain
#nevent1q…y7q7

2025-09-16 20:49:41 CEST

- reply

Ok i see, but what's and how things are getting clustered into a certain AS is important. These are all just heuristics; for instamce just because several nodes share the same AWS region doesn't mean they are one AS, and that you shouldln't connect to more than one.

2025-09-16 20:42:01 CEST

@nprofile…gz0c may like this:
https://youtube.com/watch?v=g5BMI88QO_w

2025-09-14 13:24:28 CEST

- reply

>The number of knots nodes i'm connected to has dropped off a cliff. fascinating.
>I also ban all aws nodes from my node. surely a coincidence.
Are we not splitting hairs? ASmap makes you disconnect/not connect in the first place to a set of nodes, which is defined in the dat file.
Maybe it's not technically an (ip) ban, but the dat list acts de facto as a "shun list" the way i see it.
Please correct me if i'm wrong.

2025-09-14 12:18:12 CEST

- reply

I understand that the *intent* of Asmap is righteous; but at the end of the day your are banning/closung connections to peers that are "on the list"
I just hate everything about it. Pseudo-scientitic labeling of "good vs bad" peers. We'll get a risk score next

2025-09-14 11:25:19 CEST

- reply

How is ASmap heuristic node clustering much different from Chainalysis' heuristic utxo clustering??
Both are applying (questionable) heuristics to some public (or private) metadata;
Are Bitcoiners really advocating for the use central banlists* now? REALLY??
🤮
*yup, it's literally downloading a list from https://github.com/asmap/asmap-data/blob/main/latest_asmap.dat . But i'm sure our beloved governments will provide such a curated peer list going forward... 🤦

2025-09-09 16:54:02 CEST

- reply

You don't have to use it for Silent Payments. It's a separate sub-wallet.
Alternatively, use CakeWallet

2025-09-03 19:31:02 CEST

- reply

Yes, they should have stayed put, or slightly increased the limits. But they didn't act rationally and totally insecure, pushing this through just to prove a point.
ZKPs don't need that much data; fun fact, Citrea, cited as ine of the beneficiaries, rather uses Inscriptions instead of the op_return. Core burned all their social capital, and it was all for nothing.
At the same time, they are stalling what would be the right way to enable proper two-way pegs and thus scale bitcoin: CTV+CSFS.
It all makes no sense 🤷 (unless one subscribes to the theory this was a deliberate sabotage)

2025-09-03 18:24:40 CEST

- reply

Dude, they are literally simply asking for a setting to remain as it was for over a decade.
And bitcoin was obviously working just fine that way.
You are totally turning truth by 180°.

2025-09-03 09:00:43 CEST

- reply

One can just chieve the same thing with SQL against the database, right? 🤷
Can even fling a nice BI dashboard on top..

2025-08-29 18:23:35 CEST

🇩🇪Stoppt die #Vorratsdatenspeicherung 2.0! ⚠️ Die EU plant radikale Massenüberwachung.
Deine Stimme zählt: 📣 Nimm bis zum 12.9. an der EU-Anhörung teil.
Mit unserem Cheatsheet verteidigst du in 5 Minuten deine Grundrechte: 🛡️
https://www.vorratsdatenspeicherung.de/content/view/804/79/lang,de/
Via @echo_pbreyer

2025-08-27 21:00:58 CEST

Anyone watching #EuroBasket2025 here?
#MakeYourMark

2025-08-27 21:00:14 CEST

- reply

Hmm, I didnt see that response in Amethyst. Only Primal.
Tbh, Nostr and relay mgmt is a book of seven seals to me. It's gotten so fucking complicated with all these different relay types...

2025-08-27 08:24:06 CEST

- reply

Do you see this?

2025-08-26 18:33:40 CEST

- reply

Few.

2025-08-26 18:32:10 CEST

- reply

Asking permission is seeking denial.

2025-08-26 18:31:05 CEST

- reply

BSV? 😂

2025-08-23 07:37:40 CEST

- reply

Go apk only. It's a loosing battle trying to appease the big app stores.
Users needs to learn Zapstore, Obtainium

2025-08-22 11:54:22 CEST

- reply

If it includes the development angle as well, yes. And mining ofc

2025-08-21 09:31:07 CEST

- reply

Yep, i already have Obtainium (and Aurora, and F-droid, and Accrescent 😉). But you occasionally run into conflicts if you switch between different stores for updates (at least I have), hence I try to stick to Zapstore as my goto app store for bitcoin/nostr things

2025-08-20 20:02:38 CEST

- reply

Or not serving (ie relaying) 4MB jpegs

2025-08-20 20:00:23 CEST

- reply

"Not in The Prophecies: Practical Attacks on Nostr
Security Analysis on Nostr"
#nevent1q…uccw

2025-08-20 19:34:45 CEST

- reply

Wait when this happens on OP_RETURNs
#nevent1q…t8tl

2025-08-20 18:07:07 CEST

- reply

Thanks! Upgrading Amber to 3.4.6 did the trick.
For some reason Zapstore did not automatically list the Amber update possibility -- unless I specifically selected the app

2025-08-19 14:56:36 CEST

- reply

#asknostr
#nevent1q…svjx

2025-08-19 12:43:38 CEST

LOL, @nprofile…jtu6 perfectly called this on RHR.tv
👇
"Tether Appoints Former White House Crypto Council Executive Director Bo Hines as Strategic Advisor for Digital Assets and U.S. Strategy"
https://tether.io/news/tether-appoints-former-white-house-crypto-council-executive-director-bo-hines-as-strategic-advisor-for-digital-assets-and-u-s-strategy/

2025-08-18 07:14:00 CEST

Login with Amber on Primal doesn't work. Anyone else with the same problem?
It just opens the Amber app Activity page, but nothing else.

2025-08-10 14:04:59 CEST

- reply

why no one is getting laid anymore

2025-08-09 06:25:05 CEST

- reply

I also predominantly (well, only) use My Follows.
But if I only log in every few days I will almost certainly miss some interesting post from my follows -- which in turn raises "frustration" w nostr
I would totally use an algo feed that's just the popular posts and discussions from my follows since my last login

2025-08-06 17:07:38 CEST

- reply

Hmm. It is less engaging (true), and thus you log in less often - and will miss a lot of posts, potentially some of the (few) really interesting ones.
I would love a For You algo feed on Nostr, then i can literally just check every few days and check what I missed

2025-07-31 16:08:25 CEST

- reply

For own tweets, yes (ideally).
For other ppl's tweets, I would like to re-post the Tweet on Nostr - not just the x.com / xcancel.com link. Maybe screenshot + link is the only way

2025-07-30 16:56:18 CEST

What's the best tool/methods to share
1) your own
2) someone else's
Twitter posts on Nostr?
#AskNostr

2025-07-19 21:17:52 CEST

- reply

Unrealated to the Space, but have you seen this:
How Lightning’s Routing Diminishes its Anonymity" (ARES 2021)
?
https://arxiv.org/pdf/2107.10070

2025-07-19 20:21:20 CEST

- reply

It was a pretty good convo; listened the full 4h live 🙏
Two constructive comments:
1) I think you had some misrepresentation on Phoenix:
-> you cant have channels with other peers than acinq. Thus they know when and how much you are paying and receicing, and since they are your trampoline also the destination. It's a convenient wallet, but not very private.
2) On the UX section: both of you ignored that you can deterministically send any amount with Monero (or any other blockchain for that matter), while with LN the larger the payment the less likely it succeeds. LN payments generally have this 'Please please go through' vibe to it.
That's objectively worse ux

2025-07-19 19:53:42 CEST

- reply

https://image.nostr.build/af59c1fa42caf4072c924faeaeec57e883149d5e003d3bba09fb00f1dde40752.jpg

2025-07-14 21:48:21 CEST

- reply

👀
#nevent1q…0s45

2025-07-13 14:01:30 CEST

- reply

Not every single, just the big ones - which most users subscribe too. Probaly less than 20. It's not impossible.
Ideally ppl would publish to their own respective relays, and clients would find them via DHT-style discovery. But that doesnt scale I guess. Hence the current middle ground (some big relays as central access point for 95% of notes)
#nevent1q…tec0

2025-07-13 13:56:26 CEST

- reply

Yep. Exactly like you could always host your own blog + RSS in the old days - except no kne/very few would find you.
Censorship is not about 💯% prevention, but throttling reach (substantially). Reach is the currency of the internet.
And the Nostr network is not immune to that at all (albeit less suceptible than fully centralized platforms, obvs)

2025-07-13 10:09:59 CEST

- reply

Explain.
Assuming you are a persona non grata (the main relays not allowing your notes), would Outbox relays also not censor you? Aren't we just crossing our fingers they won't do that?

2025-07-12 16:43:24 CEST

- reply

Well akshually they could. i.e. the main relays refuse to store notes from your npub.
Ofc you can publish to your own relay, but whst are the chances normies are connected to it?

2025-07-08 19:52:22 CEST

- reply

Great movie! I may have just torrented it the other day 😇

2025-07-06 20:50:27 CEST

So, Nostr reports I have 0 followers.
And people wonder why it's "NOT TAKING OFF" 🤪😂

2025-07-06 20:47:07 CEST

- reply

Best product on ze internet. And not bootstrapped by VCs or gRaNtz

2025-07-06 20:44:45 CEST

- reply

Three days ago. And two days before.

2025-07-06 20:42:05 CEST

- reply

Oh, he knows
#nevent1q…jrhs

2025-06-22 20:51:47 CEST

- reply

Will take a listen. Any particular recommendation?

2025-06-22 19:44:02 CEST

Peak Eric Adams = best metal singer of all time. There is no second best.
Fight me.
#Metalstr https://image.nostr.build/bca0e7fd9b0b15bdb0e09bf01b8cd18e37f05e6b07012bf2b66340e63f02914e.jpg

2025-06-22 10:26:14 CEST

MAGA fanbois suddenly deciding to "opt-out" and taking "a stance from the sidelines" is hillarious

2025-06-17 00:05:38 CEST

- reply

Have you been to The Big Smokers in Holešovice?

2025-06-17 00:03:55 CEST

- reply

They have announced over a year ago that they are winding down their custodial wallet (in favor of their self custodial Alby Hub), and gave users a year long notice period - all the while communicating this repeatedly through all channels.
These ppl complaining now were living under a rock, and turned a deaf ear on all the emails and comms. And certainly never used the wallet either.

2025-06-16 20:00:01 CEST

- reply

Does India let foreigners study at its universities (generally speaking).

2025-06-15 17:11:03 CEST

- reply

But then only have unannounced = unroutable channels, righr?? Else peers will likely force close

2025-06-15 13:10:29 CEST

- reply

That's absolutelty possible. You just need to enable gossip
./run_electrum setconfig use_gossip True
"This will allow you to open lightning channels to any other node instead of just the following hardcoded trampoline nodes."
Source:
https://electrum.readthedocs.io/en/latest/swapserver.html

2025-06-14 20:53:17 CEST

@nprofile…vdjx just read about the submarine swaps, and to my shame, I haven't closely followed Electrum in the past.
Question:
Is it practical to use Electrum Lightning (unannounced channels only) without running it in always-on daemon mode? e.g. just on desktop

2025-06-14 08:08:07 CEST

- reply

Spam? These are vaild transactions 😁

2025-06-13 21:44:12 CEST

- reply

If you're circle jerking, you have one hand less for coding.
It is known!

2025-06-13 21:42:19 CEST

- reply

If you have to ask, you're probably rekt 😉
Last time I did it was like 1-2min

2025-06-13 13:06:52 CEST

- reply

https://stacker.news/items/1001011

2025-06-11 08:21:23 CEST

- reply

Monero community's approach is interesting:
1) Devs pitch their feature/project to the market (users), apply for funding.
2) Users vote with their money.
3) ➡️Features that are actually desired by the community get developed

2025-06-11 07:43:47 CEST

Bitcoin Core dev proposes to convert Core into a walled garden, membership-only repo.
🤷
All because every once in a while there is actual work to be done moderating a PR (btw something, for which already a full-time paid grant by @nprofile…uazd exists)
The more I read such nonsense coming out of Core, the more I think that giving Devs effectively a tenure (through Chaincode, longterm grants Brink, OpenSats etc) is part of the problem, not the solution.
"We want to do our thing, amongst ourselves, not be subject to public scrutiny. But please keep paying us."
Discuss.
---
cc @nprofile…f670 @nprofile…jsen @nprofile…tacz
https://gnusha.org/pi/bitcoindev/CABaSBax-meEsC2013zKYJnC3phFFB_W3cHQLroUJcPDZKsjB8w@mail.gmail.com/T/#u

2025-06-05 20:03:19 CEST

- reply

Via @nprofile…3478?

2025-06-05 19:58:43 CEST

#ICYMI: Recorded live from the Litecoin Summit, this privacy panel with BasicSwap's
@thegreatestdoc
explores the importance of privacy in decentralized systems, how privacy-preserving tech evolves to fill pragmatic needs, and more!
Don't miss it 👉
https://www.youtube.com/watch?v=hy4bPyRO6no

2025-06-04 21:46:50 CEST

- reply

describe op-return_PR;
#nevent1q…znyz

2025-06-04 21:45:17 CEST

- reply

Floppy, destroyer of hope 😂

2025-05-28 06:44:47 CEST

- reply

Stay humble and use them. For payments.

2025-05-26 20:44:46 CEST

- reply

My point is: it would take decades for Bitcoin to reach its (full) monetary potentisl, since fiat currencies fail gradually across the world.
At the same time it would take only a few years of constant spam for Bitcoin to be abandoned by disillusioned node runners.
It could fail wayyy before it even reaches your $300trillion market cap. The gambler's ruin fallacy

2025-05-25 23:47:52 CEST

- reply

That should be a no brainer consensus.
#nevent1q…dnjj

2025-05-25 23:44:04 CEST

- reply

>And if Bitcoin transactions can't outprice >JPEGs in the long run, then it's just not that >valuable.
The demand for *arbitrary* data is gigantically larger than monetary data. Bitcoin the money will never be able to compete with that, and expecting it to do so is just stupid.
Especially if we take the time dependency into account. The monetary use case proves its value in the Long Run (as fiat systems gradually start to fail one by one in the future).
But by the time we reach the point we actually need it, it could well be already dead - because it was just dominated by garbage in the meantime and ppl stop running nodes for this type of junk.

2025-05-25 23:21:56 CEST

- reply

Exactly.
Yet So many gigabrain mental gymnastics to argue that "Bitcoin is technically ™ just a database"

2025-05-22 08:59:21 CEST

GM. Was doing BOLT12 ⚡before it was cool.
Anno 2021 with @nprofile…44wp , via c-lightning command line. It was literally the main reason why I was (and still am) running a CLN node
Glad to see it's finally becoming more and more popular

2025-05-17 23:46:33 CEST

- reply

it’s also disappointing so many bitcoiners use fiat more than Bitcoin

2025-05-17 23:40:55 CEST

- reply

👀
#nevent1q…s7qe

2025-05-17 21:50:40 CEST

- reply

I mean, I wouldn't mind some more intelligence in bitcoin, and Core 😝

2025-05-17 21:48:19 CEST

- reply

You're missing an Espresso macchiato on your desk 😁

2025-05-17 18:46:29 CEST

- reply

Can't wait for 1MB jpegs on Bitcoin nodes
#nevent1q…9dte

2025-05-17 17:21:12 CEST

Are there any Bitcoin node projects that set everything up with Ansible?
If not, is there any good reason why not?
Genuine question

2025-05-16 10:02:33 CEST

- reply

Yep..
Are you planing to still also code up also the unhappy path?

2025-05-15 12:48:01 CEST

- reply

Wen daemon? 😇
Lightning Network Blinding Daemon (LNBD)

2025-05-11 20:20:12 CEST

- reply

Accurate description. Yet there are two claims that just contradict each other and cannot be squared:
1) consensus and (mempool) policy are truly separated.
If so, then the latter is up to each client implementation - or rather each individual node config.
If we believe that ( I do, and based on your comment so do you ) then we *must* accept node runners' autonomy over their mempool. Even if it means that it will no longer reflect the perfect world for dependent layers/system (e.g. lightning)
2) there is an objectively "optimal" mempool (the one that 99.99% approximates of what will be mined by miners) that should be adhered to by all nodes.
If that is the case, then the policy settings of the 95%-dominant client are *effectively* like consensus. And should be subject to the same level of scrutiny as a consensus changing soft fork.
What bothers me in the current discussion is that Core try to have *both ways*. They (Lopp being the most vocal) claim it "just a policy setting", i.e. #1, where plebs dont get a say since it is Bitcoin Core dev business. And at the same time claim that we have to have a "common mempool" (i.e. #2), too, because otherwise it would be detrimental to the overall network
So which one is it???
If The Mempool™️ is a common (#2), then you must allow broad discussion. And you should really make it part of protocol consensus.
Otherwise let people run their own settings and leave them be.
tl;dr You can't have your cake and eat it too.
----
Detour:
What really happened imho is that Core and layer2 devs have always banked on the implicit assumption that mempools are virtually identical among nodes - because they all ran the same software, with the same default settings.
They are now caught with their pants down, as this was always a lazy assumption (one I would have made too!! not prentending to be smart here), and are trying to force the reality fit the model.

2025-05-10 19:32:11 CEST

- reply

There is a clear separation between 1)consensus and 2)policy. The latter being each client's decision - this has at least been the argument of Lopp & co on why they can bypass "broad consensus ™️" in the ecosystem.
Let's entertain that thought. It works perfectly well in Lightning land: multiple implementations, adhering to the same base protocol rules ("consensus"), but differ in certain features ("policy").
Why is that/or not a model in Bitcoin mainchain land?

2025-05-01 08:29:21 CEST

- reply

Bitcoin Core is the dominant (really only) client in the ecosystem. It's maintainers this have the additional duty of being good stewards of the network/project as a whole - of they want it or not.
1) With that market dominance default configs matter as much as consensus rules.
But they are not just proposing to change/disable data carrier, but to remove this option completely -stripping users of the very choice to configure their mempool if they do choose.
2) What about miners? Adam Back correctly points out that through mempool policy miners construct their block template. Core physically removing this option will have make impact. First miners realize this, and speak up like Bob Burnett. Maybe @nprofile…xafw also cares. https://image.nostr.build/98f8088b2694caf9055bf779eff6e51ce9a9181bf2ae98eb19bfc10bb932808c.jpg
3) Loop and others made it clear that user concern *does not matter* - that Core contributors *alone* can discuss on this!
Plebs are to shut up and dribble.
Before the GitHub comments were locked there was a clear 4:1 ratio of commenters REJECTING this change. But Mr @nprofile…8lp0 says they don't get a say.
This is a violation of the (unwritten) rule of being good stewards.
How does Ten31 see this? Are you supporting and endorsing such behavior?

2025-04-29 19:30:23 CEST

- reply

Not sure you guys realize how arrogant, snobbish and elitist this comes across.
"Shut up and dribble you plebs! The Pros will handle this. This is Devs-only business!"
You *will* the support of the user base, if such important changes are just pushed through by a handful of ppl - while other changes (which you may not like) are filibustered for yearz.
And snarly sentiment a la "Good luck with your fork" just confirms this. Disappointing.

2025-04-29 12:51:46 CEST

- reply

So since stupid drama is out now, we're can finally get CTV+CSFS done, right??

2025-04-29 12:05:52 CEST

- reply

NixOS? Can you share a link?

2025-04-29 11:32:34 CEST

- reply

Thank you for the response.
Re Citrea. While they might be further along, it's still far from the usual rigid requirement, and certainly not an operational product.
This just makes the whole reference to and argument for Citrea in the OP mailing list incredibly weak (and dangerous imho)
Re: GitHub
First, I disagree that this qualifies already as "harassment". It's a valid, albeit dissenting argument, which should be able to be presented at the main stage.
Second, resorting to fine print bureaucract arguments for blocking ("Oh you should not have discussed this here's but in the line over there") makes Core look incredibly weak and insecure. Especially without warning/notice.
You must see that.
This is not the way trustworthy stewardship of a critical FOSS project looks like.
Even benevolent dictators must be benevolent to not lose support from Us the People.

2025-03-18 09:21:17 CET

- reply

Vielleicht würde sie gewählt (und wird bezahlt) um die Interessen des Landes zu vertreten, nicht die der "Bitcoiner"? 🤔🤷

2025-03-08 19:54:09 CET

- reply

I still remember seeing that @nprofile…azkh post from 2(?) years ago and immediately went and traded some. The rest is history.
♥️ Robosats