Not sure if was legal or not for the Waymo to stop there, but given that Waymo stops take quite a bit longer than stops with Uber/Lyft (as it takes a while for the car to continue driving) this was one of the worst places possible to stop. Especially as there would have been space available right after the crossing next to Walgreens.

Something similar is the case in the European Union, as the electricity network is usually a different company than the electricity providers. The network is often owned by some municipal company and charges customers only for the transport of energy over the network. For the energy itself customers can choose from dozens of different providers, some of them generate their own electricity, others just buy and resell electricity on the market.

With Fi you run into issues if you use it for too long outside the US. And also I read that people had troubles re-activating a Fi eSIM from outside the US in cases where they (for example) lost their phone.

Meanwhile newer iOS versions seem to nowadays have generic VoLTE (and even VoWiFi) support that even works for smaller MVNOs without an iPhone carrier profile (as long as their VoLTE implementation somewhat conforms to standards).

I heard this claim before but I was never able to reproduce it. Does this only happen with the "Storage Saver" option enabled and/or when metadata has been manually changed? At least with the "Original Quality" option my takeout data seems to exactly match the files that were originally uploaded.

For the comparison I pretty much only use the logged hashes which allow me to figure out if any hashes (and associated files) are missing in the new version of the backup. This isn't a perfect solution yet as a few things aren't detected. For example Google Takeout bundles mails in mbox files and I currently don't check for missing mails. It would be better to convert the mbox files to a Maildir first so that the comparison can be done on a per-mail basis.

For example in the past I had several occurrences of duplicate photos where each of the two instances has exactly the same bytes as the other one. Usually that should have gotten deduplicated, but it hasn't. What's even stranger is that deleting one of the two pictures also deleted the other one. Re-uploading the original photo usually made both duplicates show up again. The way how I was able to get rid of those duplicates was to wait a day or so until I re-upload the data and to attempt that process several times. At some point only a single photo showed up.

Also those duplicates only showed up in the regular photo view. Even if both of the duplicate instances were added to an album viewing the album would only show the photo once.

Exporting my Google Photos sometimes fails consistently even with lots of attempts. Out of well over 10 export attempts or so this year maybe a single one succeeded. I have a few hundred GB of data stored on that account. I also currently have a support ticket with Google open on that issue, but after initial follow-ups haven't received a response in a couple of months now.

That said my current approach for backing up things is to upload an "age" encrypted version of the data from Google Takeout to Wasabi. Once uploaded I run a script that shows me the diff between the data sets (so that I can ensure that no old data went missing that shouldn't have gone missing) before I delete older data. Probably not the most optimal approach though. Might be better to just set up some versioning layer on top of Wasabi and to keep deleted or modified data forever.

Yes - Comma owns that repository and there are instructions on how to put the software on Comma devices. But then also lots of commits are from authors not affiliated with Comma and my understanding is that quite a few users of that software aren't actually using the official repository, but various forks maintained by third parties.

Comma is not selling openpilot (the software that makes your car self-driving), but they are selling the Comma devices that out-if-the-box just include dashcam functionality and a few additional features.

Openpilot is an open-source project on Github that makes cars self-driving and that also runs on regular Linux PCs as well as those Comma devices.

Do you suggest that Comma should not be allowed to sell the Comma devices anymore (that out of the box work as a Dashcam)? Or do you suggest that Comma should not be allowed to contribute to an open-source project that can make cars self-driving?

If you're in Pacific time and you buy the ticket for a date in the future (let's say June 1st) before 3pm your local time everything works fine. But if you buy the same ticket for June 1st after 3pm Pacific local time (which is already the next day in Vienna) the ticket that you're buying isn't for June 1st but actually for June 2nd (only visible once you receive the confirmation).

So apparently they're somehow translating between timezones for the displayed dates, although that doesn't make sense: If I buy a ticket for June 1st on Vienna public transport I don't care what my local time is. Even if I'm in California while buying that ticket I still want it to be valid on June 1st instead of June 2nd.