Skip to content
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

Regarding the Filtered Post in the Timeline Apis #30228

Open
gowtham18k opened this issue May 9, 2024 · 0 comments
Open

Regarding the Filtered Post in the Timeline Apis #30228

gowtham18k opened this issue May 9, 2024 · 0 comments
Labels
suggestion Feature suggestion

Comments

@gowtham18k
Copy link

gowtham18k commented May 9, 2024

Pitch

Currently, if a post is filtered we have the filter details in the new field of the post response as filtered. Based on the type of the filter warn or hide we are handling it in the client based on the type. But here the problem is I have created a filter that hides the post. in one particular hashtag I have filtered 20 posts in the client API has been called and It returns a response with 20 post details. but in the client, I'm able to see only the load more button. So my suggestion is to send the post in the API with the warn filter. skip those posts having a hide filter. In this way, we will have 20 posts in the API that can be visible to the user. If the exclude_filters feature is given for the timeline API that will also work for the above scenario.

Motivation

As I mentioned in the details above Users will not have to see the load more button in the initial state itself. we can able to build customized features on top of that. For example, we can bring the read recipient feature also. It will improve user interaction in the application

@gowtham18k gowtham18k added the suggestion Feature suggestion label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
suggestion Feature suggestion
Projects
None yet
Development

No branches or pull requests

1 participant