@sunaurus@lemm.ee is this something you’d consider for lemm.ee?
you can log into lemm.ee through this website!
True but my login info would be stored in lemmy.world and not my home instance.
Problem is deeplinks such as https://m.lemmy.world/post/1291838 don’t work
@ruud, any chance we can get voyager updated. Post editing has been added in .20 and it can’t be done in .18.2
Just saw this, that's very cool! will be trying it out
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
@ruud@lemmy.world, @aeharding@lemmy.world, @stux@geddit.social - Are there any instructions on how to set this up for my own instance? 😁
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.
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.
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.
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.
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.
This Community is intended for posts about the Lemmy.world server by the admins.
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Any support requests are best sent to info@lemmy.world e-mail.
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
