degmods/degmods.com
6
1
Fork 0
Code Issues 31 Pull Requests Actions Packages Projects 3 Releases Wiki Activity

Only a few mods are being fetched/presented #238

New Issue
Closed
opened 2025-03-04 17:19:14 +00:00 by freakoverse · 1 comment
freakoverse commented 2025-03-04 17:19:14 +00:00
Owner
Copy Link

For some reason, which may be as a result of the from/since filtering on the /mods (maybe on landing page too), only about/around 20 mods are being fetched from a relay (or relays), even though there are around 150 to 200+ mods.

Probably the same issue over at blogs?

For some reason, which may be as a result of the from/since filtering on the /mods (maybe on landing page too), only about/around 20 mods are being fetched from a relay (or relays), even though there are around 150 to 200+ mods. Probably the same issue over at blogs?
freakoverse added the
Kind/Bug
Priority
High
 labels 2025-03-04 17:19:14 +00:00
freakoverse added this to the Issues project 2025-03-04 17:19:14 +00:00
freakoverse moved this to In Progress in Issues on 2025-03-04 17:19:17 +00:00
enes closed this issue 2025-03-11 14:45:31 +00:00
freakoverse moved this to Done in Issues on 2025-03-11 15:23:38 +00:00
freakoverse commented 2025-03-11 15:26:48 +00:00
Author
Owner
Copy Link

issue is would still be there with the current setup, so the solution-ish that we went with is to replace pagination with 'load more' and have a subscribe function to keep loading in events as they're discovered. This decreases the chances of missed events, but because of the NDK caching issue with dates, it might show a huge chunk of events instead of showing the limit (basically the issue now is that it's messy =P). So that's the current fix, and the messy bit will be band aided with the server/dvm that'll be implemented.

issue is would still be there with the current setup, so the solution-ish that we went with is to replace pagination with 'load more' and have a subscribe function to keep loading in events as they're discovered. This decreases the chances of missed events, but because of the NDK caching issue with dates, it might show a huge chunk of events instead of showing the limit (basically the issue now is that it's messy =P). So that's the current fix, and the messy bit will be band aided with the server/dvm that'll be implemented.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Bug
Priority
High
Milestone
No items
No Milestone
Projects
Clear projects
No project Issues
Assignees
Clear assignees
b endo enes eugene freakoverse m s y
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: degmods/degmods.com#238
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?