By the way, nostr:npub16v2dg43sg34m3r2tuw60zqv3t2a59pdr7mqq6vw4qg2wwsdljw0s4fenz8 is this true? Or is it just that OP_RETURN 80 byte is required for your system to work?

I believe Ordinals can solve it in the same way. An ipfs hash is only 32 bytes. It fits perfectly fine in a 40 byte OP_RETURN.

No need to panic about it, just store the meat somewhere else and keep using the blockchain for what it was meant for -- validation.

I meant Wasabi, sorry.

The whole Samurai vs Ocean saga.

nostr:npub15lmjekxgcl8337n0gnqnrcqatwyv9arhywjkvfh0x0tfjrn2nu2sgz2796

This is a non-issue, and it's beyond me why all the fuzz.

nostr:note1jlkjemhngjrpngzyeelmxkfddpe8g38tsfe0p5fspjvjss6n3rlq47xg64

nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk's rationale is "see? I was right." That's it. But there are no "right and wrong" when it comes to OP_RETURN.

That being said, Wasabi only has to implement storing the message they need somewhere else, hashing it and then store the hash in a 40 byte OP_RETURN transaction. The client validates the message comparing its hash to the hash stored in Luke's 40 byte version of OP_RETURN, problem solved, everyone happy.

It's an easy solution and takes minutes to develop.

I agree. Also consider that decoupling the components that make up the whole system might be the only way towards scaling things up on the long run.

It doesn't need to be a perfect system, it only needs to be anti-fragile.

The take is correct from an engineering standpoint.

"Every bit counts" used to be the motto in IT. Where it went?

Now, politics... I'll leave it to politicians.

If one could draw a funny figure in the middle of each frame, so that it looks like an animated cartoon with a "cloud of information" around, it would become instantly popular.

How much of what? If there is a "what" then you "own" that "what".

There is also the distinction to be made about when "owning" deserves quotes and when it doesn't.

When you own gold that you have in your power, then it is truly yours. Just an example.

This has been addressed by Veritasium in an excellent video about this particular light bulb and the actual conspiracy by Edison and supposed "competitors".

Yes, the creation of planned obsolescence as we know it today was a real conspiracy.

My interactions with nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk have always been pleasant.

I appreciate talented hard working people, and he is one of them.

Disagreements are normal in engineering. Don't make it personal.

Orange pill them.

nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg Having issues with nos2fox.

Home page doesn't load. Writing a comment accidentally hit the top and it was lost.

We live on blood sugar. Sugar is a carbohydrate. When you burn sugar those carbon atoms need to go somewhere, they are not destroyed.

We breathe CO2 out, plants breathe it in.

That's how this planet works.

You can plant a tree in a small pot, confine it to it for life, it will grow tall (as much as it can), and it will not consume the dirt. Very little carbon is taken from the soil.

We eat plants (or animals that ate plant), turn them into sugar, turn sugar into CO2, breathe CO2 out, plants breathe it in and grow, and so on.

No urgent serious transaction should depend on OP_RETURN > 40B.

Period.

Not Luke's or Ocean's fault. It's poor decisions in the design of the software that produce such transactions.

https://stacker.news/items/343322/r/nostrdev

nostr:note13junuyhmn8q70z0g4q74rssnvdwsgrvvdall9wgm2dpudc0d6uxsxu3f7t

nostr:note1fhnhpq52l9cuzep35vscmrdgvz4r93kducc7upzlnmqcte3cxm2styas84

Been busy working on this little tool with Chovy.

https://nostrdev.codeberg.page/follows-web/

Feedback welcome!