Tvheadend is pretty good these days. The only thing in your list that I haven't seen any evidence of is commercial skipping.
I've just migrated off mythtv onto tvheadend and kodi and because they didn't have a great legacy of old analog tuners and other crazy, the setup for a bunch of DVB-T and DVB-S tuners makes a ton more sense than the gymnastics you had to do to map different multiplexes to specific tuners.
Get off my lawn! =)
Check out the IPv4 address space consumption graphs at http://www.potaroo.net/tools/i..., there is no new space for you in North America. In fact the only place there is still new space for you is in the African region.
See the 1
Noone is going to make anyone give up their old
It's all over man.
I'm loving the irony of you letting people know where the link is to the comments inside the comments section.
The AC braintrust has done well.
Please return the user interface to how it was. You are just pissing the long term userbase off.
Pulling out the read more link is like pulling the start button / menu from windows 8. It is a user interface disaster because it's not obvious w\
here you should click for the comments.
Slashdot has always been about the comments, if you minimise them by obfuscating the link to them you are left with the news stories from reddit \
a couple of days late and some obvious paid advertising plants.
Implementing aspects of the failed beta interface piecemeal with no discussion seems a bit underhanded.
If you aren't lucky you might succeed at killing slashdot which would be a shame.
The mind just boggles at how incredibly futile it is going to be googling for help on an app called 'Software'. I think the gnome guys have gone from mild contempt for the user to rabid hate and fury.
ditto regarding the badly disguised spam stuff.
I was here before there were user id's and I just happened to get in pretty early the day they opened registrations.
I get Sydney because that is one of the only places that is approximately 30ms away. The details on what the traceroute's actually had in them are fuzzed away by the reporter, so you can't rely on them to say anything in particular.
Anycast nodes switching about could look a whole lot like the latency just going up to the uninitiated. Most internet providers don't actually have a huge say in which anycast node for a service gets chosen by their network unless they actually have a local node in their own network.
To address the issue in the article, I expect that if Chorus / Telecom received a request to tap your connection you will never know that they have tapped it. The dark fibre circuits we have through them are provisioned on day one with an optical tap that is configured to direct a small percentage of the light to any gear that they might one day connect to it. The latency would be completely unaffected.
What makes more sense given the story is that Dotcom was on a fast fibre tail using a service that was actually in Sydney somewhere ( ~30ms away ) and for whatever reason this service switched to a node in the middle of the USA which could be 180ms away. Nothing there to do with taps or government conspiracies. They may well have been tapping his circuit as well, but the latency won't be anything to do with it. Even if they did have to divert his connection through some GCSB site, the latency would not be as high as 180ms.
As far as ping times to perth, from the same box in skytower:
[ ~ ]$ ping www.perthix.com
PING www.perthix.com (184.108.40.206) 56(84) bytes of data.
64 bytes from 220.127.116.11: icmp_seq=1 ttl=120 time=81.3 ms
64 bytes from 18.104.22.168: icmp_seq=2 ttl=120 time=80.1 ms
64 bytes from 22.214.171.124: icmp_seq=3 ttl=120 time=81.2 ms
--- www.perthix.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 80.181/80.933/81.383/0.628 ms
I've got my own access card for Level 47 and 48 of Sky tower, I'm aware of exactly what it is and why we decided to buy co-location space up there.
Our connection from skytower has to go a way across town before it hits the southern cross landing station, so the best case latency across southern cross is a bit lower again.
My point earlier on was that you can get anywhere return trip in New Zealand on a fibre circuit in under 35ms. Add the 24ms to get across to Australia or the 120ms to get to San Jose and you still don't get to 180ms unless you are using ADSL2+ or cable. Our POP in Christchurch is 20ms from Skytower in Auckland.
I get 24ms between a host in our network physically in Skytower in Auckland and a host in a Vocus datacenter in Sydney.
[ ~ ]$ ping ns03.vocus.net.au
PING ns03.vocus.net.au (126.96.36.199) 56(84) bytes of data.
64 bytes from isv02.syd01.nsw.VOCUS.net.au (188.8.131.52): icmp_seq=1 ttl=55 time=24.8 ms
64 bytes from isv02.syd01.nsw.VOCUS.net.au (184.108.40.206): icmp_seq=2 ttl=55 time=24.6 ms
64 bytes from isv02.syd01.nsw.VOCUS.net.au (220.127.116.11): icmp_seq=3 ttl=55 time=24.7 ms
--- ns03.vocus.net.au ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 24.698/24.761/24.872/0.150 ms
200 is totally awful! How much of that is made up by the last mile latency?
At the place I work, I would accept as a fault any report from a customer of latency of 200ms to anywhere physically in New Zealand ( aside from end customer tail latency ). Most ISP's in New Zealand peer at either WIX or APE or both and we pay extortionate rates for paid peering with Telecom and TelstraClear to handle the two exceptions to that rule.
The worst case for us is that we have an end customer in Christchurch that is talking to an end customer in Christchurch of an ISP that only peers with us in Auckland. Even that only means about 40ms worst case plus the latency of the tail circuits.
A debugged program is one for which you have not yet found the conditions that make it fail. -- Jerry Ogdin