if people want to contribute code, they can check out the various repositories in the LemmyNet GitHub org to see which issues are looking for someone to pick them up.
ethical ads are virtually non-existent. when limiting ads to ethical ads it's unlikely you're getting even remotely close to bringing in the necessary funds.
people promoting ads are typically those who expect others to suffer while they themselves are using ad blockers. there are some people who honestly turn off ad blockers, but i wouldn't recommend anyone to do that for any site, as i don't consider the majority of ads ethical and it's also often used as a malware/phishing/scam distribution mechanism.
this is also a vicious cycle of more people blocking ads -> ads getting worse to offset the lost ad revenue -> more people blocking ads. this is what lead to the internet today, where the majority of the internet is basically unusable if you don't use ublock origin or a comparable solution.
our foundation is in NL, because that's where @ruud@lemmy.world is located, but the active admin and infra team members are distributed across the world with members in Netherlands, Germany and USA currently.
there are multiple dedicated test instances that are used for development purposes.
testing on lemmy.ml is mostly happening for release candidates that require actual user activity to find remaining bugs, at the point where it's getting close to a proper release.
it's around 2.5% of our monthly expenses that go to the lemmy devs. 2% of the stated minimum donation goal would be the hosting costs for lemmy.ml. with the assumption that the lemmy donation goals is met, that would mean around 0.05% of the donations to lemmy.world/fedihosting foundation are used for lemmy.ml hosting costs.
this was already explained in a few other places in the comments here, but in the end, even if it wasn't directly going to instance operating costs, if you pay people a salary and they then take it out of their own pockets there is no real difference, as the money would still end up in the same place.
edit: it has since been clarified that only donations via Lemmy's open collective account are used for lemmy.ml hosting costs. our donations towards Lemmy development are not done through open collective and therefore 0% of lemmy.world/fedihosting foundation donations are used for lemmy.ml hosting costs.
whether this is something that makes a difference in the end is something you have to decide on your own, but this is still the addressing the frequently mentioned topic of having donations explicitly for development rather than also supporting lemmy.ml operations.
Federated image links to non-lemmy websites sometimes show up as image_proxy links from the poster’s instance. This is a really annoying issue that results in misleading domains showing up next to posts as well as breaking image display in the post itself.
that is not directly a mlmym issue, it's that people copy links on instances with image proxying enabled and use them in new posts :|
feel free to also raise them as issues on the repo directly to have them documented.
by the way, we run the version on the main branch on https://mlmym-unstable.lemmy.world/, although it does have a domain lock to lemmy.world.
I've started changing some smaller things over on Fedihosting-Foundation-Forks/mlmym. I don't really have time, motivation or Go knowledge to fully maintain and develop new functionality there, especially as I don't use it myself, but I'm currently planning to keep it on life support at least and see if I can at least fix some stability issues.
I also already forked and updated go-lemmy, which should now support the latest Lemmy 0.19.11 APIs.
Currently the primary focus for this is to have builds for old.lemmy.world, but I wouldn't be opposed to have this used as a generic repo if other people want to contribute. I'm currently not planning to intentionally break things in a way that would prevent usage outside of Lemmy.World, but unless there are other people interested in contributing as well, I will primarily just focus on ensuring compatibility with the Lemmy version we are running.
our registration application system is completely automated and we're making it very clear on our signup page what text you need to provide in order for your application to be approved.
Additionally, you should have received an email about your registration being rejected within a minute of verifying your email. Unfortunately your application fell within a window of these notifications being broken on our end, as we had to fix some stuff following our recent Lemmy update. Other users will generally receive this notification when their application is rejected.
As you explained why you'd want to sign up on lemmy.world rather than entering the required text your application had been denied. Our application processing system is also purging accounts from the database when the application gets rejected, so the username is available again and you'll be able to sign up again with the same name.
in short form, we have HAproxy running on a hetzner cloud VM for Lemmy/Lemmy-UI, another HAproxy VM for the alt UIs, a VM for the alt UIs.
for the main LW box, which runs lemmy containers, lemmy-ui, pictrs and a database each for lemmy and pictrs, we have a physical box with an EPYC 7502P 32 core CPU, 128GB memory and NVMe SSDs.
there are various mentioned in !syncforlemmy@lemmy.world, the main one i was referring to was the one where in some cases posts in local communities won't show comments.
if people want to contribute code, they can check out the various repositories in the LemmyNet GitHub org to see which issues are looking for someone to pick them up.
the main repositories, by language, are:
additionally, there is a range of open source alternative web interfaces and apps that wouldn't mind contributions. some of them are listed here: https://github.com/dbeley/awesome-lemmy?tab=readme-ov-file#alternative-front-ends