I'm working on my guitar practice app, Captrice[1]. Last week, I added an interactive metronome tutorial[2] in the app to help onboard beginners (quite a challenge). This week I'm planning to implement the long pending "device sync" functionality - currently it's a local-only webapp (it's all static pages; no backend server). So for the past couple of days, I've been learning and evaluating the existing sync solutions.
The app has been my long term side project for more than 2 years now. I've been playing guitar for more than 20 years, mostly as a hobbyist. It started as a personal project and I've got immense value out of it in terms of speed building and consistency of practice. I believe other guitar players can find it useful too.
A few months back I got a burst of inspiration to pursue it more seriously. After my last contract ended, I've been primarily working on it. Eventually I may go back to contract work again but for now I'm excited to spend dedicated time on it! Do give it a try, or share it with guitar players in your circle.
The last few months I’ve been reading a lot about neuroscience behind learning and practicing music and I’m fascinated by the subject. It has helped me realise why the app works for me, as well as my own mistakes that held back my progress for many years despite putting in decent efforts.
It was a much needed inspiration to continue working on it with a re-evaluated roadmap.
I’m also interested in this. I have a similar use case, to implement “cross device sync” functionality for a local-only webapp. I tried out automerge but it felt like it’s meant for syncing data when multiple users collaborate, and not data sync for a single user who is expected to use only one device at a time (I could be wrong about this).
I have implemented a POC sync mechanism via central server and I believe it’s simpler as it takes advantage of certain assumptions about the app. I’ve yet to productionize it so I am interested in knowing if my understanding is correct or if there are other existing solutions for this use case.
I've been building a desktop app on the side that addresses the problem of screenshots getting accumulated on disk over a period of time. It provides an alternate workflow for capturing screenshots, where the app let's the user select tags before taking the screenshot. Tags can be associated with actions such as "move to trash after 1 day", "delete after 7 days" or "store in /specific/location".
I have got the main functionality working and I've been using it myself in a crude way (using sqlite client directly for data entry etc.) for about a week. It was not meant to be a serious project to begin with - I just wanted to build something to evaluate Tauri for desktop apps. I am still not 100% convinced if such a tool is worth building, so the code hasn't been published anywhere. Do you care enough about "screenshots management and cleanup" to use something like this?
I would go further with this, essentially matching patterns of files in certain directories. Another use case for example is removing old log files from a directory.
In any case, I would have it as a user option to carry through the action, i.e. "the following is scheduled for deletion saving X disk space, do you wish to continue?".
Tags with actions sounds useful. Maybe worth a demo video to get opinions from a broader audience?
Personally, I think I'll stick to pruning my screenshots folder once a year with an image manager. I'm pretty content with niri's builtin screenshot capture or something like Greenshot on windows. Just my two cents
Gerrit uses a “Change-Id” trailer with a unique value. When you “fix up” a commit, the commit SHA changes but the change id remains the same. That’s how it can identify different commits with the same change id as patchsets of the same change.
This is based on what I remember (haven’t used gerrit in a while), so it may not be accurate.
I used gerrit in my previous job and miss using it. Would definitely prefer it over GitHub which is more popular (and convenient of course, can’t deny that).
Your understanding of the Change-Id footer sounds like it matches mine.
I’d note that it works that way presently, but the teams behind git, gerrit, jj-vcs, and a couple of other relevant stakeholders have an email thread going in which, from what I understand, they discuss standardizing on the approach taken by jj-vcs:
If any one's looking for the answer to why it's not recommended to edit library imports - when you import collections from the library, you can receive updates whenever the collection author publishes a new version. These updates might include new exercises or improvements to existing ones. However, if you've made your own modifications to the collection, these personal changes will be overwritten when you update to the newer version.
I haven’t tried using it for bass guitar but I believe it should just work? I assume you want tabs for bass guitar. Alphatab, the tablature editor supports bass guitar and other stringed instruments too. I guess it even supports notation for drums/percussion.
For that matter, I think the app should work for practicing any instrument that can be practiced with a metronome if you ignore tablature (which is only for reference anyway).
For now I want focus on guitar as that’s my primary use case but I’d love to extend it for other instruments in future.
The app has been my long term side project for more than 2 years now. I've been playing guitar for more than 20 years, mostly as a hobbyist. It started as a personal project and I've got immense value out of it in terms of speed building and consistency of practice. I believe other guitar players can find it useful too.
A few months back I got a burst of inspiration to pursue it more seriously. After my last contract ended, I've been primarily working on it. Eventually I may go back to contract work again but for now I'm excited to spend dedicated time on it! Do give it a try, or share it with guitar players in your circle.
[1]: https://www.captrice.io/
[2]: https://app.captrice.io/metronome-101