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?

From: snej
2004-08-23 07:41 pm (UTC)

Re: NNTB, Zilla #1576

I've never felt that argument held much water. The distinction between HTTP fetches of regular HTML pages by an accredited web browser, vs any other form of downloading, makes little sense.

Worse, the cows have already left the barn. It is already possible to take a copy of someone's journal. My newsreader app is doing it every half hour as it fetches my friends' Atom feeds and appends the posts to its database.

It is public content. Redistribution of that content is legally iffy, but I can store that content for my own personal use, via my web browser or a newsreader or any other mechanism. Any LJ user who thinks that's wrong is laboring under a common but regrettable misconception about what "public" means.
(Reply) (Parent) (Thread)