Tyler Burns

InfoSec - Cypherpunk - Vegan Ⓥ 🌱 - Animal Rights - Bitcoin - Privacy Proponent - Frugality>Consumption

Public Key

npub1d30mhvhd0sagmu83wdm26wqk00heptfn05xvgmfx7r9xscstnfcs7xynp3

NIP-05 Address

Profile Code

nprofile1qqsxchamktkhcw5d7rchxa4d8qt8hmus45eh6rxyd5n0pjngvg9e5ugprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqyv8wumn8ghj7un9d3shjtnnv96xcctww35hxtnfdudkndpj

Publishing to

relay.noswhere.com

relay.satlantis.io

us.azzamo.net

relay.anonymousgreen.com

Author Public Key

npub1d30mhvhd0sagmu83wdm26wqk00heptfn05xvgmfx7r9xscstnfcs7xynp3

Show more details

Last Notes

2026-06-27 22:42:33 UTC

- reply

For real, the one weekend I missed and they hit it! Ugh, I've been participating in these block parties for so long, but was busy this weekend and forgot to point it to the pool.

2026-06-27 19:45:10 UTC

- reply

The one weekend I was busy and didn't point my miner to the block party! 😭

2026-06-27 02:52:57 UTC

- reply

https://antoinep.com/posts/relay_policy_drama/

2026-06-26 23:55:44 UTC

- reply

You don't give them an alias for you to go by to make convo a little easier?

2026-06-26 15:10:26 UTC

- reply

What is going on in Venezuela is such a tragedy. The images are horrific. They need as much support as they can get. I love that platforms along with bitcoin can get funds directly to the people that need it most. Though sadly, usually what is most needed at times like this is simply more helping hands.
#nevent1q…75m8

2026-06-26 14:11:10 UTC

- reply

That's why I specifically mentioned sustainable tree forestry.

2026-06-26 06:10:55 UTC

- reply

As a tennis player myself, it is really something to see pros play at ground level. You can't quite appreciate the power as much when watching from above on TV. At ground level, the power and speed is so much more apparent.

2026-06-26 02:24:48 UTC

- reply

Sounds like a challenge.

2026-06-26 01:32:28 UTC

- reply

https://blockspace.media/insight/everything-you-need-to-know-about-the-op_return-data-limit-debate/

2026-06-26 01:23:47 UTC

- reply

Haha, I try not to play that game. Any market price driven by leverage will always be a short term price. That leverage will always come due and with it, the price. While it is mind-boggling that the price has come down $67k, I try not to think about my net worth coming down similarly.
For my own sanity, I focus on my net worth at times like this for future planning. My net worth in bear markets highlights true market conviction in what bitcoin is. There is a growing number of people year after year that are choosing to use and hold bitcoin even during the darkest bear markets. It actually brings me solace thinking about that in times like this. Sentiment is extremely bearish and yet here we are at ~$60k.

2026-06-26 01:13:11 UTC

- reply

If there wasn't any collateral damage to keeping it at 83 bytes, I'd be fine with that. The problem is all about comparative harm and I feel there is far more harm in leaving the limit at 83 bytes than there is in effectively removing it.
It is a shame that the debate has fixated on the monetary use case of bitcoin rather than the technical reasonings for wanting the limit removed to avoid those harmful side effects of not doing so. After all, I don't think there are too many in this debate that don't want bitcoin's use case to be monetary.

2026-06-26 00:26:38 UTC

- reply

I grew up in an Irish catholic family, married a catholic, and was married in a catholic church.
Your analogy is faulty and attempts to reframe things based on a strawman argument. v30 proponents never stated their argument was "well, people could already break in, so who cares, let's remove the fence."
It was/is all about comparative harm. This argument has been made countless times and to suggest you haven't heard it before means perhaps you haven't been paying attention. The "gate" wasn't just a leaky gate, it is actively directing activity to a far more harmful path. The entire existence of OP_RETURN came about to allow for provably unspendable outputs to avoid the UTXO set from becoming bloated. The OP_RETURN limit is actively harmful now due to the fact that it directs activity toward the UTXO set which increases the cost of running a bitcoin node (since every node must store the entirety of the set in memory). It also promotes the use of alternative relay networks such as Libre Relay (which is harmfully centralizing). Not to mention the fact that default relay policy should be as close to matching what actually ends up in a block or else it becomes difficult to determine what the fee market is and what the broader mempool looks like. Again, this has all been discussed before and pretending like v30 proponent's arguments were something otherwise is disingenuous.
A chain-split by any other name is still a chain-split.

2026-06-25 23:17:31 UTC

- reply

That doesn't sound very catholic to me.
My wife isn't vegan. I hate the sin, not the sinner and I've always lived by that. You're free to make whatever decision you like. But frankly, you just sound insufferable at this point and I prefer to not engage with that. I'll debate the technical aspect based on its merit, but I'm not going to refrain from engaging in the rest of that.
Generally game theory is not a safe upgrade mechanism for a trillion+ dollar monetary network. Just ask BCashers how that went for them. But if you'd prefer not to learn lessons from past mistakes, but all means learn them the hard way in 43 days.

2026-06-25 22:45:12 UTC

- reply

Ad hominems won't prevent you being forked off in 43 days.

2026-06-25 22:44:22 UTC

- reply

You will be hardforked from bitcoin nodes running version 25 (the latest version on 10/9/23) in 43 days as well. Your argument is faulty.
Again, as I previously stated, big difference between relay policy and consensus rules.

2026-06-25 22:20:50 UTC

- reply

That is factually incorrect. It is absolutely not the same. The introduction of v30+ running along-side nodes running pre-v30 never introduced the risk of a chain split, which is precisely what BIP-110 does. And it does so with an extremely dangerous activation method (only 55% signaling needed) and with no replay protection as well. It is reckless development, just like running knots is reckless.
Have fun with you're hard fork in 43 days. Tick tock.

2026-06-25 21:51:50 UTC

- reply

You would have to ask Satoshi that. He was the one that put in the 100kb size limit, which is 1/10th of the block space to prevent any single txn from consuming an entire block.
The weight units introduced with Segwit are just a 4x multiple of both.
Again, it needs to be reiterated that this isn't consensus policy. This is relay policy.

2026-06-25 17:46:51 UTC

- reply

https://blockspace.media/insight/everything-you-need-to-know-about-the-op_return-data-limit-debate/
https://blog.lopp.net/a-laymans-guide-to-bip-110/

2026-06-25 17:45:01 UTC

- reply

The removal of the limit makes technical sense. The drama in response to it is the virtue signaling theater.

2026-06-23 20:27:36 UTC

- reply

It isn't just two weeks when there is no hash power. Bitcoin operates on block time, we just say two weeks because that's what it averages out to. But in reality, you're waiting for 2016 blocks to pass no matter how long that takes.

2026-06-22 22:29:54 UTC

This is crazy. Surveillance is about to get far far worse before it gets better.
#nevent1q…9jcv

2026-06-22 03:34:14 UTC

- reply

#nevent1q…2xmk

2026-06-20 20:43:21 UTC

- reply

https://blossom.primal.net/5074199d90e9a635e448c7e1f100524ddcef1124e5ee48323b7b8f29e4d2aef1.jpg

2026-06-19 15:59:07 UTC

When some tells me the chances of mining a solo block with my single Bitaxe...
https://blossom.primal.net/3a540da0a902ffe8859fefb7cc14d2c0581848dee515d1c6f8dcdf63412a0d52.jpg
#nevent1q…kz0k

2026-06-19 15:56:35 UTC

- reply

Raising the difficulty one bitaxe at a time. 🫡

2026-06-19 12:19:17 UTC

- reply

I can't speak to their reasoning. I know they put a lot of work into hardening it. Thankfully you can still install any browser you'd like on GrapheneOS. I find Vanadium doesn't work well with autofill services like Bitwarden, so it can be cumbersome to use for some things anyway.

2026-06-18 23:50:04 UTC

I really hate when I have a typo in a Nostr note that I just published. 😭

2026-06-18 22:44:18 UTC

It is long passed due that users need to ditch Chrome enmass as well as any Chromium-based browser. They control far too much of the browser market.
#nevent1q…nz45

2026-06-18 16:30:08 UTC

- reply

They're on Mastodon and their posts are just bridged to Nostr.

2026-06-18 12:28:57 UTC

- reply

I think it is more about how this deao highlights how completely pointless the war ultimately was. So much needless destruction that put the world on a more dangerous and costly path than how things were prior to the war.

2026-06-18 04:29:16 UTC

GN Nostr

2026-06-18 03:44:32 UTC

I was just thinking about how NIP-05 is largely useless for most people, but then was thinking about how that is largely because people don't do anything with it other than stick it in the KIND-0 profile.
In the event of an nsec compromise, it would be useful *prior* to that happening to sign a KIND-1 note stating what your NIP-05 identifier/domain is. That way if/when your nsec is compromised, you can successfully migrate to a new nsec/npub and refer to that note stating what your true NIP-05 identifier is that can't be forged because if was signed with your old nsec.
If your nsec is compromised, the attacker can overwrite what your NIP-05 is in your profile, since relays generally only keep the latest KIND-0 event. But you'll still always be able to refer to that note you signed prior to your nsec compromised since it can't be forged.
So yes, NIP-05 can be very valuable in this instance. I urge you all to pre-emptively publish a note stating what your NIP-05 indentifier is so that you can refer to its immutability should you ever need to in the future.
#nevent1q…plz6

2026-06-18 03:43:05 UTC

My NIP-05 identifier is tylerburnsveg@anonymousgreen.com — In the event of my untimely nsec compromise, look to this domain for my true Nostr profile.

2026-06-18 01:47:09 UTC

- reply

I'm so devastated for you. You've had to face so much tragedy. Fuck cancer, is right.
Despite that tragedy, the love and happiness we share with those close to us is worth that heartache. The worse your heartache, the strong the love was.
I'm wishing you and your family well. 🫂

2026-06-17 11:03:00 UTC

- reply

Then the US better pull all funding support for Israel if they are to go their own path.

2026-06-17 03:03:32 UTC

- reply

That's amazing!

2026-06-15 21:57:01 UTC

I just nuked 61 Nostr zombies from orbit using the NUCLEAR OPTION in #PlebsVsZombies! ☢️🧟‍♂️🧟‍♀️
💀 MAXIMUM CARNAGE ACHIEVED! 💀
My Zombie Score™ was 19%! What's yours?
🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟪🟩🟩🟩
Follow @npub1pvz…sd4h and join the hunt at: 🏹
https://plebsvszombies.cc

2026-06-15 15:25:03 UTC

Really good documentary. These women sail the North Atlantic on this rustic catamaran while overcoming whatever obstacle is thrown their way.
I love technology, I've built my career around it. But I think there is so much more to gain as individuals if we learn to live without it, even if for a brief moment.
https://www.womenandthewind.com/

2026-06-15 12:24:24 UTC

- reply

Another comment about Nostr as well. Seems like more word is getting out about Nostr, which is good. I think were going to see a lot more users here over the next year.
https://blossom.primal.net/3fa9705ae51f4f6fd9a6360c47b4170f0b6526ddea8b282d7b4843d1721a83c6.jpg

2026-06-15 12:17:01 UTC

Interesting interaction I saw on Reddit just now on a post about the UK social media ban.
...change is in the air...
https://blossom.primal.net/ff0b828afe8fba8a9478ab1ffe3e6f88b4adc69d67281f608109a9936d9c071e.jpg

2026-06-15 12:11:01 UTC

- reply

So my Zeus runs in the background most of the time because I also use it with NWC for sending Zaps myself. So most of the time for me zaps I receive just come right through without any need to manually settle. But I have received a few zaps while offline and they just settled when I opened the app next and saw that I had a zap to receive. Personally I use it because I was previously hosting my own LN address on my own domain, but decided I didn't want to expose my own IP on my own web server any more. So this was a good non-custodial compromise.

2026-06-15 11:47:26 UTC

- reply

The implementation is pretty seamless with Zeus. Not sure what other wallets out there might use it though.

2026-06-15 11:27:31 UTC

- reply

https://github.com/supertestnet/zaplocker

2026-06-15 11:16:42 UTC

- reply

Is this similar to Zaplocker that @nprofile…ctjf uses in their wallet? It works pretty well.

2026-06-15 02:34:52 UTC

- reply

Rochester is a great city. ✌

2026-06-14 23:37:43 UTC

Having left the corporate IT world, I don't miss the planned obsolescence of IT infrastructure and software combined with a patch work of deprecated protocols for the sake of backward compatibility. All of this built upon closed-source software that kept you relient upon third-party vendors that would rip you off every billing cycle because they knew you weren't going to migrate elsewhere. So much money wasted in the corporate world, it is really astonishing.
#nevent1q…qp2j

2026-06-14 13:49:46 UTC

Tick tock
https://jlopp.github.io/knotzi-death-march/
#nevent1q…70zc

2026-06-14 13:44:02 UTC

- reply

I tried hosting my own instance of Primal Cache Server (since the client allows for custom cache servers), but the repository is so out of date and the README install instructions don't match the code. Based on several Github Issues posted, looks like it doesn't run on any of the latest versions of Nix and none of the run commands are available or working. I feel like if they're going to make it an option to run your own cache server, it should be maintained better to allow people to do so. Otherwise it is a bit of theater.
https://github.com/PrimalHQ/primal-server/issues/17
At this point their backend server seems to be barely maintained and/or their developers are working on it via a non-public/local repository running old versions of Nix.

2026-06-13 15:46:31 UTC

- reply

Fiat can't really contract the money supply since fiat, at this point, inherently relies upon expanding the money supply to keep debts from collapsing the system.
Americans are and always have been the beneficiaries of having the world reserve currency. Printing the currency to facilitate trade and thus allow foreign countries to hold it (treasuries) in reserve is what keeps the system afloat. Any contraction in the supply would go against this hegemony.
As far as taxing goes, the bottom demographics are already largely not taxed. If you're not employed or are low income, you're not pay much if any taxes (speaking from the US's perspective at least).

2026-06-13 15:33:36 UTC

- reply

I think UBI could work if in tandem with UBI, other safety net programs such as unemployment, welfare, SNAP, etc are done away with. That way it removes the incentive to not work since those programs depend upon a beneficiary not working. It would be a more fair system that everyone benefits from, rather that selectively incentiving those at the bottom to continue not working and therefore perpetuates the problem rather than actually trying to solve one.
That being said, I've yet to see whether or not AI disrupts the workforce to the degree that AI companies are touting their products are going to do. Seems like a lot of marketing. I'd much rather first see the monetary system fixed that brings about far more exploitation and inequities in the world than any implementation of UBI on top of an already broken system.

2026-06-13 02:26:27 UTC

- reply

Those are some intense moon boots.

2026-06-13 01:28:29 UTC

- reply

Isn't he an NBA basketball player?

2026-06-13 00:38:29 UTC

I feel like there is a big gap in the app ecosystem for users running a pruned node. I've always run a full archival node and recently spun up another pruned node to test out and have come to realize that there aren't many wallet options or server middleware to cross the gap for pruned node users.
There used to be Electrum Personal Server that worked with pruned nodes for users to connect their wallet apps to, but that is no longer maintained.
Seems like one of the few options is to use Sparrow to connect directly to Core via RPC on the desktop. But that leaves a big gap for mobile solutions.
There are plenty of Lightning wallets if you're running a lightning layer on top of bitcoin. But again, not many solutions for validating your on-chain txns or using a cold wallet with a pruned node. Most on-chain wallets use the Electrum protocol that require a full archival node at this point in time.

2026-06-11 23:42:49 UTC

https://blossom.primal.net/8747e2d2246f0a59b1d714d93ab89e9e3a7b82c51aceed6f2fb4e2d219ed25c8.mp4
#nevent1q…3kxl

2026-06-11 16:04:46 UTC

- reply

It is just far too coincidental that all these governments around the world are implementing "age restrictions" and requiring ID for social media, etc at the same time for it not to be a coordinated effort to push for more mass surveillance. You can't convince me otherwise. No one is asking for this outside of government.

2026-06-11 15:43:33 UTC

- reply

Narrator: The train did in fact come to an abrupt halt in 58 days.

2026-06-10 19:23:21 UTC

When I set up my new relay, I was able to take my note history from @nprofile…utvn and import it directly into Strfry. Pretty cool. Thanks @nprofile…0k9y It is nice having a local copy of your notes on your phone. I just wish more clients supported having local relays.
#nevent1q…gjaj

2026-06-10 17:53:55 UTC

My self-sovereign bitcoin/nostr app stack is in a really good place right now. I'm amazed at the progress of both of these ecosystems over the last several years. Looking back, say just 10 years ago, things were so very different and unpolished. It will be interesting to see where we are 10 years from now.

2026-06-10 14:56:15 UTC

- reply

The problem with that is that most of my stocks are locked in retirement accounts that have withdrawals restricted to 59.5yrs old (or performing limited Roth ladder schemes to withdraw penalty free early). Meanwhile bitcoin is highly liquid and available at any time to spend and use. While I'd love to be able to sell stocks first, the reality is that my bitcoin was/is my after tax investment that I can spend in my early years while I wait for my other accounts to become available.

2026-06-10 14:13:44 UTC

The market will eventually come to terms with the fact that the rest of the "crypto" industry is downright fradulent and bitcoin is where the real value lies. It was never "blockchain, but not bitcoin" like many wanted you to believe. Bitcoin is the blockchain.
#nevent1q…e7ls

2026-06-10 13:56:46 UTC

Running my own personal nostr relay now. Long overdue now that the outbox model has been more popular for a while.

2026-06-10 03:44:06 UTC

I'm so glad we don't know who Satoshi is so that we don't end up finding out something like this. 😆
#nevent1q…hwhe

2026-06-09 03:05:04 UTC

- reply

There is a big difference between UI/UX end user testing and fuzzing an app for vulnerabilities (which it seems like you're partly describing here). One can be performed by a casual end-user to provide feedback on the typical end-user experience, the other needs to be tightly integrated into your DevSecOps SDLC to ensure that vulns are being found and remediated prior to them making it into production. Testing for edge cases with the casual enduser experience likely results in finding non-critical bugs that aren't the end of the world, but finding edge cases through fuzzing and code review can yield critical vulnerabilities that would be catastrophic in production.

2026-06-09 02:32:53 UTC

- reply

To be fair, you can run your own Primal caching server and the client does allow you to input your own server instead of using and relying on theirs. But it is a fairly beefy server that pulls notes in real time from other relays that you specify regardless of whether or not your client is actually requesting those notes. So it isn't exactly a server that you can spin up without some decent hardware and bandwidth.
That said, I do think there is a place for clients like Primal on the ecosystem. Primal is great for use with mobile metered connections precisely because of that caching services. Data use with Primal is far lower than with other clients, especially with the outbox model now being more widely used. Yes, the potential for censorship is going to be there, but the great thing about Nostr is that none of use are locked into any single client. I find myself using multiple clients regularly simply because I have yet to find the perfect client for every situation.

2026-06-07 23:15:59 UTC

- reply

@npub16x7…a44x is definitely a cool client, one of the better ones that deserves more recognition. It has a lot of cool features.

2026-06-07 14:15:11 UTC

Very interesting video. I think about this often. As someone who pursued FIRE, it makes me question why humans put in 40+ hour work weeks simply in the name of productivity and consumption.
https://youtu.be/TQd2k1pEXp4

2026-06-07 03:26:30 UTC

I am once again asking for a block from the bitcoin network. Brutal. Difficulty adjustment can't come soon enough...
https://image.nostr.build/82b992e097b8b8dc254a4688caf8776ea230543a4234f34dca349ddc96dbfbe2.jpg
#nevent1q…npad

2026-06-06 18:03:16 UTC

- reply

Ya, they had access to it all, present the evidence then. Their words alone aren't trustworthy what so ever.

2026-06-06 03:21:42 UTC

It never fails that in the rarity that I do send an on-chain txn, it has now been an hour since the last block. 😆

2026-06-05 20:39:39 UTC

Syncing the lightning graph entirely over Tor on a new node is painful. More so than an IBD.

2026-06-02 13:26:49 UTC

- reply

You're not forced into that security model with Nostr either if you don't want. You can always use a key vault for your nsec as well, like with what NIP07 and NIP46 provide.

2026-06-02 11:47:49 UTC

- reply

Ahhh, the infallible trusted third party. Phew!!! Had me worried there for a second.

2026-05-30 14:29:19 UTC

- reply

I bought my bidet for $50. They're not expensive at all.

2026-05-29 22:06:20 UTC

- reply

Djokovic has 24 slams in his bag, not 22.

2026-05-27 21:46:45 UTC

- reply

Strange. Maybe try a different relay?

2026-05-27 20:56:13 UTC

- reply

That's not true at all. Difficulty, on average, only changes by a few small percentage points each adjustment. So there is plenty of time to remain profitable so long as you aren't getting into mining with an unprofitable setup from the get-go.

2026-05-27 20:47:21 UTC

- reply

Worked fine with Amber for me. I just copied the bunker link it gave me and it connected.

2026-05-26 22:13:28 UTC

- reply

Those are the people that get replaced.

2026-05-25 00:56:32 UTC

- reply

🌱

2026-05-24 02:59:26 UTC

- reply

Don't put the link in your note! Some noob is going to click it. 😆

2026-05-23 14:28:06 UTC

- reply

Ya, I didn't have too much of a need for a PoS solution, so it wasn't a major consideration for me.

2026-05-23 11:26:26 UTC

- reply

This is a good writeup of Virtual Private Node. I might have to give it a try and see what it is like. For years, I've been running my own full node with each part of the stack manually installed, permissioned, containerized, and isolated from each other. Full node, LND, mempool, THub, LNBits, Electrs. It is a lot of work keeping each component up to date.
I've often pondered about streamlining things and moving away from the full stack and manual approach, but have never found a good automated server platform with the right trade-offs. This one is definitely interesting.
#nevent1q…u0q2

2026-05-22 17:18:46 UTC

- reply

I think this is the FO part of FAFO.

2026-05-22 16:12:59 UTC

- reply

I always find that the outside of the dough dries out a little whenever I use a towel to cover the bowl while it rests for the initial rise. So I end up using a solid top to cover it. Does that happen for you during that phase? Is your towel damp? Once I break it into balls it goes in the dough box, so that's not an issue.

2026-05-22 16:06:41 UTC

- reply

So by that logic, I can take my gun and fire it off high into the air. As long as no one gets hurt, the only crime here is for the people that do in fact end up hurting people.
The crime is in the endangerment of others through a reckless act. The victims are those that were endangered. Because just like firing a gun off recklessly and needlessly into the air will kill an innocent someone at some point, so will driving without a seatbelt.

2026-05-22 15:25:02 UTC

- reply

From your violation of my personal/property rights. Being ejected by not wearing a seatbelt violates the rights of those around you.

2026-05-22 10:21:59 UTC

- reply

I didn't say you said that. But getting a ticket for something that is dangerous to those around you is appropriate as usual. Complying with said law isn't an option if it is dangerous to others.

2026-05-22 02:20:17 UTC

- reply

Not wearing a seatbelt isn't just for your own safety, but the safety of others in the car with you as well as outside the car. You become a projectile when not wearing a seat belt. I've seen people thrown from the car a hundred feet. I've seen someone not wearing their seatbelt kill the child next to them who was wearing a seatbelt. I've seen people die from accidents that you'd walk away from without a scratch on you if wearing a seatbelt. Not wearing one is idiotic and not wearing one puts others in danger. Your rights end the second you put others in danger.

2026-05-21 10:58:23 UTC

- reply

Great article. One thing that wasn't really touched on, although maybe tangentially, is the idea that you could have no idea that you received any on-chain Zap at all. Only two clients support this misguided feature. That means that for all other Nostr users that are using other clients, they could have no idea that they've received on-chain Zaps to their npub.
Since most clients (thankfully) don't support on-chain Zaps, their clients have no way of notifying them that they're receiving money to their npub this way. Furthermore, people who are using on-chain Zap clients (Ditto, Amethyst), these clients can't in any way determine if the person they're sending on-chain Zaps to use or have ever used one of these clients. It is far more likely than not that they'll be sending Zaps to a person who won't be notified in any way that they received anything.
Putting aside all the horrible practices that on-chain Zaps have for privacy that you outlined, the entire argument for on-chain Zaps at the moment is convenience. But I can't think of a worse UX for a common user than to have build a payment system that will in all likelyihood result in the recipient not being notified that they received anything at all or not having any means for the sender to know who they can actually successfully send money to and who they can't.
At least if I try to send a lightning Zap to someone without a LN address, it will say that I can't. That's what proper UX should do.

2026-05-20 04:49:52 UTC

- reply

In fact, given that LN addresses have been around for longer than Zap event kinds have, most LN address configurations didn't support Nostr Zaps (event kind 9735) for a long while. Therefore, I would imagine that a large number of zaps that have ever taken place weren't recorded publicly on Nostr as events.

2026-05-20 04:42:42 UTC

- reply

Technically you could have your LN address not send kind 9735 events upon txn receipt. In which case, you can receive zaps without them being made public on Nostr. Can't do that with on-chain payments to your npub.

2026-05-17 03:11:50 UTC

- reply

Oh man, now I need to play some DRG. For Carl!

2026-05-08 02:33:46 UTC

Living on bitcoin is extremely difficult, at least in the USA where I'm at. I haven't used a centralized exchange in probably 5 years and I really don't want to go that route.
But I'm realizing, then unless things change soon, that's the only option. Businesses don't accept it. P2P exchanges aren't reliable enough and are often riddled with fraudsters. And even if that weren't the case, dealing with P2P with the fiat banking system is a massive headache. The second you have any sort of volume with transaction activity, it raises alarm bells with fraud departments and I've had to sit on calls with them and explain in detail the reason for all my transactions over the last week, etc. It's annoying to deal with as well as stressful wondering if they'll shut my account down if I say the wrong thing.
I'm not moving, though I wish I could, but family obligations are local, so we're staying put.
Things need to get better if we want bitcoin to be money. Laws, infrastructure, technology, adoption, perception, etc. Bitcoin isn't just used by criminals, but the stigma of that permeates through legacy finance like a plague.
I'm hopeful we'll get there someday, but I'm not sure if it will be soon enough for me before I cave and sign back up with the centralized exchanges I swore off many years ago.

2026-05-07 19:58:42 UTC

- reply

You can share mute lists, but ya, regex support would definitely be beneficial. Ultimately there are better ways at controlling spam and bots though than a blacklist type approach.

2026-05-07 18:18:27 UTC

- reply

What the heck. I already had it installed on my phone. Haha. I must've downloaded it at some point in the past, but forgot about actually trying it out. Going to give this a try now.

2026-05-07 18:14:16 UTC

- reply

Oh nice. Didn't know about that. I will definitely have to check that out. Thanks.

2026-05-07 17:53:35 UTC

- reply

Isn't that akin to just muting users and/or text strings?

2026-05-07 16:59:06 UTC

We really need to build a P2P bitcoin exchange on top of Nostr. Things like Robosats, Bisq, and Vexl are nice, I've used many of them extensively, but they're also ripe with fraud abuse which can get your accounts in trouble when trading with the wrong person.
We're almost all bitcoiners here and there is a wide mix of people looking to either accumulate or sell bitcoin. We could use the web of trust with Nostr to find people within our trust circles looking for a partner who we could regularly exchange with. Similar to the idea of Vexl, but rather than needing to find exchange partners via our phone's contact list, we could use our Nostr follows (which are already public) to find trusted people looking to exchange with. From there, all exchange details can be done privately through encrypted communications.
Obviously you can't fully stop fraudsters, but being able to find exchange partners among the people in your community you trust would go along way toward facilitating P2P bitcoin trades which is really needed to help bitcoin fight KYC. I think Nostr is in a prime position to help facilitate this.

2026-05-07 15:39:04 UTC

Wait, so banks are slow in processing transactions, so to combat that they come up with EWA apps that are really just PayDay loans in disguise. This is creating the problem so that they can come up with an even worse solution. And they claim to be helping people while they're actively robbing them.
Imagine in the future just being streamed your income as bitcoin as you work via lightning. That way you have access to the money you earned immediately. Oh, and also no one can debase the currency you earned robbing your wages through inflation.
https://www.youtube.com/watch?v=hBI_FLYfwmM

2026-05-07 14:21:25 UTC

- reply

I want self-sovereign zaps to be as easy as possible for the end-user as well. But I think some perspective is always good too.
In order to perform a Zap in the alternative fiat world, it would require opening an account with an institution, providing loads of identifying data and documentation, waiting several days for account opening and funds to be transferred, and requiring all parties that will be transferring funds to be a part of the same closed-system and go through the same process each.
While it may require a little technical knowledge in the beginning, this is a battle that can be won because the incumbent system is so disastrously bad in comparison.