From: Jim Forster <jim@connectivitycap.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: the keyboard of geoff goodfellow <geoff@iconia.com>,
Brian Longwe <blongwe@gmail.com>,
Starlink <Starlink@lists.bufferbloat.net>
Subject: Re: [Starlink] Starlink in Kenya (Lennox Omondi)
Date: Sat, 11 Nov 2023 23:21:16 +0200 [thread overview]
Message-ID: <B5AC5719-21E8-4121-881B-99196F2178D3@connectivitycap.com> (raw)
In-Reply-To: <CAA93jw5auz+cpS72kXhwdkAhguHJODBjvHiWkUoMuwgvGTJhGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1092 bytes --]
(Very briefly)
IXPs are great, but these days mostly need CDNs as not so much traffic is between ISPs — it seems most consumers are heavy users of FANG-ish site. Maybe sighlty different I guess for business users, but still...
Local CDNs have huge value, but need more traffic than most smaller ISPs can muster. That’s where IXPs can shine now, if they somehow get some CDN/cachess. Habari.co.tz has done that for the Arusha IXP they manage. I think that’s what Brian @ CTN is trying to do as well. Over in the Philippines, Rise.ph has done a great job doing this with their Getafix.ph. See https://www.linkedin.com/feed/update/urn:li:activity:7113399324490813440/ for a bit more about them.
— Jim
> On Nov 11, 2023, at 7:57 PM, Dave Taht via Starlink <starlink@lists.bufferbloat.net> wrote:
>
> Africa, and for that matter, rural america, could use more IXPs and
> CDNs. I have been watching brian's progress here eagerly, but as the
> info for what he and jim and so many others are attempting to create
> in Africa has been arriving daily piecemeal,
[-- Attachment #2: Type: text/html, Size: 4061 bytes --]
prev parent reply other threads:[~2023-11-11 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 17:48 the keyboard of geoff goodfellow
2023-11-11 17:57 ` Dave Taht
2023-11-11 21:21 ` Jim Forster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=B5AC5719-21E8-4121-881B-99196F2178D3@connectivitycap.com \
--to=jim@connectivitycap.com \
--cc=Starlink@lists.bufferbloat.net \
--cc=blongwe@gmail.com \
--cc=dave.taht@gmail.com \
--cc=geoff@iconia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox