Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]
While we’re changing the calendar, can we rename September through December so they’re not off by two?
Septem, Octo, Novem and Decem are the Latin words for 7, 8, 9 and 10 respectively, but they’re actually the 9th, 10th, 11th and 12th months of the year. This is because the Roman calendar was originally only 10 months, but Julius Caesar inserted two new months in the middle, without renaming the last four.
Maybe the oldest tech debt in existence - the calendar was changed in 45 BC.
This. Sunday is part of the weekend, not the weekstart.
Practically everyone should know SI, or have at least heard of it before. It’s the standard system of measurement used in most of the world. It includes base units for time (seconds), distance (meters), mass (kilograms), electric current (amps), temperature (Kelvin), amount of a substance (mole) and intensity of light (candela), plus a bunch of units derived from these.
It’s practically only the USA that doesn’t use some of three units (for example, preferring feet over meters)
ISO is a standards body. They define a bunch of standards. One of the more well-known ones is ISO 8601, which defines standards for dates and times. It specifies that weeks start on Monday.
Since you’re using Hetzner, one option is to get a Hetzner storage box to store the media. 1TB space is $4/month (not sure about EU pricing). You can mount the storage on another system via NFS.
On-disk cache prevents a “thundering herd” problem when you reboot - an in-memory cache would be empty on rebootz whereas an on-disk cache survives a reboot. Linux handles caching files in RAM automatically.
they can be uploaded to S3 (object storage) where it is 10x cheaper to store them
This is heavily dependent on the VPS. Some of my VPSes are cheaper than object storage would be.
RAM is a good idea. You could put the cache in /dev/shm.
Anything loaded from disk is going to be cached in RAM anyways.
Even if you build your own thing to communicate with the AC, Home Assistant is still useful since it lets you easily automate things and interact with other devices, and you get a bunch of things included (nice UI, storage of historical data, dashboards, etc). You could build your thing as a Home Assistant integration.
Companies are throwing away old hardware (like 8th/9th gen Core i5) that’s perfect for running Home Assistant. See if there’s an e-waste recycler near you - they might let you buy an old system for a nominal fee.
Use a page caching plugin that writes HTML files to disk. I don’t do a lot with WordPress any more, but my preferred one was WP Super Cache. Then, you need to configure Nginx to serve pages directly from disk if they exist. By doing this, page loads don’t need to hit PHP and you effectively get the same performance as if it were a static site.
See how you go with just that, with no other changes. You shouldn’t need FastCGI caching. If you can get most page loads hitting static HTML files, you likely won’t need any other optimizations.
One issue you’ll hit is if there’s any highly dynamic content on the page, that’s generated on the server. You’ll need to use JavaScript to load any dynamic bits. Normal article editing is fine, as WordPress will automatically clear related caches on publish.
For the server, make sure it’s located near the region where the majority of your users are located. For 200k monthly hits, I doubt you’d need a machine as powerful as the Hetzner one you mentioned. What are you using currently?
If your current setup works well for you, there’s no reason to change it.
You could try Debian in a VM (virtual machine) if you want to. If you’re running a desktop environment, GNOME Boxes makes it pretty easy to create VMs. It works even if you don’t use GNOME.
If you want to run it as a headless server (no screen plugged in to it), I’d install Proxmox on the system, and use VMs or LXC containers for everything. Proxmox gives you a web UI to manage VMs and containers.
This applies to a lot of services. Only expose something publicly if the public need to access it, and make sure it’s properly secured. If it’s just for you or your family (or friends) to use, use a peer-to-peer / mesh VPN like Tailscale.
Blue Iris is by far the most capable NVR, but it’s Windows-only so you’d need a Windows or Windows Server VM. For a basic setup, Frigate is more than sufficient.
I’d say try Frigate on your ThinkCentre and see how well it runs. I wouldn’t buy new hardware prematurely.
Do I understand that I could then share the igpu between Jellyfin and Docker/Frigate?
I’m not sure about containers like LXC, but generally you need SR-IOV or GVT-g support to share a GPU across multiple VMs. I think your CPU supports GVT-g, so you should be able to find a guide on setting it up.
It must be a lot of work to self-host DigitalOcean.
If your element has an id, you can just reference it from the window scope
This is brittle, as defining a global variable with the same name (or the browser adding a API with the same name) will override it. This functionality was only kept for backwards compatibility with sites designed for Internet Explorer. The spec says to use getElementById instead.
PSMC sounds like a bootleg TSMC lol
legacy fab it opened just 19 months ago
what
Fibre optic is generally better for this use case, but Ethernet would work fine too. Be sure to use CMX rated cable, as it’s rated for outdoor use (uses a more durable, UV-resistant jacket, and is suitable for direct burial).
Run it in conduit so you can easily replace it in the future if needed.
I think you’re right - people using the paid ones want to get their money’s worth. Even on the expensive plans like Claude Code’s $100/month subscription, people often end up using the equivalent of thousands of dollars worth of API usage, which doesn’t even cover the full cost of providing the service.
As far as I know, this is only for the free version of ChatGPT. It costs a lot of money to run, and they’re still not profitable, so it makes sense that they want to monetize the free version. The other option is to completely shut down the free version and only have the paid one.
They’re unaffected as they pay for the OpenAI API (there’s no free API) which is a separate product to ChatGPT. This change only affects ChatGPT, and I think only the free version.
That’s essentially how the Roman calendar was named for six out of the 10 months: