925 karma · joined September 21, 2007
Why is this simple notion mentioned nowhere in the EFF letter?
argh.
I wonder when we will reach "peak peak-resource stories"?
Quite a few states have laws limiting the scope in both time and 'intellectual space' over which your employer may claim rights. In Washington (I'm not a lawyer, but I have recent experience with this), the law limits PIAAs to development using company resources, in the same or prospective market, and term of employment +6 months -- and burden of proof is on the employee. From what I researched at the time, this seemed to be about the middle of the road for employee-cum-entrepreneur legal protections. I'm not sure it matters in the end...if you can't afford to leave your job, can you really afford a legal battle with your behemoth ex-employer? The best way to avoid needing the legal protections is to be open, transparent, and avoid conflicts of interest.
There's more than one way to build a command economy...
git diff-and-fix-hubris-and-corruption-but-oh-wait-not-really government/legislation/intentional_obfuscator.rb
?But...there are probably more important battles to choose to fight during your project.
Also, "hurt a site financially" seems a bit hyperbolic; ad-blocking users are priced in to CPM. If a content site's audience intersects largely with adblock users, and they don't like the revenue picture, they are more likely to succeed by exploring alternate revenue models or move to serving different audiences, than by convincing their users to change.
[edit] I'm not trying to make a judgment on adblockers being right or wrong, just pointing out what I see as inconsistencies in the argument against them.
By your logic, it's immoral to mute the TV, go to the kitchen, and make a sandwich during the commercial break. In reality, some percentage of the population makes sandwiches instead of watching ads, and this behavior is priced into the advertising contracts.
There. Fixed it for ya.
Flash was part of the reason I switched; I was not wholly comfortable with [what I perceive as] the fragile and convoluted page load dependency between google vis and jquery (perhaps you have a better way).