- cross-posted to:
- [email protected]
- [email protected]
- cross-posted to:
- [email protected]
- [email protected]
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@[email protected] , he came up with the idea (see https://m.geddit.social).
You must log in or register to comment.
Is there a way to change the comment sorting in Voyager? On the desktop and in the old mobile app, I preferred the “Top” sorting for comments (it’s annoying that I can’t set this as a default, but I’m assuming that’ll get fixed in time). But when I go to Voyager, I can’t figure out how to change comments away from the default sort. Is it possible to change the comment sort order in Voyager? Is it in a menu I haven’t checked yet? Some button I thought did something else?
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.
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.
Its lemmy.world They updated the version to 0.4.2 today and were getting issues. Join a different instance
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.
Join another instance. I was on lemmy.world but now jumped to aussie.zone and everything is the same after subscribing to the communities.
There’s ongoing Lemmy.world authentication issues. Should be resolved once Ruud gets online.
Best idea ever !
Awesome! Question, I made an account at the beginning of the month on Lemmy.World but I never got the verification email… Is there a way to get it re-sent?
It works for any instance though, not only lemmy.world.
Huh, ok, I tried logging into other instances with that email and they worked but when I came back to lemmy.world it told me I needed a verification email. So there isn’t a way to re-send it is there?
This is awesome!!!
@ruud, any chance we can get voyager updated. Post editing has been added in .20 and it can’t be done in .18.2
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.
As a dev of a web Lemmy client, this was fixed in Lemmy 0.18.1, a proxy is no longer necessary.
Okay. I’ve seen someone mention that it’s not needed, but nobody seemed to care about the whole problem to elaborate. Thx.
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 a great idea! My favorite app paired with my favorite instance is a match made in heaven! lol. Thanks Ruud!
@ruud what’s the advantage of this than accessing it via Google?
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!
That iOS UI though… No, thanks.
As an Android user who got used to MaterialYou the “cold” iOS UI really looks jarring. But it’s impressive nonetheless what they accomplished with a web app.
Yes, but it’s too out of place.
Problem is deeplinks such as https://m.lemmy.world/post/1291838 don’t work
They do work but they’re structured differently: https://m.lemmy.world/posts/feddit.de/c/[email protected]/comments/1477069
Edit: Nevermind. Voyager seems to handle their route state in a weird way. Refreshing this while logged in works while the link does not work for third parties.
It works if you’re logged out. If logged in, all requests must be proxied through your own instance, and post IDs vary per instance.
In the future, it might not force a redirect and show you content for a logged out/“roaming” state, but not now
So… They don’t work?
What is the difference between wefwef and m.lemmy.world?
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.
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!
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.
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. @[email protected] 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 ✅
Hey is it dynamic or you have to add a list of instances to direct connect?
Update: sorry, just saw your answer below 🤷♂️
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?
btw, wefwef is called Voyager now.
Just because it had to be more confusing 😅
Sorry!
Thank god, such an awful name.
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.
