1. 26
  1.  

  2. 3

    guifi is much, much larger than that picture makes it look. https://guifi.net/ca/node/2413/view/map Do zoom out, but NB that there seems to be a map projection bug here–not important if you’re just getting a sense of the scale of the network.

    1. 2

      This article pairs really well with another article from the other day. (Though I’m sure a lot of you already saw it.)

      https://lobste.rs/s/rqqyez/dear_developer_web_isn_t_about_you

      1. 1

        Is there any delay tolerant email client? I would love an email server that can retry with decay.

        1. 4

          Client or server? SMTP servers already include retry. I feel like every client I have ever used will retry once networking is restore if it was down when you send.

          The sender MUST delay retrying a particular destination after one attempt has failed. In general, the retry interval SHOULD be at least 30 minutes; however, more sophisticated and variable strategies will be beneficial when the SMTP client can determine the reason for non-delivery.

          Retries continue until the message is transmitted or the sender gives up; the give-up time generally needs to be at least 4-5 days. The parameters to the retry algorithm MUST be configurable.

          A client SHOULD keep a list of hosts it cannot reach and corresponding connection timeouts, rather than just retrying queued mail items.

          https://www.ietf.org/rfc/rfc2821.txt

          1. 1

            Shouldn’t they all be, in theory? (At least, if you’re using pop3?)

            Back in the day when email was distributed via nightly uucp syncs between individual pairs of machines, it certainly was delay-tolerant. But, at that time, I’m pretty sure email addresses also had routes in them.