I think you are totally right here. The phrasing of this question as being about 'security' is actually totally off base. From the student's perspective, there is no advantage to security. Only the textbook publishers actually benefit from security - they don't want people who haven't paid for the textbooks to read them.

For the student, what he or she actually cares about is being able to easily access he or her school stuff. The worst case scenario is not someone stealing his or her password, it's not being able to recall his or her password and thus being unable to participate in class. Lastpass etc is overthinking it. Just set the password to something simple and easy to remember, and write it down just in case they forget.

Don't forget too that if Salmond alienates the UK taxpayer, even a modest boycott on Scottish exports would ruin the Scottish economy. Any deal he strikes has to look palatable.

I shall be referring this matter to the German police.

Go do that; their contact address is support@polizei.de

> sued

*prosecuted, even.

1 second / 4.4 trillion * 3E8 m/s = 68 microns.

That's the distance light covers between frames. Wow.

okay, what did the bartender say?

"Do you think this is a fucking joke?"

Oh no! That pixel representing the 25x25 area of my face will violate my privacy so badly if I happen to look up at the wrong moment!

It didn't but yahoo is a webmail provider and webmail kinda implies that the provider will either be storing the key or at the very least be able to access it by tweaking some javascript a litte.

Not necessarily. Securely handling keys is indeed impossible for untrusted Javascript, but it should be feasible to provide a browser add-on (analogous to Enigmail for Thunderbird) with a key management UI and PGP bindings for Javascript. As long as that add-on is open-source and vetted by browser vendors, you don't need to trust Yahoo's web page (let alone their server) with your private key.

Ideally, this would be a core part of Firefox / Chrome, or at least a unified add-on, but in practice Yahoo!, Gmail and others would probably insist on making their own.

However, a general-purpose add-on could potentially allow encrypting/signing the content of any text field in a page, so it wouldn't depend on the email provider's support.

(n/t)

Yet calls other people idiots.

> SourceForge

What year is it?!

Its free, take it or leave it. contribute or STFU.

You don't like it? We don't care.

And the problem isn't ours its yours since you're the one whining.

This attitude is why every single piece of free software that is widely in use (Firefox, Ubuntu, Android, etc.) is developed and distributed by commercial companies. Community-driven development is good at fixing bugs, but sucks when documenting or supporting.

It is from their perspective, which makes this a stupid decision even by their own interests.

each time a big truck enters

It's not a big truck!

Sure, let's tear apart the integrity of our global network for the sake of sticking it to a government. Did anyone think through what would happen if you disrupted the network on such a scale? The national ISPs would host their own root, and anyone abroad who wanted to keep accessing those domains would likewise switch to alt roots.

End result, the domain name system gets fractured, ICANN and the US govt retain less control of the internet, and also they look like assholes.

Good thing this was dismissed as the dumb idea it was.