Old enough to remember when people were screaming from the rooftops that the mempool would never be empty again.
Discussion
LOL
Ahh yes, the long tradition of āthe sky is fallingā will always be a favorite feature of the btc community.
It will never be full again!!
Testing zaps for this noteā¦ we made one attempts toā”zap this note, at evanprim@ln.tips, over a period of less than a minute. In each case, we found that your lightning address server did not respond correctly. We recommend that you use a cloud-based Lightning node which is optimized for Nostr zaps, to get your zaps working.
How is that address even still listed? I havenāt had it on my account in over a year.
thanks, this is an interesting test case, we should be using the freshest "kind 0" data to get your address ( https://github.com/nostr-protocol/nips/blob/master/01.md#kinds ) ... we're going to look into it now and see how that happened...
OK, so we got your "kind 0" from the relay "wss://bostr.lightningspore.com", on 03/26 -- so about 10 days ago -- and this was the data we got in the event...
{
"name" => "Evan",
"about" => "He's just this guy, ya know? Tech consultant. Space laser technician. Lefty.",
"lud16" => "evanprim@ln.tips",
"nip05" => "_@evan.best",
"website" => "evan.best",
"display_name" => ""
},
So yes, your nip05 correctly reflects "_@evan.best", but your lud16 is set to "evanprim@ln.tips" ... it would be interesting to know if 1) you have just forgotten to update your lud16 OR.... if 2) bostr.lightningspore.com is serving a very outdated kind 0 for you....
I think itās number two. Any client I check lists my correct npub.cash address.
confirmed on our end, ok good, looks like nostr:npub1sp0rex959gshtgypve45upmm4vepxm4xea9eja4f2ftfj97euv5s3rj02v in this case was serving up an outdated kind zero for you. interesting.
Ahh haha I havenāt updated my bostr server instance in a bit. How did you even come across that?
um.... not sure, it's in a list of relays that we have... ok good, so u are saying that it might be serving out-of-date data, right?
The whole point of bostr was that it just collects data from a bunch of relays and proxies it over a single connection. So I donāt understand why itād be out of date data, but I havenāt restarted or updated the application in a while.
How do I get it to serve my correct ln address?
My server is actually down currently which might explain the issue. Iām not sure if something is caching the old value tagged to my relay.
Definitely not serving anything atm
Looks like we got a unique (never before seen) event from your relay about 24 hours ago, but not since. Not sure if that is helpful.
Yeah itās down. My Tailscale cert expired and now Iām trying to get inside so I can renew it
94.5% of all internet problems are because of expired certs.... was just at the airport yesterday and a bunch of the monitors were showing nice looking windows 10 alerts about expired certs....
FYI Iām getting each of your posts 3 times
You are getting duplicate posts from nostr:nprofile1qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59uq3qamnwvaz7tmwdaehgu3wd4hk6tcppemhxue69uhkummn9ekx7mp0qqsf07zg4hxyccnkdp07fppxmetpfzru3fg6mgzx3nk8r7af8qnjjygzpjv7a ? Isn't that your client's job, to get events from relays and de-duplicate them? I've never seen that before on nostr actually, I primarily use #yakihonneĀ and #coracleĀ and #damus, depending on what flavor of "broken" I am looking for on a particular day....
https://bostr.lightningspore.com/
Its back online, but I have to keep messing with my server
Cant boot the server up anymore, takes too much memory and becomes unusable. Had to upsize the instance temporarily
Yeah, it definitely is. Iāve ensured that zap address is gone everywhere.
Here we go. This is the metadata we have for you: #
:id => 90380,
:agent_id => 8953,
:event_id => 3857311,
:lud06 => "evanprim@ln.tips",
:website => "evan.best",
:nip05 => "_@evan.best",
:about => "He's just this guy, ya know? Tech consultant. Space laser technician. Lefty.",
:banner => "https://pbs.twimg.com/profile_banners/86647789/1644685872/1500x500",
:display_name => nil,
:name => "Evan",
:picture => "
",
:bot => nil,
:created_at => 2025-03-26 00:05:13.582070000 UTC +00:00,
:updated_at => 2025-03-26 00:05:13.582070000 UTC +00:00
}
Hi evan š“āā ļøš¤š nice to meet you š¤
Mempool FOMO was just another cycle. The only thing that never empties is bad takes
the eternal mempool right up there with ātransitory inflationā and āthis time itās different