I'm discovering the old gopher protocol.

Could we consider Gopher as a more ecological alternative to HTTP and the Web?

Could we consider today that Gopher is better for consulting content and the Web to use services?

I think I'm going to dig more into this ancient technology.

@Drulac Because from what I understand, you only download the content, usually pure text, and nothing else.

With gopher you need only one request per content while with the Web you may do several subsequent requests for the CSS, JS and image when you only want to get one page.

Also, the gopher protocol requires less overhead than HTTP.
Everything is technically simpler.

Here is an article which explains a part of it:

Sign in to participate in the conversation
Qowala's Mastodon

Welcome to Qowala's Mastodon instance!
Here, we love open source and we study and work on social networks so naturally we also host a Mastodon instance.
Friendly people are welcome, but as this is a small server, there are limited available slots. So, choose wisely to join or not.