I think that the difference is that Google seems to do it correctly. I've worked in both Google offices and in other companies that did "open floor-plan", and I noticed a few things that Google does right:
It's open within small groups (~12-15) of desks with higher walls separating the groups. This generally means that you have a team sitting together with open communication and you don't have to worry about noise/distractions from other teams.
They have meeting rooms of various sizes, from non-bookable phone rooms (often used for personal calls) up to larger meeting rooms. People are encouraged to grab a meeting room if they're having an in-depth discussion with multiple folks.
Common areas (kitchen, cafeteria) are separated from work areas. This means that visual/auditory/olfactory distractions from those areas are minimized, while still providing a place for people to get together and chat informally.
There are quiet areas for people to focus. Most office have quieter "library" style areas, as well as "wellness" rooms with comfortable chairs/dimmable lighting. I have migraine issues, so the wellness areas were invaluable to me.
That's not quite accurate. If you've shot at someone/been shot at in the past 15 minutes then your ship will go to a safe spot but won't disappear for a while (15min?). For that duration your ship will be in space and can be scanned down and destroyed by someone with the appropriate tools.
They have a number of those in my city, and I love them. The numbers are big enough that I can see it from a distance and when the counter hits 0 the light goes yellow. I wish they'd put them in more intersections around here.
Strange, I am a Canadian citizen who flew from Toronto, Canada to California in August and I was not fingerprinted at all. Perhaps it's only people who are from non-NAFTA countries?
Perhaps it's just a more permanent way of indicating that it's a handicapped spot? Wheelchair symbols painted onto the pavement like they have here in Canada can fade with time making it unclear that it is/was a spot. It's a bit harder to not notice when you've got a big orange thing sticking up from the pavement.
I believe UNCO is the code they use for 'unconfirmed' bugs; mostly cases where a bug report has been submitted but it has not been looked at yet by a member of the Mozilla team.
You can still do that these days, though you'll probably need a non-stock monitor mount in most cases. One of the DBAs where I work uses 2x24" monitors running in portrait mode, 1080x1920.
Don't see how the security is any better than a direct https link between Exchage and your phone.
I honestly am not familiar with Androids/iPhones - do they have the option for remote lockdown/wiping of the device? I know this has been used a few times where I work when someone has managed to lose their BlackBerry or has decided to not return it after being let go from the company.
I think that may run afoul of the new policies as well:
All add-ons must be distributed free of charge. Developers may not create "premium"; versions of add-ons with additional for-pay features, charge money to download an add-on, charge for services related to the add-on, or otherwise require some form of monetary compensation to download or access an add-on.
* fit to be certified as insane (and treated accordingly)
* capable of being guaranteed or certified; "a certifiable fact"
wordnet.princeton.edu/perl/webwn
* That can, or that must be certified; Mentally ill to such an extent that involuntary institutionalization is appropriate; crazy
en.wiktionary.org/wiki/certifiable
I'm currently the president of the Computer Science Club at another Canadian university. We, too, have a variety of machine architectures, and provide web/email accounts to students. We've stopped seeing as many signups for the web hosting and email side of things, and we've shifted our focus recently to a number of other things. For example, we're starting to run tutorials to introduce first year students to both the University's undergraduate computing environment as well as our own, and advertising some of our more powerful machines as a method for students who want to run processor/memory-intensive experiments to do so cheaply. One other thing we did was to make a deal with the web-design club at our school so that they now host all club sites which they design on our servers, since we have the ability to set up subdomains under our university's domain on their behalf. Lastly, one other thing which we're working on improving is setting up a proper library with copies of the various textbooks needed by students, as well as various other recommended reference books.
I'm involved with a group which runs one of the official Ubuntu mirrors, and some days our load hovers around ~300 on that machine. Luckily we're getting a new machine to replace our mirror soon.
I was referring to the fact that other laptops were available to be hacked in the competition mentioned in TFA (which I know nobody reads). With some of the talk which is seen about Macs being more secure or not needing anti-virus software installed on them, having a Mac hacked before a Sony/Fujitsu machine running Windows (which is well-known as a rather vulnerable OS) would be bigger news than if the Windows machines were hacked first.
...if a lot of the folks were focusing solely on the new MacBook air, because it makes a much better headline: " Hacks MacBook Air" vs " Hacks HP Notebook". I'm sure that the other machines could have been exposed quickly as well if they were drawing as much attention as the Air.
Aah. I was unaware that Verisign owns the.com/.net nameservers. In that case the plan is much more sensible. Also, you should never assume that someone posting on/. has read TFA.;)
Yes, but if it still hits on a known TLD, chances are good that their nameserver will have the NS records for that TLD cached, so the request itself won't hit the root nameservers. If someone requests www.gogle.com, and their local nameserver doesn't have anything cached for the "gogle.com." domain, it'll still likely have the NS records for "com." cached, and thus skip the root nameservers.
Most residential and business users will be behind a local DNS server, which probably caches the nameservers for individual TLDs. Since those NS entries on the root servers generally have a 48-hour cache time (and many ISPs DNS servers are probably (mis)configured to hold the data for longer), it doesn't seem like many requests would actually be getting through to Verizon's root servers, especially not enough to make a service like this viable.
Not even a password would be necessary. Nearly all crawlers will pay attention to robots.txt, so if she merely had that in place, the entire issue wouldn't have come up.
She did request that they did, and they did so. Then she asked them for $100,000 in compensation for copying in the first place. You can read more here.
Slashdot Mirror
I think that the difference is that Google seems to do it correctly. I've worked in both Google offices and in other companies that did "open floor-plan", and I noticed a few things that Google does right:
That's not quite accurate. If you've shot at someone/been shot at in the past 15 minutes then your ship will go to a safe spot but won't disappear for a while (15min?). For that duration your ship will be in space and can be scanned down and destroyed by someone with the appropriate tools.
They have a number of those in my city, and I love them. The numbers are big enough that I can see it from a distance and when the counter hits 0 the light goes yellow. I wish they'd put them in more intersections around here.
Strange, I am a Canadian citizen who flew from Toronto, Canada to California in August and I was not fingerprinted at all. Perhaps it's only people who are from non-NAFTA countries?
According to the summary it links user IDs to the IP of the server they were on, not the client's IP.
Perhaps it's just a more permanent way of indicating that it's a handicapped spot? Wheelchair symbols painted onto the pavement like they have here in Canada can fade with time making it unclear that it is/was a spot. It's a bit harder to not notice when you've got a big orange thing sticking up from the pavement.
Or just an increase in the sale of mirrors.
I believe UNCO is the code they use for 'unconfirmed' bugs; mostly cases where a bug report has been submitted but it has not been looked at yet by a member of the Mozilla team.
You can still do that these days, though you'll probably need a non-stock monitor mount in most cases. One of the DBAs where I work uses 2x24" monitors running in portrait mode, 1080x1920.
I honestly am not familiar with Androids/iPhones - do they have the option for remote lockdown/wiping of the device? I know this has been used a few times where I work when someone has managed to lose their BlackBerry or has decided to not return it after being let go from the company.
Not really, it's there in both names. ;)
Whoosh.
Definitions of certifiable on the Web:
* fit to be certified as insane (and treated accordingly)
* capable of being guaranteed or certified; "a certifiable fact"
wordnet.princeton.edu/perl/webwn
* That can, or that must be certified; Mentally ill to such an extent that involuntary institutionalization is appropriate; crazy
en.wiktionary.org/wiki/certifiable
Why not just leave some spare money around instead? Obama does seem to be all for change...
I'm currently the president of the Computer Science Club at another Canadian university. We, too, have a variety of machine architectures, and provide web/email accounts to students. We've stopped seeing as many signups for the web hosting and email side of things, and we've shifted our focus recently to a number of other things. For example, we're starting to run tutorials to introduce first year students to both the University's undergraduate computing environment as well as our own, and advertising some of our more powerful machines as a method for students who want to run processor/memory-intensive experiments to do so cheaply. One other thing we did was to make a deal with the web-design club at our school so that they now host all club sites which they design on our servers, since we have the ability to set up subdomains under our university's domain on their behalf. Lastly, one other thing which we're working on improving is setting up a proper library with copies of the various textbooks needed by students, as well as various other recommended reference books.
I'm involved with a group which runs one of the official Ubuntu mirrors, and some days our load hovers around ~300 on that machine. Luckily we're getting a new machine to replace our mirror soon.
I was referring to the fact that other laptops were available to be hacked in the competition mentioned in TFA (which I know nobody reads). With some of the talk which is seen about Macs being more secure or not needing anti-virus software installed on them, having a Mac hacked before a Sony/Fujitsu machine running Windows (which is well-known as a rather vulnerable OS) would be bigger news than if the Windows machines were hacked first.
...if a lot of the folks were focusing solely on the new MacBook air, because it makes a much better headline: " Hacks MacBook Air" vs " Hacks HP Notebook". I'm sure that the other machines could have been exposed quickly as well if they were drawing as much attention as the Air.
Aah. I was unaware that Verisign owns the .com/.net nameservers. In that case the plan is much more sensible. Also, you should never assume that someone posting on /. has read TFA. ;)
Yes, but if it still hits on a known TLD, chances are good that their nameserver will have the NS records for that TLD cached, so the request itself won't hit the root nameservers. If someone requests www.gogle.com, and their local nameserver doesn't have anything cached for the "gogle.com." domain, it'll still likely have the NS records for "com." cached, and thus skip the root nameservers.
Most residential and business users will be behind a local DNS server, which probably caches the nameservers for individual TLDs. Since those NS entries on the root servers generally have a 48-hour cache time (and many ISPs DNS servers are probably (mis)configured to hold the data for longer), it doesn't seem like many requests would actually be getting through to Verizon's root servers, especially not enough to make a service like this viable.
That's a completely irrational idea!
Able to read Perl? I call shenanigans!
Not even a password would be necessary. Nearly all crawlers will pay attention to robots.txt, so if she merely had that in place, the entire issue wouldn't have come up.
She did request that they did, and they did so. Then she asked them for $100,000 in compensation for copying in the first place. You can read more here.