[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [syndication] OCS Version 0.5 draft
> As I mentioned before, it's probably a good idea to have a master OCS
> index that lists other possible OCS files available.
Hmm, an interim step here would be for anyone wanting to republish an OCS file
to set up a personal list on Syndic8. Recognizing, however, that the current UI
is, well, clunky, there does need to be an easier way to do it. I'll see what I
can do.
> Use the rss
> taxonomy module to add categories to the ocs files, or group by update
> frequency, or when the channels were created etc.
Yep, this is one of the very cool things about using namespaced modules.
Picking up on the sematics of what someone else has already slaved over means
considerable time savings.
> Instead of one 400G OCS file you end up downloading 4,000,000 100K
> files once you've traversed the network. Without OCS you don't have
> the metadata about the lists of other channels. Perhaps my rss
> blogroll points to rss channels that have some kind of restrictive
> licensing or require a sign-on. An OCS module could be developed to
> characterize that kind of information.
Indeed, I considered this in the personal list functions. The ability to have a
list that's public or private and, eventually, shared to a group. Heck, signing
with shared keys is one way to sling 'em about without leaving their contents
exposed.
> OCS doesn't preclude P2P in any way. But it does reduce bandwidth
> requirements by allowing you to be more selective about the channels
> you're discovering and by not forcing you to download the last 15
> postings to my weblog in their entirety.
+1
-Bill Kearney