From: Rich Brown <richb.hanover@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Has any one seen the VSee Network Stability Test?
Date: Mon, 30 Sep 2024 13:21:19 -0400 [thread overview]
Message-ID: <7B33A568-0A9A-4D5E-9C94-5E1E369AA604@gmail.com> (raw)
In-Reply-To: <3CDF93BB-6257-46E2-B6F3-DEE3246A3CBA@gmail.com>
Update: I heard back from VSee support. They were quite clear that they do NOT wish to share their code, nor to make their server side a public API.
My questions:
- Is the existing 1.0.4 version (https://test.vsee.com/network/index.html) "good enough" for widespread testing?
- Does anyone know of a similar test setup that makes source code available?
Many thanks.
Rich
PS I made a short code for the URL: bit.ly/VSee
> On Sep 29, 2024, at 9:04 AM, Rich Brown <richb.hanover@gmail.com> wrote:
>
> I came across an intriguing utility a while back. The "VSee Network Stability Test" is a web page that continually monitors the quality of your network connection so you can determine whether your Zoom call crapped out because of a network problem. (VSee provides telehealth services, and I imagine they created this test so they could blame someone else...)
>
> It appears that the test page establishes an RTC connection to their server, and uses the response times of the traffic to compute latency, jitter, and packet loss. It also computes MOS score (used to rate telephone call quality) and shows all three in graphs. Check it out at:
>
> https://test.vsee.com/network/index.html
>
> Although the underlying data is compelling, their web page is as ugly as sin (at least for non-techies). I have asked VSee whether they might be open to making changes, or if they might make the source code available, but I think it's unlikely.
>
> Alternatively, does anyone know of an equivalent facility that has a) a nicer web page and b) source code available? Thanks
prev parent reply other threads:[~2024-09-30 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 13:04 Rich Brown
2024-09-29 16:03 ` Dave Taht
2024-09-29 18:13 ` David Collier-Brown
2024-09-30 17:21 ` Rich Brown [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/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=7B33A568-0A9A-4D5E-9C94-5E1E369AA604@gmail.com \
--to=richb.hanover@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/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