I've seen terrible things

Like:
* le /g/aylords trying way too fucking hard to fit in (they already learned le e[spoiler]/prog/[spoiler]in memes, /prog/ro!)
* le same e/g/in /g/ros imitating lelcunt unironically and thinking this is the default form of protesting here
* /g/roskis trying to bring their `daily programming threads' here
* e/g/in re/g/g/it e/g/g/wings bitching about the state of the board and not leaving (like a weeaboo who went on a trip to Japan, bitches about their lack of forks and knives and doesn't go the fuck back to his third world country)

So I've set up a reasonable amount of machines to flood once again. I might have to space out the replies at some times, because I'd rather avoid the situation where all my machines get banned from 4chan.

I'm sure most of you won't accept my form of protest, but for me it seems like an efficient way of improving the board's quality. After the first flood wave, the moderators started coming here more often, which is not the optimal solutions but at least it kept the recent threads programming-related. I do have to admit I miss Nikita and some of the original /anus/ shitposting, but my purpose is not bringing more moderators, it's keeping the shitstains out of here.

Yes, this will make them engage e/g/in mode, because I remember reading on a /g/ troll bait thread about how they loved pissing us off, so I advise you to ignore their unoriginal shitposting from now on.

The setup will take me about one week, so expect the flood to start next week. I'm aiming for at least 15 days, but it's very likely to get banned, so the flooding might not be as continuous as I'd like it to.

>>39
>>36
The only thing I know for sure is: do not start ironical shitposting. It gets you. One day some dude imports a word like 'lel' and it drives you crazy, you hate that stupid word. You can't change it. You think if you spam it constantly everybody will get sick of it.
I always thought you were the one who imported 'lel' from the less greener pastures. I guess you're merely the one who popularized it instead.
No, I didn't. I saw that abomination for the first time here: posts that were a  single lowercase 'lel'.  It felt like something from imageboards/reddit/youtube/whatever.

I don't know if the guy was trying to make other users cringe. But sometimes it works too well: I have been screaming of rage.

>>38
What was it that made you go ``postal'' on the board?
I'm sure I could make up a lot of reasons that would imply a superior mind feeling insulted by too much triviality. I do hate the repetitive use of the same words. In a maniac way^*. But I might as well acknowledge a narcissistic shitty persona. Also, I may not be a particularly brilliant programmer and I have to struggle to express myself in English. So, well: maybe it was the lazy way to stand out...

I was never too proud of attempting to destroy a community to whom I owe much. Sorry, guys.

* Whoever does that, stop the /polecat kebabs/ variations, please.

There's a thing here, Mr lel-kun-sama. I'm not even joking in this one, but I was the first one to ever use LLLLLEEEEELLLL as an ironic shitpost to keep the /g/ crowd out of here. You made an attempt at copying my posts, so I got mad at first and started shitposting harder. You even went for EJPIN, when I clearly showed my dislike towards people who don't enjoy Japanese media. I even dare to say I'm the one who started using the word E/G/IN at first, but you went and modified it to EGIN, maybe because you were lazy.

(Hell, even the onahole guide at /jp/ is called ``Le onaho guide. Truly e/jp/in, /jp/ro'' and I wasn't the one who did that)

Then I started making posts excusing myself for giving you the idea of LLLEEEELLLL shitposting. After that, even saged posts were automatically replied to with a bot that said something like LLLLLEEEELLLL EGIN SAGE GRO! EGWGWGIWGIWGIWING and stuff. That's how eggwings came to be, I suppose.

Why the fuck am I saying all this?
1) If you were the one who made the EGIN SAGE bot, then don't feel sorry at all, for it is my fault and only my fault.
2) If you weren't that guy (or the guy who made the E/G/IN /G/ROSKI bot a few days ago), then there's a third one of us. It's his fault.
What I'm trying to tell you is: it's not your fault, lelcunt.

I like you.

>>42
Oh, I had forgotten about the antisage bot, it was some months ago. I don't believe I let it run for more than an hour.
I wasn't here a few days ago. Actually you didn't see me the whole summer. There seemed to be a slightly higher ratio of mildly interesting threads when I was off, but I had the unpleasant surprise to discover the LELLs were going on...

By the way, you might be amused to know that I am the author of that little screenplay with the angry boss (Freddy) Krueger (from "A Nightmare on Elm Street") and the dumb web developer Yannick. That fiction wasn't meant for a very broad audience (for obvious reasons) but produced unexpected results. The thread even got deleted!

check 'em

>>43
You mean this one https://ivasiwlrjq5dxk6b.onion/prog/read/1352640796 ?

FUCK I FORGOT MY SAGE FUCK FUCK

>>43
I am the author of that little screenplay with the angry boss (Freddy) Krueger (from "A Nightmare on Elm Street") and the dumb web developer Yannick.
Oh god, I fucking love you! Please post more.
^{PD: Your English is pretty good for a Frenchman.}.

>>46
Don't worry, we will sink the thread back to page 2 again. Try to be more careful next time.

>>47
Don't worry, we will sink the thread back to page 2 again. Try to be more careful next time.
I'm terribly sorry! I've taken steps to make sure it never happens again:

// ==UserScript==
// @name        autosage
// @namespace   invalid
// @include     http://dis.4chan.org/*;
// @include     https://dis.4chan.org/*;
// @version     1
// ==/UserScript==
(function(){
    var inputs=document.getElementsByTagName("input");
    for(var i=0;i<inputs.length;i++) {
        input=inputs[i];
        if (input.name=="meiru")
            input.value="sage";}})()

pedantic self-fix:

// ==UserScript==
// @name        autosage
// @namespace   invalid
// @include     http://dis.4chan.org/*;
// @include     https://dis.4chan.org/*;
// @version     1
// ==/UserScript==
(function(){
    var inputs=document.getElementsByTagName("input");
    for(var i=0;i<inputs.length;i++) {
        var input=inputs[i];
        if (input.name=="meiru")
            input.value="sage";}})()

>>41
>>39
>>36
The only thing I know for sure is: do not start ironical shitposting. It gets you. One day some dude imports a word like 'lel' and it drives you crazy, you hate that stupid word. You can't change it. You think if you spam it constantly everybody will get sick of it.I always thought you were the one who imported 'lel' from the less greener pastures. I guess you're merely the one who popularized it instead.I don't know if the guy was trying to make other users cringe. But sometimes it works too well: I have been screaming of rage.
I too found it insanely obnoxious, but that's no reason to repeat it over and over. I do understand your motivations, but think of your fellow /prog/riders -- while you had to endure a few ``lel''s, they had to endure the same plus all of your designed-for-maximum-annoyance lel spam. That hardly seems fair.

Moreover, who exactly did you think you were punishing? The /g/itstains(s) may not have minded your shitposting that much since they are used to living in festering filth, so really the real victims of your unadulterated scatological verbiage were the /prog/ regulars themselves. Hell, I even saw you pick on posts that were likely written by local well-meaning posters.

I was never too proud of attempting to destroy a community to whom I owe much. Sorry, guys.
Well, I could never stay angry at someone who apologized nicely. Next time you read a particularly terrible post and feel an incoming fit of textual diarrhoea, think: What would the Sussman do? Would he throw feces at everyone in his lecture just to get rid of one shit-throwing monkey that got in through an open window? Or would he just stare it down and calmly but firmly tell it to go away until it did so?

>>34
I thought it was funny.

None of you should feel bad or bear any responsibility for destroying /prog/. One, it's not your fault, and two I appreciated your shitposting as works of art. The new copy cats we have are idiots. There is no intelligence in their work. It's like a weak and crappy echo bouncing off of a wall. Their work only demonstrates a strive for conformity. If they would just be themselves it would be tolerable, but they come from a culture that is based completely in uniformity, so much so that a unique identity no longer exists. They spout memes to show they belong to the same group. I have to admit though they would be very hard to deanonymize, as none of them contribute anything unique. I'll stop ranting, but if these people are to be usable, you have to break them out of their lejun shell first, and get them to post as actual individuals.

https://dis.4chan.org/read/prog/1374162232/49-55
Whoever made posts 53-55, I fucking love you. Please post more.

I love both You-san and Sussman-san. _{Can't say the same about Me-kun, though. (´；ω；`)}

>>53
I but I love you-san, so you should love your me-san as well!

>>54
No!

As a side note, please keep in mind that this could trigger an unwanted reaction from the admins, like implementing captcha,  merging the board with /g/, or just deleting it. Of course, those are extreme cases, but as a responsible citizen of Schemeland, you should at least consider them.

More likely outcomes of this are some machines being banned for at least 15 days, some /g/ros complaining about the state of the front page but not leaving, some other /g/ros actually leaving, and hopefully you guys continuing to sagepost on these threads.

More details will be coming on the next few days.

>>55
My Prog^Synch[Technology]^TM is getting quite high level I must say. After some tests I'll upload what I have for the scraper. It polls prog for changes and merges new posts (but ignores deletions) into a database.

Things could get worse, but we'll see. I was hoping they would loose interest if we shitposted enough, but they wont stop raping this corpse. They just keep coming back ;_;

>>56
That's good to hear! Are you the one who made the Tor search engine? I'll have to re-re-re-re-re-download the bundle.

>>57
I'm the Tor search engine individual and I am not >>56. I however do offer to do source code hosting for >>56 if ey is interested.

>>56-58
Having two working alternatives makes me happy.

Please accept >>58-san's offer, >>56-san.

>>58
Thanks, we can move to a repo if you want. But the scraper is just a single python file, and base64ed gzip dumps are working ok.

>>60
First of all, are you comfortable working with fossil?
Second, what project name and user names do you want?

Finally visit this page https://ivasiwlrjq5dxk6b.onion/makepassword.cgi and post the masked password here. Keep a copy of the associated secret password.

>>1
Hey, what's the status?

The setup is ready! I will do some tests now.

Things you (possibly) want to know:
The posting will start at Wed, 21 Aug 2013 07:00:00 UTC (if my calculations are correct, that's 1377068400 in Unix time). At this time, least 40 threads full of shitposting will be necrobumped only once so as to completely ``wash out'' the front page. Then, a list of 80 threads will be necrobumped cyclically in intervals of around 30 seconds. The purpose of this is having at least 3 pages of total shitposting and having the front page in page 3 or 4.

You are encouraged to make threads around Wed, 21 Aug 2013 06:00:00 UTC | 1377064800. These threads will be sunk to page 4 (or 3, depends completely on the first batch of necrobumped threads). Please, be very careful when posting on them, as this will be the ``deep /prog/'' while the flood lasts. Using >>49 to avoid bumping a thread is strongly recommended.

If the tests go wrong, I'll announce a new date on this thread. You can also bookmark this thread and discuss the ongoing events here.

If this thread is deleted, I'll repost it with the same title and content, and sink it back to page 4 or 5 as fast as possible. Hopefully the archivers and the search engines made by you guys make this step unnecessary.

Let me know if you think I should modify the strategy, the start time or if you have any questions.

>>63
Make sure you don't bump any historical shitposting threads.

Godspeed.

>>64
That is a kinda vague request, but I'll try. I'll post the threads that will be used here.

>>63
Why not defining a mechanism for bumping the 80 shit threads instead of having them constantly necrobumped? It could be simply triggered by saging the first post of a thread. I'm afraid that permanent spamming will have terrible side effects.

Cyclical necrobump (part 1/4):
01. http://dis.4chan.org/read/prog/1376955122 Oddly content
02. http://dis.4chan.org/read/prog/1376945711 NEXT evil: lots of gravitational worms
03. http://dis.4chan.org/read/prog/1376842378 censoring feminist cunt
04. http://dis.4chan.org/read/prog/1207316436 DO U WANT SUBMIT TO BLACK MASTER
05. http://dis.4chan.org/read/prog/1339060568 tell me oh great gook master about リスプ
06. http://dis.4chan.org/read/prog/1339031127 warp hardy foop wapp wapp
07. http://dis.4chan.org/read/prog/1339018222 Paying for Coder
08. http://dis.4chan.org/read/prog/1363644651 rainy day and high as fuck
09. http://dis.4chan.org/read/prog/1363589699 Take LSD
10. http://dis.4chan.org/read/prog/1363599127 da fyootcha
11. http://dis.4chan.org/read/prog/1363579636 DAM I NEAD HELPU
12. http://dis.4chan.org/read/prog/1363427604 Giant Sea Cucumber Eats With Its Anus
13. http://dis.4chan.org/read/prog/1358093010 aysxdcfvgbhnjmk,l.ö-ä'
14. http://dis.4chan.org/read/prog/1358038530 damn memes
15. http://dis.4chan.org/read/prog/1358026969 shotgun-friend
16. http://dis.4chan.org/read/prog/1357800680 How do you like your meth?
17. http://dis.4chan.org/read/prog/1222983146 DO NOT EAT PRINGLES FAT FREE POTATO CHIPS 
18. http://dis.4chan.org/read/prog/1184059763 Joanna Rutkowska
19. http://dis.4chan.org/read/prog/1183942038 a game that makes people this stupid:
20. http://dis.4chan.org/read/prog/1183895108 coda is my idol

>>66
Please elaborate. What kind of mechanism would you use? I'm planning on bumping the threads in that list's order. When the cycle is over, it starts again (well, what else would it do).

That way, it would seem like the board is moving, but it actually is dead on the first two pages. I think this would work even with a delay of 1-5 minutes.

>>68
Your bot would check for a codeword every time a new thread is posted (could be sage in the mail field). If a shitty thread without the code is posted, it does nothing. But if we want a thread to be sunk to page 3, we can do it at will.

That way the front page is not constantly moving, leaving a nice honeypot for shitposters.

>>69
Let me see if I understand. Someone posts a thread with a secret codeword, and it's immediately sunk to page 3. If it isn't, it stays on the first page.

Sounds reasonable, but there are two problems:

First, what would you do if a /g/roski gets hold of the secret codeword? All our attempts so far would be rendered useless.

Second, if people don't make new threads in a long, I won't be able to flood the board. Considering how we've already got a thread like this and non-ironical shitposts on the front page, things wouldn't be any different.

>>67
Hey, I remember making https://dis.4chan.org/read/prog/1363427604/4 !

I also made https://dis.4chan.org/read/prog/1376842378/1,4 in a fit of antifeminazi rage. ｉ　ｆｅｅｌ　ｋｉｎｄ＇ｖｅ　ｂａｄ　ａｂｏｕｔ　ｉｔ　：（

List looks okay to me so far, nothing of particular value.

>>70
On the other hand, what will happen when a /g/roski sees that his thread is sunk to page 3? He will try to look for it and bump it and could notice the activity in page 3.

Also I wasn't thinking of a 'secret' codeword, just an elaborate way of posting that can be learned.

I'm just worrying about the consequences of a constant spam.

>>72
I understand your concern. This might not be a convincing argument, but so far we've found this thread to be effective enough. Also, this thread was bumped twice, I think. Both times were around midnight and no /g/ro came here. What I'm trying to say is, if you're careful enough with the time of your posts (or if you sage like a normal person).

Still, I like your idea of using a standard for making posts. We could even use indefinitely. Does anyone remember about BBCode steganography with [o] and [i]? We could use that.

>>71
No need to feel bad. I've done worse things.

Cyclical necrobump (part 2/4):
21. http://dis.4chan.org/read/prog/1205112117 help please
22. http://dis.4chan.org/read/prog/1205020320 REDDIT Part 1
23. http://dis.4chan.org/read/prog/1248838483 Lol MS
24. http://dis.4chan.org/read/prog/1248750254 Plates and bowls leaking
25. http://dis.4chan.org/read/prog/1188193715 Halp
26. http://dis.4chan.org/read/prog/1188180127 ••••••••••
27. http://dis.4chan.org/read/prog/1188157632 butts
28. http://dis.4chan.org/read/prog/1194177278 yes
29. http://dis.4chan.org/read/prog/1193941331 need something
30. http://dis.4chan.org/read/prog/1193774979 ow stupid people in the internets
31. http://dis.4chan.org/read/prog/1332264170 cleaning9
32. http://dis.4chan.org/read/prog/1332233044 cleaning46
33. http://dis.4chan.org/read/prog/1332233367 cleaning47
34. http://dis.4chan.org/read/prog/1332251645 reported
35. http://dis.4chan.org/read/prog/1303502372 wow
36. http://dis.4chan.org/read/prog/1303423833 hi i am Andy
37. http://dis.4chan.org/read/prog/1303367899 Shakugan no Shana
38. http://dis.4chan.org/read/prog/1303331805 /b/tards report in!
39. http://dis.4chan.org/read/prog/1256076507 hello
40. http://dis.4chan.org/read/prog/1256016977 Blood Electric by Kenji Siratori

>>74
That also looks okay.

>>75
Ah, that's good. You might not believe this, but it's actually hard to find threads that are completely full of shitposts. Some of them seem to have a bit of actual contents, some others have /prog/ ``memes'', and some of them mention /g/. I'm trying to avoid those, but seriously, it's not that easy.

Cyclical necrobump (part 3/4):
41. http://dis.4chan.org/read/prog/1255909022 funy numbers
42. http://dis.4chan.org/read/prog/1332284798 ҉ SYAD NAELC
43. http://dis.4chan.org/read/prog/1332293247 YEAH! NIGGER! NIGGA!
44. http://dis.4chan.org/read/prog/1189061640 כגדל גלדכח לננד
45. http://dis.4chan.org/read/prog/1332260552 Dirtyin' it up
46. http://dis.4chan.org/read/prog/1331607926 you ready bitches?37
47. http://dis.4chan.org/read/prog/1331769691 Dogs ate cat alive!
48. http://dis.4chan.org/read/prog/1331768835 Hey You!:)
49. http://dis.4chan.org/read/prog/1331665132 Some presidents
50. http://dis.4chan.org/read/prog/1331601697 you ready tray?0
51. http://dis.4chan.org/read/prog/1331659843 99
52. http://dis.4chan.org/read/prog/1332233687 cleaning48
53. http://dis.4chan.org/read/prog/1345382428 Oh God
54. http://dis.4chan.org/read/prog/1345432422 am I dying or just high or something
55. http://dis.4chan.org/read/prog/1345368190 Anus
56. http://dis.4chan.org/read/prog/1327754855 Grave of the Fireflies
57. http://dis.4chan.org/read/prog/1332234005 cleaning49
58. http://dis.4chan.org/read/prog/1345418044 ngger mature
59. http://dis.4chan.org/read/prog/1345394899 I want two dicks in my butt
60. http://dis.4chan.org/read/prog/1332234324 cleaning50

>>73
Does anyone remember about BBCode steganography with [o] and [i]? We could use that.
Heh, you could actually push that even further and use all available tags to encode information (though it's better if you choose a subset whose size is a power of two).

I'm not sure what the point of all this is, though. We're not trying to block off the NSA here; the average /g/ netizen has barely enough brainpower to hover their mouse over spoilered text. If you want a cheap yet highly effective and minimally intrusive steganographic measure you could just wrap your posts in a few dozen sup/sub tags -- they'll never figure it out!

>>76
59. http://dis.4chan.org/read/prog/1345394899 I want two dicks in my butt
This one is so terrible it's actually good. I'm somewhat ambivalent towards it. I don't know.

The rest look okay though.

You might not believe this, but it's actually hard to find threads that are completely full of shitposts.
Didn't Nikita make a bunch of jew threads nobody ever replied to?

>>77
I'm not sure what the point of all this is, though
Just trying something different is enough for me. I do like the idea of using more tags. I even like the idea of posting base64 encoded stuff, like the guy who made that FIOC thing.

>>78
Oh, yes, but some of them were Over 1000 Posts IIRC. I'm trying to look for more Jew threads.

This one is so terrible it's actually good.
We could always repost that one.

Cyclical necrobump (part 4/4):
61. http://dis.4chan.org/read/prog/1365370138 suck own cawk
62. http://dis.4chan.org/read/prog/1189516465 JEWS DID WTC
63. http://dis.4chan.org/read/prog/1191548838 GENERATED BY A BASIC PROGRAM
64. http://dis.4chan.org/read/prog/1191707032 DO NOT PRONOUNCE THE J-WORD
65. http://dis.4chan.org/read/prog/1188296624 OH FUCK
66. http://dis.4chan.org/read/prog/1186516209 VOLDEMOOT KILLS SNACKS
67. http://dis.4chan.org/read/prog/1352168844 Sand Niggers
68. http://dis.4chan.org/read/prog/1352116665 Every Jew
69. http://dis.4chan.org/read/prog/1350505909 smoke weed everyday
70. http://dis.4chan.org/read/prog/1186266694 Sooo friggin tired of it
71. http://dis.4chan.org/read/prog/1187402250 halp
72. http://dis.4chan.org/read/prog/1184214821 DOES PROGRAMMING MAKE YOUR E-PENIS BIGGER
73. http://dis.4chan.org/read/prog/1191611618 Sponsored Post: Cum Hungy Sluts
74. http://dis.4chan.org/read/prog/1233004288 Sexism in Computing Science
75. http://dis.4chan.org/read/prog/1351093131 motherfuckin' juice
76. http://dis.4chan.org/read/prog/1331661905 you ready bitches?90
77. http://dis.4chan.org/read/prog/1350684040 卐卐卐卐卐卐卐卐卐卐卐卐卐卐
78. http://dis.4chan.org/read/prog/1271156250 dfsdsffdsa
79. http://dis.4chan.org/read/prog/1294278532 noko
80. http://dis.4chan.org/read/prog/1292546560 /prob/