home

I am at Google, but that's probably not relevant since the reason I was curious about this is that my personal website currently implements a git server over HTTPS[1], and git's CLI/API for that is not the friendliest[2]. It sounds like jj hasn't reached the point of tackling this problem space yet, which is okay. Thanks for confirming I wasn't missing out on something. [1] https://pkg.go.dev/github.com/shurcooL/home/internal/code#Ne... [2] https://pkg.go.dev/github.com/shurcooL/home/cmd/githook/pre-...

Do you have ideas for how to test it and find out definitively in person? I haven't found a way to confirm one way or another. The Graphics/Displays page in System Information unfortunately says nothing about colors, only resolution (https://github.com/shurcooL/home/assets/1924134/af4b19a3-b85...). When looking at a 16-bit PNG of a white to black gradient, I'm not able to visually spot any banding even when zooming in. It's fairly easy to spot steps when looking at a 8-bit PNG version of the same gradient. But the same happens on the built-in display despite it supposedly having only 8-bit color ("support for millions of colors").

https://dmitri.shuralyov.com/blog If only I directed more of my writing activity to blog posts, not just commit messages¹ and issues². [1] https://github.com/shurcooL/home/commit/bb504a4ef0d7c552d363... [2] https://github.com/shurcooL/home/pull/32, https://github.com/shurcooL/home/issues/26

https://dmitri.shuralyov.com I use it myself daily to receive a chronological feed aggregating notifications from GitHub and Gerrit. I’m pretty happy to rely on that and not need to receive notifications via email or by visiting multiple web UIs. It also hosts my newer (though also more rare) personal Go packages, serving them via a custom implementation of the module proxy protocol in addition to a git server, an issue tracker, and most recently a simple code review system (see https://dmitri.shuralyov.com/go/generated$changes/1). Supports logging in via the IndieAuth protocol—try entering your website's URL at https://dmitri.shuralyov.com/login. Source code is at https://github.com/shurcooL/home, though some WIP changes aren’t there yet, and I should really move it to be hosted on my personal site for more dogfooding. One day.

In case you or others find it interesting, I've had luck removing an authentication SPOF¹ by using IndieAuth on my personal site². I wish it were an option on more of the sites where I need to sign in. ¹ https://twitter.com/dmitshur/status/1223304521767669761 ² https://github.com/shurcooL/home/commit/bb504a4ef0d7c552d363...

I’m happy to support IndieAuth (a decentralized identity protocol built on top of OAuth 2.0) on my site and give people the option to use their personal site, if they have one, as a way of identifying themselves and performing authentication. I described the motivation in more detail at https://github.com/shurcooL/home/issues/34.

Converting a simple issue tracker written in Go to run completely in the frontend [1], so that it’s easier and faster to iterate on its development at the cost of initial page load. [1]: https://github.com/shurcooL/home/compare/dev That said, I don’t think I have any additional time due to quarantine.

Upspin is a monolith, I think? https://github.com/upspin/upspin Also, my personal site is a medium-sized monolith: https://github.com/shurcooL/home

Thanks. Do you have a recommendation on how I should handle HEAD requests? Edit: I went with something like this [1] for now. It worked to solve this problem. I can adjust later as needed. [1] https://github.com/shurcooL/home/commit/b4a601ff7a3752feb291...