josh

Capital One has one of the best features. They allow you to block subscription fees from individual entities.
I can’t tell you how much anxiety this has lifted off me.

2025-04-24 17:53:04

- reply

nostrudel.ninja has the same feature. Shoutout @npub1ye5…knpr

2025-04-23 23:43:02

If you ever question the historical accuracy of the Bible, watch this guy's channel. His videos never fail to blow my mind. https://www.youtube.com/watch?v=34XBkm4QiLo

2025-04-22 23:05:55

- reply

Sounds amazing. Making camp by it? Would dream of that.

2025-04-21 14:36:49

“But people who aren’t spiritual can’t receive these truths from God’s Spirit. It all sounds foolish to them and they can’t understand it, for only those who are spiritual can understand what the Spirit means.”
‭‭1 Corinthians‬ ‭2‬:‭14‬ ‭NLT‬‬
Those who don’t acknowledge anything outside of the “natural world” are in for a shock for the things to come.

2025-04-20 00:54:46

- reply

@npub1z6f…m2tv

2025-04-19 23:40:20

- reply

It’s definitely illegal for it to be running.. I have wanted to do something similar but messing with gambling is risky.

2025-04-16 21:40:11

I like some Trader Joe’s products.. but their milk from “grass fed cows” doesn’t taste like it’s grass fed. Something seems off.

2025-04-16 20:56:26

- reply

If you study the life of David in the Bible, that’s where you will find a real man. He was a: mighty warrior, poet who wrote most of Psalms, musician, and most importantly, a man after God’s own heart.

2025-04-12 22:25:50

- reply

Yep. Switched to Firefox because of this.

2025-04-09 17:41:45

Trump saving himself from future lawsuits by first disclosing that it's a great time to buy? 😂 What in the world is going on?
#nevent1q…w74d
#nevent1q…7qsg

2025-04-08 19:13:28

10Y / 2Y spread just hit 50 bps, when turmoil usually hits full force. Buckle up.

2025-04-08 18:28:07

important
#nevent1q…qs5u

2025-04-07 21:43:14

#1 tip for buying things on Amazon: don’t use the default search algorithm.
Instead, click filters -> sort -> Avg. Customer Review.
Some results are manipulated, but this always helps me find the best products.

2025-04-07 13:24:45

This is some of the best advice. I've been saying this to friends and family for years. My dad told me when I was a kid that, if I am ever depressed or sad, go volunteer. For exactly the reasons in this post. It forces you to not focus on yourself and focus on others. What's the side effect? You will feel better. I promise you.
#nevent1q…j8py

2025-04-07 01:33:23

- reply

LUD16?

2025-04-05 16:04:35

Don’t forget the Olympic opening ceremony where they intentionally made a mockery of the Last Supper. Remember who the real enemy is though.
“For we are not fighting against flesh-and-blood enemies, but against evil rulers and authorities of the unseen world, against mighty powers in this dark world, and against evil spirits in the heavenly places.”
‭‭Ephesians‬ ‭6‬:‭12‬ ‭NLT‬‬

2025-04-05 13:47:22

I pray that my reaction is to go to Him in prayer.

2025-04-03 16:10:51

- reply

Interesting take.. would rather hold them accountable by not leaving the bitcoin on there? 😂

2025-04-03 01:47:37

- reply

He also said no tariffs on onchain fees #note1s8c…2w22

2025-04-02 20:46:48

It's crazy how fast these tariffs have taken place. https://blossom.westernbtc.com/0e191798a5d754141f8e10c3b6fb989661ece76396edb4acf4785c932477407d.png

2025-04-02 15:28:04

- reply

#note1mu8…l5kq

2025-04-02 12:08:47

@npub1xts…kk5s what is your throttling policy for your relays again? I'm almost finished making a game built on nostr, but I'm unsure at what frequency of posting from my game npub is going to be rejected.

2025-03-31 21:05:18

- reply

No way you started Goats and Other Stuff already.

2025-03-31 20:08:49

- reply

Looks like it keeps having the issue with the same other mint: 21mint.me @npub12rv…85vg

2025-03-31 18:58:38

- reply

I like this idea. Could be a flex to send something on-chain.

2025-03-31 14:00:58

- reply

Matt keeps returning to his ex-girlfriend.

2025-03-30 14:33:42

This is a good take
#note1xca…e75a

2025-03-30 11:51:01

- reply

Amazing.

2025-03-29 20:32:13

- reply

Shout out @npub1sg6…f63m for this

2025-03-29 11:13:21

Does anyone know if someone from Fold is on here? I'm trying to order the debit card but they have an old address that has "null" in it, which is causing the app to crash when I go to edit the address. It's the "Everything looks good" screen where I verify the shipping address.
cc: @npub1guh…6hjy

2025-03-29 03:06:31

- reply

Are you telling me to never read this or are you saying you have never read it.

2025-03-27 23:06:39

- reply

And to think it’s even easier for the fed.

2025-03-27 19:58:39

One of my favorite qualities of nostr: it works well with bad service.
You’re relying on a number of relays instead of 1 server, so chances are 1 or 2 of the relays are reachable.
This is especially noticeable with @npub18m7…q955.

2025-03-27 13:56:14

@npub194d…2u20 I’m trying the extension you’re using and I think I fixed the bugs 🤞. It’s my fault for recommending Gooti, it wasn’t in a place to be recommended. You can keep trying to nos2x-fox if you’re interested.

2025-03-26 22:03:42

- reply

Are you zapping my note or my account?

2025-03-26 19:43:30

Fireship is hard to beat, I linked to the part that made me think this. 😂 https://youtu.be/Tw18-4U7mts?t=142

2025-03-26 02:14:10

- reply

I see you're still running into errors. At this point, I think ChatGPT might have the answer (I pasted below). Basically, it might be that you have multiple extensions or maybe some niche browser that isn't widely supported. I would suggest using a browser like Firefox, installing Gooti, and start from there. Sorry man I'm trying everything to help you fix this 😅.
ChatGPT answer V
Below are some ideas and troubleshooting steps that may help in figuring out or working around these “FormatUnexpected character” and “secretsCache is undefined getSharedSecret” errors. They often indicate that:
Something is interfering with your NIP-44 decryption calls (the user’s signer/extension can’t return valid JSON),
Or the user’s signer is returning some unexpected/corrupted data instead of the original encrypted content,
Or the user has multiple signers / multiple Nostr extensions conflicting with each other,
Or the user is denying certain encryption/decryption calls (or the extension is failing them).
These are the most common reasons you’ll see:
FormatUnexpected character (at character 1) ApcXwCbrmC6sD4/OpmPB...
or
secretsCache is undefined getSharedSecret@moz-extension://...
1. The “FormatUnexpected character” Usually Means Bad JSON
Your code typically does something like:
const decrypted = await ndk.signer.decrypt(nostrUser, evt.content, 'nip44');
const rows = JSON.parse(decrypted);
If decrypted is not valid JSON (maybe just random binary or an error string), JSON.parse will throw “Unexpected character (at character 1).”
Why might decrypted be invalid?
The extension is returning some error or partial message instead of the real decrypted text.
The user’s extension or signer never actually performed the NIP-44 decryption. They might have canceled it, or the extension doesn’t properly handle it.
The user is running multiple conflicting Nostr extensions (for example, Nos2x, Alby, Nostr-Fox, etc.), so your app’s request to “sign or decrypt” is going to the wrong extension or is being garbled.
2. “secretsCache is undefined” in the Extension’s Stack Trace
This message suggests the extension’s internal state is broken – maybe the extension is out of sync or has a bug. For example, if the extension tries to create or fetch ephemeral keys for encryption but fails, it might produce that error.
3. Conflicts with Multiple Extensions
If the user has more than one extension that handles “Sign in with Nostr” or NIP-44 encryption, there can be collisions. Sometimes the browser picks the wrong extension to handle your request, or the extension tries to intercept calls it doesn’t fully support.
Try:
Disabling all but one extension that can handle Nostr signing and NIP-44 encryption, then reloading.
Clearing the extension’s cache or re-installing it.
4. The User Denies or Cancels Decryption
If the extension prompts “Allow [app name] to decrypt using your key?” and the user clicks “Cancel,” some signers return an empty string or a partial error that your code tries to JSON.parse. That results in a parse error.
5. “Couldn’t find corresponding private key” in Your Logs
Couldn't find cooresponding private key to public key:02e641c6324301619792025c962ec6e...
This typically means your wallet code is expecting the user to have a local set of eCash keys (or some ephemeral private key) but cannot locate it. Possibly:
The user minted tokens or created a wallet but never saved the private key event (kind=7375 or 17375) due to a partial denial or an extension error.
Or they are in a partially migrated / partially created wallet state.
When they come back, your code sees tokens referencing a public key that doesn’t exist in the user’s wallet.keys.
6. What Can You Suggest to the User?
Disable all but one Nostr/Bitcoin wallet extension (for example, if the user has Alby + Nos2x + Damus Extension, have them turn off everything except one) and then try again.
Update to the latest version of the extension. Some older versions have incomplete or buggy support for NIP-44 or for returning decrypted text in a consistent format.
Check if the extension is set to “Always Deny” or “Ask for permission every time” for encryption requests, and make sure the user actually approves the request.
If they continue to have issues, see if the extension has a debug mode or logs. In some extensions, you can open the background script console and see if it logs “secretsCache is undefined” or other internal errors that might be fixable by clearing the extension’s storage.
7. Potential Code Workarounds
If the user’s signer is unreliable or never properly returns JSON, you might let them:
Use an in-app signer (a local private key in your app) instead of the extension. That’s less secure but more reliable if the extension is buggy.
Export the minted tokens to some standard eCash format offline, rather than decrypting in the browser.
But typically, you want the extension to handle encryption safely. So the #1 fix is to have the user ensure they have a single, up-to-date, working extension that actually supports NIP-44 encryption/decryption.

2025-03-25 17:08:35

- reply

Imagine if this was inflation adjusted. Japan would look like a nosedive.

2025-03-25 11:54:23

- reply

I've made lots of changes to the wallet. Could you try again and see if you keep running into these errors? Should be more efficient and faster too.

2025-03-24 20:29:07

Side quest: create a bot that announces whenever a *suspected* solo miner finds a block. Do I embark?

2025-03-24 17:50:50

This has me delusional thinking this could happen to me if I bought one or two 😂. Even if I bought 1000 of the latest BitaxeNerdQ++, it’d take about 2.3 years. So you’re saying there’s a chance?
#note1al0…kvwg

2025-03-24 16:31:30

- reply

@npub1sg6…f63m likes this

2025-03-24 13:16:28

@npub12rv…85vg ChatGPT (o1) did a great job of summarizing how I go about: redeeming nutzaps, checking failed mint melts, and consolidating old token states. If anyone is curious of how I manage my Nostr Wallet state, check below! I still need to figure out the logic for the PENDING tokens. I haven't implemented ecash sends yet.
---
Here’s a high-level summary of how that “spent-check plus cleanup” code works and some things to keep in mind:
Combining All Potential Tokens Together
You merge tokens from three sources into one array:
The existing 7375 token event(s) for that mint (mg.decryptedTokenEvent).
Any redeemed nutzap tokens still in local storage (mg.nutzaps).
Your local “attempted sends” array (mg.attemptedSends – from sentTokensAttempted in local storage).
This means if the user tried to pay an invoice (thus minted some ephemeral “payment”/“remainder” tokens) but crashed/reloaded mid-process, those partial tokens wind up in local storage and get included in this single list.
Making an All-In-One checkstate Call
You then POST /v1/checkstate with all these tokens at once to see which are “UNSPENT” vs “SPENT.”
Anything that actually got redeemed / melted / double-spent on the mint side will come back as SPENT.
Anything still recognized by the mint as valid (including ephemeral tokens that never got used in a successful meltdown) will show up as UNSPENT.
Consolidating or Re-Saving
After the check, you have a unSpentTokens list. You can then do a fresh swap (if needed for re‑denomination or to unify everything into one set of proofs), and finally publish a new 7375 “token event” to store these updated proofs.
If some ephemeral tokens from a failed meltdown remain unspent on the mint, they’ll now get properly re‑recorded for the user.
If the meltdown actually worked and the tokens were used, they’ll be recognized as SPENT and excluded from the final set.
Cleans Up Partial States
Because of this step, your user’s final, consolidated set of tokens is always correct even if they half-finished an action the last time around.
You also publish a new 7375 event referencing the fresh set and can “delete” older events or ephemeral references.
Potential Concurrency or “Double-Spend” Edge Cases
If the user tries multiple meltdown attempts for the same tokens rapidly or in different browser tabs, there can be concurrency issues.
Generally, your checkstate call will see that some tokens became SPENT and remove them from the final set – so you won’t double-record them in 7375.
Just be aware that if the user does weird concurrency things, you could end up repeatedly rewriting events or having multiple partial states. This is somewhat unavoidable if a user truly tries to do “two meltdown calls in parallel,” but your final “cleanup on next load” logic still helps keep them from losing tokens.
Overall, your approach of “throw everything together (existing tokens + local nutzap tokens + local attempted-sends tokens) → run a spent check → re‑save or re‑swap anything that’s unspent” is a common and robust pattern. It ensures that if the user interrupts the process, the next time the wallet loads, you gather all old or partially minted tokens, see which are still valid, and store them properly in a single fresh event. That covers the most common fail scenarios.

2025-03-23 18:38:16

- reply

Sheesh why so late to the game #note1h5g…hlfz

2025-03-22 17:29:30

- reply

No menagerie?

2025-03-22 15:09:20

- reply

How someone handles being called out speaks volumes about their character.

2025-03-21 20:58:41

- reply

Convenience. Chromecast is nice.

2025-03-21 19:20:16

- reply

Sorry you're running into so many issues man. Doing my best to try and help.

2025-03-21 16:17:14

Google Chrome continues to push getting rid of ad blockers. Updated Chrome yesterday and it, again, disabled uBlockOrigin. They're stopping short of banning the extension because people would seek alternatives. I'm already there. What's your guys' preferred alternative browser?

2025-03-21 13:17:08

- reply

Did you accidentally deny encrypt / decrypt events? Try adjusting the setting for the site in your extension to allow: 7375, 5, and 7376 kind events as well as decrypt and encrypt. Then try refreshing the page.

2025-03-21 10:23:42

- reply

This is Dylan LeClairs company right?

2025-03-21 00:49:03

- reply

Chat is this true?

2025-03-20 22:45:09

- reply

Mercedes?
https://image.nostr.build/1dd3f8fff6e82df3587da6e4cc546e9717bfd6b698601cc3ab619857a590b593.jpg

2025-03-20 15:17:36

Be careful with what you share.
#nevent1q…6rwa

2025-03-20 12:10:10

- reply

I challenge people to not say “I don’t have time for that”. Say “it’s not a priority to me”. Changes everything.

2025-03-20 10:59:23

- reply

Interesting. Nostr is similar to sns when you put it that way 😂.

2025-03-19 15:17:58

Here's an obvious use case for nostr: 2-factor authentication. This could eliminate the unnecessary, resistive KYC points that many applications want you to use (Authy). Don't want to dox your nostr pubkey? Make a new one.
I'm incredibly annoyed by current 2-factor authentication options, I might make this. Might not be a priority at the moment though.

2025-03-18 02:25:39

- reply

https://image.nostr.build/f749399aeb1eeb563cd8f644c408f181219ce720418c7eac769bde28b4049d6f.jpg

2025-03-17 22:57:58

Nostr wallet coming together. Lot's of hidden features going on in the background here. Redeeming nutzaps into nostr wallet, deduplicating token events, removing spent tokens and deleting old token events, consolidating tokens into their smallest form, etc. General wallet clean up. The important parts like receiving and sending are coming 😅.
PS I think I broke my nostr wallet on Olas @npub1l2v…ajft. It's triple the amount for some reason.
@npub12rv…85vg
https://blossom.westernbtc.com/e00fdaf6d9aff2d73ff35f02b9de9c577cd9714b9f747c859634895687ce5a4a.mp4

2025-03-16 19:15:04

- reply

Whole pallet is amazing

2025-03-16 18:00:16

- reply

I think there’s a balance. We need heuristics. We can be that trusted source for our family / friends. My grandma is never going to do all this.

2025-03-15 21:27:57

- reply

Dang man. Incredible you did this by yourself.

2025-03-15 20:23:57

- reply

Accurate.

2025-03-15 13:02:34

@npub1jlr…ynqn I finally got around to syncing your notes. Pulled in quite a bit from Primal! I don't think @damus has upgraded negentropy though. https://blossom.westernbtc.com/a9ee2b398eee0d7645e9c3aad691fae37ef660521d3cc53c47ee03d299d76db5.png

2025-03-14 02:56:18

- reply

I figured it out. It looks like some of the tokens you received are malformed. Not sure where they came from but I'm pushing out a fix so it moves on gracefully if it can't decrypt the event. Should be ready in 5 minutes.

2025-03-14 00:43:06

- reply

You can set up a nostr wallet with https://westernbtc.com. I’m still building out most of the functionality. But I have a unique feature where you can receive zaps to your nostr wallet via [username]@westernbtc.com. For example what I have mine set to.

2025-03-14 00:40:13

- reply

Even what 1% is right now is incredible to see. Been so fun building.

2025-03-13 16:59:45

Unimpressive stat: 99.9% uptime.
Impressive stat: longest downtime: 1 hour.

2025-03-13 16:49:14

- reply

Is the issue you're running into that it's spinning and never finishes when you click decrypt on your extension? I've run into this issue with Gooti where I have to click the arrow next to Allow to Allow Once.
@npub1tgy…p0u4

2025-03-13 14:42:47

My futuristic prediction: our laptops will be replaced by our phones.
We’ll plug our phones into a docking station that hooks up an external monitor, keyboard, etc., when we want the desktop experience.

2025-03-13 12:42:26

- reply

This will take some digging because I can’t reproduce it yet. I’ll keep you posted.

2025-03-13 11:02:17

- reply

You're still running into this error even though you have the new extension? Even after you created a new wallet?

2025-03-13 10:59:22

- reply

If you join https://westernbtc.com, one of the services we offer is a blossom (media) server. Here it is in action https://blossom.westernbtc.com/7ef69c1cbfb0abbe3c3bb201059df539b51ee211757f117dc00c6a886e36d84d.gif

2025-03-13 10:44:54

- reply

You won't be able to use any wallet functionality if if you can't decrypt the messages.

2025-03-13 10:43:16

- reply

It looks like your extension is still having problems decrypting. Are you still using nos2x-fox? I would switch to https://getgooti.com

2025-03-12 20:03:12

- reply

The founder 😂

2025-03-12 12:09:54

- reply

It should now be scrollable and, in general, better suited for mobile.

2025-03-12 02:47:28

- reply

I actually just pushed out a change that allows you to bypass the wallet creation part. Let me know if you run into any more issues.

2025-03-12 02:26:29

- reply

I’ll take a look at it tomorrow morning. I’ve been making substantial changes and adding new features. Still working out the kinks. Thanks for the patience!

2025-03-12 01:14:57

- reply

I believe @npub194d…2u20 was trying to do a nip44 decrypt that contained a “+” character.

2025-03-11 21:58:52

- reply

I think that extension you're using isn't maintained. My recommendation would be https://getgooti.com

2025-03-10 17:40:34

- reply

Rare to see older men having this change of mindset. Respect to him.

2025-03-10 12:46:21

- reply

Okay I'm seeing the error now. You're right it has to do with your nos2x-fox extension. Never seen it before, so I'll start debugging.

2025-03-10 11:59:21

- reply

Haven't fixed the error yet but made better logging. Could you try recreating the error please?

2025-03-10 10:44:17

- reply

Thanks for reaching out! I’ll take a look.

2025-03-10 02:48:17

- reply

You can sell at a premium for fronting the risk of whatever this person you sell to does.

2025-03-08 22:56:48

@npub1l2v…ajft nostr wallet token management is hard. I feel like I need to make all these tools for the wallet "It looks like you have 10+ token events, let's clean those up", or "You have 100+ tokens totaling 5k sats, we can consolidate that to 5 tokens. Would you like to do that?" etc.

2025-03-07 22:30:32

- reply

Beautiful area!

2025-03-07 19:45:54

- reply

“Really” 🙅‍♂️

2025-03-05 17:48:15

- reply

The smudges are the real enemy here https://image.nostr.build/c2f19abfc4faeaf597dc2541997da0a0a1aec171e09616a2864726f52fd8e442.jpg

2025-03-04 03:41:00

Think of the most selfish person you know. Are they happy?
Now think of the most selfless person you know. Are they happy?

2025-03-03 19:27:33

- reply

👹

2025-03-03 19:04:46

- reply

I think most people on here don’t want to ADMIT that they like these charts. Keep doing what you do sir 🫡

2025-02-28 13:07:01

- reply

Trusted 2nd parties are vital. We all need heuristics.

2025-02-27 03:45:03

- reply

He’s back!

2025-02-26 22:50:58

Perspective. https://image.nostr.build/d504970ddf644aa55351a1ccae94de07d1fa08654526846e7b293d80f2b5d156.jpg