2600: "LATEST VERIZON DENIAL OF SERVICE ENTERS FOURTH DAY"
(from http://www.2600.com/news/view/article/12106 , pasted because their site is taking ~60 seconds to serve it right now)
Also, with GM you can just save the script with the same filename and it'll use that instead.
This project is 100% useless.
This project is a lot of work for zero benefit.
Googling around, I see tons of misuse: Example of bad usage: "White Stripes are dead (long live white stripes)"
Example of proper usage: "Palm is dead; long live Palm!" (this would mean that Palm got acquired or reformed) "Paper is dead; long live paper!" (could be proper if used in an article about how paper for PRINTING is dead but paper lives on in other forms)
REF: http://en.wikipedia.org/wiki/The_King_is_dead._Long_live_the....
I pick passwords based on easy things to type and the memorize the pattern / commit it to muscle memory. I also try to use obscure but pronounceable patterns somewhere in the pass.
KeePassX + Dropbox is a great way to go, but it's kind of more "DIY"-ish. Still not hard to set up, keeps all my passwords in sync, and KeePassX has some great features like "auto-type" which basically is a one-click website login.
I now use the max-length passwords on all the sites I use, and they're all crazy random ones. I don't memorize any of them because it's so easy to reset a password if I lost my KeePassX access (unlikely since it's on Dropbox + 4 computers + CrashPlan backups).
I don't really understand the point of OSX Server beyond possibly render farms (for music / movies)
Right. There are ways to do it, but not any /good/ ones. Good here meaning "while still letting the software execute efficiently and without a ton of added complexity"
An app can be beautifully engineered by have an awful UX. The inverse is less likely to be true (because bugs and obvious flaws like long delays and unresponsive UIs can quickly degrade UX), but still possible.
That said, I agree with pretty much all of what you said.
(from http://www.2600.com/news/view/article/12106 , pasted because their site is taking ~60 seconds to serve it right now)
You could have cat pictures encrypted with passphrase A and incriminating evidence (that stands up to the best forensic analysis currently available) encrypted with passphrase B and they wouldn't know which is which, if they unlocked ALL the data, or what.
Truecrypt is AMAZING and anyone holding onto stuff that might get them into trouble (esp. w/ foreign gov'ts) should use it.
You might also be missing something about TrueCrypt: plausible deniability. You can have different passphrases that unlock different things. You could provide them with a passphrase the only unlocks innocent documents when really you have CP stored using a DIFFERENT pass phrase -- any this would stand up to any cryptographical analysis -- they simply cannot PROVE that the CP exists or even that more encrypted data exists.
The analogy to a key isn't quite valid here; it's more like the doors in that hallway in the matrix. If you use key A in the door, you will get content A. However, you can use a different key, open the door, and it'll go somewhere else entirely. Also, if you rip the door off the wall, there is just the wall behind it. Crazy stuff, that.
REF: http://en.wikipedia.org/wiki/Death_cab_for_cutie
Regarding the _USEFULNESS_ of this: low. Regarding the entertainment factor: pretty high. I could use a m3u-> txt parser to dump a huge load of youtube videos and make a "music video playlist" -- kind of cool.
I would argue that if skin development is introducing even the slightest delay into the release cycle, they should cut it out ASAP.
Here is the whatweb output: ./whatweb https://online.citibank.com https://online.citibank.com [200] X-UA-Compatible[IE=EmulateIE7, IE=EmulateIE7], UncommonHeaders[jid], Cookies[JFPWebAppInfo,JSESSIONID], Title[Citibank Online], Country[UNITED STATES][US]
Looks like something Java-based. It's fun that sometimes software gets so large that they miss a gaping security hole like this.
ATT: 1.5mbit in most locations and costs $20-$40/month not including phone line.
Comcast: costs $50-$200/month but you can get 6-100mbit in lots of locations.
To anyone who is going to try to play the "free market; let's see some competition!" card:
It's pretty impossible to do in this industry since ATT and Comcast OWN THE INFRASTRUCTURE THAT CONNECTS TO HOUSING. You really think that every city is going to let you either dig up miles of road or put up new lines on their poles? You'd even have to pay ATT/Comcast if you went the "running new lines" route.
The residential ISP business is ABSOLUTELY an oligopoly, and you'd need billions in funding to even have a chance at breaking into the market.
I hope Comcast dies a fiery death and I'm really glad to see Netflix killing them at their own game. VOD / cable boxes have been AWFUL with software that never gets updated even though they can do OTA updates and UIs that look like stuff the airlines used in the early 90s.
UX? What's that....
EDIT:
TL;DR Comcast isn't going to change much any time soon because they already make $50-$300/month in most cases...they have no motivation to change.
If netflix gets more popular, they'll just lower their bandwidth caps more to make you indirectly pay them for netflix.
I'd wager "learning how to properly use 'learned'" wasn't one of them.
http://www.urch.com/forums/english/9214-learned-vs-learnt.ht... "The descriptive answer in American English is: There is no such word as "learnt". Use "learned" always."
Second thought: Hmm, ooh well, I just use google with site: news.ycombinator.com
EDIT: It annoys me when people hate on SQL and act like it's OMGSOSLOW. I would agree that fulltext search BY ITSELF isn't amazing, but you can use something like Sphinx to wrap it and support awesome things like Soundex / Metaphone fuzzy matching. It's also stupid easy to set up. The NoSQL movement is, IMO, largely misguided. If you need to shard data and scale ridiculously, something like Lucene can probably do it. If you need bigger than that, use memcached /redis and shard and map/reduce queries....that makes sense, but NoSQL doesn't seem like a great idea for PRIMARY data storage. It seems like you better have amazing backups :)
And you know someone is going to use [awful library] to solve [big problem] and it will "work".
I just feel like there are better choices for most projects.