Why this might not work

[lulalala]

I asked opinions from a few people, and here I reorganise them and
open for discussion if they are valid/room for improvements:

1. Often the other sites will make a copy of the feed in its own
database. this will prevent the future update flow.

2. The central server will have need to handle huge feed queries.

3. Ping back for new comments will provide a new way for spam.

4. Blogger can already allow users to have sub blogs, and then have a
central blog taking the feeds of the sub blogs.

---

My answers would be

1. I guess if the other sites like forums do that, it will only be
counted as half compliant to the whole concept. Indeed we will not
able to do much about it. One possibility is to make the new update
notification more friendly to other websites so they will like to
include this functionality. Maybe relying solely on feeds will not be
practical to them. More likely websites can choose to check the feeds
say every 10 days in order to save cost.

2. As mentioned above, if the client website only checks the feeds on
a periodic basis this should be okay. One other thing is that, the
author would like to let more people know about his/her writings so
the author will also want to keep in touch with the readers so they
really will not mind having a huge data request. In case it is too
large they can always selectively turn off the feeds, in this case I
guess the client website can use the caching in their database until
the feeds gets activated again.

3. I am no expert on this field, but I believe the solution would be
something similar to the current spam blockers.

4. I think the key thing is the flexibility. The feed factory gives
you more possibilities, and easier management. In the blogger system,
you will not be able to cross post the same post in two sub blogs
without duplication.

Discussion welcomed :D