> For your own personal sake, you may be selfishly wishing it’s as few people as possible. Eventually they’ll outlaw VPNs too and by then you’ll have little recourse. You can’t hide behind them forever, deeper change is needed.
It does not work that way in functioning democracies. This is like blithely raising people's electric bills in the name of preventing global warming. Noble aspirations but brain dead implementation that completely undermines the original goal. And fuels, one might add, the rise of political parties that just want to burn everything down.
Personally I went from more or less ignorant of these laws to completely outraged in the time it took to eat a couple of sausages.
Why don't we humans think this stuff through? Surely we can do better.
Marketing network security products is usually hard. Not any more. The practical effect of these so-called protection laws is to break shit across the entire Internet.
Hmm, maybe there's a simple legislative fix for this problem. Basically vendors that want to make you "rent" devices would have to allow termination for convenience at any time by customer including repayment of any fees paid by the customer for the device.
Termination for convenience is a standard term in contracts, hence well-understood by corporate lawyers. The repayment could be reduced using a depreciation schedule so the longer the device is in your hands the less that's returned.
I think this would work. The legal machinery is already there. The market would work out the details.
I'm planning to turn the VPN off when I don't need it. Mullvad is nice because you can just put money on the meter when you are traveling to locations that make it necessary.
I should mention that what pushed me over the edge was discovering that the FP problem was [among other things] triggered by a user comment that was then suppressed. However, it had a helpful message that I could solve the problem by uploading identification information to a website somewhere that I've never heard of.
Given the rate at which those sites are hacked, that's basically the following, simple procedure:
Step 1: Share your identifying information with the entire Internet.
Exactly. For example, what happens to open source projects where developers don't have access to the latest proprietary dev tools? Or, what happens to projects like Spring if AI tools can generate framework code from scratch? I've seen maven builds on Java projects that pull in hundreds or even thousands of libraries. 99% of that code is never even used.
The real changes to jobs will be driven by considerations like these. Not saying this will happen but you can't rule it out either.
Same here! We see them practically every day where I live - no feeder necessary, just flowers in bloom, preferably red[dish] ones.
Hummingbirds would be my favorite birds of all, except for the existence of owls. We have many owls in our neighborhood, including two that nest nearby. We know that mostly from hearing, since they do their best to stay hidden during daylight. However, they are pleasantly loud at night. That's why we know there are two of them or rather two nests--it's easy to pick up the direction of the sound.
> I base my paragraph on their choice of abandoning PostgreSQL and adopting ClickHouse(Bocharov 2018). The whole post is a great overview on trying to process data fast, without a single line on how to garantee its logical correctness/consistency in the face of changes.
I'm completely mystified how the author concludes that the switch from PostgreSQL to ClickHouse shows the root of this problem.
1. If the point is that PostgreSQL is somehow more less prone to error, it's not in this case. You can make the same mistake if you leave off the table_schema in information_schema.columns queries.
2. If the point is that Cloudflare should have somehow discovered this error through normalization and/or formal methods, perhaps he could demonstrate exactly how this would have (a) worked, (b) been less costly than finding and fixing the query through a better review process or testing, and (c) avoided generating other errors as a side effect.
I'm particularly mystified how lack of normalization is at fault. ClickHouse system.columns is normalized. And if you normalized the query result to remove duplicates that would just result in other kinds of bugs as in 2c above.
It does not work that way in functioning democracies. This is like blithely raising people's electric bills in the name of preventing global warming. Noble aspirations but brain dead implementation that completely undermines the original goal. And fuels, one might add, the rise of political parties that just want to burn everything down.
Personally I went from more or less ignorant of these laws to completely outraged in the time it took to eat a couple of sausages.
Why don't we humans think this stuff through? Surely we can do better.
reply