On Mon, Sep 13, 2021 at 01:01:38PM +0200, Daniel Stenberg via curl-library 
wrote:
> Hi team.

Hi Daniel and readers of curl mailing list,

This is not a troll e-mail but a benevolent one. Your initial
message is related to some questions I am currently asking
myself about our responsibility (as computer scientists) in
climat change and what we might do in our field to help.

> We added support for GOPHERS in late 2020. There's a new PR proposing
> support for the ManageSieve protocol. We had a PR previously suggesting
> Gemini support and the other day ICAP was brought up in a discussion.
> WebSockets is another common one discussed.
> 
> I don't think it's crazy to imagine that we might add support for more
> protocols going forward. Sooner or later.

I'd love to know what are your thoughts about GreenIt / low tech
and the paths that we may need to walk through to reduce our
environmental footprint [1] such as:

* limit or (better) reduce features in programs,
* maintain released versions for a much more longer time (such
  as 7 years [2]).

Is it conceivable to make choices of which protocols may stay
or not in curl and keep only 32 of them ?

This could sound a bit overkill but don't we live in a finite
world ?

[1] Environmental footprint of the digital world:
    https://www.greenit.fr/environmental-footprint-of-the-digital-world/

[2] Germany for 7 years of security updates for smartphones:
https://techbriefly.com/2021/09/06/germany-negotiates-with-eu-for-7-years-of-updates-to-smartphones/
https://www.heise.de/news/Bundesregierung-Smartphones-sollen-sieben-Jahre-lang-Updates-erhalten-6179995.html

Thanks for your thoughts, best regards,

Olivier.

-- 
Continuous data protection for GNU/Linux (GPL v3)
Current version v0.0.12.
 . Download source code : http://cdpfgl.delhomme.org/download/releases/
 . Contribute to project: https://github.com/dupgit/sauvegarde

Attachment: signature.asc
Description: PGP signature

-- 
Unsubscribe: https://lists.haxx.se/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html

Reply via email to