Maybe just find a source of real light bulbs. I'm in the US and get incandescents all the time, no problem, there must be some source available of them in your area.
Since fluorescents and LED cannot be dimmed, and do not work properly with motion-activated lights like I use throughout. The CFLs actually take too long to turn on -- and fluorescents suck a lot of electricity when first powered up, making them horribly inefficient for these applications.
The CFLs are supposed to last longer, justifying the price or something like that.
In my experience, not the case, whenever I tried one somewhere, it wound up burning out within a few weeks, and so did the replacement, whereas incandescent in the same place lasts months. I suppose I could have just gotten two bad ones in a row, but i'm not chancing that again.
Admittedly inefficient at 1500 Watts, however, lighting your house with homemade bulbs could get expensive and have certain dangers, and other aesthetic problems, but may be worth it.
Still, you could probably obtain a softer, less harsh/stressful color temperature than that fluorescent mercury-filled crap, with enough effort.
Without stealing of ideas, MacOS and Windows would not exist. The concept of mouse, windows, and graphical menus belong to PARC/Xerox.
Who never got their opportunity to release a product using the technology, because Apple stole it right out from under them, before it was even published, making Apple 1st to market on technology they stole.
Far more damaging than ripping on a work, when the designer's product is already out, known to the market, and available for purchase.
MetaLab didn't need to make a big deal about this.
they could of reported it to Mozilla if it were concerned. It's obvious MetaLab posted the blog entry to get attention.
Basically advertising: even negative attention is good for them.
I would wager hardly anyone on Slashdot even knew MetaLab's name prior to this article.
Now that this article has hit news, everyone who read it knows they could go to MetaLab to get a quote for UI design....
Obviously this whole incident will do a lot of good for MetaLab, in the way of free advertising, they will probably profit handsomely from this fiasco.
While Mozilla have used their imagery, and there is obvious similarity, they haven't included it in a user interface, they have combined the work with work of their own to express some ideas about how their final interface could look like.
I would think it's unlikely that their final design would look at all like the mockup.
First mockup very rarely reflects what the final product will be.
Basically, while, the imagery Mozilla posted that had some renditions including some MetaLab design elements, it was of zero commercial value, used in the creative process.
And although a derivative work, probably fair use, providing they had only used it in the mockup.
Ok.. but who the heck has existing LED room lights?
Most rooms are lit by incandescent light bulbs.
Sometimes work areas are lit by fluorescents or halogen floodlights, where the extra brightness is required, and the poor aesthetics are not an issue.
But noone's dumb enough to light rooms with LEDs.
LEDs are OK for flashlights, indicator lights, and directed light applications (spotlights), and are not the least bit suitable for lighting an entire room, and they are way too expensive anyways (over 20x as expensive per bulb as an incandescent), so use of LED room lights is simply infeasible and doesn't make any sense.
Businesses that care have IT departments or consultants hired who know how to secure their own wireless infrastructure.
The primary risk is from rogue access points setup by some employee but not approved or known about by IT.
Or employees leaking/accidentally exposing what amount to their VPN credentials.
In either case, switching to a wireless technology stopped by the walls doesn't necessarily mitigate the later two.
An employee bringing a rogue AP, might use an older or different technology such as 802.11a, instead of the new-fangled LED wireless, then it's back to square one, same security issue.
They could pick a light frequency and intensity that is attentuated by the window glass, to make it hard/impossible for someone to use a window for that.
Or in the case of a business, they could use a security film targeted at the wireless frequency range.
It's harder to install, but no more encryption to worry about.
e.g. The need for "secure wireless" will basically go away, and all be about physical install complexity.
This will make it accessible to more people, at a base level, in theory.
People won't be able to install themselves as easily though, since to get whole-house wireless, some special arrangements will possibly be needed, beyond skills of average do-it-yourselfer
So it's more expensive... but people might adopt it, since they no longer need confusing WEP or WPA technologies (that keep getting broken/obsoleted), and can simply use plain old open wireless again.
That's what repeaters/bridges are for.
You just need to convert the LED wireless to another technology,
or extend the signal using repeaters.
An example of a repeater apparatus would be: you punch a hole in two opposite sides of a wall. Mount and power two appliances on the wall on each side.
When the appliance receives a signal, it repeats it into the wall.
Its neighbor appliance which just needs to receive the LED light repeated into the wall, receives that, and repeats it into the room it is mounted in.
Come to think of it... if you punch a hole in the ceiling instead, and mount the appliance up there, so it projects LED light into the attic, it may be able to receive the LED light projections from all the other 'repeaters' that were mounted to the ceiling.
For instance, by capturing reflections off of common structure in the crawlspace,
where all the LEDs throughout the building can project to (without wall separation)
Also, it can look as innocuous as a smoke detector, or simply be built into the light fixture somehow.
The policy on how to handle employees being terminated should be accompanied with a policy about changing of passwords and access codes,
requiring thorough documentation of changes (including codes changed and the new code), AND review of all changes by an immediate peer.
To use an obvious analogy, if a bank teller gets a two week notice I don't think we expect the bank to not let them handle any cash for those two weeks
Bank tellers and all their actions can easily be watched for obvious attempts to commit a crime, and it should be immediately obvious to the manager if the teller attempts to steal anything.
If they have the combination to the vault, access cards to a secure area, building keys, or any alarm combination, it will probably be changed just after they get the news, and be up to security staff to grant access when needed.
necessarily. If I still trust the person but can't afford to keep them due to a bad economy for example
Ah. But how well do you really know them, and how sure are you that you can trust them fully in such an extreme situation?
If they do something you don't like that hurts you (but isn't technically illegal)... after that point, what are you going to do, fire them?
Unfortunately, sometimes they need to train someone else to do the job and have the same problem.
You should have thought about that long before deciding to fire them.
They know they are going, and they have little incentive to properly train someone else, which for any really complicated job takes more than 2 weeks to do anyways.
Why should they want to do that for you, really?
Most likely you'll instead get some sort of half-hearted training from them, either because they intentionally hold back, or because they're so disturbed by the news, that they won't do a good job training someone, even if they want to.
Maybe... DDos is no excuse, though.. DDoS are to be completely expected by such things and 'down due to DDoS' is unacceptable. Microsoft has proven that a well-designed product activation infrastructure can be built to stand strong even in the face of DDoS.
Admittendly they weren't so dumb as to require continuous access to MS servers (or get forced blue screen)
But same deal, really
Down to DDoS would still reflect terrible design, ignorance, or plain negligence on Ubisoft's part.
Huh? Copyright is what prevents you from making it available or getting ahold of it in the first place.
Copyright enforcers find unauthorized or unapproved sources and shut them down, so you can't get the material
If it became public domain, there's little doubt someone would have an archive and be able to make that available, esp. if someone, some time would be willing to pay.
There are plenty of logical reasons for non-negros and negros to be afforded the same rights and protections as all individuals.
There is no logical basis for distinguishing there. There is a logical basis for treating non-sentient non-self-aware animal species differently however: their usefulness as a food source, that they are weak and easily eaten, humans evolved to eat them. Playing with your food before eating is typical, a creative outlet, and convenient way of getting exercise and relieving stress (give a cat a mouse some time, and see how much fun the cat has).
it is "human" to do so.
Some humans abuse, eat, or abuse/do other things to animals we subjectively assess to be cruel/mean, so obviously it is human to do so.
Actually intelligence doesn't matter... it's "appearance of intelligence" that matters, because from the very beginning, the basis for penalizing animal abuse is an emotional/moral one, not a logical one.
Some people who see an animal experience pain tend to identify with, "empathize" with it, and commit anthropomorphic fallacies. Such is human nature.
Ok, great reason to create a registry of Bedwetters also, then (however).
Whenever you move into a new house, you will be required to inform all your new neighbors that you were a persistent bedwetter past the age of 5.
Since all past bedwetters are dangerous and cannot be trusted. It is a behavior that once practiced may never leave the person. They may suppress it for the rest of their lives, but underneath the potential is there especially given a one in a million encounter.
From Wikipedia: "The triad links animal cruelty, obsession with fire setting, and persistent bedwetting past the age of five to violent behaviors; particularly homicidal behavior"
Slashdot Mirror
So they'll add 100/120Hz modes? Or maybe the 100hz frequency is high enough for the camera to not pick up the flicker
Maybe just find a source of real light bulbs. I'm in the US and get incandescents all the time, no problem, there must be some source available of them in your area.
Since fluorescents and LED cannot be dimmed, and do not work properly with motion-activated lights like I use throughout. The CFLs actually take too long to turn on -- and fluorescents suck a lot of electricity when first powered up, making them horribly inefficient for these applications.
The CFLs are supposed to last longer, justifying the price or something like that. In my experience, not the case, whenever I tried one somewhere, it wound up burning out within a few weeks, and so did the replacement, whereas incandescent in the same place lasts months. I suppose I could have just gotten two bad ones in a row, but i'm not chancing that again.
Or... time to make your own then?
Admittedly inefficient at 1500 Watts, however, lighting your house with homemade bulbs could get expensive and have certain dangers, and other aesthetic problems, but may be worth it.
Still, you could probably obtain a softer, less harsh/stressful color temperature than that fluorescent mercury-filled crap, with enough effort.
Without stealing of ideas, MacOS and Windows would not exist. The concept of mouse, windows, and graphical menus belong to PARC/Xerox.
Who never got their opportunity to release a product using the technology, because Apple stole it right out from under them, before it was even published, making Apple 1st to market on technology they stole.
Far more damaging than ripping on a work, when the designer's product is already out, known to the market, and available for purchase.
MetaLab didn't need to make a big deal about this. they could of reported it to Mozilla if it were concerned. It's obvious MetaLab posted the blog entry to get attention. Basically advertising: even negative attention is good for them. I would wager hardly anyone on Slashdot even knew MetaLab's name prior to this article. Now that this article has hit news, everyone who read it knows they could go to MetaLab to get a quote for UI design....
Obviously this whole incident will do a lot of good for MetaLab, in the way of free advertising, they will probably profit handsomely from this fiasco.
While Mozilla have used their imagery, and there is obvious similarity, they haven't included it in a user interface, they have combined the work with work of their own to express some ideas about how their final interface could look like.
I would think it's unlikely that their final design would look at all like the mockup. First mockup very rarely reflects what the final product will be.
Basically, while, the imagery Mozilla posted that had some renditions including some MetaLab design elements, it was of zero commercial value, used in the creative process.
And although a derivative work, probably fair use, providing they had only used it in the mockup.
Ok.. but who the heck has existing LED room lights? Most rooms are lit by incandescent light bulbs.
Sometimes work areas are lit by fluorescents or halogen floodlights, where the extra brightness is required, and the poor aesthetics are not an issue.
But noone's dumb enough to light rooms with LEDs. LEDs are OK for flashlights, indicator lights, and directed light applications (spotlights), and are not the least bit suitable for lighting an entire room, and they are way too expensive anyways (over 20x as expensive per bulb as an incandescent), so use of LED room lights is simply infeasible and doesn't make any sense.
Ok... you won't notice it.. but what will your video Camera do? :)
They commonly detect refresh flicker from computer monitors.
Except now it's new and improved UvDA and VLDA . ultra-violet and visible light data association :)
Businesses that care have IT departments or consultants hired who know how to secure their own wireless infrastructure.
The primary risk is from rogue access points setup by some employee but not approved or known about by IT.
Or employees leaking/accidentally exposing what amount to their VPN credentials.
In either case, switching to a wireless technology stopped by the walls doesn't necessarily mitigate the later two.
An employee bringing a rogue AP, might use an older or different technology such as 802.11a, instead of the new-fangled LED wireless, then it's back to square one, same security issue.
They could pick a light frequency and intensity that is attentuated by the window glass, to make it hard/impossible for someone to use a window for that.
Or in the case of a business, they could use a security film targeted at the wireless frequency range.
Agree. Nobodie on slashdot knows how to run spell cheek anymore. Every conversation is full of speling erors and lots of Big Mistaks. :-)
It's harder to install, but no more encryption to worry about. e.g. The need for "secure wireless" will basically go away, and all be about physical install complexity.
This will make it accessible to more people, at a base level, in theory. People won't be able to install themselves as easily though, since to get whole-house wireless, some special arrangements will possibly be needed, beyond skills of average do-it-yourselfer
So it's more expensive... but people might adopt it, since they no longer need confusing WEP or WPA technologies (that keep getting broken/obsoleted), and can simply use plain old open wireless again.
That's what repeaters/bridges are for. You just need to convert the LED wireless to another technology, or extend the signal using repeaters.
An example of a repeater apparatus would be: you punch a hole in two opposite sides of a wall. Mount and power two appliances on the wall on each side.
When the appliance receives a signal, it repeats it into the wall.
Its neighbor appliance which just needs to receive the LED light repeated into the wall, receives that, and repeats it into the room it is mounted in.
Come to think of it... if you punch a hole in the ceiling instead, and mount the appliance up there, so it projects LED light into the attic, it may be able to receive the LED light projections from all the other 'repeaters' that were mounted to the ceiling.
For instance, by capturing reflections off of common structure in the crawlspace, where all the LEDs throughout the building can project to (without wall separation)
Also, it can look as innocuous as a smoke detector, or simply be built into the light fixture somehow.
The policy on how to handle employees being terminated should be accompanied with a policy about changing of passwords and access codes, requiring thorough documentation of changes (including codes changed and the new code), AND review of all changes by an immediate peer.
To use an obvious analogy, if a bank teller gets a two week notice I don't think we expect the bank to not let them handle any cash for those two weeks
Bank tellers and all their actions can easily be watched for obvious attempts to commit a crime, and it should be immediately obvious to the manager if the teller attempts to steal anything.
If they have the combination to the vault, access cards to a secure area, building keys, or any alarm combination, it will probably be changed just after they get the news, and be up to security staff to grant access when needed.
necessarily. If I still trust the person but can't afford to keep them due to a bad economy for example
Ah. But how well do you really know them, and how sure are you that you can trust them fully in such an extreme situation?
If they do something you don't like that hurts you (but isn't technically illegal)... after that point, what are you going to do, fire them?
Unfortunately, sometimes they need to train someone else to do the job and have the same problem.
You should have thought about that long before deciding to fire them. They know they are going, and they have little incentive to properly train someone else, which for any really complicated job takes more than 2 weeks to do anyways. Why should they want to do that for you, really?
Most likely you'll instead get some sort of half-hearted training from them, either because they intentionally hold back, or because they're so disturbed by the news, that they won't do a good job training someone, even if they want to.
The great and powerful Jobs has spoken!
Go away and come back next year.
Next year? Oh? But I want my tethering now. Can we at least tether the iPad to the iPhone?
Do not arouse the wrath of the great and powerful Jobs! I said, 'Come back next year.'
Pay no attention to that man behind the curtain....the...Great......Jobs has spoken.
Maybe... DDos is no excuse, though.. DDoS are to be completely expected by such things and 'down due to DDoS' is unacceptable. Microsoft has proven that a well-designed product activation infrastructure can be built to stand strong even in the face of DDoS.
Admittendly they weren't so dumb as to require continuous access to MS servers (or get forced blue screen)
But same deal, really
Down to DDoS would still reflect terrible design, ignorance, or plain negligence on Ubisoft's part.
SSH is attacked often because a lot of sites run it.
Disable SSHD on all machines, and run Kerberized telnet instead.
Huh? Copyright is what prevents you from making it available or getting ahold of it in the first place.
Copyright enforcers find unauthorized or unapproved sources and shut them down, so you can't get the material
If it became public domain, there's little doubt someone would have an archive and be able to make that available, esp. if someone, some time would be willing to pay.
There are plenty of logical reasons for non-negros and negros to be afforded the same rights and protections as all individuals. There is no logical basis for distinguishing there. There is a logical basis for treating non-sentient non-self-aware animal species differently however: their usefulness as a food source, that they are weak and easily eaten, humans evolved to eat them. Playing with your food before eating is typical, a creative outlet, and convenient way of getting exercise and relieving stress (give a cat a mouse some time, and see how much fun the cat has).
it is "human" to do so.
Some humans abuse, eat, or abuse/do other things to animals we subjectively assess to be cruel/mean, so obviously it is human to do so.
The good news is said super rats have no appetite for our carbon-based non-arsenic containing foods.
The bad news is the super rats' excrement will fill the soil with the poison, eventually getting into the water and plants, and killing us all
Actually intelligence doesn't matter... it's "appearance of intelligence" that matters, because from the very beginning, the basis for penalizing animal abuse is an emotional/moral one, not a logical one.
Some people who see an animal experience pain tend to identify with, "empathize" with it, and commit anthropomorphic fallacies. Such is human nature.
Ok, great reason to create a registry of Bedwetters also, then (however).
Whenever you move into a new house, you will be required to inform all your new neighbors that you were a persistent bedwetter past the age of 5.
Since all past bedwetters are dangerous and cannot be trusted. It is a behavior that once practiced may never leave the person. They may suppress it for the rest of their lives, but underneath the potential is there especially given a one in a million encounter.
From Wikipedia: "The triad links animal cruelty, obsession with fire setting, and persistent bedwetting past the age of five to violent behaviors; particularly homicidal behavior"
I see how it is... you are one of those species-ist human supremists.
Now go add your name to the registry of animal haters :)
That would be all well and good if they were providing complete public frameworks, so that private ones would not be needed for any valid use case.
But it's not... these apps can't possibly be implemented using the public frameworks
So, Apple is essentially stifling their platform.
Better to have some apps broken by an update of the OS later, than to have those apps never written at all, probably.
I don't think being an iPhone 3GS owner can quite be considered a form of forced labor.