Vancouver on NYE!

No

Collectivity of people willing others by violence, also called "democratic" statism.

Yes, I consider statism a form of fascism with better marketing.

#39c3

✨Merry Christmas✨

Let’s carb load for January’s nostr:nprofile1qqs0t3y6x90j7h9zm6ljsgch3mx64jqehtrrhmgzdvf57t3pccnxgwsprpmhxue69uhkc6t8dp6xu6twvaex2mrp0yhxxmmdqy2hwumn8ghj7mn0wd68ytndv9kxjm3wdahxcjx724t 😊🍰

Unfortunately, I declare Firefox for Android unusable at current state. It just stops working and rendering pages and needs complete reset after some time.

I'm not the only one with this problem.

Too bad, I've been using some extensions (although the problem occurs also without extensions) and I like the send tab to desktop feature and local on device translation.

Using Vanadium for now.

The Breez SDK has added privacy to Spark, but since there are several implementations, I don't know if others have done so.

Spark fees are 0.25% when sending to LN and 0.15% when receiving.

But again, I'm not sure which implementation each one uses, so fees may vary.

nostr:nprofile1qqstxwlea9ah3u6kjjszu6a7lrnhqkfh8eptp2z6v0e9558tlkkl2rgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wfjkccte9ekkjmnfvf5hguewvdshx6p0qythwumn8ghj7un9d3shjtnswf5k6ctv9ehx2ap0wsvavr i just tried your app is amazing, great UX.

So many changes in v0.12.0! 😅

We’re very excited to roll this one out to app stores in the coming days.

I like Marmot, but it is very complex for clients to implement. It's not going to have widespread support in nostr.

Any need for a large shared lib in nostr is doomed to fail.

I've got a serious questions about the use of spark services in nostr:nprofile1qqstu8vf099ljt09m4jvres0dgk8ps2q4wkfjvjp3lhrp3wxxllfg7gpramhxue69uhkummnw3ez6vpn9ejx7unpveskxar0wfujummjvuhsz9mhwden5te0wfjkccte9cc8scmgv96zucm0d5hszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcmnwfft .

nostr:nprofile1qqszrqlfgavys8g0zf8mmy79dn92ghn723wwawx49py0nqjn7jtmjagpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7sujtmp 2 months ago posted a note to show how you can watch all transactions of a users in case you had previously sent him some sats.

I think the only useful info you can retrieve is the amount of the wallet, is it correct, or you can deduct any other information?

How can you force a unilateral exit with your twelve words?

Is the seed phase a bip39 or is a custom format?(I think the second one)

I see there is a fee of 2% on each inbound onchain transaction, this mean the wallet can not act as normal onchain wallet.

Are there any other hidden cost when you transact via lightning or fees are just the normal lightning routing fees?

CC nostr:nprofile1qqs0eac2gh86s9l24qfmnw52xawhz0f3d862yleaetpafygjmanaxlspzdmhxue69uhhqatjwpkx2urpvuhx2ue0qy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7ramexg

#asknostr

no love for marmot?

We traveled “in bitcoin” before it was a thing.

Me and Rikki started “Bitcoin Explorers“ in El Salvador in 2021, then kept moving: Central America, Asia, the Middle East, Europe, Africa. And I’m not saying this to flex. I’m saying it because the timeline is the timeline. The content exist. The story speaks for itself.

Now. El Salvador was an engagement cheat code (and everyone knows it).

The uncomfortable truth: when we posted El Salvador content, everything grew faster. Like… four times as fast.

My tweets got reposted by Bukele. I got 4000 followers in a day for this picture you see here.

Our videos about El Salvador hit 10k views while being shot like amateurs (because we were amateurs). We weren’t filmmakers. We weren’t a production studio. We were just there, documenting what we were seeing with the tools we had in the most honest possible way.

If we wanted, we could’ve turned that into a visibility machine.

We didn’t.

Because we didn’t want the easy path. We didn’t want to go where everyone goes just because it performs. We didn’t want to become a tourism brochure for an algorithm or even worse, a government.

And eventually we had to admit something most people won’t say out loud: realistic reportage takes time, money, and resources. We didn’t have enough of them to keep doing it the way we wanted...properly.

So we stepped back. I found other jobs I'm super happy with and my voice remained independent.

Now let me ask you something. genuinely.

Why do you think so many Bitcoin creators focus on El Salvador? Why do you think so many creators post about it like it’s the only place on Earth where Bitcoin exists?

Because it’s simple:

- Post a beach breakfast and you get quadruple the reposts of a normal post.

- Post a critique? You risk getting dogpiled, losing followers, losing access, losing 'opportunities.

That’s the part people don’t post.

And yes: there are people in the space who will make it personal, who will lean on social pressure, who will remind you that stepping out of line has a cost. I’ve seen and heard enough to know the incentives are real even if nobody wants to say it clearly.

The saddest part is who ends up paying for this illusion: not the insiders. Not the people doing the reposting. Not people who threaten you over tweets.

It’s the people at home:

- liking

- retweeting

- booking flights

- buying tickets

- chasing a “ Bitcoin paradise” that mostly exists in social media posts apart from a few exceptions and small communities

A lot of content creators aren’t documenting reality. They’re documenting what the algorithm and their paycheck rewards.

And at that point… what’s the difference between them and the journalists they love to hate?

Same dynamic:

- follow the narrative

- repeat what powerful people want amplified

- avoid the messy parts

- monetize the attention

Different ecosystem. Same playbook.

We didn’t want to be that. We could’ve milked it. We didn’t. Not because we’re morally superior, spare me that story.

Because it didn’t fit who we are, and it didn’t fit what we wanted to build long-term.

If I’m going to talk about Bitcoin “in the world,” I want it to be real:

- not just the pretty parts

- not just the safe parts

- not just the parts that get you reposted by the right accounts

Reality is complicated. Adoption is uneven. People are people. Politics are politics. Incentives are incentives.

And if your content never shows the trade-offs, the friction, the contradictions… then you’re not educating anyone. You’re doing marketing.

❤️ If you’re new here, read this twice: Bitcoin doesn’t need fairy tales. It needs adults.

It needs people who can handle nuance without turning it into a loyalty test.

So next time you see a creator post a perfect “Bitcoin country” shot, ask yourself:

- What are they not showing?

- What can’t they say without losing access?

- What gets rewarded here. and what gets punished?

The algorithm isn’t truth. It’s the incentive map. And most creators are just following it like obedient little tourists.

LDK ha tutte le funzioni per interagire con LN, non è una vera e propria “implementazione”

Esatto! LDK è il Lightning Development Toolkit, ovvero una serie di librerie che permettono di integrare Lightning in maniera semplice e veloce!

Ad oggi non ha una sua implementazione completa di un nodo (ma dovrebbe essere in programma, riprendendo il lavoro fatto su sul progetto ldk-server, se non sbaglio)

private note storage spec would be perfect for this

seriously how is this not a thing!? nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is noone doing giftwrap stuff?

nostr:note1sp4xegfn2fhqd3rq8w25my47q4qydwcc8rudhazkxfq83v9y7yhsssxp9l

I didn't check, does bitchat connects to relays in background nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg?

That's the only work done by Pokey in background, keeping an open WS is expensive.

They can only enforce this on centralised platforms. Nostr is safe, although we might want to start utilising Tor & i2p a lot more, get ready for when everything needs to be onion routed.

We dont hate core enough

Today marks the start of Rizful’s “30 Days, 30 Devs” initiative.

From September 21st through October 20th, 2025, we’ll highlight one Nostr developer each day and thank them for their work with a zap of 100,000 sats.

We’re kicking things off with a zap to nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 — whose early vision and relentless building helped make Nostr what it is today.

Thanks nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 ! Your 100k zap is sent!

Please help us with this initiative .. simply reply to this note with the pubkeys of any devs you would like to see zapped. Don't be shy, we've got 30 days!

running v29.1 with those defaults as well. if people want to fill empty blocks with cheaper txs then why not

I also find the criticism Apple receives amusing, especially from people who use Windows.

I guess you don't know that macOS/iOS is open source, except for the graphical environment and applications such as Pages, etc.

The entire kernel and OS environment is open source.

Projects such as WebKit (Safari engine), Swift, CUPS, libdispatch (GCD), mDNSResponder (Bonjour), launchd, among others, are also open source and from Apple.

Not to mention the contributions that the BSD ecosystem receives thanks to Apple, among others:

- Clang/LLVM: Apple promoted Clang/LLVM and maintains it as an open project; FreeBSD adopted it as the default compiler since FreeBSD 10 (2014).

- LLDB and the modern STL: the LLDB debugger (part of LLVM) and libc++/libc++abi were born at Apple (initially led by Howard Hinnant) and are now widely used in BSD.

- Grand Central Dispatch (libdispatch): Apple opened libdispatch, its concurrency library; there is a cross-platform version also used in FreeBSD.

- Bonjour / mDNSResponder: Apple's multicast-DNS/DNS-SD daemon is open and has a port/manuals in FreeBSD.

- CUPS: Apple acquired it in 2007 and kept it open source, used by macOS and other Unix-like systems; today its development for Linux is led by OpenPrinting.

- Swift: Apple's language is open source; since Swift 6.2 Apple announced official support for FreeBSD, and SwiftPM already supports the FreeBSD platform.

- Security (TrustedBSD/OpenBSM): macOS integrates the TrustedBSD MAC Framework (the basis for sandboxing), and Apple released/relicensed parts of OpenBSM that were integrated into FreeBSD.

When will Microsoft do this?

Interesting!

Oggi ho scoperto che nsec.all salva le private key su un suo server privato, si sono cifrate, ma questa cosa non mi piace affatto.

A Bitcoin conference in the mountains. #proofofwork