fubarred
The point of Web of Trust is to only trust keys that other people you know have also signed. Everything else is garbage until proven otherwise.
Key servers are untrustworthy because anyone can upload random shit to them.
Trying to shift WoT to a third party is trying to get something for free that doesn't emphasize solving the problem: getting everyone you know signing keys of only other people they know.
https://www.kernel.org/signature.html#kernel-org-web-of-trus...
In other words, regulation is a necessary "evil" to make unsustainable behavior illegal.
"Nuptial love maketh mankind, friendly love perfecteth it, but wonton love corrupteth and embaseth it." ~ someone that hailed from southern Hertfordshire about a century later than in the article
GWB's NCBLA further inculcated standardized testing as an official religion in American education system. It's a complete and utter failure; another in a long line of ill-informed, "top-down solutions" that cause more harm than good.
http://www.washingtonpost.com/blogs/answer-sheet/post/a-deca...
First Bogey's Books in Davis, then even Borders. :(
From what I heard at the time, Powell's (one of the bookstore others would sell their inventory to) was overwhelmed with shipments from closing bookstores and the market rate for used domestic books was quite low for a long time. Has this changed?
Also it's worth nothing that going out-of-your way to be fair isn't just "being nice," it selfishly reduces risk of issues, especially in small, highly-connected industries where reputation is the first consideration.
So if we are to take her account at face value, it seems like WB misjudged that word would get around and then lawsuits. (An expensive lesson in hubris.)
http://www.foo.be/docs/tpj/issues/vol2_1/tpj0201-0004.html
Also, Castle Bravo was ~3x bigger than predicted because of a failure to correctly model the tritium production from lithium-7.
https://en.wikipedia.org/wiki/Castle_Bravo#Cause_of_high_yie...
USN Independence-class littoral combat ship
So based on personal style, it's possible to get better by walking a middle path of not too crappy and not over-crafted.
(The real work is the stuff that needs doing or somehow seems "most important.")
If fired, they would have missed their destination by thousands of miles.
http://www.foo.be/docs/tpj/issues/vol2_1/tpj0201-0004.htmlNote: a maths user error, not a "Perl sucks" rant.
(Anyone from/in India or the nearby area know?)
From the supply-side point-of-view (film maker, movie theater, on-demand service), it depends. Artists can choose to release for free like The Beastie Boys are other doing, knowing enough people will still buy the retail package to keep them afloat. But to see your blood, sweat and tears shared without people paying a dime, might be tough. It's further complicated because you don't want to tick off freeloaders that can be converted to customers or whom happen to be major customers in same-brand products/services.
Both taken together, it's becomes a self-selecting, personal choice to vote with one's wallet.
https://en.wikipedia.org/wiki/The_Better_Angels_of_Our_Natur...
(Religious extremists, totalitarian regimes notwithstanding.)
- 0 Facebook, 3 Google, 0 Twitter
- 0 Advertising
- 6 Analytics: 1 ClickTale, 4 MixPanel, 1 Chartbeat
- 0 Social
- 6 Content: 3 Google, 3 Optimizely
Disable SSLv3
RubyGems blames YARD, YARD blames RubyGems: awesome (not)
For edge devices, it's a criminal that high security standards are not more pervasive. Though given the nature of retail products, it's not a big surprise even though it is still disappointing. (How many of these boxes even work for longer than 5 minutes without spontaneously rebooting (crashing) or having a xfer rate within an order of magnitude of the channel bandwidth?)
PS: If there were a minimal OpenBSD/(x86|arm) based pfSense-alike project that could be easily themed, minified and plugin-ed, that would rock... and potentially dramatically reduce the attack surface by reducing the duplication of awful embedded web app implementations. (Yes, there are DDWRT and other Linux embedded network gear projects and pfSense (which is great)... OpenBSD for fewer lines of code.) It seems like what might happen going forward because the existing vendor stacks are often terrible and likely expensive for them to maintain. (Kickstarter for hw+sw or enterprise "crowd"-funded perhaps.)
Folks requesting pfSense ARM support: https://forum.pfsense.org/index.php?topic=34707.0
An explanation of Postgres / Oracle similarities:
Postgres Plus AS (the commercial product) aims to be a drop-in replacement for Oracle, so it's no surprise that Postgres tends to overlap with regard to Oracle functionality. It also makes it safer to choose Postgres as a default starting point, because the migration options to Oracle / Postgres Plus / etc. are there.
http://www.enterprisedb.com/products-services-training/produ...
Disclaimer: unaffiliated pimping Postgres Plus because it likely subsidizes Postgres OSS dev. (Postgres OSS code is generally well-engineered.)
3rd-party: there's the non-FUSE port https://openzfsonosx.org/
Overall though, services should expose either a well/self-documented RESTful, zmq or similar API such that they can be rewritten in (your favorite whatever here). Being able to discover the API meta information automagically can be helpful for autogenerating clients.
The other aspect is that services have a risk budget: if the service is conventional and not as crucial, increase the experimentation. If the business/process model is risky/uncertain, use common, stable technologies.
(Gist: Pick from the toolbox, carefully... apply common-sense... Don't get stuck on perfect now or perfect waay later... Anticipate a little now to avoid pain of changing later.)
PS: Enterprise Rails is a great read. It's safe to ignore the Rails bits, because the architecture bits are universal and excellent.
Update: RESTful API metadata formats http://apiux.com/2013/04/09/rest-metadata-formats/ (and also https://en.wikipedia.org/wiki/HATEOAS )