Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Launch HN: GoLinks (YC W19) – Internal short links for teams

news.ycombinator.com

Post reply on HN
Print view View original

31–40 of 97 posts

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#31

Post by seantomburke »

Sephr wrote: post #29

Personally, at my company we just use a private link redirecter at go.company-name.example. We use a modified version of the open source Zerodrop webapp[1]. This solution doesn't require a browser extension with elevated permissions that increases your attack surface. 1. https://go.eligrey.com/zerodrop

Always happy to see go links being used at other companies! You can actually take this a step further at Eligrey. By setting up a DNS Entry that redirects go.eligrey.com to the domain go you would then allow your links to become conversational and even quicker to access. For example you could say "Checkout go slash zerodrop" without physically sending an email or message.

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#32

Post by jbob2000 »

We are distinctly not allowed to use URL shorteners at my enterprise company and our fraud prevention department regularly educates us about the dangers of clicking URL-shortened links (you have no idea if it will send you to a phishing site or not).

URL shortening was created so people could send tweets without using up their character counts on a URL. I'm pretty sure most software companies aren't communicating via Twitter, so I'm not sure the practical application of this anyways.

Good luck.

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#33

Post by seantomburke »

mountainofdeath wrote: post #30

Don't domains managed by Microsoft Active Directory do the same thing? E.g. If git is hosted on git.contoso.com and my workstation is part of contoso.com, I can just go to https://git

Yep, that's correct! That works assuming you have access to setup subdomains for contoso.com. We make it easy for any employee, technical and non-technical, to update and create links.

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#34

Post by pacifika »

So I built this as a prototype for the college I worked on. Broken links are a big problem with learning materials which are hard to change after publishing.

The idea was that someone is responsible for each link and any 404s would get corrected. Then if the person left active directory would assign the manager.

Hope that’s useful. It was also called go.

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#35

Post by lol768 »

Whenever I see mentions of go links, I think "How are you handling TLS?" which there's not a great answer for* so I think it's neat that the extension model solves this problem.

* I don't trust most enterprise IT teams to be able to set-up and administer a secure CA with the appropriate critical nameConstraint that limits the CA to signing certificates for `go`.

--------

OP: You should probably mention the TLS problem on https://www.golinks.io/support.php#technical since right now I assume the CNAME approach will only work with HTTP.

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#36

Post by usaphp »

kyeong wrote: post #13
usaphp wrote: post #6

It asks me to install a browser extension, which asks for this permission: "It can: Read and change all your data on the websites you visit". Is it normal?

The extension will read the text on screen to determine if there are any golinks so that it can change it to a click-through link. We know this may sound scary but rest assure that we do not have any ability to see or save any content. Your privacy is our top concern.

Correct me if I am wrong but if I visit my tax account page or something where the ssn is displayed - you can see it too?

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#38

Post by jazamora »

hamandcheese wrote: post #37

I love the usability of go links when I’m at work, but it sucks that they don’t work on mobile.

You are able to use go.golinks.io/KEYWORD with ours or if you are setup on the enterprise tier with us, we can setup full TLS go.youcompany.com/KEYWORD

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#39

Post by seantomburke »

jbob2000 wrote: post #32

We are distinctly not allowed to use URL shorteners at my enterprise company and our fraud prevention department regularly educates us about the dangers of clicking URL-shortened links (you have no idea if it will send you to a phishing site or not). URL shortening was created so people could send tweets without using up their character counts on a URL. I'm pretty sure most software companies aren't communicating via…

It's less of a link shortener and more of a link manager for companies. The concern that companies have with URL shorteners is they can't manage who is creating these links, and who owns these links. With GoLinks, the company will own the links, they can manage, edit, update, delete any links within the organization, so they will be centralized. The added benefit is that with a memorable link, you can access go/benefits much easier than bit.ly/fE7r232r. URL shorteners aim to shorten links, Golinks aims to make links memorable.

Re: Launch HN: GoLinks (YC W19) – Internal short links for teams

#40

Post by seantomburke »

pacifika wrote: post #34

So I built this as a prototype for the college I worked on. Broken links are a big problem with learning materials which are hard to change after publishing. The idea was that someone is responsible for each link and any 404s would get corrected. Then if the person left active directory would assign the manager. Hope that’s useful. It was also called go.

Yep! This is a problem we've addressed by making everyone in the organization an owner. If a link breaks, anyone in the organization can change it, even if the original creator leaves the company. Checkout out our blog to learn more about the history of go links, you may see why the "go" term is so popular.
Post reply on HN