Doctree - Hackdot

Re:Doctree by beliu on Saturday April 30, 2022 @02:58PM (#31218303)

I’m helping with the doctree effort at Sourcegraph. Apologies, the site isn’t actually up yet. This project is still very early stages and we wrote up the README to serve as a sort of launch spec that we could update in response to feedback we receive. We made the repo public so we could build in public but didn’t expect it to receive this much attention this early!

So sorry that the site isn’t up yet. We’ll update the README soon to reflect that. If folks are interested in trying out a super early version, there’s the Docker run command and if you’d like to help us realize this vision, please join our Discord! https://discord.gg/vqsBW8m5Y8

[ Parent | on HN ]

Re:Doctree by bradleyjkemp on Saturday April 30, 2022 @01:40PM (#31217682)

And it's not just DNS issues. The domain doesn't even seem to be registered: it's available for purchase...

edit: No longer! Hopefully someone benevolent picked it up

[ Parent | on HN ]

Re:Doctree by mdaniel on Saturday April 30, 2022 @01:43PM (#31217719)

Sweet, a phishing opportunity!

    | Welcome to the doctree.dev demo site!
    |---
    | Enter your github oauth2 token to see it work

[ Parent | on HN ]

Re:Doctree by slimsag on Saturday April 30, 2022 @02:59PM (#31218319)

To be clear, we do own the domain. It was registered about ~7 days ago. It's just not deployed yet.

[ Parent | on HN ]

Re:Doctree by bradleyjkemp on Saturday April 30, 2022 @03:02PM (#31218336)

May want to double check that: domain data shows it was only registered today about an hour ago: https://client.rdap.org/?type=domain&object=doctree.dev

It was definitely available to purchase when I commented

[ Parent | on HN ]

Re:Doctree by slimsag on Saturday April 30, 2022 @03:21PM (#31218469)

..huh, yep, you're right. That's.. super embarrassing and huge screw up on my part, uhg. I was 100% positive I submitted the order through Namecheap before pushing the repo up to GitHub for this exact reason, and that it went through.. but yeah, looks like I didn't and we don't own it. :(

Good news is we've got doctree.org, so will be using that instead. I've removed all references to the other domain.

If it was a good samaritan, shoot me an email -> [email protected]

[ Parent | on HN ]

Re:Doctree by __ryan__ on Saturday April 30, 2022 @05:09PM (#31219389)

I love namecheap but I have walked away thinking I’ve completed an order to find that there’s a second order confirmation screen numerous times.

[ Parent | on HN ]

Re:Doctree by slimsag on Saturday April 30, 2022 @05:25PM (#31219518)

This was probably it.. luckily, it seems like it may have been a good samaritan from HN, they reached out to me just now. People here rock :)

[ Parent | on HN ]

Re:Doctree by devass on Saturday April 30, 2022 @01:53PM (#31217803)

Probably some developer misusing the .dev domain for their own personal test projects, yet again.

[ Parent | on HN ]

Re:Doctree by HWR_14 on Saturday April 30, 2022 @01:57PM (#31217832)

You mean "some dev deciding to keep using the .dev for personal test projects, as was the standard before ICANN and Google took a standard community resource and privatized it, yet again"

[ Parent | on HN ]

Re:Doctree by chrisseaton on Saturday April 30, 2022 @02:09PM (#31217917)

> as was the standard

Which standard was that? I thought only example.com was special-cased?

[ Parent | on HN ]

Re:Doctree by HWR_14 on Saturday April 30, 2022 @02:21PM (#31218012)

Before ICANN started auctioning off TLDs it was common practice to use .dev and .test (probably others that escape me).

It wasn't formalized, but that doesn't really matter. It was well known and commonly done.

In fact, it couldn't have been formalized, because the TLDs were limited and by definition any non standard TLD was for internal use only. It would make no sense to have a defined standard for an impossible situation.

[ Parent | on HN ]

Re:Doctree by detaro on Saturday April 30, 2022 @03:04PM (#31218354)

> In fact, it couldn't have been formalized, because the TLDs were limited and by definition any non standard TLD was for internal use only.

No, there never was any guarantee that the existing TLDs were all that would exist ever, so non-standard TLDs were just that: non-standard, undefined what happens to them. And you even provided a counter-example: .test is explicitly reserved by an internet standard to never be in public DNS and thus safe to use for testing purposes.

[ Parent | on HN ]

Re:Doctree by chrismorgan on Sunday May 01, 2022 @02:49AM (#31222792)

Using .dev was always contrary to spec. Dunno how common it actually was—I personally never encountered it. Clearly ICANN decided it wasn’t such a hazard as .home and .corp, which are both indefinitely delayed (https://icannwiki.org/Name_Collision) due to their popularity (despite being contrary to spec). You should instead have used something like .localhost (reserved in RFC 2606) if it’s on your local machine, or .test (reserved in RFC 2606) in a local network, or some domain that you control (even if it’s not publicly routable).

[ Parent | on HN ]

Re:Doctree by my69thaccount on Saturday April 30, 2022 @03:11PM (#31218403)

https://github.com/basecamp/pow

Pow used .dev and .test in the 2000s-2010s

[ Parent | on HN ]

Re:Doctree by chrisseaton on Saturday April 30, 2022 @03:19PM (#31218457)

That’s not a standard that’s just someone using them.

[ Parent | on HN ]

Re:Doctree by rvieira on Saturday April 30, 2022 @02:08PM (#31217903)

Incidentally, I've been getting a lot of timeouts from .dev TLDs today.

[ Parent | on HN ]

Re:Doctree by mdaniel on Saturday April 30, 2022 @01:42PM (#31217703)

Unless "tosh" is one of the project authors, I'd guess this was submitted to HN before an official launch. That is, I bet there are a lot of broken links from the website field in GitHub projects, and the only reason you expected this one to work was because it made the front page of HN and was in sourcegraph's GitHub org

[ Parent | on HN ]

Re:Doctree by tosh on Saturday April 30, 2022 @02:12PM (#31217935)

found it via the author’s tweet:

https://twitter.com/slimsag/status/1519910761400741888

[ Parent | on HN ]