Not all of my passwords can be that long. My bank password (the one I care about the most) has a 5 char limit and and I hate random passwords. I came across a good method a few years ago for generating passwords that need to be short: Take a song and chose a line then take the first character of each word and you have an easy to remember but hard to guess password.

Say what? Unless something has really changed between Debian and Ubuntu there really shouldn't be much crud being built i`since it provides a remove feature for obsolete dependencies. I have been running Debian for over a decade and I only reinstall for server replacement or corrupted drives.

It also doesn't help that in some cases the change is rather jarring and the problem has gotten even worse now that the systems are fly by wire.

I had the same problem with the Nvidia drivers but 3.12 was such a large difference on my other systems that I spent the time and patched the Nvidia drivers myself using patches I found using a Google search "Nvidia Linux 3.1.2".

You should be able to do the same but if you get stuck, feel free to contact me for help.

I remember this exact logic right before we had the huge dot-com crash in the early 2000s. If it's not making revenue now it is dangerous to assume just throwing ads on it will somehow make it turn a profit rather than turn users off the product.

What does logic have to do with it? I work for a company that uses 3d secure and it has changed nothing about how the bank treats us when a chargeback happens.

Thankfully tor exports a handy list of exit nodes. This list is also kept in other places and it came in handy a few months back when someone used tor to flood my ssh server with a massive amount of ssh logins. You can even find some scripts that parse the list and turn it into an iptables ruleset.

You are so wrong it's not even funny. The retailer is almost always held responsible for any fraud. If a charge is determined to be fraudulent the retailer is out the money plus a chargeback fee and on top of that, the event is kept track of so if the overall total gets too high, the merchant account gets terminated.

Stupid managers as well. Every few years my employer retries that idea only for the bug counts to skyrocket as the hours get later. After about an 11 hour day, more time is spent fixing bugs created by overtired employees than making actual progress.

You know who got bullied a lot in my school? The kid with the pacemaker. Please tell me how he was supposed to stand up for himself. Also in my experience the kids who fought back ended up with the bullies coming back in groups.

The problem is the kids who bully and not the victims.

The trend of "cutting the cable" has more to do with the fact that with all of those channels, there is still nothing worth watching most of the time. Most of the channels are barely distinguishable from each other and all show similar crap. Even channels that were supposed to be different have become the same as everything else (MTV cut back on music, Syfi cut back on science fiction etc). And that's on top of the fact that anything I find worth watching tends to be on when I would rather be doing something else.

So I'd say the problem with cable is actually the lack of choice disguised as choice.

That's nice and all but can we trust our data formats to stay static for that long? Having the data but being unable to open it seems rather useless to me.

What makes you think they had a choice where they ended up? They needed to pass an internship to graduate and I wonder how many potential opportunities wouldn't exploit them this way.

Why? It autodetects source files and subfolders so they never need to touch the build system.

Once your project reaches a certain size the actual commands and their arguments end up making a multiline mess for each command and aren't actually that helpful unless it's the build process itself you are debugging. It gets even worse if you generate dependency files which involve piping the output of gcc through some arcane sed commands.

I generally prefer having make tell me what it's doing (Generating depfile.d, building file.c, linking file.o) etc. And then it's very easy to spot what file threw the error. Where I work, we turn on every GCC warning we can find and that alone is several lines per gcc execution (programmers are under orders to not leave warnings). Compiles here happen several times an hour but the build system only gets worked on when I have some free time and feel like I need some pain in my life (once a year at best). The other programmers don't know or care that the build system crawls the source tree, duplicates the tree structure in a build folder, generates dependency and object files in the corresponding subfolders of the build folder etc etc. They only want to see what source or include file they broke.