Voyager for Lemmy
m.lemmy.world
Voyager is a beautiful mobile web client for Lemmy. Enjoy a seamless experience browsing the fediverse.
  • infotainment@lemmy.world
    90·
    1 year ago

    This is a great idea, Voyager’s mobile experience is super polished.

    Long shot, but would it be possible to get Mlmym installed at old.lemmy.world? Would be a fun throwback!

  • Molecular0079@lemmy.world
    60·
    1 year ago

    Gotta say, it’s weird seeing a iOS interface on an Android device XD, but it feels very smooth and polished, especially for a web app.

        • Fushuan [he/him]@lemm.ee
          6·
          1 year ago

          Yeah we know that (almost) everyone who used iOS had Apollo, it’s been kind of obvious with the barrage of comments. However, there’s no Apollo for android and tbh I kinda hate the iOS feel it has, so if someone says that it feels/felt weird, chances are that they are an android user.

          • kratoz29@lemmy.fmhy.ml
            2·
            1 year ago

            That’s what I’m seeing, honestly to me it looks and behaves great, the only downside is that it is a PWA and it doesn’t feel as fast and polished as stock apps.

            • Fushuan [he/him]@lemm.ee
              1·
              1 year ago

              And that’s because you used Apollo. The context of this particular chain is that it felt weird for android users, because it has an iOS feel, and they answered that that’s why it felt weird, so it’s impossible that they used to use Apollo, since they were an android user.

        • aname@lemmy.one
          61·
          1 year ago

          I am not used to Apple interface so it was just clunky and weird, yes

          • ToastyBanana@lemmy.world
            51·
            1 year ago

            As a iOS user, same could be said about Android. It looks bad and is unintuitive to use for me. It’s about ecosystems and people getting used to one thing over the other!

            • aname@lemmy.one
              4·
              1 year ago

              Definitely. Personally Liftoff is the client I am currently using and liking.

  • Elektrotechnik@lemmy.world
    26·
    1 year ago

    Voyager is, by far, the best lemmy experience I’ve tried. Hiding posts is a godsend. And they did all this as a web app?? Impressive!

    • damnYouSun@sh.itjust.works
      14·
      1 year ago

      And they did all this as a web app??

      A lot of things that used to require native apps Android/ iOS / Windows / Mac can now be done as a web app which is easy because it means you don’t need to compile the code four times.

      • Elektrotechnik@lemmy.world
        2·
        1 year ago

        It is not connected to the Lemmy account… I used their URL “vger.app” at first, but then lemmy.world implemented it themselves. When I logged in over that URL, I had to “rehide” the topics.

        Sorry, I don’t know the specifics.

  • Tygr@lemmy.world
    26·
    1 year ago

    What a great idea! My favorite app paired with my favorite instance is a match made in heaven! lol. Thanks Ruud!

  • WhoRoger@lemmy.world
    25·
    1 year ago

    also if your account isn’t on lemmy.world

    To clarify, the login details only go through your server, right?

    • ඞmir@lemmy.ml
      1·
      1 year ago

      I’m fairly sure Voyager is a fully client-side app that can use the API from any instance directly no matter where it’s hosted. Someone correct me if I’m wrong

      • WhoRoger@lemmy.world
        4·
        1 year ago

        The devs themselves said they need to proxy information including password through their servers due to how cors works. But people are saying that this may be resolved somehow, so idk.

  • sphred5@lemmy.world
    16·
    1 year ago

    It was working great yesterday and earlier today, but now when I am on there it shows me as logged out, and then when I log in it says it’s successful, but then shows me as logged out still. They keyboard is also not working when trying to enter my user name, I had to paste it.

    • Alien Surfer@lemmy.world
      3·
      1 year ago

      I’m having lots of problems too. Even native client apps are giving me trouble. Must be lemmy.world having issues.

      • YⓄ乙 @aussie.zone
        2·
        1 year ago

        Its lemmy.world They updated the version to 0.4.2 today and were getting issues. Join a different instance

        • YⓄ乙 @aussie.zone
          2·
          1 year ago

          Join another instance. I was on lemmy.world but now jumped to aussie.zone and everything is the same after subscribing to the communities.

  • BadaBing@lemmy.world
    182·
    1 year ago

    While I do love the quick innovation and updates of Lemmy, I have to admit that it’s a bit confusing and hard to keep up with.

    • Gnothi@lemmy.world
      18·
      1 year ago

      It will start to stabilize eventually, but we’re probably not going to see that anytime soon!

    • Redjard@lemmy.dbzer0.com
      9·
      1 year ago

      wefwef is an app, a webapp. Usually reachable under wefwef.app
      You can install it as a progressive webapp through your browser.
      This now is rehosting the files of wefwef on the m.lemmy.world domain, basically a fork that promises to keep in sync with the official codebase and the official domain. The m.lemmy.world domain shouldn’t need any connection to lemmy.world, it is basically not much different to a filehoster that hosts an apps apk. That is why I don’t think m.lemmy.world even sees your credentials if you log in anywhere.

      As to why, I’m not sure what the use of this is. Maybe in case the official domain goes offline?

      • AlmightySnoo 🐢🇮🇱🇺🇦@lemmy.world
        17·
        1 year ago

        That’s because when you use wefwef through wefwef.app, your data goes through wefwef.app before going to the instance, the app AFAIK does not communicate directly with the instances yet. You basically have to decide whether you trust wefwef.app enough to proxy your data through them.

        Using m.lemmy.world would mean your data goes through lemmy.world directly, which you already chose to trust.

        • Redjard@lemmy.dbzer0.com
          5·
          1 year ago

          Oh, you are almost right, I was wrong. Checking the network traffic it seems images (and some parts of posts?) are fetched directly, but other elements are fetched through wefwef.app, namely everything that needs the users session. maybe this is done to process some lemmy outputs serverside into for example the notification icon? This surprised me, I was confident the only requests to wefwef.app would be static elements and the code itself.

            • Redjard@lemmy.dbzer0.com
              1·
              1 year ago

              This is about cors headers on the api calls? That only don’t affect other apps because they are offline and ignore cors?

                • Redjard@lemmy.dbzer0.com
                  1·
                  1 year ago

                  Makes sense, never thought about that. An annoying situation, I wonder how many security issues would crop up if browsers allowed ignoring cors for pwas…

                  Currently apicalls are proxied through the server but end up with the lient all the same, with the session being stored in local storage “credentials”?
                  Will you currate a manual whitelist for direct calls or have the app test if direct fails and fall back to proxied?

            • iso@lemy.lol
              11·
              1 year ago

              Hey is it dynamic or you have to add a list of instances to direct connect?

              Update: sorry, just saw your answer below 🤷‍♂️

        • G0FuckThyself@lemmy.world
          5·
          1 year ago

          Okay what If I am already using wefwef than my data is already passed through wefwef, so there is no benefit now? or still I should logout with wef wef and use m.lemmy.world?

          • Redjard@lemmy.dbzer0.com
            4·
            1 year ago

            Most things passing through are public anyway, as lemmy is allmost entirely public. The only privat info is your password and wefwefs session. Those are visible in clear to the server, so could in theory be logged. If you change your password (and invalidate your sessions) after wefwef switches to direct you should be good.

          • XpeeN@sopuli.xyz
            1·
            1 year ago

            Stopping the stream of data is always possible. You can use google daily until you suddenly don’t, the steam of data is (or probably just the proccessing of your queries in this case) stops.

        • Nato Boram@lemmy.worldEnglish
          3·
          1 year ago

          It would surprise me if that was the explanation since this can be easily fixed by Lemmy.world itself by not sending two Accept-Control-Allow-Origin headers, thus breaking web clients.

          Right now, I’m forced to route my own calls to my server on the app I’m making because Lemmy.world is misconfigured.

          I guess that for instance below 0.18.1, it makes sense, since Lemmy had a bug at that point that didn’t allow web clients to connect.

  • IthronMorn@sh.itjust.works
    11·
    1 year ago

    Aaannnnddd I’m back. Was on wefwef but went to Jerboa and then connect. But I think I’ll stay at voyager as it’s definitely the most polished so far.

  • PriorProject@lemmy.world
    10·
    1 year ago

    It’s nice to see this officially hosted for lemmy.world users. I’ve been curious about wefwef but there was no way I was going to enter my creds into a third-party proxy. It feels much better to do so via an instance hosted by the world admins where my Lemmy account is though.

    FYIW, when you save this as a PWA via Firefox mobile, the name is just “voyager”, which I assume makes it hard to distinguish from the voyager instance hosted by its devs. I don’t think this can be changed as a user (unless I’m too dumb to figure it out). If the PWA app name can be changed server side, might be good to call it Voyager World or something.