Public Pastes
BitBucket - Backup your code in the cloud! Host unlimited private projects, for free. SIGN UP takes 10 seconds, and it's free!
SHARE
TWEET

Other Highlights from 4th March 2013

a guest Sep 27th, 2015 2 Never
  1. (11:22:17) +AoC: Going to need a block on https://www.youtube.com/watch?v=eVrmeAH89Rw
  2. (11:22:29) +AoC: latest Manly Tears video, feel free to not load it
  3. [...]
  4. (11:35:11) +Thesmothete: Manly tears is the same exact size as the bust
  5.  
  6. (16:50:48) +fsdfdsf: No! Awesome page screen. I've been logged out.
  7. (16:51:59) +nikka: eded
  8. (16:52:03) +nikka: enjoy
  9. (16:52:22) +nikka: we all were
  10. (16:52:24) +nikka: it seems
  11.  
  12. (18:09:59) +fsdfdsf: I wish we filtered lel
  13. [...]
  14. (18:11:57) +tjanster: We should filter people's excessive suggestions to filter.
  15. (18:12:33) +fsdfdsf: I also wish death upon the people in /sp/ that came up with it
  16. (18:12:36) +fsdfdsf: We should likely filter that too
  17.  
  18. (18:48:44) +Anikitan: i've been ban requesting the same guy for avatarfagging for... 7 months now
  19. (18:48:49) +Anikitan: and he still keeps at it
  20. (18:48:57) +Anikitan: some men just want to watch the world burn
  21. (18:49:37) +fsdfdsf: Anikitan maybe the world needs to burn a little
  22. (18:50:05) +Anikitan: not from a gay furry avatarfag it doesnt
  23. [...]
  24. (18:59:19) +duanemoody: [18:50:10] <+Anikitan>   not from a gay furry avatarfag it doesnt
  25. (18:59:23) +duanemoody: he sounds special
  26. (18:59:38) +Anikitan: a snowflake
  27. (19:00:11) +tjanster: Some men just want to watch the world yiff.
  28.  
  29. (20:14:14) +duanemoody: is there some way to retrieve the last, oh, fifty posts on a board without having to comb all the boards
  30. (20:14:39) +duanemoody: inb4 the normal page view
  31. (20:14:54) +AoC: archive
  32. (20:14:57) +AoC: probably
  33. [...]
  34. (20:16:01) +Anikitan: blank search on an archive works if your board has an archive
  35. (20:16:16) +duanemoody: GEE, IF ONLY WE WERE SOMEHOW CONNECTED TO THE GUYS WHO CODE THIS SITE
  36. (20:18:53) +duanemoody: seriously, if i had an API to give me the most recent post number I could code the rest
  37. (20:19:10) +duanemoody: /j/ has it but somehow the rest of the site doesn't
  38. (20:20:59) +AoC: wait, I think the public API added a board data thing last time
  39. (20:21:11) +duanemoody: yes, but it's obtuse as fuck
  40. (20:21:35) +duanemoody: i have to grab page zero, look for the top post that isn't a sticky, and dive for the last post in it
  41. (20:22:05) +duanemoody: THEN retrieve the last fifty posts from their post numbers which officially the API doesn't support
  42. (20:23:07) +AoC: isn't it better to just continuously poll page zero, collect the data of the replies and then sort them by descending post number?
  43. (20:23:32) +AoC: and yeah, the system is obscure because of inner php/sql shenanigans, the API is as good as it gets
  44. (20:24:07) +AoC: and dammit it's a lot better than what we had before, with clumsy scrappers that raped bandwidth
  45. (20:24:52) +duanemoody: the most i want from the API is 1) get OP post number from arbitrary post number
  46. (20:25:00) +duanemoody: 2) last X posts
  47. (20:25:23) +duanemoody: no matter how fucked the SQL is, requesting the last X posts has got to be easy
  48. [...]
  49. (20:25:44) +duanemoody: not asking for "X posts by the same IP"
  50. (20:25:47) +AoC: well, that first one you can do with a bit of sys requesting
  51. (20:25:51) +duanemoody: and have
  52. (20:26:16) +duanemoody: as of now the extension i wrote boldfaces links that are OPs
  53. [...]
  54. (20:28:37) +AoC: Alternatively, if you're parsing the report details page, you can just check the "Reply to" field
  55. (20:28:59) +AoC: which I'd actually appreciate in an interface, just get the associated report data without having to load another page
  56. (20:29:14) +duanemoody: not particularly complicated
  57. (20:29:15) +AoC: like a goddamn animal
  58. (20:29:29) +duanemoody: yeah, moot was asking me earlier today why i was coding this
  59. (20:30:10) +AoC: because it's there/it will make life easier
  60. (20:30:22) +duanemoody: because i get paid to do this for a living, why not
  61. [...]
  62. (20:31:04) +duanemoody: i don't dislike the API, i just find it useless for much other than archiving
  63. (20:31:15) +duanemoody: it's nowhere near granular enough
  64. (20:31:30) +AoC: you're missing the goal of the API
  65. (20:31:40) +duanemoody: to keep people from scraping the site?
  66. (20:31:45) +AoC: which is easy realtime updating of threads
  67. (20:31:59) +AoC: instead of polling the pages every 5-30s
  68. (20:32:06) +duanemoody: yes but it can't return anything smaller than an entire threda
  69. (20:32:10) +duanemoody: or entire page
  70. (20:32:26) +duanemoody: which in turn means more bandwidth
  71. (20:32:29) +AoC: it's the json version of the thread though, which is a whole lot smaller
  72. (20:32:36) +duanemoody: ok, that's true
  73. (20:33:09) +duanemoody: but if i need to retrieve post data from a sticky with 3000 posts
  74. (20:33:22) +duanemoody: just one post from all that
  75. (20:33:54) +AoC: I see what you're saying, that we could use an API for what sys is left to do
  76. (20:34:17) +AoC: redirecting, finding specific posts and related data
  77. (20:34:32) +duanemoody: that hover on the front page? there's a backend pulling the post's content but it's hardcoded such that we can't see it
  78. (20:35:06) +duanemoody: so it doesn't even use ajax
  79. (20:35:13) +duanemoody: just hidden divs
  80. (20:35:18) +duanemoody: already populated
RAW Paste Data
Top