Thread - Nostr Hypermedia

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 (15)

Ryan ryan@spatia-arcana.com 1 week ago

I just worked citrine support into prism, guess it's time to add this too 👀

1 replies ↓

hzrd149 _@hzrd149.com 1 week ago

added to

GitHub

GitHub - hzrd149/awesome-blossom: A collection of tools and apps built using the blossom spec

A collection of tools and apps built using the blossom spec - hzrd149/awesome-blossom

for what its worth

shredder shredder@zaps.lol 1 week ago

@SondreB

𝖘𝖊𝖙𝖙𝖔 setto@basspistol.org 1 week ago

Dumb question probably, but what's the usecase? 😅 Posting blobs while offline?

2 replies ↓

SondreB sondreb@nostria.app 1 week ago

How about a file metadata kind, allowing this to become OneDrive/Dropbox replacement?

1 replies ↓

SondreB sondreb@nostria.app 1 week ago

It's possible to send encrypted files over messages, though these come with no metadata, so when a user looks at their media server files, there is no information about what the file potentially is. If an encrypted kind was written as well, the user would know a bit more about it and not delete by mistake.

greenart7c3 1 week ago

For now it's just a shared blob cache.

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 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 1 week ago

pragmatic. a predictable boundary beats the usual mobile bloat where apps just grow until the device chokes.

florian florian@slidestr.net 5 days ago

Nice, I have implemented the same spec in

GitHub

GitHub - flox1an/almond: A temporary BLOSSOM file storage service with Nostr-based authorization and web of trust support.

A temporary BLOSSOM file storage service with Nostr-based authorization and web of trust support. - flox1an/almond

(when FEATURE_CUSTOM_UPSTREAM_ORIGIN_ENABLED is set) independently to operate as an edge caching server.

1 replies ↓

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 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 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

florian florian@slidestr.net 4 days ago

GitHub

GitHub - flox1an/almond: A temporary BLOSSOM file storage service with Nostr-based authorization and web of trust support.

A temporary BLOSSOM file storage service with Nostr-based authorization and web of trust support. - flox1an/almond