John Preston via Nettime-tmp on Tue, 13 Jun 2023 18:36:39 +0200 (CEST)


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

Re: <nettime> Direction of Travel

Hi Rich,

I think it comes down to deciding what the threat models are and what tradeoffs we want to accept in terms of what solution we want to use.

I suggested Riseup early in the meeting because I am vocal and solution oriented, any my own tradeoffs include that I prefer delegating the burden of managing modern email platforms! 😅 That may have steered the conversation in a particular direction.

This is not a final list of options by any means, everything is open up for discussion and good to have your extremely actionable proposals as a different perspective!

I wonder, maybe it could be a multi-site or federated thing? So if people want to host a 'node' then everyone can email that, but it gets re-circulated on Riseup or any other provider if we go that route as well. That would be very redundant, but I'm not sure if such a thing has been done with e-mail mailing lists before. It makes me think more of other protocols like UUCP/Usenet and FidoNet.

Thanks,
John (they/them)



13 Jun 2023, 17:26 by [email protected]:
On Wed, Jun 14, 2023 at 12:02:10AM +1000, paul van der walt via Nettime-tmp wrote:
* John Preston will reach out to riseup.net, to ask whether they would be
willing and/or able to host a list of our size,
* Jordan Crandall knows the executive director of rhizome.org and so will
put out feelers in that direction,
* Henk said that waag.org would be able to host nettime if we wanted that.

These may or may not be good options, but I thought that the idea was
to do everything possible to avoid having to revisit this issue in the
future -- which is why I didn't volunteer to host the list even though
I could have it running on existing infrastructure in a matter of hours.

Otherwise: what's the plan when riseup.net (et.al.) go away? (That's not
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.

These are baseline skills for any competent sysadmin, so this shouldn't
be that hard. There have got to be half a dozen (or more) people here
who have this skillset, right? Or who are capable of learning and who
are willing to invest the necessary time/effort?

Otherwise, all that will happen is shifting and deferring the problem,
not solving the problem. And if you want to choose that path: well,
it's certainly an option. But that choice will have consequences.

---rsk
# 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: [email protected]
# @nettime_bot tweets mail w/ sender unless #ANON is in Subject:

#  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: [email protected]
#  @nettime_bot tweets mail w/ sender unless #ANON is in Subject: