Unable to load image

Any 4chan /tg/ regulars here? What's the deal with "bumpstrag"? Any other board celebrities I should be aware of?

I started browsing /tg/ again after a pretty long break, and noticed there's a lot of non-general threads in the catalog that are about random worldbuilding related topics ("how does your setting deal with XYZ", etc.) that are days and days old, despite there being very little activity in those threads. In some of them, someone would angrily respond to some random inane reply with "frick yourself bumpstrag". At first I thought bumpstrag was being used as a general term for someone bumping a thread, but after seeing it used quite a lot, it became apparent that there's a board boogeyman individual referred to as "bumpstrag" infamous for keeping threads alive for days and days by bumping them with inane replies.

Having nothing better to do, I decided to do some extensive research on the topic (and by that I mean I looked up "bumpstrag" on google and 4plebs).

Turns out there's multiple PDF files on this guy:

https://i.4pcdn.org/tg/1579640139044.pdf

https://i.4pcdn.org/tg/1633336990007.pdf

Another thing I noticed lurking on /tg/ is that apparently, recently the mods implemented a change to how autosaging works on /tg/. I was curious to what exactly they did, and looking through archives, I found the answer:

https://archived.moe/tg/thread/89336498/#89417677

If true, it means this person is singularly responsible for mods first making all threads on /tg/ autosage after 14 days, and then going even further and making all threads on /tg/ autosage after 7 days. Which sounds hilarious to me, that a single neurodivergent could have such a massive effect on an entire board, and that the original solution they made was to autosage threads that are 14 days old, which implies that he must have kept threads alive for much longer before that. I wonder what's the longest he kept a thread up alive?

49
Jump in the discussion.

No email address required.

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.