From: Bryan P Johnson <bilko@onebabyzebra.com>
Subject: Re: Nobody's interested in livejournal in gnus?
Date: Mon, 9 Sep 2002 11:30:53 -0400 [thread overview]
Message-ID: <a05111b00b9a26d58954f@[207.69.217.16]> (raw)
In-Reply-To: <8665xf9sgv.fsf@duchess.twilley.org>
At 6:56 AM -0700 9/9/02, Jack Twilley wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>There wasn't a single response to my post -- maybe it didn't make it
>out there, or maybe nobody here uses livejournal or wants to use it
>within gnus.
>
>I think it'd be good to use all of the message tools to compose
>journal entries and comments as well as to use the superior
>newsreading tools in gnus to browse journals. Does anyone agree?
>
>I no longer think nnslashdot is a good place to start, and I'm looking
>for suggestions. There is already an elisp package called ljupdate
>that people use to update their journals so it can be done.
>
>Jack.
I'd defnitely be interested in it. But as an FYI, I've looked at the
lj protocol, and unfortunately at the moment all it allows are new
posts and edits of old posts, along with retrieval of things like
friends lists and friends groups and such. It has no way for you to
see comments made to a post, nor even a way to see how many have been
made. There is definitely no way to add comments.
Which means that one would have to parse web pages to enable that
functionality, and that is something that the lj_dev community
recommends against. Not that that should stop you. :-)
BrYan
next prev parent reply other threads:[~2002-09-09 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-09 13:56 Jack Twilley
2002-09-09 14:10 ` Kai Großjohann
2002-09-09 14:48 ` Michael Livshin
2002-09-09 15:30 ` Bryan P Johnson [this message]
2002-09-09 17:57 ` Calle Dybedahl
2002-09-09 18:15 ` Edward O'Connor
2002-09-10 8:26 ` Kai Großjohann
2002-12-29 17:51 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='a05111b00b9a26d58954f@[207.69.217.16]' \
--to=bilko@onebabyzebra.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).