My Creative Zen Xtra (2003) is still going strong. 30GB harddisk (also available in 60 GB), large blue-backlit LCD, excellent user interface, IMHO. Replacable battery, however the Li-ion cell it came with is still doing what it's supposed to do. Built like a brick, however the front aluminium cover which gives access to the battery compartment hasn't got the sturdiest of closing mechanisms. Not a 'scroll wheel' of course because that was patented technology at that time. But side buttons and a jog wheel for volume and selection works for me.
I did install the 2.10.03 'plays for sure' firmware to make it WMP 10 compatible. Apparently that didn't always work out well for it has a reputation as "Zen killer". But I never had any problems with it...

I also still have (but don't use) my Creative D.A.P. Jukebox (Disc-man sized, blue/silver, 6GB HDD, pre-ipod era). Fond memories... but 6 GB is just too small.

Here in the Netherlands, years is stretching it a bit. But -a- year should be easily doable. This year I know of one occasion I had to re-set my alarm clock due to a power outage not of my making (as a hobby electronic / radio amateur I do trigger the automatic circuit breakers sometimes). Regional power outages lasting longer than a couple of minutes make the national 8 o'clock news as major news items - they are that rare but they do happen a few times each year.
Last time we had a major power outage in a region near me (a few larger villages had no power for a couple of days somewhere in december 2007) was when an Apache helicopter flew into a set of HVAC lines (50KV, I think). It was on one of the very few places in our power grid there is no loop in the network, which is why it took a few days to restore the power for those villages, instead of seconds.
The thing I noticed when the accident happened (it was a Wednesday evening and already dark) were the lights flickering for a couple of seconds and I made a remark to my dad about something big probably shorting out. My dad, now retired, worked for KEMA at that time which, amongst other things, tests high voltage equipment for power grids, which might explain my interest in the subject as well. Later that evening, when I got home I heard about the helicopter accident on the re-run of the national 10 o'clock news.
The helicopter made an emergency landing and luckily nobody was harmed.

This part of the text is where you should start then (By the way, I am certainly not a physician, just interested, as you are):

The AB group is the earliest discovered (?) blood group system. The Rh group another (that +/- thing you were taught is an extreme simplification of it and points only to one antigen from the complete 60-odd set of Rh antigens). And there are 33 more blood group systems, apparently. I knew there was more than AB and Rh but I didn't know there were that many myself.

Start on some Wikipedia pages first. A lot of information is pretty accessible there. For example: http://en.wikipedia.org/wiki/Human_blood_group_systems
Then, if you want to know even more, start following the references away from Wikipedia and try to get articles about the subject from medical literature.

Implicit question answered here. For the tl;dr & tl;dt folk: Use a vacuum cleaner.

I wrote an app almost 10 years ago . Just looked through the code a bit. It says "Build with PRC-Tools 2.0 and Palm OS SDK 4.0 or better". Written all in C++. Most of my work I did in a simple text editor. Not in an IDE. And I used makefiles I wrote myself and a command-line to compile the lot. I remember compiling for the m68k mostly because that would cover all our potential customers. But there was already ARM support in the works... until we just dropped it. We had too few sales to warrant further development. Not that our version for WinCE PDAs was doing any better, by the way. A couple of years later the first IPhone was released. And for that platform we still develop and sell.

There was partial support for C++ in 'recent' versions of PRC tools... classes and use of new and delete, and if you really wanted them, exceptions and RTTI. But no STL, streams... I wrote a file io and string class to keep the back-end code compatible (we had a significant chunk of back-end code already written in C/C++ and used it in apps for many platforms).
Also you had to manually segment your code for Palm OS because there was a fixed code segment size (my app used five code segments and I had to specify for each function in which code ). Long function calls were used to make the segments interact and you had to keep in mind to use them as little as possible because, although the compiler did the work of adding those long function calls for you, they still incurred a performance hit.
I finally retired my company Palm M515 two years ago when I got a second hand HTC HD2 from a friend (and promptly updated it with CyanogenMod). I managed to save most of my (calender, notes, contacts) data and it's now part of the Google cloud...

It was fun to program for that platform, I learned a lot from it but I would say, in this day and age, it's utterly useless to start a new project for it. I would recommend Android over iOS, if you just want to make a mobile app. Although Apple's tools (XCode) are better IMHO, you can do a lot more with Android and the apps you make for them before you have to spend money on it (AFAIK the only thing Google asks is a $25 one-time fee if you want to publish on the play store and you can always side-load for 'homebrew'). And you can develop and compile an Android app on a variety of computer hard- and software platforms, while a recent Apple (i)Mac(book/mini) is required to make iOS apps.

If you're really adamant to create a PalmOS app, get yourself PRC-tools, cygwin and a 'recent' PalmOS SDK and you might actually manage to get a working app. Time-stamps of my versions are of april 2004 so I do not have the final versions... Also, the PalmOS 4 emulator and/or PalmOS 5 simulator, with roms and of course the full Palm desktop suite installed on your machine so you can make backups and install .PRC's on your PDA. Did I forget anything else (except for the fact some of these are a bit difficult to find on the 'net).
Ow, yes, there is a PalmOS developer suite for PalmOS 5 and 6, using Eclipse and a lot of integrated goodies. A 250MB sized beastie... but I haven't got the faintest clue where to get it nowadays.

Even if you DNRTFA....
Apparently ... depends... in this form, yes... 2* yes, sort of...

How did you think Sandstone and Shale are created... or Obsidian? What do you think Amber is? Just because it is ground up other stuff with nice fossils in it (Sandstone/shale), a kind of glass (Obsidian) or has a non-geological origin (tree resin in case of Amber) doesn't mean it can't become rock.

Keyboard hijack should not be a problem. Remote login on the machine you intend to analyse the foreign hardware device on... Do not use a GUI that defaults keyboard input to itself, do not use one of the main TTYs , so a keyboard hack which cycles through the available '[ctrl]F1-7' targeting the default Linux virtual terminals available can't find any one logged on. Use an OS that doesn't auto-mount (which eliminates several Linux distro's, but at least you can make them behave, if you want to) or, even worse auto-executes at mount. Analyse the hardware make-up of the device at leisure before you manually mount the partitions yourself and take a look at the software. Did I miss something? Please tell :) Always happy to learn.

What's more of a show stopper is the nasty rumour about direct memory access bugs in USB chipsets which might actually give malign devices an attack vector that way. Don't know what's true about that one 'though. The last time I saw it mentioned, was about that security researcher that claimed sensitive information (and even attack code updates) from a trojan spread through his air-gapped machines using modulated data on sound waves emitted from one laptop's speakers to another one's microphone.

Actually... if the object was made by metal, that would be the 'only' way. The only objects I bothered to physically label are my laptops and they aren't of the 'ultra expensive' kind... so I use a soldering iron for that.

For hand-held digital devices (a PDA in the not too distant past, now a smartphone), I've only put a message of ownership on the lock screen.

My experience is, in general, Asus makes decent featurefull router firmwares. However, I like tinkering and moar ;) options so my RT-AC68U soon got DD-WRT on it and some custom scripts. Multiple WLan segments with their own SSID so I have a public and private channel, multiple VLAN segments, one for DMZ, one for local lan, one for 'experiments'. Everything with a proper IPTables script which runs at boot... Custom DNS lookup table. It's just fun to hack router.

A clunky interface doesn't matter to me, as long as it has the options I need. At the time I flashed my router I couldn't find a Tomato firmware for it, else I sure would have given it a spin...

What I do miss with the RT-AC68U is '3rd party' binaries support. It's a shame Optware, or something similar, doesn't work yet on the AC-68U. I did try something with a crosscompiler but I have not yet had good results. I'd really want to run bind and postfix on it... amongst other things.

Well ... maybe they also use some heat/radiation methods to kill bacteria?
The article mentions using iron filings to remove the oxygen, which makes me suspect they use an air tight container. So, if you manage to not have any bacteria in there, in the first place, and that air tight container is any good, I don't suspect anything living to take a bite from that slice, except when somebody actually intends to do so.

That's where this comes in. Call it a trackball for your feet (although it's actually concave) with added thigh-strap.
Then there's also projects working on representation of your body in the 3d world, including relative position of your various body parts, like Stem. Combine these three and everything first-person should be quite immersive without you falling through a window, tripping over garden tiles or being run over by the school bus. As long as you're okay with poor feedback when you bump into something virtual or slice through your favourite adversary with a katana of your choice. They didn't fix that part to satisfaction yet.
With Oculus Rift alone, your immersion will only be adequate for vehicle simulation, racing games and maybe some top-down strategy.

(3) If the person who has an abundance of it is unwilling to provide* at any reasonable price, yes.
(4) If the food is purposely made** to spoil fast, sometimes even before you were able to take a bite from it.
(5) If you have to pay the producer of your piece of food over and over again*** in full, if you want it to last or if you want to eat it in another venue than you originally intended.

(* publishers that let works go 'out of print' but still prosecute 'alternative means of distribution'. It is called artificial scarcity and is something very common when dealing with monopolies.)
(** certain DRM mechanisms come to mind.)
(*** LP, Cassette, CD. Celluloid film, Video cassette, Laser disk, DVD, Blu-ray. Digital distribution with various restrictions. Multiple devices for playback, or the inability to be able to.)

Seems to be ok now? ... However, the second link is not clickable. HTML source says:

Over 10 million viewers worldwide have watched <a>The Ben Heck Show</a>

Maybe this link is good enough instead?

Infrared currently is used as a point-to-point connection where (most of the time) there has to be a clear (as in: only air) path from one node to the other. It's mostly used as a device-to-device type of connection, not as a network of devices.

Li-Fi should integrate into the lighting plan of rooms, should be capable of operation using reflections instead of direct point-to-point. Of course, reflections and re-transmissions probably cause signal degradation if no filter capability exists so the software protocols should be able to compensate or, if unable, scale back to lower network speeds. The same for 'foreign' light sources (the sun included). Individual light points should act as repeaters with one point in a room connected to the 'regular' network being enough to provide the entire room (however large it may be) with full network access. At least, those are the 'promises' I heard about Li-Fi.

And, indeed, being unable to penetrate walls can be an advantage.

Argh and then I forgot to post as a user. Sorry slashdotters.