[Mixtape]

Just my $0.02 as a net/sysadmin for a small municipality in the US:

A big part of why we haven't been able/bothered to migrate to a proper .gov domain boils down to the amount of technical debt we'd need to pay back in the process of doing so. Everything that we do uses our non-.gov domain, namely our Office 365 connectors. On top of that, end users' day-to-day communications with the public make use of the existing domain. Modifying that in any capacity could prove disruptive to ongoing communications and potentially render them liable for dropping the ball somewhere. Not to mention that every single internet account ever created by staff using the current domain would need to be migrated or risk being lost forever.

Additionally, we're a small team. Only myself and one other individual would really have the technical knowledge to migrate our infrastructure. The opportunity cost involved would be massive. There are grants available to help us with this, but obtaining/using those can get complicated at times.

Ultimately, the pros just don't outweigh the cons enough to make a huge difference. From a purely academic angle, should we have a .gov TLD? Absolutely. In practice though, the residents and staff are familiar enough with the current one to render it a non-issue. The average non-technical user doesn't "see" "[municipality].[state].gov". They aren't familiar with the concept of a domain hierarchy at all. They just memorize "[municipality_website]" and move on with their day.

[massysett]

> They just memorize "[municipality_website]" and move on with their day.

I haven't even done that much, I couldn't tell you offhand the URL for my county government. I always just search in Google, which takes me right to the page I need (roads, solid waste, library, etc.)

[prmoustache]

> The average non-technical user doesn't "see" "[municipality].[state].gov". They aren't familiar with the concept of a domain hierarchy at all. They just memorize "[municipality_website]" and move on with their day.

That mean they can easily be redirected to a phishing website.

[Mixtape]

Absolutely, and that's a risk that we carry, especially in the public sector. That being said though, I don't know if adopting a better-regulated domain is itself enough to alleviate that.

The very unfortunate reality is that many (most?) users evaluate phishing attempts with the null hypothesis that "this is trustworthy". They are looking for evidence that something is wrong and assuming all is well if they don't find it. To that sort of user, the thinking goes something like:

* Some trustworthy sites use .com.

* My municipality is trustworthy.

* My municipality uses .com.

If you draw out the venn diagram, there's a clear gap in that line of thinking. That doesn't matter to someone's Great Aunt Linda though. She just knows that .com is what goes after Amazon and Google, so it must be good.

With that in mind, could using .gov help to protect those folks? To a certain extent. I can see the argument for keeping the more discerning few from getting scammed. For the broader group though, it won't change anything.

Offhand, the alternative solution that I'd offer would be providing clear communication standards to the public. Specifically, defining when, how, and from whom municipal notifications go out. Think of it like the IRS only sending physical letters; archaic as it seems, it makes it pretty obvious that an email "from them" is bogus. The clearer someone's understanding of where to find us is, the more optimistic I am that they'll get where they need to be.

[xp84]

> They just memorize "[municipality_website]"

Nah, even worse, they type “municipality” or some butchered typo of it into their browser, triggering a Google search, and click the very first link they see (sponsored or no) - so they can wildly easily be tricked into phishing websites.

Arguably we’re all victims of the decade or so when Google was so good at serving up the right site, so most people just got used to not knowing any URLs. People Google “YouTube” or “cnn” rather than type even the .com after those words.

[fencepost]

You say there are grants available, but given the current environment actually relying on those seems risky - even if you were actually to get the money up front it seems like it might get clawed back.

[Mixtape]

You are correct. This is a consideration at all levels of government currently, with faith in those grants' persistence varying based on an individual recipient's responsibilities.

[cbozeman]

> The average non-technical user doesn't "see" "[municipality].[state].gov". They aren't familiar with the concept of a domain hierarchy at all. They just memorize "[municipality_website]" and move on with their day.

You've just highlighted the problem. This is something every single human being in America should know, and arguably almost the entire world.

This falls directly under the rubric of Basic Computing Knowledge > Basic Internet Knowledge.

Every single time I see someone searching for "microsoft" or "apple" I immediately stop them and tell them, "You've already done most of the work. Microsoft and Apple are commercial entities. Add .com at the end, which is what .com means. Commercial. You're adding extra work for yourself."

Yes, a few people pop off at the mouth at which point I remind them ignorance is of a thing is easily remedied with a little give-a-damn, and saves everyone time and money.

Talk about a fucking miserable failure of education. I'm 44. I expected the generation 20 years younger than me to be impossibly skilled with computers to the point that I wouldn't hope to even match them, much less surpass them. Instead what we got was a world where we dumbed every goddamn thing down so even the most drooling moron can utilize it.

It's pretty disappointing, to put it mildly.

[pests]

I think your view on the world might be a little skewed. Every human in the world needs to know how domain names work? What?