Hi all, We will be attempting to migrate Pict-rs tomorrow starting at 1700 UTC. Between now and 1700, image uploads will be disabled to try and avoid any data loss. You will still be able to like, comment and post until then. During the upgrade window, Pict-rs will be offline, so viewing images might not work. In theory CloudFlares CDN cache should cover us during the window, but YMMV. Hopefully everything should go smooth, but we do our best to make sure we have backups!
You can monitor our site health at https://dash.lemmy.world and https://status.lemmy.world
We will post updates to https://mastodon.world/@LemmyWorld as well.
Cheers, LW Infra Team 💗
Update This change is done. Images are now hosted on S3 storage and uploads are re-enabled.
Love your work in managing Lemmy’s infrastructure at scale. Would like to join you sometime
Feel free to apply https://team.lemmy.world 🤓
Love how openly you guys communicate about the management of LW. It’s interesting for anyone with an interest in self hosting things to see how you’ve scaled up. Keep up the good work!
Thanks so much 💗
Is this migrating from pict-rs to object storage or upgrading pict-ra from 0.4 to 0.5?
Object storage. Sorry if that was unclear ❤️
Ah nice congrats on the move
Thanks! It’s a lot of work for the behind the scenes stuff, but we have a great team that really cares 👼
Where can I read more about why this is happening?
I have no insight into why it’s being done in this instance, but object storage is typically used when you want to move away from storing things on your web server with “fixed” storage, and instead store it in an “infinitely” expandable storage system. It is also much easier to manage when you have multiple servers as it’s separate and shared.
Right on. This seems relatively important considering pict-rs is the lemmy default. Seems like a change that should be considered for the core repo.
The problem with making S3 config the default is that it would add friction for new admins. If you’re just starting to play around with self-hosting Lemmy then it’s 100% certain you have a local disk but not nearly as likely that you’ve got an S3 bucket ready to go. Making S3 the default would force those new admins to either tweak their configs or figure out how to get an S3 bucket before they could get going. Using local disk for images is fine for smaller instances and self-hosts, but for cost and scaling reasons having an option to switch to S3 is really valuable for larger instance like lemmy.world. Only the top 10-20% of instances are likely to really need to make the switch to S3, so Pictrs defaulting to local disk makes sense I think.
While I agree on the technical aspects, I’ll say that small instances benefit a lot from s3. My single user instance currently has over 25 Gb of media cache… Object storage (hosted on my NAS ) has been a godsend.
What kind, or host?
That we moved to S3 from filesystem
Right, but you said not AWS so I’m curious what either cloud-based S3 service, or baremetal appliance / stack you’re using with S3.
Curious as well. Could be Cloudflare R2 since they said they’re using Cloudflare elsewhere, and it has zero egress fees. Or something like Minio. Obviously just wild speculation on my part.
Almost seems like he’s being cagey about not answering for some reason
I saw “Pictrs Migration” and I thought was about to open a map porn post regarding the movement of ancient Scots.
Guyz, what is Pictr? Is it like Imgur?
Also, [excellent]
Kind of like Imgur, it’s a barebones Image hosting server which is what Lemmy uses to serve images uploaded to the instance. It makes it easier otherwise people would need to use things like catbox or imgur itself to host images.
I do feel like support could be better with it though, like if it gave us an interface where we could access our images from our account, or at the very least one for admins.
Was wondering why I couldn’t upload anything. Well, 3 more hours to sleep in. Woo!
Congratulations on the move!
Is it amazon s3 storage? How much are we paying for it?
We are not using AWS S3, we try and keep costs down where it makes sense 😉
Bro who are you? I don’t see your name in the mod list
It says in their profile.
Lemmy.world tech lead.
Oh shit! Sorry I missed if
In case you’ve not visited the team page. Here is the LW staff.
deleted by creator
Like myqqq attached is
Ight awesome
Thanks. Can we also please block threads?
There will be a announcement soon and even if we dont defederate you can simply block threads yourself in 0.19!
I hope you give us the option. I want to see what threads is like
What is threads?
0.19
ETA for update to that? Seems to work fine on the servers I’m aware of.
In the next week we will upgrade our test environment and test our automation there, if everything works fine we will then be doing it probably the week after that.
Thank you for your work.
Thank you! You are making lemmy great!
Want to say this because the release notes make it perfectly clear. Instance blocking is not and cannot be considered an alternative to defederation.
Users can now block instances. Similar to community blocks, it means that any posts from communities which are hosted on that instance are hidden. However the block doesn’t affect users from the blocked instance, their posts and comments can still be seen normally in other communities.
Not a replacement for defederation, it’s still needed to keep instances healthy. Plus the fact that Lemmy doesn’t really even have blocks, they’re just mutes called blocks (which are only useful under the assumption that the blocked account is innocent, and the blocker is just having a fit or doesn’t have credibility), if we had a way to restrict malicious users then I would say being more hands off isn’t that bad but as it stands there isn’t so defederation and moderation is still important and can’t be substituted with blocking.
But for those “I hate that instance BLOCK IT!!! FOR MURICA!!!” A instance wide defederation is too much. But for those really bad like csam or racist, radical instances it is the best to defederate.
That is a fair point, and I would agree if the only people calling for threads defederation were the snowflakes (the overly sensative opininated users you speak of). However many people have highlighted important reasons why threads federation isn’t a good idea.
Reasons such as:
- Embrace Extend Extinguish Concerns (Already discussed in great detail elsewhere I won’t beat a dead horse)
- Facebook has a very bad track record when it comes to shady and malicious practices
- Facebook has a very poor track record when it comes to effectively moderating spam and hate speech
So while there are some bad and dumb reasons people argue for defederation there are legitimate concerns over this and threads.
Side note (also a bit of a rant):
I feel like the sensitive snowflake users ruin it for people who have legitimate and valid concerns, they undermine efforts to make spaces better because people are so used to dealing with them that when a person brings up something that could be a problem or should be addressed the default response is to dismissively just tell them to block users or instances, under the assumption that a user is one of those snowflakes. (It happened back with the Rammy situation, when the user posted to alert the fediverse that their instance was rogue).
Personally I feel like there should be more severity when it comes to users who make false/opinionated claims so that any claims in general aren’t treated as false or non-credible by default, but I also realize that would be difficult given the size of the instance and also isn’t really my pace to decide since I’m not responsible for user moderation outside of my own communities or ones I mod in.
Just some things to think about. Also sorry for the late response, been having trouble on my Lemmy app. I guess better late than never though (lot of times it is never when I’m late to check or respond).
We will see. We will be of course not cu ksu king if we see a lot of just spam, hate or just ads to “Come over to threads” ads in any way we will look into defedarating them.
