Load More to use a count, not a time range #621
Labels
No labels
Blocked
Bug
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Idea
In progress
Invalid
Major feature set
Packaging
Question
Soon
UI/UX
Upstream
You're dreamin'
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nostr/gossip#621
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I really would like this 😬 Some of my custom lists only have 3 entries because they are low frequency posters.
Also, once the scroll hits the bottom we can automatically load more, we don't need a button.
Notes to myself:
I may do this:
I have replaced the old indexes:
ek_pk(keys are kind+author, values are dup ids)ek_c(keys are kind+created_at values are dup ids)With new indexes
akci(keys are author+kind+createdat+id, values are null)kci(keys are kind+createdat+id. values are null)Based on experience with chorus and analysis of usage in gossip.
This allowed me to write a "find_event_by_filter" function that respects since, until and limit. Because the indexing is incomplete, we cannot search by any tag, and we cannot search by any kind, nor can we search by ids (use events directly for that), but we can search for everything we need and especially with regard to this issue, we can use limits now.
this was done a week or so ago.