From time to time I get notes from people who have asked me to connect to them on LinkedIn and then didn't have their invitations accepted. I need to emphasize right here that it's not because I don't like you, though I wonder sometimes just how useful LinkedIn actually is. I've done a few introductions, but that's about it. I don't have the paid version, and thus most of the system's features aren't available to me.
No, the problem with LinkedIn is purely technical: Most of the time, the damned thing goes into the bushes after I try to respond to an invitation or other communication from another member. The browser spinner spins and spins, but for whatever reason the progress bar gets about three-fourths of the way toward the finish line and just stops there until the connection times out.
I get this behavior from other sites now and then. I've been very interested in the CSS WebApp IStylr, but I have yet to get anywhere with it for the same reason: Click on a control, and the transaction stalls without going to completion. IStylr may simply be on an overloaded server. It's a one-man project and it's not located in the US. LinkedIn has no such excuse, and I see this problem only very rarely on other large sites. Sometimes logging in very very early or very very late seems to help—but if I have to log in at 2 ayem to get it to talk to me, well, ain't gonna happen.
Every so often I go up to LinkedIn to try and work on the stack of invitations and other things I have waiting, and every so often I get a few transactions to go through. It seems like a lousy way to run a cloud computing site, and I wonder if there's something weird about my own system configuration that LinkedIn just doesn't play well with. If you've had this kind of problem with LinkedIn (or if you have any thoughts on where I should look for possible incompatibilities) I would fersure like to hear about it.
