ivegotnoaccount

Wait, 114°C? Is that safe, especially long term? I guess Intel has margins in place, but I recall their processors having a Tjunction around 100°C

I explicitly talked about the best case scenario, which would have been "one camera pixel is able to retrieve precisely the information of one printed pixel (or several printed pixels that act as one)"

From there, I simply listed sources of error that would make it worse and words. The only place I could see conflation occurring is when I wrote about "sub 0.1mm" which indeed refers to the printed thing, and correspond roughly to the tolerance that would be needed to achieve millions of "printable" pixels, but even if it's about the printed pixels, it still limits the amount of information that would be stored.

Would you mind indicating where there seem to be confusion according to you? Re-reading it quickly, the comment seems consistent and indicates that both the camera pixels AND the printed pixels would cause issue.

> You should be able to get a few MB on a page easily

A few hundred Kb, maybe, but a few MB seem unlikely. If I take the best case scenario (no optical aberration, perfect sensor...), my phone has a 48MP camera. We cannot have 48M * 3 colors as those 48MP are after Bayer matrix handling. We also cannot have more than one bit of information per pixel, due to printing often not having "real" greyscale but some kind of dithering and you don't know for sure how it would interact with your sensor. So in the best case, 6MB. But then, you need to add error correction: books prints are not perfect, especially at a sub-0.1mm scale. They are also not perfectly planar as paper is grainy. And the camera is not exactly at a 0 angle... In the 3 axis. So you would need to have the printed pixels be way larger than the sensor ones to be able to offset this. And so on.

Not sure I want to use what seems like a fully-closed standard for something as frequent as sharing locations when open alternatives exist.

Also doesn't "blink" nor have what's inside it "disappear" from perception.

Isn't it on their consumer lines only that Intel removed AVX-512?

Saphire Rapids is indicated as having support for it.

I know that even though you pointed to an EPYC CPU, all Zen4 support it, but Intel probably released it more for the professional users than their non-pro ones.

Well, as explained in some of my other comments, it doesn't seem that effective. Most GPT-generated garbage will probably be GPT-3 based, which doesn't seem to too often trigger as "fake" (got more "human" results when I tested it with ChatGPT), while on the other hand, it says that several of my comments are fake with >99% certainty.

While I understand the reasons why the author think it will go that way, I'm not fully convinced:

- [in average rich countries in 2030] Fast gigabit internet is cheap and everywhere (5G or mesh wifi) => Glad to hear that it will be that way, unlike the 4G for which we got the same promises yet for which I often have issues with my phone in the suburbs of a middle-sized city of a rich country. Also glad to hear ISP issues will be a thing of the past. Sorry for the slight sarcasm here, but this point is a prerequisite for the whole post.

- Outside of work for which expenses are not mine to pay, I'm really not a fan of paying extra for cloud services when I can do without.

- On the "editing code" part => That seem to introduce quite a lot of friction. What if the tool I like to use are not supported as part of this workflow? Which of those support private clouds if I'm working on things that must be kept private?

Last but not least, though this one is more a nitpick of mine than a real complain, but the article uses "localhost" quite ambiguously as sometime it refers to "running things locally" and other as a concept of the whole development machine (editing things locally, having the code on your drive...) and talk about things like OS development: While this may work fine for webdevs, I'm not so sure about other kinds of developers. GUI dev would get added friction, same for work needing low latency (the article talks about edge computing, but that requires paying even more if your structure is small). Maybe that works for Tesla OS devs, but not all companies have what is needed to create a full-fledged cloud environment for embedded developers.

Seems to have major biases against who knows what sentence structures. Even without trying to make it say fake, some of my messages and text I write in it are pretty confident I'm GPT-2...

> Well, repairs are usually warrantied themselves.

I don't know if this holds when the issue occurs more than one year after the repair, and has, at first sight, has nothing to do with it (Won't get into the details as it's not that interesting. The most important part being that the company's logs did not acknowledge a potentially-related issue reported while the servicing technician was still there).

> if you can afford to self-insure you'll probably come out ahead on average.

Yes. But if two parts of my TV broke in its first year and it needed to be serviced a second time just after because the replacement parts sent the first time randomly shut down with the company refusing to acknowledge it because "Yeah, the first technician said this, but the second time a technician came, it was not having issues" or missing logs, my guess is that buying the extended warranty at that point would probably cost less on average for that TV as I would not put any trust in it surviving long without needing another repair.

Or if you know that you will probably have issues with your computer sooner than later even though you're not rough with it.

I did initially not buy it with my current laptop. Something broke during the standard warranty. Got the motherboard replaced... With a faulty one. So they replaced it again.

Got a feeling that buying extended warranty would be a good idea. And indeed, 3 months past the standard warranty end, it refused to boot at all. And once again, got replaced with a (less) faulty motherboard (some faulty USB ports).

I'd have preferred not being given broken motherboards by the warranty service, but since I have no ultimate proofs, had I not bought it, I would most likely have been refused service.

Sadly, the fact that it assumes interchanges to be 20 minutes makes it, at least in some cases, far from reality.

At least for the local line of train I most often take (in France), the average time between trains is half an hour, but around 9AM, there is a gap of two hours (on work days) between two trains.

But then, all usages of SGX, not only DRM, would be compromised easily.

I don't know, for instance, if password wallets use it for protecting their data when they are loaded, but that would lead to pretty bad consequences.