0.19 supports both page and page_cursor. We will probably get rid of page in 0.20.
The one on join-lemmy.org or in the docs is not straightforward?
In this case the problem is that I don't have any idea how this could work in terms of federation. For users and communities it is done via webfinger, but I don't think it would make sense to implement webfinger for posts.
One solution suggested in the issue is to try and resolve all links in the post/comment text, and rewrite them to the local domain. That should work though it seems tricky to parse and replace links.
Yes afaik all the known problems with 2FA are fixed. It would be helpful if you test it on voyager.lemmy.ml to see if it works. Though it's possible that lemmy-ui isn't compatible yet with new 2FA api, not sure.
In this case it would be too complicated to keep supporting the old auth format. Plus we want clients to update soon because sending auth parameters in the url is not secure. Anyway clients can support 0.18 and 0.19 at the same time by sending both old and new auth params at the same time.
No one lives forever. Though the originals are still very much playable, only the graphics are outdated.
I am certainly open to implementing specific backend features in return for payment. You can send me a private message on Matrix to discuss the details.
The post only includes pull requests which were active last week. Scaled sort was already completed earlier. It will definitely go into the next release, like every merged PR.
When we are ready to publish the first release candidate, we will make a post that lists all the breaking changes. You can follow !announcements@lemmy.ml via rss reader to get notified about it. We will also share it in different Matrix chats, and I'm sure it will get upvoted to the frontpage as well.
Before 1.0 we definitely need to do an API cleanup, the paths are a real mess. However that will require lots of breaking changes so Im not sure when we can do it.
In case of pagination both old and new variants are supported in 0.19 (see my reply to fmstrat above). TOTP is currently broken so it wouldnt make sense to keep supporting the old version. In case of auth it would be possible to keep backwards compat, but keep in mind that we are only two fulltime devs with tons of other things to work on. If we spend a lot of time on this, it means less time for other important tasks. Besides you can support both 0.19 auth and 0.20 auth at the same time by sending auth as param and header/cookie.