We’ve installed Voyager and it’s reachable at https://m.lemmy.world, you can browse Lemmy, and login there (also if your account isn’t on lemmy.world)
PS Thanks go out to @stux@stux@geddit.social , he came up with the idea (see https://m.geddit.social).
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!
Ohhh… maybe…
old.lemmy.world would be hilarious given that lemmy.world is only one month old
you might aswell go crazy and do LemmyBB too https://github.com/LemmyNet/lemmyBB
Wow what a throwback just looking at the pics!
This would be incredible. I’ve already been directing other redditors here with a screenshot of the mlmym front end.
Let’s be careful with having too many frontends though. Are we sure it underwent proper security audit? Even lemmy-ui hasn’t yet and it was a victim of an embarrassing XSS attack.
Wow that’s cool! 🤞for old.Lemmy.world
I wonder when the same happens with a project for new.lemmy.world xD
PLEASE
That’s nice!
Are there any instances with that front end deployed rn?
This would be amazing.
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.
Oh, that’s why the interface felt so weird.
It’s a great app but the iOS interface is keeping me from really using it. It just doesn’t feel natural on Android.
Oh, thank god they changed the name.
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!
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.
Does anyone know how the hiding is implemented?
Will they still be hidden if I look at lemmy through my instance directly?
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.
What a great idea! My favorite app paired with my favorite instance is a match made in heaven! lol. Thanks Ruud!
also if your account isn’t on lemmy.world
To clarify, the login details only go through your server, right?
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
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.
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.
I’m having lots of problems too. Even native client apps are giving me trouble. Must be lemmy.world having issues.
I am using connect for Lemmy and I cannot login either, so I think is an overall problem
Same here. I swear lemmy.world is the most problematic instance I am encountering so far.
Any mod tools included with this?
Not yet. Mod tools will be coming
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.
It will start to stabilize eventually, but we’re probably not going to see that anytime soon!
Problem is deeplinks such as https://m.lemmy.world/post/1291838 don’t work
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.
deleted by creator
It’s nice to see this officially hosted for
lemmy.worldusers. 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.
I have already been using Voyager, do I need to do anything different since my account is on lemmy.world?
You can login using your lemmy.world details on Voyager
I can already login to lemmy.world using Voyager though
looks like you’re sorted then?
Sweet! I’ve been doing the same for a week or two at https://app.thelemmy.club
I just disabled the “other” login feature so it only works on thelemmy.club
What is the difference between wefwef and m.lemmy.world?
btw, wefwef is called Voyager now.
Just because it had to be more confusing 😅
Sorry!
Interesting. Seems the name was the worst thing about it. It put me off.
I guess I’m the only one who didn’t mind it.
Thank god, such an awful name.
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?
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.
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.
This is to get around CORS. @ruud@lemmy.world just fixed CORS on lemmy.world 15 minutes ago (things move fast on Lemmy, lol) so I’ll push an update to direct connect for lemmy.world tonight!
Edit: done ✅
This is about cors headers on the api calls? That only don’t affect other apps because they are offline and ignore cors?
Native apps don’t have CORS restrictions. They can make http requests anywhere.
Only web apps in a browser have this limitation.
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?
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?
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.
This.
I can understand why people say all of this is bemusing and discombobulated, haha.
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.
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-Originheaders, 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.
Oh I thought I had fixed this. Can you re-check and DM me if it’s still not right?
It works, thanks!
