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.

>>1
The quality of the board in the last few days has hit a peak not seen for years.  Please don't fuck around with it.

To the report advocate: report it as much as you want, you already know mods don't even care about the report queue, they simply delete the threads they want.

If this gets deleted, I'll repost this thread as many times as needed. If I get banned for simply reposting this thread, I will repost it once again once I find another machine. (No, cloning my MAC is impossible, because technically this is not my network)

>>2
Hit a peak?

Check these threads:
http://dis.4chan.org/read/prog/1376317831/1-
http://dis.4chan.org/read/prog/1376397890/1-
http://dis.4chan.org/read/prog/1376393458/1-
http://dis.4chan.org/read/prog/1376392319/1-
http://dis.4chan.org/read/prog/1376386216/1-
Those are the ones I could find in the front page, but there are even worse.

I won't deny there were some other good threads, but if you want to keep them, I suggest you to continue posting on them, even if they happen to sink to older pages.

Hell, if you want, I could find a way of filling those threads with relevant content. I want to go for a more sophisticated flood this time, so maybe I could make a HTDP repost thread and bump a few select good threads too.

>>3
Reported.

>>5
Thank you.

>>1

/g/aylords trying way too fucking hard to fit in
Help a PHP noob
create an image which displays its end MD5 sum in the image itself
CVS, Subversion, GIT, Mercurial... I need to see and choose from them.

They ain't even trying.

>>1
/g/roskis trying to bring their `daily programming threads' here
Wait! How do you know about DPT threads, if you haven't come from /g/ yourself?

>>7
Don't tell them about G00gl3 yet, they might gain a competitive advantage over us!

>>4
So let me see if I understand your reasoning.  You don't like the existence of shitposting among the good threads, so you're going to punish everyone with more shitposting?  At what point are the trolls going to realize that their shit is annoying?  And you're offering to bump good threads with good content.  So basically, you want the status quo, but more of it?  How is your bot going to determine good content?

You get a say in this.  You can post good replies instead of complaining.  You get to make that vote as often as you like.  Why don't you devote your time to digging up good stuff to post on here instead of to destroying /prog/ out of spite?  What more could you hope to accomplish?  Who's going to be bullied into being smarter?

>>8
They made it entirely obvious.

>>10
My bot is not going to do anything other than flooding. I'll feed it the content myself. If you don't want it, I can just necrobump old threads with blank posts.

Who's going to be bullied into being smarter?
Nobody. I'm doing this because I feel like doing so.

I remember reading on a /g/
Why don't you fucking stay there.

Nice job lel, you really make them feel right at home.

Actually I have a better idea. Keep good threads off the front page (where /g/ tourists can't reach them) and sage all your posts. Use your local prog.db to generate your own front page.

>>14
But scraping the entirety of /prog/ takes so long ;_;

>>15
Do you want me to upload an up-to-date prog.db.xz? It's just 50 megabytes (although it's over 1 GiB uncompressed).

>>16
That would be nice, but you should wait until this thread is no longer visible to many.

>>1,14
Why don't we combine the two? Let the front page burn while we're having quality threads and cups of Scheme several pages in.

>>18
Seconded. >>1 please don't bump good threads.

>>17
Why not give it a little push? Bump recent shit threads.

There, that wasn't so hard now was it?

It's still compressing, though. Check back in 20 minutes.

>>17
https://ivasiwlrjq5dxk6b.onion/files/prog-20130813130608.db.xz

Or if you don't have tor,
https://ivasiwlrjq5dxk6b.tor2web.org/files/prog-20130813130608.db.xz

>>23
Many thanks.

>>24
Your welcome lol.

do it! /prog/ isn't /prog/ without a good spam storm.

Don't merely spam them!
For the borderline threads, post pieces of wiki articles on scary math subjects that /g/uise can't understand, like calculus.

For the totally worthless threads, scrap some interracial\scat\nigger rape\snuff\incest\cannibalism `erotic' `fiction' from asstr and spam threads with pieces of that.

>>12
Someone made a troll bait thread there and linked it here.

>>18
I'll definitely do this.

Also, I know I bumped the thread, but I picked this specific time hoping the /g/ children are asleep and the true /prog/riders are around. You might want to use this thread as an ``anchor'' for future quality threads. If you have any other suggestions, I'll be glad to hear you.

>>28
No need, we can just use /prog/scrape.

The /prog/ search engine now also has a hidden ``see recently posted-in threads whose last-bumped time is at least 24h ago'' feature, but I won't tell you how to use it.

>>29
You mean the Tor search engine? Don't make me download the goddamn bundle again.

but I won't tell you how to use it.
(´；ω；`)

It's painful to see the e/g/in/g/roskis using LEL spam as a way of pissing off people. I wonder if it's an e/g/in meme over there already.

>>30
$ sudo apt-get install tor
[sudo] password for user:
Reading package lists... Done
Building dependency tree      
Reading state information... Done
E: This is not ubuntu, faggot.
$

goddammit, >>32-kun

>>27
I used to theorize a lot. Years ago, I have abused sagebombs which was the most stupid attempt at censoring shit threads. I have now to live with that shame: that was the lamest thing to do.

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. That doesn't work, you just get called lelcunt and your very own shitposts keep being spammed when you stop.

Same mistake with the check my dubz. I revived it when I got mad at the 'sleep sort' guy (he admitted he was doing it, in the thread)

I have always advocated the creation of an invisible board of saged threads, far from the front page.

>>23 thanks. I didn't want to scrape the whole thing again. I'll monitor the deep /prog/.

>>34
Was the antisemitism/homophobia shtick another one of your brilliant attempts to get people sick of those things? Because that sure fucking backfired.

>>35
Your also welcome lol.

>>34
What kind of shitposting should I strive for, then? I don't think I will shitpost like lelcunt does, but what do you you think of the incomprehensible spam that mentions like one line of the Torah and then adds shitloads of random BBCode and Unicode characters? I don't think the idea of posting the fanfiction shitposts is a bad one, by the way.

Please keep in mind the purpose of the incoming storm is to keep /g/ away for a few days. Maybe they will stop complaining and actually leave the place they hate so much.

>>36
No, when the antisemitic spam started (2011?) I was still well behaved: two messages per week on average, sometimes with code.

I think I lost all hope around that time and started to hate the whole board and its regulars. I became a dedicated shitposter. I have put a lot of work in it. I could wake up at night to shitpost because I just thought of some "brilliant" new scheme.

A lot of my day was spent crafting shitposts. I have browsed circa-2002 Java forums looking for the ugliest snippets of code just to create genuine-looking homework threads. I have lurked /g/ to bring you the 'muh' among other shit. I think I have peaked at 50% of all the posts in a 24h timeframe. There was absolutely no /g/ invasion until recently.

>>37
Just let them turn the front page into what they want. Pick the lost riders and the above average newcomers and invite them in the backroom by a mere evocation of /prog/scrape, or a reminder of the whole point of sage.

>>34
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.

>>38
What was it that made you go ``postal'' on the board?

>>38
There was absolutely no /g/ invasion until recently.
You make it look much better now. I can appreciate your dedicated work now.

Also, glad you made it to this thread, even after the vague criteria.

>>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.