- 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.
This is awesome!!!
Any mod tools included with this?
Not yet. Mod tools will be coming
Does it update at the same cadence as the original?
Currently I need to manually update the container but I might install watchtower
Minor nitpick, but isn’t a moderator icon redundant for an admin?
I wouldn’t say so. Admins run the site, moderators run communities. This happens to be a community with an admin as a mod.
Are you planning on disabling “Other” logins from this? I wouldn’t blame you if you did but at the same time, I’d keep using the vger URL for the purposes of how I’m using it.
No ill keep the other logins
Yeah I just installed watchtower and that sorted out the updates
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!
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.
This is really nice!
Very cool! Given the separation between lemmy’s backend and frontend, I’m guessing this is relatively easy to do (?) which means theoretically many instances could have a whole range of frontends built in from which the user could chose as they like?
This is awesome :) Thank you!
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!
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.
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. @[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?
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?
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.
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.
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!
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!
I wonder when the same happens with a project for new.lemmy.world xD
That’s nice!
PLEASE
This would be amazing.
Wow that’s cool! 🤞for old.Lemmy.world
Nice idea! Just stole that xd 🤦 Here’s old.lemy.lol!
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.
Are there any instances with that front end deployed rn?
Ohhh… maybe…
This would be incredible. I’ve already been directing other redditors here with a screenshot of the mlmym front end.
you might aswell go crazy and do LemmyBB too https://github.com/LemmyNet/lemmyBB
Wow what a throwback just looking at the pics!
old.lemmy.world would be hilarious given that lemmy.world is only one month old
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
wow nice!!
Nice work! Really fun to see everything getting better and better!
What a great idea! My favorite app paired with my favorite instance is a match made in heaven! lol. Thanks Ruud!
@[email protected], @[email protected], @[email protected] - Are there any instructions on how to set this up for my own instance? 😁
Should all be here! https://github.com/aeharding/voyager#self-host-docker-deployment
Thank you very much! Keep up the awesome work!
