Replies: 1 comment
-
|
🟢 v4.0.6 is out. This one is a small consolidation release rather than a feature drop, so the wishlist mostly rolls forward untouched. The headline is the AeroVault crate convergence: the full AEROVAULT3 container and the revision 4 Reed-Solomon error correction now live in the published Per-item detail with commits and statuses lives in the tracker: #337. Suggestions for the next tag continue in the fresh v4.0.7 wishlist: #339. Thanks as always for the input. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Welcome to the rolling wishlist for v4.0.6 and the v4.x releases that follow. This thread collects enhancement suggestions from the AeroFTP community and triages them into the upcoming v4.x tags.
The previous wishlist (#270) ran across the v4.0.0 to v4.0.5 stretch and shipped a large amount: the native AeroCrypt encrypted overlay (turn any backend into a zero-knowledge vault, browsed in the normal dual panel), AeroVault v4 with Reed-Solomon self-healing, an interactive CLI (full-screen TUI plus an inline
profiles -imenu), server groups, file versioning for Filen and MEGAcmd, per-protocol credential persistence, a custom icon picker and docs links on every Quick Connect page, and a wave of AeroFile polish (rubber-band selection, click-to-deselect, draggable dialogs everywhere, lossless/lossy image labels). With v4.0.5 out, we close that thread and open this one.Three tracks shape the project, this thread is one of them
To keep it clear where a given idea belongs, the three planning surfaces of AeroFTP are:
The three tracks intentionally feed into the same releases. A v4.x tag will typically land items from all three.
How to contribute
Please post one suggestion per comment so each one can be reacted to and discussed independently. A good suggestion includes:
Reactions on individual comments are welcome and count as "I want this too" signals. Free-form replies discussing trade-offs are also welcome under the same comment.
Scope
In scope:
Out of scope:
Companion thread: COMMUNITY ROADMAP (#162)
Big features and multi-day architectural pieces live in #162 "COMMUNITY ROADMAP". If your idea fits the wishlist (less than a few days of work, in scope for the next tag), keep it here. If it is a bigger piece, #162 is the right home for it.
Carry-over from #270
Items raised in the v4.0.5 wishlist (#270) that did not make a tag and are still open are eligible for triage here. The rule:
originally from #270 comment <link>trailer. That keeps reactions per item meaningful in this cycle and avoids carrying stale assumptions over.Triage
Before cutting each v4.x tag we will:
Reactions on comments inform priority. Tie-breaks favor items that improve daily-driver ergonomics for tester profiles (existing community testers, documentation drilldown, error message clarity).
Thanks in advance for the input.
Beta Was this translation helpful? Give feedback.
All reactions