I've noticed it didn't work yesterday, either. Tested from two locations. California: li16x-xxx:~# telnet fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C li16x-xxx:~# traceroute6 fb.me traceroute to fb.me (2a03:2880:2110:df01:face:b00c:0:8), 30 hops max, 80 byte packets 1 2600:3c01:ffff:0:ca4c:75ff:fef5:d63f (2600:3c01:ffff:0:ca4c:75ff:fef5:d63f) 206.674 ms 206.681 ms 206.639 ms 2 10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1) 0.668 ms 0.660 ms 0.653 ms 3 10gigabitethernet1-2.core1.sjc2.he.net (2001:470:0:2f::2) 0.850 ms 0.842 ms 0.973 ms 4 2001:504:0:1:0:3:2934:2 (2001:504:0:1:0:3:2934:2) 1.758 ms 51.504 ms 2001:470:0:14a::2 (2001:470:0:14a::2) 0.907 ms 5 ae0.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::9) 1.065 ms ae1.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::15) 1.953 ms 1.454 ms 6 ae6.bb01.frc1.tfbnw.net (2620:0:1cff:dead:beef::aa) 69.617 ms 69.712 ms 69.723 ms 7 ae1.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::93) 67.326 ms ae2.dr04.frc1.tfbnw.net (2620:0:1cff:dead:beef::1de) 66.698 ms ae2.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::9b) 66.627 ms 8 po1019.csw13b.frc1.tfbnw.net (2620:0:1cff:dead:beef::12bd) 68.058 ms 67.433 ms 67.786 ms 9 * * * 10 * * * 11 * * * Europe: Cns# telnet -6 fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C Cns# traceroute6 fb.me traceroute6 to fb.me (2a03:2880:2110:df01:face:b00c:0:8) from 2001:470:XXXX::, 64 hops max, 12 byte packets 1 cnst-3.tunnel.tserv6.fra1.ipv6.he.net 9.78 ms 9.188 ms 8.916 ms 2 gige-g2-20.core1.fra1.he.net 10.158 ms 6.491 ms 6.453 ms 3 ae1.br01.fra1.tfbnw.net 29.037 ms 7.278 ms 6.869 ms 4 ae1.bb01.fra2.tfbnw.net 7.048 ms 6.844 ms 6.812 ms 5 ae11.bb02.iad2.tfbnw.net 94.231 ms 93.68 ms 94.441 ms 6 ae4.bb02.frc1.tfbnw.net 107.464 ms 107.978 ms 116.968 ms 7 ae2.dr01.frc1.tfbnw.net 104.31 ms ae40.dr01.frc1.tfbnw.net 103.572 ms ae40.dr02.frc1.tfbnw.net 124.374 ms 8 ae2.dr02.frc1.tfbnw.net 103.912 ms po1021.csw13b.frc1.tfbnw.net 104.85 ms 105.569 ms 9 * * * 10 * * * 11 * * * I have no explanation how they could possibly be down for more than a day, even if only on IPv6; perhaps only he.net is affected? C.
On 18 May 2013 21:45, Constantine A. Murenin <mureninc@gmail.com> wrote:
I've noticed it didn't work yesterday, either.
Tested from two locations.
California:
li16x-xxx:~# telnet fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C li16x-xxx:~# traceroute6 fb.me traceroute to fb.me (2a03:2880:2110:df01:face:b00c:0:8), 30 hops max, 80 byte packets 1 2600:3c01:ffff:0:ca4c:75ff:fef5:d63f (2600:3c01:ffff:0:ca4c:75ff:fef5:d63f) 206.674 ms 206.681 ms 206.639 ms 2 10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1) 0.668 ms 0.660 ms 0.653 ms 3 10gigabitethernet1-2.core1.sjc2.he.net (2001:470:0:2f::2) 0.850 ms 0.842 ms 0.973 ms 4 2001:504:0:1:0:3:2934:2 (2001:504:0:1:0:3:2934:2) 1.758 ms 51.504 ms 2001:470:0:14a::2 (2001:470:0:14a::2) 0.907 ms 5 ae0.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::9) 1.065 ms ae1.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::15) 1.953 ms 1.454 ms 6 ae6.bb01.frc1.tfbnw.net (2620:0:1cff:dead:beef::aa) 69.617 ms 69.712 ms 69.723 ms 7 ae1.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::93) 67.326 ms ae2.dr04.frc1.tfbnw.net (2620:0:1cff:dead:beef::1de) 66.698 ms ae2.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::9b) 66.627 ms 8 po1019.csw13b.frc1.tfbnw.net (2620:0:1cff:dead:beef::12bd) 68.058 ms 67.433 ms 67.786 ms 9 * * * 10 * * * 11 * * *
Europe:
Cns# telnet -6 fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C Cns# traceroute6 fb.me traceroute6 to fb.me (2a03:2880:2110:df01:face:b00c:0:8) from 2001:470:XXXX::, 64 hops max, 12 byte packets 1 cnst-3.tunnel.tserv6.fra1.ipv6.he.net 9.78 ms 9.188 ms 8.916 ms 2 gige-g2-20.core1.fra1.he.net 10.158 ms 6.491 ms 6.453 ms 3 ae1.br01.fra1.tfbnw.net 29.037 ms 7.278 ms 6.869 ms 4 ae1.bb01.fra2.tfbnw.net 7.048 ms 6.844 ms 6.812 ms 5 ae11.bb02.iad2.tfbnw.net 94.231 ms 93.68 ms 94.441 ms 6 ae4.bb02.frc1.tfbnw.net 107.464 ms 107.978 ms 116.968 ms 7 ae2.dr01.frc1.tfbnw.net 104.31 ms ae40.dr01.frc1.tfbnw.net 103.572 ms ae40.dr02.frc1.tfbnw.net 124.374 ms 8 ae2.dr02.frc1.tfbnw.net 103.912 ms po1021.csw13b.frc1.tfbnw.net 104.85 ms 105.569 ms 9 * * * 10 * * * 11 * * *
I have no explanation how they could possibly be down for more than a day, even if only on IPv6; perhaps only he.net is affected?
li16x-xxx:~# telnet www.facebook.com http Trying 2a03:2880:2050:1f01:face:b00c:0:9... Connected to star.c10r.facebook.com. Escape character is '^]'. ^CConnection closed by foreign host. li16x-xxx:~# telnet fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C So, this is only fb.me that's affected, not www.facebook.com. Doubtful that only he.net customers are affected, probably a world-wide issue. C.
On Sat, 2013-05-18 at 21:51 -0700, Constantine A. Murenin wrote:
I have no explanation how they could possibly be down for more than a day, even if only on IPv6; perhaps only he.net is affected?
tried a server in UK and US, facebooks ipv6 issue 4 works fine telnet fb.me http Trying 173.252.110.27... Connected to fb.me. Escape character is '^]'.
On Sat, May 18, 2013 at 09:45:18PM -0700, Constantine A. Murenin wrote:
I've noticed it didn't work yesterday, either.
Tested from two locations.
California:
li16x-xxx:~# telnet fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C li16x-xxx:~# traceroute6 fb.me traceroute to fb.me (2a03:2880:2110:df01:face:b00c:0:8), 30 hops max, 80 byte packets 1 2600:3c01:ffff:0:ca4c:75ff:fef5:d63f (2600:3c01:ffff:0:ca4c:75ff:fef5:d63f) 206.674 ms 206.681 ms 206.639 ms 2 10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1) 0.668 ms 0.660 ms 0.653 ms 3 10gigabitethernet1-2.core1.sjc2.he.net (2001:470:0:2f::2) 0.850 ms 0.842 ms 0.973 ms 4 2001:504:0:1:0:3:2934:2 (2001:504:0:1:0:3:2934:2) 1.758 ms 51.504 ms 2001:470:0:14a::2 (2001:470:0:14a::2) 0.907 ms 5 ae0.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::9) 1.065 ms ae1.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::15) 1.953 ms 1.454 ms 6 ae6.bb01.frc1.tfbnw.net (2620:0:1cff:dead:beef::aa) 69.617 ms 69.712 ms 69.723 ms 7 ae1.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::93) 67.326 ms ae2.dr04.frc1.tfbnw.net (2620:0:1cff:dead:beef::1de) 66.698 ms ae2.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::9b) 66.627 ms 8 po1019.csw13b.frc1.tfbnw.net (2620:0:1cff:dead:beef::12bd) 68.058 ms 67.433 ms 67.786 ms 9 * * * 10 * * * 11 * * *
Europe:
Cns# telnet -6 fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C Cns# traceroute6 fb.me traceroute6 to fb.me (2a03:2880:2110:df01:face:b00c:0:8) from 2001:470:XXXX::, 64 hops max, 12 byte packets 1 cnst-3.tunnel.tserv6.fra1.ipv6.he.net 9.78 ms 9.188 ms 8.916 ms 2 gige-g2-20.core1.fra1.he.net 10.158 ms 6.491 ms 6.453 ms 3 ae1.br01.fra1.tfbnw.net 29.037 ms 7.278 ms 6.869 ms 4 ae1.bb01.fra2.tfbnw.net 7.048 ms 6.844 ms 6.812 ms 5 ae11.bb02.iad2.tfbnw.net 94.231 ms 93.68 ms 94.441 ms 6 ae4.bb02.frc1.tfbnw.net 107.464 ms 107.978 ms 116.968 ms 7 ae2.dr01.frc1.tfbnw.net 104.31 ms ae40.dr01.frc1.tfbnw.net 103.572 ms ae40.dr02.frc1.tfbnw.net 124.374 ms 8 ae2.dr02.frc1.tfbnw.net 103.912 ms po1021.csw13b.frc1.tfbnw.net 104.85 ms 105.569 ms 9 * * * 10 * * * 11 * * *
I have no explanation how they could possibly be down for more than a day, even if only on IPv6; perhaps only he.net is affected?
Taken from my home machine (Mountain View, CA; Comcast connection); only IPv4, sorry: $ telnet fb.me 80 Trying 173.252.110.27... Connected to fb.me. Escape character is '^]'. GET / HTTP/1.0 Host: fb.me HTTP/1.0 301 Moved Permanently Location: http://www.facebook.com/ Content-Type: text/html; charset=utf-8 X-FB-Debug: QataDVOUSq+vNlfgI3enUcTGQ86k+aJ3APJ2ledddJw= Date: Sun, 19 May 2013 05:17:48 GMT Connection: close Content-Length: 0 Connection closed by foreign host. $ mtr fb.me Packets Pings Host Loss% Snt Rcv Last Avg Best Wrst 1. gw.home.lan 0.0% 11 11 0.4 0.3 0.2 0.4 2. c-67-180-84-1.hsd1.ca.comcast.net 0.0% 11 11 16.6 24.6 9.2 40.0 3. te-0-0-0-12-ur05.santaclara.ca.sfba.comcast 0.0% 11 11 9.2 10.2 9.2 11.7 4. te-1-1-0-6-ar01.sfsutro.ca.sfba.comcast.net 0.0% 10 10 13.5 14.7 11.9 24.9 5. he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.ne 0.0% 10 10 13.7 16.6 13.7 23.0 6. xe-10-2-0.edge1.SanJose1.Level3.net 0.0% 10 10 43.3 37.2 22.3 54.7 7. vlan70.csw2.SanJose1.Level3.net 0.0% 10 10 79.6 81.6 79.4 91.4 8. ae-72-72.ebr2.SanJose1.Level3.net 0.0% 10 10 81.3 81.0 79.5 81.7 9. ae-2-2.ebr2.SanJose5.Level3.net 0.0% 10 10 81.9 81.0 79.4 82.6 10. ae-6-6.ebr2.LosAngeles1.Level3.net 0.0% 10 10 80.2 80.7 79.9 81.4 11. ae-3-3.ebr3.Dallas1.Level3.net 0.0% 10 10 81.6 81.1 79.8 81.6 12. ae-73-73.csw2.Dallas1.Level3.net 0.0% 10 10 80.6 80.9 80.0 83.0 13. ae-71-71.ebr1.Dallas1.Level3.net 0.0% 10 10 80.0 82.4 80.0 92.0 14. ae-2-2.ebr1.Miami1.Level3.net 0.0% 10 10 81.8 84.0 80.0 95.2 15. ae-1-51.edge4.Miami1.Level3.net 0.0% 10 10 79.8 89.5 79.8 130.2 16. TRINITY-COM.edge4.Miami1.Level3.net 0.0% 10 10 87.9 88.3 87.0 92.3 17. ??? 18. 24.244.158.2 0.0% 10 10 87.8 88.2 86.6 90.0 19. 208-87-35-103.securehost.com 0.0% 10 10 87.4 87.7 86.8 88.3 Seems ICMP traceroute should work to them, at least for IPv4. I can try from another destination if needed. Can you determine if this is a IPv6 vs. IPv4 thing? -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
Works fine over v4, just fails on v6. I connect to the same IPv6 address. nagios:/# wget -6 fb.me --2013-05-19 00:31:42-- http://fb.me/ Resolving fb.me... 2a03:2880:2110:df01:face:b00c:0:8 Connecting to fb.me|2a03:2880:2110:df01:face:b00c:0:8|:80... failed: Connection timed out. Retrying. --2013-05-19 00:32:04-- (try: 2) http://fb.me/ Connecting to fb.me|2a03:2880:2110:df01:face:b00c:0:8|:80... failed: Connection timed out. Retrying. --2013-05-19 00:32:27-- (try: 3) http://fb.me/ Connecting to fb.me|2a03:2880:2110:df01:face:b00c:0:8|:80... failed: Connection timed out. Retrying. nagios:/# tcptraceroute6 fb.me traceroute to edge-star6-ecmp-13-frc1.facebook.com (2a03:2880:2110:df01:face:b00c:0:8) from 2607:fe28:0:1000::5, port 80, from port 57831, 30 hops max, 60 bytes packets 1 router-core.mtcnet.net (2607:fe28:0:1000::1) 0.256 ms 0.213 ms 0.218 ms 2 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 0.224 ms 0.134 ms 0.136 ms 3 v6-premier.sxcy-mlx.fbnt.netins.net (2001:5f8:7f0a:2::1) 1.582 ms 1.556 ms 1.538 ms 4 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 5.657 ms 5.532 ms 5.569 ms 5 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 7.362 ms 7.364 ms 7.473 ms 6 v6-ins-kc2-po20.kmrr.netins.net (2001:5f8::8:2) 7.388 ms 7.356 ms 7.345 ms 7 v6-ins-kc1-po21.kmrr.netins.net (2001:5f8::14:1) 15.680 ms 7.440 ms 7.346 ms 8 sl-crs2-chi-te1-2-0-1.v6.sprintlink.net (2600:4::6) 16.969 ms 16.930 ms 16.850 ms 9 sl-st31-chi-bu-20.v6.sprintlink.net (2600:0:2:1239:144:232:1:104) 17.616 ms 17.489 ms 17.590 ms 10 2600:4:2000::f (2600:4:2000::f) 17.292 ms 17.340 ms 17.377 ms 11 ae1.bb02.ord1.tfbnw.net (2620:0:1cff:dead:beee::452) 17.565 ms 17.476 ms 17.524 ms 12 ae24.bb02.iad2.tfbnw.net (2620:0:1cff:dead:beef::1499) 38.345 ms 51.348 ms 35.481 ms 13 ae4.bb02.frc1.tfbnw.net (2620:0:1cff:dead:beef::c2) 49.026 ms 48.936 ms 48.869 ms 14 ae2.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::9b) 62.555 ms 45.535 ms 45.502 ms 15 po1022.csw13c.frc1.tfbnw.net (2620:0:1cff:dead:beef::12c1) 46.482 ms 46.301 ms 46.364 ms 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * ^C70% completed... -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Constantine A. Murenin Sent: Saturday, May 18, 2013 11:45 PM To: outages@outages.org Subject: [outages] fb.me is down I've noticed it didn't work yesterday, either. Tested from two locations. California: li16x-xxx:~# telnet fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C li16x-xxx:~# traceroute6 fb.me traceroute to fb.me (2a03:2880:2110:df01:face:b00c:0:8), 30 hops max, 80 byte packets 1 2600:3c01:ffff:0:ca4c:75ff:fef5:d63f (2600:3c01:ffff:0:ca4c:75ff:fef5:d63f) 206.674 ms 206.681 ms 206.639 ms 2 10gigabitethernet2-3.core1.fmt1.he.net (2001:470:1:1db::1) 0.668 ms 0.660 ms 0.653 ms 3 10gigabitethernet1-2.core1.sjc2.he.net (2001:470:0:2f::2) 0.850 ms 0.842 ms 0.973 ms 4 2001:504:0:1:0:3:2934:2 (2001:504:0:1:0:3:2934:2) 1.758 ms 51.504 ms 2001:470:0:14a::2 (2001:470:0:14a::2) 0.907 ms 5 ae0.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::9) 1.065 ms ae1.bb01.sjc1.tfbnw.net (2620:0:1cff:dead:beef::15) 1.953 ms 1.454 ms 6 ae6.bb01.frc1.tfbnw.net (2620:0:1cff:dead:beef::aa) 69.617 ms 69.712 ms 69.723 ms 7 ae1.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::93) 67.326 ms ae2.dr04.frc1.tfbnw.net (2620:0:1cff:dead:beef::1de) 66.698 ms ae2.dr02.frc1.tfbnw.net (2620:0:1cff:dead:beef::9b) 66.627 ms 8 po1019.csw13b.frc1.tfbnw.net (2620:0:1cff:dead:beef::12bd) 68.058 ms 67.433 ms 67.786 ms 9 * * * 10 * * * 11 * * * Europe: Cns# telnet -6 fb.me http Trying 2a03:2880:2110:df01:face:b00c:0:8... ^C Cns# traceroute6 fb.me traceroute6 to fb.me (2a03:2880:2110:df01:face:b00c:0:8) from 2001:470:XXXX::, 64 hops max, 12 byte packets 1 cnst-3.tunnel.tserv6.fra1.ipv6.he.net 9.78 ms 9.188 ms 8.916 ms 2 gige-g2-20.core1.fra1.he.net 10.158 ms 6.491 ms 6.453 ms 3 ae1.br01.fra1.tfbnw.net 29.037 ms 7.278 ms 6.869 ms 4 ae1.bb01.fra2.tfbnw.net 7.048 ms 6.844 ms 6.812 ms 5 ae11.bb02.iad2.tfbnw.net 94.231 ms 93.68 ms 94.441 ms 6 ae4.bb02.frc1.tfbnw.net 107.464 ms 107.978 ms 116.968 ms 7 ae2.dr01.frc1.tfbnw.net 104.31 ms ae40.dr01.frc1.tfbnw.net 103.572 ms ae40.dr02.frc1.tfbnw.net 124.374 ms 8 ae2.dr02.frc1.tfbnw.net 103.912 ms po1021.csw13b.frc1.tfbnw.net 104.85 ms 105.569 ms 9 * * * 10 * * * 11 * * * I have no explanation how they could possibly be down for more than a day, even if only on IPv6; perhaps only he.net is affected? C. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
On 18 May 2013 22:34, Frank Bulk <frnkblk@iname.com> wrote:
Works fine over v4, just fails on v6. I connect to the same IPv6 address.
Dunno about you, but my non-happy-eyeballs browser takes a couple of minutes before an fb.me link completes. I vaguely recall the same issue yesterday, which, if true, would be quite amusing for a site so prevalent to be down for so long. :-) Since becoming IPv6-enabled, this is by far not the first site that's stopped working at some point in time for me, due to my browser being IPv6-aware. People talk about publishers not turning on IPv6 for their domains, since there are misconfigured clients; I'd say IPv6 clients face a bigger problem, in the face of so many misconfigured servers. And fb.me is still down, BTW. C.
On Sat, 2013-05-18 at 22:55 -0700, Constantine A. Murenin wrote:
People talk about publishers not turning on IPv6 for their domains, since there are misconfigured clients; I'd say IPv6 clients face a bigger problem, in the face of so many misconfigured servers.
And fb.me is still down, BTW.
8 2620:0:1cff:dead:beef::12b5 286.407 ms 2620:0:1cff:dead:beef::12d1 289.605 ms 2620:0:1cff:dead:beef::105f 289.441 ms 9 * * * 10 * * * kinda the right addressing at least :) not that I care, given I dont facebook as i value my privacy
On 19 May 2013 00:32, Noel Butler <noel.butler@ausics.net> wrote:
On Sat, 2013-05-18 at 22:55 -0700, Constantine A. Murenin wrote:
People talk about publishers not turning on IPv6 for their domains, since there are misconfigured clients; I'd say IPv6 clients face a bigger problem, in the face of so many misconfigured servers.
And fb.me is still down, BTW.
8 2620:0:1cff:dead:beef::12b5 286.407 ms 2620:0:1cff:dead:beef::12d1 289.605 ms 2620:0:1cff:dead:beef::105f 289.441 ms
9 * * * 10 * * *
kinda the right addressing at least not that I care, given I dont facebook as i value my privacy
I use twitter, and people use fb.me links on twitter, which didn't work. Heh, finally someone must have noticed, and instead of fixing it for IPv6, they've just removed the AAAA record: li16x-xxx:~# telnet fb.me http Trying 173.252.110.27... Connected to fb.me. Escape character is '^]'. ^CConnection closed by foreign host. li16x-xxx:~# telnet -6 fb.me http telnet: could not resolve fb.me/http: Name or service not known But it's still amusing that it's been down for so long. I wonder how many hours (or possibly even days) it's been down for. :-) C.
On Sun, 2013-05-19 at 09:46 -0700, Constantine A. Murenin wrote:
I use twitter, and people use fb.me links on twitter, which didn't work.
I must be lucky, none of my shorteners have failed, so they cant post via fb ;)
Heh, finally someone must have noticed, and instead of fixing it for IPv6, they've just removed the AAAA record:
its facebook, its too hard to fix, like their (lack of) privacy.
Wait, a site that's dedicated to sharing your life isn't privacy oriented? You don't say. On May 19, 2013 5:20 PM, "Noel Butler" <noel.butler@ausics.net> wrote:
** On Sun, 2013-05-19 at 09:46 -0700, Constantine A. Murenin wrote:
I use twitter, and people use fb.me links on twitter, which didn't work.
I must be lucky, none of my shorteners have failed, so they cant post via fb [image: ;)]
Heh, finally someone must have noticed, and instead of fixing it for IPv6, they've just removed the AAAA record:
its facebook, its too hard to fix, like their (lack of) privacy.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
Actually, my own reason for not joining facebook is that, back in the day, they seemed to have required a registration to use any portion of the site whatsoever, and I didn't want to impose such contagious and exclusive conditions onto the people I want to share my content with. Their privacy problems come from having been providing too much privacy to start with (for whichever reasons), and then gradually reducing said privacy (as market conditions and priorities or philosophies have changed). C. On 19 May 2013 17:31, Mike Hale <eyeronic.design@gmail.com> wrote:
Wait, a site that's dedicated to sharing your life isn't privacy oriented? You don't say.
On May 19, 2013 5:20 PM, "Noel Butler" <noel.butler@ausics.net> wrote:
its facebook, its too hard to fix, like their (lack of) privacy.
Not trying to rain on anyone's parade (honest!), but: could you guys move this over to outages-discussion ? That list is better-suited for where this conversation is going. Respectfully, -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Sun, May 19, 2013 at 05:45:36PM -0700, Constantine A. Murenin wrote:
Actually, my own reason for not joining facebook is that, back in the day, they seemed to have required a registration to use any portion of the site whatsoever, and I didn't want to impose such contagious and exclusive conditions onto the people I want to share my content with.
Their privacy problems come from having been providing too much privacy to start with (for whichever reasons), and then gradually reducing said privacy (as market conditions and priorities or philosophies have changed).
C.
On 19 May 2013 17:31, Mike Hale <eyeronic.design@gmail.com> wrote:
Wait, a site that's dedicated to sharing your life isn't privacy oriented? You don't say.
On May 19, 2013 5:20 PM, "Noel Butler" <noel.butler@ausics.net> wrote:
its facebook, its too hard to fix, like their (lack of) privacy.
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
This is the outages list, not the discussion list guys =) Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 On Sun, May 19, 2013 at 8:45 PM, Constantine A. Murenin <mureninc@gmail.com>wrote:
Actually, my own reason for not joining facebook is that, back in the day, they seemed to have required a registration to use any portion of the site whatsoever, and I didn't want to impose such contagious and exclusive conditions onto the people I want to share my content with.
Their privacy problems come from having been providing too much privacy to start with (for whichever reasons), and then gradually reducing said privacy (as market conditions and priorities or philosophies have changed).
C.
On 19 May 2013 17:31, Mike Hale <eyeronic.design@gmail.com> wrote:
Wait, a site that's dedicated to sharing your life isn't privacy
oriented?
You don't say.
On May 19, 2013 5:20 PM, "Noel Butler" <noel.butler@ausics.net> wrote:
its facebook, its too hard to fix, like their (lack of) privacy.
Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (6)
-
Constantine A. Murenin -
Frank Bulk -
Jeremy Chadwick -
Josh Luthman -
Mike Hale -
Noel Butler