From: Dave Taht <dave.taht@gmail.com>
To: Kenneth Porter <shiva@sewingwitch.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] cloud gaming on a comeback?
Date: Wed, 10 Jan 2024 11:58:38 -0500 [thread overview]
Message-ID: <CAA93jw45ALPq=-GGJKEO8EW9ovjfkoH7_QJgQJ32wbgvOa-sDw@mail.gmail.com> (raw)
In-Reply-To: <81b5bd03-bf4f-4353-88df-0c1ffeecd304@sewingwitch.com>
On Wed, Jan 10, 2024 at 11:45 AM Kenneth Porter via Bloat
<bloat@lists.bufferbloat.net> wrote:
>
> I miss the days when teams could operate their own game servers on
> colo'd equipment. I ran several Tribes 2 servers for my team 20 years
> ago on a Linux server I shipped to a game hosting company in Kansas
> City. We also ran some of the early Battlefield servers. There were a
> lot of game servers like that. But the game publishers switched to
> operating their own servers to prevent teams from running servers that
> unlocked all the gated content, such as bonus weapons that a player had
> to earn with months of play. That was when I stopped playing those games.
I tested the fq_codel for wifi code against ioquake3. It works. Using
edca also works. If the big telcos got behind twitchy games big-time,
sponsoring teams running over their technologies, perhaps progress
would be made. It could become like NASCAR....
Regrettably i find the current generation of games like CoD too
realistic. It is one thing to shoot a daemons, gleefully, another to
shoot at people.
>
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
--
40 years of net history, a couple songs:
https://www.youtube.com/watch?v=D9RGX6QFm5E
Dave Täht CSO, LibreQos
next prev parent reply other threads:[~2024-01-10 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 16:33 Dave Taht
2024-01-10 16:45 ` Kenneth Porter
2024-01-10 16:58 ` Dave Taht [this message]
2024-01-10 18:47 ` [Bloat] [NNagain] " Dick Roy
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/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw45ALPq=-GGJKEO8EW9ovjfkoH7_QJgQJ32wbgvOa-sDw@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=shiva@sewingwitch.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