The pants project owns the domains `monorepo.build...
# development
h
The pants project owns the domains
monorepo.build
and
pants.build
, but has never done anything with either of them. I’m not inclined to renew them, as it’s $75/year to do so in the
build
TLD for some reason, unless anyone has a differing opinion?
I know that’s not a lot of money, but OTOH why spend it?
Maybe just
pants.build
, at a stretch
w
pants.build
maybe to avoid malicious typo-squatting
One day, someone's gonna get LLMs to spit out malicious rustup/pantsup or whatever scripts: Like, if an LLM emitted this - how many people would bat an eye? (Using a picture, to reduce the chance that someone actually tries to run it)
p
We could make
<https://get.pants.build>
redirect to the get-pants.sh script, or even directly serve it. Not sure if it's worth $75 though. Dropping
monorepo.build
sounds reasonable.
w
We could make
<https://get.pants.build>
redirect to the get-pants.sh script, or even directly serve it. Not sure if it's worth $75 though.
Sure, just mean about keeping the domain vs kiboshing it. typos are always tricky, and typos for cases where we have scripts that pull from a URL - eesh. I don't do those in general, so doesn't affect me. But the majority of devs probably do
p
The only time I download
get-pants.sh
is when I'm adding pants to a new repo or checking for updates to the copy I keep in each repo 😛 Then I document that people should use the script in the repo they just cloned.
@happy-kitchen-89482 Is it 75 per domain or 75 for both?
aside:
get-pants.sh
is available for $35/year - that would have quite the "cool" factor, but it's not particularly useful. At least my employer blocks non-standard TLDs by default, so I would have to get that unblocked to use it. I can't access
pants.build
or
monorepo.build
for example. (I disagree with their security methodology, but oh well)
h
It’s $75 each
😱 1
Yeah, I will keep
pants.build
for now, but let
monorepo.build
expire unless I hear other opinions
👍 1