Fetching remote content only works if you are logged in.
Someone should setup a 2westerneurope4u instance which can only be accessed from European IPs.
Make sure you use rustup to install cargo. The debian version is probably too old.
Personally I would block any corporate instances on principle. It's a community project and not a shopping mall. But I don't make decisions for lemmy.ml alone.
It's not necessary to create multiple posts. Instance admins can sticky any federated post to the top of their local site.
Then users would have to deal with key pairs. By using websites we get the domain system which users are already familiar with. And it supports normal password login which is impossible in p2p.
Maybe on another instance but not on lemmy.ml
-
Correct the performance problem now is all from local users (visiting lemmy.ml in their browser or app).
-
If lemmy.ml goes down, other instances still have full mirrors of them. Users there can interact with their local mirror as usual, and other users can see those interactions. However these would not be federated to other instances (lemmy.ml is responsible for announcing community posts to followers). However federated actions are retried a few times so it might federate later.
Image processing isnt causing any noticable cpu load.
You can make a pull request in the lemmy-ui repo to improve it.
If you upload videos on Peertube, Youtube or any other platform with
og:video:urlattribute, Lemmy will automatically embed it.