It's indeed way faster, but it shows only a fraction of posts. For instance I don't see any mostr.pub (activitypub gateway) posts, even though all my relays are connected.
After just over a month of no updates, Coracle 0.3.0 is now available! To give you an idea of why it took so long, here's the diff summary:
> 166 files changed, 6718 insertions(+), 5118 deletions(-)
The entire fetching layer has once again been rewritten, resulting in faster and more complete data everywhere, particularly feeds. I hope to open source around 3k lines of this goodness after some further refinement.
Navigation has also had a refresh, thanks to nostr:nprofile1qqs9c5yvxn6csehvwdq64ugvcxh496fr9wulskwgzq72tm8j42fm77qpzpmhxue69uhkummnw3ezuamfdejszxthwden5te0dehhxarj9ejx2cm9de6x7mne9e3k7mgprpmhxue69uhkummnw3ez6am0wfkxgtngxdazu6nshkdpzv et al's feedback in a nest last week. You can now see your profile in the header, and search/scan are available right there without having to visit a new page.
I also managed to finally re-build Coracle's app store around NIP-89, including recommendations from your social graph.
Note publishing also gives you more information about which relays accepted the note, with a retry button if publishing fails. NIP 05 "verification" has been removed, instead showing follow status.
Chat and DMs have had some love as well, including better new message notifications, and image uploads. You can also add more than one image to regular notes as well.
One of my favorite new features is the optional "thread" view which you can open from a deep reply. This will trace the thread from that note back to the root and show all ancestors without nesting.
For the full changelog, see below:
- [x] Faster login and initial load
- [x] Faster and more complete feed loading
- [x] More bandwidth-sensitive notifications fetching
- [x] Fewer missing profile badges
- [x] Use NIP 89 for app recommendations
- [x] Add support for kinds filter in advanced search
- [x] Add support for displaying kinds 0, 3, 10002
- [x] Add detailed summary of relays a note was published to
- [x] Emphasize follow status instead of nip05 addresses
- [x] Add image uploads to chat
- [x] Add new thread view
- [x] Removed profile popover, click on a person's name to find mute and follow buttons
- [x] Add configurable imgproxy url
- [x] Show hover state on icon buttons
- [x] Re-work navigation, put search in nav
- [x] Add word count to new note
- [x] Add support for attaching multiple images to a note
- [x] Fix note parsing when parentheses are involved
- [x] Fix person detail layout on small screens
- [x] Fix chat/dm header
- [x] Fix lots of bugs
Thanks for sticking with me! Let me know if you run into any problems, you can message me on nostr, or you can file an issue at github.com/coracle-social/coracle.
Discussion
Coracle semi-randomly selects relays from people you follow in order to conserve resources. You can try increasing the "Max relays per request" setting to cast a wider net, but setting it too high may lead to flakiness. Coracle also doesn't query all followers for a large follow list. This is something I'm hoping to address soon. Let me know if the relay limit improves things!
Thanks for your answer! If I increase max relays, some posts change. I still can't see posts from my own relay (nostr.data.haus), which has some unique posts from a RSS gateway.
Any way to just use my own relays?
Not at the moment, but I have thought about adding the option. I'll look at adding that.
This is interesting, I assume nostr.data.haus has content you want to see, but not published by pubkeys you follow? The main feed goes by pubkey of your follows list, so it would make sense to miss out on relay-based feeds. To overcome this you might create a list with the relays you want to read from "globally" (i.e. without filters)
I've just released a fix for a bug that was preventing replies from people you follow to people you don't from showing up. This should help a lot, but the specific behavior you mention is still an interesting problem.
thank you for this explanation!