tummy.com

I've been thinking about the best way to do this, and I too didn't want to rely on having a backup script running all the time. Windows seems to have a low-level api for querying the filesystem/vfs for changes since you last looked: http://msdn.microsoft.com/en-us/library/windows/desktop/aa363798(v=vs.… And BTRFS has some ability to do this with find-new: http://www.tummy.com/blogs/2010/11/01/fun-with-btrfs-what-files-have-c… It's nice that btrfs has these new interesting features, also see send/receive, but it's not available in the vfs, and I suppose never will be.

Python and vim: Two great tastes that go together (slides): http://www.tummy.com/Community/Presentations/vimpython-20070225/vim.ht…

Generally pretty solid advice. I say that as someone who is known for solving tough wireless problems. :-) On the cable termination part: I've (mostly) stopped crimping cables because I've had too many go flaky and don't have 4-5 figure testing equipment. One thing I'll add is that there are ends for solid conductor and stranded, make SURE you have the right ones for the cable you are using. These days I always just put on keystone ends and then use commercial patch cables from there. I've had very good luck. I'd recommend against the advice to use a screw driver to punch them down, the Leviton ones I prefer you just put the cap on and they punch down themselves. The random ones I get from Ace Hardware have a little punch tool included. One additional recommendation I have is to put 5GHz radios in each space. 5GHz has more spectrum, and less interference, but it penetrates drywall significantly worse. But that's a good thing, because it cuts down on interference from your neighbors. Beware of microwave ovens, baby monitors, cordless phones (last 2 more in residential areas). They can be intermittent interference, and won't show up on the non-commercial spectrum analyzers. Our 2.4GHz used to go out when we'd run our brand new microwave. But it would also go out at other times, possibly when a neighbor ran theirs? 2.4GHz penetrates buildings quite well, which kind of sucks. My credentials: https://www.tummy.com/articles/pycon2012-network/

I don't think that 4.4.4.4 is a current DNS server. Perhaps you mean 8.8.4.4 or 4.2.2.4? 4.2.2.X was originally intended to be 4.4.4.4, but it didn't happen: https://www.tummy.com/articles/famous-dns-server/

Hopefully, this will become a recurring annual event where significant progress gets made on language development. I don't think we've had a gathering of this many Python core developers for a full week since the 2006 "need for speed" sprint in Reykjavik. https://www.tummy.com/blogs/2006/05/29/wrap-up-of-the-python-need-for-…

The PyCon people have historically done a number of detailed blogs on running high capacity/utilization wireless networks. http://www.tummy.com/articles/pycon2010-network/ http://serverfault.com/questions/72767/why-is-internet-access-and-wi-f…

8.8.8.8 is public DNS from Google. 4.2.2.2 is private DNS from Level3; see eg http://www.tummy.com/articles/famous-dns-server/ for a history.

I see that Level 3 is on the list. Please don't use Level 3 DNS[0]. They have no obligation to provide DNS services except to Level 3 customers[1], they don't like providing those services, and they have been known to hijack DNS requests to inject ads and other services[2] for unauthorized users. [0] http://www.tummy.com/articles/famous-dns-server/ [2] And if you're a Level 3 customer, you're probably not using this list [2] http://james.bertelson.me/blog/2014/01/level-3-are-now-hijacking-faile…

Seems reasonable. Those servers were never intended for widespread public use, so they may as well make back some funds for upkeep, and maybe encourage some more-technical users to switch away. Here's a blog post with some background on these servers: http://www.tummy.com/articles/famous-dns-server/

For vim scripting with Python: http://www.tummy.com/presentations/vimpython-20070225/

> other public DNS services except for Level 3's 4.2.2.1 Level 3 doesn't actually run a public DNS service, they run DNS servers that happen to permit requests from non-customers. You'd be well advised not to use it outside L3's network. http://www.tummy.com/Community/Articles/famous-dns-server/

http://www.tummy.com/Community/Articles/pycon2010-network/ peaked at ~600 people.

4.4.4.4 was what they originally wanted to set up DNS on (The guys behind 4.2.2.[1-6] that is ...) however those are not Verizon's or GTE's name servers, there is no resolver running on that IP address, it is on 4.2.2.2, and they are Level 3's name servers which they anycast for use on their network by their customers. For a bit of the history behind it check out this site: http://www.tummy.com/Community/Articles/famous-dns-server/ Using the DNS server is not suggested, since it is not officially a public DNS server, and Level 3 could cease the service at any time (in all likelihood that is very slim, since they have been telling their customers to use them for years now). Since they are anycast it will reach the closest server to your location when you query that DNS, and as such using it shouldn't be too big of a deal, whether you are a customer or not.

Much better exposition here: http://www.tummy.com/Community/Articles/pycon2008-network/

You might want to take a look at tummy.com http://www.tummy.com/Hosting/ You can e-mail them to ask about your needs

Sure, that's Level 3's official position. Unofficially, everyone uses it and there is clearly someone inside making the deliberate decision to keep it publicly available. https://www.tummy.com/articles/famous-dns-server/ As I said, the crux of the problem isn't Google's "blocking", but rather making it intermittent. Obviously it's well within their rights to play whatever games they want - drop every other packet, vary the latency based on your IP, duplicate packets, or make it appear some queue occasionally holds your packets for 3 seconds. It's also within their rights to redirect all DNS lookups to an April Fool's page. And to do any of this selectively based on how many different Google services you use. But that is not what any user expects, and in the end that's all protocols are - expectations. To me, the pushback I've gotten here fits right in with Surveillance Valley's general attitude of shirking responsibility with some fine print disclaimer, knowing full well what the constructive situation is. "I'm just going to go like this [spinning arms], it's not my fault if you walk into me". If you can't see how people would expect to be able to reliably ping 8.8.8.8, or how intermittently dropping pings causes confusion (as in the original comment above), then I can't help you.