Conversation

Notices

1. djsumdog (djsumdog@djsumdog.com)'s status on Thursday, 24-Oct-2024 03:23:13 JST djsumdog
   The DeVault Report:
   
   https://dmpwn.info/
   
   It looks like @drewdevault, the coward who secretly authored (and tried to deny authorship) of the Stallman Report is now trying to nuke every part of his past.
   
   The DeVault Report contains tons of archived links showing Drew is super into lolis, like crazy into lolis. He's written bots/scrapers and image hosts just for his loli addiction.
   
   He accused Stallman of defending potatophiles, and yet DeVault's own reddit history shows him constantly defending nonces.
   • xianc78 likes this.
   • Matt Hamilton (eriner@noauthority.social)'s status on Thursday, 24-Oct-2024 03:29:10 JST Matt Hamilton

     in reply to

     @djsumdog

     > Those who live in glass houses should not throw stones

     xianc78 likes this.
   • menherahair (menherahair@eientei.org)'s status on Friday, 25-Oct-2024 09:17:04 JST menherahair

     in reply to
     @djsumdog >secretly authored (and tried to deny authorship)
     given the benefit of the doubt, was this ever proven? he could just host it for someone
   • djsumdog (djsumdog@djsumdog.com)'s status on Friday, 25-Oct-2024 09:17:07 JST djsumdog

     in reply to

     • menherahair
     Yes. The DNS A records for the stallman report website were the same as his blog at one point. Not sure if it's in the report, but someone also queried his blog's IP address with the stallman report host and was given back a LetsEncrypt certificate for Stallman Report draft site:
     
     https://archive.ph/4yGYf
     
     So I think it's clear he's behind it. Even if he didn't write all of it, he certainly helped and hosted it, and in the HackerNews thread he pretended it was someone else's report he wasn't involved with.