towerful

No.
I tried a smart watch for a week or so, and hated wearing it.
Hadn't worn a watch in 20 years, and it felt very strange

I'm always nervous about fintech companies. Maybe it's time to get over that and give curve pay a spin.
The cashback seems nice, considering a lot of shops I use are on there.

Not if you use wildcard dns records.

Yup, true.

But contactless via a phone can have no limit.
Adding a debit card to phone case means the upper limit is £100. Which is actually fine, and is the limit I have normally set for phone contactless. But I can instantly remove that limit via my banking app.

And the phone needs to be unlocked to make a payment.
Do if I lose my phone anyone can charge £100 to the debit card.

Servers: one. No need to make the log a distributed system, CT itself is a distributed system.

The uptime target is 99%3 over three months, which allows for nearly 22h of downtime. That’s more than three motherboard failures per month.

CPU and memory: whatever, as long as it’s ECC memory. Four cores and 2 GB will do.

Bandwidth: 2 – 3 Gbps outbound.
Storage:
3 – 5 TB of usable redundant filesystem space on SSD or.
3 – 5 TB of S3-compatible object storage, and 200 GB of cache on SSD.
People: at least two. The Google policy requires two contacts, and generally who wants to carry a pager alone.

Seems beyond you typical homelab self hoster, except for the countries that have 5gbps symmetric home broadband.
If anyone can sneak 2-3gbps outbound pass their employer, I imagine the rest is trivial.
Altho... "At least 2 [people]" isn't the typical self hosting

Edit:
Tried to fix the copy/paste.

Also will add:

https://crt.sh/
Has a list of all certificates issued.
If you are using LE for every subdomain of your homelab (including internal), maybe think about a wildcard cert?
One of those "obscurity isn't security", but why advertise your endpoints? Also increases privacy (IE not advertising porn(dot)example(dot)com)

This... Except for contactless payment.
I used graphene for a month. It was lovely. Even things like banking apps worked.
I don't care about absolute privacy, but I do care about controlling my privacy. Grapheme gave me that.

I had only 1 issue.
Contactless payment.
It's extremely convenient to me, from public transport to groceries. I just bop my phone.

The fact that Google has that locked down surely violates some EU laws. But I'm sure they wave away the laws because of "financial security" or some other bullshit.
As if bank card NFC/contactless doesn't suffer exactly the same issues.
I looked into some "graphene contactless payment" type systems or workarounds, and I couldn't find anything that would fill the gap.

Everything else. Or anything else, if you select a single quark (presuming we don't split a quark).

If everything is moving away from us, then everything is moving away from everything else.
It's just that some things are moving away from us faster than they are moving away from other things

Everything else.

Galactocentrism was established in 1925, which realised that our solar system is not near the center of the Milky Way. So, we are moving relative to the center of our galaxy.

In 1929, evidence was found that everything else is moving away from us. So we are moving relative to everything else.

In 1931, the Big Bang theory started superceding Galactocentrism, which was an acentrist model of the universe (where there is no center).

If I was responsible for the safety and wellbeing of a flying tube with 200 people in it, I would absolutely be pissed about not being able to get a proper rest.

Eventually, yes

Smaller file size, lower data rate, less computational overhead, no conversion loss.

A 64 bit float requires 64 bits to store.
ASCII representation of a 64 bit float (in the example above) is 21 characters or 168 bits.
Also, if every record is the same then there is a huge overhead for storing the name of each value. Plus the extra spaces, commas and braces.
So, you are at least doubling the file size and data throughput. And there is precision loss when converting float-string-float. Plus the computational overhead of doing those conversions.

Something like sqlite is lightweight, fast and will store the native data types.
It is widely supported, and allows for easy querying of the data.
Also makes it easy for 3rd party programs to interact with the data.

If you are ever thinking of implementing some sort of data storage in files, consider sqlite first.

All the cool kids are running kubernetes