Upcoming cross-site reading list, Salmon protocol

[charmian]

1. Very informative post about upcoming features at DW.

To wit, there is

a) discussion of the cross-site reading list. It will be a paid user feature, it will only show the last 100 entries and be updated every 60 min, and the entries from the other site will ONLY be visible to the person subscribing to them (even if they are public otherwise).
b) in the future, it will be possible to upload communities to DW, if you are a maintainer (and probably, you should also get permission)
c) the new entry posting page: the 'metaphor' underlying posting will be changed, to incorporate new drafting options,

Anyway, someone has already protested the cross-site reading list, perhaps unaware that RSS/ATOM allows people to read LJ-entries off of LJ. Maybe someone ought to point out to this person that they can at least disable syndication of entry content in RSS/ATOM on LJ? They can't disable it totally, though (if they don't like the fact that they can't totally disable RSS, then they should stop using LJ, because that's how things are there).

EDIT: It seems that DW will actually not be using authenticated RSS for this new feature: http://dw-news.dreamwidth.org/17591.html?thread=1814455#cmt1814455

2. I mentioned the Salmon Protocol in my last post. Here's more info on the subject.

http://www.readwriteweb.com/archives/salmon_protocol_for_distributed_aggregated_content.php <--Read Write Web post on the SP.

http://salmon-playground.appspot.com/ <-- A prototype of the Salmon Protocol

http://www.alevin.com/?p=1806 <-- Blog post about the problem Salmon is meant to solve.

http://groups.google.com/group/salmon-protocol <--The Google Group for people working on the project. Rather technical.

Comments

[matgb]

So if you only load your DW reading page [any page on DW] twice a day, then external sites only get polled twice a day

From what I understand, it checks every time you're active on DW in some way, and if it hasn't polled for over an hour it'll poll.

But yes, not as good for those of us with active friends on LJ. Especially not if, as Janine implies, that reading filters won't work--I have a filter on LJ especially for high frequency linkbloggers who sometimes post ten times an hour, I only ever read them on the filter as they swamp everything else.

Ah well, either they'll iron out the details or I'll keep using my LJ filters as well--can't afford paid account currently anyway, hopefully that'll change soon but...

[pne]

From what I understand, it checks every time you're active on DW in some way, and if it hasn't polled for over an hour it'll poll.

I was going by Mark's second bullet point:

We will only download new entries every 60 minutes (this may change). This means that, when you view your reading page on Dreamwidth, we only contact remote sites every ~60 minutes to ask for new entries. (emphasis mine)

Though it's quite possible I jumped to conclusions since he didn't specifically say that polling checks only happened on reading page load.

[matgb]

See, I just searched through all the comments to find where I'd read that, then reread the post. Mark;'s last bullet point:

We only download entries while you're browsing the site. In short, whenever you view a page on Dreamwidth (any page), we will update your reading page with remote entries if it's been more than an hour.

Which works for me.

[pne]

Ah! OK. Must have skipped that bit.

Thanks for pointing me to the horse's mouth.

[yvi]

Sounds a bit strange to me (pulling my reading page when I am only surfing the stats page, or something), but okay with me. Especially as I am not planning on using it anytime soon :)

[matgb]

I think it'll only be doing it if you sign up to it, but for me, given I have a fairly busy LJ friends page, if it doesn't poll regularly, it'll almost certainly miss stuff.

While I may only update my reading page irregularly, if I'm active, odds are I'll be commenting and replying throughout the day, so it makes sense to me, anyway.

[janinedog]

From what I remember of Mark's demo of the feature to me (he showed me a half-working version of it about a week ago), posts were not actually associated with accounts, because the only real option is to associate them with OpenID accounts, which means changing the code on half the site to allow OpenID users to have/control entries (since it's assumed now that they cannot). And since the content won't even be visible to anyone except the reader, that's more logic to put in there if it's associated with an OpenID account (to show it to them, too). And since it's only around for 2 weeks anyway, doesn't seem like it's worth it really.

But, obviously anything can change at this point. I agree that allowing the imported entries to be filtered by user would be very useful. And I may not even be fully understanding how it's working at this point either, so don't take my word for it. :)