or the community you are posting to doesn't allow Undetermined language, and that's what you've selected. There is no error handling for that yet
Where can I find these stats?
every instance is sharing in the traffic to browse the fediverse. Not one service is responsible for serving content, you (the instance admin) are only serving for your members.
The downside of this is there is a huge amount of replicated data stored everywhere. Content of popular communities will be scraped by and stored on many many servers, filling up servers and increasing storage and bandwith bills for all those servers
Thanks for mentioning your provider, their prices are a lot cheaper then DO !
only pictures and posts that the instance-member are subscribed to, and from the moment they interacted with it. But yes, I'm curious to see where this goes.
I noticed it when I was looking in the database and disk on my instance, where there are already thousands of posts and more then a thousand images - while my own instance only has a couple of posts and images
lots of traffic on many small files eventually uses more disk space and bandwidth. Depends on the growth of the instance
yes. running a server costs money. I have lemmyfly.org running just 2 days now on digitalocean using a cheap 1GB ram, 25GB diskspace and 1000GB bandwidth for $7,- a month. Storing images on the server will eventually take up all space and bandwidth meaning you have to upscale -> pay more.
Using a different location for storing images and/ or videos is best to offload the instance !
yes, they are hosted on the server that is running the Lemmy instance. But every other instance that is linked to that instance will 'scrape' all posts incl images and store them on they're own server. So posts and images are served from the instance you yourself are a member of
I do, and looking forward to contribute. I'm not a UX designer though...
it definitely needs some UX attention
yep, same issue I had! the link :) https://lemmy.one/post/36440
after changing the docker-compose.yml file you have to destroy and up the postfix container
docker-compose stop postfix && docker-compose rm postfix
docker-compose up -d
after changing your lemmy.hjson file, just restart the lemmy
container.
oh it's visible because I'm admin/ mod ?