Horrible as it is, this is a battle of social acceptance. Google wants wearing a camera on your face to become socially acceptable. Those of us who don't want to see this become the norm want to make sure it doesn't become socially acceptable.
Unfortunately the best way to achieve this is by being hostile towards people wearing the damn thing. Just as walking up to some random couple at a bar, pulling out your cellphone, and pointing the camera at them would likely attract hostility as a non-socially acceptable behaviour, so must wearing google glass.
This doesn't have to be violence, but it does have to be enough to make:
- the individual unhappy (negative re-enforcement against the socially unacceptable behaviour) - observers nervous about engaging in the behaviour themselves (hmm, everyones telling this guy to shove his google glass up his ass, and one guy is even offering to help, maybe I shouldn't buy one just yet!) - businesses nervous about incidents, hopefully enough to ban the devices
Yes surveillance is ubiquitous, but it's usually managed by business owners or government agencies, which means it's very unlikely to end up on youtube. A bar wouldn't survive very long if they made a habit of posting embarrassing moments from their surveillance tapes on the web.
People with cellphone cameras is also ubiquitous, but using one to record something is usually fairly obvious.
Covert surveillance is also now mostly trivial, but it's not socially acceptable and very few people actually do it, so the chances of being covertly recorded in a bar are pretty slim unless someone has reason to.
Google glass is in an all new category. To many, walking up to a table while wearing google glass is roughly equivalent to walking up to that table with your cellphone camera pointed at the people sitting their, and thus has gotten much the reaction you would expect.
It's a fairly commonly used term, and I wouldn't really call it a grudge so much as an acknowledgement of the disconnect in reality with those who assume an out of proportion interest in anything involving space.
Lots of people find space interesting and are generally supportive of ongoing research and efforts, but generally maintain a healthy balance of other interests.
Space nuttery is in my opinion defined by an unhealthy and unrealistic obsession with space. These are people who would (or at least have said they would) sell all their worldly possessions for the opportunity to spend some time in space, who would volunteer for a one way trip to mars. Basically a space nutter is someone who spends a fair bit of time flailing their arms and shouting "SPAAACCEEE" excitedly.
Business in general has become very risk adverse with a few exceptions (spacex and google being the big ones). Many of us feel constrained in this environment where everything we do has to mostly work or we won't get a second change or an opportunity to improve it. Everything has become about risk management and ROI and soul crushing metrics. It's very refreshing to see this kind of apparent "lets just do something we know probably won't work the first time, and keep doing it until it does" attitude.
Indeed. I'm not a space nutter, but this impresses the hell out of me. With a problem this hard, the fact that they are down to minor mistakes like this and not major fundamental issues is awesome.
One keeps backups to protect themselves against such horrible, very rookie mistakes. They happen. Yes we can rage about how it shouldn't have happened, and yes someone at steam should get slapped, and yes "everyone should have backups" doesn't lessen the reality of what happened here, but having backups is still a good idea and is the difference between an inconvenience and sobbing in the corner when something like this happens.
At this point I'm far more inclined to jump ship to BSD (which to be honest feels very much like Linux did back before all this nonsense) and contribute my efforts to making it what I want. Neither is really what I want, but I feel at this point BSD is actually closer, and at least philosophically more aligned with what I'm looking for.
I'm not looking to exaggerate, but i do feel the BSD developer base is noticeably increasing for the same reason, having met many recent converts who all tell much the same story.
This is a terrible argument and totally against everything that drove me to Linux in the first place. If I don't like the way something works, I can and am encouraged to roll my own. Systemd is the culmination of this new mindset of "lets all just standardize so it's more presentable to the masses and business". Projects are becoming their own little ecosystems rather than a set of useful utilities that can be used somewhat independently. Gnome is kind of the extreme version of this, but everything seems to be heading in this direction, and now the core system functionality is becoming similar.
We are heading towards a Linux where doing your own thing is becoming less supported and discouraged, and this I find depressing. Sure we may actually have a year of the Linux desktop, but that desktop may as well be Windows.
This. IMHO, the whole point of Linux has always been the unlimited possibilities for customization
The problem in my opinion is a noticeable shift in this mentality over the last several years.
At some point, mass adoption became the big goal, and the spirit of flexibility and building a better mousetrap started to lose ground to standardization and making things more user friendly. Linux is basically morphing into an open source Windows clone bit by bit. This is probably good for humanity and all, but for many it's the opposite of what drew us to Linux in the first place.
In particular, systemd is the ultimate culmination of this new mindset. Systemd is a big, all encompassing beast where you can't easily swap out components and where many packages are gaining direct or indirect dependencies on it, making it hard to run a systemd free system. It may work better and be more user friendly, but it's the antithesis of the original Linux spirit.
As to using a distro that doesn't have systemd as a default, as a former Gentoo user I can tell you it's not that simple. Systemd is undoubtedly the most disruptive thing to hit gentoo in awhile. Simply specifying -systemd use flag isn't enough, I had to straight up blacklist packages and then uninstall/replace a bunch of packages with non-systemd requiring alternatives and fix the respective breakage. I don't use gnome, however a few gnome libraries got pulled in as dependencies of various things, and it was a huge headache to clean that shit out. Meanwhile slackware has straight up dropped gnome3 because it's too much of a pain to make it work without systemd. On Debian, gimp, a graphical editing tool, has an indirect systemd dependency!
I honestly think we'll see the kind of jobs requiring that being automated before we see better tools for those jobs. The days of people going around warehouses gathering stuff on a list are coming to an end.
I'm in a similar boat. I recently (a few months ago) migrated from Gentoo to FreeBSD.
The problem with systemd, and probably why so many people are running from it, is that it's not as simple as just not using systemd, or even not using a distro with systemd as a default.
A lot of packages are gaining direct or indirect dependencies on systemd, and it is becoming a huge pain to run a systemd free system. I found myself having to use portage's blacklist for the first time because simply specifying -systemd as a use flag wasn't enough. I also had to uninstall a bunch of packages and fix the associated breakage. I don't use gnome, but enough gnome packages ended up installed as dependencies of various things that it was a real headache. Slackware has straight up dropped gnome because it's too hard to have it without systemd. And of course you have systemd as an indirect requirement for gimp. Yes friends, when a graphics editing tool depends on a specific init system, it's time to get the hell out of there!
Systemd isn't the only factor, but it's certainly a major one and I think it's pushing a lot of people (like myself) who have kinda been disillusioned with Linux for some time over the edge. At some point mainstream adoption became the big goal, and this mindset where it was better to have a less flexible but easier to use system started destroying a lot of what drew us to Linux in the first place. Linux is basically morphing into a more open version of Windows for the sake of mass appeal, which may be great for humanity, but it's not why I got interested in Linux.
You can say you'll _probably_ be fine, but as said in my original post, even if you are completely in the clear, just dealing with LEA is going to be unpleasant, and for whatever cents I could get renting something that can be had fairly cheaply, it's just not worth that risk or effort involved in mitigating that risk.
1) Even encrypted, I'd still be pretty wary of having arbitrary files stores on my machines. Even if legally in the clear, just dealing with an LEA when someone uses your machine as a child porn host is going to be unpleasant.
2) Bandwidth is far more valuable to me than storage space. I've got tonnes of storage space, it's cheap. Bandwidth far less so.
I wouldn't trust either to control any device with actual destructive capability.
X10 doesn't need a path to the internet. With such a primitive protocol all it takes is a dying fridge or UPS to make devices randomly turn on and off (this is actual experience talking).
It's important to consider house insurance when doing this kind of hackery.
If your house catches fire and they dig a charred bundle of relays and a rasp pi rigged up to your mains you might have some explaining to do.
Sensors are one thing, but as soon as you go to actually control mains voltage, I think you are truly better off going for something more "mainstream".
I'd recommend looking at Insteon. It is the closest to what you are looking for off the top of my head.
If you want to avoid going through some service they own/control, you might need to roll your own management system, but as far as cheap devices you can control programatically I think they're probably what you want.
I'd like something that is easily reprogrammable without having to compile code, then reflash a device, etc.
Architecturally you probably want the devices to be dumb. They can report information or accept commands. Leave any logic to some kind of centralized controller.
Bonus note: avoid x10 (if it's still even around). It's dirt cheap but pretty much the shittiest system out there. I lost much sanity to it back in the day.
Personally I did the x10 thing back in the day using at first an ocelot controller and then eventually my own hacked together system using the ocelot as a modem. The shittiness of x10 aside, I grew bored with it fairly quickly. It's all fun and has a neat "house of the future" feel, but I didn't find a great deal of utility in it, and what utility there was is already covered by purpose specific devices (smart thermostats, etc).
I still remember trying to set up an older printer on my mothers laptop with windows 8. I spent what felt like a half hour clicking around trying to find the damn printer settings. Eventually I gave up and googled it. The instructions on _Microsoft's_ site used the built in search feature. Even they couldn't figure out the convoluted path to the "add new printer" page. This was my first (though unfortunately not last) experience with windows 8, and subsequent exposure has not gone any better.
They've sinced changed it, but you can still use archive.org to view the old version:
What made xhtml suck. As a non-web guy who just occasionally dabbles, xhtml seemed like a good idea. Unclosed tags in html always looked ugly, and as far as I can tell, that's really the most notable difference between xhtml and html.
- It's not a slideshow.. apparently some information is still conveyed in article form - It's not plastered in ads - There was no 'please wait while your page "loads" crap'. - It's providing information that isn't blatantly incorrect, common knowledge, or irrelevant
Language, maybe. The tool stack around that language though, I call BS.
Sure, a c++ guy can pick up java itself fairly quickly, but it takes time to come up to speed on the various widely used libraries and tools. General programming concepts transfer, the specific workings of something like EJB or OSGI don't.
Slashdot Mirror
* there .. :(
Horrible as it is, this is a battle of social acceptance. Google wants wearing a camera on your face to become socially acceptable. Those of us who don't want to see this become the norm want to make sure it doesn't become socially acceptable.
Unfortunately the best way to achieve this is by being hostile towards people wearing the damn thing. Just as walking up to some random couple at a bar, pulling out your cellphone, and pointing the camera at them would likely attract hostility as a non-socially acceptable behaviour, so must wearing google glass.
This doesn't have to be violence, but it does have to be enough to make:
- the individual unhappy (negative re-enforcement against the socially unacceptable behaviour)
- observers nervous about engaging in the behaviour themselves (hmm, everyones telling this guy to shove his google glass up his ass, and one guy is even offering to help, maybe I shouldn't buy one just yet!)
- businesses nervous about incidents, hopefully enough to ban the devices
There are subtle but important differences.
Yes surveillance is ubiquitous, but it's usually managed by business owners or government agencies, which means it's very unlikely to end up on youtube. A bar wouldn't survive very long if they made a habit of posting embarrassing moments from their surveillance tapes on the web.
People with cellphone cameras is also ubiquitous, but using one to record something is usually fairly obvious.
Covert surveillance is also now mostly trivial, but it's not socially acceptable and very few people actually do it, so the chances of being covertly recorded in a bar are pretty slim unless someone has reason to.
Google glass is in an all new category. To many, walking up to a table while wearing google glass is roughly equivalent to walking up to that table with your cellphone camera pointed at the people sitting their, and thus has gotten much the reaction you would expect.
It's a fairly commonly used term, and I wouldn't really call it a grudge so much as an acknowledgement of the disconnect in reality with those who assume an out of proportion interest in anything involving space.
Lots of people find space interesting and are generally supportive of ongoing research and efforts, but generally maintain a healthy balance of other interests.
Space nuttery is in my opinion defined by an unhealthy and unrealistic obsession with space. These are people who would (or at least have said they would) sell all their worldly possessions for the opportunity to spend some time in space, who would volunteer for a one way trip to mars. Basically a space nutter is someone who spends a fair bit of time flailing their arms and shouting "SPAAACCEEE" excitedly.
Gotta agree.
Business in general has become very risk adverse with a few exceptions (spacex and google being the big ones). Many of us feel constrained in this environment where everything we do has to mostly work or we won't get a second change or an opportunity to improve it. Everything has become about risk management and ROI and soul crushing metrics. It's very refreshing to see this kind of apparent "lets just do something we know probably won't work the first time, and keep doing it until it does" attitude.
Indeed. I'm not a space nutter, but this impresses the hell out of me. With a problem this hard, the fact that they are down to minor mistakes like this and not major fundamental issues is awesome.
I would assume for the same reason they are using an open system rather than a closed system: to save weight and complexity.
Also, I'm not a space nutter, but this stuff impresses the hell out of me. That looked damn close.
One keeps backups to protect themselves against such horrible, very rookie mistakes. They happen. Yes we can rage about how it shouldn't have happened, and yes someone at steam should get slapped, and yes "everyone should have backups" doesn't lessen the reality of what happened here, but having backups is still a good idea and is the difference between an inconvenience and sobbing in the corner when something like this happens.
At this point I'm far more inclined to jump ship to BSD (which to be honest feels very much like Linux did back before all this nonsense) and contribute my efforts to making it what I want. Neither is really what I want, but I feel at this point BSD is actually closer, and at least philosophically more aligned with what I'm looking for.
I'm not looking to exaggerate, but i do feel the BSD developer base is noticeably increasing for the same reason, having met many recent converts who all tell much the same story.
Or just run Ubuntu.. or maybe Windows?
This is a terrible argument and totally against everything that drove me to Linux in the first place. If I don't like the way something works, I can and am encouraged to roll my own. Systemd is the culmination of this new mindset of "lets all just standardize so it's more presentable to the masses and business". Projects are becoming their own little ecosystems rather than a set of useful utilities that can be used somewhat independently. Gnome is kind of the extreme version of this, but everything seems to be heading in this direction, and now the core system functionality is becoming similar.
We are heading towards a Linux where doing your own thing is becoming less supported and discouraged, and this I find depressing. Sure we may actually have a year of the Linux desktop, but that desktop may as well be Windows.
This. IMHO, the whole point of Linux has always been the unlimited possibilities for customization
The problem in my opinion is a noticeable shift in this mentality over the last several years.
At some point, mass adoption became the big goal, and the spirit of flexibility and building a better mousetrap started to lose ground to standardization and making things more user friendly. Linux is basically morphing into an open source Windows clone bit by bit. This is probably good for humanity and all, but for many it's the opposite of what drew us to Linux in the first place.
In particular, systemd is the ultimate culmination of this new mindset. Systemd is a big, all encompassing beast where you can't easily swap out components and where many packages are gaining direct or indirect dependencies on it, making it hard to run a systemd free system. It may work better and be more user friendly, but it's the antithesis of the original Linux spirit.
As to using a distro that doesn't have systemd as a default, as a former Gentoo user I can tell you it's not that simple. Systemd is undoubtedly the most disruptive thing to hit gentoo in awhile. Simply specifying -systemd use flag isn't enough, I had to straight up blacklist packages and then uninstall/replace a bunch of packages with non-systemd requiring alternatives and fix the respective breakage. I don't use gnome, however a few gnome libraries got pulled in as dependencies of various things, and it was a huge headache to clean that shit out. Meanwhile slackware has straight up dropped gnome3 because it's too much of a pain to make it work without systemd. On Debian, gimp, a graphical editing tool, has an indirect systemd dependency!
I honestly think we'll see the kind of jobs requiring that being automated before we see better tools for those jobs. The days of people going around warehouses gathering stuff on a list are coming to an end.
I'm in a similar boat. I recently (a few months ago) migrated from Gentoo to FreeBSD.
The problem with systemd, and probably why so many people are running from it, is that it's not as simple as just not using systemd, or even not using a distro with systemd as a default.
A lot of packages are gaining direct or indirect dependencies on systemd, and it is becoming a huge pain to run a systemd free system. I found myself having to use portage's blacklist for the first time because simply specifying -systemd as a use flag wasn't enough. I also had to uninstall a bunch of packages and fix the associated breakage. I don't use gnome, but enough gnome packages ended up installed as dependencies of various things that it was a real headache. Slackware has straight up dropped gnome because it's too hard to have it without systemd. And of course you have systemd as an indirect requirement for gimp. Yes friends, when a graphics editing tool depends on a specific init system, it's time to get the hell out of there!
Systemd isn't the only factor, but it's certainly a major one and I think it's pushing a lot of people (like myself) who have kinda been disillusioned with Linux for some time over the edge. At some point mainstream adoption became the big goal, and this mindset where it was better to have a less flexible but easier to use system started destroying a lot of what drew us to Linux in the first place. Linux is basically morphing into a more open version of Windows for the sake of mass appeal, which may be great for humanity, but it's not why I got interested in Linux.
Too low reward to risk and effort for me.
You can say you'll _probably_ be fine, but as said in my original post, even if you are completely in the clear, just dealing with LEA is going to be unpleasant, and for whatever cents I could get renting something that can be had fairly cheaply, it's just not worth that risk or effort involved in mitigating that risk.
Two biggest reasons:
1) Even encrypted, I'd still be pretty wary of having arbitrary files stores on my machines. Even if legally in the clear, just dealing with an LEA when someone uses your machine as a child porn host is going to be unpleasant.
2) Bandwidth is far more valuable to me than storage space. I've got tonnes of storage space, it's cheap. Bandwidth far less so.
I can just imagine what a rocket looks like on IR.
I'm going to assume either all white or all black, depending on polarity settings.
I wouldn't trust either to control any device with actual destructive capability.
X10 doesn't need a path to the internet. With such a primitive protocol all it takes is a dying fridge or UPS to make devices randomly turn on and off (this is actual experience talking).
It's important to consider house insurance when doing this kind of hackery.
If your house catches fire and they dig a charred bundle of relays and a rasp pi rigged up to your mains you might have some explaining to do.
Sensors are one thing, but as soon as you go to actually control mains voltage, I think you are truly better off going for something more "mainstream".
I'd recommend looking at Insteon. It is the closest to what you are looking for off the top of my head.
If you want to avoid going through some service they own/control, you might need to roll your own management system, but as far as cheap devices you can control programatically I think they're probably what you want.
I'd like something that is easily reprogrammable without having to compile code, then reflash a device, etc.
Architecturally you probably want the devices to be dumb. They can report information or accept commands. Leave any logic to some kind of centralized controller.
Bonus note: avoid x10 (if it's still even around). It's dirt cheap but pretty much the shittiest system out there. I lost much sanity to it back in the day.
Personally I did the x10 thing back in the day using at first an ocelot controller and then eventually my own hacked together system using the ocelot as a modem. The shittiness of x10 aside, I grew bored with it fairly quickly. It's all fun and has a neat "house of the future" feel, but I didn't find a great deal of utility in it, and what utility there was is already covered by purpose specific devices (smart thermostats, etc).
I still remember trying to set up an older printer on my mothers laptop with windows 8. I spent what felt like a half hour clicking around trying to find the damn printer settings. Eventually I gave up and googled it. The instructions on _Microsoft's_ site used the built in search feature. Even they couldn't figure out the convoluted path to the "add new printer" page. This was my first (though unfortunately not last) experience with windows 8, and subsequent exposure has not gone any better.
They've sinced changed it, but you can still use archive.org to view the old version:
Current: http://windows.microsoft.com/e...
Old: https://web.archive.org/web/20...
What made xhtml suck. As a non-web guy who just occasionally dabbles, xhtml seemed like a good idea. Unclosed tags in html always looked ugly, and as far as I can tell, that's really the most notable difference between xhtml and html.
Yup.
I'm quite confused because:
- It's not a slideshow.. apparently some information is still conveyed in article form
- It's not plastered in ads
- There was no 'please wait while your page "loads" crap'.
- It's providing information that isn't blatantly incorrect, common knowledge, or irrelevant
Not what I was expecting at all. This is actually a legitimate technical article.
I.. have to go re-evaluate my understanding of not just the current state of slashdot but of my life in general.
Language, maybe. The tool stack around that language though, I call BS.
Sure, a c++ guy can pick up java itself fairly quickly, but it takes time to come up to speed on the various widely used libraries and tools. General programming concepts transfer, the specific workings of something like EJB or OSGI don't.