This sounds great! The main barrier I see is getting everyone I want to install the app. Perhaps a "mass-SMS" variant could work, so it's independent of whatever messaging apps everyone runs.
I'm not sure why but this seems very phone dependent. I can stand next to another person, both running Merlin in silence, and mine will pick up much more than some people's phones. My phone is not particularly new (Zenfone 8).
I've gotten used to this essential feature too via Semaphore CI, and I just can't stand not being able to SSH into a GitHub Action. Debugging is so slow.
Not all though, I've been looking at Minimed pump reverse engineering (which would be just reading glucose data, not controlling the pump), and that's not solved yet, at least not for the 780G. But I hope it will be, and perhaps I'll be able to contribute.
Some password managers like 1Password can do the two-factor stuff for you, so you don't have to pull out your phone. On the fully supported pages it'll just autofill your username, main password, and one-time password.
Those of you who use ROS in production, do y'all use ROS 1 or 2? Do you maintain your own fork? I'm curious how people do this, with the upcoming Noetic deprecation.
I've been fiddling a lot with getting my CGM glucose data on a smartwatch, in a way that I like, recently. I'm in the middle of a small series of posts on my silly blog here: https://fyhn.lol/blog/glucose-watch/
This is very interesting, and I (T1D) would like to learn more. However, the e-mail signup doesn't work for me. ("Oops! Something went wrong while submitting the form.")
Home: A 13-inch Asus Zenbook from 2014 (UX32LN) now running Ubuntu (MATE) 22.04. It's still good!
Work: A recent 13-inch Dell XPS that shipped with Ubuntu 22.04. It's also great, but the function key row has been replaced with touch buttons which is not good at all (including the escape and delete keys).
Work, previously: A 13-inch Dell Latitude from 2017. I originally ran 16.04 on it, then 18.04 until the above replaced it. Worked very well. Had every port you can wish for, including ethernet. Eventually the battery swelled and the keyboard stopped working.
And like in all things, there is probably a better middle ground. Don't commit forever to a horrible partner, but also don't look for the "perfect person" with whom there will be no difficulties. Neither is good. Look for the "good enough" partner and really try to make it work.
Isn't this only relevant for fixed gear bikes, where you can skid the rear wheel to brake, and you want maximize the number of possible "skid patches", or orientations of the rear wheel while the pedals are in a fixed position?
I agree, `mktemp` is very useful. I recently worked on a script that would check if you had a repo locally, if so update it, and otherwise clone it for you. `mktemp` made it a lot simpler, as I could just always clone it and be sure that I would have a freshly cloned state.
I dunno, I've submitted four bugs. One solved within a day, one after 20 days, and two still unresolved as far as I know. It could of course be better, I don't think it's quite like you describe.
For instance != is just a way to write something that looks similar to ≠. With ligatures, you can actually see the symbol you're representing, and not an approximation. I suppose that is the appeal. And it looks neat.
One one hand I agree. But my experience is that an okay password manager makes the process of logging into things, creating new accounts, updating passwords, etc. so streamlined that it rarely bothers me anymore.
I tried this out now, and it seems really useful, both at work and outside work.
Feature request:
There are some sites I consider as generally unwanted distractions always, and some that I consider as unwanted distractions only when I'm at work. How about differentiating between work/home modes, or allowing for profiles, or something similar?
The difference is whether the author of the pull request considers his code not ready for review or not. Both are work in progress but they need different treatment.
This is good. We have been emulating this with either a "don't review yet" tag or by opening a pull request without setting reviewers, but it's clearly better to have support for it built in. More people will use it, and I don't have to train people in our particular way of indicating not-ready pull requests.
One thing this project does really well is to start the readme with a screenshot. I open the link, scroll down to the readme, and I immediately see what sort of user interface/experience I will get. Some commenters have noted that Gita is similar to other multi-repo tools, but both Repo and wstool are more effort to evaluate, because their readmes don't have pictures.