From: Brennen Smith <brennen@ookla.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Rpm <rpm@lists.bufferbloat.net>
Subject: Re: [Rpm] an ookla feature request
Date: Fri, 17 Jun 2022 09:11:52 -0700 [thread overview]
Message-ID: <CAFwpvt5KbeWRQ=CxsdgLYgkmw6ynKiycX=dGbmOp1rRypTtVdA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4dRS+56bSyhWV4ZyYOeLd1zK2Eyi+oO1bMhAf4DvGvkg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]
Ahoy Dave et al.,
Great questions!
1. We provide the detail on the share page at a high level. We are super
careful on the result pages though to make sure that no PII/sensitive data
is shared so it is sanitized compared to the detailed result page - here's
a Speedtest from Burien, WA as an example:
https://www.speedtest.net/result/i/5158723178
- We have the platform - iOS. We don't share the OS version for
privacy/security reasons - what if someone shares they are on a vulnerable
OS version?
- Provider - should be visible, assuming our detection works correctly.
While we have some clever overlays, GeoIP is painful.
- Link technology - we do capture the link technology on the test result,
however if someone has a good contact within Apple on the radio data, I do
have a question there.
- Loaded latency - we show the IQM value, but not the min max for now. I'll
ask our Product team why that decision was made.
- The detailed result page has a lot more detail if you scroll, but we
recommend against sharing screenshots of that as it can contain sensitive
data like precise location and IP addresses.
2. Agreed - we actually do those types of marketing callouts; here's an
example:
https://www.facebook.com/speedtest/posts/pfbid0J9S2pc3H1ptoSQCT2xJoJBSN9DyvV7jvXUXVYJChrTTmtYczEsRuJKc6sAaWCXyUl
With that said, it's all over the place on how people share the data in the
thread 😆.
Cheers,
Brennen Smith VP Technology
(206) 739-0807 | brennen@ookla.com
linkedin.com/in/brennensmith <https://www.linkedin.com/in/brennensmith/>
On Fri, Jun 17, 2022 at 9:01 AM Dave Taht <dave.taht@gmail.com> wrote:
> It would be helpful if the detailed results showed the provider, OS,
> and link technology.
>
> Even more helpful if y'all would share within your facebook, twitter,
> linked circles a request to folk to download the new ookla speedtest
> test and post a screenshot with their detailed results within those
> circles.
>
> This is a test yesterday over verizon 5G on an android, deep in the
> los gatos hills.
>
> --
> FQ World Domination pending:
> https://blog.cerowrt.org/post/state_of_fq_codel/
> Dave Täht CEO, TekLibre, LLC
>
--
This email, its contents and attachments contain information from Ziff
Davis, Inc. and/or its affiliates which may be privileged, confidential or
otherwise protected from disclosure. The information is intended to be for
the addressee(s) only. If you are not an addressee, any disclosure, copy,
distribution or use of the contents of this message is prohibited. If you
have received this email in error, please notify the sender by reply email
and delete the original message and any copies.
[-- Attachment #2: Type: text/html, Size: 4774 bytes --]
next prev parent reply other threads:[~2022-06-17 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 16:00 Dave Taht
2022-06-17 16:11 ` Brennen Smith [this message]
2022-06-19 17:04 ` Sebastian Moeller
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/rpm.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFwpvt5KbeWRQ=CxsdgLYgkmw6ynKiycX=dGbmOp1rRypTtVdA@mail.gmail.com' \
--to=brennen@ookla.com \
--cc=dave.taht@gmail.com \
--cc=rpm@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