Description
Is your feature request related to a problem? Please describe.
I want to have more control over my timeline .
The problem is similar to #14872
.
Describe the solution you'd like
I want to tell Grok what kind of stuff do I want to see on my timeline on the short run (instantly) or on the long term and it reflects on my timeline i e "For You" as per my wishes including time based algorithmic shifts .
This approach is more libertarian giving users the choice more over the algorithm and content they interact with .
Additional context
I guess whenever this feature is rolled out , it will be in huge demand and therefore X can go with giving users a limited number of tokens for injections per day or per month or for some premium users as per business requirements however reversals should not cost tokens .
I hope my want is clear enough though the implementation may require you to put effort into it .
Demo
- Me to Grok : I don't want to see content from American political commentators or content that discusses American politics.
Now , Grok should clarify all doubts before proceeding with the injection. Like :-
Grok : So do you want to see no content that discusses American politics. What about if American politics is a reference and not a central theme in particular posts . What would you like for such posts ?
A chain of clarification before injection would improve algorithm recommendation multifold .
-
Me to Grok : I want to see more content from people who are writing Frontend code in public and posting on the platform . I am learning Spring Boot framework so I don't want other kinds of frontend like MERN or PHP.
-
Me to Grok : When I wake up in the morning and open X , I want to see positive stuff that ensures I am in a good mood and have a productive day . I do not want to see negative stuff on my timeline in morning hours . Morning's the time of refreshment , fresh air and therefore I want to see lovely and positive posts . Also posts that are resourceful and sparks curiosity within me towards learning stuff (definitely not random but towards the stuff I like which you know) .
I hope the above demonstrations are clear and the engineering team can definitely think of more use cases and types of requests that may arise .