fiatjaf

Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

NIP-05 Address

_@fiatjaf.com

NIP-57 Address

fiatjaf@zbd.gg

Profile Code

nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdaksz9nhwden5te0wfjkccte9ehx7um5wghxyctwvsf8rne8

Publishing to

relay.westernbtc.com

relay.nostr.band

nostr.wine

Author Public Key

npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6

Show more details

Last Notes

2024-11-01 10:52:53

I liked this so much that I wanted to host it directly as the homepage of a khatru relay.
So I started trying to extract the electron stuff that was hardcoded into it and ended up rewriting all the Nostr-related logic and some of the other parts too and ended up with https://git.fiatjaf.com/jouble
It's hosted at https://jouble.surge.sh as a standalone web client, and embedded in https://pyramid.fiatjaf.com/browse for browsing just that relay (although it will load metadata, replies, reactions and parent posts from elsewhere when you click).
#nevent1q…gfra

2024-10-27 03:15:37

Some Mastodon people are seeing the truth: #nevent1q…9sc2
Hacker News discussion: https://news.ycombinator.com/item?id=41952994

2024-10-26 22:14:49

How reliable is browser fingerprinting these days?

2024-10-26 21:56:15

- reply

All the 3 solutions in the post assume this. And I agree it's not the case all the time, that's why solution-c at least gives the microblogger the option to not talk about his other stuff in his microblog, if he is aware of the fact that the people following him might not be interested. Not all people who have podcasts also send a note on X.com about their latest podcast episode every time.

2024-10-26 20:53:03

Some fundamentals of Nostr and where exactly we should strive for most decentralization and why were never very clear to me, as well as how should we go about dealing with microapps and "other stuff" that isn't microblogging, but today I got this better understood (although the article might not be as clear to readers):
#naddr1qq…295e

2024-10-26 10:32:06

- reply

I'm glad I got to keep my consistency. Please let me know if you notice me failing on that. My plan is to always make it clear whenever I change my beliefs.

2024-10-25 23:38:55

So this was merged:
#nevent1q…z7fg
#nevent1q…mvz4
Try opening this note on https://nostter.app/ then clicking on
- wss://algo.utxo.one
- wss://catstrr.swarmstr.com
- wss://pyramid.fiatjaf.com
- wss://yabu.me
- wss://questions.swarmstr.com
- wss://labour.fiatjaf.com

2024-10-21 19:32:07

- reply

I see what you have in mind. That would be good to have, but might be too much for nak, I don't know.
I might still do it at some point, but can't promise when.

2024-10-21 18:42:48

https://cdn.satellite.earth/4ef40a189f22264b7b1f852eadce9dba65e212efb6a3555a807e4795e60f75d6.mp4

2024-10-17 20:46:44

- reply

I did, but please don't use these horrible Markdown links, they look very broken.
I think cjdns uses a DHT, which makes me automatically against it, and Yggdrasil doesn't have an explanation of how it does routing anywhere I could find, which is sad because I don't want to spend my life studying it and if they had a big new idea on that front I assume they would have put it in bold text at the landing page, right? Do you happen to know how it works?

2024-10-17 12:17:05

- reply

I say that because I'm trying to use what essentially are DMs in a thing, but are not real DMs, so I wanted to use a different kind -- but then the external wrapper would be the same kind anyway, and I still need a relay list to know what relays to publish these things.
And then https://github.com/nbd-wtf/go-nostr has each NIP as a different subpackage and it kinda makes no sense to split functionality between them if one always necessarily depends on the other and the other isn't used anywhere except with the one.
At least we should expand NIP-17 to include other use cases, because having stuff explicitly saying "direct messages" there is awkward when the same "nip17" package must also be used when you're passing around other kinds of stuff.

2024-10-17 12:12:28

@npub1gcx…nj5z @npub1jlr…ynqn are there other use cases for gift-wraps happening besides messages?
If yes, are these using other kinds for the rumor besides 14, but aside from the shouldn't they work exactly the same way? Like the flow for subscribing and publishing these should also use the kind 10050 relay list and everything else is the same except for the kind number?
If that is the case, shouldn't we merge NIP-17 and NIP-59 to simplify things, and then add a table of kinds being used besides kind 14 for all the other use cases?

2024-10-15 22:06:36

https://newsletter.squishy.computer/p/natures-many-attempts-to-evolve-a

2024-10-15 21:56:24

It's time for big public relays to start adding some restrictions on the content they accept and from whom.

2024-10-14 13:28:45

- reply

If only we had a way to publish podcasts on Nostr!, but that is impossible, too hard, we will never be able to.

2024-10-13 14:58:45

- reply

Since when you do you have concerns? Coinos has been online for 4 years straight and it's offline once today so you're vindicated? Wait, it's already online again.

2024-10-13 14:56:03

- reply

let thing
try {
JSON.parse(stuff)
} catch (err) {
console.log("what should we do now?")
}
thing?.whatever?.inside?.()

2024-10-13 14:53:01

Nostr is pro-censorship.
#nevent1q…h9m5

2024-10-12 14:23:10

Some timestamping fun here, for those of you who asked:
#nevent1q…pf9t

2024-10-12 01:31:33

- reply

https://www.youtube.com/watch?v=cGtjr-U5bT4

2024-10-12 00:58:19

This video is how I feel when people try to convince others to use Nostr by highlighting the Nostr experience as it is today, not realizing that with so few people here this is all a bunch of nothing and very uninteresting to most.
"Look, on the internet you can listen to a baseball game or share automobile statistics!"
Maybe Bill Gates had no idea of what could the internet accomplish as it gathered more users, but I like to think we have a lot of ideas of what Nostr can accomplish as it grows, and I feel that talking about those can be much more interesting than talking about the fact that you can get a 50 sats zap today.
The potential is so much bigger that it might end up inspiring the newcomers, while the present might just depress them.
#nevent1q…zsuv

2024-10-12 00:32:11

Apparently AI sucks: https://shenisha.substack.com/p/are-ai-coding-assistants-really-saving

2024-10-10 20:34:50

It's weird to see external people that are aligned with Nostr's goals and even the overall design to complain about petty bugs or small details -- well, even big issues.
"Oh, I like the idea of Nostr, but it's so bad because I tried a random client and the search button doesn't work, therefore I will assert that Nostr is retarded and will never succeed."
The thing is: to whom are you complaining? Nostr isn't an organization trying to sell you anything, and if you are aligned with the goals then that supposed "Nostr problem" is also your problem so start trying to solve it. Or maybe you have a better alternative?, otherwise the tone of the complaint doesn't make sense.

2024-10-10 19:21:43

The internet is a place where any comment about B being better than A will immediately face a response claiming that the market will decide.

2024-10-08 20:02:13

https://privatelawsociety.net/know

2024-10-08 15:12:20

Too many developers trying to make the superapp of Nostr when the best approach is too have smaller apps doing less things and a better compatibility layer between them.

2024-10-08 10:14:19

- reply

I was smelling that too, ahahah.

2024-10-06 21:41:35

- reply

After using it for a while my conclusion is that it isn't very good.

2024-10-06 17:07:27

- reply

Infinite.

2024-10-05 00:13:12

Contributing to open-source projects can be rewarding, even if sometimes it takes a much longer time than we would expect: https://github.com/bigskysoftware/_hyperscript/pull/487

2024-10-03 20:21:34

Single-click relay browsing also works on Coracle. Some links for testing:
wss://catstrr.swarmstr.com/
wss://gm.swarmstr.com/
wss://questions.swarmstr.com/
wss://eyes.f7z.io/
wss://labour.fiatjaf.com/
wss://ppe.swarmstr.com/
wss://140.f7z.io/
wss://yabu.me/
#nevent1q…z907

2024-10-03 11:27:34

- reply

It is. I guess this entire site has to be restyled and together with that the Asciidoc styles. Also Asciidoc has support for sidebars and stuff, but currently that will just show up in the middle of the text since there is no space -- maybe on Wikifreedia the sidebars would have more space to exist.
Oh, I also have to fix the &'#s issue or whatever that is.
There is not enough time.

2024-10-03 11:25:16

- reply

Right now when I browse wss://ppe.swarmstr.com/ (by the way, it's just one click on the relay URL to browse on Gossip now) I see a bunch of notes that are replies to other notes that are outside the relay.
But it would be cool to have something like a feed of notes that people paid to publish specifically to that relay, like a privileged billboard, I don't know. Maybe you could even reorder the feed such that highest paying notes are returned first instead of the most recent -- or ranked by a combination of newest+more expensive, I don't know.

2024-10-03 11:22:13

- reply

What happens if I pay and then someone takes my notes from other relays and throws them into this? That will exhaust my credits? The solution is to require AUTH for publishing such that only you can publish your own notes to this relay. That's built into NIP-70 which is enabled by default on khatru, you just have to require all events to have the "-" tag. Then the question becomes about how to properly publish to this relay, and then we will need some specialized clients or some special relay view section within clients with tools for publishing relay-specific notes.

2024-10-03 11:22:05

- reply

Zaps are cool, but it would be nice to have an HTML page with a dumb form where we can request an invoice and pay.

2024-10-02 16:24:27

- reply

A bunch of proposals for variants of doing that stuff have been (and continnue to be) suggested. I don't know what is the best way (they all look flawed to me given that there is no single source of truth for what is the latest update on the subkeys of each person) -- but even with all that decided and solved I think it's a bad idea because it would add so much complexity to clients and/or relays that Nostr would essentially cease to work or instantly centralize around a single big entity that would become the central source of all truth and the almighty index of all events. That's why I'm considering these other ways.

2024-10-02 15:15:16

- reply

Exactly: #nevent1q…ae58

2024-10-02 15:14:07

- reply

#nevent1q…3mau

2024-10-02 15:08:09

- reply

#nevent1q…d20p

2024-10-02 15:07:14

Here's some sound advice for those wanting to write good software:
#nevent1q…0k3x

2024-10-02 15:05:36

- reply

Give me ssh access to your machine and I'll try to debug.

2024-10-02 14:56:32

- reply

That is a myth. Markdown was not used in plain text messages previous to its creation in 2004. There is no way anyone would write [bla](https://bla.com/) or [![alt text](https://img.com/image.jpg)](https://link.com) in a plain text document.
Also the language is completely unspecified and ultimately unparseable, such that every parser is different and adds a new thing to it, thus making everything incompatible with everything else and incentivizing everybody to support all features that any random person comes up with, which just increases the work for everybody and bloats software everywhere.
To be fair, the initial Markdown version example, https://daringfireball.net/projects/markdown/index.text, was very readable as plain text specifically because it did NOT use the horrible link formats anywhere. If those were added later by rogue implementations that's another example of the bloat that the Markdown brand has accumulated over the years.
Asciidoc is a much better language, but I also don't think we should use it for the same bloat reasons. We want clients to be simple to implement and kind:1 is already too hard to deal with without all these things.
Bluesky's text formatting is actually the best way to handle this problem I've seen: https://docs.bsky.app/docs/advanced-guides/post-richtext and @npub1l3c…6vs2 has a NIP proposal that is very similar to that -- but again I don't think we should do any of that at all.

2024-10-02 14:40:17

- reply

Looks like you're trying to use lnd@v0.18.3 while the library expects v0.17.3. Did you include a newest lnd version in your go.mod? Maybe it was included on your behalf.

2024-10-02 13:39:37

- reply

I like it more now that I know it is publishing stuff to the public instead of encrypted crap.

2024-10-02 13:35:34

- reply

Here's a useless bug report:
"Unable to spawn a new child process: Failed to spawn child process “/usr/lib/x86_64-linux-gnu/webkit2gtk-4.1/WebKitNetworkProcess” (No such file or directory)"
I do have webkit2gtk-4.1 installed, but on /usr/lib/webkit2gtk-4.1, I don't know why it was looking under that other place.

2024-10-02 13:29:55

- reply

Maybe their talent is just to make proofs-of-concept?

2024-10-02 13:28:30

- reply

Technically you would still hold the key as a user, stored somewhere safe. You just wouldn't use it daily, as all your signing would be done by these providers in the cloud. So if they disappear you can get your key from storage and use it to create more shards. You could also distribute shards to multiple providers, like 5, and make the signature be possible with just 3 out of the 5, and so on.
I don't know about the incentives, it would be almost free for these providers to support a new user, so I'm not sure payments will be needed. I mean, Blockstream has been providing co-signing services for Green wallet users for years at zero cost, for example.

2024-10-02 13:24:16

- reply

No, I don't want to reconstruct the key, I just want these providers to construct signatures, which apparently FROST can do safely -- I don't get why you can't do that with MuSig2 (wait, I guess it just doesn't work because MuSig2 has the "distributed key generation" step built in).
So I, as a user, don't have to do any cryptography or hold any keys during my daily life as a Nostr user, I can just instruct clients to fetch signatures from a server somewhere, and that server will coordinate with the 3 entities that hold my key shards to get a signature, then return the signature to the clients and, boom, I have a signed event.

2024-10-02 13:19:20

- reply

I think we could make it so the possibility of these entities colluding is small and then tradeoff is reasonable for most people (but not for all, of course) -- the alternative of trusting a single provider to hold absolute power over your entire identity, like x.com, is far worse.
I don't get what you mean by "various kinds of delegation or setup with the initial key". What do you have in mind there?

2024-10-02 13:13:30

- reply

Is that a fork of the full Fedimint repository?

2024-10-02 13:13:11

- reply

What is a "regular" schnorr m-m?

2024-10-02 02:50:11

- reply

Good to know, that prompted me to take a better look at FROST, which for some reason I initially thought was more constrained than MuSig2 in this regard and would never support this flow.

2024-10-01 22:30:48

- reply

Are you saying we have proofs of concept or and now we need real products or that we need proofs of concept?

2024-10-01 20:36:49

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

2024-10-01 20:36:32

- reply

Is it possible to take an nsec you already have and split it into 3 somehow, give one shard to each server and then they somehow collaborate to make a signature? I think you can't do MuSig2 for that, but maybe some other, simpler (less safe?) algorithm? I've asked @npub1vad…nuu7 this once but he never answered.

2024-10-01 20:33:29

- reply

Would you run one?

2024-10-01 19:55:08

Did we give up custodial nsecbunker providers? What else do we need on that front? @npub1l2v…ajft @npub1zfs…w445 @npub1myg…sn5p @npub1000…vwqk

2024-10-01 19:52:33

Portrait of a Lightning channel being force-closed: #nevent1q…mqx0

2024-10-01 19:49:05

- reply

In my mind an "algorithmic choice" means a choice made using an algorithm.

2024-10-01 19:44:57

- reply

I know, I know.

2024-10-01 19:44:28

- reply

What @npub1cgd…kfex meant is that he is not proposing that Nostr users have subkeys for themselves, just encryption keys that they use to encrypt messages in a group. The goals are very different and in this case it doesn't pose any problems to the protocol.

2024-10-01 19:43:03

- reply

@npub1zuu…c2uc is on it.

2024-10-01 17:53:11

- reply

How much do I have to pay to see the source code?

2024-10-01 17:51:19

- reply

This week you were BORN? Maybe you mean you were "born again"? That would make more sense.

2024-10-01 15:16:39

- reply

What about the UX for managing all these keys? Every time you try a new app you must create a new key using your master key, so where does that master key live?
In an offline hardware device?, then it will be incredibly hard and only 5 people in the world will do it, everybody else will just paste nsecs and the protocol will be bloated for no reason.
Or in an online device or server that keeps running 24/7 and answering requests for creating new keys somehow? Now we have just recreated NIP-46 but 100 times worse.

2024-10-01 13:45:12

- reply

I thought this was an app for writing public long-form articles actually.

2024-10-01 12:59:03

- reply

This is another reason why we should never have styles in Nostr notes.

2024-10-01 12:57:27

- reply

I guess my typical day is getting a bunch of PRs that are annoying to review so I just merge everything without looking.

2024-10-01 12:42:13

https://comet.md/

2024-09-30 17:16:37

- reply

PGP key revocation relies on keyservers, so it's not reasonable.
https://github.com/nostr-protocol/nips/pull/829 has a somewhat-comparable model that may work for Nostr, but anchored on more solid grounds.

2024-09-30 17:09:05

- reply

If you are using a random key what is the value of the AUTH?

2024-09-30 15:30:23

- reply

Once x.com becomes a custodial nsecbunker provider I think everybody who thinks Nostr is cryptographically unsound will be able to switch, knowing that their sacred keys will be finally safe.

2024-09-30 15:27:57

- reply

To be fair, it's not unreasonable to have this primal desire for subkeys and key rotation. The problem is that:
1) it's not possible to do without centralization (or a blockchain) -- Bluesky tried, and the best solution they came up with was a big server that hosts a history of keys for everybody and can censor anyone;
2) doing it by means of Nostr events that declare subkeys or delegation or whatnot, creates insurmountable complexity that turns Nostr into an unusable pile of bloatware and away its most basic feature: the chance of working;
3) it's not the only way to protect your key from rogue computers and apps -- NIP-46 and other methods exist and are much nicer to use, with still many unexplored possibilities;
4) it's not clear that more than 16 people in the entire world want this at all -- when was the last time a normal person thought about rotating their PGP keys?

2024-09-30 14:59:22

Nostr has been promoted to the status of "absolute joke": https://cdn.satellite.earth/943d5b5c4ab21939a5a1f3094cf92e24a3ac80507d50c71766a0d41d08185b62.jpg
https://x.com/jamesob/status/1839626122671116528

2024-09-30 13:45:27

NIP-29 groups on Nostrmo?
#nevent1q…acul

2024-09-30 12:14:01

- reply

Mas que introdução é essa que não tem nem um link?

2024-09-30 12:12:00

- reply

https://badges.page/

2024-09-29 22:30:56

This is great if you're bored: https://cdn.satellite.earth/7208f75c933e35047af89e591495ea14e510acdfe2b782267921ae84eb2b4207.png
Just answer everybody on wss://questions.swarmstr.com/.
(running https://github.com/mikedilger/gossip 'unstable' branch)

2024-09-27 23:31:23

- reply

racist

2024-09-27 23:30:22

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

2024-09-27 12:46:56

- reply

The reason for the goroutines is that results from different virtual queries must be returned in order, so we must do the queries in parallel then aggregate results from all of them partially instead of doing them in sequence and potentially returning results just from the first.
I am not claiming the way I did was the best possible, I would be glad to learn about better ways.

2024-09-27 12:34:49

- reply

It was deleting tags from the filter and making it so we would query external relays without the "d" tag and return anything from that pubkey instead of the correct event.

2024-09-27 12:20:08

- reply

Oh, it's that thing? Sorry, I thought it was the proprietary "private chats" thing 0xchat has currently.
We need a new number with only two characters for the MLS NIP, please, it's very important.
Hex is accepted now, by the way.

2024-09-27 11:59:22

- reply

It wasn't an argument, it was a question.

2024-09-27 01:14:00

- reply

And after that what happened? Some other bug?

2024-09-27 01:10:12

- reply

https://github.com/dgraph-io/badger

2024-09-27 01:09:39

- reply

Interesting, no, I don't know, maybe it sucks. In my tests I was impressed, but I also wasn't expecting much and didn't know what to test either.

2024-09-27 01:08:22

- reply

No, it's because I think LMDB is cooler.
But now I think I have a more defendable argument with this Badger thing.

2024-09-27 00:47:51

@npub1fjq…leku how big have you gone with a Badger database? It seems to become unmanageable at around 8GB, using an unreasonable amount of much memory in those complicated Ristretto caches and whatnot and maybe the Golang GC doesn't work well with it so CPU also goes to the roof. Or what else could be happening?

2024-09-27 00:45:11

We need clients to do something about this. It's getting hard to manually browse so many relays on nostrrr.com.
#nevent1q…ht90

2024-09-27 00:44:03

- reply

Bluge works pretty well for fulltext search, did you try it?

2024-09-27 00:39:56

- reply

My opinion is that you should remove NIP-104, whatever that is, and keep only NIP-17.

2024-09-26 22:42:02

- reply

I don't know, I am in a group called "0xchat users" or something, I guess I may have joined it by mistake then. Sorry about that.

2024-09-26 22:40:44

@npub1937…haj6 I changed SQLite on github.com/fiatjaf/eventstore to return errors when one of the limits is reached instead of just nil, copying Postgres. Hopefully that doesn't break anything.

2024-09-26 18:54:00

- reply

This is the full code for running the thing, provided that you fill in the environment variables and run it from a folder that has all the images prepared, which you can do with some simple ffmpeg commands.

2024-09-26 18:52:10

- reply

#!/usr/bin/env fish
set next (head -n 1 _next_frame)
echo "[eng] publishing frame $next"
# upload the image
set url (satellite-upload --sec $SECRET_KEY --base-name 'noi-' $next.png)
# format the timestamp
set minute (jq -n "$next / 60 | floor | . % 60" | string pad -w 2 -c 0)
set second (jq -n "$next % 60" | string pad -w 2 -c 0)
set timestamp "$(echo -n $minute)min$(echo -n $second)s"
# publish the event
set content "$timestamp
$url"
set event (nak event --sec $SECRET_KEY -k 1 -c $content $RELAY)
# print reference
set nevent (nak encode nevent -r $RELAY -a (nak key public $SECRET_KEY) (echo $event | jq -r .id))
echo "[eng] https://njump.me/$nevent"
# increase count for the next run
set next (echo $next | jq 'tonumber | . + 1' | string pad -w 4 -c 0)
echo "[eng] next is $next"
echo $next > _next_frame
# update picture
nak event --sec $SECRET_KEY -k 0 -c "{\"name\":\"emperor's new groove\",\"about\":\"we are playing the entire thing\",\"picture\":\"$url\"}" $RELAY purplepag.es relay.damus.io nos.lol relay.nos.social user.kindpag.es

2024-09-26 18:44:17

I wish 0xchat didn't have
- kind 1 feeds
- NIP-28 horrible chats
- auto-subscription to hardcoded NIP-28 groups that keep subscriptions open day and night and send me notifications
- some proprietary "private chat" technique
It could be great.

2024-09-26 17:50:20

I'm excited for the post-meme era.

2024-09-26 17:44:57

- reply

It works for me too most of the times, that doesn't mean it isn't a bad idea.

2024-09-26 17:42:37

@npub1zfs…w445 what happened here now?
https://cdn.satellite.earth/befe4dcbeb80006eda3e2eae051051825b1485358d830706af5efdc280ff90d9.png
I just downloaded Coop 0.2.0 and deleted my ~/.config/*coop and ~/.local/share/coop/ directories (but still Coop shows the old user I had created months ago, why?) and then tried to create a new identity.