I’m not using it at the moment. But what would be the benefit of self hosting?
The other day wefwef.app hit api limits on lemmy.world so nothing was loading for awhile. The dev recommended selfhosting if you were able to go avoid these shutdowns.
Another benefit would be that your selfhosting instance would theoretically be available even if wefwef.app was down for some reason or another.
Thanks, that sounds intriguing. I guess I need an API key?
deleted by creator
Thanks, that sounds intriguing. I guess I need an API key?
Nope, just install it and you’re off to the races!
deleted by creator
Wait, why do you need to host a web client?
It isn’t just a client right now. Due to CORS restrictions on Lemmy 0.18 instances, wefwef also has a proxy that sits between the PWA and the Lemmy instance.
ah, I see. Thanks for the explanation!
You don’t need to, but the developer of wefwef encouraged it a few days ago because Wefwef was hitting API limits, so the app wasn’t working for some hours.
If you selfhost it, you won’t ever run into this issue.
There are probably other reasons too. Among them, why not? :)
I was a bit confused because for me a web-client usually means a self-contained app running directly where I need it. But now I understand it’s a client that runs on the web(server)
Would it be possible to host it on GitHub Pages?
In the future probably but currently no. Unfortunately Lemmy 0.18.0 has issues with corrs forcing wefwef to proxy all traffic. Ones cors issue is resolved static hosting with sites like GitHub pages should be possible.
I’m not using it at the moment. But what would be the benefit of self hosting?
Currently the benefit is not sending your credentials and other requests through wefwef.app and avoiding throttling. If you value privacy self hosting is a good idea. If you trust wefwef, then the only other reason is to customize/develop wefwef.
After CORS fix in Lemmy is done and wefwef updates your requests should go directly to Lemmy servers so privacy concerns are mitigated.
