@hartlco @vincent @manton Now that I have an abundance of micro.blog clients on my phone, I really need a TweetMarker-like solution on MicroBlog.

Anyone here know someone who could build something like that? 🤞

@stevesnider @hartlco @vincent 🙂 I think we need to roll out an API that can be used in third-party apps first and later the official app, when it is updated to remember the timeline position.

@manton @stevesnider I’m up for that. @Burk hinted I should add it as a feature... 😋

@vincent Resist building a server API for this yourself. I did that for Twitter and do not recommend it. 🙂

@vincent Agree with @manton. At the very least, make the tip jar first! I know not everything should be about money but if you are making a server API then you should be bloody well paid for it.

@vincent a big reason I've leaned towards Icro so far has been that it has maintained my timeline position. Gluon is amazing by the way.

@vincent I can understand that. I used to be a Twitter completionist, but have long since given that up. On Micro.blog I can still keep up (easily) just based on the number of people and the volume of posts, so I try to read them all when I can.

@simonwoods @vincent Just to underscore this... Don't build a server API because it will fragment the API, making it harder to build apps. For Gluon-only timeline sync now, there's iCloud.

@vincent @manton Wow, I never would have thought of that -- the things I learn everyday! I now entirely agree with Manton.

@manton @simonwoods @stevesnider Yeah, I was talking about just the Timeline within Gluon, and on device only. The timeline scrolls to the top if you’re at the upper most post... so I’d like to change that to stay where it is when new posts come in.

iCloud is an option across devices for Apple stuff for sure (but not across platform).

Anyway, I don’t want to build any API for that - as you say. If I did write an API I would let anyone use it. Same with the image proxy I am testing, doesn’t have to be Gluon only.

Agree with Simon though... tip jar 😃

@vincent I use and prefer gluon when I'm in and out of mb. But Icro seems able to backfill more when I've been away for a day. I would really love a client agnostic API so I can bounce between clients :)

@jpayne hey John. Thanks. I know what you mean with the backfill. The way it works in Gluon is that I keep your timeline stored locally (so it’s super fast when the app starts again from cold). If you’re away for a day and there are many posts, for example 100 posts, I can’t get that amount of posts back from the API.

Even though I say “this is the last post ID and give me back everything after that” - I would only get back 40 from the API... not 100.

Other client apps don’t seem to keep it in memory for long, so it basically just loads a fresh set (starts from scratch), and when you scroll down it will again load a fresh set of past posts. Hence you see them. (That’s my understanding anyway).

Saying that I’m working on making that better for Gluon somehow with a new sync engine.

For the record, I won’t make an API for syncing timelines. That’s a job for Manton @manton at some stage hehe. He’s got experience with that 😅🙃

@vincent Yep. So we also need @manton to support more posts in the backfill when he does the timeline position API, right? :)

@jpayne more posts for backfill would be good, yeah 😊

@jpayne @vincent That "40 posts" sounds familiar but it must be a bug. It is supposed to support paging back through at least a few days worth of posts.

@stevesnider This is also why I generally use Icro. It does a good job of position holding.

@stevesnider I would love to use a Micro.blog API for that 😁

@manton @hartlco Yup. Happens to me too on Gluon. Think I mentioned it to @vincent last week. It would help to have mb backfill more than 40 posts.

@manton that sounds promising :)