Hello All!
The following covers Least Authority’s work for the Tahoe-LAFS Software
Foundation during June 2025:
-
Create Tahoe-LAFS Mobile from PrivateStorage Mobile:
-
Refactoring of core libraries and magic folder is now complete (but
for minor details) and may be inspected at
https://gitlab.com/tahoe-lafs/bala-lafs . The advantages include:
-
Orderly dependency graph resulting in more comprehensive
generalisations.
-
A reduction of line count to roughly 40% of the original.
-
Only uses basic Haskell techniques, not even requiring type
classes.
-
Better modelling of capabilities leading to better code
factorisation and type safety.
-
A single tree-like cache with driving functions that houses
isolated files, plain folders, magic folders and
pending-download status.
It also preserves downloaded data and notes the error-cause
when a change
of grid config makes it unavailable, and it will support e.g. conflict
resolution when the time comes.
-
Magic folder read support (currently still just takes the newest
participant version) based on said tree-like cache.
-
Closer attention to laziness to handle files larger than main
memory.
-
A robust, fair and efficient concurrent share fetching algorithm.
-
A base from which to easily implement a storage/cloud server.
-
Consistent error handling.
-
The next task is to port the mobile app to the new core/MF library.
This will simplify the mobile app code.
-
Recovery Phrases:
-
Looking at remaining ZKAPAuthorizer integration issues and making
ZKAPs optional (Gridsync #733)
-
Replacement for the Current Issue Tracking System and Web landing page (
trac#4095 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4095>)
-
Deploying Forgejo and its requirements (mailer and backups -
infrastructure#44
<https://github.com/tahoe-lafs/infrastructure/issues/44>)
-
Continued work on infrastructure:
-
To manage shared secrets with a ”infrastructure-pass” repository (
trac#4177 <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/4177>)
-
Maintenance and Community Work:
-
Supporting and pair programming with other members of the community
on writing tahoe client tests.
Additionally, a few hours of our time was spent on project administration
and coordination.
Please let us know if you have any questions or comments.
_______________________________________________
tahoe-dev mailing list
tahoe-dev@lists.tahoe-lafs.org
https://lists.tahoe-lafs.org/mailman/listinfo/tahoe-dev
