-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 19/01/15 11:01, Shane Kerr wrote:
> All,
> 
> On Tue, 06 Jan 2015 14:59:38 +0100 Mirjam Kuehne <[email protected]>
> wrote:
> 
>> We looked at tweets mentioning IPv4 and IPv6 and how they appear
>> on a map over time. It's great to see that IPv6-related tweets
>> are more popular. Find more information on RIPE Labs:
>> 
>> https://labs.ripe.net/Members/emileaben/visualising-ipv4-ipv6-tweets
>>
>>
>> 
If you have any questions or suggestions, please let us know.
> 
> Sadly twitter itself doesn't appear to support IPv6 yet (at least
> for their web stuff):
> 
> $ host -t aaaa twitter.com twitter.com has no AAAA record $ host -t
> aaaa www.twitter.com www.twitter.com is an alias for twitter.com.

Nothing in Alexa 1M list that resolves to the Twitter AS seems to have
IPv6.

They do have 3 IPv6 prefixes visible in routing though:
https://stat.ripe.net/widget/routing-status#w.resource=AS13414

I'd be very curious if these are just 'stakes in the ground' or if
these get some actual use. I haven't seen any recent IPv6 plans from
Twitter (quick search only found:
http://www.networkworld.com/article/2189085/lan-wan/many--name--sites-sitting-out-today-s-world-ipv6-launch.html
), and a quick asking around got me nothing.

I also didn't find any recent request to @twittereng to support #IPv6
that got any traction, so I just posted one (
https://twitter.com/meileaben/status/557854531401568258 ), maybe that
can bring it to their attention?

cheers,
Emile


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJUv4bkAAoJEKxthF6wloMO6K4QAIDEu7pdkmFeUSzlrVPN/+x9
Vzc1H/+x/vG7LetBqH+ckO+p5iO2SnQX9Wq6IfYBRycU4NXXDKd1ThpHMiwg1d+r
mS/LUl0tQNy3SmCRYgSxfGlTTatPtcyT/2cHd4QDRpWSUMGcDIGljqoLgNoU1dPC
ftVZjJvGQUTjllEVhkqpntnGp17nCc//8CtzgmH4Bmys4VCkeaLkwSnaWjm53rg3
cGyhR7K7lMBOdKVimHlkGXS8aPHj810r9CIkR3KoOzRLdTtpr8hzt/7alWo4VYau
zoheIL1Yt11fKR3MWuCt9sDjSE6nU4p54YX9NHO6HNfjAQWnBmxY72yOwX+N6Jhr
igvRKr6a2aMyZ3ZmAzIzFSuEGvQoEdvQVSeScfSF72hA+WWqL4Qus5wmRUDk8AqH
DSt2zedGLslpmGZApbvWuUhDA9e5oFJxNAI6fLpvzu66+81RPwqu4VvnE6ANXkvr
ozfhdF99OKrx+67KKTlg0L7VcEw/f59zeCR446HbqKpB9iNR1O1gLTWoCRhOjtIz
5B/wO7Lfwo5cL+cZ/zY8d/pJvElOgNUdTfEYinbWlBgCvZWTnVSuMDeIQqZguFSM
/YLayeOgScUkhEoSMRJxHQBmvEu9OxO8lohcDXUC/p5FLChb/WNif2KEEu7nuj/+
RvdifqNzYQ8zHGUlpfGH
=kpTE
-----END PGP SIGNATURE-----

Reply via email to