From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] I've always liked the idea of doing up building-wide networks
Date: Fri, 18 Jul 2014 16:25:02 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1407181622190.17284@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw7-5tPYxCH9t=R0sdcmb3SHGuWyucaTGLy=0pbneQpy=Q@mail.gmail.com>
On Fri, 18 Jul 2014, Dave Taht wrote:
> ... In particular when it came to getting minimal interference on all
> the wifi access points. It is better to have fewer, better wifi APs
> with a co-ordinated channel allocation strategy in an apartment
> building than everybody installing one willy-nilly.
the key is the co-ordinated channel allocation, beyond that it can be better to
have more, "worse" wifi APs than fewer "better" ones to reduce interference.
> http://www.frankston.com/public/?name=20140717-0146
looks interesting
> BTW: When I find an interesting link, these days, I tend to just put
> it on my g+ rather than the email lists, and tend to feel I'm wasting
> other people's bandwidth by doing it on the list - although sometimes
> a good discussion is sparked. Should I stop forwarding stuff like this
> (and the mit paper) to the list?
to the list, even if it's a link I don't care about, it's easier to delete it
along with other e-mail than to go to G+ and look at it.
Also, remember that people's G+ feeds show a sampling of what other people post,
so some people will miss it if you only post it to G+
David Lang
next prev parent reply other threads:[~2014-07-18 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-18 16:13 Dave Taht
2014-07-18 16:46 ` David Personette
2014-07-18 17:35 ` Alijah Ballard
2014-07-18 23:25 ` David Lang [this message]
2014-07-19 0:31 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1407181622190.17284@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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