In case you hadn't figured it out yet

[grahams]

I have stopped maintaining AliveJournal. As I mentioned in a comment to an earlier post, Be doesn't boot on either of my current machines, and I simply don't have the drive to tinker enough to make it happen. While it's disappointing, after pouring as much effort as I did into BeNews, BUGGER, AliveJournal, etc, I simply can't shake the feeling

Comments

[bride]

That's too bad... =P Well, I took a copy of the source, in case I feel like playing. It'll probably fall off my radar too, but it would be cool if ALiveJournal worked with the new Client Identification protocol (whenever _that_ happens)...

Re: OpenBeOS

[rennegadde]

Every OS HAS an LJ client : a web browser. What's this obsession with taking the web browser out of this web community? I just don't get it.

Re: OpenBeOS

[grahams]

A laptop can play mp3's, but most people would prefer to carry around an iPod when they are walking around the city.

It's a case of specialized tools, often they are easier to use and more powerful, and this is just one of those cases. Things like friends group management is much simpler to use and faster with a standalone client.

If someone was actually developing AliveJournal currently you'd see lots of features that would be impossible without a "real" programming language, but since I gave up the ghost on LJ and nobody else picked up the torch, it is stale.

Re: OpenBeOS

[rennegadde]

Thank you for the reply. Your analogy does make sense, though it isn't the best comparison. Maybe a better way to say it would be that some people climb a tree and grab a fruit to eat, and others use a tool that does the reaching for them or buy from a market.
Perhaps I will investigate the options I have for a client, but I have a feeling they will be designed for working on my own journal/account, and not for viewing others. Since I would still use the site for other's journals, I would probably still use the site for my own.

Thanks again.