I'm soured on 1&1 too. At work, we have one domain (our primary one) on Netsol, and the rest of the names on 1&1. Unfortunately, 1&1 bounced an email to us and put us in collections and never bothered to give us a phone call.
We only found this out when we wanted to consolidate all our domains with 1&1. (Of course, I found that our 10-year old domain had the contact info from our old ISP!)
Because of the transfer screwup, we kept it status quo with one name on NS and the others on 1&1. It was such a hassle with 1&1 that I am thinking seriously about consolidation again, only to Netsol instead! (and that is saying much!)
I'd like to see reforms at ICANN, so I don't have to worry about being screwed when some registrar is bought out by someone or when some different set of suits is put in management.
P.S. Direcnic is not the cheapest, but I use them personally and I have no reason to switch. Besides, considering their location, they have disaster preparedness down pat.:)
I heard of people doing that, but that it also kills the bearings. The rollers sit in a plastic box; granted, they're better made than the average junk bearings in a ball mouse, but still...
Re:A warning about Kensington input devices
on
Mouse or Trackball?
·
· Score: 1
I've used trackballs for over 12 years and until recently, I owned Kensingtons. I had the $100 wireless model and it was great when it worked!
Unfortunately, the trackball started getting erratic in the X axis (pointer jumped sideways) and it would get worse despite cleaning it (did I mention that you needed to clean it--and take it apart--almost every day?) and swapping batteries.
The Kensington tech support agreed that the device was bad and sent me a new one. It died a year later. Same cause. I gave up.
I use a Marble Mouse. Wish it had a wheel, wish the ball were larger, but it works. I'm very disappointed in Kensington. Their input device division is almost an afterthought with them.
One thing people forget: All of us have a limit to how much information we can take in at any one time. I'm not a professional tech-support person but I have had to work problems over the phone with computer-owning relatives (complete with screaming kids in the background!) If you've been that person and a disembodied voice over the phone is giving you a series of instructions, the omission of any one of which will hose your system, perhaps you'll see the problem.
And even when one RTFMs, it never seems enough. I am a new Linux user and I have spent the past month reading about Linux, picking a distribution (or two), installing it and RTFM again and again to get all my stuff working.
I'm an experienced computer user (20 years) with a CS degree and I was (and am) still impressed with all the endless minutae one has to know to get Linux running. Sometimes, I think Linux embodies hard work for its own sake, and many (weak-minded) people in the outside world embrace that philosophy.
And "RTFM All The Way" is a good philosophy only if the M's are all perfect and tell you all you need to know. For example, I have two SCSI controllers in my system. Neither of them are set up, though I've low-level drivers for both of them. There is no HOWTO for setting up SCSI, only the SCSI Programming HOWTO.
What I've been able to learn about Linux SCSI comes from little bits and pieces, notably the source code for one of my drivers (an NCR53C400, my scanner's card; an AHA152x is the other.)
Source code? I am a geek and have read source code in various languages for years. But really. That's end-user documentation? Please.
I now know what address to feed the NCR driver, but I still don't know how to take Linux by the hand and say, "See! There's your SCSI controllers! Old, maybe, but they work!"
I suppose if I work on it in my spare time for 10 years, I may get a gold star.
Slashdot Mirror
I'm soured on 1&1 too. At work, we have one domain (our primary one) on Netsol, and the rest of the names on 1&1. Unfortunately, 1&1 bounced an email to us and put us in collections and never bothered to give us a phone call.
:)
We only found this out when we wanted to consolidate all our domains with 1&1. (Of course, I found that our 10-year old domain had the contact info from our old ISP!)
Because of the transfer screwup, we kept it status quo with one name on NS and the others on 1&1. It was such a hassle with 1&1 that I am thinking seriously about consolidation again, only to Netsol instead! (and that is saying much!)
I'd like to see reforms at ICANN, so I don't have to worry about being screwed when some registrar is bought out by someone or when some different set of suits is put in management.
P.S. Direcnic is not the cheapest, but I use them personally and I have no reason to switch. Besides, considering their location, they have disaster preparedness down pat.
I heard of people doing that, but that it also kills the bearings. The rollers sit in a plastic box; granted, they're better made than the average junk bearings in a ball mouse, but still...
I've used trackballs for over 12 years and until recently, I owned Kensingtons. I had the $100 wireless model and it was great when it worked!
Unfortunately, the trackball started getting erratic in the X axis (pointer jumped sideways) and it would get worse despite cleaning it (did I mention that you needed to clean it--and take it apart--almost every day?) and swapping batteries.
The Kensington tech support agreed that the device was bad and sent me a new one. It died a year later. Same cause. I gave up.
I use a Marble Mouse. Wish it had a wheel, wish the ball were larger, but it works. I'm very disappointed in Kensington. Their input device division is almost an afterthought with them.
No one's quoted Gibson yet?! "The street finds its own uses for things"--Neuromancer That's all.
One thing people forget: All of us have a limit to how much information we can take in at any one time. I'm not a professional tech-support person but I have had to work problems over the phone with computer-owning relatives (complete with screaming kids in the background!) If you've been that person and a disembodied voice over the phone is giving you a series of instructions, the omission of any one of which will hose your system, perhaps you'll see the problem.
And even when one RTFMs, it never seems enough. I am a new Linux user and I have spent the past month reading about Linux, picking a distribution (or two), installing it and RTFM again and again to get all my stuff working.
I'm an experienced computer user (20 years) with a CS degree and I was (and am) still impressed with all the endless minutae one has to know to get Linux running. Sometimes, I think Linux embodies hard work for its own sake, and many (weak-minded) people in the outside world embrace that philosophy.
And "RTFM All The Way" is a good philosophy only if the M's are all perfect and tell you all you need to know. For example, I have two SCSI controllers in my system. Neither of them are set up, though I've low-level drivers for both of them. There is no HOWTO for setting up SCSI, only the SCSI Programming HOWTO.
What I've been able to learn about Linux SCSI comes from little bits and pieces, notably the source code for one of my drivers (an NCR53C400, my scanner's card; an AHA152x is the other.)
Source code? I am a geek and have read source code in various languages for years. But really. That's end-user documentation? Please.
I now know what address to feed the NCR driver, but I still don't know how to take Linux by the hand and say, "See! There's your SCSI controllers! Old, maybe, but they work!"
I suppose if I work on it in my spare time for 10 years, I may get a gold star.
Take care,
Dave