The Supreme Court curbed the Environmental Protection Agency’s ability to broadly regulate carbon emissions from existing power plants, a major defeat for the Biden administration's attempts to slash emissions at a moment when scientists are sounding alarms about the accelerating pace of global warming.
As a heads up in advance, we have an intermediate protection ready in case the site goes down again due to extremely high traffic, like it did for Roe v Wade. (We are also working on infrastructure and performance improvements in the meantime, but I'm the actual worst, so...) If that does go into effect, you'll see the following:
posts will only be visible to logged in users
your upbears will still work (number will change), but they won't stay highlighted yellow.
So... uh... no need to panic. (IF that even happens)
Sorry for sharing an uneducated opinion but would it help/be possible to disable the real time page updates, and only update upon URL change or refresh? That's gotta be pinging the site all the time from every tab right?
It also sometimes makes my open threads suddenly disappear so I wouldnt miss it
I appreciate the suggestion. I think that's something that's been discussed before. while I'm not as much of a front-end dev, I've been told that the site's usage of websockets makes this not as bad? don't want to out any of the other devs, but maybe someone else can chime in if they feel comfortable doing so.
Can confirm. The bottlenecks that happen when the site gets high traffic are in the database. New websocket messages happen in response to post and comment creation, which are relatively lightweight operations with a small payload.
So live updates have consistently been an issue that needs to be resolved on the frontend, but making that fix would not stop the site from getting overloaded
Hey, just wanted to ask who the right people to contact are regarding getting a better understanding of the various service interactions and deployment-related stuff for the site.
I'm on the analytics side of database operations (so a slightly difference space than the needs of an API interacting with the DB layer- but still familiar with Postgres which I assume is what is being used since this is a lemmy fork), but I'd still like to get an understanding of how the site's services interact to see if I can potentially find any performance gains that might alleviate some of this stress a bit.
Edit- nevermind. Found resources on the pinned c/technology thread and am looking into them now.
As a heads up in advance, we have an intermediate protection ready in case the site goes down again due to extremely high traffic, like it did for Roe v Wade. (We are also working on infrastructure and performance improvements in the meantime, but I'm the actual worst, so...) If that does go into effect, you'll see the following:
So... uh... no need to panic. (IF that even happens)
Sorry for sharing an uneducated opinion but would it help/be possible to disable the real time page updates, and only update upon URL change or refresh? That's gotta be pinging the site all the time from every tab right?
It also sometimes makes my open threads suddenly disappear so I wouldnt miss it
deleted by creator
I’m convinced it’s intentional in order to make us touch grass whenever it becomes annoying enough… almost at least.
I appreciate the suggestion. I think that's something that's been discussed before. while I'm not as much of a front-end dev, I've been told that the site's usage of websockets makes this not as bad? don't want to out any of the other devs, but maybe someone else can chime in if they feel comfortable doing so.
Can confirm. The bottlenecks that happen when the site gets high traffic are in the database. New websocket messages happen in response to post and comment creation, which are relatively lightweight operations with a small payload.
So live updates have consistently been an issue that needs to be resolved on the frontend, but making that fix would not stop the site from getting overloaded
Hey, just wanted to ask who the right people to contact are regarding getting a better understanding of the various service interactions and deployment-related stuff for the site.
I'm on the analytics side of database operations (so a slightly difference space than the needs of an API interacting with the DB layer- but still familiar with Postgres which I assume is what is being used since this is a lemmy fork), but I'd still like to get an understanding of how the site's services interact to see if I can potentially find any performance gains that might alleviate some of this stress a bit.
Edit- nevermind. Found resources on the pinned c/technology thread and am looking into them now.
yeah that feature kinda just sucks anyway
Thank you and the team for all your hard work, I've been too angry to touch most other sites in the last week. :fidel-salute:
:fidel-salute:
:rat-salute:
I just want to say good luck, and we're all counting on you.
:fidel-salute-big:
Hi! Thanks for all your hard work!
If I had a certain set of web skills, how would I go about helping you all out?
ping @layla or @CARCOSA and they can help you get set up. thanks!
TY!