[Imc-communication] [IMC-US] [alster at indymedia.org: [IMC-Tech] Indymedia North Carolina / Chapel Hill = dead]
andypie
andycleimc at earthlink.net
Tue Jul 24 04:53:04 UTC 2007
On Jul 24, 2007, at 12:46 AM, andypie wrote:
> "where people go on indymedia" (toward the bottom & 'see more') on
> "Traffic" lists Chapel Hill as the 19th most visited Indymedia site.
>
> http://www.alexa.com/data/details/traffic_details?
> url=cleveland.indymedia.org
>
> There needs to be some sort of protocol or test to see if a site is
> truly dead, long term.
>
> no site administration, unable to contact anyone, overrun by
> fascists, with a reasonable time period sounds like a place to
> start. If its mostly college students in the collective, allow for
> summer vacation.
>
>
>
>
> On Jul 23, 2007, at 10:49 PM, john duda wrote:
>
>>
>> ----- Forwarded message from Alster <alster at indymedia.org> -----
>>
>> From: Alster <alster at indymedia.org>
>> To: Tech Imc <imc-tech at lists.indymedia.org>,
>> "imc-commwork at lists.indymedia.org" <imc-
>> commwork at lists.indymedia.org>,
>> IMC Comunications <imc-communication at lists.indymedia.org>,
>> listwork <listwork at sos.indymedia.org>, dns at sos.indymedia.org
>> OpenPGP: id=05059C17;
>> url=http://keys.indymedia.org/cgi-bin/lookup?op=get&search=05059C17
>> Subject: [IMC-Tech] Indymedia North Carolina / Chapel Hill = dead
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA512
>>
>> Hi,
>>
>> it seems like Indymedia North Carolina / Chapel Hill has been dead
>> for
>> quite some while. Attempts to resurrect it have failed. When visiting
>> the URLs of this 'approved/official Indymedia Center (IMC)' (which
>> can
>> thus be reached through the 'indymedia.org' domain name, meant to
>> tell
>> people that this is a serious IMC),
>>
>> http://chapelhill.indymedia.org/
>> http://nc.indymedia.org/
>>
>> you come across a lot of racial hate, pro-nazi propaganda, commercial
>> spam, exploitable security holes and other stuff which makes me think
>> this web site should not remain accessible in the same way it is now.
>>
>> Unfortunately, this IMC seems to have evaporated, all of its mailing
>> lists have not been moderated for a pretty long time and have thus
>> a lot
>> of emails pending for moderation:
>>
>> imc-nc:
>> 333 pending,
>> owners: wsgural at juno.com, jdevins at email.unc.edu
>> imc-nc-editorialimc-nc-editorial:
>> 322 pending,
>> owners: wsgural at juno.com, jdevins at email.unc.edu
>> imc-nc-announce:
>> 127 pending,
>> owners: adm at decry.org
>> imc-nc-tech:
>> 284 pending,
>> owners: wsgural at juno.com, jdevins at email.unc.edu
>> imc-nc-video:
>> 102 pending,
>> owners: adm at decry.org, adonnycl at students.depaul.edu,
>> ginn at cornell.edu
>>
>> To stop these mailing lists from continuing to act as spam traps, I
>> suggest to deactivate all of them. I also suggest to deactivate the
>> 'nc at indymedia.org' email alias.
>>
>> To stop the website from being continuously exploited and Indymedia
>> users from being mislead, I recommend to deactivate the web
>> hosting and
>> to make site backups available to some reliable IMC techs instead.
>> For
>> the same reasons, I also recommend to set the DNS records so that
>> they
>> will point to the newly founded Carolina, USA, based IMC (whose exact
>> name I'm not currently aware of).
>>
>> I also suggest to mark this IMC (ID 58) as dead in the IMC
>> database and
>> to remove any outdated information (contacts, URLs, feeds) which
>> relates
>> to it.
>>
>> All action should be taken in a way that it is revertable in case the
>> IMC should be revived at some point.
>>
>> A copy of this email goes to all email addresses which are currently
>> setup as contacts for this IMC in one or the other way.
>>
>> Should there be too many people thinking this is not the right
>> approach
>> for dealing with this situation, then I suggest all involved
>> groups to
>> decide for themselves how they will deal with this situation and how
>> they assure the continued reliability of the infrastucture they
>> maintain.
>>
>> Being aware it be the 'right' way to do it, but a way no mentally
>> sane
>> person would ever want to go, I will not try to convince my local
>> IMC to
>> make this an IMC process proposal and attempt to follow up on each
>> step
>> which would be involved. I think it is a pity that there is no
>> other way
>> to cause a formal disaffiliation of an IMC which has long been
>> dead (but
>> please do not include me in a on-list discussion on this topic at
>> this
>> point - you're welcome to email me personally or to start a new
>> thread
>> on this topic, though).
>>
>> Alster
>> - --
>> GPG key
>> http://keys2.indymedia.org/cgi-bin/lookup?op=get&search=05059C17
>> Fingerprint 1B8B 128F 8435 541C B3A5 1B7E CF5A 9D55 0505 9C17
>> All other https://docs.indymedia.org/view/Main/AlsteR
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFGpS0mz1qdVQUFnBcRCh60AJ9TNRfqIiAOprlIecLtRGhz13D56gCgrx1u
>> DWpZD7e33m8Yd3hJFfQqGsA=
>> =hK3M
>> -----END PGP SIGNATURE-----
>> _______________________________________________
>> imc-tech mailing list
>> imc-tech at lists.indymedia.org
>> http://lists.indymedia.org/mailman/listinfo/imc-tech
>>
>> ----- End forwarded message -----
>>
>> --
>>
>> 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
>>
>>
>> _______________________________________________
>> IMC-US mailing list
>> IMC-US at lists.indymedia.org
>> http://lists.indymedia.org/mailman/listinfo/imc-us
>
More information about the IMC-communication
mailing list