Posts
Post has shared content
Public
Hard drive manufactures need to demonstrate that they're safe from malware attacks, not just claim to be.
Add a comment...
Post has shared content
Public
Lenovo's new laptops include a program "Superfish" that makes all HTTPS browsing unsafe: https://eff.org/r.ym9y The company's clueless and factually inaccurate response, “at no time were consumers vulnerable—we stand by this today” will further damage their brand.
Add a comment...
Post has shared content
Public
Your Mobile Phone Camera Doesn't Matter
All these rantings and ravings on the internet, saying that someone's favorite camera is the only good one, and all the rest are junk. I've decided that this is like a bunch of kids saying that their dad's car is faster than the next kid's dad's car. Silly. Even if the car could do 110 mph, it's unlikely the dad or the kid would ever be in the car going that fast.
Mobile phone cameras. It's frustrating to read all this stuff about people saying cameras are good, or not, or work well, or not - when all the time, these same people haven't got a clue about photography, or how to get the most out of their camera - let alone, basic photography stuff like "composition". Does it matter if the camera has a high-tech lens or a piece of plastic, when the photographer moves the phone around simply in trying to push whatever it is that takes the picture - and then blames the phone, when the image is blurry.
There was a discussion on G+ recently about the merits of several cameras - but when it came down to asking those participants to post photos they had taken themselves, with a phone camera, not one of them would do so. ...and when I went to their home pages on G+ to look at their photos, the images were pretty awful.
The link below will get a lot of people angry and upset, as everyone "knows" that if they spend more on a camera, they will get better photographs..... except that this is nonsense. Photographs are made by PEOPLE, not by cameras. The camera is just a tool, like a chisel. You don't create a beautiful wood carving by buying better chisels, you LEARN how YOU can do so.
It's a fun article. Read it anyway. If you really want to learn how to take better mobile phone photographs, first learn what makes a photograph better, and it's not the toys/tools we use - it's YOU.
All these rantings and ravings on the internet, saying that someone's favorite camera is the only good one, and all the rest are junk. I've decided that this is like a bunch of kids saying that their dad's car is faster than the next kid's dad's car. Silly. Even if the car could do 110 mph, it's unlikely the dad or the kid would ever be in the car going that fast.
Mobile phone cameras. It's frustrating to read all this stuff about people saying cameras are good, or not, or work well, or not - when all the time, these same people haven't got a clue about photography, or how to get the most out of their camera - let alone, basic photography stuff like "composition". Does it matter if the camera has a high-tech lens or a piece of plastic, when the photographer moves the phone around simply in trying to push whatever it is that takes the picture - and then blames the phone, when the image is blurry.
There was a discussion on G+ recently about the merits of several cameras - but when it came down to asking those participants to post photos they had taken themselves, with a phone camera, not one of them would do so. ...and when I went to their home pages on G+ to look at their photos, the images were pretty awful.
The link below will get a lot of people angry and upset, as everyone "knows" that if they spend more on a camera, they will get better photographs..... except that this is nonsense. Photographs are made by PEOPLE, not by cameras. The camera is just a tool, like a chisel. You don't create a beautiful wood carving by buying better chisels, you LEARN how YOU can do so.
It's a fun article. Read it anyway. If you really want to learn how to take better mobile phone photographs, first learn what makes a photograph better, and it's not the toys/tools we use - it's YOU.
Add a comment...
Post has shared content
Public
This is so incredibly important. This is why Linus Torvalds is no longer my hero, since seeing him in person at DebConf '14. He is extremely good at the technical stuff, but his attitude is unacceptable.
Much of the Open Source community tries to advertise the community as one happy place to the outside. Where contributions are valued only by their technical quality, and everybody meets at conferences for beers.
Well, it is not like that. It's quite a sick place to be in.
I don't usually talk about this too much, and hence I figure that people are really not aware of this, but yes, the Open Source community is full of assholes, and I probably more than most others am one of their most favourite targets. I get hate mail for hacking on Open Source. People have started multiple "petitions" on petition web sites, asking me to stop working (google for it). Recently, people started collecting Bitcoins to hire a hitman for me (this really happened!). Just the other day, some idiot posted a "song" on youtube, a creepy work, filled with expletives about me and suggestions of violence. People post websites about boycotting my projects, containing pretty personal attacks. On IRC, people /msg me sometimes, with nasty messages, and references to artwork in 4chan style. And there's more. A lot more.
I am used to rough discussions on mailing lists, and yes, when I was younger I did not always stay technical in flamewars, but nowadays I am pretty good at that, I am sometimes articulate, but never personal. I have a thick skin (and so do most of the others involved in systemd, apparently), and I figure that plays a major role why we managed to bring systemd to success, despite all the pressure in the opposite direction. But from time to time, I just have to stand back and say "Wow, what an awful community Linux has!".
The Internet is full of deranged people, no doubt, so one might just discount all of this on the grounds that the Open Source community isn't any different than any other community on the Internet or even offline. But I don't think so. I am pretty sure there are certain things that foster bad behaviour. On one hand there are certain communities where it appears to be a lot more accepted to vent hate, communities that attract a certain kind of people (Hey, Gentoo!) more than others do. (Yes, the folks who post the stuff they do usually pretty clearly state from wich community they come).
But more importantly, I'd actually put some blame on a certain circle of folks that play a major role in kernel development, and first and foremost Linus Torvalds himself. By many he is a considered a role model, but he is quite a bad one. If he posts words like "[specific folks] ...should be retroactively aborted. Who the f*ck does idiotic things like that? How did they not die as babies, considering that they were likely too stupid to find a tit to suck on?" (google for it), than that's certainly bad. But what I find particularly appalling is the fact that he regularly defends this, and advertises this as an efficient way to run a community. (But it is not just Linus, it's a certain group of people around him who use the exact same style, some of which semi-publically even phantasize about the best ways to, ... well, kill me).
But no, it's not an efficient way to run a community. If Linux had success, then that certainly happened despite, not because of this behaviour. I am pretty sure the damage being done by this is quite obvious, it not only sours the tone in the Linux community, it is also teaches new contributors to adopt the same style, but that only if it doesn't scare them away in the first place.
In other words: A fish rots from the head down.
I don't mind using strong language, I don't mind the use of words such as "fuck", I use the word all the time too, it's really not about that. I must simply say that I wished it would stay at that, because what actually is happening is so much worse, and and so much more hateful.
If you are a newcomer to Linux, either grow a really thick skin. Or run away, it's not a friendly place to be in. It is sad that it is that way, but it certainly is.
The Linux community is dominated by western, white, straight, males in their 30s and 40s these days. I perfectly fit in that pattern, and the rubbish they pour over me is awful. I can only imagine that it is much worse for members of minorities, or people from different cultural backgrounds, in particular ones where losing face is a major issue.
You know, I can deal with all this shit, and I guess in a way with the energy we are pushing the changes we propose with we are calling for opposition, so this post is really not intended to be a call for sympathy. The main point I want to make with this is to correct a few things about our communities, and how their are percieved. Open Source isn't a kindergarten. Open Source is awful in many ways, and people should be aware of this.
Not everybody in the Linux community is like this, the vast majority isn't. Not even all our different communities really have a problem with this at all. But many do, and the most prominent one, the Linux community as a whole certainly has.
I am not the one to fix any of this, I cannot tell you how one could do it. And quite frankly, I really don't want to be involved in fixing this. I am a technical guy, I want to do technical things.
My personal conclusion out of all this is mostly just that I don't want to have much to do with the worst offenders, and the communities they run. My involvement with the kernel community ended pretty much before it even started, I never post on LKML, and haven't done in years. Also, in our own project we are policying posts. We regularly put a few folks on moderation on the mailing list, and we will continue to do so. Currently, the systemd community is fantastic, and I really hope we can keep it that way.
And that's all about this topic from me. I have no intentions to ever talk about this again on a public forum.
Well, it is not like that. It's quite a sick place to be in.
I don't usually talk about this too much, and hence I figure that people are really not aware of this, but yes, the Open Source community is full of assholes, and I probably more than most others am one of their most favourite targets. I get hate mail for hacking on Open Source. People have started multiple "petitions" on petition web sites, asking me to stop working (google for it). Recently, people started collecting Bitcoins to hire a hitman for me (this really happened!). Just the other day, some idiot posted a "song" on youtube, a creepy work, filled with expletives about me and suggestions of violence. People post websites about boycotting my projects, containing pretty personal attacks. On IRC, people /msg me sometimes, with nasty messages, and references to artwork in 4chan style. And there's more. A lot more.
I am used to rough discussions on mailing lists, and yes, when I was younger I did not always stay technical in flamewars, but nowadays I am pretty good at that, I am sometimes articulate, but never personal. I have a thick skin (and so do most of the others involved in systemd, apparently), and I figure that plays a major role why we managed to bring systemd to success, despite all the pressure in the opposite direction. But from time to time, I just have to stand back and say "Wow, what an awful community Linux has!".
The Internet is full of deranged people, no doubt, so one might just discount all of this on the grounds that the Open Source community isn't any different than any other community on the Internet or even offline. But I don't think so. I am pretty sure there are certain things that foster bad behaviour. On one hand there are certain communities where it appears to be a lot more accepted to vent hate, communities that attract a certain kind of people (Hey, Gentoo!) more than others do. (Yes, the folks who post the stuff they do usually pretty clearly state from wich community they come).
But more importantly, I'd actually put some blame on a certain circle of folks that play a major role in kernel development, and first and foremost Linus Torvalds himself. By many he is a considered a role model, but he is quite a bad one. If he posts words like "[specific folks] ...should be retroactively aborted. Who the f*ck does idiotic things like that? How did they not die as babies, considering that they were likely too stupid to find a tit to suck on?" (google for it), than that's certainly bad. But what I find particularly appalling is the fact that he regularly defends this, and advertises this as an efficient way to run a community. (But it is not just Linus, it's a certain group of people around him who use the exact same style, some of which semi-publically even phantasize about the best ways to, ... well, kill me).
But no, it's not an efficient way to run a community. If Linux had success, then that certainly happened despite, not because of this behaviour. I am pretty sure the damage being done by this is quite obvious, it not only sours the tone in the Linux community, it is also teaches new contributors to adopt the same style, but that only if it doesn't scare them away in the first place.
In other words: A fish rots from the head down.
I don't mind using strong language, I don't mind the use of words such as "fuck", I use the word all the time too, it's really not about that. I must simply say that I wished it would stay at that, because what actually is happening is so much worse, and and so much more hateful.
If you are a newcomer to Linux, either grow a really thick skin. Or run away, it's not a friendly place to be in. It is sad that it is that way, but it certainly is.
The Linux community is dominated by western, white, straight, males in their 30s and 40s these days. I perfectly fit in that pattern, and the rubbish they pour over me is awful. I can only imagine that it is much worse for members of minorities, or people from different cultural backgrounds, in particular ones where losing face is a major issue.
You know, I can deal with all this shit, and I guess in a way with the energy we are pushing the changes we propose with we are calling for opposition, so this post is really not intended to be a call for sympathy. The main point I want to make with this is to correct a few things about our communities, and how their are percieved. Open Source isn't a kindergarten. Open Source is awful in many ways, and people should be aware of this.
Not everybody in the Linux community is like this, the vast majority isn't. Not even all our different communities really have a problem with this at all. But many do, and the most prominent one, the Linux community as a whole certainly has.
I am not the one to fix any of this, I cannot tell you how one could do it. And quite frankly, I really don't want to be involved in fixing this. I am a technical guy, I want to do technical things.
My personal conclusion out of all this is mostly just that I don't want to have much to do with the worst offenders, and the communities they run. My involvement with the kernel community ended pretty much before it even started, I never post on LKML, and haven't done in years. Also, in our own project we are policying posts. We regularly put a few folks on moderation on the mailing list, and we will continue to do so. Currently, the systemd community is fantastic, and I really hope we can keep it that way.
And that's all about this topic from me. I have no intentions to ever talk about this again on a public forum.
Add a comment...
Post has attachment
Public
Reset the Net
This won't come as a shock to anyone who knows me, but I'm in full support of Fight For The Future's Reset the Net campaign. Surveillance is censorship. We need real surveillance reform, but since Congress has watered down the one bill that would actually t...
This won't come as a shock to anyone who knows me, but I'm in full support of Fight For The Future's Reset the Net campaign. Surveillance is censorship. We need real surveillance reform, but since Congress has watered down the one bill that would actually t...
Add a comment...
Post has attachment
Public
My standard configuration
I use Arch GNU/Linux . I know how to use it very well, and I love it dearly. One of the amazing things about Arch is that you get to build your system from the ground up (but without waiting for things to compile). Therefore, the system that I run is exactl...
I use Arch GNU/Linux . I know how to use it very well, and I love it dearly. One of the amazing things about Arch is that you get to build your system from the ground up (but without waiting for things to compile). Therefore, the system that I run is exactl...
Add a comment...
Post has attachment
Public
I [redacted] hate Apple
If you know me in real life, you know that it's no secret that I am not a fan of Apple's mobile products. They are disgusting: They won't let you install apps not from the App Store without jailbreaking the device, and the criteria for getting apps into the...
If you know me in real life, you know that it's no secret that I am not a fan of Apple's mobile products. They are disgusting: They won't let you install apps not from the App Store without jailbreaking the device, and the criteria for getting apps into the...
Add a comment...
Post has attachment
Public
I [redacted] hate Apple
If you know me in real life, you know that it's no secret that I am not a fan of Apple's mobile products. They are disgusting: They won't let you install apps not from the App Store without jailbreaking the device, and the criteria for getting apps into the...
If you know me in real life, you know that it's no secret that I am not a fan of Apple's mobile products. They are disgusting: They won't let you install apps not from the App Store without jailbreaking the device, and the criteria for getting apps into the...
Add a comment...
Post has shared content
Public
Originally shared by ****
MH370 A different point of view. Pulau Langkawi 13,000 runway.
A lot of speculation about MH370. Terrorism, hijack, meteors. I cannot believe the analysis on CNN - almost disturbing. I tend to look for a more simple explanation of this event.
Loaded 777 departs midnight from Kuala to Beijing. Hot night. Heavy aircraft. About an hour out across the gulf towards Vietnam the plane goes dark meaning the transponder goes off and secondary radar tracking goes off.
Two days later we hear of reports that Malaysian military radar (which is a primary radar meaning the plane is being tracked by reflection rather than by transponder interrogation response) has tracked the plane on a southwesterly course back across the Malay Peninsula into the straits of Malacca.
When I heard this I immediately brought up Google Earth and I searched for airports in proximity to the track towards southwest.
The left turn is the key here. This was a very experienced senior Captain with 18,000 hours. Maybe some of the younger pilots interviewed on CNN didn't pick up on this left turn. We old pilots were always drilled to always know the closest airport of safe harbor while in cruise. Airports behind us, airports abeam us and airports ahead of us. Always in our head. Always. Because if something happens you don't want to be thinking what are you going to do - you already know what you are going to do. Instinctively when I saw that left turn with a direct heading I knew he was heading for an airport. Actually he was taking a direct route to Palau Langkawi a 13,000 foot strip with an approach over water at night with no obstacles. He did not turn back to Kuala Lampur because he knew he had 8,000 foot ridges to cross. He knew the terrain was friendlier towards Langkawi and also a shorter distance.
Take a look on Google Earth at this airport. This pilot did all the right things. He was confronted by some major event onboard that made him make that immediate turn back to the closest safe airport.
For me the loss of transponders and communications makes perfect sense if a fire. There was most likely a fire or electrical fire. In the case of fire the first response if to pull all the main busses and restore circuits one by one until you have isolated the bad one.
If they pulled the busses the plane indeed would go silent. It was probably a serious event and they simply were occupied with controlling the plane and trying to fight the fire. Aviate, Navigate and lastly communicate. There are two types of fires. Electrical might not be as fast and furious and there might or might not be incapacitating smoke. However there is the possibility given the timeline that perhaps there was an overheat on one of the front landing gear tires and it blew on takeoff and started slowly burning. Yes this happens with underinflated tires. Remember heavy plane, hot night, sea level, long run takeoff. There was a well known accident in Nigeria of a DC8 that had a landing gear fire on takeoff. A tire fire once going would produce horrific incapacitating smoke. Yes, pilots have access to oxygen masks but this is a no no with fire. Most have access to a smoke hood with a filter but this will only last for a few minutes depending on the smoke level. (I used to carry one of my own in a flight bag and I still carry one in my briefcase today when I fly).
What I think happened is that they were overcome by smoke and the plane just continued on the heading probably on George (autopilot) until either fuel exhaustion or fire destroyed the control surfaces and it crashed. I said four days ago you will find it along that route - looking elsewhere was pointless.
This pilot, as I say, was a hero struggling with an impossible situation trying to get that plane to Langkawi. No doubt in my mind. That's the reason for the turn and direct route. A hijack would not have made that deliberate left turn with a direct heading for Langkawi. It would probably have weaved around a bit until the hijackers decided on where they were taking it.
Surprisingly none of the reporters , officials, other pilots interviewed have looked at this from the pilot's viewpoint. If something went wrong where would he go? Thanks to Google earth I spotted Langkawi in about 30 seconds, zoomed in and saw how long the runway was and I just instinctively knew this pilot knew this airport. He had probably flown there many times. I guess we will eventually find out when you help me spread this theory on the net and some reporters finally take a look on Google earth and put 2 and 2 together. Also a look at the age and number of cycles on those nose tires might give us a good clue too.
Fire in an aircraft demands one thing - you get the machine on the ground as soon as possible. There are two well remembered experiences in my memory. The AirCanada DC9 which landed I believe in Columbus Ohio in the eighties. That pilot delayed descent and bypassed several airports. He didn't instinctively know the closest airports. He got it on the ground eventually but lost 30 odd souls. In the 1998 crash of Swissair DC-10 off Nova Scotia was another example of heroic pilots. They were 15 minutes out of Halifax but the fire simply overcame them and they had to ditch in the ocean. Just ran out of time. That fire incidentally started when the aircraft was about an hour out of Kennedy. Guess what the transponders and communications were shut off as they pulled the busses.
Get on Google Earth and type in Pulau Langkawi and then look at it in relation to the radar track heading. 2+2=4 That for me is the simple explanation why it turned and headed in that direction.
Smart pilot. Just didn't have the time.
A lot of speculation about MH370. Terrorism, hijack, meteors. I cannot believe the analysis on CNN - almost disturbing. I tend to look for a more simple explanation of this event.
Loaded 777 departs midnight from Kuala to Beijing. Hot night. Heavy aircraft. About an hour out across the gulf towards Vietnam the plane goes dark meaning the transponder goes off and secondary radar tracking goes off.
Two days later we hear of reports that Malaysian military radar (which is a primary radar meaning the plane is being tracked by reflection rather than by transponder interrogation response) has tracked the plane on a southwesterly course back across the Malay Peninsula into the straits of Malacca.
When I heard this I immediately brought up Google Earth and I searched for airports in proximity to the track towards southwest.
The left turn is the key here. This was a very experienced senior Captain with 18,000 hours. Maybe some of the younger pilots interviewed on CNN didn't pick up on this left turn. We old pilots were always drilled to always know the closest airport of safe harbor while in cruise. Airports behind us, airports abeam us and airports ahead of us. Always in our head. Always. Because if something happens you don't want to be thinking what are you going to do - you already know what you are going to do. Instinctively when I saw that left turn with a direct heading I knew he was heading for an airport. Actually he was taking a direct route to Palau Langkawi a 13,000 foot strip with an approach over water at night with no obstacles. He did not turn back to Kuala Lampur because he knew he had 8,000 foot ridges to cross. He knew the terrain was friendlier towards Langkawi and also a shorter distance.
Take a look on Google Earth at this airport. This pilot did all the right things. He was confronted by some major event onboard that made him make that immediate turn back to the closest safe airport.
For me the loss of transponders and communications makes perfect sense if a fire. There was most likely a fire or electrical fire. In the case of fire the first response if to pull all the main busses and restore circuits one by one until you have isolated the bad one.
If they pulled the busses the plane indeed would go silent. It was probably a serious event and they simply were occupied with controlling the plane and trying to fight the fire. Aviate, Navigate and lastly communicate. There are two types of fires. Electrical might not be as fast and furious and there might or might not be incapacitating smoke. However there is the possibility given the timeline that perhaps there was an overheat on one of the front landing gear tires and it blew on takeoff and started slowly burning. Yes this happens with underinflated tires. Remember heavy plane, hot night, sea level, long run takeoff. There was a well known accident in Nigeria of a DC8 that had a landing gear fire on takeoff. A tire fire once going would produce horrific incapacitating smoke. Yes, pilots have access to oxygen masks but this is a no no with fire. Most have access to a smoke hood with a filter but this will only last for a few minutes depending on the smoke level. (I used to carry one of my own in a flight bag and I still carry one in my briefcase today when I fly).
What I think happened is that they were overcome by smoke and the plane just continued on the heading probably on George (autopilot) until either fuel exhaustion or fire destroyed the control surfaces and it crashed. I said four days ago you will find it along that route - looking elsewhere was pointless.
This pilot, as I say, was a hero struggling with an impossible situation trying to get that plane to Langkawi. No doubt in my mind. That's the reason for the turn and direct route. A hijack would not have made that deliberate left turn with a direct heading for Langkawi. It would probably have weaved around a bit until the hijackers decided on where they were taking it.
Surprisingly none of the reporters , officials, other pilots interviewed have looked at this from the pilot's viewpoint. If something went wrong where would he go? Thanks to Google earth I spotted Langkawi in about 30 seconds, zoomed in and saw how long the runway was and I just instinctively knew this pilot knew this airport. He had probably flown there many times. I guess we will eventually find out when you help me spread this theory on the net and some reporters finally take a look on Google earth and put 2 and 2 together. Also a look at the age and number of cycles on those nose tires might give us a good clue too.
Fire in an aircraft demands one thing - you get the machine on the ground as soon as possible. There are two well remembered experiences in my memory. The AirCanada DC9 which landed I believe in Columbus Ohio in the eighties. That pilot delayed descent and bypassed several airports. He didn't instinctively know the closest airports. He got it on the ground eventually but lost 30 odd souls. In the 1998 crash of Swissair DC-10 off Nova Scotia was another example of heroic pilots. They were 15 minutes out of Halifax but the fire simply overcame them and they had to ditch in the ocean. Just ran out of time. That fire incidentally started when the aircraft was about an hour out of Kennedy. Guess what the transponders and communications were shut off as they pulled the busses.
Get on Google Earth and type in Pulau Langkawi and then look at it in relation to the radar track heading. 2+2=4 That for me is the simple explanation why it turned and headed in that direction.
Smart pilot. Just didn't have the time.
Add a comment...
Post has attachment
Public
Plans for the new steevie (and a short personal update)
steevie Replacement & encryption So a week or so ago I ordered a super nice hard drive - a 120 GB Intel SSD (note: that links to the 80 GB version but I did get the 120 GB version). Unfortunately, there's been snail-mail problems and the drive hasn't come y...
steevie Replacement & encryption So a week or so ago I ordered a super nice hard drive - a 120 GB Intel SSD (note: that links to the 80 GB version but I did get the 120 GB version). Unfortunately, there's been snail-mail problems and the drive hasn't come y...
Add a comment...
Wait while more posts are being loaded

