From: Sebastian Moeller <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Getting bloat tests into open source speedtest
Date: Tue, 3 Sep 2019 14:01:06 +0200 [thread overview]
Message-ID: <1B771A2B-FCBD-4305-B89C-6BD7B35976AE@gmx.de> (raw)
In-Reply-To: <87o901a9ij.fsf@toke.dk>
> On Sep 3, 2019, at 13:45, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Sebastian Moeller <moeller0@gmx.de> writes:
>
>> Hi Toke,
>>
>> +1
>>
>>> On Sep 3, 2019, at 13:39, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>>>
>>> Hi everyone
>>>
>>> I came across this open source speedtest: https://www.netztest.at/en/
>>> (also run by nic.cz and integrated into the Turris Omnia firmware:
>>> https://www.netmetr.cz/en/ ).
>>
>> I tried to contact the www.netmetr.cz folks (last year), but so far.... crickets...
>
> Heh, well thanks for trying at least. I figured the upstream open source
> project might be the best way to get things fixed; we'll see if they are
> responsive :)
I would hope so,. My gut feeling is, that we should address this with BEREC (https://berec.europa.eu) as all these national regulator's internet speedtests all closely follow the BEREC recommendations and there might be little perceived freedom for the national implementation according to the BEREC guidelines for changes/additions. Last time I contacted the implementor of the german speedtest (breitbandmessung.de), they basically send me bunch of BEREC documents and deflected my questions towards the EU ;)
Best Regards
Sebastian
>
> -Toke
next prev parent reply other threads:[~2019-09-03 12:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 11:39 Toke Høiland-Jørgensen
2019-09-03 11:41 ` Sebastian Moeller
2019-09-03 11:45 ` Toke Høiland-Jørgensen
2019-09-03 12:01 ` Sebastian Moeller [this message]
2019-09-03 12:05 ` Mikael Abrahamsson
2019-09-03 13:05 ` Toke Høiland-Jørgensen
2019-09-04 19:48 ` Kenneth Porter
[not found] <mailman.587.1567520500.1240.bloat@lists.bufferbloat.net>
2019-09-03 15:21 ` Rich Brown
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=1B771A2B-FCBD-4305-B89C-6BD7B35976AE@gmx.de \
--to=moeller0@gmx.de \
--cc=bloat@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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