SHARE
TWEET

Panic over /j/ leak on /q/

a guest Apr 26th, 2015 206 Never
  1. Panic over /j/ leak on /q/
  2.  
  3. (16:56:22) +AoC: https://images.4chan.org/q/src/1375224484154.png I don't remember this being leaked before
  4. (16:56:47) +Spitch: That's not good
  5. (16:56:50) +AoC: sound the alarms, McNuggets is compromised
  6. (16:56:58) +Spitch: Rapeape?
  7. (16:57:09) +azatsu: Shti
  8. (16:57:14) +azatsu: How did this get leaked?
  9. (16:57:26) +AoC: https://boards.4chan.org/q/res/710551#p710975
  10. (16:57:27) +Spitch: Well someone just fucked Mcnuggers over
  11. (16:57:39) +azatsu: This is really bad actually
  12. (16:57:58) +azatsu: Someone autistic enough will search the whole archive for that ID and start associating a lot of things
  13. (16:58:05) +AoC: I'm just happy that none of the /q/ archives have lookup by ID
  14. (16:58:12) +azatsu: Yeah, but still
  15. (16:58:18) +Spitch: People will make the time
  16. (16:58:20) +AoC: yeah, massive trail
  17. (16:58:24) +azatsu: Where is that, AoC?
  18. (16:58:27) +Scrubadour: fucking sound the alarm
  19. (16:58:29) +Spitch: Should we alert the moot since rapeape appears to be AFK?
  20. (16:58:34) +Cadfael: yeah I saw it in /sp/ first
  21. (16:58:35) » Join: relare (~relare@Rizon-18518C94.washdc.fios.verizon.net)
  22. (16:58:35) » ChanServ (+v) relare
  23. (16:58:36) +AoC: azatsu https://boards.4chan.org/q/res/710551#p710975
  24. (16:58:41) +Scrubadour: mvb ALTERNATIVE
  25. (16:58:42) +azatsu: MVB Alternative moots Zephro
  26. (16:58:49) +JamesIha: MOOT MOOT MOOT
  27. (16:59:01) +azatsu: >german janitor
  28. (16:59:02) +azatsu: ?
  29. (16:59:08) +Cadfael: just checked and yeah someones screencapped that thread
  30. (16:59:20) +Spitch: Did we fire someone yesterday or something?
  31. (16:59:34) +azatsu: The last ones were ATIWAB and memo I think
  32. (16:59:37) +azatsu: and ATIWAB was american
  33. (16:59:44) +azatsu: Or at least I'm pretty sure about it
  34. (16:59:58) +Scrubadour: fsdfdsf kami' WalterWhite we have a leak in /q/
  35. (17:00:07) +AoC: http://archive.foolz.us/sp/thread/38204616/#38208213
  36. (17:00:09) +Cadfael: http://archive.foolz.us/sp/thread/38204616/#q38208213 this was where it was originally posted and a br'd the guy for impersonation
  37. (17:00:12) +AoC: found the source
  38. (17:00:24) +azatsu: In fact it is not impersonation
  39. (17:00:26) +azatsu: But it is leak of identity
  40. (17:00:33) +Spitch: Indeed
  41. (17:00:43) +AoC: do we even have german janitors now?
  42. (17:00:43) +azatsu: Why did he do this anyway, what the hell
  43. (17:00:47) +azatsu: He could have just told us
  44. (17:00:51) +azatsu: He was mad about something
  45. (17:01:12) +Troid: fuck.
  46. (17:01:30) +Cadfael: >I got the screenshot from sportschan. I have no idea who the janitor is.
  47. (17:01:39) +Spitch: Nuggers probably should change his IP now, or does that even work on /q/?
  48. (17:01:54) +AoC: yeah, but his is pretty static
  49. (17:01:58) +Scrubadour: yeah changing IPs would mean he's got a new ID
  50. (17:01:59) +azatsu: If anyone develops a script for searching
  51. (17:02:04) +azatsu: I'd recommend not posting on /q/ at all
  52. (17:02:13) +Troid: McNuggets's ID is 100% static
  53. (17:02:16) +Troid: unfortunately
  54. (17:02:18) +azatsu: since he has posted so much that he can most likely be identified by the way he writes
  55. (17:02:26) +azatsu: I can spot AoC in a single second in /jp/ threads
  56. (17:02:30) » Quit: +relare (~relare@Rizon-18518C94.washdc.fios.verizon.net)
  57. (17:02:32) +azatsu: Of /q/
  58. (17:02:40) +AoC: http://boards.sportschan.org/sp/res/40418.html
  59. (17:02:42) +Spitch: Yeah, he does post frequently
  60. (17:02:44) +AoC: found the source
  61. (17:02:56) +azatsu: Who is this guy
  62. (17:03:26) +azatsu: It can't be memo
  63. (17:03:40) +azatsu: Since he was /mu/
  64. (17:03:48) +Spitch: It's an odd screencap to make
  65. (17:03:58) +azatsu: Any ideas AoC?
  66. (17:04:51) +JamesIha: wasn't ATIWAB /sp/?
  67. (17:05:14) +Spitch: No he was /fit/
  68. (17:05:26) +azatsu: Sixtus
  69. (17:05:33) +azatsu: I haven't seen him in a long time
  70. (17:05:34) +JamesIha: ah nvm then
  71. (17:05:35) +Cadfael: As far as Im aware only me and AoC are on /sp/
  72. (17:05:36) %yournamehere: /sp/ has had only two janitors ever
  73. (17:05:45) %yournamehere: oh AoC I forgot
  74. (17:05:48) %yournamehere: sorry bro!
  75. (17:06:03) +azatsu: I don't have any other suspicions aside of him
  76. (17:06:03) +JamesIha: well could it have been this guy ? https://sys.4chan.org/j/res/2254#p2694
  77. (17:06:07) +AoC: it's probably not the actual janitor, but someone in contact with one
  78. (17:06:10) +Spitch: I don't think this would have been sixtus
  79. (17:06:14) +AoC: that provided old screenshot
  80. (17:06:21) +AoC: anyway, trip lookup gives this
  81. (17:06:22) +AoC: http://archive.foolz.us/_/search/tripcode/%21DwgeSpOOKY/page/4/
  82. (17:06:33) +AoC: and I'm sure we'd know a fairly active tripfag janitor
  83. (17:06:59) +azatsu: I can't think of anyone else
  84. (17:07:02) +Spitch: >i got the screenshot from sportschan
  85. (17:07:07) +Troid: what a time for RapeApe to be away
  86. (17:07:14) +Troid: is the /q/ thread gone at least?
  87. (17:07:26) +AoC: Spitch, already posted the sportschan source thread
  88. (17:07:44) %yournamehere: that trip was never an /sp/ janitor
  89. (17:07:54) +Spitch: Oh, I didn't see
  90. (17:07:55) +azatsu: the thread on /q/ is ok
  91. (17:07:58) +azatsu: except for the leak post
  92. (17:08:28) +azatsu: I can't think of anyone other than sixtus, honestly
  93. (17:08:53) %yournamehere: fuck, MRQ's code leaked
  94. (17:08:56) +Spitch: Sixtus is the inactive /int/ janitor, I don't really see why it would be him
  95. (17:08:57) %yournamehere: I just realized that
  96. (17:08:59) +Spitch: Yeah
  97. (17:09:04) +Spitch: That's the biggest issue
  98. (17:09:09) +azatsu: Because there were very few /int/ janitors
  99. (17:09:12) +azatsu: and he was one of them
  100. (17:09:14) +azatsu: nikka only did /int/
  101. (17:09:17) +Spitch: He's very active on /q/
  102. (17:09:17) +azatsu: Who else would it be?
  103. (17:09:53) +Spitch: It's possible that any of us could have given the shot to someone else/uploaded it to sportchan and so
  104. (17:09:55) » Quit: ~moots (~moots@the.run) (Remote host closed the connection)
  105. (17:10:06) +Spitch: why do u leave in our time of need ;-;
  106. (17:10:10) +AoC: It's fair to assume that the "mu int and sp" thing is throwing us off since the poster tripcode is not linked to us
  107. (17:10:30) +azatsu: Thing is, someone clearly has a gray name on /j/, which leads to the suspicion that he was most likely the one with the leaks
  108. (17:10:34) +azatsu: even if he did not leak
  109. (17:10:41) +Cadfael: I dont think its nikka, he was fired before the 5/29/13
  110. (17:10:45) +azatsu: It's not nikka
  111. (17:10:56) +azatsu: Nikka never gave a fuck about /sp/
  112. (17:11:20) +Troid: yournamehere, no luck getting a manager's attention?
  113. (17:11:23) +azatsu: So I can imagine that the tripfag had contact with this ex-janitor, which in turn told him he was a janitor for /int/, /v/, and /sp/
  114. (17:11:45) @RapeApe: i'm here.
  115. (17:11:46) +Confederate: It's not nikka, he was fired months ago. This screenshot is recent
  116. (17:11:53) +Spitch: Oh good
  117. (17:11:59) +AoC: may 29
  118. (17:12:05) +Spitch: https://boards.4chan.org/q/res/710551#p710975
  119. (17:12:08) +Spitch: So you don't have to scroll
  120. (17:12:15) +azatsu: The only person that janitored /int/ and possibly /sp/ would possibly be sixtus
  121. (17:12:16) +AoC: with the int report being in feb 25
  122. (17:12:17) @RapeApe: i'm looking at it.
  123. (17:12:45) +azatsu: I'm not saying it was him, just that I don't remember anyone that janitored /int/, and possibly /sp/ too
  124. (17:13:08) +azatsu: Also it's been a long time since he showed up here
  125. (17:13:35) » Join: nemo (~nemo@Rizon-65EE049C.hsd1.ma.comcast.net)
  126. (17:13:35) » ChanServ (+v) nemo
  127. (17:14:03) @RapeApe: sixtus's account was terminated a long time ago
  128. (17:14:28) +azatsu: It's anothe person then?
  129. (17:14:30) +azatsu: I see
  130. (17:14:47) +AoC: I'm happy I found out about this first
  131. (17:14:55) +AoC: because the profile just fucking screams me
  132. (17:15:13) +azatsu: Well, moot personally said that you were fired
  133. (17:15:18) +azatsu: Indirectly, yes
  134. (17:15:41) +azatsu: And you don't demonstrate any kind of erratic behaviour that could possibly lead to this conclusion
  135. (17:16:02) +azatsu: Also you never used emoticons as a tripfag
  136. (17:16:54) » Join: McNuggets (~McNuggets@9F75A1A7.32C1C13.19ABDAC4.IP)
  137. (17:16:55) » ChanServ (+v) McNuggets
  138. (17:17:04) +McNuggets: evenin'
  139. (17:17:08) +AoC: !
  140. (17:17:19) +AoC: McNuggets you better lay low
  141. (17:17:23) +Spitch: Who wants to tell him
  142. (17:17:25) +McNuggets: hmm?
  143. (17:17:30) +Spitch: https://boards.4chan.org/q/res/710551#p710975
  144. (17:17:32) +Spitch: Take a gander
  145. (17:17:36) +Troid: somebody posted a /j/ screencap which includes your ID
  146. (17:17:41) +AoC: your cover is blown
  147. (17:18:00) +McNuggets: rofl, well I didn't blow it :P
  148. (17:18:11) +Spitch: What an optimist
  149. (17:18:24) +AoC: anyway, the lesson here people is
  150. (17:18:30) +Troid: your janitor position isn't in any danger, just your /q/ ID
  151. (17:18:35) +AoC: this is why nobody posts nicknames in /j/
  152. (17:19:18) +azatsu: I just wonder why this janitor would even screencap /j/ stuff
  153. (17:19:29) +Troid: yournamehere, are you still around?
  154. (17:19:31) +McNuggets: Beats the hell out of me. *shrug*
  155. (17:19:40) %yournamehere: yeah
  156. (17:19:54) +AoC: ammo for when inevitably fired?
  157. (17:19:55) +Troid: can you ban and wipe https://boards.4chan.org/e/res/1601750 for CP spam
  158. (17:20:41) %yournamehere: done
  159. (17:20:56) +Troid: thanks
  160. (17:21:14) %yournamehere: McNuggets: I wouldn't worry. Find a new IP to post on /q/ with
  161. (17:21:16) +azatsu: I thought we would never have to deal with this kind of person
  162. (17:21:30) +McNuggets: So is there a betting pool on how long it takes before someone notices/calls it out?
  163. (17:21:42) +Troid: I'm amazed no one has yet
  164. (17:21:48) %yournamehere: ^
  165. (17:21:53) +AoC: differing interest pools
  166. (17:22:06) +AoC: the ones that tend to argue with MQr are not the same freesp
  167. (17:22:27) +azatsu: What I worry the most honestly is the script being developed, /jp/sie searches for that ID, starts blaming and quoting everything you say in every stance to shitpost
  168. (17:22:33) +azatsu: However, this would grow old in a few months
  169. (17:22:59) +McNuggets: Eh, I can post from my cell if there's something important on /q/ I wanna bitch at someone about.
  170. (17:23:02) +Troid: unfortunately foolz is likely going to implement a search by ID eventually
  171. (17:23:15) +AoC: this is worst case scenario. Best, it's treated as a novelty without value for the discussion due to the lack of followup
  172. (17:23:16) +Troid: but, uh, at least /jp/sies are split between that and warosu?
  173. (17:23:19) +AoC: from the leak source
  174. (17:23:34) +azatsu: Well, they could have guessed dongfix was a mod by the leak of the extension
  175. (17:23:40) +azatsu: But they weren't able to
  176. (17:23:49) +McNuggets: Of course, I'm not the only "MQr" on /q/ ... there's a purple named fellow who posts now and then.
  177. (17:23:55) +azatsu: And anyways, he had + on #4chan for a long time anyway
  178. (17:23:59) +Troid: lol
  179. (17:24:00) +azatsu: *in any case
  180. (17:24:14) +azatsu: How famous are you on /q/, McNuggets?
  181. (17:24:14) +AoC: did that other MQr post about the garden though?
  182. (17:24:31) +Troid: azatsu: probably one of about two most recognized IDs
  183. (17:24:32) +McNuggets: Oh, true ... guess he didn't
  184. (17:24:43) +McNuggets: but yeah I'm pretty well known on /q/ ... static IP
  185. (17:24:44) +azatsu: Well, don't worry about your identity as a whole
  186. (17:25:02) +azatsu: Just that if everything goes wrong, we'll have to deal with /jp/ being awfully autistic about your statements
  187. (17:25:23) +Troid: I don't agree with that post being left there any longer than it needs to be
  188. (17:25:31) +AoC: on the contrary
  189. (17:25:33) +azatsu: If we take it down someone might notice
  190. (17:25:36) +Troid: if you don't want to create a scene by deleting it or the thread, then permasage
  191. (17:25:41) +AoC: quick removal would mean that it's not only true
  192. (17:25:46) +azatsu: And thus the screenshot will be confirmed as legit
  193. (17:25:47) +AoC: but that we're panicking about it
  194. (17:25:49) +Troid: no one ever notices permasage
  195. (17:26:08) +azatsu: The decision taken by mods is comprehensible, we must not let them now that we're worried about this
  196. (17:26:20) +Troid: OPs who post with "fur" in the OP on /q/ don't even notice their own threads sinking
  197. (17:26:22) +azatsu: And honestly, it's no big deal, and if anything, will affect only one board
  198. (17:26:54) +Troid: I know - I'm not saying we should remove it because it has McNugget's ID, but because it's a /j/ screencap
  199. (17:27:12) +azatsu: What I do not like to know is that after so much security and reinforcement we still need to deal with leaks by members of the team
  200. (17:27:24) +Troid: and in this case, having that post there doesn't help up pinpoint the leak
  201. (17:27:36) +McNuggets: Fortunately, the vast majority of /jp/ stays far away from /q/. I'm not really worried about fallout. Of course if a Mod wants to plant the seed of ">2013 >believing fake screencaps", I wouldn't complain. ;)
  202. (17:27:41) +AoC: azatsu welcome to why the admission process is so obscure and slow
  203. (17:28:18) +McNuggets: Do we know who made the screencap?
  204. (17:28:25) +AoC: we do not
  205. (17:28:36) +Troid: not us lowly janitors, anyway, GrapeApe might have a better idea
  206. (17:28:41) +Troid: it's kind of irrelevant now
  207. (17:28:47) +McNuggets: True
  208. (17:29:11) +AoC: yeah, whoever it was is no longer in a position to continue providing information
  209. (17:29:14) +AoC: http://boards.sportschan.org/sp/res/40418.html
  210. (17:29:36) +AoC: and furthermore, they seem to not be concerned by lobbing destructive intel
  211. (17:30:01) +AoC: since the cap was just "proof" rather than "I know all the names and will be dropping them like they're hot"
  212. (17:30:58) +VCR_Working: what happened
  213. (17:31:07) +McNuggets: I done got outted. XD
  214. (17:31:15) +VCR_Working: well yah
  215. (17:31:24) +VCR_Working: but i mean what's goin on now
  216. (17:31:36) +McNuggets: Oh, we're just sort of speculating potential fallout
  217. (17:32:00) +AoC: this too shall pass
  218. (17:32:22) +McNuggets: Ayup
  219. (17:32:24) +VCR_Working: used to be huh..
  220. (17:33:06) +VCR_Working: i don't recall there being any janitors with that specific overlap
  221. (17:33:06) » Join: relare (~relare@Rizon-18518C94.washdc.fios.verizon.net)
  222. (17:33:06) » ChanServ (+v) relare
  223. (17:33:40) +McNuggets: ah well ... afk a bit. tacos calling!
  224. (17:34:06) +VCR_Working: part of me senses this is atiwab butthurt
  225. (17:35:25) @RapeApe: it was sixtus
  226. (17:35:28) +AoC: as much as the profile fits due to recency of events and his tendency to leak intel, I doubt it
  227. (17:35:33) +VCR_Working: oh
  228. (17:35:37) +AoC: there we go
  229. (17:35:38) +VCR_Working: welp
  230. (17:35:45) +Spitch: How do you know Rapey?
  231. (17:35:50) @RapeApe: he's already fired, so not much can be done
  232. (17:35:53) +Spitch: IP's matched?
  233. (17:36:06) » Quit: +relare (~relare@Rizon-18518C94.washdc.fios.verizon.net)
  234. (17:36:23) +Troid: with that thread off page 0 already, I don't think you could go wrong with just permasaging it
  235. (17:37:09) +VCR_Working: i forget, what was he canned for again
  236. (17:37:41) +Spitch: Inactivity I believe
  237. (17:37:43) » Join: relare (~relare@Rizon-18518C94.washdc.fios.verizon.net)
  238. (17:37:43) » ChanServ (+v) relare
  239. (17:37:57) +AoC: <+sixtus>      i like being a janitor
  240. (17:37:58) +AoC: <+sixtus>      i hope im doing everything right
  241. (17:37:58) +AoC: breaks your heart
  242. (17:38:17) +Spitch: D'awwh
  243. (17:38:22) +McNuggets: awwww
  244. (17:38:44) » Quit: +relare (~relare@Rizon-18518C94.washdc.fios.verizon.net)
  245. (17:38:47) +McNuggets: Well that's kind of a good sign ... I don't think he ever knew which boards I Jani
  246. (17:38:49) +Spitch: #janifeels
  247. (17:41:42) +McNuggets: Looking at it all, it doesn't look like it was malicious either. My outting appears completely accidental. *shrug*
  248. (17:41:58) +Spitch: Yeah, I'm sure he had nothing against you.
  249. (17:42:30) +Cadfael: idgi though whats his connection to some tripfag on /sp/, surely theyre not the same person
  250. (17:42:51) +McNuggets: I'd give this one my bad for mentioning my /q/ ID on /j/ since my IP never changes.
  251. (17:43:26) +AoC: casually mentioning to an internet friend you have more free time now because you no longer have to janitor since you were let go a while ago
  252. (17:43:34) +AoC: bullshit they say, prove it
  253. (17:43:56) +AoC: since you were pretty inactive, you just have a couple of amusing caps you took for your own because you found them funny
  254. (17:44:13) +AoC: friend goes cool and saves them
  255. (17:44:45) +AoC: weeks later, said friend is bored in the sp shitposter board and decides to have some fun by impersonating a janitor
  256. (17:45:10) +AoC: with the little secret data he has. Namely, a couple caps and the address of the jani board
  257. (17:45:19) +Troid: I'm also at fault for bringing up that /q/ post in the first place
  258. (17:45:40) +Troid: a little bit of identifiable information sneaks onto /j/ here and there, which would be fine if we could rely on its secrecy
  259. (17:45:51) +AoC: second random poster sees thread, impersonates in sp thread, and it keeps trickling
  260. (17:46:06) +AoC: at no point nobody realizes the weight of the information in the image
  261. (17:47:23) +VCR_Working: it's going to hit eventually
  262. (17:48:12) +Scrubadour: maximum. damage. control.
  263. (17:48:27) +Troid: of all the people it could have been, it's pretty unfortunate
  264. (17:48:37) +Cadfael: yeah I guess it may have played out like that, i mean its quite strange. And yeah I saw it first on /sp/ and just thought it was a fake mock up so my bad, but then i remembered that jani humour thread and the panel about the /sp/ jani
  265. (17:48:41) +Troid: I thought I had a totally static IP and it changed a few weeks ago
  266. (17:49:08) +McNuggets: Well, I specifically pay for a static IP, so it better not change without notification.
  267. (17:49:13) +VCR_Working: lol
  268. (17:49:31) +McNuggets: But, like I said, the cell phone and tablet are options and they don't sit on the same IP.
  269. (17:49:38) +McNuggets: or I could just proxy
  270. (17:49:43) +Scrubadour: you runnin' some sorta VPN?
  271. (17:50:04) +Troid: you could possibly release your current one and just pay for another, static one
  272. (17:50:13) +AoC: well, our fears are more about retroactive recognition rather than future, but I'm sure it won't be that bad
  273. (17:50:43) +McNuggets: fortunately, there's no indication there of which boards I Jani, so anyone could be MQr's victim! muhahah!
  274. (17:50:46) +AoC: specially since at no point it shows what boards you janitor
  275. (17:51:37) » Part: +AoC (AoC@ministry.of.arcane.knowledge) ((ノ ゚Д゚)ノ ======= ┻━━┻)
  276. (17:51:54) » Join: AoC (AoC@ministry.of.arcane.knowledge)
  277. (17:51:54) » ChanServ (+v) AoC
  278. (17:51:59) +VCR_Working: lol
  279. (17:52:04) +AoC: wrong window ctrl+w
  280. (17:52:35) +Scrubadour: someone has to recognize it AND write a search script
  281. (17:52:46) +Scrubadour: my money's on /g/
  282. (17:53:12) +Troid: I don't get what you guys mean by search script
  283. (17:53:30) +Troid: /q/ is archived, but a search script isn't going to help you unless it's implemented by the people running the archive
  284. (17:53:57) +Troid: unless you want to crawl every single page on a slow archive (they're all slow) to scan for an ID
  285. (17:54:26) +Scrubadour: >not crawling the archives
  286. (17:54:30) +Scrubadour: i shiggy diggy
  287. (17:54:55) +Scrubadour: i've been meaning to for completely wholesome analysis reasons, but haven't gotten to it yet
  288. (17:58:09) » Join: Alkaid (~Alkaid@AED33985.C751EDFB.8AC8D7C4.IP)
  289. (17:58:10) » ChanServ (+v) Alkaid
  290. (18:00:27) +azatsu: Oh so it was him
  291. (18:00:33) +azatsu: Spot on I guess
  292. (18:01:33) +azatsu: Shame though, I remember he was quite a nice person here
  293. (18:02:56) +McNuggets: ooh ... if someone does notice my ID there and points it out and raises a stink, can I go in there and post "Holy shit fuck that nigger janitor tryin' to take credit for my post!"
  294. (18:03:16) +Troid: not in that thread
  295. (18:03:31) » Join: duanemoody (~duanemood@blah.blah.blergh)
  296. (18:03:31) » ChanServ (+v) duanemoody
  297. (18:03:32) +Troid: it's already permasaged, I believe, and if not, it's best to leave it alone
  298. (18:03:39) +yetsturdy: huh
  299. (18:03:46) +Troid: I think it would be asusing if it comes to somebody actually making a thread about that post and calling you out, though
  300. (18:03:50) +Troid: *amusing
RAW Paste Data
Top