2,545 karma · joined September 26, 2014
> Extended date representations are not currently supported (±YYYYYY-MM-DD).
https://docs.python.org/3/library/datetime.html#datetime.dat...
> MAXYEAR is 9999.
https://docs.python.org/3/library/datetime.html#datetime.MAX...
I'm also waiting for longnow.org to start using long dates behind the scenes, like image urls, html metadata, http headers, etc. They need to eat their own dog food as far as software goes.
<link rel="icon" href="https://static.longnow.org/2022/06/favicon.png" type="image/png">
<meta property="og:image" content="https://static.longnow.org/2021/10/header-talks.jpg">
<meta property="article:modified_time" content="2024-06-11T17:21:23.000Z">Why not 002019? 6 digits. That would be valid a lot longer.
"Elon Musk moving servers himself shows his ‘maniacal sense of urgency’ at X, formerly Twitter"
https://www.cnbc.com/2023/09/11/elon-musk-moved-twitter-serv...
DoS has become more of an issue now that all of the GPTBots are generating a lot more traffic. https://news.ycombinator.com/item?id=40865627
Looking at the http logs, around 5pm an ip address started spamming a whole bunch of requests to the same url. The same ip was doing pretty normal stuff on the website about an hour earlier.
My theory is holding down F5 key would cause the page to reload about 30 times a second. The website was not able to handle that many requests per second and it effectively became a denial of service attack.
This was around 2007-2010 and I think by now browsers have stopped repeating a reload if the F5 key is held down.
But, wow apparently the FDA rounds cups in nutrition labeling to be exactly 240ml “legal cup”, which I agree is super annoying. It’s 1.4% more.
“For purposes of nutrition labeling, 1 cup means 240 mL, 1 tablespoon means 15 mL, 1 teaspoon means 5 mL, 1 fluid ounce means 30 mL, and 1 ounce means 28 g (21 CFR 101.9(b)(5)(viii))”
Recently I’ve been tempted to make an SMTP server that translates emails into a web-hook. Please tell me more horror stories so that I might be convinced not do it.
> This may sound like a mess to you. But it was remarkably enjoyable to work in. Gone were the concerns of code duplication. Gone were the concerns of consistency. Gone were the concerns of extensibility. Code was written to serve a use, to touch as little of the area around it as possible, and to be easily replaceable. Our code was decoupled, because coupling it was simply harder.
If someone hits control+I, or an italics button, it should use <i> tags, not <em>.
Right. Xerox got Apple stock out of the deal. Not really stealing. Bought and paid for.
Thank you for sharing it!
Now I need to lean SS7 signaling.
I suppose then the hope is that nmbl would basically be a general-purpose fully-featured replacement for grub, which seems to be going in the direction of being a full kernel anyway:
> one with quite some bells and whistles, with networking, complex storage, cryptography, http client, ca store and stuff (I mean, that's how I understand it, i.e. it should be able to load kernels from sources that require all that). It hence will need require regular updating (as much as the 2nd stage kernel most likely, if not more often, since it probably needs ca store built in), and quite possibly will break every now and then nonetheless, because it's basically a full OS you are boot as first stage.
- https://lwn.net/Articles/981149/
It sounds like if you don't need grub's complex features, then systemd-boot is probably the safest way to go, but if you do need grub's complex features, then nbml aims to be the safest and most reliable way to get those features.
> The question is: that there are CVEs everywhere, we're not unique in this sense, and whether we would use systemd-boot.
> So, systemd-boot, it also works only on UEFI, and I believe that the plans are to keep it that way.
> Ultimately, the thing is that the kernel CVEs will get fixed no matter what, the question is: do we want to have more work fixing more CVEs. The kernel has a lot of developers, has very high visibility, and they're able to fix the CVEs in a reasonable time period. And, those aren't going to going to go away, the kernel CVEs aren't going to go away, whether we do this or not.
> Systemd-boot, any boot loader, that aims to replicate the things that the kernel does is ultimately going to run into the same problems as grub. We're going to have the font CVEs, we're going to have filesystem and storage and memory allocation bugs. All of that stuff is going to exist in whatever boot loader.
> Again, for an individual user, if you want to install systemd-boot, great, go ahead and use it. It's good, it works. But as a general option it's just going to have the same issues, unfortunately.
I think the performance characteristics of the web are subject to change over time, especially to allow increased security and privacy.
https is another example of increased security+privacy at the cost of being slightly slower than non-https connections because of an extra round trip or two to create the connection.
The lesson I take from it is: don't use complicated optimization techniques that might get out of date over time. Keep it simple instead of chasing every last bit of theoretical performance.
For example, there used to be a good practice of using "Domain Sharding" to allow browsers to download more files in parallel, but was made obsolete with HTTP/2, and domain sharding now has a net negative effect, especially with https.
https://developer.mozilla.org/en-US/docs/Glossary/Domain_sha...
Now they're realizing that HTTP/2's multiplexing of a single TCP connection can have negative effects on wireless connections, so they're working on HTTP/3 to solve that.
Also don't use polyfills. If your supported browsers don't support the feature then don't use the feature, or implement the fallback yourself. Use the features that are actually available to you.
The only other alternative is to send the CSS inline, but that doesn’t work as well for caching for future page loads.
103 Early Hints is not nearly as useful as it doesn’t actually save a round trip. It only works around long request processing time on the server. Also, most web frameworks will have a very hard time supporting early hints, because it doesn’t fit in the normal request->response cycle, so I doubt it’s going get much adoption.
Also it would be nice to be able to somehow push 30x redirects to avoid more round trips.
Latency is really important for live audio at shows, so that was probably the priority.
Re XHTML - It looks like the website is being served with a text/html content type. Did you give up on your XHTML experiment? How did it go? Maybe it would help if browsers reported back errors to the server, like how "Content Security Policy" reporting works.