skynet-9000

I'd like to take a moment and refute these silly arguments that I made.

> You are forgetting that DRM stopped all that piracy that bankrupted the movie industry. That's also why there were so few movies released in the last 15 months or so.

DRM didn't stop anything, and the movie industry is not bankrupt.

One could easily argue that there might be other reasons why few movies were released since the start of 2019.

> It really debunks that myth that open source software could ever handle the strong encryption that's so desperately needed to protect new movies and TV shows from showing up on The Pirate Bay.

The myth? Do you realize that literally every single web browser is built on an open source foundation? And how is decryption in the browser going to keep a determined person from grabbing the screen output or even grabbing the keys?

Remember, not your keys, not your lock.

> I for one welcome this cogent and secure technological response to a market issue.

Why would a technological response be appropriate for a market issue?

True. :) but adding /s is not as much fun, especially on April 1st.

A new Java application? Java is getting pretty long in the tooth. You might be better off building on top of Go or Rust, especially for those specific scenarios (Go in particular was designed to build network services.)

Or k3s (https://k3s.io), which is Rancher's awesome and lightweight Kubernetes distribution.

You are forgetting that DRM stopped all that piracy that bankrupted the movie industry. That's also why there were so few movies released in the last 15 months or so.

It really debunks that myth that open source software could ever handle the strong encryption that's so desperately needed to protect new movies and TV shows from showing up on The Pirate Bay.

I for one welcome this cogent and secure technological response to a market issue.

This only applies to the first request until the cache expires.

If a client makes 50 requests before the cache expires, then those will all be based on the cached result.

This is still efficient enough that there's probably no more than a single DNS hit for every web page load, even with a short (say, 5 second) TTL, because most web assets will be loaded within that five second window. (If your web page takes longer than 5 seconds to load, you have far more significant issues than a few UDP DNS requests.)

Whether the list of invalid use cases are straw man arguments are left as an exercise to the reader, but this article seems to be arguing only one side of the perfectly valid trade-off between flexibility (low TTL's) versus latency (high TTL's).

In other words, if high TTL's are so great and there's no compelling reasons to not use them, why not make them one year? Ten years?

On the other hand, many (probably most) applications can probably absorb a five-minute outage without anyone screaming too loudly.

Clearly there is a balance between "long" and "short" (probably somewhere between one second and infinity). It's good to think about these things and optimize for lower latency, but if five-minute or longer TTL's simply don't fit your use case, then don't feel bad about it.

I watched a documentary about an attempt at this, and it almost started global thermonuclear war! Here's a clip: https://www.youtube.com/watch?v=NHWjlCaIrQo

You might want to build some rate limiting into your lambda as well!

> Twitter systematically allows illegal behavior like parler did.

Does this sound libelous to you, and do you have evidence supporting this? Even AWS's response didn't allege Parler "systematically allowed illegal behavior".

> If you’re not flaunting ToS,... you should be fine.

https://aws.amazon.com/aup/: You may not use, or encourage, promote, facilitate or instruct others to use, the Services.. for any.. offensive use, or to transmit, store, display, distribute or otherwise make available content that is.. offensive.

What does offensive mean? Who defines it?

Isn't that part of the charm? ;) You can call them or email them for details (http://www.myatari.com/atariord.htm), or check out their Ebay store:

http://www.ebaystores.com/Atari-Sales-and-Service/Atari-8-Bi...

These use Ethereum, not Bitcoin, and ETH is usually mined with GPUs, not CPUs. This isn't overly relevant to your point, since it probably doesn't matter too much in terms of power consumption per unit of work; GPUs consume huge amounts of power and generate lots of heat, just like CPUs, and often more.

My first Atari was a 130XE. I now have 800XL's and a couple more XE's, but my favorite case design is still the XE. It just always seemed like a futuristic case to me, while the XL beige case kinda felt more like the previous era. Of course, beauty is in the eye of the beholder.

My Atari (no affiliation, but a happy customer since the 90's) still has a ton of (brand new, old stock) parts and (in some cases) brand new computers, and they're stored in beautiful northern California, so they don't get any UV damage. They're also absolute knowledge sinks for Atari's (both 8-bit and ST):

http://www.myatari.com/

> if unions hadn't existed, you'd still be slaving away 6 days a week (minimum), 10 hours a day, your children would be working instead of going to school and everything labor related would certainly have been worse.

This is not historically accurate.

For example, Henry Ford actually increased wages (without worrying about unions, and he had literal enforcers to bully people.)

He claimed to be doing it for altruistic reasons, and so that workers in his plants could afford a Ford, but the real reason was because he had to, because people could choose to work elsewhere, even if they had to move. Also, he attracted people from other cities and states to move to Dearborn.

This is the real antidote to union-busting and union-towns. Any job that basically needs a person can always be paid minimally, but multiple employers have to compete for that person; perhaps an alternative job is far away, but mobile people will always be worth more because their market is larger. It was a bit different 150 years ago during the Industrial Revolution, because of information asymmetry and the cost of relocation.

So why form a union? Just get a better job from an employer that literally values you more. It's not like these companies don't exist.

> a great deal of the benefit of salt comes from friction as cars drive over it

You may have never tossed a handful of rock salt on steps that have a quarter-inch of ice on them and watch holes actually form in the ice within a half hour or so.

who owns any of those companies? the shareholders. are they treated any better?

the issue is the spectrum auctions.. a new carrier can't even get off the ground, even if they were willing to fight through the morass of local and competing regulations to put up towers etc.

that's what socialism is (well, if they're govt controlled or effectively govt controlled). real capitalism encourages competition, and real entrepreneurs try to discourage it and gain an effective monopoly. that tension is part of the beauty of the whole thing, but when govt approves these mergers with government granted monopolies (i.e., the wireless spectrum), then it all goes to pot very fast.

Their prepaid plan is only $25/mo w/ 8gb lte when prepaid the year in advance. That's wayyy cheaper than any of the other big players, and their network/coverage is supposed to be better than t-mobile (and almost as good as verizon).

Incorrect title. Nothing in the title about workers elsewhere being inspired.

Wapo title: Amazon fights aggressively to defeat union drive in Alabama, fearing a coming wave

Subtitle: Amazon’s relentless push to beat back a union drive among warehouse workers mirrors the company’s past efforts to oppose unions in Seattle, New York, Canada and the United Kingdom

"All" the foods you buy? This is a seriously clickbaity headline and not even what the Oxfam source material claims. (It would be slightly more correct if it said, "All the junk food you buy in the grocery store")

In that case, the rights of the (private) service provider are in tension with those of the (also private) individual, so it's a matter for legislation and the courts. Congress has passed laws protecting the speech of the individual within certain types of service providers, i.e. telecom/ISP/website publishers.

You can say anything you want, as long as you do not infringe on my rights, such as by consuming my resources (time, telecom services, fax paper, etc) when I explicitly said not to (via a Do Not Call listing, etc.)

It's similar to a No Trespassing sign; you can picket on public property (free speech), but doing that on private property (when marked with a sign that fit certain criteria, in most states) might get you arrested and charged with a crime.

In the U.S., the rights of the individual generally trump "public interest".

> Swartz never created a social media platform nor had to make decisions on how to moderate user generated content across millions of users.

He is credited as a co-founder of Reddit.

https://en.wikipedia.org/wiki/Aaron_Swartz

Things change; the liberal become illiberal.

Twitter used to be "the free speech wing of the free speech party"[0]

The American left used to stand up and fight for free speech. Only eight years ago, the ACLU defended the KKK in court.[1]

0. https://finance.yahoo.com/news/twitter-still-free-speech-win...

1. https://www.aclu.org/press-releases/aclu-em-defends-kkks-rig...

Why does an air filter need wifi?

> Don't pretend any other country have as much surveillance capability as the US does.

The level of surveillance in Xinjiang vastly exceed that of anywhere else in the world except for military installations.

mitigations? you mean exploits?

Agreed. This is the "Francis Bacon" I was expecting: https://en.wikipedia.org/wiki/Francis_Bacon

> Apple prioritise the user at the expense of the developer. I think this is the right balance.

Not for the developer.

We always use interns to do security critical work -- the less experience, the better. We also have exacting security standards, and a Critical Password Policy, since there are no non-critical passwords.

Critical Password Policy

Rule 1: All critical passwords must contain the company name, lower case, with no special characters or spaces.

Rule 2: All critical passwords must have between 3 and 1024 randomly selected sequential integers appended, each of no less than 1 and no greater than 3.

When you are creating your critical passwords, it is critical that you follow the rules in the exact sequence as stated above, and that you do not introduce any external sources of randomness or entropy.

Failing to follow this Critical Password Policy may result in your dismissal and later blame before a Congressional committee.