People talking about how millennials are so unlucky financially because of crashes and house prices inflation etc

Meanwhile we have the opportunity to own and understand the best performing asset in human history, earning returns in 4 years what took boomers 40 years to earn.

We can spin up businesses with a few AI prompts

We actually have access to information that isn't propaganda

We have it made, we are the luckiest generation

Miss me with that victim shit

“banks work” nostr:note10x4kfrmdzs9ggvkta6gx0n8gwxthj62hj3nskpxvcc8kv8se85qqevrznq

This isn’t what I’m up against, but thanks. It’s a great project. Without a lot of backend services, Apple devices are largely expensive bricks.

Let’s, for the sake of argument, say that I did want to jettison thousands of dollars of Apple hardware into an active volcano.

What are equivalent laptops and phones (I’ve seen no watches remotely close, but bonus if you know one) as measured by:

1. Build quality

2. Performance (component integration, speed, battery life, etc.)

3. Warranty and support (a la AppleCare)

4. Just Works™️ OS and applications

Before answering, kindly only chime in if:

1. You own the product(s) in question

2. You hearby acknowledge that, while I’m highly technical, I long ago lost interest in compiling my own kernel or wrestling with bootloaders. I’m a “business user,” not a developer. That’s my use case.

Please and thank you. 🙏🏼 #asknostr

With respect, while I don’t think the 80 byte OP_RETURN thing should actually be filtered because it’s a lot point by now, there IS a critically important difference between filtering and censoring in this context:

• One is a question of WHAT is allowed in the bitcoin chain, which is a universal policy. Every node does this and this is similar to arguments with RBF and the like. In a sense, this is the only thing bitcoin does, is filter with extreme prejudice, WHAT goes into the chain.

— there is an argument to be had on whether the byte issue is good/bad, but it’s not censoring privacy transactions or coinjoins. It’s a filter that *happens* to catch one kind.

• The other is a question of WHO gets into the blockchain. F2Pool here had the audacity to claim that a certain address, with a certain balance, is owned by some “evil” people because some govt body, without trial or due process, has declared their evil acts and demanded punishment & eviction from market activities.

Regardless of whether this particular kind of filtering should be considered good, or that it potentially sets a bad precedent, they are not the same thing in terms of the danger and subjectivity of the decisions.

Deciding WHAT goes into the chain is a process of defining the bitcoin system, deciding WHO can get into the chain is censorship and violating the basic tenant of neutrality.

The phrase isn’t “Bitcoin is for everything,” it’s “Bitcoin is for everyone. nostr:note14hm0a4xz7v5dmsmslj6h694vmnlytc59k4mv2s254clm3zdcpzmsujjv3x

If you care about actually mitigating mining centralization concerns then surely the answer isn't let's have luke unilaterally decide what is spam.

What if “fossil” fuels have absolutely nothing to do with decaying organic matter? What if the planet creates it by a normal geological process?

How would that single fact change your mental model of the world? 🤔 nostr:note1706ejgwqyzmmsp5wu0vznzx2yl8adnhlyns4mm4ydwdyrce5mpns8np78a

🤙

Can you put a link to the tik tok in the notes, I got peeps not on nostr i want to send these videos too, but I don’t have tik tok.

You don't have to have consensus to update a parameter. Your node. Your rules.

Okay a bitcoin transaction can be used to ferry a small amount of information around. Max 80 bytes. The specific way this is achieved is by using an operation in the spend script called OP_RETURN.

OP_RETURN has been highly controversial in days of Bitcoin yore, and before a cap was imposes, people used it to stick larger amounts of arbitrary data in transactions.

The OCEAN mining pool is coordinated by Luke's own alternative node implementation called Knots. Knots basically is Bitcoin Core with some feature patches and different default values applied. One of those different default values is 40-something bytes for OP_RETURN data. Why? Because Luke probably disagreed back in the day with 80 bytes in Core.

Samourai maintains Whirlpool, a non-custodial mixing service. Whirlpool generates transactions that utilize OP_RETURN to carry around some information about the mix round. That information exceeds Knots' max threshold, therefore those transactions never appear in block templates to the miners.

I think that's that gist of it.

Seems very odd that "experimental" things are being included in the "official" releases. Can't they have a beta version that's explicitly presented as such?