nkellenicki

As long as you keep your node up and running your content will never disappear. So if you just want to share files with friends I can see this working well - just keep your node available.

The "device information" is likely an opaque ID, and the "location" will likely be encrypted using an asymmetric key-pair set up during the pairing process, so the only thing capable of decrypting the location will be your phone.

The part you're correct about is that as they control the device, there's nothing saying they can't build a backdoor into it that reports the information (ie. location) back to them once it hits your phone. And we're also taking it on trust that it works the way they say it works, as it's not open-source.

But as someone else commented, eventually you have to trust something.

They don't have that information about you. From the bottom of that page:

"The Find My network extends these capabilities by locating missing devices even if they can’t or don’t connect to the internet. The Find My network is a crowdsourced network of hundreds of millions of Apple devices that use Bluetooth wireless technology to detect missing devices or items nearby, and report their approximate location back to the owner. The entire process is end-to-end encrypted and anonymous, so no one else, not even Apple or the third-party manufacturer, can view a device’s location or information."

I don't use lvm often enough to memorise the commands. "rm spacer.img" is short and easy for _anyone_ to remember.

None of that is even remotely related to your initial point.

Because it's abstract. The people aren't _actively_ having to do anything, such as hand over their records - it's happening away from them. It's hard to connect with abstract.

It's easier for people to connect with the reason _for_ doing it. Stop the terrorists, it may happen to you, etc. But the other way round is harder because it's invisible and you can live your life without caring. Even the warnings fall on deaf ears because "come on, you're being irrational" or "meh, doesn't affect me".

Yes - the ESP32 is capable of Bluetooth Low Energy to talk with your phone. But, you're responsible for implementing the functionality you want yourself.

With my custom watchface I built, I sync ntp and weather every hour. I get about 100 hours of battery from it (4+ days).

I still use RSS. One thing I've discovered is that nearly every site offers an RSS feed. I presume they're not aware of this, and that whatever CMS they use (WordPress, etc) offers it out of the box. Often times it takes a simple "View Source" to find it.

RSS doesn't seem to be dying, it's just that it's no longer mainstream since Google Reader died. I run my own instance of TinyTinyRSS on my server and couldn't be happier.

> ES and other companies have a business that sells a managed version of their product.

Therein lies the flaw in the argument. If a company decides to develop something and open source it, it's not a product. If the company chooses to assign their time and resources to help develop it, great, but the moment it no longer becomes beneficial for them to keep supporting it, they'll drop it and leave it to the community.

Many companies invest time and resources into furthering open source projects without being the owner/creator of it. This is no different, whether they created it in the first place or not - they chose to open source it.

Building your business around something that you give away for free will always be a terrible business model.

You can't install Windows on it. The processor isn't x86, it's custom Apple silicon built on the ARM architecture. Windows is incompatible.

A couple of weeks ago AT&T, Verizon, Sprint, and T-Mobile announced that they had started working on their cross-provider RCS implementation - https://www.theverge.com/2019/10/24/20931202/us-carriers-rcs...

Does Google doing this essentially mean they've gotten sick of waiting for the carriers and decided to bypass them entirely? If so, the carriers can't be happy about that.

I had honestly never heard of Netlify. I thought GitHub Pages was the standard, with S3 static hosting a second (more involved) option.

EDIT: Googling suggests Netlify offers a build, deploy, hosting pipeline all-in-one box. Which is substantially more than any of the projects mentioned here. These serve a single purpose - simple hosting of static websites.