Well, good for reducing its presence. Not so much for forensics, unless someone grabbed a copy before deletion.
db0’s fork was from another fork, which is almost three years old at this point. Scratch that, github just reassigns the fork parent if the source repo gets deleted.
Oh gotcha, wow, yeah I guess that would be fueling my confusion. Insane that a user interface itself would add a blocklist lmao. Like trying to make a steering wheel that won’t let you drive to bike shops because you think cyclists are too left leaning. Just a totally nonsensical concept
Also, to make it worse, it’s open source software, but the blocklist isn’t in the software. When you start up the software, it downloads a specific file (not in the open code) that has the block list.
There are a few open blocklists too though, like normal. You can turn those on or off at will. But not this secret one.
So yeah, it’s 100% malicious.