Allow viewing and editing beyond the latest 30 posts

[vickychijwani]

Pagination needs to be implemented. When the user scrolls down to the bottom, the next page of posts should be fetched and displayed. Linked: #102.

The API for pagination is going to be changed soon in an upcoming Ghost release, probably should wait for it. Relevant Ghost issue: TryGhost/Ghost#5463.

[vickychijwani]

The big problem with implementing pagination is what to do about cached posts that are deleted from the server.

• If we no longer fetch all posts from the server, we don't know what's been deleted in the first place
  • One might think this can be worked around by making an API call to check the existence of each post that may have been deleted. However, if fetching a single page with 15-20 posts, all other posts (perhaps in the hundreds) may have been deleted.
  • Maybe instead we perform these existence checks only very rarely, like once a week or once a month?
• Also, what about posts beyond the first page that are already cached? When and how will they be updated? Because the current idea is to always fetch the first page of posts on app start / resume, plus any new pages when the user scrolls to the bottom

[danhunsaker]

If it were me, I'd check the cached posts periodically (x days after last caching), and also include a menu option or button of some kind to manually refresh the cache. Additionally, when a cached post is opened, I'm pretty sure it would already trigger a check against the live blog at that point, but that's another point I'd check at.

[Memphizzz]

Needed as I currently only see my drafts...

[Memphizzz]

For real guys? This is an open issue since June 29 2015(!!). Come on!

[gldraphael]

One improvement would be to show draft posts + the first x posts. Or better still, feature a toggle to hide drafts from the list.

The reason is the same as @memphizz, all I see are draft posts. And without search, it makes it impossible to fix typos to recently published posts from within the app.

[Memphizzz]

Well, no response, nothing. Can we assume development is dead on this issue?

[vickychijwani]

@Memphizzz I still work on this app, but you need to understand that I'm doing it in my free time. I have a separate, completely unrelated, full-time job too.

I realize that this is a big issue for some people (that's why I went to the effort of linking to it from the app in the first place - to guage how many users actually run into this issue), but I have nothing more to add at the moment. I see no point in spamming everyone subscribed to this issue unless I have something meaningful to say.