Only acceptable use of attestation is when done on behalf of device owner. So if they let me submit list of keys allowed for my account, fine, but any other use is just evil restriction of what software I can run on my own devices.
You usually hope that TTD points to the culprit in such situations. But once I encountered single-byte corruption that didn't make any sense in TTD trace, there was good value at write and next read was garbage. I never discovered whether that was CPU bug, corruption by GPU shaders, stray kernel writes, or whatever.(I think it's unlikely that CPU bug would manifest with both native and TTD-instrumented runs. Corrupted byte was inside heap allocated memory so it shouldn't be in GPU pagetables at all. Kernel writes wouldn't appear in TTD trace, so really I think that was most likely issue, but how to debug that...)
Maybe they don't do that for larger destination providers. But definitely no coincidences here. (in the post I replaced address with example.com because I'm curious if I will ever get other spam onto it, but here's another one unmodified)
curl --request POST --data '{"email": "[email protected]"}' https://www.pangram.com/api/validate-email
I hate that type of diagrams. Why sRGB-encoded image, pretends to show any color outside of sRGB region? It doesn't make any sense! (and when these diagrams attempt to illustrate sRGB, often actual colors encoded are narrower than full sRGB)
>Official Mono releases have switched to do that since then, but (I think) for backwards compatibility reasons Unity never enabled that functionality and kept everything at double precision so far.
Probably because Unity uses ancient Mono fork. And that apparently started because they didn't renew their non-copyleft license with Xamarin.
In practice they don't do that, apart from spamming few addresses like office@ or accounting@. If some address starts getting spam I reject everything sent to it. For addresses that are getting spam but needs to be public (like contact addresses on website) I do more aggressive filtering (eg. I noticed that enforcing that recipient is actually present in To/Cc header cuts down a lot of spam).
That's mostly papering over design mistake that most syscalls doesn't accept target pid. Otherwise you could just create suspended process, configure it with syscalls that explicitly take target pid, and start it.
>the more of them you add, the larger is your communication and coordination overhead. In no small part because humans are self-interested agents that simply aren't designed to compose their capabilities seamlessly.
What proves that AI doesn't have the same limitations? There's only so much computation you can do in given space, and all communication is limited by universal speed limit.
Huh? CE7 platform builder is just extension to stock VS2008. And it doesn't really do much, just few treeviews for selecting components. The real issue is the build system, which is some hideous combination of bat files and nmake.
Kernel is the only part that seems written with any sort of care, everything else is barely holding together with duct tape.
I don't think cell tower connection will give you any more precision, GNSS fix will be much more accurate. (within few meters)
You could get more accurate fix with RTK data, but I'm not sure if that's actually widely used. And in any case that doesn't require active communications either, you could get correction data from satellite broadcasts too.
I remember when iCloud arrangements required by China was seen as draconian. Now it seems we're not far from people cheering for such laws elsewhere...