Basically topless dudes in the jungle. It's a thing here.
We have a large Japanese community from what I can tell when looking at the popular notes DVM in the morning.
Me, after looking in the NIP repo PRs
This could be a nice idea π‘( nostr:nprofile1qqsfnw64j8y3zesqlpz3qlf3lx6eutmu0cy6rluq96z0r4pa54tu5eqpz9mhxue69uhkummnw3ezuamfdejj7qg0waehxw309ajxzmt4wvhxjme0hynkd5)
Unfortunately for now you have to navigate through them.
For public bookmarks it could be a DVM. If DVMs don't get killed off.
Germany will introduce a mandatory account with the state where everything about you is stored in a central place. Nothing to see here.
I can't even open reddit. GM.
"Why did you stop using Nostr"
https://old.reddit.com/r/nostr/comments/1josljh/stop/
> it's an annoying fucking echo chamber of mostly crypto-bros mostly jerking each other off. with a dash of keto pics, and neonazi memes, oh and constant "GM" messages". I think it's hilarious how unaware most of the users on there think they'll "succeed"
GM Will
Tradeoff between a centralized cache relay and scanning everyone's follower list on all relays all over nostr.
Maybe that's even better, idk. I built this 2 years ago and now it's updated to work with 1.0.0 π
This is all so stupid.
Also no cloudflare config etc (if this is still needed, idk)
It's for multiple backends. If the extension works for you, good. I use this with the API as well, to automatically create accounts.
I hereby signal I will not support any change to NIP90 that changes the very nature of it. If the core devs decide to go for http API calls and bots for it's replacement I will not comply. If clients decide to go with it, be my guest. We have something unique and instead of embracing it, there's plans to replace it with the mess from the old web.
I'm not saying everything is perfect right now. I'm saying killing of a unique feature is not something I will support. If the free market supports their plans, so be it. I don't.
This allows you to host your own ln address with your own lnd/ln it's backend and support of zaps. The new release supports lnbits 1.0.0 that had some breaking changes.
Nostdress (self hosted loghtning addresses with nip57 support) has been updated to work with lnbits 1.0.0.
If you run an older version of lnbits, also run an older version of nostdress.
If you updated to lnbits 1.0.0 this will make it work again.
https://github.com/believethehype/nostdress/releases/tag/v.0.9.2.3
Nostdress (self hosted loghtning addresses with nip57 support) has been updated to work with lnbits 1.0.0.
If you run an older version of lnbits, also run an older version of nostdress.
If you updated to lnbits 1.0.0 this will make it work again.
https://github.com/believethehype/nostdress/releases/tag/v.0.9.2.3
That being sad. Nostdress is broken for lnbits 1.0.0 is broken. All my ln addresses are broken, all my DVMs ln addresses are broken. I don't know how to fix it because i think it's a bug in lnbits. FML.
Me: Changes node to knots.
Works amazingly well.
Hey there's an 1.0.0 update for lnbits, let's do that too..
Happy (international and national) socialist's labour day. π
A good time to remember all the time that gets stolen from you through taxes, debt and inflation by people with guns and money printers.
https://www.swanbitcoin.com/politics/why-bitcoin-will-end-the-worst-heist-in-history/
Will be fixed in next update. Fix is already merged.
