Em Adespoton

It’s a meta-app that consumes other maps, does navigation, and acts as a dashcam at the same time.

That was the trash can; they brought back a modified cheese grater with the M1 chip.

I miss the XServe.

And I move more to using OpenStreets, Organic Maps and Sidekick Pro. Shame that Apple’s going the same way as Google.

Nest and Eero/echo are two brands I wouldn’t trust even if jailbroken. They’ve both been shown to contain more hardware than originally announced after some third party tear downs.

Since by design cryptocurrencies aren’t backed by banks/nations and any transaction is permanent, they are by definition not safe. At best, you can save out your wallet to an encrypted drive, then write it back to your phone when you need to use it. Make copies, so if one gets lost, you don’t lose the value itself.

Yes; the problem IPFS has is the same problem IPv6 has. The hash-in-a-URL solution can function cleanly in the background on top of what people already use.

The idea is to verify the archival copy’s URL, not to verify the original content. So yes, a server could push different content to the archiver than to people, or vary by region, or an AitM could modify the content as it goes out to the archiver. But adding the sha256 in the URL query parameter means that if someone publishes a link to an archive copy online, anyone else using the link can know they’re looking at the same content the other person was referencing. If the archive content changes, that URL will be invalid; if someone uses a fake hash, the URL will be invalid (which is why MD5 wouldn’t be appropriate). The beauty of this technique is that query parameters are generally ignored if unsupported by the web server, so any archival service could start using this technique today, and all it would require is a browser extension to validate the parameter. Link it to something like Web of Trust, and you’ve solved the separate issue you described. In fact, this is a feature WoT could add to their extension today, and it would “Just Work”. For that matter, Archive.org could add it to their extension today, too.

Only works for archived pages though, because for any regular page, a large portion of the page will be dynamically generated; hashing the HTML will only say the framework hasn’t changed.

It’s projection. Paxton doesn’t like who’s benefiting.

I’m still missing your point. I’ve got all my apps I’ve downloaded backed up, at least for macOS. iOS… easier to grab the older ones off a pirate repository once Apple stops listing them. Are you trying to say that everyone should be running Debian Stable without non-free on commodity x86 or RISC-V hardware with only open source hardware gerbers and no proprietary chips?

Apple is the only provider of Apple IDs. Other yhan that, I’m not sure what gave you the impression I’m dependent on a single provider?

I’ve been an Apple customer for 35 years. Had an Apple account as long as Apple has had such things. A few years ago (specifically, when Apple started retiring 32-bit apps from the App Store) I saw where Apple was going and created a dedicated account for my Apple ID that’s separate from the one I use for my contact for Apple services. If Apple locked me out of my account today, I’d lose access to 14 years of app purchases on that account. That’s about it? And at some point I started using an alternative ID for some of my purchases, so I’d only lose access to some of them. And of course, I now keep copies of everything backed up, since they could vanish from Apple’s servers at any time.

Superfluous “a”

That’s the question, isn’t it? Can you actually buy a car in 2025?