I was reading the nfs man page the other day and found some interesting information about nfs over udp over gigabit likely to cause silent data corruption due to IPIDs being 16 bit and the timeout for packet fragments to arrive is 30 seconds by default. With heavy nfs traffic on a gigabit link you can get repeated IPIDs after about 5 seconds. The UDP checksum helps most of the time, but it is also only 16 bit, so collisions are likely with that many packets flying around.
So, found a bug in firefox? If I link to page that is properly encoded to have a \ that is escaped, firefox will unescape the URL in the address bar, but if I click on the address bar, and press enter, it strips out the \s because they're not valid in URLs. So, the URL looks exactly the same as the working version, but it doesn't load the same page.
It you have a google account please help with reporting this as harmful and impersonating.
*DO NOT INSTALL* (except if you are a malware researcher 😉)
Fake F-Droid app, please report:
I will soon be writing a spec for a semantic markup language (likely a variant on HTML, but with hardly any presentation elements). The first use will be for a social media system, but it should be applicable to documents in general.
What prior art should I know about?
What else do I need to know, in order to not fuck this up?
New mission: dumpster diving/buying old hard drives and dumping their Internet Explorer 6 saved cache to find old web relics
@Cryoclaire thank you for making those cool hellovoid t-shirts.