willnorris

9 ms·

1.
by willnorris 3y ago
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&#x27
2.
by willnorris 4y ago
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-stor
3.
by willnorris 4y ago
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,
4.
by willnorris 4y ago
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 exampl
5.
by willnorris 4y ago
same team. different company.
6.
by willnorris 7y ago
From https://blog.golang.org/gopher : The gopher has no name, and is called just the "Go gopher"
7.
by willnorris 7y ago
on it: https://news.ycombinator.com/item?id=20228237
8.
by willnorris 7y ago
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'
9.
by willnorris 8y ago
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/
10.
by willnorris 8y ago
https://opensource.google.com/docs/releasing/publishing/#dis...
11.
by willnorris 8y ago
We currently only list project that are or were primarily developed by Google. We decided to include projects that started at Google and were since donated to foundations, such as Kubernetes. But we aren't yet including projects where
12.
by willnorris 8y ago
> The default google approach to open source is unidirectional source dumps after all the work is done. I can definitely say that is not our default approach to open source; in fact it's a very small minority of projects that actual
13.
by willnorris 8y ago
Could you expand on this a bit? We've tried to be very transparent with how we approach and think about open source by publishing all of our internal documentation at https://opensource.google.com/docs/ . Is ther
14.
by willnorris 9y ago
Thanks. What you said definitely exemplifies the problem we were trying to solve. People often look through one or two of our GitHub organizations, but don't realize that we actually have over 100 of them. Plus many of our projects are
15.
by willnorris 9y ago
The problem is that we have over 2,000 projects, so simply listing them all on one page doesn't work very well. Hence why we built this directory, which allows browsing by category, by tag, by language, as well as full text search.
16.
by willnorris 9y ago
The other problem is that we have 100+ GitHub organizations, so browsing them all together is impossible.
17.
by willnorris 10y ago
To clarify the timeline a little bit here... Rosehub wasn't actually motivated by the MUNI hack, as it predated it by 8 months (Rosehub started in March 2016, MUNI hack was announced in November). As noted in the blog post, it was ins
18.
by willnorris 10y ago
There's no indication in the questionnaire of who is actually running it, what is being done with the data, whether results will be published and where, etc. Does anyone have more info? Right now, this just looks like a black hole.
19.
Nuclide is not actually open source(github.com)
4 points by willnorris 10y ago|0 comments
20.
by willnorris 10y ago
http://www.theverge.com/2013/9/3/4691040/android-kitkat-the-... "There's no exchange of money involved"
21.
by willnorris 10y ago
Just to be clear on this, Google projects (including side projects of Google employees) do not require copyright assignment in the way that FSF projects to. They require an explicit copyright license , but the author retains the copyrig
22.
by willnorris 10y ago
Somewhat confusingly, pulse.cio.gov lists senate.gov as supporting HTTPS with an 'A' from SSL Labs. While that is of course technically correct, it doesn't tell the full story, since no actual content is served over HTTPS. W
23.
by willnorris 11y ago
There are the actual Indie Web Camps that occur several times throughout the year. And each month there is the Homebrew Website Club Meetup ( http://indiewebcamp.com/next-hwc , named after the Homebrew Computer Club).
24.
by willnorris 12y ago
Google Code has always been exclusively for open source projects. From https://code.google.com/p/support/wiki/FAQ#Hosting_Your_Open... > Can I use Google Code to host projects that aren't open sour
25.
by willnorris 12y ago
that's definitely a bug that you can't read the agreement text without logging in. We'll see about getting it fixed.
26.
by willnorris 12y ago
nice project... I just updated a couple of minor gofmt, go vet, and golint issues I had overlooked in google/go-github, so the score is a little higher now :) Just curious, at what level are you raising the cyclomatic complexity as an
27.
by willnorris 12y ago
CCA?
28.
by willnorris 12y ago
Yes, we do vendor everything, in that we have a snapshot of all of our dependencies in our source control system. But we do it across the entire codebase, not per project. That is, we typically only ever have a single version of a library
29.
by willnorris 12y ago
I'd recommend seeing the comments from jamesgpearce (of Facebook) and amateurhuman (of GitHub) on this previous thread: https://news.ycombinator.com/item?id=8321995 . Also, this Wired piece does a really good job of ca
30.
by willnorris 12y ago
Chrome forcing the user to re-approve the extension when it tries to access more data is a feature, not something to work around. That alone is reason enough for me to say "thanks, but no thanks"

More ›