>Random is not included in GBomb because GBomb is an email
>application, and sending random emails is probably not a
>good thing.
>
>However, the BlogBomb random ssi tag can be inserted into
>the GBomb archive template, which means it will work in html
>pages, but not email.

I don't care about email. But what you are suggesting is a different thing and is self-defeating. GBomb archives the template with the ssi tag inside, not with the output in the moment of the scheduled archiving.

So, in Feb 2015, you'll have a "daily archive" with 3650 pages, any of them publishing a random selection from the same group of news dated Feb 2015. And it isn't in anyway the purpose of an archive (and even a very "search engine stupid" thing).

Can i conclude it is impossible to archive the feed mix?

Bye.

>I don't care about email. But what you are suggesting is a
>different thing and is self-defeating. GBomb archives the
>template with the ssi tag inside, not with the output in the
>moment of the scheduled archiving.

Yes it is self defeating...as is archiving redundant information, which is what your are suggesting.

>So, in Feb 2015, you'll have a "daily archive" with 3650
>pages, any of them publishing a random selection from the
>same group of news dated Feb 2015. And it isn't in anyway
>the purpose of an archive (and even a very "search engine
>stupid" thing).
>

The question becomes, why would you set up an archive of news that isn't "newsworthy"?

It makes no sense from a content point of view. Something that is stagnant doesn't need an archive.

If there's no content about a particular topic, why would there be any interest in it? If a single pheed hasn't been updated in 10 years, I doubt you've missed out on any thing.

What you're suggesting is that is is somehow better to have 3650 ( leap days) pages with the same 15 paragraphs/items, just rotated? They haven't updated, remember. If they updated you wouldn't need to use the random function, which was the reason for your initial question.

The key to GBomb is using "newsworthy" subjects, which means they update. This is how the content "rotates". If your pheeds do not update often enough, then you'll need to use a weekly/monthly list or chose more popular topics.

Think about it...If a topic doesn't update, is there really any interest in it if no one is even talking about it?

Also, if using an RSS search engine, make sure to format the search using the "sort by date", and NOT "relevance". This will often update your results much, much faster.

No, i'm not suggesting it in any way...

>What you're suggesting is that is is somehow better to have
>3650 ( leap days) pages with the same 15 paragraphs/items,
>just rotated? They haven't updated, remember. If they
>updated you wouldn't need to use the random function, which
>was the reason for your initial question.

I'm just saying that if you have a feed with not so much updates (let's say 1-2 news in a week) AND if you set Godfatherbomb to archive it daily, you'll have duplicates.

With so many feeds for any subject is very easy to find 10 more different feeds on the same subject. But if you can't mix them, and instead you put all of them in the template, you'll have duplicates again (except for those with updates).

>The key to GBomb is using "newsworthy" subjects, which means
>they update. This is how the content "rotates". If your
>pheeds do not update often enough, then you'll need to use a
>weekly/monthly list or chose more popular topics.

This is true, i missed to state daily archiving was a priority (and the kind of the niche was another).

>Also, if using an RSS search engine, make sure to format the
>search using the "sort by date", and NOT "relevance". This
>will often update your results much, much faster.

In fact i solved the whole thing upstream, widening the range of my search and sorting it by date.

Bye.