throwawayy293 (u/throwawayy293)

throwawayy293 commented on Web Scrapers Claim to Sell Personal Data on Facebook Users on a Hacker Forum privacyaffairs.com/facebo... · Posted by u/comprev

throwaway78981 · 4 years ago

Some might laugh this off as 'oh it's just scraping'. But I remember reading some comments in HN that there are apps that can scan faces and pull personal info including where they live, work etc. So each leak uncovers a person little by little.

This vindicates the stance taken by Signal to not even collect metadata.

Edit: I mean surreptitiously scan the face of a stranger you see in public and the app will tell you about them. Don't know names of the apps.

throwawayy293 · 4 years ago

https://www.wikipedia.org/wiki/Clearview_AI already does that too

throwawayy293 commented on What the GNU? ariadnavigo.xyz/posts/wha... · Posted by u/nathell

enriquto · 4 years ago

This kind of emotional articles are the best motivation to renew my FSF membership.

throwawayy293 · 4 years ago

increasing my donation to FSF. we need more education on why free software and the GPL matters. Everyday is an attack on the computing freedoms that people take for granted.

throwawayy293 commented on FyneDesk, a fresh look at what it means to be a desktop environment fyne.io/fynedesk/... · Posted by u/pjmlp

pjmlp · 4 years ago

Yeah, but then it wouldn't be with Go.

throwawayy293 · 4 years ago

point being? this Go brigading is annoying

throwawayy293 commented on Docker Desktop no longer free for large companies theregister.com/2021/08/3... · Posted by u/alanwreath

throwawayy293 · 4 years ago

I personally support Docker Desktop for Mac for an organization of 250-300 engineers.

I have been supporting it for 2 years now. Been through all the Docker Desktop upgrades, performance issues everytthing. I have researched docker performance on macs running k3d + k3s + istio and a bunch of microservices. I have had to jump into the internals of Docker daemon and docker cli and networking to solve how docker networks are provisioned for various proxying issues.

1. Docker dragged their feet with native performance for file syncing. We have to selectively enable it and just so that it doesn't bog the machine down.

2. When running it gets the CPU running at 75-80C, causing the fan to run non-stop at 3000 rpm at least. It is definitely impact by bad macbook pro design, which is terrible at airflow and heat sink activities

3. We were on unstable for a bit to test the new file syncing approach. Docker dropped that in stable and said "deal with it"

4. The paid forced upgrade notification means that I can't peg the Docker Desktop version for the whole org at a certain version.

5. Right after we switch from the unstable to stable, the next minor version is a breaking change.

6. Number 4 would be fine it docker would keep to their guarantee of stable being stable. They do a terrible job of being backwards compatible. The current stable we had was 3.3.1. With the constant minor upgrades, and pushing people, some people went to 3.6.0. (the latest as of yesterday, Aug 30) This broke everything inexplicable with just a VM error where k3d would keep crashing. I downgraded everyone back to 3.3.1 to get teams unblocked while waiting for me to find a fix.

7. Finding a fix usually involves waiting for Docker to prioritize something but at this point I don't trust that Docker know what it is doing.

I am currently pushing for Linux laptops, hosted dev environments and reducing the need to run distributed monoliths. We shall see.