Import daily posts from RSS

[andrewducker]

Title:
Import daily posts from RSS

Area:
posting

Summary:
The ability to read an RSS feed and post the results to DW would be great. I'd use it for importing from Delicious, and it could also be used with Twitter, and a myriad of other services.

Description:
At the moment there are various off-site services people store their information on. And there are some services that allow you to produce a daily blog post. However, most of those either don't support DW (or LJ), or they require you to hand over your user name/password in order to be able to post.

If DW could do the scraping for you, and then produce the post on a daily basis, then this would make life significantly easier and more secure.

As an example, I'm thinking of something like this:
http://andrewducker.dreamwidth.org/2279883.html
which is currently produced using Delicious Glue, and is reliant on (a) Delicious continuing to support blog posting and (b) me handing them my DW password...

Poll #5993 Import daily posts from RSS

Open to: Registered Users, detailed results viewable to: All, participants: 40

View Respondents

This suggestion:

View Answers

Should be implemented as-is.
12 (30.0%)

Should be implemented with changes. (please comment)
7 (17.5%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
20 (50.0%)

(Other: please comment)
1 (2.5%)

Comments

[msilverstar]

I would really like some good way to post from delicious and diigo.com, and I don't care about the method.

[azurelunatic]

Don't forget post-by-email, for people looking for an immediate solution and services that will send things out to an email address of your choice. One sets up a post-by-email PIN, which only gives access to post, not to monkey around with other things, should a service go bad for any reason.

Our documentation on it is, er, scant-to-invisible, but it's not been changed from LJ's implementation.

[faithofone]

Post-by-email is a paid feature, right?

[denise]

Not on DW: everyone can use it.

[faithofone]

Oh score! Love finding out I can do things I thought I couldn't do.

This means I can post via texts from my phone!

[azurelunatic]

I seem to recall some OMGNOOOOO speculation about similar capability being usable to snatch content to which one had no particular right to make a permanent public archive (I think someone said "Yeah, and think about all the people who'd just feed the sports page into their journal" when this came up on LJ) so when the remote site offered the ability to authenticate with OpenID or OAuth, that might be a good plan.

If it does happen, links to the source should be automatically included; if someone wants to remove them, they could edit it manually. (My journal was embedded on someone's ad impressions site without my permission and without linkbacks, which led to me ragefacing and cutting my LJ syndication down to links-only.)

[andrewducker]

If someone wants to feed the sports page onto their journal, then what's the problem? If it's a copyright violation then the original site can complain, and if not then individual users can choose to drop that person from their reading list if it bothers them.

So long as I can point the import at http://feeds.delicious.com/v2/rss/andrewducker?count=30 I'll be happy.

[faithofone]

My "with changes" vote here backs up Azz's OpenID or OAuth comment. It'd be kinda weird if someone else was syndicating my Twitter feed to their journal.

[sporky_rat]

My with changes is the same.

[andrewducker]

So long as the other site didn't _have_ to offer OpenID or OAuth. If it was just something that kicked in if it did then that would seem like a reasonable compromise.

[faithofone]

Then how are we to determine who the owner of the content is? It's not okay to just copy all of someone's content and post it somewhere else. I know that RSS makes this a bit tricky, given that the authors are offering a way to syndicate the content. However there's a difference between providing feed reading services and providing easy ways to repost content without the person who created the content's permission.

If there isn't a way to verify that you own the content, then I'm not okay with having it imported. The other option would be storing the username and password that you use to login to that site, in the same way that Dw stores information for crossposting.

[cheyinka]

Mine as well.

[kyrielle]

Mine also. I realize it's an inconvenience for people using a service that doesn't provide any way to authenticate, but the reverse creates content ownership problems that will open the old "if a service provides a way to do it" argument in ways I don't think Dreamwidth needs.

And since Twitter (one of the sources most likely to cause one to want this) DOES offer a method of authenticating....