[-] bmygsbvur@lemmy.ca 2 points 10 months ago

It's on the GitHub issue tracker already. Did you not read the post?

[-] bmygsbvur@lemmy.ca 3 points 10 months ago

Very easily you say? Maybe tell us what this cron job is so we can all add it?

[-] bmygsbvur@lemmy.ca 5 points 10 months ago

Doesn't change the fact that this is an issue.

[-] bmygsbvur@lemmy.ca 3 points 10 months ago

Because there's already an issue dated July 6: https://github.com/LemmyNet/lemmy/issues/3504

Like I said, people already know about this months ago.

[-] bmygsbvur@lemmy.ca 3 points 10 months ago

Thanks for this.

[-] bmygsbvur@lemmy.ca 4 points 10 months ago

Yes. This is a great alternative solution.

[-] bmygsbvur@lemmy.ca 2 points 10 months ago

"Quietly delete the images periodically". If only it was made easier for admins. You can't even report these images because nobody knows it was there in the first place.

[-] bmygsbvur@lemmy.ca 4 points 10 months ago

Doesn't change the fact that this is an issue that needs to be resolved.

[-] bmygsbvur@lemmy.ca 3 points 10 months ago

Sadly not the case

[-] bmygsbvur@lemmy.ca 4 points 10 months ago

That's another issue. Also a necessary feature.

[-] bmygsbvur@lemmy.ca 3 points 10 months ago

They probably have the tools to deal with it. Lemmy certainly doesn't.

[-] bmygsbvur@lemmy.ca 4 points 10 months ago

Remove it from docker compose.

view more: ‹ prev next ›

bmygsbvur

joined 10 months ago