@estl95.bsky.social
Reposted
I’m pretty excited to announce that the actual storage runtime for shdwDrive v3 is basically done!
Steven and I have some bug hunting to finish up, but I’ve moved onto polishing the iOS app.
In the coming weeks, I’ll be able to give a more definite time frame as far as an actual release date!
Steven and I have some bug hunting to finish up, but I’ve moved onto polishing the iOS app.
In the coming weeks, I’ll be able to give a more definite time frame as far as an actual release date!
September 24, 2025 at 7:04 PM
I’m pretty excited to announce that the actual storage runtime for shdwDrive v3 is basically done!
Steven and I have some bug hunting to finish up, but I’ve moved onto polishing the iOS app.
In the coming weeks, I’ll be able to give a more definite time frame as far as an actual release date!
Steven and I have some bug hunting to finish up, but I’ve moved onto polishing the iOS app.
In the coming weeks, I’ll be able to give a more definite time frame as far as an actual release date!
Reposted
Reposted
Home stretch!
Everything runs, the iOS app builds and runs perfectly!
Now, it’s just a matter of going module by module to clean up any AI slop remaining and optimize the codebase… but, it all works!
Everything runs, the iOS app builds and runs perfectly!
Now, it’s just a matter of going module by module to clean up any AI slop remaining and optimize the codebase… but, it all works!
October 3, 2025 at 10:56 PM
Home stretch!
Everything runs, the iOS app builds and runs perfectly!
Now, it’s just a matter of going module by module to clean up any AI slop remaining and optimize the codebase… but, it all works!
Everything runs, the iOS app builds and runs perfectly!
Now, it’s just a matter of going module by module to clean up any AI slop remaining and optimize the codebase… but, it all works!
Reposted
In building v3’s codebase, I created a dedicated module whose sole purpose is to manage the FFI surfaces. This bridge is how the iOS app initializes the storage runtime on the mobile device.
Why this is important is bc when we port to Android, it means simply adding new surfaces to one just module
Why this is important is bc when we port to Android, it means simply adding new surfaces to one just module
Fantastic, hopefully not too difficult to modify for the android version.
October 7, 2025 at 11:32 PM
In building v3’s codebase, I created a dedicated module whose sole purpose is to manage the FFI surfaces. This bridge is how the iOS app initializes the storage runtime on the mobile device.
Why this is important is bc when we port to Android, it means simply adding new surfaces to one just module
Why this is important is bc when we port to Android, it means simply adding new surfaces to one just module
Reposted
Nice progress on cleaning and refining aspects of the gossip network over the past few days!
October 11, 2025 at 5:49 PM
Nice progress on cleaning and refining aspects of the gossip network over the past few days!