-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paginated inbox #163
Comments
Yeah also depends on #152 |
Pagination is important because if the JSONLD object grows too much we'll hit response limits. If we keep pending activities on the first page you could be DDOSed by just receiving too many activities. Maybe always paginate and have another collection for pending activities, so it's also explicit. |
|
@RangerMauve does this mean we can paginate the inbox via url params? also for fetching approved or pending separately? |
We don't have approved or not tracked yet but we could add that as a next step for indexing if that'd help. |
hey @RangerMauve, i'm not fully understanding this part:
what does it mean to delete an activity? in general, can you reexplain this point? |
Ah by "deleting an activity" I just meant to add some code inside In addition to deleting the activity from the store we also need to clean up any indexes referencing it. |
Generally whenever you add any data to a store you should have an api for removing the data from it. |
We need to add tests - @RangerMauve could take this on |
Nula and/or Agus to work on this. They should do an estimate for this task and let us know, so we an put it in the roadmap
Just an idea we can discuss later. I don't remember now if the inbox could be paginated, but if it is, the first page could always be pending activities and later pages activities that have been approved (and can be rejected at any time)
The text was updated successfully, but these errors were encountered: