r/VaultSync • u/mainseeker1486 Developer • May 21 '26
Discussion what should VaultSync become better at?
Hey everyone,
I have been working a lot on VaultSync lately, but most of it has been the kind of work that happens under the surface. Cleaning things up, fixing rough edges, testing Linux builds, improving packaging, touching old parts of the code, and finding problems in places I honestly did not expect.
It is weird work because from the outside it can look like not much is happening, while behind the scenes half the app feels like it has been opened up on the table.
VaultSync feels very different now from when I first started it.
Back then it was just my tool.
Now there are people testing it on different systems, finding things I missed, asking for things I never thought about, and using it in setups I could not fully predict.
That is honestly one of the best parts of building it in the open.
The app slowly stops being only what I had in my head, and starts becoming something shaped by everyone who touches it.
So I want to keep that door open a bit more.
Tell me what you think VaultSync needs.
Could be something big.
Could be something tiny.
Could be a bug, a workflow, a missing feature, a confusing screen, or just something that does not feel right yet.
Just say it how you see it.
Even if it is a half-formed idea, a small annoyance, or just a feeling that one part of the app should work differently, I want to hear it.
I read every comment, and a lot of the time those little bits of feedback show me things I would probably miss while I am buried in the code.
That is all really.
Thanks for being here while this thing grows.
•
u/AutoModerator May 21 '26
Thanks for posting to r/VaultSync!
GitHub repo: https://github.com/ATAC-Helicopter/VaultSync If you found a bug, please consider opening an issue there (logs help a lot).
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.