89 karma · joined April 7, 2013
Fact is, that their backbones aren't on any limit at all. The real bottleneck of the Internet connection is actually the last mile, the subscriber line. And that cable is exclusive per customer, so no shared medium and throttling wouldn't improve anything than making it possible to earn more money by selling premium contracts. To be fair, this is different for Internet over the TV cable which is indeed a shared medium. Still, throttling on the basis of a monthly limit doesn't make sense since it is reset for the beginning of every month.
Oh, and also that ISP was the only one not interested in doing a direct peering with Google's local CDNs for free. In France Google is actually paying for getting YouTube better routed.
The important thing is that these ISPs just try to make money on both ends of the cable while actually arguing with the power of the opponents. "Hey enduser, here you'll get YouTube! - Hey Google, wanna have more satisfied users?" And that they are often actively lying for achieving that.
Seriously, all those todo/productivity/alarm apps that try control you are just bullshit. At least as a techie you could circumvent them all. In the end, it's all about your habit and your will and going to bed earlier etc. and the use of that app is, if any, only some creative reminder. It's important to get that the app itself doesn't solve anything for you.
Also note that if there is any unjustified punishment (in this case e.g. a huge traffic jam, canceled trains, ...) or just misbehavior of the app or the hardware itself (e.g. no location data) the effect might be rather counter-productive.
More interesting is the other change: reCaptcha now tries to detects real users and then only generates a simple number captcha for the classical part. Likely they are using your Google Account cookie or Google Analytics for that.
WordPress is nice if you need a blog or at least a CMS for luser or if you need some framework to build on. Is that the case?
Maybe it's a useful abstraction (e.g. uptime, maintenance, development) and maybe it's good that someone without developer knowledge could work on it, but you told it would need a lot of integration work? Sounds like you should create an API then. If you need an API anyway, than this actually would be a great way to test it in a real environment. Otherwise likely unneeded effort.
To speak about WordPress plugins, please mind, that most of them are rather simple. Hook some button code and JavaScript somewhere and offer some simple configuration backend UI. Deep integration for any features the user might see often needs custom CSS work, editing the site template or even coding within the plugin. At least that's my experience with my personal requirements. Or to say it in different words: Integrating Facebook buttons isn't that hard anyway, but a professional newsletter would be a lot of work anyway. Also you could likely reuse the plugin code and transform it into Rails code.
Seriously, words like "shit" or "penis" aren't offensive at all these days. Other are just collegial and unprofessional. For someone from Europe this really looks like needless uptightness. It's like a kid isn't even allowed to see her naked mother.
Also, from some educative point of view, I think it's likely the worst solution to simply conceal them from your kids. As a parent you could easily explain their meaning, that it might be rude for some etc. Actually, the important point is to be reflective when learning those words. Those rather simple words are not like showing hardcode porn to children. I don't wanna say that you couldn't be verbally offensive, but that's not the point here.
Indeed you could personalizes the keys for every user. So you could detect a leaked private key that is widely used and proceed against. Still that wouldn't hinder personal further use of that private key, e.g. for exporting data (similar to breaking DRM).
Also, the "potential source of vulnerability" has nothing to do with how big you are.
SSL is as save as the CA list used by the browser is. It really doesn't matter which CA you actually choose then.
In fact, you don't have to trust StartSSL at all. They securely give you a valid cert while you don't have to reveal your private key at any time. Your private key is either generated manually on your sever by yourself or within the browser, on client side.
The important points are: StartSSL is trusted by all modern browsers and systems and they are cheap. There is nothing more to care about. In fact, _any_ trusted CA could be attacked and generate certs for man-in-the-middle attacks.
So, stop your stupid prejudice here. Actually, a CA from the Netherlands got known for being corrupted some years ago.
I just don't see it that wrong like you do. I wonder, if there is an argumentation to really call them stupid. And I don't even think this is relevant referring to their image.
As you said, this only affects people who aren't either informed about computer topics, don't know they had a Yahoo mail at all or who simply reregister their old mail address.
As I user, I have to update my email address I use and other services should delete inactive accounts, too. Or at least notify inactive users. I know, especially the latter option is more or less inexistent. But although think of all the data that users have no access to, because of lost passwords etc. I rather see that deleted.
Also, if Yahoo is doing things right, they would only delete accounts with no activity for a serious amount of time, e.g. no access, not even POP3 since over 2 years.
Isn't the real problem that users and services put too much trust in plain email addresses? Especially when accounts are outdated? Crypto might help here someday in the future.
We could even say: Isn't it your fault that you didn't keep track on which services you used that email? Or that you lost your password? Why blame Yahoo for that?
"Encrypt synced passwords with your Google credentials" is impossible in times of app specific passwords, right?
Also some companies, e.g. CloudFare has it documented somewhere, also use TLS 1.2 in their internal network.