TCP.IM: Here’s the beta.
Month: August 2002
-
-
10 Tips on Writing the Living Web: A piece from A List Apart that looks good, I’ll have to do more than skim it when I get back from vacation.
-
Wow! Dave points out some new functionality for Radio and Frontier:
Heads-up, some time in the next 24 hours we’re going to release tcp.im, which allows Radio and Frontier to be an instant messaging client or server (either can be either).
-
Yep. I’m in San Louis Obisbo, or somewhere pretty near it. LA was fun, now I’m a little further up the coast. I’ll be making a trip to Fry’s, the geek Mecca, sometime before I leave.
-
Well, here I am in Beverly Hills blogging by
email on a slow and painful set top box webtv
thing. Real updates will have to wait until I can
sit in front of a real computer. -
And we’re off!
-
Well I’m off to LAX via BWI and PHX tomorrow morning. A few things I should read when I get back: Radio for K-Loggers, Radio tweaks, and Enabling Web Services. More will follow when I find the internet again.
-
Putty is a free Win32 Telnet/SSH GUI client.
I also use Putty all the time, it’s great stuff!
-
Ack! I’m falling behind in the RSS feeds and I haven’t even left yet!
-
Ha! I got her back up and running. I booted from a win2k CD and did a restore. I’m sure it has fuxored my registry, because I’m constantly being asked to install stuff. A clean install is coming, but for now it should be able to sit idle and serve me from across the country.
-
I guess that’s karma for you. My Win2k box is having issues and will only boot into safe mode. My weblog may not update for a week after all. I’ll do my best to get her back online before I leave for CA.
-
California
Good morning! I’m going to California tomorrow for a week, and I leave tomorrow. I have several options open for blogging remotely, though it hinges on a win2k box staying up (It has UPS so it should be okay) and my cable connection to not crap out. It’s the cable connection that I’m more worried about. As long as my server stays up, I’ll be blogging by email and blogging remotely.
I’m running around today getting ready for the trip, but I’m sure I’ll hop online and try to keep caught up on the RSS feeds. I’m told that the hotel that we’re staying in has WebTV, but I’m not sure a) if this is correct and b) if it won’t cost an arm and a leg. If it’ll run me $10-20, I’ll do it. Any more and you can fuggedaboutit.
-
USA Today: A riveting piece about 9/11 from the eyes of the FAA and air traffic controllers. It’s intense reading.
-
Remotely Blogging with Radio
Remotely Blogging with Radio
I remember reading somewhere awhile back that a user of Radio was complaining about only being able to blog from one machine. I didn’t quite understand it, as I have blogged from several machines on my home network and several different machines at work. Granted, I don’t have a copy of Radio running on each machine, but it’s easy enough.
How do I do it? I have a server at home that runs Windows 2000. It acts as a fileserver for the local network and does all kinds of other cool stuff. It’s a PII450, nothing special anymore, though it was quite a beast when it was new. This server also runs radio. Did I mention that I also have a cablemodem connection to the internet? I think that helps.
You see, I set up port forwarding on my router/gateway box to forward the port I use for Radio (the default is 5335) to the server running radio. The great thing about Radio is that because it is essentially a web application with a small backend program that runs on the host computer, you can access most of it from any browser. Of course, that assumes that you enable remote access, which I have done.
This means that I can blog from my main box, at my workstation at work, or anywhere on the road, as long as my cable connection doesn’t flake out and the box is on. Of course, you can’t do everything on machines that aren’t running Radio. The one pet peeve I have with this setup is that I can’t easily save files to my local www folder. This means that if I stumble across a cool macro while at work or on the road, I need to remember to download it to Radio machine the next time I am home. The other thing that bugs me is that I can’t edit OPML files on the road. A quick search about a month ago didn’t reveal any small footprint applications that I could use at work or elsewhere that would allow me to edit or save OPML files. Of course, even if I could edit them, I would still not be able to save them to my www folder so that they are upstreamed to the internet…
As long as you can deal with the quirks, blogging with radio on several machines is quite easy. It comes naturally to me, and given the few times I’ve read that people want to blog from more than one machine, I thought I should let the world know. Of course this doesn’t solve everyone’s problems: this solution is not an option for 56k users or people who don’t have (at least one) machine running all day every day. But it does work for the geek that many Radio webloggers are. I continue to think that the $40 I paid for Radio is some of the best money I’ve ever spent. Grouping all of my news into one place via RSS feeds has not only made my web surfing more efficient, but I have expanded my reading list to include dozens of new sources that I wouldn’t have found out about otherwise.
-
OpenBSD Journal: OpenBSD Sparc goes ELF from a.out. It may sound trivial, but I view it as A Good Thing.
-
AMI BIOS or not? Best. Hot or Not. Parody. Evar! Seriously though, it will only make the truly hardcore geek laugh, but it’s funny. [via the toolbox]
-
US Airways Files Chapter 11: Whew, I’m glad I’m flying Southwest. This is pretty big. No huge scandal, no accounting irregularities, just vanilla post-9/11 economic soup.