What if you pay them 20 million dollars? ;-)
wefwef
wefwef is now Voyager! Subscribe to [email protected].
It is him, arrest him FBI, Spez leaked through Fediverse.
too soon π
I heard aeharding has been blackmailing ruud
call.mp3
Iβd love to self-host, but I have no idea how. What are the server requirements? Is a Raspberry Pi sufficient?
Raspberry pi should be sufficient if you can get docker on it!
As to selfhosting, I have created an Unraid CA template and submitted it. I hope it will be in the CA store shortly!
was wondering what's going on...thanks for the update!
Interesting, I didn't realize the app sent requests server side. I thought it was more locally running.
It's a reverse proxy for CORS limitations that will be resolved in the next version of Lemmy. :)
I just setup my own self hosted with docker so that is at least one less user hammering the site. :)
Would you mind sharing your docker-compose.yml?
I just followed his instructions on his GitHub and did a docker pull and then docker run.
I fail at following the two extremely simple steps posted at https://github.com/aeharding/wefwef#prebuilt
This is what I get (running on some recent version of Ubuntu Linux on a machine in my garage):
$ docker pull ghcr.io/aeharding/wefwef:latest (...) Status: Downloaded newer image for ghcr.io/aeharding/wefwef:latest ghcr.io/aeharding/wefwef:latest $ sudo docker run --rm -it -p 5314:5314 wefwef Unable to find image 'wefwef:latest' locally docker: Error response from daemon: pull access denied for wefwef, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. See 'docker run --help'. $
Try either of these as the last argument (replacing wefwef
):
aeharding/wefwef:latest
ghcr.io/aeharding/wefwef:latest
Whoever wrote these docs probably builds the image as wefwef
locally and its just an oversite that they forgot their username (aeharding
) is prepended along with the container repository (ghcr.io
) when publishing.
This possibly seems to be happening again, no issues with an account from another instance but Lemmy.world account doesnβt load comments, posts and sometimes says that my account doesnβt exist.
What's the current technical plan to alleviate this? Some kind of multi-node setup behind wefwef.app? Less strict rate limiting by lemmy.world for your endpoint?
Long term: Lemmy CORS support! It will allow direct connect to the instance from your device.
https://github.com/LemmyNet/lemmy/issues/3109
Short term: Coordinating with lemmy.world (ruud) on rate limits