confused about the newest update . will we continue to have a web app or do we have to switch to a native app (ex: ios app).? it almost sounds like the web app is going away
confused about the newest update . will we continue to have a web app or do we have to switch to a native app (ex: ios app).? it almost sounds like the web app is going away
You're viewing a single thread.
How I'm reading it, is that all Lemmy v0.18 servers (and lower) will no longer work with Voyager v2 web app. And Lemmy v0.19 does work. But I might be wrong..
Here is the changelog text
The next release of Voyager will be v2. Voyager v2 will break support for lemmy v0.18 for progressive webapp clients! This is due to CORS limitations where web clients cannot set a custom Cookie header for backward compatibility, and the new v0.19 lemmy-js-client removes authentication via the auth url param.That's exactly how that reads, to me. Next server version will break auth for any PWA.
This only applies to those self hosting. For the general public, there will be no issues or real points of action. From GitHub:
Native app users
No action required! Voyager will continue to support Lemmy v0.18 for the foreseeable future, while adding support for new v0.19 features over time.
PWA (https://vger.app) users
Voyager running on https://vger.app will continue to support Lemmy v0.18 until v0.19 has been out for a while and all large instances have upgraded. This will be accomplished by pinning https://vger.app to Voyager v1. After some time, https://vger.app will drop support for v0.18 by upgrading to Voyager v2. Dropping support for Lemmy v0.18 will allow supporting new v0.19 features.
Voyager self-hosters
The next Voyager release will be v2. Voyager v2 will break support for Lemmy v0.18 for PWA clients, and Voyager v2 may be released before Lemmy v0.19 is released. If you have Voyager auto-updating via watchtower or some other means, I recommend to disable it until your instance updates to Lemmy v0.19.