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.

>>83,84
The ``Story About Ping'' one got a good laugh out of me. Also the ``Sponsored Post: FIND A FEMALE FUCK BUDDY'' is actually very amusing in a retarded kind of way.

The rest look good to go.

Hell, how would the offline posting even work?
By referencing posts by their hashes and using that for quoting and such. Of course, a proper /prog2.0/ reader would replace those nasty hexadecimal hashes with nice sequential integer references.

The self-moderation system could work as follows: each self-appointed moderator (in practise, every user) whitelists/blacklists a bunch of posts (identified by their hashes) locally, then signs the list with their public key and posts it in a special thread. The other users can then subscribe to particular pubkeys (according to how accurate they seem to be in their judgement of value) and prune their databases according to them. A simple server policy could be, for example, to prune posts that have not been whitelisted (by any key, trusted or not) unless they are newer than one month or that they have been quoted by a whitelisted post, and to prune posts that have been blacklisted by a trusted key.

In case you can't tell, I kind of like fossil.