I suppose so, but all they’ll see is a an encrypted session.

I haven’t found one, no. I just use markdown and a static HTML site generator.

Is this a trick question?

Websites are complicated. Easy, secure, cheap: pick two. There is no such thing as a universally easy, secure and cheap solution, or else we would always be using it.

Assuming you want secure and easy, I would suggest you pay someone who knows what they’re doing.

It was time in 2013.

I think we’re talking past each other here: You are talking about blocks as physical delineations in an ssd, containing many pages with erase cycles. Op is talking about the filesystem view of blocks, which is different altogether. ZFS, for instance, should have its block size aligned with what a disk presents to the HAL, or you end up with lots of wasted space or terrible performance.

For SSDs (you’re right, outside op’s problem), the internal block size is usually much bigger than the emulated block size, often 128K. But we don’t use filesystems with 128K block sizes, or we couldn’t reasonable run databases or store small files.

There was a brief time in the wild west of SSDs being new where some shipped with 8k blocks, but this caused a bunch of problems for storage drivers because no one had yet decided if the translation of FS blocks to should be handled by filesystems or by disk firmware. We now let manufacturers decide how they should r/w to media, and trust the firmware’s presented block size.

That block size is now 4k for most disks, spinning or ssd. We still see some weird layouts in high-performance or high-endurance disks, but they are exceptions.

so if a 512e SSD doesn’t receive the rest of the page in time (e.g. with IO scheduling, 512 byte fs sectors, unaligned partitions, or bad luck)

I’m not sure what this means, pages are a concept in an ssd’s physical structure, they don’t mean anything to a filesystem (except in volatile memory).

Except for leaving things default, almost none of that comment is true.

4k is default for most disks today. Some transition-era ssds used 8k blocks.

Do not worry about emulated block size, because ssds only use that to report to the filesystem, no sectors exist on solid state media.

Erasing the partition table and/or uefi metadata space.

It isn’t technically tough to do anymore, but you can only self-hosting the sip endpoint, you need to rely on and pay for upstream trunking.

Also, be aware that 911 or emergency service contact is all over the place. In Canada, VoIP providers do not provide 911 unless they have a pots tie-in somewhere, and there are still tragic issues where 911 calls are routed to dispatchers thousands of km away.

If you have any nontechnical people who expect all the features of a landline using this, don’t do it yourself.

You don’t even need to lift a finger. I use WG Tunnel, which turns on my VPN as soon as I leave my WiFi. I’m always tunneled or home.

Not a productive comment.

Ansible certainly works here, most implementations I’ve seen are terraform with ansible or cloudinit.

Most of my stack is containers, so I personally prefer cloudinit and a handoff to ansible.

Calibre Web Automated. I have Kobo integration enabled, so when I add an ebook to the “sync” folder, it appears on my Kobo. pretty nice system.

It’s better to think about it as though you are making a queue of changes that need approval to be permanent. Rather than just accepting that you just installed a ton of dependencies for no reason because you didn’t really want the software, you can cleanly reverse any of the changes.

In a sense, it accomplishes a similar thing as nix in a different way.

it’s not like sD devs forced them to adopt their option

It kind of is, though. You dont typically select your preboot environment, it’s selected for you.

You have already identified the problem in the logs.

You have a fake drive with firmware that says 1.8tb but are actually much lower.

access beyond end of device

This means an inode is mapped to a non-existing sector. Get your money back, if you still can.

Yeah, but things like human readable logs are almost all gone because of journalctl changes that went into the systemd ecosystem without anyone really running by folks who look at logs everyday.

It’s not the functionality of systemd I don’t like, it’s the Poettering way of just making changes to stuff without bothering to learn how any of the rest of us professionally use things.

In tempus, the setting is called “continuous play”. In feishin, it’s called “auto-dj”. Both settings are turned on by default, so you shouldn’t have to do anything.

Scrobbling helps because every played track goes into played history, and play counts help dynamic song selection more and more over time.

I don’t use the ratings, but I’ll “heart” songs I like.

I scrobble my playing from navidrome using listenbrainz and tell my two clients Tempus and Feishin to use the scrobbled data to build dynamic playlists. If I start with a particular song or album, the mix following that is usually kept in the same mood, only strays into weird stuff once in a while, but no more that YouTube Music used to.

Mir was canonical’s own fault for trying to pull a (blatantly obvious) licensing move where Mir would have been nearly impossible to compete with in a future Ubuntu.

And that’s setting aside the absolutely insane statements canonical’s Mir team were making about Wayland at the time.

When you fumble something so badly that Intel stops supporting your efforts on it in protest, you messed up.

I mean, there’s a difference between not gatekeeping when talking about cloudflare and completely waving Cloudflare’s banner on your front lawn.

• Cloudflare has full access to your traffic, and privacy is a very strong motivator for a good chunk of self-hosters.
• You might also be interested in Cloudflare’s unending string of bad actor captcha redirects that Cloudflare inexplicably won’t resolve, for all their 800lb gorilla strength in warding off DOS volumetric attacks.
• Another thing you would think Cloudflare has resolved: captcha hell.

So yeah, I wouldn’t have phrased it the way original comment was phrased, but holy cow, bro… Cloudflare is far from perfect and the people that will have existential problems with Cloudflare are very likely to be self-hosters.