SHARE
TWEET

everything of relevance from 16 december 2012

a guest Aug 25th, 2015 5 Never
  1. ==16th December 2012==
  2.  
  3. '''Tripfag holocaust and technical problem with Regular Expressions'''
  4.  
  5. (10:54:36) +Kazisho: https://boards.4chan.org/q/res/332900
  6. (10:56:18) +fsdfdsf: lol
  7.  
  8. (15:09:00) +AoC: dongfix Manly Tears alert
  9. (15:09:02) +AoC: https://boards.4chan.org/v/res/167110631#p167113021
  10. (15:09:49) %dongfix: ty
  11. (15:09:58) +fsdfdsf: I can't work miracles over here, lately the spamming hasn't been so bad on /a/ at least. They have laid off a bit on chapter release day.
  12. (15:14:36) +fsdfdsf: Beamu has been helping a bit on chapter release day, he comes and deletes dubs
  13. (15:18:11) %dongfix: i banned him AoC
  14. (15:18:18) %dongfix: just need to wait till he comes back once again
  15. (15:18:57) +AoC: Cool, I'll keep an eye out
  16. (15:19:04) +AoC: this one was particularly sneaky
  17. (15:19:32) +fsdfdsf: It's funny yet not that Kronie switched to the Rei trip
  18. (15:20:07) +AoC: I saw him active today under Kronie
  19. (15:20:25) +fsdfdsf: His trip is the Rei trip with Kronie as the name
  20. (15:20:37) +AoC: ah
  21. (15:21:00) +fsdfdsf: He's right, he knows we can't trip ban him now
  22. (15:21:12) +fsdfdsf: Cause if we trip ban him we'll get a couple thousand with him
  23. (15:21:21) +AoC: pssshaw
  24. (15:21:24) +fsdfdsf: Maybe not that many but a few
  25. (15:21:30) VCR_Working: WELL THAT'S WHAT THEY GET FOR USING A PUBLIC TRIPCODE
  26. (15:21:39) +AoC: didn't we already mass ban the first Rei#clones ?
  27. (15:21:41) +fsdfdsf: Hey I'm all for it
  28. (15:21:48) +fsdfdsf: There's people using it that don't even know how it started
  29. (15:22:08) +fsdfdsf: No Rei#clones is not banned
  30. (15:22:23) +fsdfdsf: #clones is what kronie is using
  31. (15:22:47) +fsdfdsf: I think public trips can be fun though
  32. (15:22:54) +fsdfdsf: There's a lot of people who are stupid and think Rei is one person
  33. (15:23:14) VCR_Working: the problem is the faggots who hide behind it
  34.  
  35. (15:40:38) +fsdfdsf: I really need to stop reading /q/, it brings me down every fucking time
  36. [...]
  37. (15:51:15) +Azatsu: it's been a long time since I've seen m00t replying to anything that's not tech or whole 4chan related on /q/
  38. (15:51:19) +Azatsu: Like, very specific board problems
  39. (15:51:45) +Azatsu: so you shouldn't worry, and well, the problems that people complain about /a/ are problems that, just like almost every single board specific problem, can only be fixed with more janitors, and that's being provided
  40. (15:54:38) +Azatsu: fsdfdsf have you ever bought an anime BD?
  41. (15:54:48) +Azatsu: I might buy the first volume of nekomonogatari
  42. [...]
  43. (16:01:21) +fsdfdsf: Azatsu I don't have any BD but I do have DVDs and I bought them off amazon
  44. [...]
  45. (16:01:38) +fsdfdsf: And you're right about the /q/ stuff
  46.  
  47. (17:10:05) +Bloom: https://boards.4chan.org/v/res/167144517
  48. (17:10:07) +Bloom: pfffhhahhahhaha
  49. (17:10:13) +Bloom: what a fucking dumbass
  50. (17:25:12) +Beam: He is so mad
  51. (17:34:14) +Aerolite: https://boards.4chan.org/v/res/167144517#p167152482
  52. (17:34:18) +Aerolite: especially right here
  53.  
  54. (18:58:50) +AoC: I know this goes against moot's policy of janitor's not being able to tell samefag, but I think that a tagging system would be more useful than BR alone. Instead of forcing ban evaders under new names and resetting IP, just let them carry on except that now we have a "This poster is tagged for ban evasion, delete everything until he gets frustrated"
  55.  
  56. (21:01:49) +AoC: Be warned that there's some sort of exploit that leaves spoiler tags applied to the rest of the page
  57. (21:01:59) BluRay: fun
  58. (21:02:02) +AoC: moot mvb dongfix
  59. (21:06:11) +AoC: BR as Privilege rule for now and try to contain it
  60. (21:13:49) +horsemilk: AoC: give a link to an example of that, please
  61. (21:14:03) +fsdfdsf: I just saw it
  62. (21:14:08) +fsdfdsf: The spoilers go all over the page
  63. (21:14:12) +fsdfdsf: don't know what's up
  64. (21:14:28) +Beam: >>>> is it apparently
  65. (21:14:39) +horsemilk: I tried to find something like that a while ago, but couldn't do it quick enough to keep interest.
  66. (21:14:46) +fsdfdsf: Beam has it
  67. (21:14:47) +horsemilk: nested bbcode is always a big source of bugs.
  68. (21:14:50) +fsdfdsf: Pretty sure that's it
  69. (21:14:55) +AoC: that's just how it's parsed, but I'll try to find a living example
  70. [...]
  71. (21:21:05) +fsdfdsf: This needs to get fixed
  72. (21:21:13) +fsdfdsf: People are doing it to try and destroy threads
  73. (21:22:33) +AoC: /v/ already got the hint and is reporting every instance
  74. (21:24:46) +horsemilk: yeah
  75. (21:24:59) +horsemilk: this could lead to xss.
  76. (21:25:13) +horsemilk: it's all three of those things; greentext, whatever >>> linking is called, and spoilers.
  77. (21:25:46) +horsemilk: these things need to be done with a proper parser; regex doesn't cut it.
  78. (21:27:59) +Beam: annnd now I gotta go
  79. (21:28:04) +Beam: worst fucking timing ever
  80. (21:28:13) +horsemilk: ah
  81. (21:28:20) +fsdfdsf: Should we ping them again AoC?
  82. (21:28:29) +horsemilk: the first > of the closing </span> is being taken as part of the >>>
  83. (21:29:17) +AoC: sent a PM to moot, let's see how that goes
  84. [...]
  85. (21:55:44) ~moot: dongfix changed the way the quote regexes work
  86. (21:55:49) ~moot: i disabled posting for now
  87. (21:56:19) +AoC: yay we get to sleep
  88. (21:56:29) +fsdfdsf: Glorious admin
  89.  
  90. (21:57:01) +horsemilk: moot: is it possible to enable posting only on /j/ so I can play with this?
  91. (21:57:10) ~moot: no
  92. (21:57:22) +horsemilk: can I look at the formatting code, then? :3
  93. (21:59:12) +duanemoody: can i have the keys to the car
  94. (21:59:32) +duanemoody: and or the regex dong wrote
  95. (21:59:35) +horsemilk: duanemoody: I doubt posting will be enabled until this is fixed, so looking at the code isn't dangerous.
  96. (21:59:48) +duanemoody: that's my point
  97.  
  98. (23:37:20) +AoC: still doing a bit of fallout cleaning in /v/
  99. (23:37:34) +AoC: the board was active before sp, tv and a so they took refuge there
RAW Paste Data
Top