Why stop half way? Push the clock another 5-6 hours forwards, go to work right after Midnight so you can get out around noon and have 4 hours of daylight left in Winter and 10 in Summer!
Well, it gets a bit unwieldy when you get closer to the international date line. Now, the "next day" is at midnight, with timezones being locked, if you're living close to the IDL your day would change somewhere in the afternoon, 2pm is Tuesday and 3pm is Wednesday... or something like that.
We could turn back the clock 6 hours instead of one. That way we go to work when it's still dark and it remains dark for most of the time we're at work, and then when we get out it's about (real) noon and even in Winter we have at least 3-4 hours of daylight left. And in Summer even a whooping 10!
If the holy grail is to have daylight when you get out of work, why don't you put your time change where your mouth is?
I travel a lot. And as such I can tell you it means little to me whether I go from Europe to the US or whether daylight saving strikes, equally I'm struggling to get back to a sensible rhythm.
Fortunately I was able to simply go and ignore DST altogether. I come to work an hour late during the Summer and also leave an hour late. Hello flexible work times, go suck on my nuts DST.
Time and again various IoT crapware has proven that it is insecure. The reason for this is simple. Companies making TVs have experience making TVs. And even if the corporation behind it (like with, say, Sony) should have some experience with computers and securing them (ok, I admit, Sony is a bad example...), that doesn't mean that they talk with each other. Or that securing computers applies equally to securing IoT devices. If anything, IoT has more in common with cellphones, and even here you can easily see (with Samsun, no less) that experience in one area does not translate to the other.
Embedded devices and developing them has fundamentally different rules than developing "real" computers or cellphones. Unlike with computers and cellphones, you're not only responsible for the hardware, you're developing the software, and you either even have to develop your own OS or at the very least tailor a Linux distribution to your needs. If you're lucky, you have someone in your team (or you buy one) that can actually tailor Linux.
Your chances of this person also being a security expert is slim to zero.
What you're dealing here is a very newly developed piece of software, a veritable "v1.0" (which, as anyone in IT knows is more akin to a "v0.9beta"). And you pit that against people who have literally decades of experience hacking machines on the internet who know all the old tricks and the new 0days. This is a pitched battle if there has ever been one.
And all the old tricks that every security conscious developer of internet facing computer software knows by now work again. Because the people developing the IoT-Software, i.e. people developing embedded software, have no experience with security issues. They developed for closed systems, with a focus on small code and optimal use of resources rather than sanity checking and input testing.
If you throw someone into a job where he suddenly should react to a threat he cannot even assess because he doesn't even KNOW what the threat is, the result is the IoT crap we have today.
You mean the gateway router that the ISP configured with a DHCP-Server that you do not have the password to so you could reconfigure it (provided you know how to, anyway)? That gateway router?
Works for me too, might make people think twice before buying crappy IoT junk if they suddenly get to pay for putting a bank out of business for a few days.
I'm thinking of something akin to the FCC Title 47 CFR Part 15. You know, the "this gadget can handle interference and doesn't broadcast interference" sticker you find on every piece of equipment sold in the US. By law, these things have to comply to this.
How about a "this gadget can handle malformed and malicious signals from the internet and does not broadcast any" sticker? And noncompliance gets you slapped with a fine from here to Albuquerque.
You can't do that? Then stop putting an internet connection on your fucking toaster and you're fine!
In theory, yes. In practice, does the system detect the change and brick the phone if it's not been done by a techpriest that has been blessed by the Adeptus Mechanicus?
Actually so far the results are pretty convincing. Mostly because our top echelons have no problem bumping people back down that don't perform, and people actually ask to be returned to their previous positions if they notice that their performance isn't up to speed.
This is mostly due to the way our payment system works, which is quite heavily tied to your performance. A poorly performing team manager can go home with considerably less money than a very well performing person working under him. So your incentive isn't to "climb the ladder" but to do your job well and perform at or above the required level.
Slashdot Mirror
Really?
I didn't know I wasn't people.
Why stop half way? Push the clock another 5-6 hours forwards, go to work right after Midnight so you can get out around noon and have 4 hours of daylight left in Winter and 10 in Summer!
Well, it gets a bit unwieldy when you get closer to the international date line. Now, the "next day" is at midnight, with timezones being locked, if you're living close to the IDL your day would change somewhere in the afternoon, 2pm is Tuesday and 3pm is Wednesday... or something like that.
We could turn back the clock 6 hours instead of one. That way we go to work when it's still dark and it remains dark for most of the time we're at work, and then when we get out it's about (real) noon and even in Winter we have at least 3-4 hours of daylight left. And in Summer even a whooping 10!
If the holy grail is to have daylight when you get out of work, why don't you put your time change where your mouth is?
I travel a lot. And as such I can tell you it means little to me whether I go from Europe to the US or whether daylight saving strikes, equally I'm struggling to get back to a sensible rhythm.
Fortunately I was able to simply go and ignore DST altogether. I come to work an hour late during the Summer and also leave an hour late. Hello flexible work times, go suck on my nuts DST.
Yes, but why do you feel entitled to make the rest of us get up early?
Write English!
Damn Czechs.
Meanwhile, people download the movies from pirate bay and not only save their money but also can watch their movies...
Time and again various IoT crapware has proven that it is insecure. The reason for this is simple. Companies making TVs have experience making TVs. And even if the corporation behind it (like with, say, Sony) should have some experience with computers and securing them (ok, I admit, Sony is a bad example...), that doesn't mean that they talk with each other. Or that securing computers applies equally to securing IoT devices. If anything, IoT has more in common with cellphones, and even here you can easily see (with Samsun, no less) that experience in one area does not translate to the other.
Embedded devices and developing them has fundamentally different rules than developing "real" computers or cellphones. Unlike with computers and cellphones, you're not only responsible for the hardware, you're developing the software, and you either even have to develop your own OS or at the very least tailor a Linux distribution to your needs. If you're lucky, you have someone in your team (or you buy one) that can actually tailor Linux.
Your chances of this person also being a security expert is slim to zero.
What you're dealing here is a very newly developed piece of software, a veritable "v1.0" (which, as anyone in IT knows is more akin to a "v0.9beta"). And you pit that against people who have literally decades of experience hacking machines on the internet who know all the old tricks and the new 0days. This is a pitched battle if there has ever been one.
And all the old tricks that every security conscious developer of internet facing computer software knows by now work again. Because the people developing the IoT-Software, i.e. people developing embedded software, have no experience with security issues. They developed for closed systems, with a focus on small code and optimal use of resources rather than sanity checking and input testing.
If you throw someone into a job where he suddenly should react to a threat he cannot even assess because he doesn't even KNOW what the threat is, the result is the IoT crap we have today.
For real?
Thanks for the warning, I almost bought a BluRay player.
An important part of our culture is lively debate. Unless you start making arguments that threaten our position that we cannot refute.
You mean the gateway router that the ISP configured with a DHCP-Server that you do not have the password to so you could reconfigure it (provided you know how to, anyway)? That gateway router?
Hackers don't.
Companies trying to do business do.
People potentially liable for operating faulty devices do.
Works for me too, might make people think twice before buying crappy IoT junk if they suddenly get to pay for putting a bank out of business for a few days.
Well, you may only put the sticker on if your system complies with its requirements.
You may only sell your gadget if it has the sticker.
See how it would help?
What happened, did they forget to turn off the light in the building and some bums moved into the abandoned site?
So we're talking about a piece of fashion or bling rather than a cellphone?
Ok, now it starts to make a lot more sense. I thought it's supposed to be a tool, but instead it seems only the one using it is one.
I'm thinking of something akin to the FCC Title 47 CFR Part 15. You know, the "this gadget can handle interference and doesn't broadcast interference" sticker you find on every piece of equipment sold in the US. By law, these things have to comply to this.
How about a "this gadget can handle malformed and malicious signals from the internet and does not broadcast any" sticker? And noncompliance gets you slapped with a fine from here to Albuquerque.
You can't do that? Then stop putting an internet connection on your fucking toaster and you're fine!
In theory, yes. In practice, does the system detect the change and brick the phone if it's not been done by a techpriest that has been blessed by the Adeptus Mechanicus?
Actually so far the results are pretty convincing. Mostly because our top echelons have no problem bumping people back down that don't perform, and people actually ask to be returned to their previous positions if they notice that their performance isn't up to speed.
This is mostly due to the way our payment system works, which is quite heavily tied to your performance. A poorly performing team manager can go home with considerably less money than a very well performing person working under him. So your incentive isn't to "climb the ladder" but to do your job well and perform at or above the required level.
And this, kids, is why outsourcing to India is delivering the quality it is.
I don't know about your friends, but with mine it would only earn you ridicule for being duped into buying an overpriced, overhyped cellphone.
With the fluff stripped, still impossible to repair sensibly and still a battery you can't replace.
The right to swing your Canadian fist ends at the US' nose.
They will. And still people won't upgrade.