olafure

Excuse me, was it an F or an F# at end of bar 846?

Here's a hypothetical but a realistic scenario that not having reproducible builds is a major issue:

1. I create an app for a client.

2. Client installs the app on their 10,000 enterprise mobile devices and trains the users.

3. Month passes. I've changed everything in the app.

4. Major security or outage event happens. I need to change a line in the app and those 10,000 devices need to be updated ASAP.

5. If I can't checkout the old version, change the line and ship it without wondering "what else will change in this build" - then both me and my client are going to have a bad time.

It will take two weeks for a full qa/audit of the app and there's no time for that.

I think we're due a full disclosure on this favicon service, what information is collected and what is stored.

DDG has repeatedly said that they have "not collected any personal information".

For example,

1. Does the service store the fact that it got a request for a domain?

2. Does it store any ID along with that information and if so, how unique is that ID? How is it generated and what is it linked to?

3. What other information is stored along with the request?

4. How does DDG process this information?

5. Who has or can get access to this information?

I'd really like them to establish a "counterfeit reviews" unit too.

Many years ago their review system was one of their businesses advantages. Many users and fairly honest reviews.

Now it's rife with fake and bought reviews, rendering it useless.

I used to use Amazon a lot. The two big factor were pricing and reviews.

Today their review system is massively rigged and can't be trusted.

The catastrophe would be worthy of inclusion in Randall Monroe's What If? book.

$3600/year is significant for a startup on a shoestring budget.

I like Prusa, but after they stopped releasing firmware updates for my MK2S for no good reason, so did my business with them. Such a shame.

I start bash scripts, by setting the holy trinity: set -eou

That prevents end-of-the-world scenario like the one above, if the script derails.

Tinder and Mozilla have the same score of 33%. I don't agree with that. Tinder willingly shares very, very personal data along with your contacts (assuming without said contact consent).