[IMC-Editorial] Re: [IMC-Tech] my problem with the newswire, by jenka

[john duda]

On Thu, Mar 18, 2004 at 10:26:38AM -0800, blah blah wrote:
> perhaps it is the automated system that is now
> automatically taking items from CERTAIN local imcs
> (not all of them by any means) and reposting those
> features as newswire items in global.

i think the system takes feeds from any imc which has a working rss
feed for features listed in the contacts database(in which all local
imcs should theoretically be able to update their own entries. )

> 
> now, come on.  how hard would it be to ask local imcs
> to actually SUBMIT the items they want on the global
> newswire, or at LEAST having the option to CHOOSE
> whether that particular feature goes on the global
> newswire, so that it is not AUTOMATIC that EVERY
> feature goes on the global newswire.

some imc's already do this.  for example, the netherlands imc, which
aggresively promotes newswire articles to features, most of which are
not at all of interest to people outside of the netherlands.  they
have their mir setup to have a separate category for stories of global
relevance, which then gets made into a rss file for pick up by global
indy.  i think that the other codebases could probably also do
something similar, but i am not sure of the details.  it would have to
be primarily a local decision/initiative.  i also don't know how many
imc's are doing this already.

> 
> and a first time user to the site does NOT know what
> 'features/open publishing' means.....
> i mean.....someone could at least put a mouseover
> event that explains what 'features' and 'open
> publishing' refer to -- that's not that hard to do....
> 
> I also think that the 'liveradio' link should go on
> the left column.....the newswire keeps getting shoved
> farther and farther down the page due to the growing
> calendar of events.....

the liveradio.indymedia.org link seems pretty much dead, i think it
was scheduled for removal already.

john

-- 

this is where my public key can be found:
gpg --keyserver pgp.mit.edu --recv-keys 03817826
Key fingerprint = 6C11 8D70 2ADE EFA9 498D  72CB 77EA 391A 0381 7826