JoeRuelle
Joe Ruelle

Anyone else working on Nostr for B2B please say hi.

Surname pronounced: roo-ELLE.

Public Key

npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnx

NIP-05 Address

joe@milliwatt.com

NIP-57 Address

zaps@primal.net

Profile Code

nprofile1qqstjrpukuwkvdp7qygy6hy6ma7mqhfkv5a3wcqllxewaw4gr0n8sgcpz4mhxue69uhkg6t5w3hjuur4vghhyetvv9usz9nhwvaz7te38yezuvfk8qhrzwpwxuarwdehxu2yvdx5

Publishing to

ditto.pub/relay

192.168.18.7:7777

relay.primal.net

Author Public Key

npub1hyxredcavc6ruqgsf4wf4hmakpwnvefmzaspl7dja6a2sxlx0q3sxwtqnx

Show more details

Last Notes

2025-04-03 20:34:32

I'm torn between this well-thought out list of Nostr breaking changes from @npub1acg…p35c and this well-argued article on not forking the ecosystem that made the rounds earlier.
https://newsletter.squishy.computer/p/dont-fork-the-ecosystem
#nevent1q…mtlr

2025-03-31 19:00:38

- reply

Yeah, flat times. I looked at nostr.band stats just now, and yesterday was a 3 month low. Actually close to the 2023 peak.
The B2B route I think is promising, with this B2B friendly architecture and this candy jar of open source. But attracting regular people to regular Nostr, I'm not quite sure what the best pitch is.

2025-03-30 16:05:17

- reply

One tricky part there is iOS doesn't do disambiguation like Android does.

2025-03-30 15:21:35

- reply

It was intended from day one.

2025-03-30 08:25:00

- reply

There is no Official Lexicon Committee. ATProtocol Lexicons are much more decentralised that Nostr NIPs and Kinds (at least in the current PR and merge context). Any ATProtocol dev team can just create a lexicon shrink-wrapped to that team's already well-formed application design. Any other team can use that lexicon. Groups are free to get together to discuss lexicon norms before embarking on similar projects. Lexicons can't be deleted. Lexicons are backwards and forwards compatible. Any one lexicon can reference any definition in any other lexicon in an open manner.
It makes sense that it's a better thought out system. The team that designed lexicons had years of painful experience trying to clean up interop messes with SSB (very much resembling the interop messes we have on Nostr now) and this is their fresh "take two". Nostr is repeating many of the mistakes of SSB and now what we're seeing is lots of suggested ways to fix these mistakes, most of which are evolutionary steps towards the ATProtocol lexicon system anyway—so why not just skip up the evolutionary ladder and import the whole finished system? At least that's my take.

2025-03-30 06:01:29

- reply

Lol, that kind of sums it up. That would never happen on ATProtocol, there would be an immediate schema validation fail.

2025-03-29 21:32:31

- reply

I'm guessing atomic follow events across whatever relay set would still be pretty robust, even if slight variations each reconstruction. But just imagine a bot (or even a human) following 100k nostr:npubs and clients having to piece that list together each time.

2025-03-29 20:37:11

- reply

十人十色

2025-03-29 18:29:43

- reply

Eating green eggs and ham in a house.
Eating green eggs and ham with a mouse.
Still green eggs and ham, as far as I can tell.

2025-03-28 18:24:26

- reply

You like sports? Great? Here are some Bitcoiners who play sports! Or travel? Got you covered there too, here are some Bitcoiners who travel!

2025-03-28 09:42:02

- reply

More here
https://www.pfrazee.com/blog/lexicon-guidance

2025-03-28 08:26:43

- reply

Yes, just hoping to create a bunker URL and then use it without having to consent to anything in realtime. Like if there was a make passive setting like this when creating bunker URLs:
https://image.nostr.build/18f1d7e89619993bf9afd93e84e199ef379e798d1aa3387439c80174452c2c9a.png

2025-03-27 17:26:32

Potentially unpopular opinion: Nostr should adopt ATProtocol-style lexicons.
ATProtocol lexicons are good because they encourage more detailed Kind schemas.
Let's take the example of NIP-29 chat groups and how the same group can look very different when viewed in 0xchat versus when viewed in Chachi. Want one thing to look right? Open the group in 0xchat. Want another thing to look right? Open the group in Chachi.
In ATProtocol it would be like this. Chachi comes into existence. When it does, 0xchat already has a hyper-detailed lexicon schema (com.0xchat.message) and this lexicon leaves little grey area—maybe some cosmetic grey area and that's about it.
On day one Chachi has to make a choice. Follow this hyper-detailed existing 0xchat lexicon or create a new Chachi lexicon. If going the first route, Chachi declares the 0xchat lexicon in each event that Chachi sends ("$type": "com.0xchat.message”) and by doing so Chachi is saying “I agree with everything in this very detailed schema of theirs and if something isn’t right then I’m the one that’s out of line, it’s me.”
If going the second route, Chachi will not be interoperable with 0xchat.
That's just the choice Chachi has to make. Is it worth it to forge a new path? Or is it better to piggy-back off 0xchat's success? Maybe there are other clients also using 0xchat's lexicon; does Chachi want to be on that bigger team? Or maybe Chachi has a super feature idea and it’s totally fine to go it alone, the users will come for that feature. Either way, Chachi has to make a choice, and it has to make that choice on day one.
You could say that the Nostr way is pretty much the same as the flow I just described above, with only minor semantic differences. Chachi has to choose to follow a NIP (and a Kind) on day one, or to go it alone. Like Flotilla went it alone at the start. But no. It’s not the same in substance. Of course Chachi does have to choose a NIP and a Kind on day one—but Nostr Kinds are like laws in countries where the authorities have left themselves a *lot* of room for interpretation. Singapore this is not. Rather this is more like [insert name of murky country here]. Did you break the law? Maybe you did, maybe you didn’t, depends on who’s asking who and why.
The current Nostr way allows devs to procrastinate, put off the “tidying up” until some undetermined point in the future. And the one who pays for that procrastination is always the user.
In short ATProtocol lexicons both allow for and encourage a significantly higher level of detail and expressiveness—and in doing so they tend to force tidiness from the start. If you take Nostr’s Kind1 schema and compare it to app.bsky.feed.post (their Kind1), and not only that but all the lexicons that app.bsky.feed.post references (such as app.bsky.richtext.facet and app.bsky.embed.images and app.bsky.embed.record ...) it's quite clear we’re looking at an order of magnitude difference in detail. And at the end of the day this is all about detail. That’s where the devil is. And the devil is having a lot of fun on Nostr these days.
If you're an ATProtocol developer and you've got a cool idea for, say, a VR client, and you decide you're going to re-use the app.bsky.feed.post lexicon and all its mandatory entourage—well there's very little wiggle room for you. Either you state outright that this is your lexicon in each event and you stick with the program—or you don't and you make a new lexicon and you declare that new lexicon explicitly in each event. And that’s good. Because over there devs can't just say to users "you know what guys, you figure it out". The devs have to figure it out themselves. And beforehand.
So why the lower level of detail for Nostr?
One reason Nostr Kinds are less opinionated is to increase the chance of being merged on Github. Meaning much of this is psychological (as opposed to technical, given that in theory there is no limit to how detailed a Nostr Kind can be, though there are also technical differences that give ATProtocol lexicons more expressive power). Nostr kinds are discussed—and discussed, and discussed some more. This has a watering down effect.
ATProtocol lexicons are discussed too, but in fewer situations, and the discussions end sooner. Part of this is because there is no two-tier system of “merged” and “un-merged”. (On Nostr an un-merged spec is a little like a second-class citizen, and devs feel a lot of pressure to get their specs merged and first-class-ified). ATProtocol lexicons also start off with devs and their unique ideas—but they aren’t ever merged. You can have a much-copied lexicon, one that say five or six other clients make use of. And you can have a solo lexicon, one used by your client alone. That’s where the difference is. This means that on ATProtocol it’s all about traction. Not traction in order to make the case that your PR should be merged. Just good old traction.
Of course the downside to lexicons is that devs with clients that have good traction gain a lot of lexicon power. If I make an ATProtocol client for publishing serialised fiction called CheeseRead, and my chapter publishing lexicon is com.cheeseread.chapter, and I get a lot of users, and a few other serialised fiction clients emerge (maybe for other operating systems), and they use my com.cheeseread.chapter lexicon too—then I’m in a pretty strong position. And bonus: I get to feel proud of myself because all these other clients have my brand showing up in their event json.
This doesn’t mean I can screw with the lexicon and break things on their end. Under the rules all old data must still be valid under an updated lexicon, and new data must be valid under the old lexicon, so new fields must be optional, non-optional fields cannot be removed, etc. (or a fresh lexicon is needed). But it does mean that it’s harder for other clients to pull users from me because my client is going to be very optimised for this lexicon. (Mind you this can also be a good thing because it means others in the space have to think beyond copy-paste.)
All in all though, there’s something to be learned here. ATProtocol lexicons are more decentralised—due to there being no “PR & merge” concept—and more practical—due to how much grey area they usually remove.
The lesson for Nostr: there is no point in getting everyone on the same page if that page doesn’t have enough words on it.
The ATProtocol lexicon concept is a smart concept that can be borrowed. It encourages what I call “fearless detail”. At any rate Nostr has to move off Github sooner or later, so why not dump both the platform and the flow at the same time? And jump on the lexicon train.

2025-03-27 13:15:53

- reply

Do it again on Nostr. Tel Nostr you'll start writing the next chapter when you get a certain number of zaps on the chapter before. Feedback in zap messages welcome. I'll zap you along!

2025-03-27 12:27:57

- reply

That is true, I think most of Dickens' novels were in that bracket.

2025-03-27 10:33:20

- reply

Look into this, some good logic that can be borrowed.
https://atproto.com/guides/lexicon
https://github.com/lexicon-community/awesome-lexicons

2025-03-27 10:28:15

- reply

And also position. Images inserted and rendering in-line in Primal are rendered all at the end of the post in other clients. You think you've made a nice step by step help post on Primal, only to open it somewhere else and see it makes no sense.

2025-03-27 10:24:46

- reply

Much more thought went into ATProto lexicons, have to say.

2025-03-26 12:21:33

- reply

I also don't think Big Nostr is bad.
For me the issue is if going hard in that direction then ATProtocol can become Nostr a lot faster than Nostr can become ATProtocol. Like when that Netflix exec said the goal of Netflix “is to become HBO faster than HBO can become us”.
AP is scaling down fast, and soon a lot of the lite stuff (AppView lite, Relay lite, etc.) is going to be boxed up. And it'll only get lighter. Other words I suspect AP can eventually get pretty close to the lightness of Nostr in certain key areas, but Nostr won't get near the consistency of AP.

2025-03-26 08:22:37

- reply

Still not sure how I can make a Kind1 post to this demo communi-key that's up now?

2025-03-25 18:53:27

- reply

Right-o! But I'm still a bit confused, don't I have to do at least *something* to sent my post to the communi-key? I get that clients don't have the UX yet, but I still have to hack together *something* right?

2025-03-25 18:50:30

- reply

dang man, dem chromosomes is mutating fast.

2025-03-25 18:49:18

- reply

How does evaluating any aspect of social media outside of the context of overall usage make sense?

2025-03-25 18:25:02

- reply

ATproto have already unlocked this power up.

2025-03-25 11:36:15

- reply

You mean follow this NIP-C0 and and use your npub as the community-pubkey?

2025-03-25 08:55:16

- reply

Yeah of course
https://www.bankinfosecurity.com/criminals-remotely-ghost-tap-nfc-for-card-cash-out-attacks-a-26860

2025-03-25 08:39:23

- reply

Also the name Nostr isn't the best. If it were called the Ostrich Protocol instead of the Nostr Protocol, that'd be better.

2025-03-24 12:32:13

- reply

I like the idea of NIP-05 resolving handshake.org domains because then you don't have to change anything about the UX or the flow, clients when noticing a handshake domain just have to add the "hns.to" before the URL and they'll find the json, so for example me.nostr/.well-known/nostr.json just make it hns.to.me.nostr/.well-known/nostr.json and done.
This is idea usually loudly booed because another chain. But it's a pretty frictionless update.

2025-03-24 12:23:36

- reply

Yeah, ditto is interesting, I think Alex is going in a pretty similar direction. The NIP-05 as I understand it is a sort of a placeholder to speed up the fediverse port (this all started on Mastodon) but how it's been evolving behind the scenes now I'm not sure, maybe some synergies.

2025-03-24 12:11:22

- reply

Yup. As for the 'temptation of consistency', I think the direction it's going is multiple parties will simply crawl and index (or try to) all of Nostr to fill in the gaps. Primal does it, Ditto does it, Nostr.band does it, npub.world does it... who else? I can't see that train stopping.

2025-03-24 11:50:06

- reply

In the case of Ditto, whether your posts can go a community (like this Gleasonator demo community) is determined by your NIP-05. That's your authority to post.
If there was such a thing as a NIP 5.1 (a NIP 5.0 for communities) and you could have multiple of those, it seems at first glance that the end result of such a thing would be pretty similar to the end result for communi-keys. As in you could publish to multiple communities at once, one community could span relays, there'd be moderation, etc.
https://image.nostr.build/059b3dd70710aed837dec6c7402cf22ed271dd5b5d109209909774f4772f07b0.png

2025-03-24 11:32:12

- reply

Yup. And Nostr has the same issue (date of an event can be in the past) but showing such a warning on Nostr is much harder.
-A relay might not record the time it received an event
-A relay might record the time it received an event but this information isn't exposed to clients
-A relay might record the time it received an event and this information is exposed to a given client but that client might not care
-A relay might record the time it received an event and this information is exposed to a given client and that client might care but it is unable to determine whether something suspicious is going on (are the event date and receipt date out of alignment for THAT relay only, perhaps because the event was rebroadcast, or is something else at play, need more data...)

2025-03-23 12:22:48

- reply

To get a sense of "17+04" UX options:
- Open 0xchat and start a chat with someone. This will be a NIP17 chat.
- Go to Primal and send a message there. That message (NIP 04) will appear in the same 0xchat chat with a warning bubble which if tapped states "This message is not a gift-wrapped message"
Of course 0xchat needs to implement both specs, but that's at least how the UX can achieve a sense of backwards compatibility without it actually being backwards compatible.

2025-03-22 13:56:31

- reply

hope so!

2025-03-22 13:24:05

- reply

I feel sympathy for your fired coach. I’m sure that’s not an easy way to earn a living even without LLMs.

2025-03-22 09:48:59

- reply

> NOSTR client may not understand what's happening fully,
Still in different pages I think. As far as I've dug, LN invoices can denominated in all the various currencies(assets) supported by taproot, but of course one at a time. So in the case of Nostr zaps these are LN invoices denominated in Sats. The users therefore couldn't pay these invoices with LN-USDT (despite it being taproot) To give the user a choice of LN invoice denominated in Sats or USDT invoice would require a new type of zap request event with an extra qualifier for currency and such. So the NIP itself would have to be updates, and all clients would then also have to update accordingly. In addition to the cosmetic stuff.
This is after a very cursory glance mind you, anything you think could change or invalidate that?

2025-03-21 15:40:37

- reply

ah was just testing 😀 🫡
will there be a chachi nip29 relay up soon?

2025-03-21 15:27:51

- reply

is the chachi group relay down?

2025-03-20 18:22:18

- reply

You've got a business background, penny for your thoughts on Cashu mints and licensing. Think licensing requirements are inevitably going to hit mint operators with mints doing a certain volume (likely those affiliated with viral apps)? A class of licensed/regulated mints emerges—good thing, bad thing?

2025-03-18 15:35:51

- reply

Nice thanks!

2025-03-18 09:26:21

- reply

Serverless computing. Brought to you by servers :)

2025-03-18 07:28:27

- reply

Ah, that's all the issue is, just a lack of an event? I was confused there, but now it makes sense.

2025-03-16 20:26:04

- reply

What less ambiguous measure would you prefer? Total zap amount by week?

2025-03-16 16:54:53

- reply

I agree on this, because below:
nevent1qvzqqqqqqypzpwgv8jm36e358cq3qn2unt0hmvzaxejnk9mqrlum9m464qd7v7prqqsdycqmjxfy65xqgc8jk8988qj6h37pv0n4mwszfh9d2s6x3ud2nfg9hda7y

2025-03-16 16:40:52

- reply

Ah hah. Earlier I tried 0xchat when logged in via nsec.app bunker, no go for redeem, but revert to nsec and all good—so what you said tracks. Wonder if a collaborative ECDH via Frost would do it?
nevent1qvzqqqqqqypzqs3fcg0szqdtcway2ge7zahfwhafuecmkx9xwg4a7aexhgj5ghleqqsdfqyp8nwk9mypej2xvys3uhf05w98dujj6fjnz4nflm969czc0nsh49klp

2025-03-16 15:51:47

- reply

Nsec bunkers on the roadmap?

2025-03-16 15:49:19

- reply

This is great. This one feature adds so much value to nostr keypairs.

2025-03-16 05:38:41

- reply

"Pre-paid zaps" is what primal labels their in-app purchase item.

2025-03-15 16:58:21

- reply

That's true. Though I'd argue that the corporate world has by and large already adapted by outsourcing custody, and that chapter is closed. Just not sure that approach works for Nostr. Very different departments.

2025-03-14 14:32:04

- reply

Keys for communities seems like a good idea. How to handover the keys though? As I understand with flotilla the new admin just hands over control of the server where the relay is hosted. So the community team can rely on the intricate IAM settings of whatever cloud provider and choose from the zillions of potential ways they want the joint holding, handover, and post handover situations to look like. Layers upon layers, decades upon decades.
I guess you could use bunkers and frost shards and whatnot to try to cobble together some kind of IAM for community keys, but the difference there is that you'd never have a situation where the old lord of the rings is shut out. With cloud IAM, anyone who was on the inside, no matter what role they had at the time, once on the outside can be shut out for good. Which can be useful, given human nature and that whole revenge urge thing.
Or maybe all admins from the start can be working off of bunkers and the actual nsec is held cold in escrow by some trusted third party but then... I dunno. Everything else but that aspect seems to make sense.

2025-03-14 11:41:16

- reply

#naddr1qv…thfl

2025-03-14 10:36:55

- reply

I'll do a quick thread and paste here stay tuned.

2025-03-14 08:22:46

- reply

I was wondering if it might be Wendy's, cause then you could use "From Frosty to Frostr" for the name of your Ted Talk.

2025-03-13 15:07:52

- reply

No fear, Alby.
https://m.primal.net/PeYK.png

2025-03-13 14:09:08

- reply

nodana.io

2025-03-13 13:30:40

I like it when Japanese Nostr tops the zap list.
https://m.primal.net/PeSk.png
Also if you want a who's who of Japanese Nostr look through all the people that this guy zaps. In a way the best examples of unique communities on Nostr right now are the language-specific communities.
https://primal.net/p/nprofile1qqs294npyyuy4zphnv83vyyx4j2x2recnneyf3j06rfqjtpvnzahvyc637vcv#zaps

2025-03-12 19:16:26

- reply

You mean in the context of encryption decoupled from signing?

2025-03-11 10:12:44

- reply

Yes indeed. Either you think you can somehow "scold" the project open-source, which is silly, or you're aware it's a dog barking at squirrels scenario, which is also silly.

2025-03-08 12:21:27

- reply

Cool. Can you also lock it to a nostr pubkey using cashu.me?

2025-03-06 06:55:56

- reply

What about this for only zaps mode? Don't remove the like button, repurpose the like button as an instant zap button (same icon). And then make the regular zap button always show the choose amount slider. So it actually becomes a custom zap button. (Icon demo below.) The whole long press or short press thing on the zap button has always bothered me, this would fix it.
https://image.nostr.build/28479dd1caea27f676367af723ad36523b86a0d95b1186ced4c8303f4ca86531.png

2025-03-01 18:21:34

- reply

I think a few parts for that spaceship can be pulled from ATproto lexicons and sub-schemas
https://docs.bsky.app/docs/advanced-guides/custom-schemas#sub-schemas

2025-02-28 18:38:40

- reply

Yeah lots to unpack. It would be nice if integrations like could handle their own payment, maybe drawing from the users NIP-60 wallet with an approval popup. That way clients wouldn't have to collect and then pay the integration provider later as if they were collecting VAT.

2025-02-28 16:36:31

- reply

Good going. I can think of a few clients if they integrated this I'd be happy to pay a few sats per search, because those clients do most other things well. Not sure how payment might work. If you've tried Keychat, the way they have an integrated cashu wallet that just pays 1 sat to the relay for each message you send is quite nice—wonder how to achieve a UX like that in an integrated search DEV context.

2025-02-28 16:23:01

- reply

Very nice! Are you guys crawling all of nostr yourselves or is there an index/firehose for rent somewhere for this type of thing?

2025-02-28 07:48:28

- reply

Some recent discussion on those tradeoffs here
https://github.com/nostr-protocol/nips/issues/1810

2025-02-26 13:04:06

- reply

Ins't this more or less means to the same end?
nevent1qvzqqqqqqypzq77777lz9hvwt86xqrsyf2jn588ewk5aclf8mavr80rhmduy5kq9qqsqqqqv6w6jgsef6cfw8k8djv9yw36pdthjf0qa890vvzysgk964zqqsregp

2025-02-26 08:24:33

@npub1syj…f6wl does "Seen on" here mean (a) of the relays that we know of for you, these are the relays the post was seen on, or (b) of the relays we know of in all of the nostr universe, these are the relays the post was seen on?
https://image.nostr.build/019027ade94e6cc76c540c23a87bfdc2a01117884585d0ab350f9f63066dc063.png

2025-02-25 08:04:53

- reply

Nice, looks fantastic. Feels like the final piece of the nostr key puzzle 🧩

2025-02-25 07:58:05

- reply

1. An argument against bitcoin as a viable currency
2. An argument against the assertion that bitcoin "changes everything"
Need to be clear which you're after.

2025-02-25 06:11:40

- reply

@nprofile…04pe is there a plan for njump.me to host a FROST-management portal of some sort where users who created a nsec+FROST with the current join nostr flow can revoke the bunker and create a new one? Or does that already exist somewhere, like on promenade?

2025-02-24 10:49:55

- reply

Every client lets users choose *some* relays themselves. So it will quickly devolve into:
-You aren't letting users choose their own relays
-Yes we are
-No you aren't
-Yes we are
https://m.primal.net/PJPO.png

2025-02-24 05:02:00

- reply

I suppose but then I'd expect passionate bitcoin folks to prefer a social networking protocol that is far more decentralised than Nostr.

2025-02-23 11:48:24

- reply

All about community demarcation. Right now there's only really one community to on Nostr pick from. It didn't suit him. That's fair enough. If I joined a new network and the only community to pick from was kitchen-renovation maxis, I'd also be out.
If there were three or four clearly demarcated communities on Nostr then he'd have had a better chance of picking a community he liked.

2025-02-23 06:39:28

- reply

Would piggybacking off an existing client app like Damus as Will is suggesting here help with that snag? It's one I'd love to see un-snagged.
nevent1qvzqqqqqqypzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qqszyhgpt5vr23a2mvjh7pxspt04vlycj5gz8z2wj67fgfukncn3akswdkj4s

2025-02-18 16:14:51

- reply

I think that's a fair argument, but on the basis of ethics or principles.
Not on the basis of team size or tech stack, as many of these teams don't have anything to point fingers at there.
On the tech stack side it could be their design is simply optimised for native APIs. PWAs can’t fully plug into the accelerometer, gyroscope, ambient light sensor, bluetooth, USB on and on. Geolocation on a PWA can be of by many meters more than on a native app. And so on. There are a lot of things you can only do on a native app—or you can do a very watered down version on a PWA that people at best don't find nice—and at worse hate.
These are make or break things when it comes to the business side.
Or it could be down not to native APIs but rather deep-link integration with other native apps, or just certain market dynamics when it comes to attracting foot traffic and so on.
Basically there are many reasons to have empathy for teams that would love to go all in on PWAs but don't.

2025-02-18 13:23:39

- reply

I'm all for PWAs, building one myself.
But as a business you can't be both profit motivated opt for a PWA when it could be a native app w in-app purchase. Even if all your users are coming to you organically, profit wise you will sacrifice far more than the 30% you save. And for users that are not coming organically, it's orders of magnitude.
So "profit-focussed and PWA-first" is somewhat of an oxymoron on iOS.

2025-02-16 07:35:43

- reply

Are there any down-to-earth practical reasons to use Bitcoin over there? Like a 10% discount, no tourist tax, certain places don't accept anything else? Or do the reasons pretty much all fall into the abstract domain (you're contributing to a worldwide effort to...)

2025-02-15 18:24:04

- reply

That's a good point.

2025-02-15 18:20:00

- reply

I suppose. Though what about for someone without enough of a programming background to engage in bot wars? Normal users with no programming background at all and no savvy friends I suppose would be complete victims—all attempts to alert others would be thwarted or hijacked by the hacker. (They could only communicate the issue off Nostr, but who would know of their off Nostr presence?)

2025-02-15 17:45:17

- reply

Yeah but the hacker can run a bot too.
- A bot that instantly sends a delete request for every message posted by the spam bot
- A bot that follows up every spam bot message with forged clarifications (follow me on my new npub at...)
-A competing spam bot that responds to your spam bot's response and says "This is the real account to follow me on, check to see it matches my NIP-05" (But that hacker has already swapped out the NIP-05 in the hacked account to match the fake new one the hacker created).

2025-02-15 17:15:11

- reply

Thanks. But how do you nuke your nsec with a spam bot exactly? Assuming the hacker has their own spam bot and is willing for it to engage in some kind of Benny Hill spam bot war with your spam bot.

2025-02-15 16:41:43

- reply

Did I tell you I love penguins?

2025-02-15 16:32:06

- reply

Nostr hasn't had a "famous fail" yet. But it will. Picture someone well-known on Nostr, maybe an existing Nostr personality, maybe a famous person who has wandered over and built a good following. A client has weak security. This well-known personality pastes in their Nsec, a hacker lurking in the client by some means grabs it.
The hacker then starts posting troll content from the personality's account. Both the personality and the hacker have access, neither can lock the other out, so it's likely going to be pretty Benny Hill for a little while at least. The personality now has to start from scratch in full public view, and might be be hard to watch. Certain niche tech media will have fun covering it.
Like I said this kind of thing will happen and when it does Nostr as a whole will need to use the event to point out that nsec hygiene is critical. That'll be helped if nsec copy-paste login has been widely deprecated. At any rate everyone will be suddenly pretty freaked out about their own accounts.
Also remember that is someone has your nsec you could never know about it, for years even. They're popping in now and again to have a look at your NIP-60 wallet, waiting for the balance to grow.

2025-02-15 12:53:37

- reply

This! This stuff is what needs to be trending, very happy to see this in the number one spot.

2025-02-14 18:51:15

- reply

They are technically the top trending notes across the whole network. Can't really blame a top trending feed for showing the top trending notes.

2025-02-14 10:49:27

- reply

Thanks very clearly put. I suppose some startup somewhere is creating a physical vending machine where you can put real cash in and cashu tokens come out, along these lines.
https://m.primal.net/OfZp.png

2025-02-14 10:25:41

- reply

On that note, in future would purchasing cashu tokens with a credit card via wherever be any easier than purchasing standard in-LN-wallet sats with a credit card via say Strike or Moonpay? Or nothing really changes there, it's still the same on-ramp for cardholders? Thanks!

2025-02-13 14:07:00

- reply

Ah hah, you've definitely found a good itch to scratch there.
I can see what you're doing as being useful for a whole bunch of things once the parties involved are all satted-up, super interesting. Commissioning creators comes to mind.
As for getting satted up in the first place, I'm with you on the risk element.
Part of me thinks Primal’s solution, by means of which new users are essentially buying pre-paid zaps via Apple or Google, is the only on-ramp that won’t have an egregious drop-off rate. Like I was the head of Nostr marketing and growing the zap economy was my main KPI then I'd channel all new users to Primal. What they've got there seems to be fully-compliant, fast and clean. Single point of entry to the zap economy isn't so robust though.

2025-02-13 13:36:08

- reply

I'm not sure. Be it nutzaps or old-school zaps, at some point dollars, euros and friends need to cross the border into lightning land.
Would be great if Nostr had it's own peer to peer exchange, small amounts only, but I don't think that's feasible either due to payment concerns.
Bit of a head-scratcher. Feels like an arcade where the games are a lot of fun but only the staff have coins.

2025-02-13 04:10:39

- reply

Happy to, added you to one of these chachi groups, test those out

2025-02-12 18:19:02

- reply

Yup. But also fun to imagine if nostr was text-only from the start, and the whole nostr culture developed around this. Feels like the internet is at a time where text-only plus decentralisation could combine to make an actually pretty good marketing pitch.

2025-02-11 15:35:11

- reply

This just announced.
https://blog.mozilla.org/en/mozilla/ai/roost-launch-ai-safety-tools-nonprofit/

2025-02-11 14:10:48

- reply

"or it will look weird when others can see your reply but can’t fetch the root"
Could that not be a marketing opportunity for the root and zapbox? Provided a standardised placeholder makes clear that a root indeed exists and what one has to do to be able to see this root (zap this much to this person...).

2025-02-11 04:04:01

- reply

Spin one up Stu! I'll join.

2025-02-10 17:36:37

- reply

Learning a lot in this thread. You sound like you know this stuff inside out, does cashu help with this UX problem in any meaningful way?

2025-02-10 14:00:58

- reply

Playing Royal Match or Candy Crush is kind of like this. There's always a next level, and you can learn to play smarter, and faster, but all that does is bring you to the next level a little sooner. What playing those games taught me is that the key is to *enjoy* the problem solving more, not necessarily to get better at it.

2025-02-08 13:25:25

- reply

When you buy the purchase card lists "prepaid zaps" :)

2025-02-08 13:15:41

- reply

🤫

2025-02-07 14:44:24

- reply

Good stuff! Besides all this what I like about Primal is you can feel genuine care for new-to-Nostr users throughout.

2025-02-07 14:16:34

- reply

The way the relays are woven in is really nice.