NostReport on Nostr: **Today on NostReport:** If you were away from Nostr for more than a few hours ...

**Today on NostReport:**

If you were away from Nostr for more than a few hours yesterday you may have missed Snowden (npub1sn0…jdv9) joining our ranks (

quoting nevent1q…r7q4

The problem is that most major states are pressuring corporations to limit speech.

The solution is to remove the ability to limit speech from corporate hands.

By moving the content-layer of the Internet to a neutral, ownerless protocol, nobody can delete the things you share. Nobody can destroy the things you create.

I feel like I'm looking at the future.

). This led to a large influx of new users, and increased activity. Many users noted slower than usual feeds.

Snowden’s embrace of Nostr brought up interesting topics such as security of browser extensions

quoting nevent1q…k02a

I'm not a dev, but I don't think it's actually a hard requirement (at least in Firefox, which the TBB forks from) to write to local storage. I think other sites write to memory, if localdb write fails -- or I think that's what snort.social was looking at on their git issue, but I may be misremembering. In a privacy browser, persistence isn't really a good thing.

Since Alby is centralized (please correct me if I'm wrong -- looks like LUD16 addresses and you're requesting email conf), why not just throw a warning banner (that local storage is disable, and you'll have to either enable it or reenter your key after every browser restart)? May be worth thinking about what *must* be written, and what can be regenerated / re-polled, but I'm just a user.

Cheers.

, compatibility with Tor

quoting nevent1q…ey3r

It doesn't work, unfortunately. Current version of Alby improperly depends on localdb storage in the browser, which can't (shouldn't) be enabled in the Tor Browser because it opens vulnerabilities. I actually wouldn't be Alby because of this, but I found a (terrible, painful, not recommended) workaround that let me limp along.

Many nostr webapps fail entirely in the Tor Browser due to missing exception handling for when localdb writes fail -- like snort.social -- and others initially appear to load but then don't function when you click buttons that write to localdb. Credit to snort.social, because I think they're actually looking at doing a patch to fix it, which is nice because I'd like to try it. Other webapps do work just fine (e.g. https://iris.to, which I'm using right now in the Tor Browser), because either they've written in fallbacks for when localdb is unavailable, or are written to avoid the problem, or... I don't actually know, but somehow they work.

For browser extensions like Alby, nos2x (on github) is an open source example that works fine. Please look at how they implemented it and push an Alby update. Because anybody privacy-conscious enough to use Nostr is probably privacy-conscious enough to be tempted by the Tor Browser, and in the long term, if people like me have to choose between Alby and Tor, Tor comes first.

Best regards.

, and the use of proof of work vanity npubs (npub1sn0wden…) (

quoting nevent1q…qw7e

He really studied everything down to mining key pairs and tor issues. As you’d expect. Didn’t just jump on.

).

We look forward to hearing more from Mr. Snowden!

Our meme of the day is (

quoting nevent1q…tj8g

).

Thank you for following **NostReport**. If you have any feedback for this account or would to contribute material for the next **NostReport**, please send us a DM. Keep it weird Nostriches!