Avatar
Cyberhub
f87d7e594c12133de18296f9e4a574c307b3b7f1c39f0806fe7d1992f6ce58ed
Good stories are lies that reveal truths more real than reality.

Look at that Nostr effect! Second wind of vertical growth. The nostr growth doesn't feel like it wants to slow down anytime soon either.

Thanks, I'll keep an eye on it to see if eden.nostr.land starts seeing my notes. It's been a while since it has worked for me.

I'll close extra clients on my desktop and see if that helps. How long for the rate limits to reset?

I'm getting 502 errors when I try to go to the eden and puravida invoice sites, so maybe I'm hitting some rate limits?

I have multiple clients open on my desktop, and have been doing several refreshes, so that may be my problem.

Any help from #[2] and #[3] is much appreciated.

Any ideas why my eden and puravida nostr land relays aren't working for me, #[0]?

Strange. I've already tried adding and removing wss://relay.orangepill.dev to my relay list several times, but Snort always shows it as red for me. And none of my notes are being seen on the relay.

I can't figure out why many of my paid relays are no longer working for me. Is it possible my payment status was reset or something? Has this happened to anyone else?

eden.nostr.land

puravida.nostr.land

relay.orangepill.dev

bitcoiner.social

Replying to Avatar Ezofox

Upgraded https://relay.orangepill.dev and https://nostr.plebchain.org to Nostream version 1.22.5.

Apologies for the brief downtime caused by the 504 timeout errors. The new version fixes it.

I wonder why I can't connect to relay.orangepill.dev? Could my payment status have been lost?

The new NostrGram tool for showing which relays a note is seen at is very handy. I'm definitely having relay problems, but I'm not sure what to do about it.

I have 5 paid relays, and nostr wine is the only one working for me.

wss://nostr.wine

wss://nostr.milou.lol

wss://eden.nostr.land

wss://relay.orangepill.dev

wss://bitcoiner.social

wss://puravida.nostr.land

I downloaded my complete note history from NostrGram (another cool tool!), but I don't know how to rebroadcast it to make sure it is available across all of my paid relays, or to new paid relays that I will join in the future. This seems like a critical piece of owning your own data.

Any suggestions or tips for why these paid relays may not be working for me before I start reaching out to the relay operators?

Replying to Avatar Sovereign Matt

Twitter threads on BOLT 12:

"BOLT 12 is a protocol layer solution to the invoice problem, while LNURL is an application layer solution.

This means BOLT 12 has better privacy, less centralization risk (DNS), and better UX for non-technical users.

What can we use BOLT 12 for?

1. Subscriptions.

2. Bitcoin Lightning ATMs

3. Private Refunds

Lightning took Nostr to the next level.

But BOLT 12 will take it even further.

BOLT 12 + NOSTR = THE EVERYTHING APP

If you didn’t already know, BOLT stands for Basis of Lightning Technology.

BOLTs are like BIPs for Lightning⚡️

BOLT 12 is already supported experimentally on

@blockstream

’s

@core_LN

and is also being actively implemented by the teams at

@acinq_co

,

@lightningdevkit

, &

@Lightning

BOLT 12 is distinct from BOLT 11 (the current invoicing spec on LN) in a bunch of different ways.

The main component of BOLT 12 is a new type of invoice called an “offer”.

An offer can be thought of as a ‘meta’ invoice- an invoice on top of an invoice.

Offers are useful because they are persistent and static.

This means that you can use them for donation pages, billboards, and zapping fellow plebs on Nostr!

BOLT 11 invoices, on the other hand, can only be used once, and must be generated in real-time.

BOLT 12 offers also allow you to create recurring subscriptions denominated in sats OR dollars.

This could be used to fund paid relays or creators (Patreon style), and for other subscription services.

BOLT 12 is Lightning native, which means that it’s different from LNURL/Static LN addresses because you aren’t required to run a web server to generate invoices.

Your Lightning node handles all the work.

This allows for fully self-custodial zapping⚡️”

https://twitter.com/LN_Capital/status/1627338727247814657?s=20

https://twitter.com/LN_Capital/status/1589321548133203968?s=20

Nostr improvements 🤝 lightning improvements

Unfortunately, the nature of social networks tends to create a kind of gravitational pull for people to engage most eagerly on accounts that have the most followers. If you engage smartly on a note posted by a popular account, rather than just post on your own account, your reach can be hugely magnified. Same goes for posting a thoughtful response to an account with low followers - instead you save your valuable reply for a similar note posted by a popular account.

But what if there were some way to incentivize a decentralizing engagement pattern to counter this naturally centralizing one? What if people were somehow rewarded for engaging with under-discovered small accounts that have the potential to become popular accounts?

Possible solutions?

Maybe the simple social dynamics of having more quality interactions with small accounts is the only solution that's possible or necessary here. But maybe there are creative incentives that can be designed in at the client or protocol level.

For example. What if notes were "collected" by the highest zapper. This would incentivize you to go out and find cool notes from under-discovered accounts and scoop up cool collectibles at bargain prices.