Dikaios1517

Completely agree! The user should be able to interact with the original post that was quoted from the main feed, without having to tap into it. Primal is not the only client that doesn't show the option to interact with quoted posts without manually opening the quoted post, though. Coracle, Nostrudel, Jumble, Nostur, and Damus ALL have the same behavior as Primal in this regard. Amethyst is actually the outlier. 😂

2025-06-04 20:44:39

- reply

Indeed. A debit card is really the same principle, but attaches to a checking account instead of a credit line. Therefore, it is subject to the same KYC regulations and much of the same charge-back risk.

2025-06-04 20:42:41

- reply

Indeed, you can. Kind 10000 mute lists support muting npubs, hashtags, threads, and words. Which of those types of items your client supports muting may vary. I had a rant about discrepancies in the way Nostr clients handle mute lists yesterday:
#nevent1q…5deh

2025-06-04 19:32:44

- reply

Yeah, not sure if the seller was using Shopstr for DMing me. May have been, or may have been using another client with NIP-17 DMs.
Either way, even after providing tools that allow media to be encrypted, users will still need to take advantage of it. I could 100% still see some users uploading directly to a public Blossom server and copy/pasting the URL into the DM, thinking they're all good because DMs are encrypted.
Not really anything that can be done about that.

2025-06-04 17:33:21

- reply

That makes a lot of sense. Quite unfortunate for those who would like to have a tool like Amber on iOS, but it kind of needs to be awake in the background waiting for signing requests in order to work locally.

2025-06-04 04:50:30

- reply

The ones I have I outlined here:
#nevent1q…q2m6
The first idea probably hinges on DMs working consistently for the notification when someone signs up that you invited, and DMs are quite a mess right now.
The second idea hinges upon more clients supporting PoW. The only one I know I can add PoW with right now is Coracle, but it's off by default.
I am also interested in hearing any ideas you might have about bringing the incentives of paid relays into alignment with participating in the guardianship of the network overall. You had mentioned that the way Bittorrent accomplished this was an example to follow, but I am not terribly familiar with the incentive structure there.

2025-06-04 03:32:19

- reply

Looks right up my alley! I'll hop in and take a look later this week or early next.
I have to go dark on Nostr for a couple days to prepare a couple messages I will be delivering this weekend, then I should have some time available to dig in.

2025-06-04 03:28:55

- reply

You've got a couple things going on here.
As @npub1qqq…eecw mentioned, your npub stays the same no matter what else you set up on your profile. You can change your display name, change your Nostr address, change your Lightning address, and change your bio information all you want and your npub will still be what it is now. It's like a unique fingerprint for finding your notes.
That said, it's not exactly something people can easily type in when trying to find you. They could try searching for your display name, but there might be a lot of Neals out there in the Nostrverse. They are just as likely to find another Neal as they are to find you that way.
To make it easier to find the correct npub without having to type it in, Nostr addresses were created. This is a way to register your npub with a particular domain. That way, someone doesn't have to know your npub. They can instead search for [name]@[domain.com], which is much easier to write down for someone, or to remember. When this search is performed, the Nostr app reaches out to that domain and effectively asks, "Hey, do you have a 'ModernChains' registered with you, and if so please give me their npub." There can only be one "ModernChains" registered with a given domain, so the Nostr app will only get one npub back as a response. The Nostr app will then check that Nostr profile and confirm that the Nostr address matches the domain it reached out to. If it does, it will be displayed in the search results to the user. This sort of address, defined in NIP-05, is what you got from nostrplebs.com.
The next thing is a lightning address. This is completely separate from a Nostr address and is used for receiving sats on the Lightning network, utilized on Nostr for zaps, which you are likely well aware of, given that you have been sending and receiving zaps.
Here's where things can become a bit confusing. Both of these addresses (Nostr and Lightning) can be the same. Nostrplebs allows you to use your Nostr address with them as a Lightning address by forwarding any Lightning related requests to a different Lightning address you give them. For instance, my nostrplebs address forwards to my coinos.io Lightning address at the moment. Primal, on the other hand, has their own Lightning wallet. So you can use your primal.net address both for receiving zaps to your Primal wallet AND as a Nostr address to make it easy for others to find you on Nostr. However, Primal does not allow you to forward zaps sent to your Primal address to a different Lightning wallet.
Now, you are probably still registered with nostrplebs.com, even though you have updated your profile to use your Primal address. However, you can only have one of them active on your profile at a time. If there was a monthly subscription required for nostrplebs, I might suggest you make sure you cancel it if you have decided to use your Primal address, but they're a one-time cost to register, so it doesn't make any difference.

2025-06-04 02:29:43

- reply

Not a one. I don't read from public relays.
You can add muted words, too. Just recognize it will only work for this particular spam attack and you'll have to figure out what words you should mute on the next go-round.
This time, adding "randomuser.me" will get the job done, since that's where all the spam bots' profile pictures are hosted.
Of course, you also have to be using a client that supports muting words.

2025-06-04 02:16:36

- reply

Yes. Inviting someone to Nostr should come with some way to be notified if they accepted the invite, so you can immediately follow them, bootstrapping them into your web-of-trust. I believe @nprofile…9wgx is working on something like that with https://nostrmeet.me/
Another thing clients could do is default to adding a certain amount of PoW to new users' notes, defining new users as those with no kind 10002 relay list, or no notes on their outbox relays with a timestamp older than X number of days. The exact number of days someone should be considered new is debatable and each client could use a different length of time. Then, clients could default to showing notes from npubs outside of the user's WoT that meet the minimum PoW. Coracle has the latter option, for instance, but no default PoW added to notes for new users.
The above could even be paired with a feature like Nostur has, where you have a few seconds to cancel a post before it is written to your relays. That way if you see a typo, you can cancel and fix it before it is permanently on display. During that few seconds, the client could be performing the required PoW.

2025-06-04 01:50:59

- reply

Yes. All entries added to a kind 10000 from Amethyst are encrypted, as far as I can tell. Whether npubs or muted words. Which means other clients that don't support private entries on the mute list won't have those npubs or words muted at all.

2025-06-04 01:48:12

- reply

No. Just "block," which is really "mute" by a different name.

2025-06-04 01:46:10

- reply

This is a good point. Muting spammers and scammers is probably fine to be public. Meanwhile, muting people who annoy you for other reasons might be better private. 😂

2025-06-04 01:43:47

- reply

Amethyst allows you to choose whether the mute is public or private? I am not seeing any option to select that.

2025-06-04 01:34:38

- reply

Hadn't thought about it that way, but you're absolutely right. So long as spam isn't an issue, there's no demand for paid relays. No one feels any pain from not having them. Therefore, the best way to drive demand for paid relays is to generate spam.
That said, I wouldn't accuse any particular paid relay operator of being behind the recent spam attack without some pretty damning evidence, and I don't think anyone has accused any particular relay operator. At least not that I have seen.
Chances are that the bulk of what most of us would consider spam is just being perpetrated by people who like to cause trouble simply because they can, or because they think they are making a point.
Spam on public relays is inevitable, no matter who may be behind it. You will find it on any sufficiently large network where the following are true: 1. It's free and easy to create new identities on the network. 2. New identities can write data others will see without a cost.
On Nostr, we're not able to make it difficult to create a new identity. Nor would we want to. That means our only option for mitigating spam is to impose some form of cost for new identities to write data to relays that others will see. Public relays impose no cost at all, so they are guaranteed to have spam.
The three typical means of imposing costs to writing data to a relay are social, computational, or monetary. WoT relays would be an example of social cost to gain write access. PoW relays would be computational cost, but we hardly see any of these in the wild since most clients don't support adding PoW to notes. And, of course, paid relays come in as the monetary cost option.
It's a tough nut to crack, though, when you are trying to encourage the network to grow. We WANT new users to come here, and we want them to have a pleasant experience so they will stay. Adding social, computational, or monetary costs in their way is antithetical to that goal. Yet, new users are also the ones most likely to be spam bots that will make the experience of new and existing users alike unbearable. Costs should therefore be imposed in such a way that they are virtually unnoticeable to legit new users, but are prohibitive to spammers.
I have a couple ideas how that might be achieved.

2025-06-04 00:36:47

- reply

I can't believe I didn't even check Jumble...
Jumble appears to add encrypted entries to your kind 10000, similar to Amethyst. Which is great for Jumble, but whoever you mute there won't be muted on any client that doesn't support it.

2025-06-04 00:25:23

Ok, it's time to gripe a little bit, as I discovered an annoying lack of interoperability between various #Nostr clients that really ought not to be the case:
Mute lists.
Beware, this is a bit of a long one...
When a user mutes an npub, or a word, they don't want it to only be muted in Amethyst, and not muted at all in Primal. They want it to be muted across all Nostr clients they use.
The standard mute list, according to NIP-51 is kind 10000. All users should have exactly one of these, and relays should only keep the most recent version.
Mute lists may contain a few different types of muted content:
1. Muted users/npubs, designated by a "p" tag.
2. Muted hashtags, designated by a "t" tag.
3. Muted words, designated by a "word" tag.
4. Muted threads (such as hellthreads), designated by a "e" tag.
Some clients also encrypt the entries added to the mute list. While not required, it is part of the spec that clients should expect to see within a kind 10000, and I think it should be preferred. A given npub should not be aware that another npub has muted them and unencrypted mute lists are readable by anyone, unless we move to only saving mute lists to relays that can require AUTH to read them.
Yet, I see a wide variety of handling of mute lists by clients.
#Amethyst uses kind 10000 as expected, and encrypts all content saved to the mute list (hooray!). It seems to support muting npubs and words, and has no support for muting hashtags or threads. @npub1gcx…nj5z, please chime in to correct me if I have misrepresented anything here.
#Coracle uses kind 10000 for muted npubs and also decrypts the muted npubs that were added by Amethyst, so they are also muted on Coracle. However, users muted on Coracle are not encrypted. I imagine this is because Coracle is trying to use mute information for the sake of building web-of-trust scores (mutes by those within your WoT count as -1 in the scoring), and any encrypted mute information cannot be used to calculate those scores. Also, though Coracle supports muted words, it does not seem to see the words I have muted from Amethyst in my kind 10000, and seems to be keeping a separate list, because words I have added in Coracle don't show up on my kind 10000, and are therefore not seen by other clients. @npub1jlr…ynqn, can you offer some clarity on how Coracle handles mutes, especially regarding muted words?
#Primal web seems to have an old kind 30000 list with only two npubs listed, while Primal Android didn't show any muted users at all, but adding a muted user added the npub to my kind 10000, which suggests Primal simply doesn't support decrypting the other entries that were added from Amethyst. Also, muting an npub on Primal resulted in all the encrypted entries on my mute list from Amethyst being nuked.
#Nostur did not display any of the above. Not my kind 10000, encrypted entries or not, or the kind 30000 Primal had been using at some time in the past. Adding a "blocked" user in Nostur also did not add them to my kind 10000 and did not add any other list type that I could find on listr.lol either. I am guessing it is using a list kind that isn't recognized or is just storing blocked npubs locally. @npub1n0s…lahe, can you provide some insight into how Nostur is handling mutes/blocks, and why it doesn't seem to be using kind 10000?
#Damus appears to be using kind 10000, but only shows entries that have not been encrypted. However, when adding a new blocked user, it does not appear that Damus wipes out the encrypted entries in the list. If not supporting encrypted entries within your client, this is the best way to handle them, rather than erasing them when replacing the kind 10000 as Primal did.
#Nostrudel behaves much the same as Damus, using the kind 10000 and only showing entries that have not been encrypted, but also not wiping encrypted entries when adding a new entry.
#Pokey also seems to have trouble respecting mute lists for the sake of muting notifications. This appears to be because Pokey only looks for your mute list on your inbox(read) relays, while users publish their mute list to their outbox(write) relays, and those may not necessarily be the same. However, I wonder if it is also an issue of Pokey indeed being able to find a user's mute list, but not taking encrypted entries into consideration. @npub1v3t…yvjh, can you confirm whether Pokey is able to mute notifications from npubs that have been encrypted in a users mute list?
Is it possible to get these and other major clients on the same page about how to handle mute lists?
Yesterday, @nprofile…8jsn posted this about what interoperability means on Nostr:
#nevent1q…d6zu
I pointed out that in order for this to be the case, we also need to agree on the format and expected content that will be contained in a specific note kind. From what I can tell, there is little agreement on how mute lists should be handled.
Should they include encrypted entries? If they do, should clients respect the encrypted entries, since the user who created that kind 10000 certainly doesn't want to see notes from the npubs they added to their mute list, encrypted or not? Clients certainly should not nuke encrypted content from the mute list if it is present, right? Or should we drop support for encrypted entries on mute lists altogether, since some clients are relying on mute lists from npubs within a user's WoT to determine what content is likely to be spam?
Users just want to know that when they mute an npub or a word in one client, that it will also be muted in other clients, and that muting in one client won't nuke their mute list in another client.

2025-06-03 22:17:16

- reply

It's one directional, as far as I can tell. You need to upload the media using https://blossom.band to get a blossom URL for sharing the media, and it will also show up in your nostr.build dashboard.
If you upload directly to your nostr.build dashboard, though, you can't get a blossom URL for sharing it. Only a standard nostr.build one.

2025-06-03 20:21:02

- reply

Also, muted words seem to be very client specific.
I have muted words on Amethyst, but they don't show as muted on Coracle. Instead, I guess I had added a different muted word there. Then Primal shows I have no muted words at all. Same with Damus.
Now I understand that there are plenty of folks out there who only ever use one client, so this isn't an issue for them. They can mute a word on their preferred client and it's all gravy until the next spam attack and they have to add a different word.
That's not the case for users like me, though, who use a wide variety of clients. Read relay selection is a solution that should work with most clients, and it should work against current and most future spam attacks without additional configuration needed.

2025-06-03 19:33:31

- reply

That's fair.
Again, muted words is a great feature, and definitely one to have in the tool-belt for dealing with this kind of nonsense.
I have also been very happy with how well reading from WoT relays and paid relays has worked on most clients. I also wish more clients would support adding PoW to notes so that relay operators could realistically add minimum PoW requirements for anyone outside the WoT to also be able to write to the relay without flinging wide the gates to spammers.

2025-06-03 19:18:37

- reply

Yeah... count me out. When I need to spend, I'll take the cap gains hit.
If you have a profitable job, then live within your means and save in Bitcoin.
If you are retired or between employment, this is what you saved for. Spend wisely and not frivolously.
If you are wanting to start a business and leverage your stack to do it, then maybe I can see this being an option for you, but I know there will be plenty of people who think they are making a sure bet, only to end up with Mallers owning their Bitcoin in the end.
I also can't understand the mindset of the person who is lending their fiat into such a scheme. Real inflation is upwards of 8%, and "risk free" rates can't come anywhere close to that on a 1 year horizon (remember that these loans are only 1 year terms), but these lenders are willing to put up capital at a return that maybe keeps pace with inflation, depending on what margin Strike is getting, when they could put the same money into Bitcoin, with a 5 year CAGR currently sitting at 60%.
The only explanation is that they think lending the fiat with fiat interest income will outperform Bitcoin over a 1 year time horizon, or else they would simply buy Bitcoin with that fiat they are lending.

2025-06-03 19:11:11

- reply

Until that anchor is something shared with legitimate users.
Say they all start using a free Blossom server to host their profile pics (like Nostr.Build), and MiniBits or npub.cash for their lightning addresses. Then using muted words will block a large chunk of legitimate users along with the bots.

2025-06-03 18:31:31

- reply

The hidden words feature is really a superpower that more clients need to implement. I remember that we used it as a band-aid during the old reply-guy spam back in late summer of last year, too.
However, it is just that: a band-aid. It stopped working when the bots no longer used the words we were blocking, and this one will fail, too, if they stop using that user generation service to host their profile pictures.
Reading from relays that are better at spam mitigation is a more robust and long-term solution. And I say that as someone who does not run a paid relay I am trying to shill.

2025-06-03 17:15:54

- reply

Exactly. When it comes to where they are more likely to find users who will make them money by using lightning every single day, it's a far higher concentration here.

2025-06-03 06:25:43

- reply

Alas, remember when @nprofile…w35w hung out here instead of Xitter?

2025-06-02 19:03:17

- reply

I think it would be the other way around in this case. Why not rename dollars to tips?

2025-06-02 17:52:24

- reply

I have an old one in my notes. Maybe it wasn't you who made it... "Nostr It" sound familiar?

2025-06-02 17:30:49

- reply

If you don't have Alby extension set up, you can go to the Settings page in Nostrudel, then the section for Lightning, and there will be a "Connect Wallet" option that will have NWC as one of the connection options.
https://relay.brightbolt.net/41f2b4f320e09b1646ea0d0da948270b4cc195120857f6d2c6b1bbefa6d88b2a.jpg
If you have Alby extension, Nostrudel will default to using that instead, and you can connect your wallet to your Alby extension via NWC.

2025-06-02 17:21:19

- reply

It has recently been added to @npub1z0l…8ldk Honey.
There was another one that I think @npub1l2v…ajft made before Shipyard, where you could schedule a post based on a block height, date and time, or other factors. Don't know if it is still up and running, though.

2025-06-02 17:13:42

- reply

You've got a couple options.
1. Use someone else's existing WoT relay, or a couple different ones. The upside to this is that you just need the relay address to add it to your relay list. The downside is, it's based on the relay owner's web-of-trust, instead of yours. So you may not see notes from people who would be within your WoT that don't happen to be in the relay owner's.
2. Set up your own WoT relay that pulls in notes from those in your WoT. For this I would use @npub1utx…50e8's WoT Relay implementation found here: https://github.com/bitvora/wot-relay and you'll need to have a domain and have a bit of know-how to point that domain to your relay end-point on whatever you are running it on.
3. Use Coracle as your Nostr client and set the WoT filter to a minimum of 1. No more spammers, regardless of which relays you are using.
For options 1 and 2 to work, your relay list must not have ANY public relays that you are READING from. You can write to public relays if you like, but if you are reading from any, you will see spam.

2025-06-01 07:30:04

- reply

Phoenix is pretty nice. Been using it on the side for a couple years now. They also recently added a new kind of lightning address powered by bolt-12 invoices, but they warn that it might not work with all wallets to be able to send to it.
The major reasons I can't recommend it as a daily driver for newbies at present are 1. No way to connect it to Nostr apps for one-tap-zapping, 2. No way to reliably receive zaps to their new lightning address spec, 3. Even though they lanage your lightning channel for you, you have to know a thing or two about how liquidity works to avoid surprise on-chain fees when you run out of inbound.

2025-06-01 07:07:26

- reply

Are you using one of the existing market/classifieds NIPs (NIP-15 & NIP-99) or doing something different entirely?

2025-06-01 06:50:53

- reply

This will give you a bit of context, I think:
#nevent1q…aulh

2025-06-01 06:39:33

- reply

Wha?
Was there some attempt by Amethyst to get apptoved on Apple's iOS app store that I'm not aware of, and they were rejected for not meeting their security requirements?
As far as I am aware of, Amethyst was only ever made for Android. No iOS version was ever developed.
The reason probably had nothing to do with Apple's security requirements and everything to do with the fact that it's an entirely different OS architecture that requires a complete rebuild of the app, and not worth it when Apple's draconian rules didn't allow zapping to be available by default.
Heck, we still don't have an Android version of Damus, and that has nothing to do with Google's "security requirements" either. It's just a completely different OS to try and build for.

2025-06-01 01:56:23

- reply

Yes, Primal's caching server aggregates my notes from the relays I have set up to write to. However, it does not allow me to read directly from the relays I want to read from. I can only read from Primal's caching server, which pulls in notes of other users from the relays they wrote to.
Therefore, any web-of-trust filtering on my read relays, or payment requirements for someone to post to them, are to no avail. Their note will be aggregated by Primal's caching server from whatever relay they post to, regardless of the ones I want to read from, and displayed to me.
Indeed, you can't even set which relays are read vs write in Primal, because they don't let you read from relays. They only let you write to them and read from the caching server which aggregates notes from all known relays.

2025-05-31 23:57:19

- reply

For something like that to work, you would need to be able to select a relay to read from that won't accept posts mentioning you without the user paying first.
You don't have that option with Primal, because you can't configure which relays Primal reads from. It only reads from their caching server.

2025-05-31 22:44:00

- reply

Yep. Again, it's a nice feature to have them encrypted, since you don't necessarily want to advertise what words you are muting to anyone who reads your mute list.
If you ask me, mute lists should be encrypted by default.

2025-05-31 22:22:22

- reply

People spending all their time and energy to earn something others created for free.

2025-05-31 22:19:23

- reply

I'd like to see a hybrid relay. WoT can post without PoW, and anyone else needs to either pay to post or include PoW.

2025-05-31 22:07:09

- reply

So, Amethyst appears to be putting this information into the user's standard mute list (kind 10000). However, it is also encrypting the words you are muting, so this will only carry over to other clients if 1. they support muting words, AND 2. they support decrypting your mute list.
I have noticed this being an issue when muting npubs, too. Amethyst encrypts the npubs you mute in that client. Very nice feature, since you don't necessarily want someone to know that you have muted them. However, not all clients support this, so the npub won't be muted on those clients unless you re-add them to the list without encryption.

2025-05-31 21:54:37

- reply

Indeed. Plastic is on the way out, and good riddance.

2025-05-31 21:24:02

- reply

So you're saying that if Lightning is going to work, the receiver needs to be the one who pays the fee, everyone has to be locked into KYC custodians so they can get cheap credit, and we need plastic cards filling our wallets, instead of just using an app on our phone?
Sorry. Hard pass.

2025-05-31 20:53:33

- reply

Lightning is a protocol, not a company. Lightning can't "offer" anything.
There is nothing stopping a custodial lightning wallet provider from offering 30 days of credit, but then I guarantee they would have KYC so they can collect if you don't pay it back.
There's also a reason credit card companies are able to offer 2% cash back. It's because they are charging each merchant who accepts your card 4%+ in transaction fees, and just passing a portion of that on to you. Lightning doesn't have anywhere near that kind of ridiculous fee rate, and what little fee is charged is paid by the sender, not the receiver, as it should be.

2025-05-31 20:48:22

- reply

Just someone spinning up reply bots, similar to replyguy from last year, but this time they parrot your note with the words scrambled.
Annoying, but harmless and easy to filter by using decent relays.

2025-05-31 20:34:51

- reply

How very odd... Why such a disparity of experience when everyone on Primal is reading from the same caching server? 🤔

2025-05-31 19:37:36

- reply

Yeah, problem is, you don't get to choose which relays you read from in Primal. That's why I don't usually use it, and rather use a client like Amethyst, Coracle, Nostur, or Damus, where I CAN choose the relays I read from.
I am just perplexed because I expected to see a torrent of reply spam when I decided to check out the situation on Primal, and I am seeing none. I know plenty of other users on Primal ARE seeing it, so I have no idea why I am not, since all Primal users effectively read from the same relay; namely Primal's caching server.

2025-05-31 19:25:58

- reply

Well, Damus is a client that lets you pick which relays you read from. Major benefit of using a full fledged Nostr client during spam attacks.
It's a mystery to me why I am not seeing spam on Primal, though, since it doesn't have that benefit.

2025-05-31 18:59:24

- reply

Have you tried out Nostur yet? I think it has one of the best looking UIs of all Nostr clients, while also giving the user a ton of features, including the ability to set which relays you read from.

2025-05-31 17:19:42

The AskNostr feed barely has any questions today ouside of, "What's with this reply bot spam?" and "How do I get rid of these reply bots?"
Read only from WoT relays and paid relays, my friends, and they'll all be gone.
Unless you use Primal, where you don't have a choice where to read from...

2025-05-31 04:52:39

- reply

So, this is definitely something Nostr devs have considered at length. For one such discussion, refer here: https://github.com/nostr-protocol/nips/issues/103
There's NIP-26 for key delegation, which was merged, but is unrecommended: https://github.com/nostr-protocol/nips/blob/master/26.md
And here's another proposal with a discussion: https://github.com/nostr-protocol/nips/issues/116
There are significant challenges to implementing key derivation and rotation, but if you think you can add to the discussion and even suggest a possible solution, by all means head on over to GitHub and chime in!

2025-05-31 01:48:37

- reply

Well, it's either that or you have to get some other general piece of hardware that requires even more know-how to get up and running, or you have to use one of the node-on-a-phone options, like Zeus or Phoenix, which have their own tradeoffs.

2025-05-30 23:52:03

- reply

What tardbots? I don't see any tardbots. 😉
WoT relays are your friend when Nostr has an influx of reply spam.
Alternatively, use whatever relays you like and use Coracle with your WoT filter set to a minimum of 1.
No more tardbots.

2025-05-30 21:19:02

Ok frens, for the sake of those of us who run Web-of-Trust(WoT) relays, can we establish this as a best practice?
Follows (kind 3) should be for npubs you believe to be real people whose posts you enjoy seeing in your feed.
Other follow lists (kind 30000) can be used for any other reason you like, including following bots.
Following bots in your kind 3 requires WoT relay operators to choose one of the following paths:
1. Unfollow you so you are no longer part of their WoT and the bots you follow will no longer be included on their relay. However, that also excludes all the other npubs you follow, too.
2. Manually blacklist the bots from the relay (available on some WoT implementations and not others).
3. Manually exclude you from the WoT while keeping you as a follower (available on some WoT implementations and not others). However, this has the same side-effect as option 1.
4. Live with the bots' posts showing up in the feed all the time.
Excuse me while I go investigate who is following all the bots...

2025-05-30 20:47:56

- reply

Yes, for newcomers (or others who have been around a while and always wondered but never spoke up) to find the answer to a common question, and for those who spend time helping answer questions to easily be able to copy/paste or provide a link to the answer each time it comes up again, instead of typing it out all over again.

2025-05-30 18:49:29

Seems we have a new spam attack going on. Similar to replyguy, but mixing up the words of the post they are replying to.
Any clients with web-of-trust or pagerank filtering shouldn't be affected much, if at all.
@npub132n…8cn4, I thought asknostr.site was using pagerank-based filtering. Maybe that's only for the original question itself, not for the replies? The bots are in full force on your client, unfortunately.

2025-05-30 18:26:55

- reply

More details, please.
Are you wanting notes that are stored on relays encrypted so only you can see them, like a relay-hosted version of Obsidian or Joplin?
Or are you wanting encrypted direct messaging, like Signal or SimpleX?
We have encrypted direct messaging in 0xChat and Keychat, and many flagship clients, too. It's a mess right now, because they aren't using the same DM spec, though. You'll receive some messages in one app, but not others. 0xChat seems to be the best about showing all of them.
We don't yet have the relay-hosted version of Obsidian or Joplin with encrypted notes only you can read.

2025-05-30 03:59:19

- reply

Yeah... Carrying in a proper holster is important.

2025-05-30 03:28:50

- reply

That's a fair point. Some folks are more on top of notes when they are mentioned than others, though. 😂
I generally lean the same way when it comes to my feed, though. I make heavy use of my web-of-trust relay.

2025-05-30 02:51:16

- reply

Interesting idea. Might be a bear to implement, though, and it would have to be implemented by the majority of clients in order to be useful. Otherwise, users might pay to have their note put into @npub1qny…95gx's feed, is a feature that a few clients support, but he doesn't use those clients, so he never sees it and they wasted their sats.
It does kind of remind me of what @npub1pmh…uksr and @npub1yz8…pxp7 are working on with @npub17vs…66ne, though. Haven't heard any developments on that front in a little while, though.

2025-05-30 02:24:15

- reply

You absolutely can. In fact, you can set @npub1h2q…w8ch to automatically send sats to any lightning address when your balance hits a threshold you decide.

2025-05-30 02:02:55

- reply

In any client that supports Blossom, put https://blossom.band/ as the media server. In any client that still only supports NIP-96, put https://nostr.build/
In the ones you mentioned, Nostur and Primal both support Blossom. Couldn't find any way to change what media server is used in Damus, but it uploads to nostr.buld, and probably using NIP-96.

2025-05-30 01:48:23

- reply

Everything you upload to blossom.band will show up in your nostr.build regardless of which client you use to do it. They are the same thing.

2025-05-30 01:45:26

- reply

I meant to tag @npub15yp…mpcx on that second one, but I guess I still had Coinos' npub in my clipboard...

2025-05-30 01:23:03

- reply

No, that's totally fair. He was locked up for over a decade. He never had the chance to learn what scams they all are by touching the stove like most of us have. I'm happy to not give him too hard a time about it.
Still would have preferred he wasn't promoting shitcoining in the last speech to end the so-called Bitcoin conference, though.

2025-05-30 00:16:06

- reply

The short answer? People do. As soon as one person proposes a change, 10 other people will have proposals that are variations on it.

2025-05-30 00:13:17

- reply

They had their database go belly-up and the most recent backup was 24 hours old, so they had to try to restore wallets that had transactions between the time of the backup and the time they got everything back online.
#nevent1q…33ml

2025-05-30 00:08:24

- reply

I think they handled the situation about as well as can be expected. They were transparent about their progress in restoring wallets as fast as they could with the data they had available to them. Sounded like it was a pretty manual process.
That said, they're a custodian. Keep as small a balance there as you can get away with.
If you have what it takes to switch to self-custody Lightning, then do so. If you don't, then consider taking a bit of time to learn.
As far as custodians go, I wouldn't consider them more or less trustworthy than any other. They're probably the most ideal custodian for using with Nostr due to their feature set and ease of setup, but that doesn't make them any less likely to rug you, intentionally or not.

2025-05-29 23:42:04

- reply

Fixed money and more productive work.

2025-05-29 23:27:30

- reply

Well, there's always incentive to vote yourself free money. Problem is that you can't get everyone else to also go along with you.
Say you propose a change to the code that gives every node 1 Bitcoin, irrespective of whether they mine. Well, you as a node runner might be incentivized to run that new code, but that doesn't matter much if you're the only one running it. You still need to 1. Make everyone else who runs a node is aware of it, and 2. Convince them that it is in their best interest to also run it.
Might think that's easy, right? Won't all those node runners also want to receive a free Bitcoin without doing any work? Sure, they likely would, if they don't know any better. However, there's plenty of node runners who are fully aware of what would happen if they did so, because even though they would have a free "Bitcoin," it wouldn't really be Bitcoin anymore. It undermines the whole reason why Bitcoin is valuable in the first place. They also know that it would just create a fork that people would sell, expecting that it will lose value over time.
Even those who like the idea will want to put their own spin on it. Some will wonder why stop at 1 Bitcoin per node and will want to receive 2 or 3 instead. Others will rightly note that it's too easy to spin up a bunch of nodes and get more Bitcoin for free, and they will want to limit it to one node per person by requiring KYC to ensure no one can get more than 1 free Bitcoin. Others will be adamantly against KYC, and they will want to regulate who gets the free Bitcoin by some other means that better preserves privacy, like requiring a certain amount of proof of work that can be done by an average PC's CPU, but which would be prohibitive to spin up a lot of them. Someone else will note that if each node is getting a full Bitcoin, it will be more than worth the money to buy as many PCs as you can, each able to generate the required proof of work for the free Bitcoin, so they will suggest limiting it to 1 Bitcoin per node and per IP address... So on and so forth, with each camp gaining supporters and eventually getting fed up with one another and spinning up their own idea that has a small minority support.
Meanwhile, the actual Bitcoin keeps chugging along. Tick tock, next block.
It's exceptionally difficult to get people to agree on anything that is a change to the way Bitcoin works. Even in the least controversial of circumstances, there are competing ideas about how to do things. As such, making no change at all always has the advantage over any proposed change. It is the default position of what will occur if not everyone agrees about exactly what the change should be, including every minute detail about how it will work.

2025-05-29 22:30:08

- reply

"If you get a loan against your Bitcoin, you don't have to sell it, and you avoid capital gains."
Yeah... Until I'm forced to sell it due to margin-call. No thanks.

2025-05-29 21:54:18

- reply

Can do. I'll pop over to the Discord.
Our of curiosity, though. Why use Discord instead of something built on Nostr?

2025-05-29 21:43:46

- reply

There is a massive difference between wanting the price to go down so you can buy more vs wanting the entire basis of the value to be undermined so you can get some.
Your node also isn't meaningful on the network if you don't own Bitcoin and use your node for transacting. Only nodes that are actually being used to conduct transactions and verify the validity of the Bitcoin received by those relying on that node matter. A node that is just sitting there keeping a copy of the chain, but not being used by anyone, effectively has no vote. Whether it wants to increase the supply doesn't matter.
Let's entertain the idea that a number of nodes and miners want to increase the supply of Bitcoin, so they start running an alternative version of the code that allows more coins to be mined and distributed to the miners and node runners. What happens then?
Well, you end up with a chain split. All the nodes that want to inflate the supply will accept a block mined with the increased reward, while all of the nodes that don't want the supply increased will reject it. So there will be two versions of Bitcoin at that point, and anyone who owns Bitcoin on the original version will own an equal amount on the new version (we'll call it Inflato-coin), where the supply is able to inflate beyond 21 million coins.
Anyone who knows how scarcity works to ensure a money retains its value will do what any sane person person would. They will sell the version they expect to go down in value, namely Inflato-coin, and buy more of the version they expect will retain its value. As you might expect, this will cause Inflato-coin to rapidly fall in price compared to Bitcoin, which will have a cascading effect of more and more holders selling it, driving the price down even more. There will, of course, be some idiots who think this is the buying opportunity of a lifetime, and that they will make crazy gainz when the market rebounds and Inflato-coin just gets back up to its previous ATH, but they will just be the exit liquidity for those who know better. They'll just end up as the bag-holders.
There is no way around this, because consensus is messy. You never have a situation where literally everyone agrees what should be done, and that is doubly the case when it comes to mucking around with the Bitcoin's supply cap. Yes, there might be a sizeable amount of node runners who want to "vote" themselves more coins by destroying the entire value-proposition of what they hold, but there will also be plenty of node runners who would never do so. That being the case, a chain split would be inevitable and it would become clear very quickly which version is able to retain its value, and people will choose to keep that version and sell the other.

2025-05-29 20:01:09

- reply

There is no incentive to undermine the very feature that gives Bitcoin its value. The only way it will reach million dollar heights is if the fixed supply remains reliably enforced, and the only way it will retain that value or higher will be if it retains its fixed supply.
Every increase in USD denominated price is a challenge to the market, daring it to prove that more supply can't be made available to meet the current demand. If the supply is no longer immutably fixed, then the price will likewise plummet. So there is no incentive for either mining pools or node runners (who are relying on Bitcoin maintaining its value) to inflate the supply.

2025-05-29 19:54:15

- reply

Not really. Most block formation and coinbase is not controlled by the miners at all, but by the mining pools.
At any rate. When a block is mined, it is broadcast out to the nodes on the network for them to validate in retain in their copy of the chain. If the mining pools included a transaction that is outside of the consensus rules the nodes are enforcing, then the nodes will reject that block. They simply will refuse to add it to their copy of the chain. One of the consensus rules they enforce is the amount of new Bitcoin included in the coinbase. If miners, via their mining pools, try to award themselves more than what the nodes are enforcing, the nodes simply won't accept that block.
So long as the nodes won't accept blocks with an inflated supply, then mining pools won't run code that tries to award miners more Bitcoin, because they don't get paid at all if the nodes reject their blocks. They only get paid for blocks the nodes are willing to accept as valid.

2025-05-29 19:36:49

- reply

Can't go wrong with this list of articles compiled by Anilsaidso, which @npub1h8n…rpev has read the vast majority of on Bitcoin Audible. I reposted Anil's list as a Nostr long-form, with all of the available audio linked, here:
#naddr1qq…uwmu
If your client can't display the above Nostr URI, here's a regular URL: https://dikaios1517.npub.pro/post/1733001418581/

2025-05-29 18:57:37

- reply

All value is subjective. The answer is, whatever someone is willing to pay.
And since when are reposts costly? There is no scarcity for reposts. They may be costly reputationally, if you are reposting content others wouldn't want to see. Outside of that, though, it costs nothing to repost except a couple seconds of your time.
Since Bitcoin is perfectly scarce, and reposts are not, it follows that the value of reposts would trend toward 0.

2025-05-29 18:47:21

- reply

Wow! That's quite the upgrade!
Could this replace Riverside for podcasters?
I like the calendar and note scheduling integration.
Lists would be used for having a set group of people you invite to a room, right? Would it be possible to support encrypted lists? Wouldn't necessarily want to dox who is being invited, especially for private rooms.

2025-05-29 17:37:39

- reply

Yeah, I have received that pair of errors before, as well.

2025-05-29 17:21:39

- reply

Should have added a sensitive content warning, huh? 🤣

2025-05-29 16:05:47

- reply

Good question. The only part of the notification that may not be easily understood is the "Hash Mismatch" portion. The rest is plain.
I don't think the problem is primarily a lack of understanding the meaning of the warning. I think the issue is that users are assuming the Zapstore is wrong in presenting the warning at all. That the file certainly isn't malicious, and there must be a bug in the Zapstore.
It's a sort of normalcy bias. Apps generally install fine. They've never experienced installing an app that was actually not what the dev released, but was a malicious app put in its place. So they assume it couldn't actually be what has occurred.
What's more, they're probably correct that it isn't a malicious app. It's probably just that the dev made a change after signing and didn't update the signature on the Zapstore. However, the correct course of action is not to assume that's the case and install the app anyway directly from GitHub... The correct thing to do is reach out to the dev and alert them to the fact that there is a hash mismatch, so the dev can diagnose why.
Perhaps the alert should suggest this course of action.

2025-05-29 03:27:07

- reply

Android needs Nostur.

2025-05-29 01:51:54

This did not disappoint. Great discussion @nprofile…mctc and @nprofile…ucf3!
#nevent1q…r7fa
https://fountain.fm/episode/rrhOoP3LoVLMCitU58uw

2025-05-28 21:29:55

- reply

"Bitcoiner"

2025-05-28 21:19:33

- reply

That I did not know, and that's a really good option, too! Thank you sir! 🫡

2025-05-28 19:26:57

- reply

You only need to provide that to use Primal's built-in wallet, which is provided by Strike.
If you have a Nostr Wallet Connect compatible wallet already, you can link it to Primal in their Android app or on Primal web. This feature is not available on Primal iOS, yet.

2025-05-28 18:41:15

- reply

You guys accepting Bitcoin via Zeus now?

2025-05-28 01:23:16

- reply

What client are you using that your feed is filled with people you aren't even following?

2025-05-28 01:19:03

Part 3 of the #AndroidElite setup, covering #Amber Signer is out now!
Part 4 covering #Amethyst will take a bit more time. There is much more to cover for a tutorial on a full #Nostr client, especially one that packs in as many features as Amethyst, and it will be the longest tutorial of the series, I am sure.
#naddr1qq…xwma

2025-05-27 21:54:44

- reply

Eh, I would still reserve that for merchants that are keeping at least a portion of the sale as sats.

2025-05-27 18:30:15

- reply

@nprofile…mctc has yet to drop an uninteresting episode.

2025-05-27 18:27:11

Being able to pay any merchant who uses square from my Lightning wallet is pretty cool, for sure.
Every merchant being able to auto-covert a portion of their sales to Bitcoin is even better. Though that will receive less fanfare, I'm sure.
#nevent1q…wlpx

2025-05-27 16:03:13

- reply

If you get a lot of spam replies, I recommend using a popular paid relay like nostr.wine. You don't have to pay to use it as a public inbox relay, since you'll only be reading from it, but only those who have paid will be able to write to it. Another option is a web-of-trust relay or two, and the reply spammers likely won't be on the relay's white-list. A more extreme option would be to run your own zapbox relay, which means you won't get replies from anyone except those who have zapped you above the threshold. It's sort of a dynamic paid relay that resets its whitelist on a recurring basis.
If you don't have a lot of reply spam, public relays work just fine, and broaden who is able to reach you when they reply.

2025-05-27 15:56:15

- reply

Nostur doesn't use the "outbox/inbox" terminology. Instead, you just configure which relays you are using to read from, write to, and search from. Then you "announce" which relays you want others to see that you are reading from and writing to. Announcing just creates a new kind 10002 (replacing your old one) that others can find, listing your read and write relays. Read = inbox, write = outbox.

2025-05-27 15:35:37

- reply

Nostur

2025-05-27 15:04:48

- reply

Part 2 is out now!
#naddr1qq…jr6u

2025-05-27 03:22:19

- reply

I believe PDF upload is only for paid accounts.
The concept is sound, though. As long as you have a place to host the PDF, upload it there and copy/paste the url into a Nostr note.

2025-05-26 20:20:09

- reply

So sue me for my proper punctuation. lol

2025-05-26 19:50:22

- reply

Bitcoin: A peer to peer electronic cash system.