Post ASiJdF5bbBZktz9xUe by ge0rg@chaos.social
 (DIR) More posts by ge0rg@chaos.social
 (DIR) Post #ASiDb89rnZvB6JlLMW by ge0rg@chaos.social
       2023-02-15T18:06:02Z
       
       0 likes, 0 repeats
       
       How can I radically deduplicate my timeline, using @apps? #FediHelpI enabled "group boosts" (in app and on server), but it's not enough. I don't want to see...📋...boosts of posts/boosts that were in my timeline📋...my own boosts of posts/boosts from my timeline📋...re-boosts by the original author to get more engagement📋...posts that I've seen with any other account in the appI'm reading my timeline and I only ever want to see a post once. Repeating after a few weeks is tolerable.
       
 (DIR) Post #ASiDbAD8APijT1IyjA by apps@toot.fedilab.app
       2023-02-15T18:39:09Z
       
       0 likes, 0 repeats
       
       @ge0rg Only solution is to hide boosts. Long press the home tab and uncheck "Show boosts".
       
 (DIR) Post #ASiERoztli8r1TE0tk by ge0rg@chaos.social
       2023-02-15T18:48:34Z
       
       0 likes, 0 repeats
       
       @apps will that hide all boosts, even for posts that originally weren't on my timeline?
       
 (DIR) Post #ASiFFKsxzujm6zapJg by apps@toot.fedilab.app
       2023-02-15T18:57:57Z
       
       0 likes, 0 repeats
       
       @ge0rg It will hide all boosts in your home timeline.
       
 (DIR) Post #ASiFpeTIeeIzHWu7xw by ge0rg@chaos.social
       2023-02-15T19:04:13Z
       
       0 likes, 0 repeats
       
       @appsBut that's not a solution then because it will hide all content from people I don't follow. I only want to hide duplicates... 🤷
       
 (DIR) Post #ASiH99aRIFQ7Ew6g7s by apps@toot.fedilab.app
       2023-02-15T19:19:02Z
       
       0 likes, 0 repeats
       
       @ge0rg Ok. The best we can do is to extend the "group reblogs" to the whole timeline (current visible messages).That will not cover the case "I already see a similar boost few hours ago".Because a such feature would need for each boost a dB call to check if the reference ID already exists in cache (ie: supposed to have already been read, which is impossible to say with the automatic cache feature). So it's not so simple.
       
 (DIR) Post #ASiJdF5bbBZktz9xUe by ge0rg@chaos.social
       2023-02-15T19:46:23Z
       
       0 likes, 0 repeats
       
       @appsI'd have imagined a table of (ID, seen-timestamp), with the ID indexed, and one could cross check it on fetch from server or when fetching the data for UI. A cleanup job could remove everything older than X days...