From: Jonathan Morton <chromatix99@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Two d-link products tested for bloat...
Date: Fri, 20 Feb 2015 10:47:52 +0200 [thread overview]
Message-ID: <CAJq5cE0d_c3=uh6AXMs9u1Y25yrnwaChqArHj-GeEBgOJ34mvw@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-PT-RaAp=S=ug77VtOE9SR8Eh_UkVmUnY70H46pHY=Lhg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2729 bytes --]
Out of curiosity, perhaps you could talk to A&A about their FireBrick
router. They make a big point of having written the firmware for it
themselves, and they might be more interested in having researchers poke at
it in interesting ways than the average big name. A&A are an ISP, not a
hardware manufacturer by trade.
Meanwhile, I suspect the ultimate hardware vendors don't care because their
customers, the big brands, don't care. They in turn don't care because
neither ISPs nor consumers care (on average). A coherent, magazine style
review system with specific areas given star ratings might have a chance of
fixing that, if it becomes visible enough. I'm not sure that a rant blog
would gain the same sort of traction.
Some guidance can be gained from the business of reviewing other computer
hardware. Power supplies are generally, at their core, one of a few
standard designs made by one of a couple of big subcontractors. The quality
of the components used to implement that design, and ancillary hardware
such as heatsinks and cabling, are what distinguish them in the
marketplace. Likewise motherboards are all built around a standard CPU
socket, chipset and form factor, but the manufacturers find lots of little
ways to distinguish themselves on razor thin margins; likewise graphics
cards. Laptops are usually badly designed in at least one stupid way
despite the best efforts of reviewers, but thanks to them it is now
possible to sort through the general mess and find one that doesn't
completely suck at a reasonable price.
As for the rating system itself:
- the Communications Black Hole, for when we can't get it to work at all.
Maybe we can shrink a screen grab from Interstellar for the job.
- the Tin Cans & String, for when it passes packets okay (out of the box)
but is horrible in every other important respect.
- the Carrier Pigeon. Bonus points if we can show it defecating on the
message (or the handler's wrist).
- the Telegraph Pole (or Morse Code Key). Maybe put the Titanic in the
background just to remind people how hard they are failing.
- the Dial-Up Modem. Perhaps products which become reliable and useful if
the user installs OpenWRT should get at least this rating.
- the Silver RJ45, for products which contrive to be overall competent in
all important respects.
- the Golden Fibre, for the very best, most outstanding examples of best
practice, without any significant faults at all. Bonus Pink Floyd reference.
I've been toying with the idea of putting up a website on a completely
different subject, but which might have similar structure. Being able to
use the same infrastructure for two different sites might spread the costs
in an interesting way...
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 3003 bytes --]
next prev parent reply other threads:[~2015-02-20 8:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 2:04 Dave Taht
2015-02-20 5:32 ` Aaron Wood
2015-02-20 8:47 ` Jonathan Morton [this message]
2015-02-20 9:03 ` Dave Taht
2015-02-20 17:20 ` [Bloat] [Cerowrt-devel] " dpreed
2015-02-26 0:00 ` [Bloat] " Isaac Konikoff
2015-02-26 0:18 ` Jonathan Morton
2015-02-26 0:23 ` Dave Taht
2015-02-26 4:22 ` Isaac Konikoff
2015-02-26 4:37 ` Dave Taht
2015-02-27 5:00 ` Isaac Konikoff
2015-02-27 5:12 ` Dave Taht
2015-02-27 19:15 ` Isaac Konikoff
2015-02-26 16:56 ` Stephen John Smoogen
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='CAJq5cE0d_c3=uh6AXMs9u1Y25yrnwaChqArHj-GeEBgOJ34mvw@mail.gmail.com' \
--to=chromatix99@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=woody77@gmail.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