Explanation of differences between corvettes, frigates, destroyers and cruisers (as recorded from a Quora discussion):

1/The next major problem set in #DeFi is #NFTLiquidity.

It has become very clear that, like fungibles, nonfungibles are their own financial asset class.

One path to see this is to envision the future of NFTs as “liquid

2/Some say that NFTs “shouldn’t be” liquid, yet the innovation process continues.

Just like photography has become much easier to create in the last 100 years, liquid NFTs will surely bring down price points of tokenized digital content but will also open expansive new markets.

3/The key observation is this: #NFTLiquidity is merely a technical problem for #DeFi, and the entire set of economic mechanisms is its solution space.

👉🏻 In particular, because of tokenization, *the NFT liquidity problem reduces to the NFT price discovery problem.*

4/In other words, if we could reliably price a set of NFTs, we could issue a token backed by their reliably priced future resale value.

This is a core mechanism that today is underutilized in the market, and one that — we will soon see — applies to all illiquid assets.

5/Today, NFT price discovery proceeds via three main mechanisms: sales, auctions, and ERC20 fractionalization.

And the fundamental problem with each of these mechanisms is capital efficiency: in each mechanism, participants need to spend *at least* $N to value something at $N.

Porting vanilla (minimal external API usage, no SIMD, no threading) C++ code to work in the browser with emscripten and WebAssembly is amazingly simple now. The Emscripten docs are excellent, but here are some things that could speed up the process of getting started:

1. Beware of code which does unaligned memory reads/writes (which "may be slow on some CPU architectures")
2. Test with -fsanitize=undefined -fsanitize=address
3. Link with "-s ALLOW_MEMORY_GROWTH=1" and "-s INITIAL_MEMORY=X", X is a multiple of 64k, allows the C++ heap to grow.

(I completely avoid unaligned memory reads/writes because when compiled to asm.js they "can fail silently".)

4. Link with "-s MALLOC=emmalloc" to reduce compiled size.
5. I usually test with -O1 because -O0 can take very long to load/execute.
6. For debugging link with -s DEMANGLE_SUPPORT=1 and -s ASSERTIONS=1

7. C++ printf() outputs to the Developer Console: Chrome Settings->More tools->Developer tools
8. If something crashes, try running in Firefox which may explain the error differently.
9. I use Web Server for Chrome for

Years before Andy Grove was attributed with the phrase:

"Whatever can be done, will be done"

A lot of us technologists assumed this was the case anyway.

It's a truism.

What if we could track every person on the planet in real time?

Or at least everyone in a major city

🤔🔮

So, given someone has this idea.

Then the only question is can it be done.

Well, we're already installing all the tech to do this for autonomous vehicles, drones and smart city infrastructure.

It really wouldn't be a huge leap to do that for people.

But how might that be possible 🤔

Sure we can already do it with phones right, but not everyone has a phone and sometimes the batteries die blah blah.

Could we do it in a way that it was difficult to circumvent, and always active?

Well, maybe we could if we put our thinking caps on about the problem.

--- this line intentionally left blank ---

Now I'm going to enter the wild world of wild speculative futurism, so take everything else with a pinch of salt 🧂

--- this line intentionally left blank ---

Turns out cell phone towers pinpoint the location of your phone as part of how they work.

And then as you move around you switch from one tower to another.

I think most people get this.

Something like the image below

Affidavit by former head of IT for large Italian defense contractor admitting he uploaded instructions through military satellite to Frankfurt to flip votes from Trump to Biden on election night under direction of US persons. Willing to testify.#ItalyDidIt