Voyager

5708 readers

68 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 1 year ago

MODERATORS

aeharding

[email protected]

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 (self.voyagerapp)

submitted 1 year ago by andrewta to c/voyagerapp

7 comments fedilink hide all child comments

all 8 comments

sorted by: hot top controversial new old

[–] hperrin 16 points 1 year ago (2 children)

This is the first Ionic app I’ve used (that I know of), and I’m super impressed. I don’t want the web app to go away.

[–] [email protected] 7 points 1 year ago* (last edited 1 year ago)

I think the situation is:

Lemmy V0.19 uses a different authentication method to 0.18 and earlier.

It isn’t possible for a web app to know the Lemmy version initially.

So a web app can be compatible either with 0.18 or 0.19.

When most instances have updated to 0.19 or higher then the web app will switch to 0.19 only

Native apps aren’t affected

[–] aeharding 4 points 1 year ago

It's not going anywhere :)

[–] [email protected] 9 points 1 year ago

Just means your homeserver will need to be running v0.19 for v2 of Voyager.

If your homeserver hasn't updated yet, don't update your PWA.

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago) (3 children)

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.

[–] [email protected] 1 points 1 year ago

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.

[–] plz1 1 points 1 year ago

That's exactly how that reads, to me. Next server version will break auth for any PWA.