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.

Forget tobacco, nothing smells better than a newly struck match

nostr:nprofile1qqsdjyv3uv8qq3ztjskqaqk263ctx2h3w9mycgn4hmstmxfh0m75qag26at7q congrats on your sweariest episode to date. Named data networking is an interesting idea, but I feel like tor+nostr is basically what Stewart described. What's missing?

Coracle does heterogenous lists instead, kind 30001 I think with t tags alongside p tags.

Replying to Avatar jb55

Sometimes when I’m in the thick of building things I forget the grander implications of the tools I’m putting out there. Thank you nostr:npub1lelkh3hhxw9hdwlcpk6q9t0xt9f7yze0y0nxazvzqjmre3p98x3sthkvyz for reminding me of that. I need to make damus more decentralized and make it better at communicating with different relays.

A good mental model for this is that right now damus CCs every relay you’re connected to. Once its easier to CC specific relays then lots of new use cases pop up.

Maybe this should be more apparent in the UI, and less mass-CCing everything.

This is in the same territory as the gossip model, but the UX story is still evading me.

Coracle and flycat both have some original patterns for relay management

I'll have to read up more on that, skunks definitely seem like a threat around here but it would be a shame if I were damaging the ecosystem

Replying to Avatar fiatjaf

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn have you thought about caching stuff locally and exposing that cache as a relay interface, so you can just seamlessly plug it in all other parts of the https://coracle.social/ code that connects to relays? Is this a bad idea?

I have thought about it, non-server relays ingeneral are a good idea