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: emarkienna
2004-08-23 05:35 pm (UTC)

Re: NNTB, Zilla #1576

Regarding the "workaround" you mentioned, I think you're completely missing the point of what I've been saying all along. I'm simply suggesting that we need to be careful what we do with other people's data, particularly when there are binding agreements in place. Lame "workarounds" to satisfy these agreements are just that: lame. The correct solution is to make a new agreement.

Well I don't think RSS is a workaround in the bad sense, just that it was another way of achieving the same thing, whilst (supposedly) not causing the problems with the TOS.

Either RSS fits with the TOS, in which case fine, but if not, surely these problems already exist with the RSS that is being broadcast on everyone's LJ? (Was there discussion of these issues when RSS was implemented?)

I'd agree with making a new agreement for all new entries/comments, it seems this would be the best way to avoid any potential problems..

How so? There's nothing that says you can't make a derivative work, just that you don't own 100% of the rights to it.

Well I meant in the sense of creating a derivative work and then publishing it (which surely isn't allowed), although I see that posting on the original journal entry could be seen as not counting as distributing it.
(Reply) (Parent) (Thread)
[User Picture]From: bleything
2004-08-23 05:44 pm (UTC)

Re: NNTB, Zilla #1576

My position on all of this is in the thread in lj_dev, so I won't repeat it here. I will say this: it is wrong to look for ways to comply with the letter of the TOS (and the law) while evading the spirit thereof. Not that I'm suggesting that's what you were doing, but that's what the term "workaround" implies in this sense.

In this case, we're talking about a thing that would be useful to many people and is difficult to find objectionable. Again, let me be clear: I don't oppose the functionality requested here, I'm just trying to make sure people consider all the ramifications of what they're talking about. I'm trying to foster reasoned discussion about more than simply the technical aspect of things.
(Reply) (Parent) (Thread)
From: emarkienna
2004-08-25 03:44 pm (UTC)

Re: NNTB, Zilla #1576

Well, my viewpoint is that it doesn't violate even the spirit of the TOS (so it's not like I'm trying to evade it), but I realise that others may think it does.

I guess my curiosity is then, why didn't these issues get discussed when RSS was introduced - or if they were, what was decided.
(Reply) (Parent) (Thread)