I came across this Andy Kirby guy on youtube, and his videos really came across as very sensationalized, exaggerated and clickbaity, which drew me away from meshcore, as I associated him with the project organization. This seems to validate my gut feeling.

> Kind of like how X is sometimes pronounced "sh" in Portuguese.

Including this case! México is still pronounced with the "sh" in Portuguese :)

That TAP data was leaked on a tor hidden service, in multiple files, and download was extremely slow on the days following the leak. One of the files was much smaller, and my friend had the bad luck to have his data in that one.

His phone was spammed so incessantly he had to change his number almost immediately.

AI for textures for over a decade? What AI?

Efros–Leung, PatchMatch? Nearest neighbours was "AI" before difusion models.

Don't you think it's a huge stretch to compare those to modern generative AI in this context? Those don't raise any of the questions that make current usage questionable.

> Fig IV: Throughput (toks/sec) and energy consumption (mWh/tok) across various hardware platforms.

I don't see any mWh/token figures in that chart.

For me the:

- Built-in dictionary - Being able to read anywhere, even when light is not available (on a taxi, for example) - Can fit it in my pocket - Less annoying to read while lying down in bed, and the page is automatically marked when I fall asleep - Adjustable typeface and font size

I feel the same way about the US. Can't imagine the vast wilderness you still have. I've never been somewhere truly wild and untouched by man.

> truly wild and untouched by man.

In the US you can find truly wild places, but it is pretty hard to find places untouched by man. Humans have been here for at least 15000 years, and from the very beginning were having huge impacts on the ecology.

That's also a joke

My LG G3 overheated so much that the screen unglued itself from the case.

Sent it to warranty 3 times, but it happened again every time. The middle of the screen got so hot I could barely hold my finger there.

The reason it sits at 8GB on idle is... optimization. The memory is there to be used, so the OS will use it to improve performance until it's needed for more important tasks.

That's a blatant simplification, and does not match reality as far as I've seen.

The OS only only has one large source of memory it uses "optimistically" - the file/buffer cache. But that's tracked separately, so it doesn't show up in normal memory usage numbers (unless you don't know how to read them).

The other source of "extra" memory usage is memory mapped executable files, which can be unmapped and then read back on demand. That's quite small though.

Everything else (mostly) is actual memory usage caused by actual drivers and programs (though it can be swapped, but that's a major perf hit).

The major reason for Windows memory bloat is the hundreds of inefficient services from both Microsoft and hardware vendors that run at startup. The "optimization" pool (let's not call it that way) is way smaller than that.

eg. pre-loading an application is a pessimization if there's not enough memory - not only does it permanently eat away a portion of the total memory due to the intricacies of Windows working set memory management, it will need to be swapped out when actual demand for memory arises, competing with other disk access.

The only actual "optimization" in Windows is Superfetch, and that barely works these days.