Crossposting notices don’t seem to show up on posts or in communities with this update, although I can see it noted on the home screen list.

It’s mad to think that that’s small change for them

I can’t believe you’re only just moving to object storage! Offload that stuff as much as possible (this is probably a grandmother suck eggs situation, I know).

When you say “photo database”, do you mean Lemmy literally stores the binary image files in the db, or just the storage area for images (ofc linked to from the db)?

That is horrific. In my day job, I stored images in a database in my first job, learnt my lesson and now have an allergic reaction just thinking about it.

Good work, team 👍

I’d definitely post more from there if the embed was as nice as e.g. using RES.

authcom

Is auth short for authoritarian or authentic?

It’s a pain in the ass, but we REALLY need to be making sure our content properly tagged so that it doesn’t pop up in federated instances as untagged nsfw content. There will likely be a crackdown on said posts that are not tagged properly, so please be aware of this fact and triple check that your posts are properly tagged.

Lemmy’s stance is that content can only be edited by the author or removed by mods/admins - that’s fair enough. What I disagree with them about is that that applies to tags too - I don’t want to have to delete posts just because they aren’t tagged correctly.

Where do people stand on allowing editing of nsfw tags?

I decided I was happy not knowing.

I like the idea of blocking until we have more granular filters. This instance will be more successful if it’s not blocked by loads of instances, and I reckon allowing stuff like this will make the block choice too easy.