I'd expect the next generation of drugs will focus on things like improving monocarboxylate transporter throughput/efficiency.
192 karma · joined February 18, 2014
I'd expect the next generation of drugs will focus on things like improving monocarboxylate transporter throughput/efficiency.
If you started getting spam to tumblr.w8ke2iowieiu3k3@example.org then I'd be suspicious. (I must remember to do this for new things I sign up to.)
Other (one-off or infrequent) protests such as Critical Mass certainly obstruct free passage along the highway, but they are tolerated.
I guess it's because everyday more and more people on here are finding themselves on the other side of the fence, i.e. finding that some of their users are ripping off their content/site.
I use No-Script and whitelist sites as required, it's just a click or two, but for any new site I go to JavaScript is disabled.
As far as home working is concerned, I do it (along with slightly different hours) during term time to allow me to do drop-off/pick-ups. There's no-one else at home when I'm working from home.
During holidays I'm either off to look after children or I work from the office. I don't have enough space to effectively shut myself off.
I'd be looking to provide an extra private/internal support email address made available to the largest customers.
And the training (and reassessment) in flying aeroplanes is ongoing, unlike most countries approach to driver education.
I passed my driving test(s) 20 years ago and since then there's been a huge number of changes in technology, laws, road layout, etc and yet my license is valid for another 30+ years.
They may understand it as "mosquito" rather than "little fly" but that is a valid literal translation, just like "gatito" is "kitten" but the literal translation would be diminutive-of-cat -> "little cat".
"And, we have reason to believe based on the data structures used by OpenSSL and the modified version of NGINX that we use, that it may in fact be impossible."
as
"We've reviewed the code and we don't think it's vulnerable."
Obviously you disagree.
Looking impressive with hindsight is relatively easy.
I wonder what the odds are on a hash collision from another email address (including abusing + addressing) that genuinely belongs to another person (rather than just exists) and therefore the resulting hash does not uniquely identify a single person.
https://github.com/joyent/node/search?q=PURIFY
Specifically it is these two files:-
https://github.com/joyent/node/blob/5fcd6e40385f45bc90916893...
https://github.com/joyent/node/blob/c20b209dbb7e2f3ac8a75a87...
In the first it just does a memset of the buffer so that the values are not unset.
In the second it doesn't use a (possibly only partially filled) buffer as a source of entropy.
1. e.g.
$ echo -n billg@microsoft.com | sha1sum
2517e4726f81e16f65eb95cf6446ad35352f566e -> This patch is a variant of what we've been using to help protect customer keys for a decade.
1. From the original Akamai missive: http://article.gmane.org/gmane.comp.encryption.openssl.user/...
a) Leaving your password unchanged on a site because it is still vulnerable.
b) Changing your password on a site that is still vulnerable.
Of course I'll have to do that work now, but you never know if Dyn will change their mind so I'll hold out until right near the bitter end.
A single IP of my home router just isn't worth $25 a year IMHO. There are plenty of other companies that offer the service for free so I'll just leave Dyn with (a probably undeserved[2]) negative opinion of them for kicking me out.
1. It was hardly difficult, they sent you a reminder each time that contained the link to click on!
2. Not entirely sure how long I've used Dyn for, the earliest email I can find is one about my host expiring back in February 2006.
If I want free wifi access around the country (via BT Openzone) then I need to run BT's router (which includes the magic to run a separate managed public Wifi access point via BT Fon).
It's annoying, but I can live with it (especially when they get around to upgrading my cabinet to FTTC and I get 60Mbps/20Mbps).
Heh. Eliding the hex values of the password might have been a good idea.
256 bits is 32 bytes
If you get 64kB of payload data back each time then it can only contain 65536-31=65505 different consecutive strings of 32 bytes.
a) Do not use company time or equipment. Pretty obvious that one.
b) No doing something that competes directly with IBM. This has to be more specific than "working with computers". It means I can still get beer money for helping friends/family fix their computers/servers, but I can't start a small consultancy that aims to take possible business away from IBM. I can start a social sports related side project website because IBM aren't in that space. But if I worked on Websphere Application Server (I don't!) I couldn't contribute to, for example, Apache Tomcat/Geronimo or JBoss AS. I could write my own game Apps and sell them through the App Store. Etc.
c) Contributing to OSS in your spare time needs to be cleared with IBM, just in case. The main reason is that everyone loves to sue IBM and OSS is fertile ground given the various OSS licenses and implications. If I do some work on some OSS package in my spare time it means I'm tainted in that area. If I then do any work on a commercial application in the same area then it opens the door for people to claim that the commercial work I've done has some work that could have been influenced by the OSS code and part of the commercial application is therefore derivative of the OSS work. With some OSS licenses this could mean that the entire commercial application is considered a derivative work and, depending on the license, the source code would need to be released or IBM could not charge for the software, etc.
It's not all doom and gloom. I work with some people that have got clearance to work on OSS software, they just have to make sure they avoid working with anything related to it on the commercial side (to the point of not having access to the source code to provide plausible deniability). You also need to think in advance and not work on anything that we could reasonably be working on in the future.
We are also regularly warned to avoid even looking at any OSS related to the commercial code we work on, for fear of tainting. Same for Googling for answers to technical questions and copy-and-pasting code from SO or elsewhere. You've generally got no idea of the copyright/licensing aspects of any code you see in the results.
IBM does use OSS in some of its commercial applications. Its use is always cleared with the lawyers first though. Certain licenses must be avoided simply because they are incompatible with selling commercial software. Where the license is permissive we always make sure we follow the rules and I've personally contributed many bug fixes in the OSS code back to the community as required (or even if not required!); these have often been found as the result of formal code inspections (which IBM is effectively funding by paying employees to perform it), peer review, static analysis tools, or general SQA testing.
http://commutingexpert.com/underground-overground-wandering-...