trunkswd said:
Darwinianevolution said:
As many of you can clearly see, the front page has been vandalised with indecent stuff. The keypoints here are:
- Talon's account was compromised.
- We've contacted the Admin's.
- We've mitigated the issue slightly by removing Talon's permissions and banning him.
- The site will have to be backdated.
- Passwords may have to be reset. [IMPORTANT]
- We don't know the full extent of the damage yet.
The staff is doing everything they can right now, so for now the best course of action is to keep calm.
Edit by @trunkswd
- We are working on trying to restore everyone's accounts and posts that were "Deleted." Anything deleted is hidden and should not be completely removed. The team is trying to find where everything is hidden to restore it.
- Passwords from what I've been told should be safe, but I would change your password just in case.
- Anyone who had their "Supporter" removed will get it back once we get everything sorted.
Edit by @Machina
- Everyone banned by the hacker has been unbanned (including my own account!), and a bug that was preventing newly unbanned people from properly viewing the website has been resolved by Bandorr. Everyone should now be able to use the site as before.
- The posts of those who were banned are still missing; we're hoping to resolve that, but that fix is probably gonna take more time.
- All Supporters at the time of the hack (and who had it removed), have had their Supporter status returned. The dates for expiration are a placeholder until Trucks and I have time to go over them in more detail. If I missed anyone out let me know!
Edit #2 by @Machina
- Restoring everyone's posts is going to be much harder than anticipated because the most recent back-ups are corrupted. Ryuu estimates there are 750,000 missing posts. We have a reliable back-up from two years ago that we're going to use to restore most (around 580,000) of those missing posts (while of course saving any currently on the site). We're still brainstorming methods to retrieve the ones posted between the date of the last good back-up and the date of the mass deletion.
- It shouldn't be possible for this to ever happen again - the Admin tool he used to delete posts has been removed from the website entirely, and JLauro has fixed the issue that was causing the back-ups to corrupt.
- The VG$2,000 removed from each account for being banned has been restored, plus an extra VG$2,000 has been added for the inconvenience.
|
As you can all see Machina has provided an update in the OP. All "deleted" posts haven't actually been deleted, but some data is missing from them such as what thread they belonged in and the user who posted them. The first step is to restore all posts from the last reliable back-up from two years ago, which will bring back about 580,000 of the 750,000 missing posts. The second step in restoring all the other posts from those affected is something we are still working to figure out.
As Machina noted, the ability to "delete" posts has been completely removed from Admin tools, so this shouldn't happen again in the future. And JLauro has fixed the issue that caused back-ups to be corrupted.
|
I somehow wish I could help, I've done this kind of work in the past and I somehow enjoy this (reconstructing data using alternative sources). But chance are techno used for data storage here fall outside of my expertise which are MS SQL, MySQL and to some degree MongoDB.
I've been thinking the quote feature might be used to identify some of the post as they identify the thread and original poster like this one (Which identify one of Ryuu deleted post in the Ukraine thread) but since quotes are fully rendered and not just referenced by ID and they also can be partial it would require use of various complex query which would also be very resources intensive to run. Still it might manage to identify a few 1000's of the remaining ~170k post.
Also in the end if unidentified post are left, it might be a good idea to associate them all to a generic fake account in a specifically created close thread that may offer the possibility for known affected user to claim post (probably using the report feature).
Last edited by EpicRandy - on 17 October 2022
