17 May 2002
Fri, 17 May 2002
Joe Gregorio - new .net news aggregator called Aggie
Joe Gregorio says:
Announcing Aggie. Release Candidate 1 of Aggie, my news aggregator application is available for download here. Aggie is a .Net based application for reading RSS files, similar to AmphetaDesk or the news aggreator in Radio. Why should you try out Aggie?
Restrictions:
- It is OSI Certified Open Source Software.
- It is a native .Net application.
- It can handle RDF and RSS file versions 0.91, 0.92, 0.93 and 1.0.
- If you are a Radio user you can use Aggie to read your news when you are away from your main computer. Radio publishes your list of news sites into a file called
mySubscriptions.opmlthat is uploaded to your gems directory. Set the channel list tohttp://radio.weblogs.com/NNNNNN/gems/mySubscriptions.opml, where NNNNNNN is your Radio site number.
- If you are an AmphetaDesk user you can try out Aggie easily. It can read and write the AmphetaDesk channels list. You won't need to manually transfer your list of news sites to Aggie. Just set Aggie's channel list to point at the file
myChannels.opmllocated in the data subdirectory where AmphetaDesk is installed.
- Aggie is multi-threaded, making more efficient use of your internet connection and getting the news to you faster.
- Aggie is small: Only a 30K download.
- No embebbed web server. No configuration through web pages. Aggie is a native windowing .Net application, the web browser is just used to view the news.
- Continuous feedback. As Aggie pulls in the news it gives continuous updates on it's progress, informing you of which sites it has visited, which ones are still to be pulled, which sites timed out, and which sites are generating invalid XML.
Installation directions:
- Aggie requires Mozilla 1.0, Netscape Navigator 6.2, or Internet Explorer 6.0. Sorry but Aggie does not currently work with Opera. (This will be fixed in a future release.)
- Since it is a native .Net application you must have the latest version of the Microsoft .Net Framework including the latest service pack installed.
- Download the ZIP file.
- Extract all the files into a directory, something like "C:\Aggie" would make sense.
- Double click on Aggie.exe.
Pleese download and enjoy! Feedback and bug reports are always welcome. [BitWorking]
I'll have to try it. Can't wait. Only thing I need to find out is what .net service pack Joe's referring to?
Posted at: 06:35 | permalink
Pittsburgh goes wireless
Companies plan pilot wireless network Downtown. Pittsburgh Business Journal May 16 2002 5:57PM ET [Moreover - Pittsburgh news]
Posted at: 00:40 | permalink
Need help debugging XML-RPC between bloglet and radio using blogger API
I'm reprinting this post from Monsur at bloglet.com hoping that somebody with expertise in Radio's XML-RPC implementation of the blogger API can help debug it. I'd like to see it work so I can start using the bloglet service with my radio blog. Thanks!
Well, Bloglet's integration with Radio is experiencing some difficulties. The integration works fine; however, some users are having difficulty setting up their XML-RPC server. The documentation is a bit sparse on this topic. I've been playing around with Radio, and here are some tips I've came up with. But at the same time I have a lot of questions, perhaps a kind Radio user out there could answer them, or let me know where to find answers to them:
- I think the XML-RPC server is the same server as your site. If you are hosting radio off your machine, you can find your server here.
- I'm a bit unclear whether XML-RPC works if you upstream your site to another server via FTP. Unless the other server is running Radio, I don't think this is possible. Anyone have any suggestions on how to implement XML-RPC in such a situation?
- There are two site settings you should have checked. On the XML-RPC and SOAP in Radio page, check the first box to enable XML-RPC. If you want to limit XML-RPC only to Bloglet's servers, click the second box, and use 208.215.141.102 as the IP address. On the Blogger API in Radio page, make sure the check box is clicked.
- Some users are reporting luck with setting their weblog id to "home". I thought Radio's XML-RPC server ignored the weblog id field, but I could be wrong. If you know you have your server set up correctly and it still doesn't work, you might want to try this.
Those are the only tips I can find now. If you run a Radio Blog with XML-RPC enabled, let me know how you got it working, and if I'm missing something. In the meantime, I'll let you know if I discover anything.
I told Monsur that with respect to his bullet points:
-
Mine is responding on http://hostname:5335/RPC2. -
I have this configuration and XML-RPC is working. -
I have these checked. -
The reason that I set blogid to home is that the XML-RPC server told me to do that and I've gotten further with that setting than any other.
Mine is dying with a parse error on the return XML from the XML-RPC call. It's gotten past the auth at this point so I figure there's either a bug in the return XML or a bug in bloglet's parse of that XML. Any ideas?
Posted at: 00:20 | permalink
