Washington post running the same headline, bravo whoever wrote the headline on hn.

quiet except for a few microsoft addresses when you run a spotlight command searching your own apple brand hard disk.

https://en.wikipedia.org/wiki/Spotlight_(software)#Privacy_c...

Since they have Little Snitch, that network request will never go out.

Didn't know about this though -- thanks. Guess I should be getting a copy of Little Snitch myself, heh

Also I disable spotlight - saves battery plus I know here I left all my shit :)

You may want to have a look at the number of possible events sent to America compared between 'basic' and 'full' (93|112), (410|422).

https://www.ghacks.net/2018/11/23/german-federal-office-bsi-...

Office then has approximately 50 times that number again:

https://www.theregister.co.uk/2018/11/16/microsoft_gdpr/

People are upset because there is no way to set this to zero aside from unplugging the machine from the network.

Thanks for the links.

You could also try installing O&O ShutUp10. I've been running it since I installed Windows 10.

You can download it (it's a free app) at https://www.oo-software.com/en/shutup10.

It nulls out a bunch of telemetry related addresses in your /etc/hosts file, and allows you to configure over a 100 different privacy settings from 1 place.

Microsoft have a long history of overriding and ignoring hosts configurations to their own addresses so I am skeptical on the utility of this. I think you might be a little too trusting.

I do not have time to repeat the efforts outlined by government contractors in the above links with this add on applied, I doubt you do either.

Better for me to avoid the OS altogether.

They do ignore the hosts file, it’s true - but they don’t ignore windows built-in firewall. I used it to blacklist a bunch of hosts when I had wireshark open to diagnose an unrelated problem and noticed all my keystrokes in the start menu search box were being sent to MS, as well as details about every application I launched. The search box keystrokes were going to onedrive - presumably to show me files matching from there, but I don’t see why they can’t download a list of files and locally search that. Sending every keystroke in that box is unnecessary.

Very interesting info, but they own the OS and in some cases the compiler: https://www.infoq.com/news/2016/06/visual-cpp-telemetry

Given that, I don't care to engage in whack a mole with them. They have the upper hand.

Safe for visual studio and visual studio code users to assume that the IDEs are sending telemetry too.

In my case the best thing is to avoid the OS. And github and whatever else their malign influence could eventually own.

> I know what I'm getting into by using Windows.

the problem is rather that you think you do - but you don't and can't.

No, I understand that I'm not in full control over what MS does with privacy related settings.

By using Windows, I'm accepting that, and in my case, instead of hunting through 15 different privacy settings screens in the control panel, I use that app to have them all in 1 place.

You conveniently left this out of your original comment, where you called people silly for not having things configured correctly.

This is a bit like saying that you've never had a problem with your car guzzling gas, or falsifying emissions, and then later casually mentioning that you actually own an electric motorcycle.

> You conveniently left this out of your original comment, where you called people silly for not having things configured correctly.

To prevent the issue the article spoke of only requires setting (2) options in the standard Microsoft settings, and also not signing in with a Live account.

You don't need additional tools for that.

Tor doesn't support UDP so no HTTP/3 but one would expect most services would be available for the foreseeable future over HTTP/2 as well.

like websites without javascript?

Working without javascript requires development time. Running old versions of HTTP doesn't. Version 1.1 is going to be fully supported for a long time.

Working without javascript requires money. Running old versions of HTTP requires ????.

Running old versions of HTTP requires nothing because people will need to support legacy devices for a long time, and it's obviously already implemented in all major components (Servers, CDNs, Clients, etc.)

You (will) run HTTP/3, because it is more efficient, meaning that your servers will be able to service more request.

You run HTTP/2 and HTTP/1, because a lot of people are still using that, and you don't want to lose them. This especially applies to mobile devices, many of which are stuck with software that cannot be updated for various reasons.

There's no threat of the majority of websites going HTTP/3 anytime soon. By the time that might be a possibility, Tor will catch up.

"Will" - are you from the future?

If it becomes the dominant way of serving web pages, you should realize that tor will add support.

How can I realise something that may or may not happen?

Everything that goes over UDP is not supported as of 2018 and some volunteer project is going to figure this out?

Hubris.

Unless they lose 99% of their users, there's enough demand. Your level of pessimism on this specific detail is ridiculous. Tor might not last forever, but it won't be lack of HTTP support that kills it.

If you wait a few years for HTTP/3 to settle, proxies will be available that could be glued into tor inside a weekend hackathon.

> If you wait a few years for HTTP/3 to settle, proxies will be available that could be glued into tor inside a weekend hackathon.

In 16 years they have not managed to support UDP and now you say of a project (you are not familiar with...), that they can get it up over a weekend hackathon.

And you are calling me ridiculous?

This speaks volumes for your predictive ability.

Good day, sir!

Do you have a contact address? I could mark my calendar for 2025. "some proxy with HTTP >= 3 and HTTP < 3 will exist" is a very basic prediction. It wouldn't have to be integrated into the tor codebase either, just spawned by the tor process.

Tor doesn't have UDP support right now because it doesn't need it for anything. The last 16 years are not equal to the next 16 years, surprisingly enough.

The first one requires money be spent on every site.

The second one requires that the feature be maintained in major web servers. Which it will be. On a per-site basis, the developer needs to do nothing.

Still not getting it. Every site is hosted. The hosting company needs to spend money on HTTP/2, and be allowed to use it. The networks need to allow TCP through. All the steps down to the transport layer now require legacy maintenance.

Lots of things need to happen for HTTP/2 to 'stay alive'.

Your use of the future tense does not convince me.

The hosting company needs to spend basically nothing, because it's built into the software.

It's built into the software because enough sites will still be using it fifty years from now, even if it's a minority of traffic.

I seriously doubt you'll ever see TCP blocked.

Is there anything that prevents Tor from supporting this protocol?