Below, you will find supporting evidence of some of the actions by the
new sf.indymedia.org group as outlined in the timeline document:
lists.indymedia.org/pipermail/imc-us-process/2004-January/000270.html

1. www.indybay.org/images/ecr_hidden12-9-03.jpg
This is a screen capture of an announcement post by Enemy Combatant
Radio to sf.indymedia.org on 12/9/03 that was hidden immediately. As
you can see, indybay.org still pointed to sf.indymedia.org at the time
but one member of the sf.indymedia group (with no agreement even from
the people in his own group) had already locked the indybay.org group
out of the shared site by taking away the admin passwords, leaving them
without a website. For reference, Enemy Combatant Radio is a project
affiliated with members of indybay.org.

This article was later unhidden after this post was made by a reader:

sf.indymedia.org/news/2003/12/1664695.php

2. www.indybay.org/images/whispered_hidden_12_18_03.jpg
This is a screen capture of an announcement post by Whispered Media to
sf.indymedia.org on 12/18/03 that was immediately hidden. Whispered
Media is a video collective that has an office in the same suite as
indybay.org.

3. www.indybay.org/images/sfimcspam_12_24_03.jpg
This is a screen capture of multiple spam made on the indybay.org
newswire on 12/23/03. The contents of those spams can be seen here:
www.indybay.org/news/2003/12/1666449.php
www.indybay.org/news/2003/12/1666450.php
This is one example of many instances of such "pro-sf.indymedia.org" spam made on indybay.org.

As many of you know by now, Enemy Combatant Radio's website:
www.enemycombatantradio.org was taken down by a person associated with
sf.indymedia.org on 1/7/04, the day after the indybay.org collective
had sent out the open letter:
lists.indymedia.org/pipermail/imc-us-process/2004-January/000266.html

The indybay.org domain is still owned by a member of sf.indymedia.org,
even though it is not a website they have anything to do with anymore as
shown in the mediation agreement:
lists.indymedia.org/pipermail/new-imc/2004-January/004742.html

All of this indicates there has been gross violations of the trust
within the indymedia network that techies with control of resources
will not abuse their power for any reason.

We hope that everyone in the indymedia community realizes that this is
an issue of tech abuse of power that will have serious implications
throughout the entire network. Member of the sf.indymedia.org (and
their linefeed.org tech collective) who are responsible for the
violations of the indymedia Principles of Unity as shown above, still
currently operate the server (stray linefeed server) that many IMC
sites are hosted on. They include:

Tijuana - tijuana.indymedia.org
Colombia - colombia.indymedia.org
Hawaii - hawaii.indymedia.org
Peru - peru.indymedia.org
Uruguay - uruguay.indymedia.org --
Argentina - argentina.indymedia.org
Bolivia - bolivia.indymedia.org
Chile - chile.indymedia.org
Istanbul - istanbul.indymedia.org
Jerusalem - jerusalem.indymedia.org
South Africa - southafrica.indymedia.org
Utah - utah.indymedia.org
Thunderbay - thunderbay.indymedia.org
Houston - houston.indymedia.org
Arizona - arizona.indymedia.org

The sf.indymedia.org/linefeed.org members have shown through their
actions that they cannot be entrusted with the amount of power they
hold by controlling IMC tech resources. I ask all members of the
indymedia network to help hold these individuals accountable for their
actions.



indybay.org