Re: [syndication] All known OCS feeds?

[burtonator <burton@relativity.yi.org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Julian Bond <julian_bond@voidstar.com> writes:

> In article <m3vgjvkdyw.fsf@relativity.yi.org>, burtonator
> <burton@relativity.yi.org> writes
> >Is there a centralized list of all known OCS feeds?
<snip>

> Seriously though, folks. There's been a few suggestions lately for an
> alternative to OCS. Now I'm not going to be drawn into whether this is good or
> bad. But ISTM that a standard for lists of feeds should only contain
> information that identifies the feed or that cannot be derived from the feeds
> that it points at.

Yes... I agree.. but I also disagree :)

It would be possible to have a list of URLs but there are a number of problems
here.  One of the most obvious is performance.  In Reptile we don't want to
waste too much CPU on the client.  The greater number of channels means more to
parse out and index.  This can take a LOT of time... 50 minutes is what it is
currently averaging.

It is better to have a server or agent build a master index with this content
and then syndicate it.  It would be a good idea to have it get descriptions,
titles, etc from the source URL.

I am working on a tool which will build a master OCS feed (or whatever) from a
list of OCS feeds but assume everything is incorrect.  It it will fetch the
source document and prefer the content there.

> It should not contain anything that can be discovered by retrieving the feeds
> themselves because the best source of that data is the originator of each
> feed.

yes... but there is no problem having it as an index.
<snip>

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
        Cell: 408-910-6145 URL: http://relativity.yi.org ICQ: 73488596 

Did you hear why they're using Windows 2000 as a prison guard?  Because it
always locks up! 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE7dEtIAwM6xb2dfE0RAthAAJoDauFBD4hMSRPP4xdtiMJHUbMFOwCdEdOq
g136MnvpFTd0N9lrJSa8Gb0=
=VbxK
-----END PGP SIGNATURE-----