You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 filterwarn
orhide
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 thewarn
filter. skip those posts having ahide
filter. In this way, we will have 20 posts in the API that can be visible to the user. If theexclude_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
The text was updated successfully, but these errors were encountered: