fiatjaf

Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

NIP-05 Address

NIP-57 Address

Profile Code

nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprdmhxue69uhkwmr9v9ek7mnpw3hhytnyv4mz7un9d3shjqgkwaehxw309aex2mrp0yh8qunfd4skctnwv46qvv7w0u

Publishing to

gleasonator.dev/relay

relay.primal.net

relay.westernbtc.com

Author Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

Show more details

Last Notes

2024-09-16 20:30:01

- reply

What client did you use to write this? I couldn't help but noticing it has an HTML tag in it, and that shouldn't happen!

2024-09-16 14:33:05

Nostr is so decentralized: https://cdn.satellite.earth/34dd6dd038d82c61fd48ae2099efbb506706b7af8800c0c97a97c2ec94abc5c7.jpg

2024-09-16 14:22:42

- reply

Muting cannot help as a decent spammer will create a new pubkey for each post.

2024-09-16 14:11:22

- reply

I'm using a list of "spam-safe" relays but apparently I am missing a lot of replies from people whose clients are sending their replies to my inbox relays.
When browsing other people's notes, though, this technique doesn't work well or needs more thought because people replying to others are not going to send their replies to my own inbox list of relays.

2024-09-16 14:03:59

- reply

I was skeptical when I saw the Windows screen, but wow, it's hard to even imagine how this is possible.

2024-09-16 13:59:38

This was 100% expected as it is impossible to do what they want in a decentralized way. At least they are being honest now.
#nevent1q…xzq7

2024-09-15 13:30:50

- reply

I might or might not have a relay that only accepts notes that rhyme.

2024-09-14 14:37:30

How have you been dealing with the reply guy and what client do you use?
I feel like most people are still suffering with him or just got used to it, which is bad.

2024-09-14 02:26:45

- reply

There are very fine people on both sides.

2024-09-13 16:49:02

Looks good.
#nevent1q…70m4

2024-09-13 12:44:10

njump.me has clickable tags now: https://cdn.satellite.earth/dd1712f9164738e30a06d98c6929764cef1ea071a28a18ef758d6bb47b235bc0.png
This is clearly an Earth-shattering event.

2024-09-12 03:33:58

Exactly this.
#nevent1q…yqfa

2024-09-11 22:12:47

- reply

Remember that none of this would be possible without @npub1ej4…ndrm's amazing work at OpenTimestamps, so remember to always be grateful to him.

2024-09-11 22:10:56

I have just started running @nprofile…auwv and timestamping all events published to pyramid.fiatjaf.com with NIP-03 (OpenTimestamps). The timestamp events, kind 1040, are published to @npub18kz…x5sz's cellar.nostr.wine which is not going to delete them -- and to some other relays.
Somehow this will protect the humanity against the AI takeover in the future, so I recommend other people to do the same with other events. The source code is at https://git.fiatjaf.com/ots_nbot and you can customize the relays, kinds and authors it tries to timestamp, among other things, via environment variables.
If you don't understand how such a simple gesture has such immense powers, listen to Antihashed Podcast episode where this is explained, or ask @npub1t6j…ksrw.

2024-09-11 13:55:11

testing opentimestamps bot

2024-09-11 05:24:57

This is a very cool Nostr use case:
#nevent1q…5zrw
You have a normal boring old static HTML page for your event, you can quickly add an RSVP system with a little bit of a social component to it using Nostr and NIP-52.
Coming soon to a https://git.fiatjaf.com/nostr-web-components near you (maybe).

2024-09-11 00:56:21

- reply

What client?

2024-09-10 21:04:09

- reply

Well, I think no one is adding relay hints in the follow lists, but yes, I think you should do that -- it doesn't have to be synchronous though, a client can fill in that field the next time it is going to update the follow list.
https://github.com/nbd-wtf/nostr-sdk will look in kind:3 these hints. Actually I think even the sample code that runs in this simulation will.

2024-09-10 19:30:01

- reply

https://how-nostr-works.pages.dev/#/outbox

2024-09-10 19:28:38

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

2024-09-10 18:28:16

HTML explanation of Nostr's decentralization possibilities: https://how-nostr-works.pages.dev/

2024-09-10 04:00:06

- reply

It did not! https://cdn.satellite.earth/1793849c2fce56dfa52a94981b26ced04f9795dc0d9d74e778855bde8c6556a6.png
@npub1acg…p35c!

2024-09-10 03:58:08

Let's see if this works: https://cdn.satellite.earth/427d57e265b64935722e8deaab3fbf643681b40d32be4176a3751930f79cde08.mp4
https://cdn.satellite.earth/48212f3638c0adf10a402041ea04772375ea9d28ee3d4204b2469db4bc1f3125.png

2024-09-10 03:28:17

No one remembers anyone else's birthday anymore now that Facebook is dead.

2024-09-10 03:19:37

- reply

No, it was @npub1m4n…c2jl.

2024-09-09 21:31:15

Farcaster is falling even though they have more money, a centralized marketing department, a founder that makes good speeches and a lot of visibility in the "crypto"-adjacent media -- so these things can't be the reason why we're losing to Bluesky.
https://cdn.satellite.earth/ad7fc33626a66a7bfa8db19ab0561645931908055aa4c97846579645040ffc45.png
#nevent1q…f96l

2024-09-09 21:17:03

Apparently Nostr did grow ~25% right when Twitter got killed in Brazil: https://cdn.satellite.earth/52a154bd99e488ee2e23563517be75f0c93c7683d2c89c9fc9393bd19d7e7017.png

2024-09-09 16:43:02

Follower counts must die: #nevent1q…y2ts

2024-09-09 14:53:46

If you have read Peter Todd's disappointing L2 essays but was sad that he didn't say anything about BitVM, the first minutes of this episode contain the best explanation of BitVM I've ever heard, both v1 and v2.
#nevent1q…mq3k
Unfortunately I didn't understand how "BitVMX" works at all, but we can't have have everything.

2024-09-09 14:46:04

Some interesting comments about IPFS: https://news.ycombinator.com/item?id=37750529
Basically all people who have used it realized it wasn't working, but those who were heavily invested on it used their cognitive dissonance to reframe it as "good for internal networks" or to say that "now it is going to get better".

2024-09-08 16:25:41

- reply

I wish I had had this idea of just copying the text of the replied note, it was genius.

2024-09-08 16:25:05

I have now read Peter Todd's review on Bitcoin L2's and covenants and found it incredibly underwhelming. Even though the title is "review" I wasn't expecting it to be really just a review. It basically contains no new insights or analyses, actually it refrains from commenting on most topics based on the fact that "there has been no analyses of this" and then it just proceeds to provide descriptions of things that should have already been known by anyone who did a little bit of research into any of the topics. While reading the essay you get the impression that all L2s are bad and no soft-forks are worth doing, but then in the end it does some sleigh of hands and concludes that CTV is great just because it is the highest common denominator among all the pool of uselessness described previously.

2024-09-07 02:17:14

- reply

The IDF is clearly the state in this description.
#nevent1q…fsyt

2024-09-07 00:24:53

- reply

At least add a home page to this thing, if I try to open it on a browser it I just get a standard 404 message.

2024-09-06 21:45:03

- reply

I would only give that title to something that is interoperable or potentially interoperable with other apps. Some random spammer abusing relays as free storage isn't a real client, for example.
An app can also use Nostr identities and consume Nostr data but not want to be interoperable, and I think that makes it not a client, or a partial client, but that isn't a bad thing either. We don't have to use Nostr events for things not suited for Nostr events.

2024-09-06 17:26:08

https://delete.nostr.com/ adapted to use NIP-66 instead of hardcoded relays by @npub1uac…99rx: https://github.com/fiatjaf/nostr-event-deleter/pull/1

2024-09-06 15:49:28

- reply

Should we all just use the NIP-22 generic comment thing?

2024-09-06 15:14:39

- reply

We need another kind for longform pins then, and another kind for each use. Or now if you pin a tweet about StarCraft that will also be pinned in your profile on a recipe-sharing app? Or what is your idea?

2024-09-06 14:56:07

- reply

A more friendly approach to all kind:1 apps out there would be to make a kind:1 mentioning the long-form and pin that.

2024-09-06 13:08:20

- reply

It looks good, but as always with all things Bitcoin it doesn't scale.

2024-09-06 13:05:44

- reply

We shouldn't talk in terms of specific apps, but in terms of standards that can be implemented in multiple chats.
I think we should move it to a NIP-29 group and 0xchat implements NIP-29, but we need more apps and more tests AND I need to fix my stupid NIP-29 relay that is haunting me with the worst and most confusing bug of my life.

2024-09-06 02:41:21

- reply

We still can't do micropayments, the bot was an illusion.

2024-09-05 20:45:26

- reply

How did change your life?

2024-09-05 19:36:56

- reply

I'm happy to hear this. How did you learn about lntxbot?

2024-09-05 15:55:34

- reply

He must think that each "app" has its own backend with all the Nostr notes stored there, so that apps specifically can be pressured to censor some people and then all users of that app will not see that content. If that is how he thinks it works then his criticism is very reasonable.

2024-09-05 12:23:55

- reply

A much bigger army was unable to make IPFS work.

2024-09-05 02:11:11

running gossip global feed https://cdn.satellite.earth/89a3b48101eca6254f9920bafe754abd4dded9a8a60b8a4a88eb7a34bc5cfa9b.png

2024-09-05 01:56:08

- reply

Thank you, but NoComment is kinda bad. I'll work on it someday to make it better.

2024-09-05 01:52:58

- reply

We should do this definitely.

2024-09-05 01:52:10

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

2024-09-04 17:15:44

- reply

You didn't even read my note.

2024-09-04 17:13:42

I really don't get the people that complain that they don't get followers on Nostr because there is no algorithm.
I never got any followers in any of these platforms with algorithms (even though I used them actively for years), except when by some unexplicable hit of luck some people started using @lntxbot on Telegram and by word-of-mouth it got to Alex Bosworth and he mentioned it on tweet and then my follower count slowly grew from 50 to like 5000 over a 3-year period.
Is there a magic trick that allows you to go from 0 to 100000 by gaming the algorithm these days and then scam your followers a high-ticket course about how to get followers and become a millionaire? Or what are these people talking about? Why do they even want followers in the first place?

2024-09-04 16:54:52

- reply

Are there other clients? We don't have to trash the current recipes, we could do a transition by doing a [REQ, legacy, {kinds: [30023], #t: [cookingwhatever], until: 2024-09-04}] and then only fetch recipes on the new standard going forward. Does it work?

2024-09-04 16:00:43

- reply

I was just thinking that it would be good to define a standard for recipes on Nostr, probably with a different kind, with some relevant tags. The current way is kinda bad because it abuses the long-articles NIP and then includes some proprietary (and very long) "t" tags. Do you have any thoughts?
And then we need some other client to prove that the standard is good and then to show how can you display or interact with recipes differently.

2024-09-04 13:44:00

Who is responsible for zap.cooking?

2024-09-03 16:16:03

- reply

It's not really necessary, because it is impossible.

2024-09-03 05:02:06

- reply

Maybe your cell carrier doesn't support IPv6, but mine did.
In any case the population of people who have IPv6 but aren't aware of it is bigger than that of people who have Tor running.

2024-09-03 03:59:53

- reply

Instead of Tor could you have used IPv6? Last year I was able to ssh into my phone on 4G using its IPv6 address if I'm not mistaken. Or is IPv6 bad for privacy blablabla?

2024-09-03 03:12:48

- reply

Anyway, I'll wait for your answer regarding the repository metadata required. I can't see a way around that if you want a nice way to browse through the repo and view things in context. But if the goal is just showing a README then that's much simpler.

2024-09-03 03:11:16

- reply

I think it's still quite far from my vision, it's a work in (very slow) progress!

2024-09-03 03:09:49

- reply

OK, already answered here: #nevent1q…vglz
But is it really that slow? It's hard for me to believe it is that slow since on my terminal it runs so fast!

2024-09-03 03:06:04

- reply

What about doing a `git clone --depth 1`? I don't know how to do that on a JS library in the browser, but should be possible. Seems to be a pure client-side thing since it worked on 'song' (from the CLI) without me having to do anything on the server side.

2024-09-03 02:57:48

- reply

I was thinking that exposing files at exact commits would be simpler, but then I realized that to get the exact commit you would need an API that returns all references and HEAD (separate from the repository state event) and then I realized that to build a GitHub-like way to browse files on gitworkshop you'll also need all these things, plus a history of commits, metadata about all commits and so on, right?
Which brings me back to: why not do a full repository clone on the browser and get all that data at once? Is it just the big size of things?

2024-09-02 19:04:27

This is high quality content, the only thing it is missing is a relay hint on the "q" tag:
#nevent1q…5gt0

2024-09-02 19:01:25

- reply

Besides being different blockchains, it's different blockchains each owned by a different company with very limited interest in benefitting the whole ecosystem on behalf of their own pockets.

2024-09-02 18:07:56

- reply

But if we can't get the archive stuff to work then we could standardize an HTTP API thing that returns raw files maybe.

2024-09-02 17:52:36

- reply

Instead of running to try to catch up with a bunch of proprietary git servers we should have a standard first, then I would gladly accept it or implement it myself on song.
That native git feature you mentioned would be my first candidate for such a standard, but last time I tried to implement it on song I failed.

2024-09-02 01:48:22

- reply

Maybe this? https://www.youtube.com/watch?v=FXT6YsNa5AU

2024-09-02 01:42:00

- reply

You're so humble.

2024-09-02 01:40:03

- reply

This was probably the best note I read today.
@nprofile…9hfj give this guy a membership.

2024-09-01 17:27:22

- reply

Just stop arguing and you win.

2024-09-01 17:26:43

- reply

I see. That could be bad, but could also be good. But what would be these marketing initiatives concretely? It might be easier to get support for specific plans limited in scope than for a generic lifelong organization.

2024-09-01 17:13:09

- reply

Sorry, I'm stupid, but there are smarter people here that you can follow, such as @nprofile…98zd .

2024-09-01 17:10:34

- reply

`nak req` has recently added the `--paginate` and related flags that should, if I understand them correctly, remove the need for these scripts. The README has some examples.

2024-09-01 16:20:21

- reply

Why?

2024-09-01 16:19:58

- reply

I don't think this makes sense. Separate clients by themselves cannot offer a compelling alternative. Hiding the protocol from usets is a losing move. If a client tries to compete in the market as if it was a proprietary platform, and if any succeed it will be by capturing and breaking the network.

2024-09-01 16:14:33

Instead of rushing to get a VPN just so you can lock yourself inside Elon's prison now, what Brazilians should be doing is to beg for screenshots every time someone sends an x.com link, annoying the maximum possible number of people on every step and making them aware.

2024-09-01 15:29:27

- reply

Why not write your ideas in public? I'm open to funding good ideas. But I guess DMs are also fine.

2024-09-01 15:27:02

- reply

@nprofile…wene are you cool?

2024-09-01 15:20:37

I think by the time this happens there will be already another pseudo-decentralized social network around with big funding and cool marketing that will attract most people.
I have no idea of what to do.
#nevent1q…ykkm

2024-09-01 12:44:12

Relay hints are the life and blood of Nostr @nprofile…754h
#nevent1q…r7nl

2024-09-01 12:41:09

- reply

No. Nostr is for everybody, we want everybody and we need everybody. It doesn't work if Nostr is just full of people who agree with each other all the time.

2024-09-01 12:17:06

How can we get Bluesky banned in Brazil now?

2024-08-31 22:50:08

- reply

Maybe we didn't need Nostr in the first place, everybody could just have blogs and provide RSS feeds!
Reader clients could keep track of all the blogs you followed and aggregate all the RSS feeds in a unified feed.
And then in order to comment on other people's posts we would post to our own RSS feed and send an HTTP request to the original poster so they would notice and read and display our comment with a link to our blog?
And people didn't even have to host their own servers, they could just rely on commodity blog providers that would host things on their behalf! This could have been huge!
And the best part: it's all HTTP and HTML, so we know it will be loved by all developers and scale to millions!
https://indieweb.org/Webmention
Join us and help make this dream a reality!

2024-08-31 22:45:05

- reply

I'm not disallowing anything, I think it's great that some people want to enhance RSS, but that isn't my goal at all.

2024-08-31 22:37:31

- reply

Blossom is better than torrents for this use case.

2024-08-31 18:19:49

- reply

https://lnvps.net/

2024-08-31 17:31:38

- reply

RSS is kinda bad.

2024-08-31 17:31:20

- reply

Thank you for finding the bugs.

2024-08-31 17:29:17

- reply

Portuguese translations are an abomination, please don't.

2024-08-31 17:28:39

- reply

I see, but what I want is a way to replace it.

2024-08-31 17:27:21

Complexity leads to capture.
#nevent1q…wmhk

2024-08-31 17:26:55

- reply

Nostr is simpel.

2024-08-31 13:15:58

- reply

@npub1vxd…rs50 is the big influencer you want to talk to.

2024-08-31 13:15:09

- reply

How is fanfares.io doing Lightning-gated content? Is it a platform-specific proprietary thing or a supposedly-interoperable Nostr thing?

2024-08-31 13:14:37

- reply

Kind 31338 is vastly underspecified.
"Audio events" is super generic. An audio message is completely different from a podcast episode and both are even more different than a song. I think it's awful that these things got lumped together in the same NIP.

2024-08-31 13:12:59

- reply

I see, so the answer is the kind 31338? Both fanfares.io and npub.pro could both become RSS bridges sourcing from people's 31338 events instead of kind 1, and publishing a podcast could become a thing that doesn't require a platform, you just publish events and later you use any bridge out there to provide an RSS feed -- until podcast players start connecting to relays directly instead of using RSS (there is a PR to AntennaPod already, we just have to change the kind number and event format).
I'm not interested in the Lightning-gated stuff for now, and I think that will be the last thing someone publishing a podcast will worry about, since podcast players won't support it, but I think in the future that could become interesting too.

2024-08-31 00:51:18

- reply

I don't have a clear answer because many ideas of how to handle this come to my mind, many of which can probably be used together depending on the user and the circumstance. I'll elaborate on this a bit more and reach back to you.

2024-08-30 22:45:00

- reply

Should have used https://khatru.nostr.technology/

2024-08-30 22:44:46

- reply

Thank you, I'll look into that.