Avatar
hodlbod
97c70a44366a6535c145b333f973ea86dfdc2d7a99da618c40c64705ad98e322
Christian Bitcoiner and developer of coracle.social. Learn more at info.coracle.social. If you can't tell the difference between me and a scammer, use a nostr client with web of trust support.

An awesome client, hadn't heard of it until yesterday

Kiwi browser lets you install extensions. I've had more success with flamingo on mobile though.

Replying to Avatar hodlbod

nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcprpmhxue69uhhyetvv9ujucm4wfex2mn59en8j6f0qyghwumn8ghj7mn0wd68ytnhd9hx2tce33z4j I was just talking to nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszyrhwden5te0wdhkcmmrduhxump0c6w75y about the OAuth stuff. You had mentioned a vulnerability where an impostor client could hijack another client's session by authenticating with the same client id. I looked briefly at OpenID Connect's dynamic discovery mechanism, and it looks like you get a shared secret at registration. We have keys though, do you think it would make sense to have a client sign an authentication request using the same key they used to publish a NIP 89 app listing?

Or, would it make sense to just re-authenticate every time you wanted to log in, without identifying the client? Pablo proposed this and I don't see any need for a client to self-identify or maintain a persistent session with the authentication provider, other than a bunker key.

nostr:nprofile1qqsrxra3gv0lnkxz2pcxh0xuq9k4f9dr7azwq3aypqtnay4w0mjzmtqpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcprpmhxue69uhhyetvv9ujucm4wfex2mn59en8j6f0qyghwumn8ghj7mn0wd68ytnhd9hx2tce33z4j I was just talking to nostr:nprofile1qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszyrhwden5te0wdhkcmmrduhxump0c6w75y about the OAuth stuff. You had mentioned a vulnerability where an impostor client could hijack another client's session by authenticating with the same client id. I looked briefly at OpenID Connect's dynamic discovery mechanism, and it looks like you get a shared secret at registration. We have keys though, do you think it would make sense to have a client sign an authentication request using the same key they used to publish a NIP 89 app listing?

Woww incredible shots. I have a film camera but have never really learned how to use it. Motivated to pick it back up now!

Great book, even better cover

Ok, you got me, memories exist metaphysically, but not corporeally

Gossip is a terrible misnomer. Inbox/outbox model is almost as bad. A better name would be the "routing model"

Added that to coracle recently, it's definitely helpful. What's the status of gossip in Damus?

I don't know, a limit of >100 seems ok to me, it really does drain your battery on mobile

Very true, relay proxies or some other server-side commodity solution is needed to straighten this out.

LORD, HIGH AND HOLY, MEEK AND LOWLY,

Thou hast brought me to the valley of vision,

where I live in the depths but see thee in the heights;

hemmed in by mountains of sin I behold thy glory.

Let me learn by paradox

that the way down is the way up,

that to be low is to be high,

that the broken heart is the healed heart,

that the contrite spirit is the rejoicing spirit,

that the repenting soul is the victorious soul,

that to have nothing is to possess all,

that to bear the cross is to wear the crown,

that to give is to receive,

that the valley is the place of vision.

Lord, in the daytime stars can be seen from deepest wells,

and the deeper the wells the brighter thy stars shine;

Let me find thy light in my darkness,

thy life in my death,

thy joy in my sorrow,

thy grace in my sin,

thy riches in my poverty

thy glory in my valley.

https://vmars.us/reads/the-valley-of-vision-A-book-of-Puritan-prayers.pdf