Comment Re:"forced labor" (Score 2) 183
By that time there were millions of slaves in the U.S. and as you pointed out, they reproduced and even resulted in a surplus for the larger plantations. There was a lively internal slave trade at that point.
By that time there were millions of slaves in the U.S. and as you pointed out, they reproduced and even resulted in a surplus for the larger plantations. There was a lively internal slave trade at that point.
Actually, the war on poverty was working until the GOP insisted on surrendering.
And yes, businesses that mooch on the taxpayer to supplement their inadequate payroll are evil. They know damned well they are mooching off of people with a lot less than they already have.
We don't claim the car thief is blameless if you leave your keys in your car, do we?
As timeOday said, they cost about 10 years wages for an equivalent free worker, so if the owner didn't keep them alive and well at least that long, it was a losing proposition.
So as despicable as the practice was, the modern practice is in some ways worse.
That's the new innovation of forced labor. In the bad old days, slaves were quite expensive so you had to provide food, clothing, shelter, and at least minimal healthcare.
The new improved forced labor lets them pick up the slaves cheap, provide them minimal food and shelter and just let them die from overwork.
Both upsides were already easily solvable. Most distro's rc scripts already call a function to start a daemon. That could easily have called a helper program to set up the cgroup and register on dbus to act as a controller for the group.
Meanwhile, at least Debian's rc scripts already had dependencies listed in their headers that could be used to compute a start order. It could as easily be used to compute a makefile to start in parallel.
The problem is, now that the init process will be such a hairball of dependencies, it becomes harder to implement such solutions without seemingly unrelated bits breaking. For example, no reasonable person expects the GUI desktop to break if you switch out init. (and no reasonable person creates such a dependency)
Or, you go with signed routes. That is, you use a public key system to prove that you have the right to broadcast a route for a particular subnet.
In practice, it will probably mean some router upgrades. No more router cpus that were considered a bit underpowered for a calculator in the '90s. However, as an interim measure, it could be used to set some BGP filters to limit the potential damage.
The problem is, we're tipped over into corporatism where the net is controlled by a very few very large legal sictions tha tthe courts insist are somehow people.
You worry about the bad old government censoring the net but forget to worry about the ISPs censoring the net.
I can't imagine why you think the overmetered network protects us from the market cornering legislation and the pompous asses. Without proper net neutrality, we get all of the above and nowhere to turn.
I appreciate the offer, but I'm really not qualified. My interest is of the avid armchair variety. As I understand it, the dialysate is the key to making it work. Previous experiments achieved some removal of urea but it wasn't adequate or it caused electrolyte imbalances. In all forms of dialysis, it's something that could easily be mixed up at home but for the requirement of a sterile solution for hemo or peritoneal dialysis.
Waiting to put on a black shirt?
Who is first on your extermination list?
If the civilian police could do the search, then they probably should have.
If the search was done on-duty, it used military resources and so should not be reported.
I read somewhere that not only was Comcast doing their hotspot crap, but that they will also be doing javascript injection to insert ads on anyone browsing the web through it.
Obviously Comcast is sifting whatever data goes to/from their customers, not just for 'bots' but also for commercial and data broker value. Even this relatively passive activity is intolerable to me.
Does anyone even trust their DNS?
Frankly, these reported 'Tor' issues are just the tip of the iceberg, and not even all that interesting in terms of what customers should be up in arms about. It is far more likely to be related to abusing bandwidth (a legitimate concern for Comcast) than to actually running Tor.
People should be screaming about the level of monitoring that is clearly happening. But I guess consumers are mostly too stupid to understand just how badly their privacy is being trampled.
There is a solution. Run a VPN. If Comcast complains, cut the T.V. service and change to the business internet service (which actually costs less).
-Matt
You'd be surprised how much use can be made of 30 minutes of information. Also, in the absence of an accident, the information you mentioned cannot determine if anyone was actually put at risk. Practically no car has GPS connected with control positions and few record 30 minutes.
Will legacy cars have an automatic out since the recorded information won't be there?
How about if the black box malfunctions or "malfunctions"
This file will self-destruct in five minutes.