weird how my day tends to be 10x better when I see this

So I think there is an exception which is Bitcoin Block

Posted this years ago, never been so important.

|￣￣￣￣￣￣￣￣￣￣￣￣￣|

| THE CLOUD |

| IS JUST |

| SOMEONE ELSE'S |

| COMPUTER |

|＿＿＿＿＿＿＿＿＿＿＿＿＿|

(\__/) ||

(•ㅅ•) ||

/ 　 づv

👋 I’m in the process of learning Python and CS in general with the intent of eventually transitioning to a career focused on Bitcoin / Nostr.

I’ve got a background in electrical engineering, specifically in electromagnetic environmental effects. Studied Econ as well.

Looking to connect with devs to work on small projects and contribute where I can.

🤝

Cryptoanarchy is beautiful.

I agree. But cantilionares use the system against the no IP builders. GPL was a response to that. It's not a true freedom license.

To Inscription frenzy:

If something is Non-Fungible & Digital, then how can it be Non-Fungible.

Your inscriptions have zero value, Open your eyes.

I'll be shifting my focus ove to another micro-app to validate a few concepts, and then on to the next nostr.watch. Rebuilding nostr.watch has been a high-priority item since shortly after Jack lit a flame under nostr in late 2022, but due to personal circumstances in 2023, I was unable to tackle it. Thanks to @opensats I am able to realize my ideas and scratch the various itches that have been keeping me awake at night.

Most people don't dig that deeply but when they do, they have this question. Computers are 1s and 0s. They are digital. How can they be non-deterministic??

Software development mostly revolves around performance both in the end product and the development process. Only very few developers even spend a thought on reproducibility. So if they compile something and it compiles 5 seconds faster, they can test the feature they were working on 5 seconds quicker. These two reasons result in stuff being non-reproducible as:

Files are processed in the order they come and that order depends on many factors. For example some file systems sort by date and others by file name.

Compilers can optimize the result, so compiling something with one version of the compiler will often give a different result than when compiled with another version.

The compiler might process multiple files in parallel and pack them into the result as they finish compiling.

Other sources of problems are timestamps or file paths that end up in the result.

Some tools on purpose use randomnes to generate IDs that are unique to every build.

Of the above issues, all result in non-reproducibility by our standards. While some lead us to comment on the build looking benign as the diff is only some random number appearing twice, others might also be benign but result in differences far too big to quickly judge with the tools we are using.

The more developers care about reproducibility over only performance, the better it will get but there are some widely used tools that consistently cause issues and maybe should just be avoided in wallets.

Most people don't dig that deeply but when they do, they have this question. Computers are 1s and 0s. They are digital. How can they be non-deterministic??

Software development mostly revolves around performance both in the end product and the development process. Only very few developers even spend a thought on reproducibility. So if they compile something and it compiles 5 seconds faster, they can test the feature they were working on 5 seconds quicker. These two reasons result in stuff being non-reproducible as:

Files are processed in the order they come and that order depends on many factors. For example some file systems sort by date and others by file name.

Compilers can optimize the result, so compiling something with one version of the compiler will often give a different result than when compiled with another version.

The compiler might process multiple files in parallel and pack them into the result as they finish compiling.

Other sources of problems are timestamps or file paths that end up in the result.

Some tools on purpose use randomnes to generate IDs that are unique to every build.

Of the above issues, all result in non-reproducibility by our standards. While some lead us to comment on the build looking benign as the diff is only some random number appearing twice, others might also be benign but result in differences far too big to quickly judge with the tools we are using.

The more developers care about reproducibility over only performance, the better it will get but there are some widely used tools that consistently cause issues and maybe should just be avoided in wallets.

A public square that is owned by a corporation isn't a public square, it's a mall.

In case the obvious has eluded you nostr:note1k4tvhcld85ukgrxs9p7ej7tfa90svdh2jmglgwmg5p9g23zg5m5ssn7z5e