GN

a!

NWC (Nostr Wallet Connect) is amazing, let's you quickly connect lightning payments to anything you want.

Nepotism Bribery Suppression of free speech Lack of transparency Blackmailed Misinformation propaganda Elitism Bitcoin Core

All of you, keep doing what you have been doing, its going up. This feels like turning people into bitcoiners again.

i wanted to say: "don't trust people who know how to talk" but idk, maybe im wrong. idk. just came to my mind while sitting.

Bitcoin needs to be more like Nostr in terms of decentralization. - It is easy to run a relay. - There are many relay implementations and its easy to implement it yourself. - There are many client options, and its easy to make one. - You can run it on your phone easily. I mean Nostr is easy to isolate, and doesn't have double spending issues. But it would be cool if we were aiming for more efficiency. View quoted note →

The bad Bitcoin future: - Normies don't run a node - We do everything on L1 - L1 grows heavy - Nodes drop off - You trust public nodes - Validation becomes specialized - Custodial wallets dominate - Regulatory capture becomes easier - Bitcoin becomes financialized but not sovereign - We still have one major client and its org and devs - Miners decide the future of Bitcoin, because they are the only ones that has incentive to run nodes (which is a heavy process). Everyone loses, including the ones in control. View quoted note →

- bitcoin needs efficiency. - bitcoin needs less bandwidth. - bitcoin needs less storage. - bitcoin needs less barrier of entry. - bitcoin needs each user to be a node. - bitcoin needs efficiency. then layers like lightning and arkv2 or more. - more nodes = more decentralized. - everyone trusting their own full node they dont even realize they are running. - isolated lightweight layers. - tight and boring layer 1 timechain. - amazes you with how easy its to run, not how many things it can do. the good bitcoin future. if we get the bad one, idk what we are going to do.

Cool ECS frameworks/libraries with different approaches:

GitHub

GitHub - friflo/Friflo.Engine.ECS: High-performance C# ECS

High-performance C# ECS. Contribute to friflo/Friflo.Engine.ECS development by creating an account on GitHub.

GitHub

GitHub - Felid-Force-Studios/StaticEcs: C# Hierarchical Inverted Bitmap ECS framework

C# Hierarchical Inverted Bitmap ECS framework. Contribute to Felid-Force-Studios/StaticEcs development by creating an account on GitHub.

GitHub

GitHub - Juiix/EntitiesDb: A high-performance, cache-efficient Entity Component System (ECS) for C#. Features chunk-based storage, fast queries, source-generated iteration, multithreading, SIMD support, and zero external dependencies.

A high-performance, cache-efficient Entity Component System (ECS) for C#. Features chunk-based storage, fast queries, source-generated iteration, m...

bro these are not ai, nostr is filled with bots now. they don't think, say something important. just repeat you or spam like.

GM View quoted note →

great things come out of limitations limiting things to be efficient is good

bitcoin is going up forever, so save in bitcoin, and focus on your craft. don't gamble, don't borrow, just stack.

GN (or insult them, because explaining takes effort .-.)

OK GN i started to make many typos again, gonna sleep 😴

who doesn't like bip110? there is nothing unreasonable about it. taproot doesn't need OP_IF defeats the whole purpose of it. we don't need OP_RETURN bigger than 32bytes. bip110 is being way to generous with 80bytes. it fixes the problem, and breaks nothing. its enforcing what was the default in the first place. how could you possibly be against it? unless you wanna turn exploits and bugs into features.