Willing to relocate: Temporarily

Technologies:

I’m looking for 3- to 12-month contracting opportunities (corp-to-corp), anywhere in the U.S., with organizations looking to move some or all of their infrastructure on-prem.

I can...

Design reliable, secure, scalable, and cost-effective compute, storage, and networking that’s tailored to the needs of your business, using open source software, open weight LLMs, and off-the-shelf hardware.

Find suitable colocation host(s) and negotiate agreements for space, power, bandwidth, and insurance; or hire and supervise a licensed general contractor for building out a server room in your office or other facility.

Get the best deals on equipment, cabling, transportation, and everything else.

Hire and supervise temporary labor for the buildout (“rack and stack”).

Bootstrap networking, storage, cluster management, and Gitops systems. I have lots of experience running Kubernetes on bare metal, arranging BGP peering at public interconnection points, and connecting private clouds to public ones.

Perform initial validation and load testing, and help you migrate services from public clouds or SaaS providers.

Provide training and consultation on SRE best practices, observability, oncall rota, etc.

Resume/CV:

I have 30 years of experience in ISP, web, and related businesses, including as a Technical Program Manager for Google SRE. I started an ISP in 1996, back when all that was needed to do so was a bank of modems and a Linux box or two. I led data center buildouts for several dot coms—including a major social networking site, Bebo—in the late 90s and early 2000s, before the “cloud” existed, and I have tons of experience in the intervening years writing software and operating production services on all of the major hyperscalers. I had a stint managing wifi buildouts in hotels all over the country, where I learned the ins and outs of finding and working with skilled and reliable tradespeople. As the founder of two startups, I know how to be scrappy and move fast in a high-growth environment; I’ve also been an employee and consultant embedded in more mature organizations, always with a reputation for getting things done.

Email: dave at pifke dot org

This is also why I hate interview processes where my co-interviewers want to debrief immediately, or when I have a recruiter breathing down my neck as soon as the call ends.

"Neither a sender nor any person acting on behalf of a sender may require that any recipient pay any fee, provide any information other than the recipient's electronic mail address and opt-out preferences, or take any other steps except sending a reply electronic mail message or visiting a single Internet Web page"

https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C...

A simple reading says, no. But I guess they don't want to put that in writing.

They're suing Florida residents with no ties to California for linking to pictures of guns on the internet.

They will likely lose, but the goal is not to win, it's to score points with their political base and maybe bankrupt the defendants with legal fees.

I once wrote to the FTC for guidance as to whether or not this included requiring unsubscribers to solve a CAPTCHA or disable adblockers or enable Javascript, but did not get a response. I believe the law is plain with regards to this, but a lot of companies seem to be willing to risk it.

See: https://www.ecfr.gov/current/title-16/chapter-I/subchapter-C...

   $ host -t mx example.com
   example.com mail is handled by 0 .

  news.ycombinator.com##:matches-path(/^/item\?id=/) tr a.hnuser:has-text(/^dpifke$/):upward(tr)

That's a poor submission, because by the time most people click on it, Github will no longer be down.

There might be an interesting discussion to be had about outages at Github, but the better submission would be an article or blog post about the outage, not just a link to the site and a three-word title.

If someone wants to write an article or blog post about this news broadcast, which links to "hard facts and analysis not available through popular channels," that seems like it might be a worthwhile submission. But just a link to the broadcast by itself is not leading to interesting or on-topic conversation—the top comment right now is an ad hominem attack against Larry Ellison, without any supporting facts or analysis that he had anything to do with this story at all.

I would be more sympathetic to the argument that this is relevant if the submission was an article about media censorship, or CBS's audience or leadership, and how said censorship, audience, or leadership relates to technology or emerging trends in media.

But this is literally just a controversial TV news broadcast, that people of one political persuasion say was "censored" and people of another political persuasion say was held off the air "temporarily" until it met network fact-checking standards. That sort of political bickering is most uninteresting, and is most definitely not why I've been reading HN for the past few decades.

Gay porn is censored in a lot of Muslim countries, that doesn't make it on-topic for HN.

If they'd cover it on TV news, it's probably off-topic.

This submission is literally a TV news broadcast.

There are lots of other places on the internet where this is on-topic, I wish people would have their debates there instead.

(I don't actually know if that is how this page came about, but it seems similar to other wiki pages I've seen used for such a purpose.)

But you probably don't want to be investigated for either.

Third link on the page ("read the long story") points to https://triskweline.de/unpoly-rugb/, which renders as a blank page with NoScript enabled.

Sigh.

(quoting https://news.ycombinator.com/newsguidelines.html)

https://h-cpc.cat.com/cmms/v2?f=subfamily&it=group&cid=402&l...

https://www.activepower.com/

...and probably others.

(A couple of decades ago I worked for a company that was a tenant at a datacenter that used these instead of batteries; it's not new or particularly exotic technology.)

And an in-progress proposal to make these various "bubble" functions have consistent semantics: https://github.com/golang/go/issues/76477

(As an aside, the linked blog series is great, but if you're interested in new Go features, I've found it really helpful to also subscribe to https://go.dev/issue/33502 to get the weekly proposal updates straight from the source. Reading the debates on some of these proposals provides a huge level of insight into the evolution of Go.)