HN user

retlehs

243 karma

https://roots.io

https://benword.com

https://github.com/retlehs

Posts7
Comments65
View on HN

The link doesn’t load for me FYI. A web version would be in Go, reusing the TUI internals. All doable, just not where I want to spend my time right now. I’ll likely get to it at some point.

This was really just a personal tool I built because I got tired of parsing default whois output. Don’t have the bandwidth for a web UI right now, maybe down the road.

It’s not about making money. It’s more that there’s no real way for people to discover it by competing for visibility on whois-related searches against established sites.

The goal was a fast terminal tool, and I'm not ruling it out, but considering how hard it would be to compete in the SERPs with other whois sites, I don't think I'd spend the time on it right now

As others have noted, the emails frequently include the sender's actual GitHub username or organization in the body or signature.

Attribution isn't speculative. The DKIM/SPF headers show the messages are authenticated and sent through the company's own mail servers, signed by their domain. These are not spoofed "joe@legitbusiness.com" messages. I include the original headers in every abuse report.

In several cases I've engaged directly. One founder replied to my "stop spamming" email and later sent me a LinkedIn request. When the name in the signature, the GitHub profile, the authenticated sending domain, and the LinkedIn account all align, the hacked-account explanation no longer fits the facts.

There's a big ford in each driveway that hasn't hauled more than dogs and kids since the day it came home

I can't speak on Knoxville because I've only spent a day there, but I've spent a good bit of time around Amarillo mostly from driving between CO and TX over a hundred times, although not really in the suburbs.

Saw a lot of beat up trucks that looked like they were owned by blue collar folks and used for truck things. But of course there's also plenty of brodozers, which I'm assuming are also fairly common in Knoxville.

You shouldn't be hardcoding CSS/JS into the template files - look into wp_enqueue_style and wp_enqueue_script.

Could use a better directory structure, too. Assets should be in a different folder, things like the walker should be in a lib/includes folder.

Being a starter theme, it doesn't make sense to just reference the Bootstrap CSS from a CDN. Shouldn't you have the LESS files so people can easily make changes without having to do overrides in their CSS?

ps. It's "WordPress", not "Wordpress" (http://codex.wordpress.org/Function_Reference/capital_P_dang...)

Disclaimer: I made Roots (http://roots.io), a Bootstrap starter theme that's been around for a while

This happened to a friend who runs a DO server on July 22nd. The server had been running for several weeks when it was suddenly taken down out of nowhere for over 4 hours to "verify" the account. There wasn't any warning and my friend immediately provided what they had requested.

Their response? They shut down the server because of "unusual traffic" coming from the server which wasn't even being used yet.. but there was "outbound traffic about 977.38 Mbps at its peak at around 2013-07-22 14:50:00UTC"

They need to fully verify accounts before letting anyone create a server. You shouldn't just take down a server out of nowhere, for several hours, after it's been running for weeks.

Looks good, I've got few questions for you:

- Why put respond.js in the footer? (H5BP puts it up in the head with the call to Modernizr)

- Why self-close your meta and link tags if you're using HTML5?

- Why doesn't the image in the demo resize as you resize the window? (img { max-width: 100%; } fixes that)

This reminded me to put some more work into my lunch app (jQuery Mobile + Yelp API + Google Maps API) I've worked on a little bit for the same reason. Thanks :)