Ademan

What is the status of NIP-59 support among relays?
> To protect recipient metadata, relays SHOULD guard access to `kind 1059` events based on user AUTH. When possible, clients should only send wrapped events to relays that offer this protection.
> To protect recipient metadata, relays SHOULD only serve `kind 1059` events intended for the marked recipient. When possible, clients should only send wrapped events to `read` relays for the recipient that implement AUTH, and refuse to serve wrapped events to non-recipients.
(Yes they're not REQUIRED but they improve privacy)
#asknostr

2025-05-26 18:47:06 UTC

- reply

Maybe in the short term, but longer term I want to see permissionless communities with opt-in moderation via labels (probably) and choosing who you trust to moderate.
You can still have approval based moderation in this scheme too.

2025-05-23 17:50:26 UTC

- reply

kind 0 *
d'oh!

2025-05-23 17:40:40 UTC

- reply

Neat! Doesn't grab my nickname though, just shows my npub (using the extension). Pretty sure the relay I picked (nos.lol) should have my kind 1 on it.

2025-05-20 21:54:54 UTC

- reply

"The term ‘qualified tip’ means any cash tip received by an individual in the course of such individual's employment in an occupation which traditionally and customarily received tips on or before December 31, 2023, as provided by the Secretary."
"in the course of such individual's employment" is probably the operative (and disqualifying) section.
https://www.congress.gov/bill/119th-congress/senate-bill/129/text

2025-05-15 22:15:42 UTC

- reply

Humorous punctuation: https://bitcoin-irc.chaincode.com/bitcoin-core-dev/2025-05-15#1121197;
As recently as *today*, someone savvy enough to make it into IRC, and is aware the mailing list exists asked "Is there a ml post (I can't subscribe, it probably just sits in mod queue forever) which goes over the rationale/reason (from bitcoin core's view) for why op_return is to be changed (and the option to configure it potentially removed in the future)?"

2025-05-15 04:58:11 UTC

- reply

I can attest that it's good stuff too!

2025-05-15 00:48:44 UTC

- reply

Unfortunately I don't have a prescription.
From my vantage point the information has been adequately disseminated (thanks in part to Optech) and some contingent has failed to discover or understand it.
If I *have to* offer some kind of idea, there could be an opportunity for educational content that's in the middle ground between bitcoin influencer and what optech does now (if you really want more work lol). I'd suspect 80-90% of Optech is readily understandable by most bitcoiners, but maybe that last 10-20% turns off the less technical audience?
Maybe a more reasonable improvement would be to publish the recap on youtube either with chapters or split into separate videos by topic so that people who aren't subscribed or don't regularly listen to the recap can more easily discover, pick and choose parts of optech to consume? (I know the podcast already has topic timestamps so hopefully it's not much extra work) At minimum, saying "hey listen to this podcast and go to MM:SS" is a lot more friction than a youtube link that takes you directly to the timestamp.
I guess my prescription there is to increase optech's reach so these people are better informed lol

2025-05-14 17:19:05 UTC

- reply

For all of the people that flooded the github issues, it seemed like very few actually read the mailing list thread. I saw at least one person earnestly say they hadn't heard the rationale for removing the OP_RETURN limit, despite it being articulated in multiple places multiple ways.

2025-05-13 21:21:39 UTC

- reply

That confusion has been actively promoted, unfortunately. Very disappointing, to say the least...

2025-05-13 19:36:53 UTC

- reply

https://en.wikipedia.org/wiki/Zooko%27s_triangle IMHO makes UX of anything non-centralized very difficult (namecoin-esque tech aside).

2025-05-12 04:50:43 UTC

- reply

Should just do vulnerability disclosures on v(N-2) to keep people upgrading 😂

2025-05-05 18:02:33 UTC

- reply

Sounds expensive!

2025-05-02 19:31:48 UTC

- reply

Fair enough, but stamps uses counterparty, and the counterparty FAQ says this about OP_RETURN and prunability: https://docs.counterparty.io/docs/basics/faq/#what-happens-if-and-when-op_return-data-is-auto-pruned
> Counterparty only needs some Bitcoin full nodes somewhere to have an unpruned copy of the blockchain. As every Counterparty full node is also a Bitcoin full node, this is easily done.
stamps references the counterparty behavior as the reason why stamps uses bare multisig and says
https://github.com/mikeinspace/stamps/blob/main/BitcoinStamps.md
> The length of the string means that Counterparty defaults to bare multisig, thereby chunking the data into outputs rather than using *the limited* (and prunable) OP_RETURN.
Since counterparty refutes/denies the pruning argument, it's IMHO safe to conclude that stamps is actually using bare multisig because of the datacarrier limit anyway.

2025-05-02 19:23:32 UTC

- reply

What protocol(s) are doing that?

2025-05-02 19:21:13 UTC

- reply

Are we sure anybody is actually doing P2MS because it's unprunable, and not because of the datacarrier limit? (and/or to be jerks)

2025-05-02 19:13:23 UTC

- reply

What's the threshold to make the list? 😂

2025-05-02 03:26:15 UTC

- reply

@nprofile…t7fy plz

2025-05-02 03:16:55 UTC

- reply

No, that's not what's happening.
What you *could* say is they want to make it easier for bad actors to do a bad thing, to prevent them from doing a way, way worse thing. Kinda like leaving your car doors unlocked in the city so thieves don't break your windows.
Someone proposed to remove the data carrier limit because it caused multiple protocols to store data in unspendable outputs instead of OP_RETURN outputs. They proposed this because unspendable outputs are really bad, objectively way worse than larger OP_RETURN outputs. Even pruned nodes can never forget these unspendable outputs, they have to carry them forever, and their existence slows down every node's block processing.
A bunch of angry, low information people flooded the github discussion and the core developers overreacted and locked the thread.

2025-04-11 00:46:30 UTC

@nprofile…5dju Do you recall if Truth Social has an API and/or exposes the old masto API? (and if I'll get b& trying? lol)

2025-03-22 18:03:58 UTC

- reply

Anything interesting? I have to admit I have written bluesky off almost completely.
https://dustycloud.org/blog/how-decentralized-is-bluesky/ is utterly damning (although the author is very sympathetic to bluesky as a twitter alternative)

2025-03-15 01:01:48 UTC

#asknostr Is there any NIP that specifies to put a json *object* inside an event?

2025-03-14 05:06:38 UTC

Lol what is a kind 1111?! What is 1 not good enough for ya anymore?!

2025-02-27 19:39:09 UTC

- reply

Ah ok, I discovered there's a subforum I don't have access to, I was wondering if you had access.

2025-02-27 03:56:28 UTC

@nprofile…5t87 How long have you been on dreamcasttalk?

2025-02-22 01:27:05 UTC

- reply

You don't wanna dogfood DMs in coracle? 😂
Sent! Subject line might be easy to mistake for spam but it should be obvious it's my email address.

2025-02-21 23:15:16 UTC

- reply

Am I missing a currency preference somewhere? lol
https://image.nostr.build/6f75b3586c2a5f3b649431b1f9244f5b59349280510f6429a8577a2fe2495503.jpg

2025-02-21 23:09:06 UTC

- reply

I keep hoping somebody will pick up https://github.com/twilco/kosmonaut and productize it. No idea how to ethically fund it besides e-begging though...

2025-02-21 23:05:56 UTC

@nprofile…ulkk sorry to be obnoxious but I shot you a DM that's semi time sensitive. (not any kind of security issue)

2025-02-21 05:03:39 UTC

- reply

That was my exact reaction.

2025-01-22 02:39:48 UTC

- reply

Now: pleasantly surprised!

2025-01-22 02:38:40 UTC

#FreeRoss Thank God he's free!
Now if only we could free him from this new sentence...
https://image.nostr.build/5696385511a2b4f03533179261e5b3c7fb9b89f2895df67af42a8593eed96764.jpg

2025-01-21 22:05:24 UTC

- reply

I'm not even a little surprised, but I'm still disappointed...

2024-12-23 20:51:19 UTC

Not a big fan of the "it's just concatenation" line of argument
https://image.nostr.build/d2fcb5b9685113bd92ce5f53c111109a5c3123910fb6f7535846043714a9b9bb.png

2024-11-23 02:21:14 UTC

- reply

Engagement on nostr is infuriating (nonexistent)

2024-11-22 16:30:37 UTC

- reply

Bonus informal bug report ;-)
https://image.nostr.build/cfaca319c527095538258a6ab5d8fdbbe3a122708626a794dd7c26a5bf84bf57.jpg

2024-11-22 16:29:27 UTC

@nprofile…mwe9 did you fix something with caching websocket connections or something? Over the past month or so I stopped using coracle (and nostr) because I was being assaulted with 22242 signing requests, and now I'm not (or at least it's tolerable now).

2024-11-22 16:26:39 UTC

- reply

You make good jerky!

2024-10-25 18:01:01 UTC

- reply

This is why I use nos2x :-)

2024-10-17 17:55:25 UTC

I really wish nos2x had some kind of support for understanding what it's signing. Like a template that says "you can always sign an event that looks like this, with this varying part" or something. Specifically thinking of how I get prompted to sign like 30 22242 events, but as long as it's to a relay I've pre-approved I'm ok auto-approving. (nos2x kind of does this already, but it only keeps track of the kind, but I don't want to blanket allow 22242s)

2024-10-17 17:51:07 UTC

@nprofile…ynwy ayyyyyyyyyyyyyyyy

2024-10-03 20:46:52 UTC

Is there a legal defense fund for good samaritans willing to disobey inhuman federal edicts in order to help people affected by helene? Seems like a good cause. @nprofile…knp4 @nprofile…e9k2
If it gets well funded, either there's enough money for everyone, or if there isn't enough money, that implies a pretty large amount of civil disobedience.

2024-09-29 20:14:19 UTC

- reply

Awesome! Glad to see y'all are innovating despite consensus changes getting bogged down...

2024-09-28 02:18:19 UTC

- reply

So if this works on mainnet, is this using presigned transactions to commit to the whole tree?

2024-09-27 20:28:52 UTC

- reply

Oh wait, that's in the nos2x client library anyway lol, so yeah I guess it's a nos2x bug?

2024-09-27 20:26:41 UTC

- reply

@nprofile…k8ew I don't know if it changed but this is what the response from nos2x is. Why is coracle trying to use nip44 encryption to update my follow list? I do have encryption denied right now so it's correct that nos2x is denying the request.
https://image.nostr.build/743945c9fcd5ae8fd0a17df0375cb7ae190b4f28b6468a8527cd3ceefe4d877d.jpg

2024-09-27 20:06:48 UTC

- reply

I definitely suspect coracle is feeding it something bogus, since both likes and comments work as expected (and I assume nos2x signing is completely indifferent to the event type, except as far as permission checks)

2024-09-27 16:55:18 UTC

@nprofile…3tq5 have you ever tried to grow gooseberries in zone 8? I've been considering blueberries but I get the impression they're pretty water hungry and I don't have a good irrigation plan for where I want to put them. Plus, I have one report that they "haven't had success" with blueberries, even with irrigation, out here.
I've obviously got blackberries but I want something that can also function as a border on its own.
I'm specifically considering https://en.wikipedia.org/wiki/Ribes_curvatum but also more common gooseberry varieties.

2024-09-27 16:05:33 UTC

@nprofile…p8jn I'm getting an error "Error: nos2x: undefined commands.ts:635" when trying to click the follow button on a user (I use a plugin, obviously). If you see this message, then the issue is limited to following (or else at least doesn't affect posting).

2024-09-27 15:55:43 UTC

- reply

https://image.nostr.build/7eb7d725c4508f9c7eab30af73a116c95c52c78cfc141429e9e149b68161b173.jpg
(They didn't have numbers for 9/2024 yet so I used august)
https://data.bls.gov/cgi-bin/cpicalc.pl?cost1=66000&year1=202408&year2=202111

2024-09-23 17:48:03 UTC

- reply

3am, 6am, and 7am for me lmao

2024-09-23 17:36:11 UTC

- reply

Same, my brother eventually got an n64 but that was in the early 00s well after its EoL so our library is pretty weird.

2024-09-23 16:53:17 UTC

- reply

Really? I think pilotwings was a launch title (I remember being confused by it at a toys r us kiosk) and waverace might have been bundled at some point, but every friend with an n64 seemed to have it. I remember enjoying it.

2024-08-04 22:09:15 UTC

- reply

That sounds weird... but I'll give it a go lol

2024-08-04 21:59:30 UTC

We had some sprite left over from independence day and I watered it down with a lemon sparkling water. If it wasn't for the sugar I'd drink this every day.

2024-08-04 18:29:10 UTC

@nprofile…6yvm I swear you mentioned that there are only meant to be 100 NIPs at some point recently but I can't find the note anymore. Any idea? (Or maybe more useful, any idea where you heard that in the first place?)
@nprofile…g5cd ?

2024-08-02 18:34:22 UTC

- reply

Wait, I just noticed that's the 10 year minus 3 month instead of 10 year minus 2 year
https://fred.stlouisfed.org/series/T10Y2Y#
https://image.nostr.build/30fca047146ad8adda33d7ae588d36bed5b53d6510d34ec33ee6aade86c64b2d.png

2024-08-02 18:30:13 UTC

WOW, I didn't realize we were so strongly inverted, for so long... I just kind of assumed since the yield curve inversion had exited the news cycle that it had crossed back into positive territory...
https://image.nostr.build/355cd2631ace3a45512d343b56b60900aee05ab51c9e1acf8226d66854ab6eb5.jpg
Source: https://x.com/BobMurphyEcon/status/1819415480328757306

2024-07-25 04:25:11 UTC

- reply

Right during my daily meeting... maybe next time.
I need to harass some people into looking at NIP-96 and telling me if I'm crazy or not though.

2024-07-23 00:06:44 UTC

- reply

https://github.com/nostr-protocol/nips/issues/1376

2024-07-22 19:36:05 UTC

I can tell this issue on the nips repo is going to stagnate forever 😩

2024-07-22 18:44:40 UTC

So is Swan pining for the fjords or is this really (as they claim) cutting their activities they had expanded into, presumably leaving their "profitable" core intact?

2024-07-20 17:48:50 UTC

- reply

BTW if you're curious about the contradiction I'm seeing, I (try to) explain it here https://github.com/nostr-protocol/nips/issues/1376

2024-07-20 05:15:03 UTC

I just wasted nostr-tools' PR #420 on a duplicate
Icing on the cake of wasting hours debugging nostr-tools' nip96 support

2024-07-20 05:12:58 UTC

- reply

https://github.com/nbd-wtf/nostr-tools/pull/413 someone identified the fix 2 weeks ago and I spent quite a few hours to come to the same conclusion lol AGH

2024-07-15 16:13:42 UTC

- reply

Thanks! Don't worry about it for the moment, I will review coracle before I waste anybody else's time. Sorry for the noise!

2024-07-15 16:09:07 UTC

- reply

Hodlbod confirmed he's using nip-96 after all, so I can reference his code to figure out what's going wrong on my end. Don't waste your time reading this garbage until I've looked over his code lol

2024-07-15 16:02:59 UTC

- reply

Ah, you're using `file[]` as the form field? I thought I saw something to that effect in the nostr.build source, but afaict that's off spec? nostr-tools uses `file` and that was my reading of the spec as well.

2024-07-15 15:59:31 UTC

- reply

So you did... I'm not sure how I came to the opposite conclusion heh.
Thanks!

2024-07-15 15:56:05 UTC

- reply

OK I've created a simple sample page for making NIP-96 uploads the way I am in my larger project. I've also included a variation that generates the Auth header differently (according to NIP-96 where it contradicts NIP-98).
Not sure what I'm doing wrong here...
https://github.com/Ademan/nip96-test
You can run it with
```
npx webpack serve -c webpack.dev.js
```
the "My version" checkbox activates the variant upload, rather than only using stock nostr-tools functions.
@nprofile…v296 any ideas? To the extent I am able as a non-web dev who's very unfamiliar with modern PHP, reviewing the nostr.build source it wasn't obvious to me what is going wrong either.
@nprofile…lwv4 I get approximately the same 400 response with nostrcheck, does anything jump out at you?
I appreciate any help y'all can give, and sorry for the noise. At least, if you're aware of clients that work with your nip96 endpoints specifically, I'd love to see them and compare...

2024-07-15 14:59:47 UTC

- reply

What do/should be done when you have p2pks very near to expiring? It seems like you just end up reverting to the "worst case" of the recipient needing to immediately redeem tokens and/or senders needing to redeem them into new p2pks them before sending, which ends up putting load on the mint.
I suppose if users had the timelocks semi-randomly distributed, then only a subset of tokens would need to be urgently redeemed?

2024-07-13 22:18:05 UTC

- reply

This is something I was thinking about the other day when you talked about million TPS. Presumably, an end user won't want to lock a bunch of funds to a service provider with no option to reclaim unused ones.
Do you have thoughts on that? I suppose a timelocked alternate spending path would work, but that becomes troublesome if you have a bunch of timelocked tokens on the verge of expiration, too.

2024-07-13 22:14:26 UTC

- reply

Really bugs me how some people are picking fights with ecash pretending this is some dirty secret that ecash devs are hiding, considering how up front you are (and have always been) about it.

2024-07-13 19:08:10 UTC

- reply

*possibly* related, although I don't think so:
https://github.com/nostr-protocol/nips/blob/master/96.md says payload should be base64 encoded, but
https://github.com/nostr-protocol/nips/blob/master/98.md says the payload should be hex encoded
This seems to be contradictory?
nostr-tools uses the hex encoding, so if the server is expecting base64 that could be a problem, although like I said, I don't *think* these servers are processing the Auth header at all by the time they send me back a 400.
I'll at least try changing it to a base64 encoded payload hash once I get back from mowing the lawn...

2024-07-13 16:11:29 UTC

#nostrdev #asknostr #nostr-tools
I'm unable to complete nip96 uploads across nostrcheck, nostr.build, and files.v0l.io I suspect it's my fault somehow, but I'm burning more time than I'd like troubleshooting. I'm using nostr-tools and afaict based on reading nip-96, examining the nostr-tools code, and looking at the requests, I'm not certain what's wrong here.
Afaict the Authorization form field is non-standard but harmless (hacking it out did not change the responses I'm getting, and reading the void-cat-rs source it looks like it should be ignored anyway).
```
POST /n96 HTTP/2
Host: files.v0l.io
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:127.0) Gecko/20100101 Firefox/127.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br, zstd
Referer: http://localhost:5000/
Authorization: Nostr REDACTED
Content-Type: multipart/form-data
Content-Length: 24052
Origin: http://localhost:5000
Connection: keep-alive
Sec-Fetch-Dest: empty
Sec-Fetch-Mode: cors
Sec-Fetch-Site: cross-site
Priority: u=4
TE: trailers
-----------------------------11234029581503681683701650224
Content-Disposition: form-data; name="Authorization"
Nostr REDACTED
-----------------------------11234029581503681683701650224
Content-Disposition: form-data; name="size"
22933
-----------------------------11234029581503681683701650224
Content-Disposition: form-data; name="file"; filename="2024-07-06-152337_1000x175_scrot.png"
Content-Type: image/png
... snip ...
-----------------------------11234029581503681683701650224--
```
You can see from the size field that the file is quite small.
I get a 400 response from all three services. (Not a 401 or 403 or anything) I'm pretty sure I'm generating the authorization token correctly (also using nostr-tools) and I glanced at the nostr.build source code and I'm reasonably confident the response I'm getting back is generated before the auth header is checked.
Both nostr.build and nostrcheck have some kind of message indicating a problem with the file upload portion. (files.v0l.io gives me a generic 400 html response)
nostr.build example
```
'{"status":"error","message":"Either no file or more than one file posted. Only one file is expected."}'
```
I'm not a web guy so nothing is jumping out at me, but does anyone notice something obviously wrong with the request?

2024-07-13 16:03:59 UTC

- reply

This is indeed an alt I just created. Since I don't want to copy keys across multiple devices. I think whatever nsecbunker does would allow me to post from other devices but sign from my desktop? Anyway I haven't looked into it enough to understand, and this works well enough for the moment.

2024-07-11 17:10:02 UTC

What is the currently recommended RAM for a bitcoind node, both for initial block download and steady state? I'll be using -txindex and making infrequent RPC calls, if that affects it significantly.
I'm provisioning a VM on a home server for a new node, so I can always adjust later if need be.
#bitcoin #asknostr

2024-07-09 16:05:08 UTC

- reply

Ah shoot, missed that you're on vacation.
IGNORE ME

2024-07-08 22:02:58 UTC

@nprofile…gu24 why did you go with nostr.build's proprietary API instead of the nip96 one?

2024-07-08 02:31:59 UTC

#asknostr #nostrdev
does anyone successfully use the nostr.build nip96 endpoint?

2024-07-06 02:15:08 UTC

- reply

Have you considered any kind of affiliate program for authors of clients if their users sign up for your paid services? I'm sure every nostr dev out there is sitting there scratching their head going "how the heck do I monetize this?" and maybe that's an interesting option.
(Not applicable to my situation, of course, but for people who are building *serious* clients lol)

2024-07-05 04:33:01 UTC

@nprofile…7hl4 I'm working on a for-funsies nostr client that I'll probably abandon fairly quickly and I'd like to integrate nostr.build
If I actually release it, it'll be FOSS and free to use, but the nostr.build github made it sound like I should contact y'all before integrating it.
Happy to provide more details and/or a preview release if you want. (Give me some time to do some cleanup first in the latter case heh) Like I said in all likelihood I'm going to abandon this pretty quick anyway, but I want to be a good steward.

2024-06-30 21:00:19 UTC

- reply

I'm actually more interested in public groups too.
My question is just: Do you really need a NIP-29-aware relay at all, for public groups?

2024-06-30 20:13:49 UTC

- reply

Can't clients enforce the moderation rules? For public groups, where everyone can see the posts, you don't actually need relay cooperation do you?
A NIP-29 aware relay could restrict event delivery to group members, and provide some privacy, as a value add, though. I'm not sure how inclined I am to trust such a relay to never leak, and since nostr events are non-repudiable, all it takes is one mole to ruin privacy.

2024-06-29 18:56:13 UTC

- reply

An automated service that polls known relays periodically and logs some stats (age of the last N notes to estimate usage), logs unusable relays, and has a simple web frontend would be nice. Any additional diagnostics are a bonus but I'm sure people could come up with a bevy of them.

2024-06-28 19:53:39 UTC

Hey @nprofile…qmdu do you have any experience with https://en.wikipedia.org/wiki/Tithonia_diversifolia ? I'm trying to find a perennial to build a privacy barrier, and also to generate compost. (The flowers are a bonus as pollinator attraction)
The problem is, I'm in Zone 8a like you, where Tithonia supposedly will die off completely in hard freezes.
I was also interested in pigeon pea, since that can even be for human consumption, but the hard freeze is a problem with them too.

2024-06-27 14:47:24 UTC

@nprofile…5uux any thoughts on what a client should do with a kind 1 with NIP-92 metadata but which has no URLs in the body?
I'm inclined to treat them as "attachments" regardless. It makes the most sense for *my* purposes, but it also makes sense that many clients may just ignore them altogether (and therefore I should probably avoid creating such notes).

2024-06-27 04:04:20 UTC

- reply

Yet another time when typescript would have saved me over an hour of debugging.

2024-06-27 03:56:37 UTC

- reply

huzzah, success!

2024-06-26 18:51:16 UTC

- reply

Can't tell if I got my test client banned from nos.lol or if something's very wrong lol

2024-06-26 16:02:09 UTC

- reply

I need a private relay for testing lol

2024-06-26 15:51:36 UTC

Test
#test

2024-06-20 20:04:20 UTC

I feel like this has been done, but has anyone named a nostr client something like "Nosferatu"? #asknostr
If not I call dibs on "Nosbooratu"

2024-06-20 20:03:37 UTC

I feel like this has been done, but has anyone named a nostr client something like "Nosferatu"? If not I call dibs on "Nosbooratu"

2024-06-20 18:51:05 UTC

- reply

considering how productive you seem to be, I believe it, and I'm sure there's a time machine involved lol

2024-06-18 18:15:10 UTC

- reply

phy too, in case someone wants to snipe my LoRastr idea (because realistically I'll never get to it)

2024-06-18 18:12:48 UTC

- reply

But I got it right 🤨

2024-06-17 23:59:09 UTC

- reply

Is that 8:00 pacific, 10:00 central?