I've been using Ian's Secure Shoelace Knot for... years? I can't even remember how long, but it's served me very well. I just love how much more secure it is and how symmetrical and balanced the final result is. It's also such a trivial upgrade for kids that have learned to tie their shoes using the "bunny ear" method... just one extra twist.

https://www.fieggen.com/shoelace/secureknot.htm

And like many things on HN, previous discussion: https://news.ycombinator.com/item?id=13399095

A couple of the startups that do go links have blog posts on the history:

https://www.golinks.com/blog/go-links-history/

https://www.trot.to/blog/2020/07/09/go-links-origin-story

Those 2 stories kind of contradict each other. One says Benjamin Staffin invented golinks, then later another Googler built golinks in 2006. The other says Benjamin Staffin created golinks around 2009/2010.

Original author of https://github.com/trotto/go-links here! We spoke with Benjamin directly, so I trust his recollection.

I forgot to add a link to our recent announcement blog post to the project README. I've added that now, and I think it may help explain why we specifically built a service like this on top of Tailscale to take advantage of Magic DNS, automatically authenticated connections, etc. https://tailscale.com/blog/golink/

UX definitely ended up being one of the hardest parts. We also never got to the point of really building a compelling product on top of the protocols. We did actually do some work on privacy though, but it never got super far. For example, you could set simple access controls on content that was only available to friends that logged in with an OpenID. I think I had it so that certain of your hcard attributes were only included for authenticated users as well.

Some of the work we did then still exists today in various forms. Activity Steams led to Activity Pub, which has seen far more adoption than we ever did.

And microformats are still widely used in some communities, though certainly not like it could have been, largely things to Google putting weight behind schema.org. For example, nearly all of the indieweb.org work is based around microformats at the core, with things like webmention, micropub, etc

The man himself! Thanks for chiming in.

same team. different company.

Go team!

yehh

From https://blog.golang.org/gopher:

The gopher has no name, and is called just the "Go gopher"

on it: https://news.ycombinator.com/item?id=20228237

Hey, Will from Google's Open Source Office here.

I apologize for the confusion this caused; that was certainly not the intent. Mea culpa! The name "libcrurl" was just an internal working name for this effort that wasn't expected to gain much attention.

This project is still very experimental in nature (as discussed at https://bugs.chromium.org/p/chromium/issues/detail?id=973603...), and there are no plans here to try and replace or compete with libcurl. We have huge respect for the tireless work Daniel does to maintain curl, and didn't mean to cause any confusion or extra work for him.

To make things clearer, the team is renaming the project, and adding some more docs outlining the goals and intent of the project: https://chromium-review.googlesource.com/c/chromium/src/+/16...

And for anyone that wants to learn more about how Google manages third-party code, all of our docs are public at https://opensource.google.com/docs/thirdparty/

> This is part of the process for releasing Google-owned code as open source.

20% projects are Google-owned code.