Right now, every request passes through wefwef.app and on to the Lemmy instance (it’s acting as a proxy). From my understanding this is due to a lack of CORS support but that will be fixed in a future Lemmy update.
There is also the privacy/security issue since your session token and what you are browsing on Lemmy passes through this same proxy. Which also will be fixed with CORS support.
If you setup your own self hosted instance you don’t need to worry about these issues.
Yes. Whoever is hosting the app is acting as a proxy for everyone that is using that hosted version. If 1,000 people are using wefwef.app it is acting as a proxy for 1,000 people and could be rate limited by the Lemmy instance. If you are hosting your own wefwef then it’s just you connecting to the Lemmy instance.
Right now, every request passes through wefwef.app and on to the Lemmy instance (it’s acting as a proxy). From my understanding this is due to a lack of CORS support but that will be fixed in a future Lemmy update.
There is also the privacy/security issue since your session token and what you are browsing on Lemmy passes through this same proxy. Which also will be fixed with CORS support.
If you setup your own self hosted instance you don’t need to worry about these issues.
Thanks. I get that self hosting means my creds won’t pass through wefwef’s servers, but does it also help with rate limiting?
Yes. Whoever is hosting the app is acting as a proxy for everyone that is using that hosted version. If 1,000 people are using wefwef.app it is acting as a proxy for 1,000 people and could be rate limited by the Lemmy instance. If you are hosting your own wefwef then it’s just you connecting to the Lemmy instance.
Thanks. That’s certainly a very compelling reason to self-host.