Voyager

7357 readers

3 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 2 years ago

MODERATORS

aeharding@lemmy.world

aeharding@vger.social

Haven’t been able to log in (lemmy.world)

submitted 2 months ago* (last edited 2 months ago) by Gingerlegs@lemmy.world to c/voyagerapp@lemmy.world

14 comments fedilink hide all child comments

To Lenny.world for days. No issues with others…

Deleted app and re-downloaded. Still can’t log in.

Any clue?

you are viewing a single comment's thread
view the rest of the comments

[–] aeharding@vger.social 5 points 2 months ago

I see what you’re saying, but I disagree it should be consistent: the user agent should accurately identify the software that’s requesting a resource.

When Voyager just sends VoyagerApp without the browser stuff, it’s because the code that is making the http request actually bypasses the browser entirely, and is done natively with CapacitorHttp (helps to bypass CORS for perf and server misconfiguration).

I could see an argument for changing it to CapacitorHttp/8.0 VoyagerApp/1.0 for API requests. But if voyager changed the header to include browser ua, that would actually be spoofing since the browser played no part of making or handling the request.

i'm not sure why this was causing issues here though, especially with the login, as that should just be 100% api stuff and therefore use VoyagerApp/1.0 from the native app?

Yes, that’s right, that is odd! 🤔