often times they won’t even action users who are engaging in transphobia, even if reported. It’s really not great.
As I said in my other reply. I don't live that life so we might not get all the cues but if anyone on our team sees transphobia it will be removed.
You too ❤️ Good luck with the community!
Most likely this is the reason
Correct, I use both myself. Pihole is also my DHCP server and I created different blocklists for different devices on my network. For example, I have "general", "media", "gaming" and "kids".
"they changed a comment before linking it"
You can even see when the post was last edited, this is just false 🤷🏻
Edit: saying we changed the comment and calling the admins here trolls while we were really just trying to be helpful. You're no longer welcome here
with a built in back room toggle for making them public
Not true. Votes are visible in the database but there is nothing built into lemmy for this.
Yep those comments were restored.
Man you're too much. Goodbye indeed
Noticeable improvements here on our home instance at Lemmy.world!
cross-posted from: https://lemmy.world/post/1061471
Another day, another update.
More troubleshooting was done today. What did we do:
- Yesterday evening @phiresky@phiresky@lemmy.world did some SQL troubleshooting with some of the lemmy.world admins. After that, phiresky submitted some PRs to github.
- @cetra3@lemmy.ml created a docker image containing 3PR's: Disable retry queue, Get follower Inbox Fix, Admin Index Fix
- We started using this image, and saw a big drop in CPU usage and disk load.
- We saw thousands of errors per minute in the nginx log for old clients trying to access the websockets (which were removed in 0.18), so we added a
return 404in nginx conf for/api/v3/ws.- We updated lemmy-ui from RC7 to RC10 which fixed a lot, among which the issue with replying to DMs
- We found that the many 502-errors were caused by an issue in Lemmy/markdown-it.actix or whatever, causing nginx to temporarily mark an upstream to be dead. As a workaround we can either 1.) Only use 1 container or 2.) set
proxy_next_upstream timeout;in nginx.Currently we're running with 1 lemmy container, so the 502-errors are completely gone so far, and because of the fixes in the Lemmy code everything seems to be running smooth. If needed we could spin up a second lemmy container using the
proxy_next_upstream timeout;workaround but for now it seems to hold with 1.Thanks to @phiresky@lemmy.world , @cetra3@lemmy.ml , @stanford@discuss.as200950.com, @db0@lemmy.dbzer0.com , @jelloeater85@lemmy.world , @TragicNotCute@lemmy.world for their help!
And not to forget, thanks to @nutomic@lemmy.ml and @dessalines@lemmy.ml for their continuing hard work on Lemmy!
And thank you all for your patience, we'll keep working on it!
Oh, and as bonus, an image (thanks Phiresky!) of the change in bandwidth after implementing the new Lemmy docker image with the PRs.
Alt of https://lemmy.world/u/elcheaponcod
Banned