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

Just pushed a small update to Bloom: 1. You can now sign in by pasting a bunker:// URL. Please note that this option is inherently a bit slower than other options. 2. Connect With Extension button no longer appears on browsers that do not have a NIP-07 extension installed. 3. Overhauled the Connect With Remote Signer dialog to tabbed layout.

IYKYK

I guess I should add noauth-connect support to Bloom now, huh? 🥰

Judging by the amount of people whining about charts today, I'd say most of you are not bullish enough. 1 btc still equals 1 btc.

Introducing noauth-connect, a drop-in, customizeable widget anyone can add to any project for NIP-46-compliant login and event signing. The project currently uses @npub1uf9g...v8xc as a bunker , but the bunker endpoint can easily be defined right from the widget with simple syntax (see README at the link below) in case you want to host your own bunker. Because we are using noauth, private keys never leave your local machine. The goal is to eventually give any project the ability to itself become a trusted bunker for other websites and applications so this is super early days. Why use this instead of Nostr Login or any other solution? IDK, do whatever you want. I wanted something super simply for both developers and users to use with a minimal workflow to let folks do what they want quickly. If that's you cool, if not, that's cool too.

GitHub

GitHub - Letdown2491/noauth-connect: Web component for NIP-46 Nostr authentication using Noauth.

Web component for NIP-46 Nostr authentication using Noauth. - Letdown2491/noauth-connect

If you want a reference implementation for the project, I have also created Nostr Profile Manager which let's you view and edit your Nostr profile and relay/media server data.

GitHub

GitHub - Letdown2491/nostr-profile-manager: A simple Nostr profile manager utilizing noauth-widget to handle login and permissions.

A simple Nostr profile manager utilizing noauth-widget to handle login and permissions. - Letdown2491/nostr-profile-manager

Would love folks smarter than I to chime in so share with others and let's see how we can improve this thing together. I'll tag @PABLOF7z to start since I know he's mentioned the idea of bunkers everywhere before.

Cooked up a little profile manager app just to test out the new noauth project I'll release later today :-)

i remember seeing @Derek Ross mention something about this the other day and I know @Logen and I have as well so decided to start cooking a little something...

What are we building tomorrow? Thoughts, thoughts, thoughts...

You can dislike something and complain about it, or you can just do something about it. Still some kinks to work out but here's a slightly improved Primal web experience. Still relies on the caching service but I'll complain about that whole thing later 🤓

GitHub

GitHub - Letdown2491/primal-web-app: Primal's web app for Nostr, as experienced on primal.net.

Primal's web app for Nostr, as experienced on primal.net. - GitHub - Letdown2491/primal-web-app: Primal's web app for Nostr, as experienced on pri...