Nuggety Botlings
Go, little botlings, go! I've removed the bar to indexing my LJ. I want the little critters to flow, flow on, my lovelies.
Sometime today I need to find some kind of way to do file transfer to swift. It's FTP has been shut off because FTP isn't, or can't be made to be, secure enough. I'll eventually manage, but I'm worried about POP now. Rumor has it that POP will be shut off as well, which I find baffling because POP can be used with SSL.
If POP goes, I need a new box. That's just the way of it. I'm in the middle of four businesses right now that seriously need POP email. For my personal life, sure, I could limp around without it. I already check half my personal mail with Pine and am cool with it, for the most part, but it makes lots of back and forth business correspondence a nuggety pain in the ass.
Then again, it's starting to look like I'll need a separate box anyway, for another development. I can do what I have to do on a VPS account (I need to run a specialized compilation of Apache) but there's a colo offer that really shouldn't be squandered. We'll see.
Oh, botlings, be sure to go over to MYG's business site and help with that lovely ranking so he can get better exposure for his embedded web server thinglet. The Google AdWords I did seem to be working, according to the hit report, but listing relevance would be even better. Some people totally ignore the relevance ads.
Actually, I guess the message didn't get relayed quite correctly. I would leave POP (and FTP) on and consider moving us over to a VPN-type architecture.
Where the non co-located networks are trusted over a secure tunnel to swift. So it would actually be an improvement. POP will probably stay though.
POP over SSL would be just dandy for me.
But it doesn't seem to matter. I don't know if you've seen it, but lots of people have. Swift, or rather, swift's ISP Is having *severe* network problems. One user of mine (who uses POP) couldn't contact the machine at all for hours. He could ping, but not establish a TCP connection to port 110.
The current theory is that there is an IP address or routing problem that is sometimes sending our traffic to some other box. Be weary. But every customer of that ISP is complaining. And I may very well just pay for a shared hosting account and move my corporate website on to that.
Swift does not seem reliable enough anymore.
MYG
- Saturday, February 07, 2004 at 00:57:20 (EST)
|
