fiatjaf

https://stuff.fiatjaf.com/

Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

NIP-05 Address

Profile Code

nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gpr9mhxue69uhhyetvv9ujudp5vf5kcmrfdahzumn9wsq3jamnwvaz7tms09exzmtfvshxv6tpw34xze3wvdhk6yu38uj

Publishing to

Author Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

Show more details

Last Notes

2026-05-17 00:04:54 CEST

Another example of a thing that could have been a Nostr closed community that forced its members to use Nostr against their will: https://handmade.network/
#nevent1q…dyu7
Do you know of other examples?

2026-05-16 18:03:21 CEST

- reply

Nostr itself is a Twitter clone.

2026-05-16 11:48:25 CEST

- reply

I learned this while implementing the text-to-image opengraph previews for https://njump.me/.
It's an absurd, really crazy shit.
I've used a Go library made for this stuff, but I'm not sure the library implements everything. Apparently there is only one huge C++ library that everybody uses that implements everything. Or most likely I didn't know how to use the Go library to its full potential.
I suffered a lot through parsing and rendering fonts, measuring the rendered text, rendering in the correct places, right-to-left, emojis (another sub-nightmare, there are a million emojis and the combinations are annoying and apparently only one font that has them all), ligatures.
Many things are still broken, I think proper text alignment for RTL, ligatures for RTL arabic fonts, or maybe ligatures in general, and who knows what else.

2026-05-16 01:12:46 CEST

- reply

I get the impression that your system is very similar to https://fanfares.io/ by @npub1ark…h43w, but I don't know for sure.
I don't like encrypted stuff like that, but if people are doing it and it works maybe it's worth standardizing it on a strict specific format that other clients can also implement? Specially if it's all for a one-time single-note thing that my NIP doesn't attempt to cover. I don't know.
I think the payment-specific stuff should be left out of the NIP because it is too arbitrary, but yes you could come up with a system for sharing these things and eventually it could become a standard.
In my NIP the best thing I could come up with were these delegated lists which are were services like Nosmero can help: someone can just go on some page on the Nosmero website and setup themselves with a Monero address or whatever, then sign a 1163 pointing to some list address controlled by the main Nosmero public key.
Now whenever they receive a payment on that address that can be verified (how does it work? the sender has to submit a tx_key to Nosmero? I don't know) the Nosmero service adds that amount to the total sent by that specific user and if it meets some threshold updates the delegated list and sends it to the user's paywall-enabled relay. Now the person who sent the payment can read.
Nosmero could simultaneously run one of such relays and as long as the user had it in their lists people could still see the paywalled content from other clients.
At the same time Nosmero could still be a client that supports normal functions but also some good UI for publishing paywalled content and special rendering of paywalled content. So 3 independent functions (payment provider, relay and client).
That's how I see it, let me know if I'm completely wrong.

2026-05-15 20:39:38 CEST

- reply

You have merge powers.

2026-05-15 19:43:26 CEST

- reply

That is never going to happen because there is a law in the universe that says we can't have good things and Google follows that law.

2026-05-15 01:11:41 CEST

- reply

Have you tried Jumble?

2026-05-15 01:09:49 CEST

https://fevela.me has draft/pending posts now.
You can save for later:
https://nostr.media/25885759b773d61e9fb62aa9ea02f4f598a5350cfb19e54ad33eb3dc9be39a0c.png
And later you can publish (as previously signed, with old timestamp) or edit and resign and republish -- or discard and delete.
https://nostr.media/f57155160ab1666f5ac41aa76579489a3cc02ecacbaf79a29782ae8e04414a61.png
Notes that fail to publish (because you're offline or your relays are offline) are automatically saved.
The "Pending" menu only shows up if you have anything pending.

2026-05-15 01:05:35 CEST

Some generations ago I wrote this: https://spotify-scrobbler.fiatjaf.com/. It requires a live bunker that it uses to sign scrobbles on behalf of the users.
Disregard the fact that its usefulness is severely limited by Spotify and that we don't have live bunkers. What other similar use cases would fit this same server-side Nostr service paradigm?
#nevent1q…0wrt

2026-05-15 01:05:22 CEST

I was trying to scrape a website briefly for research purposes.
Fetching the HTML with curl using the correct combination of headers worked fine, but when I tried to do it from inside my program it returned an error 403, exact same headers, same IP, same URL.
Eventually I found out that the website had Cloudflare in front and Cloudflare did client fingerprinting based on the TLS algorithms advertised or something like that, such that curl and browsers were allowed but not anything else.
It worked when I switched my code to using libcurl.
This is both stupid and dystopic. How did we get to this situation?

2026-05-14 18:24:06 CEST

This is good. Clients should make different choices and be opinionated instead of trying to please everybody.
#nevent1q…09nh
As long as they all talk the same protocol.

2026-05-14 17:01:11 CEST

Two immediate use-cases that came to my mind now are @npub1v0l…qj49's zap.stream server publishing stream announcements on behalf of users, and @npub15qy…yejr's git servers that can be controlled directly via ssh and still get repository announcements published under the correct user.
#nevent1q…t48d

2026-05-14 14:31:39 CEST

Satellites continue to be useless except for the governments that want to surveil, enslave and control you.
#nevent1q…t8rr

2026-05-14 14:22:33 CEST

- reply

It is not expensive to run a relay though. If your relay is only used by a few users the cost is probably less than $1/mo (there are no such cheap VPSes out there, but you could be a tenant on someone else's server), same if you host stuff on your local desktop and expose it to the internet with Cloudflare etc, or even an Android phone.
I am not trying to win the argument of how easy it is to run a community or a relay, though. The entire point of Nostr is that most people don't have to run servers.
It is probably true that it in practice it is easier to run a BitSocial community (again, Nostr relays are not just communities, they are a bunch of things), but I'm not super excited about IPFS. Are you sure it works? I was super excited about IPFS many years ago but all I got was disappointment, wasted time and lost data. I don't think it can ever work. If it seems to work for you I would bet it is because they introduced some hardcoded bigserver centralization in the mix and everybody is relying on that without even realizing.
There is a cost to connecting, routing, finding, hosting and serving data. On Nostr these costs are clear and obvious with the concept of relays. On IPFS that cost is distributed to people who never signed up for that job.

2026-05-14 11:50:56 CEST

- reply

This makes Bitsocial communities even more like Nostr relays: you said it was free to run a Bitsocial community, but now you're saying I'll need basically a server online 24/7, even if running in my home. This is equivalent to an HTTP/WebSocket server required for a Nostr relay.
Nostr relays can also run on rented hosting infrastructure.
They can also run on alternative domain name systems like .bso (although no one does this because we are not that crazy yet), we do have some relays running on .onion.
But I don't care about the similarities between Nostr relays and Bitsocial communities, it's ok if they're completely different to me, I was just making a comment.

2026-05-14 11:46:53 CEST

- reply

On Nostr you don't have to "share a relay". You read from people's relays directly, and they read from yours. But this is for the Twitter-style microblogging interface that BitSocial apparently doesn't have, so it's irrelevant here.
BitSocial communities are _like_ a relay in the sense that there is someone who "owns" them. Of course there are differences, but there are also similarities.
Nostr relays can be treated like closed or semi-closed communities too.

2026-05-14 01:14:49 CEST

If we had server-side Nostr services that could seamlessly and safely sign stuff on behalf of users what are some useful things that could be built?

2026-05-13 15:05:00 CEST

Time to fix this: https://github.com/dtonon/fevela/pull/103
#nevent1q…626r

2026-05-13 14:58:34 CEST

- reply

This is the correct answer.

2026-05-13 14:20:01 CEST

- reply

You mean https://nosmero.com/? In a brief look I couldn't understand how they're doing paywalled content, I also don't know who is behind that site, but I wish they considered https://github.com/nostr-protocol/nips/pull/2156 and provided their feedback. It's independent of payment methods and not tied to zaps or anything.
A generic standard that multiple clients implement would be better than some specific platform that does their own custom paywall scheme.

2026-05-13 14:16:43 CEST

Why are all Nostr clients trying to copy X, and yet they have a thousand emojis to select reactions from when X only has 1?
Who decided that more is always better than 1 and making the user choose is always better than simplifying things?

2026-05-13 02:04:28 CEST

- reply

Is this how FIPS routing works?

2026-05-13 02:02:29 CEST

- reply

Over the years at various circumstances I asked a bunch of people whether they would be willing to accept USD for their relays and got the answer multiple times that if they did they would become liable for the content published on the relay, or something like that.

2026-05-13 01:59:24 CEST

- reply

Aside from that it looks a somewhat like Nostr, but more limited, less chaotic, and incredibly over-engineered.
I don't know if I understood it correctly because it's painful to read all this AI text but it looks like they have all these claims about cryptographic identity (and unnecessarily each identity has to keep track of a log of all its metadata operations, like Scuttlebutt) but then all the content is at mercy of a specific server run by a community (or, more likely, they will host virtual servers for every community), and then you have to log in with Google to each different server (I did that) so I assume I'll have a different identity on each server, which defeats the entire purpose. It's better to just use Discord or one of those simple Discord alternatives.
It looks like they're trying to solve a small and simple problem, but shoved in too many new "protocol" concepts at the same time and now I would be skeptical that anyone will attempt to implement their protocol or build on top of it without relying on their software or their infrastructure, since everything is so complicated, who knows, maybe the AI will build everything.

2026-05-13 01:46:21 CEST

- reply

My first impression is that all the copy and protocol explanations are written by AI.

2026-05-12 16:47:51 CEST

I wonder if there isn't a big mismatch in the world of Bitcoin funding: too much dedicated to experimental wallets, niche technologies, Bitcoin Core fuzz testing and failed startups that market themselves to existing Bitcoiners; too little dedicated to producing useful stuff that non-Bitcoiners want, or straight-up buying existing businesses and turning them into Bitcoin companies.
#nevent1q…tz23

2026-05-12 05:17:06 CEST

This is the best news I've seen for Bitcoin in a long time: #nevent1q…8sqm
What other cases there are of services with real customers selling something that isn't "for bitcoiners" that stopped taking fiat payments?
My expectation and hope was always that a percentage of customers would bite the bullet and figure out how to get some coins in order to buy the thing. Most of them would find out it wasn't that hard anyway.
Now imagine if more services did this. Or imagine a world in which bitcoiners produced things that the external world wanted to buy, but was only being sold for Bitcoin?

2026-05-12 00:39:40 CEST

https://fevela.me/ already works offline for reading with a cool very fast internal database, soon to release offline publishing: https://github.com/dtonon/fevela/pull/100
#nevent1q…ne9s

2026-05-11 20:54:00 CEST

- reply

If IPFS and p2p just worked and we could just assume that everything everybody published was ready "in the cloud" and easy accessible by anyone then Nostr wouldn't have ever existed.

2026-05-11 20:53:39 CEST

- reply

I don't think he will understand because he thinks Nostr relays are some kind of gateway you have to hardcode into an app or something like that. So you pick one relay and you're stuck with publishing only to that and reading only from that? I'm not sure what is his understanding.
But you are right that relays are much more like what they call "communities" on BitSocial.
Relays could have been "just a keypair" on Nostr too, but that would be stupid, because one of the functions of relays is to solve connectivity. Because p2p doesn't really work on a global scale relays are both classic web servers servers with DNS names and "communities". But of course some people went overboard with the concept of relays after that, which is good.

2026-05-10 12:57:13 CEST

- reply

Please support my specific Motorola model from 2016 so I can try to contribute.

2026-05-09 15:25:34 CEST

This is surprisingly a pretty good episode: #naddr1qv…kupv
I didn't expect @npub1zxu…cx2y to be such an idealist, he used to give me the impression of a skeptic pragmatist who had lost all his early vision of a better world, but was pleasantly surprised he is still delusional.
Of course at this point he has probably already abandoned https://github.com/justinmoon/shadow, but that really sounded like a good plan and very grounded, it's still worth a listen.
Also good points in the end about how Marmot is a bad idea.

2026-05-09 14:07:17 CEST

- reply

I don't know anything, but I was convinced by this: #nevent1q…zcke
At best raising too many flags for the Samourai people is a distraction from much more worthwhile causes each person could be focusing on, like Roman Sterlingov or whatever (I also don't know about this case either, but it's just an example).
Probably even spending 5 minutes talking to your local fruit dealer about accepting Bitcoin has a much better effect in the world than donating money to Samourai at this point.

2026-05-09 13:59:03 CEST

- reply

Yes, but who will type an nsite URL? 44billion packages that in a way that is usable, and manages authentication.

2026-05-08 16:25:39 CEST

- reply

Try https://nostrord.com/open/?relay=chat.wisp.talk&group=rootstock (or install the native app from https://nostrord.com/download/ that is always much better).
Please make this link work on Wisp, @npub1utx…50e8.

2026-05-08 16:20:06 CEST

The @npub107j…ncxg exit shows how important @npub1l3c…6vs2's https://44billion.net is.
Soon some of the best clients of Nostr -- https://grimoire.rocks, https://habla.news and https://chachi.chat -- will be down and there is nothing we can do about that.
In an environment where these apps were published as fully static HTML/JS assets and used through an app like 44billion they could live forever.
Better than that: if it's easy to browse and recommend new maintainers that will incentivize new developers to continue maintaining forks of these codebases, as they wouldn't have to go looking for users and begging them to switch to a new URL. That means these apps can continue to live and users can continue to receive updates and everybody wins.

2026-05-08 15:49:28 CEST

@npub1jvx…7yqz please consider joining: #naddr1qq…d3pw

2026-05-08 03:52:20 CEST

https://www.youtube.com/playlist?list=PLPqq4mNyJqgf9Xxg51oMTRBoCxmWHhFHk

2026-05-08 00:11:24 CEST

I want Nostr to improve the status of online communication and publication in many ways. I want to see if it will really work in reality as it does in theory. I think Nostr has tons of potentially very interesting features hidden in it that will only make sense once more people are using it. I really want to see all of this in action.
#nevent1q…9fpu

2026-05-07 03:52:54 CEST

- reply

You are right that Lightning is fundamentally broken and a horrible system to build on top of.

2026-05-06 18:54:29 CEST

Nostr might not be winning against X, but at least it is winning against Postel's Law, which is a much worse enemy.
#nevent1q…vsxf

2026-05-06 13:34:01 CEST

Some people think Bitcoin doesn't have to scale and get adopted enough to become money, it can just be a "store of value" forever.
The first thing is that these people don't really believe in "storing" anything, they want their "value" to go up, not to be stored, so the discourse is already skewed from the start.
Meanwhile all the value Bitcoin has today and all its price growth came from the expectation that it would be used as money (i.e. means of payment etc) at some point.
Because random pubkeys stored on blockchains are just worthless bytes, if we stop making moves towards the only real goal (commerce adoption), then eventually markets notice and all the side "store of value" and related discourses are exposed to reality.
Remember those people that used to say Bitcoin was a ponzi scheme -- I don't know, Peter Schiff, Jorge Stolfi? Their takes were nonsense to me at first because I had in my mind that everybody believed that Bitcoin would eventually become money, so there was no way this was a game of the greater fool, everybody would benefit, even the last person to buy Bitcoin on Earth would benefit from it.
But no, these people just assumed Bitcoin would never become money, and with that assumption their reasoning makes perfect sense: if Bitcoin doesn't become money then it is nothing but a ponzi scheme -- as most of the shitcoins clearly are.
And now we have all these self-described Bitcoiners who think the same, don't be one of them. And please make them wrong again.

2026-05-05 00:50:46 CEST

The latest #pyramid release allows you to see who are the weirdos connecting to your relay:
https://nostr.media/28cb0e556f01a3b4564807cbdbdefa38f08beef78e2cb261cd7ffe78447afca5.png
And what they are subscribing to:
https://nostr.media/52c4bea08dfccef21403278fc2a743bc9ce85439c831a19116f0d233237fd895.png
(All the IPs were randomized before the picture was taken.)

2026-05-04 02:04:04 CEST

This is a stupid protocol, but I like that at least they are not shy about the need to have multiple interoperable clients with no dependency on centralized servers or domain names.
#nevent1q…aj6y

2026-05-03 21:50:09 CEST

UX specialists saw that AWS was successful and immediately concluded that their click-ops UX was the cause of the success, so they had that replicated on Google Cloud Console.
The market has decided.

2026-05-03 04:37:14 CEST

People should listen to James O'Beirne's take on quantum threats to Bitcoin more.
https://www.youtube.com/watch?v=wbJkODcrz7Q
In short: there are none, and scaling and miner revenue are much more important concerns regardless.

2026-05-03 02:15:44 CEST

I've opened my Gmail web app 3 times today and deleted all emails on the inbox. The same emails were there again the next time I opened it some hours later. I think the third time it worked.

2026-05-02 14:21:24 CEST

There are so many emojis and most of them no one uses, I don't know how you manage to find the ones you want to use in that enormous (and tabbed) pile of icons.
Even worse, my two most common emotions when reading stuff online are not represented at all.

2026-05-02 14:16:59 CEST

- reply

Looks like a scam to me.
Also next time please use direct references instead of links to a particular client's URL.

2026-05-01 19:13:14 CEST

- reply

A very cheap offline device that every humble merchant could easily acquire would be ideal.
I'm sure @npub1c87…8avm will do something and save the day here.

2026-05-01 19:00:02 CEST

- reply

Most of the videos of Bitcoin being used in commerce in backwater places I see involve a phone with a shitty wallet interface in it.
This setup is kinda bad as it has way too many requirements:
- a phone
- internet access for the receiver
- internet access to the payer
- a setup that is casual enough for the receiver to take his own phone out of his pocket and type numbers in it
- the guy with the phone must also be the owner of the shop and mix his finances with those of the shop
The last one is the most absurd to me.
If we assume everybody has a phone, though, I don't see why there couldn't exist an app that worked offline where every employee of a small business could type a number and generate a QR code that the payer scans and gets the amount already converted in his wallet to pay.
Or, if we assume the receiver will have internet, we can skip that part and let the employee generate an invoice that will be paid but the money will go to the shop's wallet, not to the employee.
These are basic things, so maybe they do exist and I'm just uninformed. I would do these apps myself if I could, but it doesn't really help if they "exist" but the people in the trenches evangelizing Bitcoin to commerce aren't aware of them.

2026-05-01 18:50:22 CEST

I paid for a meal with Bitcoin recently. The place was very modest and they just had a WoS QR code glued to wall. When I told the old woman at the cashier that I wanted to pay in Bitcoin she just told me the amount and trusted me to type that on my phone and trusted that my wallet would know how to convert that into satoshis at a reasonable exchange rate (she didn't know anything about Bitcoin I'm pretty sure).
Can't we make this better? There could exist a device with buttons where she could type the amount like she did with the credit card machines all other customers were using. She would just press the amount there and handed me a QR code to scan with the amount included, and exchange rate conversion done at some server trusted by the restaurant, it could be fully offline.
I'm just saying this because I was amazed by the fact that so many years have passed and I barely hear about these kinds of issues or the solutions to them. Makes me feel that no one is thinking about the problems of grassroot Bitcoin commerce adoption, which is the most important thing.

2026-05-01 18:32:22 CEST

- reply

No comments until you prefix your references with "nostr:".

2026-05-01 18:31:48 CEST

- reply

New name: "Tico-tico".

2026-04-30 19:34:20 CEST

- reply

I've read it, I can see why're you having this reaction, but what is written there is just a logical follow up to all the things Paul has been saying for years.
I don't think it is hilarious, the success of the Bitcoin project is a very serious matter to me and Paul happens to be very correct in his diagnostic of the problem. There are no easy solutions unfortunately, maybe no solutions whatsoever.

2026-04-29 22:08:06 CEST

Nostr promoting reunions of old friends, beautiful to see.
#nevent1q…4f0x

2026-04-29 19:57:53 CEST

- reply

Why do you think eCash hurts Bitcoin at all?
It's either going nowhere so you can just ignore it; or it will serve as a testnet with real money for technology that can be easily adopted by Bitcoin; or, if Bitcoin decides to die of apathy, people can switch to eCash and still reach the ultimate goal of Bitcoin in the end. It's a big win for all sides.

2026-04-29 01:58:36 CEST

- reply

Zero people mentioning Nostr, NIP-34, GRASP or linking to https://gitgrasp.com/ in the comments. This is just sad.
On X people are even asking for it, and yet no one answers: https://xcancel.com/citlayik/status/2049244958121742756

2026-04-29 00:55:23 CEST

Quotes as replies: back to the old Nostr days.
https://nostr.media/2e18c0dcc23e6e2cbff91e3ebc89a3a519d5e609aa0ce9dd38cc1f362a08c931.png

2026-04-28 21:02:07 CEST

- reply

That annoys me so much.
Then instead of having a simple static description of their services, which is what they need most of the times, they fall into a stupid posting frenzy (that dies after a while, when it doesn't become meme-posting) about nonsense related to their business or random pictures.
Please fix.

2026-04-28 20:58:21 CEST

- reply

In that case you're giving full authority to the person that controls that keypair, which is similar to giving full authority to a server.
In NIP-29 you only give partial authority to a server at all times, you always keep your right to migrate to a different server.

2026-04-28 20:56:25 CEST

- reply

Should be easy to always have a fallback server online if the group has any value in it.
And to coodinate a group migration that keeps the same id and history semi-automatically in case the original server is going down.
Even if the original main server goes down forever unexpectedly we can still do something, assuming some metadata about the original group and its members is stored by clients.
None of that is implemented, of course, but to me are the most important parts of NIP-29.

2026-04-27 20:11:48 CEST

If we were to market NIP-17 as a simple generic open protocol for DMs on the internet (without mentioning Nostr or NIPs or anything) by what name could we refer to it?

2026-04-27 20:10:02 CEST

Some people are sleeping on https://nostrord.com/.

2026-04-26 22:09:27 CEST

- reply

There would be no fork in that case, because there would be no money to pay for all the initial development work the sidechains need and whatnot.
Do you know how much money is poured into developing Bitcoin Core as well as grants for tons of other useless projects every year?
If eCash received 10% of that they get wouldn't have the need to sell some coins to fund their bootstrapping operation. But of course they would never get that since it's not a Bitcoin project, which is understandable.
But then somehow when they try to use the fact that they're not a Bitcoin project and transparently sell some newly-generated coins -- on a new blockchain that isn't Bitcoin -- suddenly they are stealing?

2026-04-26 18:49:55 CEST

- reply

In which world a "classical ICO" would be a better idea? Why would you even consider that?
In which sense a MASF is equivalent to a 51% attack? A 51% attack is when a coalition of evil miners decide to revert transactions in order to steal things, a MASF is just activating an optional soft-fork.

2026-04-26 18:10:57 CEST

- reply

The odds of it failing are definitely much bigger than those of it succeeding, not even Paul denies that.
But what do we lose by trying? Drivechain has zero chance of being activated on Bitcoin today anyway.
If eCash gets even a little bit of usage that may be enough to test Drivechain with real money and convince miners to MASF it into Bitcoin (Core will never do it, but CUSF solves that).

2026-04-26 18:07:57 CEST

- reply

Paul Sztorc has mentioned that he would probably support activating these things through CUSF on eCash. I haven't looked into the Rust Drivechain CUSF implementation, but I assume that for OP_CAT it should be much simpler, am I right?
OP_CCV I have no idea.

2026-04-26 17:11:31 CEST

https://ecash.com/ is a really good idea and very necessary in the current state of the world.
I really hope it gets a chance to fulfill its purpose.

2026-04-23 03:41:53 CEST

Who said Nostr doesn't have valuable original content?
#nevent1q…34ca

2026-04-22 22:11:49 CEST

- reply

Don't blame me.

2026-04-21 16:57:45 CEST

https://jumble.social/ DM implementation is looking very solid with NIP-4E support.

2026-04-20 14:42:42 CEST

- reply

What did you use to make those nice coloured diagrams?
https://fips.network/diagrams/fips-node-architecture-hero.svg

2026-04-20 14:40:06 CEST

Here, for example: https://lobste.rs/s/ktmwly/what_we_once_had_at_height_xmpp_era
A group of technology enthusiasts clamoring for an open DM protocol and no one telling them about the great news of NIP-17 privacy-preserving messaging that works + user-chosen relays for maximum decentralization.
#nevent1q…gxlg

2026-04-20 13:38:55 CEST

Everyone promoting Nostr inside Nostr is banned forever.
#nevent1q…c3mm

2026-04-20 01:25:08 CEST

- reply

This reminds me of once when a friend was searching for some program that did a small thing for his Windows computer, I think it was something about PDFs, but all he could find were two professional business-focused apps that costed a ton of money.
So I took the same query he was using on Google and appended it with "open-source" and instantly found a bunch of alternatives, all hosted on GitHub, semi-finished, but that did the job. They even shipped compiled binaries so it was just download and use.
He concluded that "open-source" was a secret magic word for getting free stuff on the internet.

2026-04-19 11:51:59 CEST

- reply

The --outbox flag does that for inboxes too already. I didn't have a better name.
That's what happened in #nevent1q…uxt9

2026-04-19 01:29:50 CEST

https://nostr.media/de0711bb4a2f969729b39ceaec8d38e4a8b8a4115ad85ff121bdd6ac90de2650.png

2026-04-19 01:22:11 CEST

I don't know when was the last time you tried or upgraded #nak, but there are some new (or maybe not super new) useful things (and hopefully not too many new bugs) that may interest you:
- "nak profile <pubkey-npub-nprofile-nip05-etc>", easily the most useful of the newish commands, I use it all the time to get the name of some random pubkey I see in the output of other nak commands.
- "nak group info/members/admins <nip29-group-address>", displays information about that group. then there is "nak group chat" that streams the chat room live in readable format, together with "nak group chat send" to send a message (from another terminal); "nak group talk" that yields a URL you can visit to join the group chat room in your browser; "nak group forum" displays the forum view of that group, together with "nak group forum create/comment" for creating a new thread of commenting on an existing thread.
- "nak bunker --profile <name>" stores your bunker data in a file under that name such that you can restart it later easily; then if you use this profile name you can later run "nak bunker connect --profile <name> 'nostrconnect://...'" from another terminal window to connect using the "scan QR code" flow instead of the "paste bunker URI" flow.
- "nak dekey" manages your NIP-4E decoupled encryption key (famously supported in Coop and Jumble DMs).
- "nak git" I think I've mentioned before, but it works pretty well, I use it everyday and as a has ton of subcommands I won't mention here.
- "nak validate" takes events as input and tells if they have all the required tags and in the expected formats according to https://github.com/nostr-protocol/registry-of-kinds.
- also when doing "nak req" or "nak event" you can pass an --outbox flag and nak will figure out the relays to connect to on your behalf, it will do that smartly according to the event authors, tags or parameters in the filters.
https://github.com/fiatjaf/nak/releases/tag/v0.19.6
Please report bugs or ask for features here in the comments or in the chat: https://web.nostrord.com/?relay=pyramid.fiatjaf.com&group=oycleloughr

2026-04-18 14:03:53 CEST

Looks like @npub1uh8…9y4m (Tadge Dryja) wanted to implement Lightning first as a much simpler protocol, with no onion routing, easier to debug, no HTLCs.
https://www.youtube.com/watch?v=o2F18lui1bE
It was interesting to hear the full story of his Bitcoin life, I don't think it had been told before. Including what happened in the mysterious foundation of Lightning Labs (how it started as a Poon-Dryja company and fast-forward some years and it's just Stark-Roasbeef) and why he stopped working on DLCs.

2026-04-18 04:32:21 CEST

- reply

Once you get the latest update to #pyramid you'll have access to many people's IPs once they connect to wss://spatia-arcana.com/ so you'll be able to publicly shame them into reading the breadcrumbs you left.
https://nostr.media/780927b2347bbf401605b8ba9a6e32fe8e6fa48b58273164c09ea01c1019decd.png

2026-04-18 01:45:33 CEST

- reply

What about StarCraft?

2026-04-18 00:14:43 CEST

- reply

I think it is fine for Zapstore to only have comments in its own relay, it's a choice clients and users can make.
But regardless of that to me the best possible UX would be to have a link on the Zapstore website with an nevent that automatically opens in my client so I can comment and interact from there.
Like what was achieved here, just with less hops. I don't mind the hops, they are cool too, I think everybody can do them, but we'll need a tool like nak but for phones.

2026-04-18 00:11:18 CEST

- reply

Honestly, what would be the great dream-like amazing UX for this in the legacy web platforms?
The Zapstore website would have a random "comment with Facebook" embedded. And in the comments no one would know who is the app author responding to comments from other randos because the identities would be totally isolated.

2026-04-18 00:08:20 CEST

- reply

As estatísticas na imagem são de um servidor mostrando quantas máquinas o estão atacando.

2026-04-18 00:03:16 CEST

Today I saw a comment from @npub1c3g…86r6 on https://zapstore.dev/apps/com.fiatjaf.topaz and I wanted to reply to it.
The Zapstore website wanted me to sign in with an extension to do that, but I only have a bunker, so thought I would open the comment on https://fevela.me and reply from there.
But the Zapstore website doesn't tell me the note id nor it gives me an nevent code, but it does gives me the author npub, so I tried to just visit that profile and wait for the note to be fetched, but I waited and it wasn't.
Turns out the note wasn't in any of the (many) relays of @npub1c3g…86r6, as the command
~> nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday --outbox
didn't give me any results. So I guessed that it was only on wss://relay.zapstore.dev. So I ran this command:
~> nak req -k 1111 -a c45041618951bb6012ac23f5cdf3d740465f2d640be841fd9bb1d0733370cd3c --outbox --since yesterday relay.zapstore.dev | nak event --outbox
And the note was automatically published to a bunch of places:
publishing to nostr.hifish.org... failed: publish: context deadline exceeded
publishing to nostr.wine... success.
publishing to wot.nostr.net... success.
publishing to purplepag.es... failed: msg: blocked: kind 1111 is not allowed
publishing to inbox.relays.land... failed: msg: blocked: this event doesn't target any real users
publishing to 0xprivacy.nostr1.com... failed: msg: auth-required: you must auth
publishing to xmr.usenostr.org... failed: msg: blocked: you must pay admission fee. visit relay url on browser.
publishing to relay.nostr.wf... success.
publishing to relay.nostr.com.au... success.
publishing to auth.nostr1.com... failed: msg: auth-required: you must auth
publishing to jskitty.cat/nostr... success.
publishing to relay.0xchat.com... success.
publishing to premium.primal.net... success.
publishing to relay.primal.net... success.
publishing to relay.0xprivacy.online... failed: msg: auth-required: authenticate to publish events
publishing to pyramid.fiatjaf.com/inbox... success.
publishing to spatia-arcana.com/inbox... success.
publishing to lightning.red/inbox... success.
(Notice that it was also published to my inbox relays because it had a p-tag to me and nak detected it automatically.)
This is a success story. Now I can finally respond.

2026-04-17 22:05:18 CEST

- reply

I didn't see the zap, it's probably sent to the wrong relay, but anyway I'll give my honest feedback:
I appreciate the intention, but this looks too much like every other AI-generated website, paradoxically it's not weird enough to catch attention.
I feel like I'll read pages of text only to find out that the entire substance was already in the page title (not saying this is the case, but it is the case for many others with similar design).

2026-04-17 21:00:13 CEST

- reply

Pay me 100 satoshis if you want me to click on that.

2026-04-17 20:11:16 CEST

There will come the day in which people will have to pay others to look at their AI-generated websites with lots of gradients, many words but completely void of any useful content whatsoever.

2026-04-17 16:38:54 CEST

- reply

Very philosophical commentary.

2026-04-17 02:17:37 CEST

- reply

What are the issues of centralized image proxies?

2026-04-16 18:47:53 CEST

- reply

Good news, but what is this partner shenanigans? Isn't the thing open for all clients to connect directly?

2026-04-16 18:03:52 CEST

- reply

I don't have anything to do with that one.

2026-04-16 17:21:32 CEST

- reply

This can't be right, right?
https://nostr.media/c91781d9c0a989d6a8d5770ee84e500555cc627472ebd12fb806ac2d3fb9555c.png

2026-04-16 17:20:33 CEST

Is Nostr a DDoS machine?
https://nostr.media/c1ca71e8e7c9c277d210a93bd742c2d6d15400fc3b9deba9d43f5fc0ef6c330a.png

2026-04-16 13:25:21 CEST

- reply

I had a crash caused by a stupid bug.
(Please update to v1.2.5 if you're reading this and you've installed it v1.2.4 yesterday.)

2026-04-16 01:31:09 CEST

- reply

This would be good on a relay.

2026-04-15 22:42:28 CEST

https://www.youtube.com/watch?v=MjMxtdzgcRc

2026-04-15 22:01:10 CEST

- reply

We could also do that, but it doesn't have to be the only solution.
Two problems:
1. it is not incentive-compatible (why would I retweet a thing I wouldn't have retweeted in the first place just because the person is new? This will bloat my feed with an opinion that isn't even mine etc).
2. it doesn't work if you don't have anyone following you at all. Like Shakespeare, imagine if he is revived and starts writing new plays on Nostr? He is really Shakespeare, but he doesn't know anyone, all his friends are dead.

2026-04-15 18:47:10 CEST

- reply

Why? The livestreaming server is a bad idea?