@JustineSmithies@support last couple of days (weeks?) they suffered a lot from script kiddies/ddos attacks and such. They have been down intermittently last week
Not sure if there’s a tangible gain to be had (apart from if it were Reddit interfering), but some people just enjoy being jerks simply for the sake of being jerks. Look at the whole The Lizard Squad situation with Xbox and Playstation awhile back, there was no reason, they just wanted to upset people for the hell of it
lemmy internally has SQL flaws that have not gotten much attention. A few days ago, over the weekend, lemmy.ca people studied some of the SQL and exposed a problem where every single new comment and new post on a local server updates 1500 rows in a database table where it should be updating just 1. There have been similar runaway SQL statements discovered. Fixes for the most recent issue are already on GitHub waiting for merge and publication.
@JustineSmithies @support last couple of days (weeks?) they suffered a lot from script kiddies/ddos attacks and such. They have been down intermittently last week
I don’t understand! What does one stand to gain by attacking lemmy?
Not sure if there’s a tangible gain to be had (apart from if it were Reddit interfering), but some people just enjoy being jerks simply for the sake of being jerks. Look at the whole The Lizard Squad situation with Xbox and Playstation awhile back, there was no reason, they just wanted to upset people for the hell of it
IMO, they think it’s super fun to attack things that are popular for some reason.
Dopamine rush?
People coming here to check it out and it doesn’t seem stable.
@SoonaPaana beats me.
Some karma from u/spez.
lemmy internally has SQL flaws that have not gotten much attention. A few days ago, over the weekend, lemmy.ca people studied some of the SQL and exposed a problem where every single new comment and new post on a local server updates 1500 rows in a database table where it should be updating just 1. There have been similar runaway SQL statements discovered. Fixes for the most recent issue are already on GitHub waiting for merge and publication.