Windows Phone 7 was artificially limited crap, any amount of head start wouldn't help it.
HN user
garaetjjte
https://milek7.pl
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": "pangramdemo@milek7.pl"}' https://www.pangram.com/api/validate-email
https://milek7.pl/mailverifyspam/another.txtI 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)
Good coffee is better enjoyed around 60-70C
If you want to scald your mouth I don't think you need coffee to do that.
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.
Can Immich on Android automatically upload taken photos like Google Photos?
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.
Incredibly rich to complain about LLM scraping with LLM generated article.
Getting closer to https://xkcd.com/416/
What about CE/FCC certification?
Swinging back? Was UE used more widely in the past than it is now?
Ah yes, in Utah, the capital of MLM scams?
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.
Could it be that it directly uses AC for flame rectification and gets confused with ugly waveform?
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...
BeOS sort-of did that.
They should have used AOSP device attestation
No, they shouldn't have used any attestation. If they are using sound cryptosystem for their ZKPs, they don't need to care at all about what hardware and software I'm using.
I don't think this is necessarily fault of NTFS, but Windows filesystem stack.
I once did have a need for binary search in memory mapped files and I experimented with Eytzinger layout (which I learned from https://bannalia.blogspot.com/2015/06/cache-friendly-binary-...). It turned out that it was slower than plain binary search, I think because keys I was looking up were often clumped together thus it played quite well with cache anyway.
WTF is that? Wasn't MZLA supposed to be the home of Thunderbird project, and now they are mixing that with some unrelated bullshit?
Just include filename size in file size for billing purposes?
Isn't that just iterated prisoner dilemma?
Magyar was member of Fidesz up to 2024. So if he actually wins would this be meaningful change or just internal party infighting?
Seems fine if you can donate to Thunderbird development. Compared to Firefox, where I don't think it's possible to donate to development at all (only to Mozilla activism side).
Since we are on HN, I think it could be explained there (before it's all consumed by AI slop):
For complex reasons, available CPU time during landing was lower than expected (it was stolen by radar pointing peripheral). This caused regularly scheduled job to spawn before previous instance finished. As such, this caused two effects: job instances were suspended before finishing by new instances in the middle of the routine, and that pilling up of the old instances eventually exhausted resources and caused kernel to panic and reboot. Rebooting during landing sounds scary, but that actually was fine: such critical tasks were specifically designed to automatically restart from previously saved checkpoint data in the memory.
What was more dangerous, was the suspended tasks before restarts occured. First, it meant routine wasn't executing to the end, which in actual flight caused blanked displays (as updating the display was the last thing routine was doing). Any more CPU time stolen, and it could be interrupted even earlier, eg. before it sends the engine commands.
Another issue is that in case of fluctuating load, new instances could actually begin running to the end, and then previously suspended job instance could be resumed, potentially sending the stale data to the displays and engine.
And finally, while each job instance had it own core and VAC set properly managed by the kernel (think of it as modern kernel switching between task stacks), that particular routine wasn't designed to be reentrant. So it was using various global variables ("erasables") for its own purpose, that when interrupted in unluckly place might have caused very bad behavior.
How likely all of above is to occur, depends on the exact profile of fluctuating load caused by the confused radar peripheral. I guess that's why Mike Stewart is trying to replicate these issues with real CDU.