- EphBlog - http://ephblog.com -

New to Blogs?

If so, Stephen O’Grady ’97 has great advice for you.

To be clear, each of you could simply visit each blog you want to read individually – like mine – by visiting the actual webpage. But as you need to check more and more of them, it becomes overwhelming. Much as I might like to think my opinions are insightful, amusing, or at least worth looking at, I can’t reasonably expect everyone I work with or speak with to visit my blog every day, mostly because they have no guarantee that anything’s changed. So just take my word for it, if you’re going to read blogs you need a ‘reader’ or ‘aggregator’. The purpose of these is simply to bring all of the different feeds you might read together in one place. Rather than visit 100 sites, I visit one. Makes it MUCH easier to keep up with everything. I can do 2 hours of research in a half hour.

Coming soon to EphBlog, we hope, will be an aggregator for all Eph Blogs. Try to contain your excitement.

Comments Disabled (Open | Close)

Comments Disabled To "New to Blogs?"

#1 Comment By Stephen O’Grady On November 4, 2004 @ 9:27 am

Have you checked out the Planet aggregrator (http://www.planetplanet.org/), David?

#2 Comment By Eric Smith ’99 On November 5, 2004 @ 3:28 pm

I just spent some time last night and today trying to get that working on our server. It installs and maintains itself using Arch. The problem is that Arch doesn’t like the default diff/diff3 on FreeBSD, so you have to get gdiff/gdiff3, which is no problem – we have that (2.7). Except that they want version 2.8.

I am not root on the server and I think I might have to pay if I want them to go in and update the gdiff/gdiff3 packages.

I am going to try to install it just into my user directory and then point to that for the arch install, which is a bit wonky, but whatever – it should get the job done.

I also tried to do it without Arch just by using a nightly build – I got much further that way, but there are errors thrown. The problem there is that it is a nightly build, so the errors represent code that was checked in and is now failing – so there will be updates over time, but that means I have to keep checking on it.

One of these two paths will eventually pan out and then I will keep us posted if and when it is working.