Manual vs automatic content syndication

32 views
Skip to first unread message

Miguel Á. Friginal

unread,
Aug 1, 2011, 1:26:32 PM8/1/11
to iDevAuthors
One of the things I wanted to get away from in this new phase is being
too specific about the dates you can post. I am thinking that whatever
we go with at the end (week days, every 15 days…), the calendar is
going to be more a suggestion than anything else. So basically you can
post on your day, sooner or later, and in general there would be no
issue if everybody tries to post sometime around their assigned day
and not more often than every 2 weeks.

The way iDev works right now is:

- every hour it grabs the RSS feed for the 2 authors of the day. There
are caches, and header and partial requests, etc. to help with this.
- if it finds a new post with a publication date in the assigned day
(in the PST timezone), it caches that response and displays it on the
site.

This doesn't really allow for much flexibility with the dates, unless
I just grab a range of days, let's say 2 days in advance to 2 days
later, in the date comparisons.

Another way to do this would be to have an admin that authors log into
(I would go with WP or similar), that has a section where you select
what things from your own RSS feed you want to push into the iDev
site. You would write your post in your site as usual, then login into
iDev where it will show you the articles available in your RSS. You
would then select the new one, and approve it for displaying in the
iDev site.

Yet another way would be to have a common category that you can add to
your Atom feed (not sure if RSS supports this). In WordPress blogs
would be as easy as assigning a category or tag to the post. When iDev
goes through your RSS it will just add any new posts that have that
category, independent of date.

What I like about this second one is that is easier for authors. What
I like about the first one is that is easier for me to admin if
somebody has problems or bends the rules (posting too often, for
example). I know the "too often" problem can be automated too, but I
am sure other problems would arise from any automated process.

Any thoughts?

Tom Ortega

unread,
Aug 1, 2011, 2:27:58 PM8/1/11
to ideva...@googlegroups.com
I thought it was already an automatic process based on Tag or Category. I'm guessing not?

Thanks,
Tom Ortega
cell: 951.212.9686 | twitter/skype: lordbron
lordbron.wordpress.com area-161.com OneMinuteBite.com


2011/8/1 Miguel Á. Friginal <miguel....@gmail.com>

Matt Rix

unread,
Aug 1, 2011, 2:48:29 PM8/1/11
to ideva...@googlegroups.com
I like the automated "just tag it" approach. If worst comes to worst and someone posts too often with that tag/category, we can just ask them to untag one of the posts or whatever, I don't think it'll be a big issue. 

2011/8/1 Miguel Á. Friginal <miguel....@gmail.com>
One of the things I wanted to get away from in this new phase is being

Gareth Jenkins

unread,
Aug 1, 2011, 2:57:06 PM8/1/11
to ideva...@googlegroups.com
Yea -- with Matt on that one. 

It adds a threat-like management system as well -- I.e. if someone posts too often but is asked to remove tags and doesn't, they can just be removed from the list. 

If it got spammed often, it could always be filtered or proxied (something like yahoo pipes would likely do it). 

G. 
--
____________________________

Gareth Jenkins
Productivity Balloon Ltd

Raimon Zamora

unread,
Aug 1, 2011, 4:06:59 PM8/1/11
to ideva...@googlegroups.com
I'm with that system too

Sent from my iPhone

Brandon Alexander

unread,
Aug 1, 2011, 5:26:56 PM8/1/11
to ideva...@googlegroups.com
Less work for me is always better :)

Sent from my iPhone
Reply all
Reply to author
Forward
0 new messages