Have they included real profiles in the screenshots of the "Discover profiles" menu and the list of likes? If so that's pretty irresponsible even with the faces obscured.
I'm quite possibly missing something, but this is baffling to me (Text S1 from the paper) [1]:
> All the chopped carrots were carefully transferred to the glass wash tray. As shown in Figure 2,
> 500 mL of ultrapure water was used to wash the blade and the chopping board further to transfer all the particles in the same glass wash tray.
Who would expect contaminants left on the blade and the board to be counted alongside those in the chopped food itself? I suppose it's difficult to rigorously separate the chopped and the chopped-upon, but the distinction seems essential to support, or not, the hypothesis about human consumption.
Something which goes further than this, but works very well for my use case and would probably suit others in the WFH crowd: OpenMPTCProuter [1]
This handles failover between connections and also aggregates them using MultiPath TCP to maximize bandwidth & overall reliability at the expense of increased data usage and the cost of running a machine somewhere with a decent connection, even a cheap VPS.
I'm using it to aggregate ADSL, Starlink and 4G, resulting in a stable 250mbps/50mbps connection.
Forgot to say that it's open source (AGPL) on GitHub [1]. I find it handy just being able to run `git blame` on a doc, but I'm sure it could be made more useful. Contributions are welcome!
The only benefit of the hosted version is that the OAuth setup is already done. If you're ok registering an OAuth app with Google (instructions in README.md) then it's trivial to run yourself. Given that there's no fine-grained permissions on Drive - it has to ask for read only access to your entire Drive just to access one doc - I completely understand wanting to run it locally.
This is similar to the Structure dashboard in Repography [1] which is a web app I built, with the added advantage that it's kept up to date automatically so you can embed it in your README.md and not have to keep updating it yourself.
I was surprised by the observation that Python rounds towards even numbers, so round(0.5) = 0, but round(1.5) = 2.
This is indeed clearly documented [1], I guess I never looked closely enough. I found some discussion on the dev-python list [2] which shows at least I'm not the only one surprised by this!
As Graydon Hoare notes in the comments on GitHub this wasn't the first repo so the real history goes back even further. He's also shared a "prehistory" repo [1] which is interesting to browse. The first commit [2] in _that_ repo is from 2008 but Graydon mentions starting work back in 2006.
Anyway in a sense this repo represents Rust in the real world rather than in gestation, so seems apt to call it the birthday.
I likewise couldn't resist doing something silly with an SVG animation on my profile [1], and I also have a micro startup [2] generating such SVGs periodically to serve as dashboards you can embed in your README.md. I'm interested in more of your predictions!
A couple of my own projects might also be of interest. Repography [1] creates posters with more of an aesthetic focus, and Work/Artwork [2] takes this even further, creating modern art.
The name still makes me giggle. I'd love to build something relevant and silly enough to put there, but I haven't found it yet.
Suggestions are welcome! :)