413 karma · joined September 9, 2010
I do wish it were possible to write the rules in a more context-sensitive way, maybe possible with some standards around payloads (if the WAF knows that an endpoint is accepting a specific structured format, and how escapes work in that format, it could relax accordingly). But that's probably a pipe dream. Since the backend could be doing anything, paranoid rulesets have to treat even escaped data as a potential issue and it's up to users to poke holes.
They still have a WAF product, though I don't think anything in the standard managed ruleset will fire just on quotes, the SQLi and XSS checks are a bit more sophisticated than that.
From personal experience, they will fire a lot if someone uses a WAF-protected CMS to write a post about SQL.
A gang war between two truck companies is obviously very inefficient, but so too is the extreme day-to-day competition for tows. You're right that the government-run scenario would involve idle capacity, but the OP article describes a situation where there is already an especially wasteful and ridiculous form of over-capacity (multiple drivers racing to the scene of a crash, a waste of fuel and labor capacity). The "surveillance system" you mention is already in place in the private towing example, it's just a wildly inefficient version that lacks centralized dispatch.
Government-run liquor stores are also a perfect counter-example to your point--their whole purpose is to not provide the most convenient consumer-friendly option possible, and instead to reduce easy access to liquor and attempt to rein in some of the negative externalities that come with it. For the record, I'm not a fan of that approach, but in many cases it's an example of government succeeding in what it set out to do, not the reverse.
There is no scenario where Zuckerberg's net worth is reduced to an amount that one person is capable of spending in a lifetime. In terms of acting as an accountability mechanism, what is the difference between $100M and $65B?
> Moreover, when they screw up, they do not pass a law to force us to clean up their mess.
What was the Emergency Economic Stabilization Act of 2008 about then? And did the CEOs of any of the banks that were bailed out by TARP end up suffering any material deprivation as a result?
(That's without being prompted with the specific $ amount of the subsidies, as far as I can see. If they had mentioned the $4 billion figure, the response might have been even more overwhelming.)
This could quickly make a side project unsustainable, if the owner of a (hypothetical, not this specific) project has limited $ for hosting costs. The author of the project can't make use of the obvious strategy of dropping in an ad or two to defray hosting costs because the images are being hotlinked. This kind of behavior would be a violation of the ToS on almost any site that has one; it would certainly be a violation of Apple's own ToS. But beyond that, it's just thoughtless and rude.
But one caveat is that if you need to hydrate serverside-rendered React markup for clientside use, that will add at least some small performance penalty. And you will also want to pass in props data that matches as closely as possible between the client and server, which means that your base page will need to include some serialized version of the data that should be passed in as props to the component(s) you serverside-rendered and want to hydrate. If this is a large chunk of data, there could be negative SEO impact if it is placed above meaningful content in the page or if the time to download it delays complete load of the page.
An example feature the SDK gives you is the ability to subscribe to an event that's triggered once the user successfully adds a Like, there's all kinds of extra stuff like that buried in there that you wouldn't expect when you just want to add a Like button.
I'm a frontend developer/engineering director at GMG, where we're looking for a strong frontend engineer to help build new features to support a high-traffic set of media sites (Gizmodo, Kotaku, Lifehacker, Deadspin, Jezebel, Jalopnik) with very active commenting communities. Most of our frontend is Backbone/Marionette.js-based, with Scala on the backend, but we're continuing to evolve our stack; experience with React and Node is a huge plus!
More info here: http://gizmodo.com/careers/job/205905?gh_jid=205905.
We also have frontend and backend openings in Budapest -- see here for more details: http://gizmodo.com/careers/budapest#openings
http://blog.rebelmouse.com/talented_javascript_developer-245.... • developer@rebelmouse.com
RebelMouse is a social CMS that allows for easily creating beautiful sites. Users (which include Fortune 500 companies as well as individuals and media companies) use it to power entire sites as well as ads and user-participation features like http://www.corybooker.com/runwithcory. There are a number of interesting frontend challenges to work on here, as we're focused on letting users easily customize their sites significantly while remaining secure and easy to use. To this end, we're looking for a developer with strong Javascript experience, including use of Backbone.js, and experience architecting large web-apps.
Key requirements:
• Strong Javascript skills and a passion for front-end web development
• High level understanding of architecture
• Experience with AMD/RequireJS, Backbone
• Experience optimizing page speed
http://blog.rebelmouse.com/talented_javascript_developer-245... • developer@rebelmouse.com
RebelMouse is a social CMS that allows for easily creating beautiful sites. Users (which include Fortune 500 companies as well as individuals and media companies) use it to power entire sites as well as ads and user-participation features like http://www.corybooker.com/runwithcory.
There are a number of interesting frontend challenges to work on here, as we're focused on letting users easily customize their sites significantly while remaining secure and easy to use. To this end, we're looking for a developer with strong Javascript experience, including use of Backbone.js, and experience architecting large web-apps.
Key requirements:
• Strong Javascript skills and a passion for front-end web development
• High level understanding of architecture
• Experience with AMD/RequireJS, Backbone
• Experience optimizing page speed