That’s not Cloudflare-specific; you can use any CDN that supports origin pull in the same way :)

It’s not ideal because… Cloudflare… but at least you’re using standard web tools. To ditch Cloudflare you just unplug them at the domain and you still have a website.

Definitely agree with this! That’s one of the pain points of “cloud” services - they really try to lock you in, making it impossible to swotch.

without having to deal with LetsEncrypt.

You still need encryption between your CDN and your origin, ideally using a proper certificate. Let’s Encrypt (and other ACME services like ZeroSSL) are pretty easy to use, and can be fully automated. I’m using Let’s Encrypt even for internal servers on my network, using a DNS challenge for verification instead of a HTTP one.

Perhaps its irrational but I’m bothered by how many people seem to think that Github Pages is the only way to host a static website

It’s strange because out of all the possible options, Github Pages is the most basic. You have to store your generated files in a Git repo (which is kinda gross) and it barely supports any features. For example, it doesn’t support server logs or redirects.

I guess it’s popular because people already use Github and don’t want to look for other services?

You seem to recommend a VPS but then suggest a bunch of page-hosting platforms.

Other comments were talking about pros and cons of self-hosting, so I tried to give advice for both approaches. I probably could have been clearer about thay in my comment though. I edited the comment a bit to try and clarify.

I have some static sites that I just rsync to my VPS and serve using Nginx. That’s definitely a good option.

If you want to make it faster by using a CDN and don’t want it to be too hard to set up, you’re going to have to use a CDN service.

Self-hosted CDN is doable, but way more effort. Anycast approach is to get your own IPv4 and IPv6 range, and get VPSes in multiple countries through a provider that allows BGP sessions (Vultr and HostHatch support this for example). Then you can have one IP that goes to the server that’s closest to the viewer. Easier approach is to use Geo DNS where your DNS server returns a different IP depending on the visitor’s location. You can self-host that using something like PowerDNS.

Nintendo could try make up something like “it’s not computer software since the Switch is a console, not a computer” or something like that. Not a great argument, but they have good lawyers and could probably convince a court that it’s true.

A VPS still counts as self-hosting :)

I host my sites on a VPS. Better internet connection and uptime, and you can get pretty good VPSes for less than $40/year.

The approach I’d take these days is to use a static site generator like Eleventy, Hugo, etc. These generate static HTML files. You can then store those files on literally any host. You can stick them on a VPS and serve them with any web server. You could upload them to a static file hosting service like BunnyCDN storage, Github Pages, Netlify, Cloudflare Pages, etc. Even Amazon S3 and Cloudfront if you want to pay more for the same thing. Note that Github Pages is extremely feature-poor so I’d usually recommend one of the others.

Was there a Linux version?

it’s legal to dump that game to a PC and play it on a Switch emulator, right?

Depends on where you live. Copyright law varies significantly from country to country.

In the USA, section 117 of the copyright act lets you create a copy for archival/backup purposes only. What I’m unsure about (and don’t know if there’s any relevant caselaw) is whether bypassing copy protection to create the copy violates the DMCA.

The equivalent Australian copyright law explicitly states that you can use the backup copy instead of the original one. The US law doesn’t (all it says is that you can make an archival copy, not how you can use the archival copy), so it’s a grey area.

Both laws are for “computer software”, but you could easily argue that a video game is computer software.

When Twitter launched, they used “post” instead of “tweet”. Tweet was a word created by the community.

User agents are essentially deprecated and are going to become less and less useful over time. The replacement is either client hints or feature detection, depending on what you’re using it for.

Most developers just write their own feature checks (a lot of detections are just a single line of code) or use a library that polyfills the feature if it’s missing.

The person you’re replying to is right, though. Modernizr popularized this approach. It predates npm, and npm still isn’t their main distribution method, so the npm download numbers don’t mean anything.

That’s exactly what you’re supposed to do with the modern web, via feature detection and client hints.

The user agent in Chrome (and I think Firefox too) is “frozen” now, meaning it no longer receives any major updates.

That really depends on the company. At big tech companies, it’s common for the levels and salary bands to be the same for both generalists (or full stack or whatever you want to call them) and specialists.

It also changes depending on market conditions. For example, frontend engineers used to be in higher demand than backend and full-stack.

Not sure what you mean by “controlled” given it’s open-source?

Which OS?

On Android, Moon+ Reader is pretty good.

My wife uses the Amazon Kindle app on her Android tablet. You can use it for non-Kindle books by sending an email to a special email address for your Kindle account: https://www.amazon.com/sendtokindle/email.

Calibre is useful for this. It shows an easy to use “send to Kindle” button, and can convert books in ePub, mobi, etc formats to the format that works best in the Kindle app (AZW3).

If you want a web interface for Calibre (eg to run on a home server and download books when you’re away from your computer), Calibre-web works well.

But why deal with separate software like dnscrypt-proxy when AdGuard Home has it built-in?

A recursive DNS server and a local DNS cache/forwarder/are two different things with two different purposes. You will always need both.

Why do you need two separate ones though? Recursive DNS servers also cache responses. Usually the only reason you’d run a local forwarder/cache is if you’re not running a local recursive server.

I use a wildcard cert in some places, but most of them are individual certs. You can have multiple ACME DNS challenges on a single domain, for example _acme-challenge.first.int.example.com and _acme-challenge.second.int.example.com for first.int.example.com and second.int.example.com respectively.

The DNS challenge just makes you create a TXT record at that _acme-challenge subdomain. Let’s Encrypt follows CNAMES and supports IPv6-only DNS servers, so I’m using some software called “acme-dns” to run a DNS server specifically for ACME DNS challenges. It’s just listening on a IPv6 in one of my VPS /64 IPv6 range.

IMO it’s easiest to just use a real domain for your local network. For example, I use subdomains of int.example.com, where example.com is my blog.

Then, you can get Let’s Encrypt or ZeroSSL certificates for all the hosts. Systems do not need to be accessible over the internet - you can use an ACME DNS challenge instead of a HTTP one. Use something like certbot or acme.sh and renewals will be automated.

Only cost is for the domain, and some TLDs are less than $5/year. Check tld-list.com and sort by renewal price, not registration price (as some are only cheap for the first year).

Throw Unbound on there too as your upstream recursive resolver

If you want to run your own recursive DNS server, why would you run two separate DNS servers?

You don’t even need to worry about an encrypted session to your upstream anymore because your upstream is now your loopback.

Your outbound queries will still be unencrypted, so your ISP can still log them and create an advertising profile based on them. One of the main points of DoH and DoT is to avoid that, so you’ll want them to be encrypted at least until they leave your ISP’s network.

AdGuard Home is a better choice than PiHole since it uses DNS-over-HTTPS by default. There’s also an app called AdGuardHome-Sync to sync settings between multiple instances.

I’d recommend running two DNS servers, and at least one of those separately from the rest of your infrastructure like on a Pi. That way, if you need to pull one of them offline, the internet still works.

And make sure it’s a VPN that supports port forwarding. Sharing is caring.

or just use Usenet.