OP's project is literally the reverse of taking a traditional desktop software, e.g. a graphic editor, and making it into a web app. Here, it's something that naturally belongs to a web site, but instead packed up into an installable desktop app.
I'd be really curious to see the rationale behind this.
I've been using some web-based tools. Somehow, they don't last (ie. namemesh, or domainsfortherestofus that @pwdisswordfish8 mention went offline for sometimes).
Then I thought having a desktop app would be great. For the long term, I don't have to worry the site is down.
This still 100% relies on their servers being up, which is no different than a website. So you absolutely still have to worry about their servers being down, which makes it pointless.
Exactly. The author appears to be telling you (you being jaywalk) that the application only requires talking out to Whois servers, and does not rely on any application/webserver…
To me the ultimate key to avoiding superfluous comments like the ones you refer to, and resulting ones like yours, would be to add a tag into the subject line when presenting Software, like [Electron]. That would also be helpful for other categories, like [subscription], [ClosedSource], etc..
Maybe they just wanted to play around with Electron, they don't owe you anything.