Seconded. I have a DECT 6.0 implementation that lets me bind up to 2 BT smartphones so that incoming calls ring at home. It's still pretty poor tech with an unacceptable lag and adds VOIP-like quality loss, but in theory would mitigate issues for those who leave the phone on Vibrate when it's misplaced.

I'd love it if DECT 7.0 could replace the chiptune ringing. I mean, POTS's bell-less "Ring-Ring" tones are soooo 1990's... add smartphone ringtone cloning to my home base phones, and it will give the industry a feature to hype our stagnant cordless phone industry and sell more units

I didn't make it clear that the cluttered resume conversions I'm talking about here were to actual PDF files.
Also, that in #3 I'd have to keep track of child files in read-only format (PDF) and re-create them for each edit.

If we're going to tout switching to something else (OpenOffice), it is advisable to be aware that we as geeks can more easily endure the PDF steps. non-technical office people currently using office won't stand all these required intermediate steps to their workflow if you offer switching them away from what works perfectly well for them now.

And to answer the GP's original question more directly: I wasn't aware of those problems until they happened. Even WITH PDF despite all my objections, it is a pain to use in practice.

Nothing personal, but it is saddening to see so many replies reiterate the same point when it is a band-aid solution. Here are my why's

1) resume upload sites accept plain txt (garbage), rtf (useless) and doc (native, but no resume site or recruiter takes ODF). Open office formats won't work here without lossy conversion, which proves my point.
2) not everything is a resume, and the problem is how disturbing problems can be for your livelihood* in an important context. The real point is that the PDF route removes the ability to freely share. Here that means having the recipient edit it, feed it back to me in an office setting or SHARE it with others+++. And sharing is the whole point of using Office productivity software, is it not?
3) It should be clear that pdf then becomes a cumbersome intermediate step. I already have multiple read-write revisions (binary, so cvs won't quite cut it). Adding multiple resumes implies keeping track of multiple read-only revisions of my document.

* Conversion engines are not perfect. No conversion process is. My cluttered resumes occasionally got broken into two pages because of the last line of text. Re-formatting to blindly guess what the engine wants requires the same QA we're trying to defeat.
+++ (pdf aint freely editable or viewable without plugins and non-native programs as of Windows 7)

Windows XP End of Life in 10.033424102237653 months.
Courtesy of this bookmarklet seen on slashdot years ago:

javascript:var%20eol=new%20Date(0);eol.setDate(8);eol.setMonth(3);eol.setYear(2014);var%20now=new%20Date();var%20diff=eol.getTime()-now.getTime();alert("Windows%20XP%20End%20of%20Life%20in%20%20"+(diff/1000/60/60/24/30)+"%20months.");

Cannot stress this enough. We're savvy people, but not immune to conversion issues between the two. When are they the worst? When sending out a resume that we cannot preview in the real Office. Why? Office requires Windows, or a Windows-only viewer*. You definitely won't lose your current job over a misformatted word file, but when looking for one, some interviews will not happen due to the glitches that were invisible to us.

Some slashdotters on principle DO NOT touch Windows. Others have only a Mac* and/or do not pirate software. You'd need Wine and a copy of office ANYWAY. What would then be the point of using Libreoffice if you're cross-editing on the same PC?

The littlest cross-edit can trigger that hidden "alien" look in real Office, and when I used to be out of a job, my weekly revisions would have become someone's pain to preview, especially with several flavors of the resume I maintained.

* MS lacks Mac viewers and shows just a lowsy link to a 3rd party utility site for those who can't pay for the real thing.

You just had to remind me of my annoying 4-tab max in the stock Android browser for Froyo. The Phone is only two years old, and I doubt it's a max based on free ram. Dolphin and Opera certainly don't stop at 4. Browsing weather + slashdot + wikipedia eats 3 tabs and ensures I must go closing tabs pretty quickly when I want to actually visit a site.

Pressing the hardware "escape" button on the phone triggers back-to-previous-page OR exit-tab-AND-return-to-shell depending on your browsing session. Actual deterministic closing happens through a preview-tab picker GUI of abysmal design. It's meant to switch windows rather than closing, and you must hit the lilliputian x on the top right. 80% of the time you inadvertently return to the wrong tab and have to start over. Why couldn't they add a "Close" option via long-press? That's Froyo, btw, so it's ~1/5 android phones still out there, AND there are no over the air upgrades away from that. I don't like apple's hold on your hardware, but IOS will cascade to everyone and the 8-tab limit, though it's not as painful as Froyo's 4 tab one.

About the past: the ~30 minute interview window is gone and the interviewers have moved on to other candidates. They have no personal interest and don't care what proof can be submitted. Nothing OP can do will fix this short of time-travelling to prevent the name removal from cascading to the code that later ended at the recruiter's hands.

About future interviews (as hard as they are in this economy): Wayback machine proof won't fly as defense in the middle of an interview*. You'd have to stop the flow completely and pull up devices. Unfortunately interviewees are assumed to be lying in their resumes anyway, to "get even" with an already unfair pool of other interviewees. As soon as recruiters find a blotch that requires much explaining, defenses mostly look like further lies because it is hard to prove things that aren't tangible, and lots of pressure drive candidates in today's job market.

* think about it. The interviewer already did the "exposing" research at their leisure and drew conclusions against the candidate, like a cop who already has DNA evidence that will put a rapist behind bars. They know code is fluid, and also know a candidate might be the one trying to steal the credit... How can the "truth" be determined if code isn't signed in blood or DNA-traced? Offering evidence to counter the employer's research without the same advante of time means convincing them on-the-fly during the interview, and without some kind of code DNA / paternity test, they could posit that the wayback machine could have code expressly poisoned by this candidate years in advance for this very purpose. I'm more concerned with how on earth the employer so freely grabbed the code, given that you don't normally leave code online unless it's in an open source repo... and then, you're usually not paid for it like the OP.

I assume most of us know about Nightly being one of the dev branches. I am a nightly user (despite various posts more or less swearing off firefox since 2010).
This UI version of nightly is news to me: It's so bleeding edge that the DL still had version #24 in the filename when I went to check. What intrigued me is why that is compiled to only EXE (installer has bigger chance of overwriting your current live EXE, unless they now use C:\Program Files\...\Nightly) and no zip file.

Every time I go on a new computer, I just download a ZIP file and expand. Before running that EXE, I make sure to back up my profile and it and the current FF nightly with version numbers, should I want to go back.

About allowing both sides to exist, I understand there is a need for diversity but it is generally only appreciated by the geek community... and even here, people always secretly play favorites. Given that anything that can go wrong will do so, we end up with garbage decisions being incorporated by both sides little by little. Being broad here: think loss of 4:3 screens/resolution, crappy A/V software now coming to mobile OSs, App stores now unavoidable on windows and mac desktops, mobile GUIs taking over PCs to the point your old program is suddenly cryptic and useless (think MSN Messenger shoving us to the Metro only Skype on Windows 8 a month ago), and fans not going away... let me add bufferbloat delays now at your cable box and TV, and annoying LED lights from everything in your bedroom at 4am. So I dont mean killing PCs or tablets is warranted, but pollution potential is there. Did I mention the idea of freemium Apps could not exist without the former learning exp of shareware and nagware of old? It is mainstream now and will not go away, creating a world where free desktop applications will grow smaller each year

Annoyingly, it's PAINFULLY similar with web searches that lead you to the android app store...

I manage several android devices but only one has my google account. To download additional copies of free App X through my PC, they won't link me to the file to redistribute at my leisure. Naaah! the site asks for my google ID. This gives concrete knowledge to google to examine my ID's* and devices as a cluster. Success here means that they push the App UP thru the cloud rather than down to me. I must root the phone to extract the APK app from the invisible /system/ folder for my other devices AFAIK. After a few more hoops are jumped to side-load the file into other phones.

Contrast that to how easy it is to download .deb or .rpm packages from official AND hobbyist repositories for stuff like mp3 encoding / decoding... even when a distro fears pressures from US lawyers. In comparison, Android market feels oppressive when google chooses where you can use their downloads. I failed to mention earlier that google can reject your download for whatever reason** after they know your google ID.

* Your other google identities AND those of relatives who never connected to your Wifi thanks to separate 3G/4G plans
** For instance, those of us with ancient [version N] phones when your App is only available for [N+1]. Google won't let us bear the "risks" . Their browser hides devices for which the app is officially unsupported. Today's publishers and distributors inspect us, refuse our rights, and pull downloads after the fact.

Even for the home power user, it's a pain if you are forced to buy brick and mortar and on a deadline because the family needs a new machine. Old-style PCI has become a pain to find on cheap towers.

I had to shelf a bunch of cards when our old ~2003 machine died 2 years ago:

• an old $120 PCI video card (the cheapest replacement costs ~$60 these days)
• a Soundblaster card (I miss when they used to have MIDI and joypad ports)
• a potentially secondary NIC that would have helped me play around with work multi-nic setups and software firewalls
• an adapter card for 3 Firewire inputs.
• a modem card (didn't get more than a couple uses after we went to DSL, but can save you a dollar and a trip to the Western Union when your potential new boss requires documents faxed before you're hired)

An old system I used to maintain had 2 native USB port and about 4 more via a PCI card I added. I think my switch from the hand-me down ISA to my self-bought PCI setup had only 1 card that got dumped. We just have so many more gadgets today.

A few cents or dollars per NEW module kills timely standard adoption. We're talking about ISPs, so let's use a well-known evolutionary example with WIFI routers available to users even outside the ISP chain:

First, no wifi at all,
then default / empty passwords all neighbors could steal,
then WEP only because WPA wasn't supported,
then no WPA2...
then (or mixed in with the above):
no support for G,
then no support for N
finally, "support" for N on just 130mbps, but not multiples of it. The unwritten word is also SINGLE band (2.4Ghz)

That is what I remember from a ton of different routers I either got from ISPs, owned, gave away or just troubleshooted. The great fragmentation tells you that it won't be an easy problem to solve. I mean, just check your Wifi now and see how many of the ancient no-nos you can still see from neighbors around you who PAID for their routers --I don't even want to know what they have to settle for at the Modem level.

Providing an upgraded router may not be the same as just "going" up to an IPv6-enabled router. Supply chains take forever (5 years) to provide today's optional features.

If you need more proof that a 2 year cycle for upgrades means nothing, just look at how few top of the line smartphones *refreshed yearly* support 5Ghz bands. Even if you paid through the nose to correct that, you still must leave the 2.4 Ghz band open because your pricy game console [refreshed every 5 years] isn't that lucky or your visitors' gadgets are behind. It's not a pretty picture. Give it 10 or 15 more years

Interestingly, your post made me think that google glasses might be a foot in the door techwise for something 100 times dorkier and less public: Virtual Reality Googles.

Those guys playing Temple Run today don't yet realize some augmented reality version may be coming to glasses near them

The 3D is cheap
The immersive stereo view is built into the nature of glasses
The GPS and compasses are already in all smartphones and there's several apps that act like smart HUDs.
It's portable and more natural than a headset, and if you [Google] builds it, [someone] will come with implementations.

I just don't want to see people looking like druggies when they extend their hands to touch things that are floating in their HUD. The eerie effect of talking into thin air left Behind by bluetooth is already sad enough

I find it extremely creepy that while they responded badly to this, he had exactly what we are afraid of: good quality pictures / video of your environment at all times. I don't agree with the violence. It's just going to be harder to paint ourselves into corners to avoid connecting with everyone else's field of [perfectly recorded] vision. If Glass takes off, it will be like walking around trying not to step on anyone's shadow: impossible.
Here's a stray thought: What will having so much visual info do to people's social networking feeds?

Did you forget "reading slashdot clearly at *any* zoom level?" ;)