Omnipotent

PomPomPurin

Mar 19th, 2023
662
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 4.43 KB | None | 0 0
  1. -----BEGIN PGP SIGNED MESSAGE-----
  2. Hash: SHA512
  3.  
  4. Just wanted to make this public and you make your own conclusions based on this information, you will have to take my word on these facts. The only evidence I have is an email delivery report (I didn't keep the PGP encrypted message on my side).
  5.  
  6. 1. On the 15th of March I emailed pompompurin and contacted him over other platforms, all PGP encrypted warning him that his identity was known to law enforcement and asking if he would delete my BF account.
  7.  
  8. 2. He was then arrested around the same timing of my email, if he was allegedly arrested a couple hours before I would have no way of knowing as his arrest wasn't reported until recently. Vincent Canfield can verify the validity of my delivery report (he owns cockmail).
  9.  
  10. My thoughts: The feds usually only file an arrest warrant once they have enough dirt on you that they are satisfied, I feel like the arrest warrant on Pom was premature, they could gather more charges having known his identity. The arrest warrant seemed quite flimsy, 1 conspiracy charge. I am assuming a much larger case will appear within the next few months. It could be pure coincidence that I emailed Pom about the LE knowing him and he was arrested the same day, it could be that he had been working with them for an unknown amount of time and that my email scared them (tbh I doubt it but there's many possibilities). I just think it's all a little suspicious. Also reading the information, why the fuck would Pom speak to the feds admitting his username and shit? Everyone knows you don't talk to the feds, if you want cooperation sentence reduction you do that through plea deals.
  11. -----BEGIN PGP SIGNATURE-----
  12.  
  13. iQKTBAEBCgB9FiEECogno842/WIsJjnCusnASMulpNgFAmQXIulfFIAAAAAALgAo
  14. aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDBB
  15. ODgyN0EzQ0UzNkZENjIyQzI2MzlDMkJBQzlDMDQ4Q0JBNUE0RDgACgkQusnASMul
  16. pNi3HQ/9EgY+Qi2vaDPXuePOQYbIigl/+xcKs1YUSQ1yAHHZLKB9sg6iJ+Al1i7/
  17. pSvtkDSjUuKLSc6Msto8gBi9kYES0SjGRYf76e8gWPf+VFsuOOqs4cFpfrgiLV3U
  18. VLv9NgqyyjZgXnInCevcPfcHx75G/FvG+rwCvu7JL7joRvp6TvFMyMdPcFVAcBrq
  19. 3Ug77xkAGS/4UgP8lwHz8AqF2n+R2Bv3luJRD8fffkqqdYC3vfTAm90seRC6IJa8
  20. a08ble+rsB08OmzlsUfqhz9kxQ6HUsirQQ2pTXxyMkDOYQ4DXbM4+9V7j1JXwnai
  21. KqFgCgw8jMwqJIIHPZWlTTMgO02AHu9ffJo95ntH6ilwou+P03V37H3/9PPWvoMF
  22. ssiPt45DI8Msnj4E4YX1nvXlPxNVi4c0Sb2xreSllLbbstdsDpeAkJlnuIK1fbcd
  23. RpNESqjApJYixVU8R++sSty21HfboCmaqS/9sJHansPC1z83yufHBwR7TIiQJ27c
  24. 70fJA9wiyupjxNUsFVvWBhj8g4+bqosAQUTBKzO07h/1yBrnGkICgsy1IknvvKhx
  25. iano0Xyj72fG3nrt6/TkY28eEaxAlMDvyee1BsrqpfRBsHkPEgDWBP4Zsa5p6Iew
  26. PJ/QFcdSIsLXFEKLRtedu1yqQfZ2GvCX5s3d+0T0fZv0aniANMc=
  27. =QSOq
  28. -----END PGP SIGNATURE-----
  29.  
  30. ////////////////////////
  31.  
  32. Email Delivery Report:
  33. This is the mail system at host mail.cock.li.
  34.  
  35. Your message was successfully delivered to the destination(s)
  36. listed below. If the message was delivered to mailbox you will
  37. receive no further notifications. Otherwise you may still receive
  38. notifications of mail delivery errors from other systems.
  39.  
  40. The mail system
  41.  
  42. <pom@pompur.in>: delivery via mail.protonmail.ch[176.119.200.128]:25: 250 2.0.0
  43. Ok: queued as 4PcNsD4cdfz9vNQm
  44. Reporting-MTA: dns; mail.cock.li
  45. X-Postfix-Queue-ID: 8AE59240FA5
  46. X-Postfix-Sender: rfc822; omnipotent@cock.li
  47. Arrival-Date: Wed, 15 Mar 2023 21:32:26 +0000 (UTC)
  48.  
  49. Final-Recipient: rfc822; pom@pompur.in
  50. Original-Recipient: rfc822;pom@pompur.in
  51. Action: relayed
  52. Status: 2.0.0
  53. Remote-MTA: dns; mail.protonmail.ch
  54. Diagnostic-Code: smtp; 250 2.0.0 Ok: queued as 4PcNsD4cdfz9vNQm
  55. Return-Path: <omnipotent@cock.li>
  56. MIME-Version: 1.0
  57. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cock.li; s=mail;
  58. t=1678915946; bh=exF0xUxbV9zUE4EGEhcj1k7TulROdIHt2RasfJSSKWg=;
  59. h=Date:From:To:Subject:From;
  60. b=nPB8UwsvG8DuUl4j5MGc2iMzLKPcytH3TXPZA6uX2FxuQwamWJqAfPRMt5zFbHfuq
  61. a/f0EeG1sCupOdUBpSY78Kazjc+z0ccO1y1p4El1GtA1kpxuTTWXDIgNy0yHYMf1r6
  62. UN+QNZqB6JLvGKMOQpi32IHR/pQP4aVUN9nAOhn+HhOSLhS4BZkCz9ellH0PwP5uln
  63. aCU0bbEC7hlyxKoJQjI2hD+oD2IOAE7yVe51ohRJCG5BzRCy+BIWS7CVZU+3LSnUTG
  64. wWu078nVjyX2/N7QSXADb4MLIBPZSzsr2AfIF9wRvQ4EKwH01R3OCFKnXyM8cn4KdK
  65. yJYSLVjDUQqFw==
  66. Content-Type: text/plain; charset=US-ASCII;
  67. format=flowed
  68. Content-Transfer-Encoding: 7bit
  69. Date: Wed, 15 Mar 2023 21:32:26 +0000
  70. From: omnipotent@cock.li
  71. To: pom@pompur.in
  72. Subject: - Message from Omnipotent -
  73. X-Priority: 1 (Highest)
  74. Message-ID: <69a63f436e6ec7894ad2cd9352aa46a7@cock.li>
  75. X-Sender: omnipotent@cock.li
  76. User-Agent: Roundcube Webmail/1.3.17
Add Comment
Please, Sign In to add comment