Christian Swertz via Nettime-tmp on Wed, 14 Jun 2023 17:22:02 +0200 (CEST)


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: <nettime> Direction of Travel 

Hello,

Am 13.06.23 um 18:26 schrieb Rich Kulawiec via Nettime-tmp:

a rhetorical question.)  You'll be right back here again.  The only way
to avoid this inevitability is to run your own domain, mail system,
and mailing list -- and to structure it so that it's a lift-and-drop
operation to shift it to another host should that need arise.
You mean running everything in something like a docker container that can easily be shifted to another machine? Probably a good idea. Concerning the domain: As far as I see, the domain nettime.org is somehow connected to the list. It is at least registered in Switzerland. If it's possible to find the access data for the provider, it should be possible to configure the MX record in a way that allows us to use for example nettime-l@nettime.org as the lists address. Is that what you mean?
If that's the intention, this would indeed disconnect the mailman service of nettime-l from the physical machine it is running on. So the strategy might be to physically run the stuff on a machine of waag.org, but in a docker container and connected to the lists domain to avoid future hassle. 

Is that correct?

All the best,

Christian.

#  distributed via <nettime>: no commercial use without permission
#  <nettime>  is a moderated mailing list for net criticism,
#  collaborative text filtering and cultural politics of the nets
#  more info: https://mail.ljudmila.org/cgi-bin/mailman/listinfo/nettime-tmp
#  archive: http://www.nettime.org contact: nettime@kein.org
#  @nettime_bot tweets mail w/ sender unless #ANON is in Subject: