>dependency that hasnt been updated since 2012
how did no one hack this shitty website before
>>29070You always could.
Litterally google my man.
>>29069It won't be the same, and no one will ever trust giving emails or waiting 900 seconds to make a post just so the chink can keep collecting 4chan passes
there's no way they have a backups either or any systems in place to fix the structural issues that have been neglected for over a decade, its and it'll be dead on the water for anyone trying to bring it back.
>>29080Twitter, but it feels like Elon always has a good reason to bail on that, so it's more anomalous that twitter persists than doesn't.
It'd be funny if Truth Social ended up getting too big to moderate.
>>29087I considered applying for janitor a few times but always decided against it since it would mean having to sit in a Discord and get to know people and that all seemed cliquey and annoying. I was right haha. I wonder how many janitors will be scared off. They'll have to recruit new ones when the site comes back up.
4chan's moderation/site management is deeply flawed for both its opaqueness and its refusal to proactively improve the site. Mods and janitors weren't your fellow poster, they were an infallible invisible force. That's why janny hate was so prevalent.
>>29069It's not about the unsavory elements found within it (like all the tracking and shadowban mechanisms), but security vulnerabilities. And you don't seem to know the differences between closed and open source code when it comes to vulnerabilities.
In open source projects (like Vichan), vulnerabilities are rarer because there's more eyes on the code which means they're more likely to get spotted and fixed, oftentimes very quickly by the person who noticed it.
This sounds counterintuitive since a malicious actor can potentially spot a vulnerability before anyone else and exploit it, but in practice this rarely happens because vulnerabilities get routinely fixed at a very good rate.
Closed source (like 4chan), though, has more vulnerabilities for two reasons:
>less people looking and checking the code means they're more likely to go undetected>increased sloppiness by the coders since the code is only available to select groups that arent malicious, thus they dont see a reason to write better codeClosed source has both a high rate of vulnerability creation AND a low rate of vulnerability fixing. This mean vulnerabilities
accumulate over time. A closed source code being leaked is a disaster because now you've got the threat of malicious actors looking at it while the source code itself is riddled with orders of magnitude more vulnerabilities than open source. This makes the probability of a malicious actor discovering a vulnerability near-guaranteed (and indeed, people have already discovered various problems with 4chan's leaked code that aren't the PDF file vulnerability that the hacker used).
Unique IPs: 23