I'm often interested in deleting accounts I don't use to avoid handing over my data to attackers when their systems are breached. The more sites I've given my data to, the more likely some random attack that grabs a DB dump is to have a copy of my Name, Email, (hashed)? password, etc. Depending on the type of site it may even get some bonus data in the form of answers to security questions.

This sounds lame, but the amount of spam currently directed at the accounts I used on: the motley fool, eharmony, Adobe, is quite high. Just putting my name at the top makes it that much more likely I'll be scammed by some phishing email.

amazon link was for rack cables, something more like this: http://www.metsec.com/cable-management/cable-tray/

Wifi is.. nice, but I wouldn't use it in a full office environment for everyday access. It's a big brick room, lots of computers, lots of interference. Not only is WiFi slower, but you end up with less throughput as interference requires random packets to be retransmitted.

I might not bother trying to find beautiful trays, but instead find regular ones, then decorate!

Take something like this: http://www.amazon.com/gp/product/B003AU3HG6?ie=UTF8&camp=213733&creative=393185&creativeASIN=B003AU3HG6&linkCode=shr&tag=preinheimerco-20&qid=1386087250&sr=8-5&keywords=wire+tray

Then put these underneath: http://www.whatisblik.com/shop/explore?theme=77

Turn your office ceiling into a pacman arena!

I very much think the city can have an issue on its own, without the hotel lobby being involved.

Property owners are learning that they can make more money posting their apartments on AirBnB than renting them out traditionally. It's in their economic best interest to hire a cleaning service, throw in some flat-pack furniture, and stop renting normally. This distorts the rental market as people who live in the city end up competing with short-term tourists for places to live. Cities want to be somewhere people live, not just somewhere people visit.

AirBnB hosts also compete against hotels with a stacked deck. They're not forced to charge the standard hotel-night taxes, nor meet ID checking requirements on guests, pay commercial property tax, meet commercial firecode requirements, etc. I can understand why hotels would be angry, but they're far from the only group with a vested interest in the outcome.

I understand the basis of the franchise laws as they exist to be: Car companies needed to expand in the old days, but lacked the capitol. Franchisees bought the rights to sell cars from a given company, put their name on the door, and started selling Ford, GM, whatever. Once the car companies themselves were in better shape (with cash kicking around) it would have been trivial for them to open their own dealership down the road, then either stop selling cars to the franchisee, or undercut their prices, etc. etc. Without those laws it would have been easy, and economically beneficial, for the car companies to kill their dealer network and replace it with corporate stores once they had the money to do so.

No franchisee has given money to Telsa to start selling their cars, so there's no one who needs those protections.

Do you regret the swath of backwards incompatible changes in version 3 that have lead to such slow uptake, or do you feel it was the best move for the language moving forward?

Watch out, they may respond with poisonous gas!

http://www.27bslash6.com/halogen.html

Thanks, I'd read the article, but not the bill text.

So, this presents some challenges to me.

I'm one of the co-founders of WonderProxy (https://wonderproxy.com), running a global proxy network you might imagine that we have a fair large log set. Our billing process involves pulling those logs into a central location, parsing out the information billing cares about (customer & amount transferred) and recording that in aggregate. We store the raw log files in the raw form for some period of time to comply with any sort of warrant from law enforcement (our goal isn't to be an anonymous proxy), then delete them.

We've deliberately avoided storing the details we have about traffic in any sort of a searchable form. We don't care unless something comes up, and as a general rule we don't think it's any of our business. So this is information about a customer we do possess, but also information that we've deliberately avoided making easy to access. To grab it we'd eschew all our UI tools, drop to a command line, and start uncompromising raw logs, then dropping in with grep or something to filter the user. Then another manual pass to make sure we haven't accidentally included a line from a different customer. For a customer who has only paid us $15 we're going to lose money once we comply.

Then there's our webserver logs. If someone logged in, we can technically deduce what requests are associated with that user, but the apache logs don't store that in a nice easy to read format. We'd probably need to correlate a bunch of different systems in ways we've never done before (because we don't care who loaded main.css on Tuesday the 4th at 16:22:32) to ensure we've handed everything over.

This is of course assuming that we're required to comply. We're a Canadian corporation, federally registered, all that fun stuff. But we do have servers in the US, even ones in California. Of course, getting an answer from our lawyer on whether or not we're required to comply would also cost well more than $15, and that's before we've started trying.

Then there's more privileged information. Internally calculated fraud scores, internal customer notes ("these people never pay on time", "serious PITA, don't give a discount", "Super nice") which is also information we have on a customer, but generally something we'd rather not share.

As a user of the web, I like this idea. As a provider of services the cost of compliance scares me.

Standards for Date/Time are one thing, I've had a lot of trouble trying to standardize on adding Dates. What's August 31st + 1 Month?

See: http://stackoverflow.com/q/7614361/37462

We're running a network of 80+ servers around the world (https://wonderproxy.com).

We've moved in stages getting things off standard ports.

Whole network standard - several hundred attempts per day
a few standard, rest on non-standard ports - tens of attacks per day
all non-standard ports - 0-5 attacks per day.

It's been worth doing just for the reduced reporting volume in our status systems.

+1

Reference: http://www.cpcc.ca/en/the-cpcc/private-copying-tariff

Interesting take on that availability: http://thetrichordist.wordpress.com/2012/04/15/meet-the-new-boss-worse-than-the-old-boss-full-post/