> "their fair share" is nebulous on purpose, because if they actually specified, then it could be argued against. By
> keeping it undefined, there is no argument that can be made. The people making that argument win by default,
> because you can't argue against it.

Its worst than that, you can't argue against it because it is absolutely correct in its nebulosity.

By saying their "Fair Share" they can invoke not just anything but...whatever YOU think. If you think $1 is fair, then that is what they just said isn't it? If you think $1million is, they said that too.... they just didn't explicitly say either because they let you fill in the blank!

How can anyone be againt one paying their "fair share"? Clearly if its fair, and its their share, they should pay it by definition right?

Its kind of like "tax reform". You can't be against "reform" without being regressive right? So once something has been called reform, anyone againt it is stuck with more complicated arguments trying to explain why it isn't actually reform, and usually has to use the word reform in its name, this implicitly contradicting himself via raw terminology.

A "Fair share" that isn't fair is a contradiction in terms, so it puts anyone who disagrees with it on automatic uphill footing.

So you setup gpg, setup a key as normal.

Setup git-annex. It supports several backends, including rsync which works with rsync.net and an amazon options, and a few others. I only use ssh backends myself.

Anyway, you can setup some backends as encrypted backends and anything that goes there gets encrypted. It can only be read by someone with a clone of the original git repo and the gpg key to decrypt it. So you keep an encrypted copy of that seperately. Its much smaller, so you can keep many copies of it, its just index information.

Then after a disaster, you get a copy of the index/key, decrypt it, and have full access to your offsite cloud storage. You can even have multiple types of backend at different services. Hell if you have a friend who runs linux and doesn't mind you using some of his disk, you can use it as a remote.

Oh, and carry an encrypted clone of the index repo with you on a usb stick.

If the password/phrase is good you shouldn't need to worry too much. Learning to come up with decent enough passwords is pretty easy too. Everybody has their favorite methods, I like things with mnemonics, they work shockingly well, I could tell you with decent accuracy some root passwords we used for all of a few months at a job I left 10 years ago.

I would think this case would be easy to distinguish from others. Basically if matter itself were expanding the way we often talk about space as, yes I could see this constant expansion pressure looking a lot like gravity but, anything on the surface that was expanding would also be moving further away from anything next to it, so if you built a structure, the walls of the structure would suffer increasing internal stress from the expansion AND its corners would be pulled away from eachother by the ground expansion.

Oh well if it MAY do something desirable through a mechanism you can imagine in the simple fantasies of your head, then by all means lets toss millions of dollars at it, surely its not only easier than finding people with the actual interest and means and a plan, lets continue just making our own and arresting them for show.

This totally justifies the invasion of our privacy so wide scale that they will drop criminal charges against people rather than admit their capabilities in court.

Look its totally working guys, all that surveillance and invasion into our privacy and they are really starting to catch the guys they create and setup for show.

so I was working at a University several years back. At the time there was an old webserver, actually a desktop. It was previously used by an admin who left and left behind a web service with notes. It was a collection of brain dumps, notes, old emails etc....which all of us admins knew about and occasionally referenced, that's why we never shut it down....or particularly considered its contents.

That is until we saw an article in the local school student run rumor mill, which most of us read, about this fascinating website on campus with a number of internal emails shedding new insight on some of the inner workings of the staff.

Of course, we saw the article because half the staff found the rumor site amusing and read it on a regular basis, so it was shut down immediately, but it didn't take long before someone posted a link to it in the google cache. Smart kids, as annoying as it was, it still put a smile on my face to see how resourceful they were.

Oh my code is embarassing as shit, don;'t get me wrong on that point. However, most code is a bit of a mess and a lot of it is not terribly well organized. So if yours is so much of a mess that it is actually the reason you don't want to release it (rather than a philosophical disagreement with open source/free software, which while i don't share, I do understand), then maybe basing products around it is something you should at least think twice about.

And thats before even getting to how its no excuse for vipolating the license.

However, I think you are actually right. This is very likely a simple screw up, and its of exactly the type I see all the time when you have people working towards deadlines and manual processes. I would almost bet you dollars to donuts that somewhere there is an email that was the only instruction a guy got that poorly outlined how to package it all up, which left out half the details or wasn't updated between its first version and when development changed their paths.

Seriously, I could totally see this sort of error as a simple fuckup. My only objection here is to the proposition made by others that it might be intentional due to the state of the code, because, that just doesn't fly in any good way for them in this situation.

This DOES however look like exactly the sort of error you get from bitrot in documentation for manual processes though.

which is exactly why it should just be banned. There really is no excuse for killing a person in your custody. Frankly, I consider it murder regardless what the law says, no better than what he did.

Nope stud finders wont even find studs in my house because its old enough to have horse hair plaster, so the studs are covered by horizontal wood slats. SOME stud finders kinda work, most don't work well (admittedly, its been a few years, maybe they got better?)

Also it wouldn't really identify the object, just that it looked like something more solid was there.

The reply of metal detector might work better....but there is also a metal chimney pipe for an old gas fireplace that used to be in the room also in the wall, along with possible steam pipes for the single pipe steam heat (as if it wasn't obvious this isn't a new house).

However.... the rooms on either side of the wall in question have drop ceilings, and there is an odd shape to the wall that makes us think something may have been in there.....but it is entirely possible that bulge in the wall has to do with the installation of the gas fireplace and chimney pipe and not the safe.

It may be the bulge exists because of the old fireplace and that is why she chose that wall, rather than the other way around.... if it was even in there, this is just kind of an old family memory of the actions of someone who has been dead for maybe half a century (she was gone before I was born, so maybe less but still decades).

We don't expect there is actually anything in there, but hey it wouldn't be the first time we found something. We actually found an invitation to a "sock hop" in 1911 (at an address which we found is currently a building with a 1920s corner stone) under one of the floors.

This is exactly the sort of thing i love seeing a project and nice explanation on. This sort of thing will never be my career path, but, is the sort of thing I might play with as a hobby project and I love seeing the areas a person can get into without much formal training expand.

Of course, I already have a use for such a thing but.... I think it will be easier to use a small drill and a camera to find out if the rumors of my great grandmother's old safe still being in the walls somewhere (plastered over of course) is true.

Have to imagine that will be cheaper and faster (if not cooler) than building one of these.

If you are so embarassed by your code as to not want to publish it, might I suggest you SHOULD be too embarassed to sell products based on it or otherwise distribute it in binary form.

I have to say, its nice to know Slashdot respects Betteridge's law, it would be a waste of time afterall to have to read past the headline to know that they have, in fact, not run out of money at all. If they hadn't clearly indicated that in the headline with the '?' which, in headlines answers the question with an implicit no; then I might wonder if it was true or not and have to read further.

I think you missed the part where one developer reverese engineered how the protocol worked and the developer had enough of a shit fit that it became apparent that continuing to use their software was going to be problematic AND it was already the case that many people didn't want to use it for issues of licensing.

Even so, nobody is under any obligation to keep using a tool someone else makes, even if they like it. He put in the work. Nobody has some right to have others continue to use a service that they don't need and can handle for themselves.

Couple of issues here. First, these are not the same. A business is offering a service to the public and then denying people who walk in, whereas a customer is simply deciding which offer he takes. This is where the stark differences only begin.

a customer can, unless the product is in some special regulated category, be anyone. In fact, even if its regulated, most criteria we are concerned with here could never really be used in licensing them, so its kind of irrelevant. Whereas a shop owner is someone who sought out and obtained a charter from the government which grants him limited liability, so he is not fully responsible for what he does in the course of his business.

This right here is the point where, in my eyes, the whole game changes. A company is a chartered entity authorized by the government. If he was a private individual servicing people out of his private home, or he was running a private members-only club.... I wouldn't argue at all, this would be quite unfair. I fully support the right of organizations like the KKK setting up members only clubs and selling whatever they want (short of slaves) to their own members.

However, when these people chartered their businesses and opened public businesses, they do so with benefits like limited liability which, I have no problem with the chartering entitiy putting restrictions on if those charters.

Which has been almost as great a service in and of itself as the content of the releases. If they had released it all at once, the administration could have prepared a cohesive response. The slow dissemination tripped them up in lie after lie in their attempts to cover up and deny the truth.

I, for one, thank them for exposing the domestic enemies of the public who operate within the highest levels of out own government.

I like fluff. I like fluff with chunky peanut butter and some jelly. This article though, this isn't my kind of fluff. Its not even making real predictions, its stating the obvious and moving on. Autonomous cars could be HUGE.

DUI (or OUI in my state)? Thing of the past. Drunken crashes? Gone with them.

need to be 17 to drive? Why? Hell, put a parental lock on the car and designate the destination. Going to work? Bring a book for the ride! Shit, tell it you want a large latte, whole milk, no sugar from dunkies, and it can coordinate with the dunkies in the area to get you one the fastest with the least time off your route. In fact, maybe it skips the closest dunkies, because you will be there before the late is ready and nobody wants to wait.