princess_J20

go/emacs/nostr/imap enthusiast

Public Key

npub1kw2e80mwn6ge338uhvaulj3w3lwyzaam8vwhkv4ycqatmufkv7nstt4wl9

NIP-05 Address

gnostr.fullmoons.art

Profile Code

nprofile1qqst89vnhahfayvccn7tkw70eghglhzpw7ank8tmx2jvqw4a7ymx0fcprdmhxue69uhhyetvv9ujuur0vd4k2arwdaehgu3wvdhk6qg5waehxw309aex2mrp0yhxgctdw4eju6t0qyxhwumn8ghj7mn0wvhxcmmv40wep2

Publishing to

relay.pocketnostr.com

relay.damus.io

nos.lol

Author Public Key

npub1kw2e80mwn6ge338uhvaulj3w3lwyzaam8vwhkv4ycqatmufkv7nstt4wl9

Show more details

Last Notes

2023-02-08 04:17:09 CET

- reply

what is filter.nostr.wine? I cannot seem to establish a websocket connection to it.

2023-02-08 02:22:48 CET

listening to: https://www.youtube.com/watch?v=MSho99GJl_w

2023-02-06 05:47:01 CET

- reply

lolz ty

2023-02-06 05:46:44 CET

- reply

forgot a nostr expert: #[1]

2023-02-06 05:44:55 CET

Q for nostr experts: if I open multiple subscriptions with REQ and a new event arrives at the relay which matches multiple of them, should the relay send the same event multiple times (one for each sub) or just pick one sub and send the event?

2023-02-06 05:10:31 CET

- reply

This GitHub issue is pretty funny. Some Grump wants to get rid of 418 in golang :P he gets wrecked in the emoji reactions though.
https://github.com/golang/go/issues/21326

2023-02-06 04:30:12 CET

- reply

🫖

2023-02-06 04:06:53 CET

- reply

beautiful

2023-02-06 03:47:08 CET

T.I.L. about HTTP Status Codes.
Status Code 200 = OK
Status Code 404 = Not Found
Status Code 418 = I'm a Teapot

2023-02-06 03:42:53 CET

- reply

ah that looks like it

2023-02-04 17:39:33 CET

- reply

1Q84

2023-02-03 17:12:04 CET

- reply

nice npub

2023-02-03 06:27:52 CET

- reply

was looking through
https://nostr.watch/relays/find
but it's a bit time consuming and could not find any after checking a few...

2023-02-03 06:26:09 CET

anyone running the strfry relay (besides nos.lol)? send URLs my way please :)

2023-02-03 05:36:38 CET

- reply

more reading https://github.com/hoytech/quadrable
interesting stuff...

2023-02-03 05:24:42 CET

reading https://github.com/hoytech/strfry seems like a pretty efficient relay.

2023-02-03 04:54:36 CET

- reply

Thanks to #[0] for setting up wss://nostr.wine!

2023-02-03 04:28:11 CET

- reply

One idea: on initialization, clients try to open up websockets to a collection of relays. whichever ones successfully establish a connection are published as a parametrized replaceable event with a fixed Kind "K", with "d" tags equal to the URL of the relay. These events ideally would be "sprayed".
Then, as another user, I could query for kind "K" authored by the user I am interested and get the list of relays, with timestamps, they have connected to. By filtering the query I can get the most recent relays, etc.
Obvious privacy concerns. But a good client could prompt user before sending (i.e., "let people know you were using relay wss://XXX"?), and maybe you could set to not send such updates for certain relays.. etc..

2023-01-30 07:44:53 CET

- reply

RIP HashCash

2023-01-29 20:33:54 CET

- reply

perhaps there should be a timestamp component to the nprofile QR code, in case clients accidentally scan old QR codes with outdated relay info

2023-01-29 18:28:03 CET

- reply

pretty fancy haha. seems like it is rendering the full javascript and then post-processing that to characters it can pass to the terminal, similar to https://github.com/browsh-org/browsh

2023-01-26 05:53:16 CET

- reply

nice work, must have been a fun project setting that up

2023-01-26 04:23:05 CET

- reply

haha nice :P

2023-01-26 04:21:23 CET

- reply

I am proud to say that I beat peasant's quest back in the day

2023-01-25 18:26:32 CET

- reply

I guess the point is to keep the notes human readable? what about super long URLs linking to images? those often make the text content annoying to look at... I guess "all" clients agree to render those URLs as images...

2023-01-24 05:08:44 CET

- reply

yeah good point

2023-01-24 04:54:02 CET

- reply

see the proposal: https://github.com/nostr-protocol/nips/pull/158 there has been lots of discussion in other pull requests and issues. seems to be quite the contentious issue :P

2023-01-22 01:34:50 CET

- reply

lolz

2023-01-21 23:38:24 CET

- reply

nice!

2023-01-20 04:46:52 CET

- reply

gitcoin

2023-01-16 03:44:06 CET

- reply

pretty fun blog post to read BTW by #[5] cuts through the hype

2023-01-16 03:36:44 CET

- reply

from IPFS: https://fiatjaf.com/d5031e5b.html #[5]

2023-01-16 03:36:15 CET

- reply

https://cloudflare-ipfs.com/ipfs/QmckaDfTCikHvTGxDGRXbUMFoLkCTkHA2z9nRF2ibdYKun/candlesticks.png
image file for DL

2023-01-16 03:34:43 CET

- reply

lnbc810n1p3ufdaapp5flmrg3dmt5snwesl9l4yev9kunkcd949ppgyq8d736wm8nqnp5ksdq5g9kxy7fqd9h8vmmfvdjscqzpgxqyz5vqsp5kgdx9p3fxexg7sqgx0g9hz0h5sye4shclxnfjwsqsgjhu07j40ss9qyyssqrtc5agx8myavy7ufcnpmtth2njelrr45tu5jhqhgf565mjx6fxr8jjlly6fqun7ymnfhmu4cjk43qnlcwpp2gr9kmspzy328524rwmcq3mr2u0

2023-01-15 22:20:43 CET

- reply

exactly! just open an incognito tab

2023-01-15 22:17:04 CET

- reply

it is possible to make whitelisted relays, and these could be used to aggregate well-known users in the nostr-verse. then you only need to add that one relay (or a relay which syncs with it) to essentially follow all the whitelisted users.

2023-01-15 04:22:34 CET

- reply

ye one of my favorite thing about nostr is that it open sources the backend so people can make their own curation algorithms. will be exciting to see how the ecosystem evolves w/ time

2023-01-13 06:44:53 CET

- reply

except for Nostr of course

2023-01-13 00:23:43 CET

- reply

🧠