Technically the protocol relies on websockets, but it would be very easy to come up with another transport mechanism, including p2p, tor relays, jsonl exports/imports, and more. The client-controlled replication is what is key, and might be harder to pull off if you stepped away from the more conventional relay architecture, but not really difgicult. You would probably need adapters to abstract away multiple implementations of a general purpose relay interface.
Just hit 10k lines of code on Coracle. I'm doing a refactor which is desperately needed (I didn't realize how snarled my code was until I started). It'll pump the line count up a bit because of boilerplate, but it's going to be so much easier to maintain.
Interesting, thanks for the extra information, I'll look into it
In Coracle, go to Reviews > Browse Relays and you'll see a feed of reviews
Shout out to npub1qn49n06hdwwyrtvdyymu2wx57jvhz7anmu20tgsdjjyae3zhwaxsjtl6rj who has reviewed a bunch of relays, thanks for helping de-commodify nostr infrastructure!
Is there a web client that is fully usable with TOR?
Iris dosn't let me follow.
Snort dosn't load anything.
Coracle loads the feed and let me follow but only after searching for a user, follow/post/dm buttons are missing and the messages area is disabled.
Tested on macOS both with TOR browser and Firefox + TOR.
Alternatives or tricks?
/cc nostr:npub16yh7kd9nacfqggacrrxcmkj8qqrrnwlvnfhwd5e3065gdmzmpp8syusv37 nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
Did you log in to Coracle? That could explain the grayed out/missing buttons. Otherwise, Coracle seems to be working ok on Tor for me.
I'd like to learn more about this. Both Coracle and Primal apparently showed a red warning page to some users because of nos.re. I'm not sure how it was triggered, whether by a link href, image src, background image src, or something else, but I want to be sure Coracle doesn't have any injection vulnerabilities. I've audited the code and don't see anything suspicious, just want to be extra sure.
note19j3s8vg2q06nkxpd4xpdxhupl3a2mvr0pw8az7hf29kam2hcp2jqswpfqr
note1p566r9j6jhlzj83kxyha8dlka7lv6evaaglpedrlp8s0va7f8tmq32xelr
Recursive parameterized slot forwarding 😵💫
Sounds like a bug, have you tried logging out/in? Is this just on the main feed page?
?width=673&height=673
It ain't much, but it's honest work
Iris, Snort, Primal.
- Better onboarding (although not relevant for switching)
- First-class relays (although relays currently are commoditized and no one cares)
- Better threads, feed control, lists, overlays to drill down and stay oriented (all matters of taste)
I can think of lots of reasons you wouldn't want to use Coracle too 🤷♂️
That's so funny, why were you there?
On Coracle I have no problem fetching the data from relays, the glitch seems on the client side, maybe related to indexdb/API storage.
On Coracle from the inspector I can see some "Cross-Origin Request Blocked" related to the NIP-05 verification, nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn perhaps this error is not properly caught and breaks the profile / dm buttons?
Cors is a common error, the problem may be with firefox's rendering. It's time I revisited browser testing