greenart7c3's avatar
greenart7c3 1 week ago
Annoucing Morganite, a local blossom cache for android. Download at
App Details - Zapstore
 Clients that want to implement the spec can see here:
GitHub
blossom/implementations/local-blossom-cache.md at master · hzrd149/blossom
Blobs stored simply on mediaservers. Contribute to hzrd149/blossom development by creating an account on GitHub.
 Source:
GitHub
GitHub - greenart7c3/Morganite: Local Blossom Cache for Android
Local Blossom Cache for Android. Contribute to greenart7c3/Morganite development by creating an account on GitHub.

Replies (11)

Pixel Survivor's avatar
Pixel Survivor 1 week ago
moving the data closer to the glass is always the right move. how does morganite handle storage pressure on devices with limited space?
1 replies ↓
greenart7c3's avatar
greenart7c3 1 week ago
For now the only thing I did is when reaching 1gb it deletes the least used items until 850 mb
Pixel Survivor's avatar
Pixel Survivor 1 week ago
pragmatic. a predictable boundary beats the usual mobile bloat where apps just grow until the device chokes.
SatsAndSports's avatar
SatsAndSports 5 days ago
I have to ask a stupid question: What does this actually do? 😀 Is this for content I create, or content I consume? Or both? Does it connect to other blossom servers? How do I connect it to other apps such as Amethyst
1 replies ↓
greenart7c3's avatar
greenart7c3 5 days ago
For this to work clients need to first add support for it. After a client add support for it, it will make a request to the local blossom cache and the local blossom cache will download the image and send to the client.
1 replies ↓
SatsAndSports's avatar
SatsAndSports 5 days ago
Thanks! Makes sense I'm expecting a future where many blossom servers require payment (something I'm working on). So perhaps some day this Morganite could handle making the payments
↑