Nostr

faisal

e4a1d3500841adb6734875d65c45e17b94d4d35db4d128dd288ca381f9bdcc90

🪁

If anyone is interested in Nostr Proof of Work, I have a draft NIP and functional implementation of a POW service provider that can remotely generate POW for your events before signing and publishing.

The general feedback and support was on Nostr, and the Github issue responses were more concerned based.

I built this entirely in anticipation for mass Nostr spam protection - in case we needed it urgently. We seem to be doing ok with spam now, however it’s possible we may need to revisit minimum POW for events when publishing - as a relay opt-in.

And just to clarify, I don’t like burnt CPU cycles either. Paying sats directly to a relay works well - however unless you pay for 10+ relays.. your events are not decentralised (as most relays move toward becoming paid to publish). POW helps address the issue of low value spam and flooding - it doesn’t solve everything.

https://github.com/nostr-protocol/nips/issues/340

I just read it and couldn’t make up my mind. We probably need time to see its use case.

- my core node crashed

- this crashed my ln node

- this also crashed my lnurl server.

ugh. All up now . Annoying.

how did core node crash?

Anything else I should do here?

wss://welcome.nostr.wine

Healed my body with ☀️

same

You could follow your mute list per Pablo suggestion! use at your own discretion 🤣 nostr:note1h8e2c27acjk2km7yyzcd242qvqhfcak0dv0dcf3k44fty85d97xqu9zf3a

Damus currently breaks if you leave display_name empty

I see your name as display_ name not supported. Is this your way to introduce changes or an interoperablity issue? I use damus with empty name field and never was an issue

Mike Dilger ☑️

If we want to grow nostr beyond bitcoiners, relays are going to have to accept fiat.

I think relays are going to accept different things at some point. I don’t think that’s conditional to the growth of the protocol as the UX of everything in question is significantly improving. I’ve seen none bitcoiners get very excited with their initial bitcoin experience here.

Lots of negativity over there for some reason

Mods aren’t doing their job

If you do through a source like HablaNews it should be fine. But I am hearing that many clients want to drop the Markdown support because of these issues.

Please drop it

https://github.com/damus-io/damus/issues/1058

Can you try another client and see?

Funny - I’ve been 429’d by imgur for about a week now. Thought it was only an issue on my personal VPN but now seeing others complain like this makes me think its actually nostr clients getting us rate limited 😂

🤣🤣

so weird that I’m not seeing this

no issue here

Found this https://coinstr.app nostr multi-custody solution. Maybe better than centralized wallets sharing schemes? Though, what creative phishing and social engineering attacks we will see…

def

Just updated and checked universe. Much better.

Just pushed build 17, this adds event preloading! Images, previews and translations will be automatically loaded by the time you scroll into view. This reduces the overall jankiness when scrolling. Check it out:

https://cdn.jb55.com/s/event-preloading-2.mp4

Nice, thanks. It would be nice to have an option to not download remote content

GigaBTC 🌽⚡️🔑

Any Damus TestFlight users seeing this?

What’s the percentage for last 10 days?

When 1 sat/vByte nostr:note1044qymh3muekcmvkdps960zjxzqx9ev80pwvvyn6242vdnay47asj40lkp

this is a test, publishing from the CLI without access to my nsec ✌️

🤔

Is this somewhat similar to what Amethyst is doing?

👀

Load More