927 karma · joined March 31, 2010
if the app key is compromised, the key is revoked and no twitter access. if you extract the twitter oauth key from a competitor's desktop/android/iphone/etc app and post it on the internet, twitter will kill your competitors twitter application until they distribute a new key. rinse + repeat.
i wonder if twitter will revoke their own app key.
p.s., those side-sticking things are really annoying.
inotify is not guaranteed to see every file system access. in fact, it often misses them when the file system is busy because there is an upper bound upon the number of inotify events that can be queued, set in /proc/sys/fs/inotify/max_queued_events.
i.e., you could get data loss using this mechanism alone. you need to also run rsync every so often, i think.
the lsyncd guys are aware of this: http://code.google.com/p/lsyncd/
(maybe this is how dropbox works under linux too, if so it presumably has the same problem..)
with 4 prisoners the probability of success is about 0.37, which is better than chance. (the probability of success turns out to be one minus the difference of two harmonic numbers.)
it's hard to give a hint without giving the answer. the best i can do is that it has to do with the structure of cycles in permutations.
see section "Materials and methods" subsection "Baseline Alcohol consumption" in the linked paper.
in particular, they are looking whether some 55-65 year olds died the next 20 years, women were underrepresented in their sample (just 37%) who tend to be lighter drinkers anyhow [citation needed]. participants were select by having been at a health care facility in the last 3 years. the socioeconomic factors they took into account where those at the start ("at baseline"). i.e., who knows what changed in the past or future, or why they were in a health care center, etc. was there an observation effect? who knows.
the yahoo article doesn't seem to represent this very well. hype hype hype
The following special filenames may be used with the |&
co-process operator for creating TCP/IP network connections.
/inet/tcp/lport/rhost/rport File for TCP/IP connection
on local port lport to remote host rhost on remote port
rport. Use a port of 0 to have the system pick a port.increases since then seems to be 5-7% per year.
good guess!
i very much enjoy a book with the same title but by burton:
http://www.mcgraw-hill.co.uk/html/0071244255.html
it contains a lot more of number theory and a little cryptography too.
standard input/output/error are not necessarily character devices (as stated in the article). they can be anything (sockets, files, etc).
http://en.wikipedia.org/wiki/Down_and_Out_in_Paris_and_Londo...
SO(3) (the group of rotations) is not discrete in any sense i can think of.
some groups have a discrete topology, but not all by any means... are you referring to cayley's theorem?
$ objdump -D /lib/libc.so.6 | grep 'int[[:space:]]*$0x80' | wc -l
447
what were you thinking they used instead? sysenter? iirc, this turns out to be slower than "int $0x80."2. linux duplicates the system call dispatch table for each architecture. check it out:
http://lxr.linux.no/linux+v2.6.35/arch/x86/ia32/ia32entry.S#...
vs
http://lxr.linux.no/linux+v2.6.35/arch/avr32/kernel/syscall_...
whereas NetBSD has no such duplication. in fact, one complaint about the linux kernel is that it has too much per-architecture code.
3. who uses minix? the linux kernel is actually not too bad. ctags is your friend. i learnt on linux+netbsd, it's not really as bad as people make out.
other kernels (like NetBSD) where designed with being portable across architectures in mind and so have much cleaner code paths (typically just one system call table and the bare minimum arch specific code to link it all together).
minix is okay but it's not really going to give you a grip on a real work kernel. "design and implementation of 4.4BSD-lite" is a really good book for this: most BSDs are very similar to this design still in a lot of ways, and many of the ideas described (e.g., VFS) are also used in linux.
this (Infer) looks like it's for a different kind of inference: classification (essentially linear, but with a few bells and whistles).
(not graphical models right now; probabilities.clj is very much lacking.)
* http://en.wikipedia.org/wiki/Trusted_Platform_Module
* http://www.intel.com/technology/anti-theft/
* http://en.wikipedia.org/wiki/NX_bit
and so on, of which Intel is currently involved with lots.
Security is what a desktop processor spends a lot of it's time doing: making sure programs are isolated from one another and the kernel whilst still executing code.
Intel has a large interest in mobile, virtualisation and network arenas; this isn't really as surprising as you make out.
$(document).ready() can be a bit of a sledgehammer in terms of latency.
correction to tip #4: iPhone's append "Sent from my iPhone" not "Sent from iPhone". i'd notice the missing "my". "Sent from my mobile." is just fine and probably a better approach.
it's not just it's not known, but also it has an uncommon composition.
for example, you may not know what the solution to abapi_al is exactly, but reasoning phoenetically should get it quickly.
you wrote:
Alas, the Haystack web site has zero technical details.
the causata web site appears to be equally placed.
i call hypocrisy. jgrahamc is involved with causata: check out their website.
count the number of times you read:
"This has to change. Stay tuned for more details."
where are the products? what have they shipped?
http://pypi.python.org/pypi/greenlet
at least in this benchmark, greenlets seem to do a very good job: http://nichol.as/benchmark-of-python-web-servers