You can now move files and folders within your "filesystem"

Time to update this one for folks that have been here for a while...

Been working on this for almost three weeks and it's almost ready for release - folder sharing on Bloom! This was one of the things that I wanted to do that other Blossom and NIP-96 solutions just did not provide and what originally inspired me to create on the project, so pretty happy to get here. Soon you will be able to share (and of course revoke the share) for any folder with the exception of the Private folder which is only ever accessible through your private key. Still a bit of UI work to do, but I expect it to go live in a couple of days for the project's one month anniversary.

After distro hopping for a while, decided to just go back to Silverblue. Not the biggest GNOME fan, but there's just not a simpler, more stable distro around that just stays out of my way.

Fedora Silverblue

An atomic variant looks, feels, and behaves just like a regular desktop operating system, but your updates are delivered as full images of a workin...

Sway > Hyprland

Any Void Linux users on Nostr? Thinking about switching back...I miss it.

Fitting that a quote from a legendary chef encapsulates my thoughts on the use of AI in any field or profession. “I don’t like gourmet cooking or ‘this’ cooking or ‘that’ cooking. I like good cooking.” — James Beard

So nice to finally have Bloom usable on mobile phones. There's still some quirks to sort out but remote signer login works, and UI was tweaked quite a bit so its very usable. For Grapheme users, not sure if its a Vanadium limitation (or feature lol) or what, but use another browser for now. I use Cromite without issue. The one thing I'll have to fix for sure, but applies to every platform, has to do with playing encrypted audio since we have to load the full audio blob before decryption. Pretty sure I can do some chunk decryption here so will test once I have a plan in place.

For all you devs out there...I've laughed so hard this morning

There's been a lot of changes to how we handle NIP-94 metadata and browser storage with the latest release, so if you use Bloom, I recommend clearing local storage. I added a new section in Settings to make this simple (and keep track of what we store), but here's a quick explainer before you go deleting things. Early on in development, I had not yet implemented NIP-94 support so blob metadata was all written to local storage. This allowed things like file previews to appear instantly and let you give blobs actual file names instead of just seeing SHA256 information. Along the way, since then, I've done quite a bit of work on the NIP-94 implementation and most of you saw no difference because file metadata was still being fetched from your browser not relays. The downside, of course, is that local storage has a limit of about 5MB so space filled up quickly, mostly due to image caching. The latest release saw a pretty big overhaul in how we fetch and display blobs where we now fetch from local storage, then compare to the NIP-94 data, overwrite local storage if NIP-94 data is different, and just store the hash locally for lookup. All preview images have now been moved to cache storage where they probably should have been to begin with. I have done a bit of work with storage key caches and lookups which gives us a better path forward, but some of you may see your local storage appear full (and it probably is). You can easily clear browser storage from your browser directly so no need to use the new utility in Settings. If you decide to clear local storage, you may see that some of your files only display their hash and now whatever you named them so this is the one gotcha. This should not impact anything that has been uploaded in the past week or so, but just wanted to give a heads up.

Just pushed a new update to Bloom! 1. Reworked search functionality to include private encrypted files (finally). 2. Simplified the UI when browsing on small screens and mobile phones (also finally). 3. File renders now use the name metadata tags and fallback to sha256 hashes when none are present. Previously, we were first fetch data from localStorage so file names could appear differently on different devices so now we have the correct expected behavior. 4. Several bug fixes related to event handling and signing that should make for a smoother experience. 5. Minor UI tweaks.

Bitcoin "crashes" to 108k, meanwhile shitcoiners..