Log in

No account? Create an account
LiveJournal Client Discussions [entries|archive|friends|userinfo]
LiveJournal Client Discussions

[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

USENET-style LJ client? [Aug. 23rd, 2004|12:48 am]
LiveJournal Client Discussions


I've been looking around at the available LJ clients and not finding one that does what I want.  Do I have to write my own?  Most clients seem to think that their job begins and ends with helping me write WYSIWYG journal entries, but I find the LJ web interface is fine for that.  What I want a client for is
  • Tell me when new comments have been attached to my friends' journal entries.
  • Tell me which comments are ones I haven't read yet.  (Currently I have to squint at the dates and usually just end up rereading comments I've already seen.)
It seems to me that this is most easily accomplished by adapting a USENET reader, such as Pan, using the following analogy:
LiveJournal USENET
User login  → Server
Friend  → Newsgroup
Journal entry  → Thread-starting post
Comment  → Reply post
And so forth.  Of course, there are some differences (deleting a comment has different semantics from cancelling a reply, thread-starting posts can be edited if yours, etc.) but I suspect a decent job could be achieved by "just" replacing Pan's backend and leaving the UI pretty much the same.

And I completely out to lunch on this?

[User Picture]From: hythloday
2004-08-23 01:34 am (UTC)
I actually have an LJ->NNTP server written in Python, which I can't release because the method it uses to get comments is to screen scrape an XML s2-styled comments page, which is verboten. Something I have on the back burner is to convert the backend from going straight to LJ into a module which reads pages from the mozilla or konqueror cache, which have an embedded XML section. (So the user can use a browser normally and also the newsreader.)

That said, generating s2 code that would do this for each user is probably a monstrous hack, and I don't know anything about the mozilla cache. (And working on something that only worked on konqueror is a bit silly, imo. :-)
(Reply) (Thread)