From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] SEO question
Date: Tue, 27 May 2014 21:14:39 -0700 [thread overview]
Message-ID: <CALQXh-PGMVFnEzoxdRHqnT+iftC54UswM3QncGjY8EBbP4t+ng@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4KyY6WkiAZPdCfYrACuPozE+ba=sZxUE8XxU8XidVbQA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
I _think_ it was the comcast keyword. That or a +1 by Yonatan Zunger
(Google+ lead), which got implicitly shared to a wider audience... I'm
glad to have gotten us some visibility into this (I started revising for
clarity as the exposure increased).
btw, I'm about to do those tests with PIE you asked for...
-Aaron
On Tue, May 27, 2014 at 7:28 PM, Dave Taht <dave.taht@gmail.com> wrote:
> aaron got 47+s and 14 reshares on this...
>
> https://plus.google.com/+AaronWood77/posts/NsyV9z3RMvV
>
> which I think is more than I've ever got. Way to go aaron?
>
> Was it the comcast keyword?
>
> One of the things that frustrates me, is even after all this time, I
> don't see more than 56,000 refs to bufferbloat on google when I search
> for the term. "Qos" gets a lot more hits,
> aqm not so much. Maybe in order to crawl into people's conciousness more we
> need to mention qos more? other phrases when people think of lag?
>
> Long overdue is a couple more magazine articles, but we needz more
> science first.
>
> --
> Dave Täht
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 1946 bytes --]
prev parent reply other threads:[~2014-05-28 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 2:28 Dave Taht
2014-05-28 4:14 ` Aaron Wood [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/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=CALQXh-PGMVFnEzoxdRHqnT+iftC54UswM3QncGjY8EBbP4t+ng@mail.gmail.com \
--to=woody77@gmail.com \
--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