Timja

Entries on a blockchain are auctioned of in an auction which allow arbitrarely low bids. So it is to expected that there is a long tail of bids with a low chance to win.

If a mempool clears, that just means there is limited demand to use the chain, even for free.

Before lightning was a thing, he anticipated the block size would increase over time. And he changed his mind when the idea of level 2 came up. Which was the right thing to do. But hard to understand at that time.

UX is a problem throughout all crypto. No matter which coin, no matter L1 or L2. It's all still like the internet before the 90s.

The question asked on that video does not mention lightning.

But his answer begins by explaining lightning.

Back early on forsaw that lightning is the way forward and not larger blocks. Which is another indication to me, that he is indeed Nakamoto.

It was a great insight very much in line with Nakamoto's thinking. Nakamoto who forsaw so many things early on like the need for a script instead of just transaction data on the chain.

Wikipedia says "Banksy is a pseudonymous England-based street artist, political activist and film director whose real name and identity remain unconfirmed and the subject of speculation."

Oh, interesting. So he only keeps his face secret, not his identity?

I remember reading an interview with Ozzy Osbourne who said he refused to work with Buckethead because it spooked him that BH always kept a mask on, even when they talked in private.

I think there is some systematic reason why people like Satoshi, Buckethead, Banksy, etc are not uncovered.

In each case, I doubt that it really is hard to figure out who they are.

Maybe it is the way the press and social media work. You get as many clicks for a wild theory as you get for a properly researched opinion.

As for Satoshi Nakamoto: The most obvious candidate seems to be Adam Back. His invention of proof of work, his biography, character, writing style and role as the CEO of the company behind the main wallet software all point to him. Also, his current communication "Bitcoin looks like something that was discovered rather than invented". That's something a creator typically says about a particularly great piece of work they did. Are there any arguments why he might not be the inventor of Bitcoin?

Most servers don't set a CORS header though.

So usually it does not work in the browser.

Try this in your console while not on Reddit:

    fetch('https://www.reddit.com/.json')

I would love a battery powered 32" E Ink screen that does nothing on its own, but lets me send it images to display.

But for that I guess I would have to give that thing access to my wifi? I wouldn't want that.

Any ideas if such a product exists and how one could use it shielded from the internet?

Not sure if the workload makes a difference.

We would have to make examples of what Computation1 is and what Computation2 is to make a prediction if certain types of workloads will impact the ratio of their performance.

Example:

    s=performance.now();
    r=0;
    for (i=0; i<1000000; i++) r+=1;
    t1=performance.now()-s;

    s=performance.now();
    r=0;
    for (i=0; i<1000000; i++) r+="bladibla".match(/bla/)[0].length;
    t2=performance.now()-s;

    console.log("Ratio: " + t2/t1);

For me, the ratio is consistently larger in Chrome than in Firefox. Which workload would reverse that?

There is no way to escape fingerprinting.

Just one example: A script which runs many different types of computations. Each computation will take a certain amount of time depending on your hardware and software. So you will get a fingerprint like this:

    computation 1: **
    computation 2: ****
    computation 3: **********
    computation 4: **
    computation 5: **************
    computation 6: ************
    computation 7: *********
    etc

There is no way to avoid this. You can make the fingerprint more noisy by doing random waits. But thats all.

My prediction: SQLite will keep gaining popularity.

Especially among pragmatic software builders who run their own business and do not work for the man. A demographic that I expect to grow.

Talking about SQLite: Is there any downside to partitioning an SQLite db into multiple files?

For example one of my systems has a table 'details' which is not vital for the system to work. It's just a nice to have, to have data in this table. And it is pretty big, growing fast.

When I copy the DB over to another system, I don't need that table. So it would be nice to have like primary.db and secondary.db. With 'details' in secondary.db. Any downside to this approach? Are JOINS slower across two files than across two tables in the same file?