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

Endpoint for last read toot #7418

lamnatos opened this issue May 8, 2018 · 8 comments · Fixed by #11762


Copy link

commented May 8, 2018

(Somewhat similar idea to #4093)

It would be nice to have a synced timeline across clients (web or not) connected to an instance. This functionality suggestion is directly inspired by the (discontinued) Tweet Marker 3rd party service for Twitter.

It would allow clients to set & get the last viewed toot on the instance itself, thus allowing them to know where to continue from when displaying the timeline. When using multiple clients it would make switching between them easier since each of the clients could show the same point in the instance's timeline.

I cannot give implementation suggestions but maybe the Tweet Marker API description could be a helpful starting point.

  • I searched or browsed the repo’s other issues to ensure this is not a duplicate.

This comment has been minimized.

Copy link

commented Jun 14, 2018

I think this is a huge quality-of-life improvement. Reading my TL goes like this.

  • Press Home to make sure my TL is up to date
  • scroll backwards until I recognize a toot
  • read forwards

I would like to be able to open any of my clients and the TL is pinned to the last toot I "read" and then I just scroll forward in time to catch up.


This comment has been minimized.

Copy link

commented Aug 20, 2018

@foozmeat Exactly my current "workflow" with Mastodon apps. I feel like an animal...


This comment has been minimized.

Copy link

commented Aug 20, 2018

I second this proposal as well. It's the one big thing I'm missing from my Twitterrific/Twitter set-up. Compared to Twitter, implementing it in the backend also would have the advantage that it would work across different clients.


This comment has been minimized.

Copy link

commented Sep 2, 2018

I would love to start contributing to Mastodon and work on this ticket. @Gargron how do I proceed? Should I write down an api proposal in this ticket and start the discussion with that here?


This comment has been minimized.

Copy link

commented Nov 26, 2018

Just wanted to chime in to say that this is the only thing keeping me from switching to Mastadon. I've listened to a few Mastadon podcasts explaining the need and purpose, and I'm totally on board. Tweet Marker / last-read-sync is just too critical to my workflow though.


This comment has been minimized.

Copy link

commented Jan 30, 2019

As someone who uses Mastodon on multiple devices and with multiple apps, the lack of syncing of my timeline positions is the biggest usability issue I have. Every time I go back to Mastodon, I start reading and then realize I've read this before and have to keep scrolling until I'm fairly certain I haven't read those. Some clients always show you the latest posts (hello web) so I have to scroll down to find where I was. With some other clients (I use Toot a lot lately) I have to scroll up.

The point is, some people want to make sure they've read everything, others want to make sure they're not wasting their time rereading posts they've scanned before. Either way, timeline syncing would be the ideal solution.

Since all (most?) Mastodon clients are currently single-platform, it doesn’t help if one app implements timeline syncing. Having it built into the API so all clients can benefit and we can get syncing across apps would solve this problem perfectly.

One think to keep in mind is that Mastodon has multiple timelines so ideally each one would have its own sync marker.


This comment has been minimized.

Copy link

commented Feb 3, 2019

Recent thread on this (for a few more +1):


This comment has been minimized.

Copy link

commented Apr 18, 2019

Well, that's the ONLY reason I haven't switched from Twitter (and AWESOME Tweetbot with tweet marker) to Mastodon.

Have there any design discussions / decision been made? I think I would be able to devote some of my time to implementing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
10 participants
You can’t perform that action at this time.