Thanks for sharing that :)

All-In-One Gestures and MeasureIt are the only extensions I have installed that aren't compatible. Unfortunately I'm a bit too fond of All-In-One to upgrade and be without it just yet.

Off-topic, but I have to ask: are you an evil slayer of monkeys or a slayer of evil monkeys?

Having a button to interact with things, with the nature of the interaction being context-sensitive, is one thing; making the function itself dependent on context is quite another, especially when the functions conflict and the contexts are similar. A good example of this is Prince of Persia: Sands of Time. They did a good job overall of giving you the ability to perform a broad range of activities with onle a handlful of keys, but they overdid it with having one button for both functions of the dagger: rewinding and coup-de-grac. This creates a problem: your ability to reverse time at any moment in the game shuts down every now and then, and your attempts to finish off a defeated opponent occasionally resurrect your enemies instead (not to mention deprive you of sand when you were counting on repleneshing it). Using just one more key would have made the game far better.

Of course having a different button for every possible action in the game is silly, but going to the opposite extreme and cramming absolutely everything into one button for the sake of eliminating one or two keys just as bad. As Albert Einstein said, "Everything should be made as simple as possible, but no simpler.".

But in this case the name of the laptop is a direct reference to the operating system that it uses, so the separation isn't clear, and the only similarity between the names of the two laptops is that they both refer to the name of the same operating system. This doesn't look like a particularly strong case.

Naturally. As I mentioned, I hadn't read the article when I wrote that and was responding directly to the parent poster's question:

There's no incongruity between the statements because a simple 256-bit RSA is not a great way to encrypt data.

RSA is usually 1024 bits or more. 256-bit sounds great if you're used to talking about AES encryption or other similar symmetric algorithms, but it's pretty small for an RSA key. I'm not an expert on cryptology (I haven't even read TFA yet so don't trust anything I say), but this looks like it was an easy target.

Aside from this and this.

What you made is a second-stage bootloader. All those really need to do is load some other program into memory and then transfer control to it. Coreboot is a primary bootloader - it handles starting up the computer, setting up the memory and CPU modes, testing harware, providing services such as the hard-drive access that your loader would need, and finally loading your secondary loader for you. Your job was easy because there wasn't much left to do.

Coreboot is more complicated than your loader because yours was piggybacking off something else, whereas Coreboot is that something else on which other people's loaders rely.

I'm not sure if I explained that well, but I hope it helped.

I agree - that this is a very appriate use of DRM. The big problem with DRM is that it is usually used to hold onto control of something after selling it to someone else. The customers then have a strong impetus to break the DRM in order to reclaim what they paid for, and those who aren't inclined to do so tend to build up a sense of resentment toward the supplier. This means making effective DRM is difficult and expensive, and also means you alienate your customers. In the case of a library you would ask to borrow an e-book for a couple of weeks and they give you a DRM'd copy of the work (hopefully made from a non-DRM archive so that they don't just vanish one day) which lasts for 2 weeks after which you can ask for another if you so wish. There's no real reason for someone to feel forced to crack this e-book (even if expiry dates are easier to crack than activation server requirement) or to resent the library or the publisher for not giving you something that lasts for as long as you can look after it (since you're just borrowing it anyway, and therefor have no reasonable expectation of being able to keep it).

You seem confused. OP was never intending to make a haiku. Piaku has no relation to haiku other than the shoutout in the name, so claiming that it isn't in haiku form is missing the point. Incidentally, your response is not in haiku form either; you have too many moras in your second line.

It's piaku,
so:
three, one, and four

Microsoft couldn't successfully sue over the Windows trademark. Microsoft lost that case [citation], and after 2 more years of trying to appeal the decision they eventually gave up and bought the Lindows trademark for $20 million [citation] instead.

Personally, I'd use this Homestuck meme for that

It's not only possible, but it's already done in the case of stored procedures and prepared statements. When a newbie first arrives, inform him that his code should access the database using stored procedures and that when he absolutely has to construct statements directly then those statements must be prepared and never constructed from user input. No more SQL injections. If the newbie ever takes a moment to stop and consider why that rule is there then he will most likely (I hope) learn the lesson for himself through contemplation.

My credit card uses a PIN. I have only rarely encountered merchants who accept cards without requesting the PIN, and in those cases a signature is always required. Usually they ask for the PIN and a signature. I'm South African, and it worked the same way in New Zealand when I visited last year (except that they have 4-digit PINs instead of the 5-digit ones we have here).