« first day (1367 days earlier)      last day (2749 days later) » 

12:00
or just try it until it possibly starts working?
[ SmokeDetector | MS ] Few unique characters in answer, offensive answer detected, repeating characters in answer: Is there a way to clear your printed text in python? by LOL U GOT TROLLED on stackoverflow.com
@SmokeDetector k
the revision thing in the top-right corner of metasmoke tells you what revision is currently deployed
@ArtOfCode so when it's no longer showing 7467ac6 give it a go?
basically, yeah
12:09
[ metasmoke ] ci/circleci failure on 40d0756: Your tests failed on CircleCI
so the query format is like /api/posts/search/regex?query=foo%3Cbar or what?
@tripleee yep, query is the regex you want to use
and a key, obviously
yeah, thanks
12:27
[ metasmoke ] ci/circleci success on a763523: Your tests passed on CircleCI!
[ metasmoke ] ci/circleci success on a763523: Your tests passed on CircleCI!
@trip how do you look up who owns a domain?
I'm trying to look up who owns underwise.com but I can't figure out how.
whois search?
Domain Name: underwise.com
Registrar URL: godaddy.com
Registrant Name: tian fei
Registrant Organization:
Name Server: NS63.DOMAINCONTROL.COM
Name Server: NS64.DOMAINCONTROL.COM
DNSSEC: unsigned
@thesecretmaster yeah, it's just that godaddy's whois is apparently "updated" so you don't get results from services like who.is or even your regular whois command-line client
directly
@thesecretmaster that only reveals that it's available from godaddy
And a name, right?
@thesecretmaster well yeah, but that's often forged and/or uninformative
that name looks like a Chinese sea goddes, so yeah, not helpful
@tripleee Thanks.
(background: they're taking like everything on their site from SE without attribution)
@tripleee How'd you get that? I tried using the -h flag on my command line (arch), and didn't get anything.
@thesecretmaster -h whois.godaddy.com
you need the WHOIS server address as well as the flag
12:33
Yeah, I just tried that.
I'm gonna guess the arch client is different then :)
not familiar with Arch but if all else fails, direct telnet to port 43
there are multiple generations of the whois protocol, the referral logic was a big change but it looks like godaddy (unilaterally?) changed something on their side recently
FWIW my result is from MacOS Sierra
I think the arch client is lying to me: -h HOST, --host HOST connect to server HOST
@tripleee mine from Ubuntu
if it's using that as the referral server, not the final destination, that would be a problem, but this is pure speculation
strace would probably help you figure out where it's going wrong if you really want to know
12:36
can confirm that $ telnet whois.godaddy.com 43 works, though
Eh, I don't care enough. I don't use whois very often
This makes me sad. They've taken it without even keeping the formatting. If you're going to plagiarize, do it well!
They don't seem very wise...
@ArtOfCode some servers use the input as a wildcard, you have to figure out their protocol for submitting a verbatim query, IIRC it's =query or something like that
J F
J F
> several seconds ago
lol
12:37
@tripleee You can just type the domain name with GD
@ArtOfCode yeah, thankfully
Hey people
My arms feel like they're made of butter. I've been carrying boxes all morning for the moving of part of the office
get some bread
12:42
But bread is like all carbs
like 90% carbs
but it'll be good with the butter
I think it was a 'bread and butter' joke...
groans
Maybe I was being dense on purpose to ruin the joke :D
@Magisch I don't think there was any knead for that...
@Henders aaaaargh
12:44
wow
that was so bad it was actually funny again
the level of punniness in here is rising
@Mithrandir Just like a freshly made bloomer?
12:58
Autoflagging RFC: #AF4. What do we need to expand autoflagging further?
9
your comments please
[ SmokeDetector | MS ] Few unique characters in answer: Uniform Integrability of exponential random variable by phdmba7of12 on math.SE
tp- by ArtOfCode
sd - v
@quartata you were talking about security for autoflagging expansion a few days ago; there's an RFC you can chuck comments/suggestions on there
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, repeated URL at end of long post: You need a consume; stick your by user725486 on askubuntu.com
tpu- by Ashish Ahuja
fp- by Mithrandir
13:26
!!/location
@Henders ArtOfCode/EC2
[ SmokeDetector | MS ] URL in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: puresupplements786.com/stackt-360/ by lucy fennesey on astronomy.SE
tpu- by Henders
[ SmokeDetector | MS ] URL in title, pattern-matching website in body, pattern-matching website in title, repeated URL at end of long post: puresupplements786.com/stackt-360/ by user251649 on apple.SE
tpu- by Ferrybig
[ SmokeDetector | MS ] Blacklisted website in body: How to Set up review page at word press by Sarah on stackoverflow.com
tpu- by Mithrandir
API quota rolled over with 8933 requests remaining. Current quota: 19999.
stackoverflow: 377
math: 337
superuser: 76
askubuntu: 67
physics: 61
serverfault: 52
codegolf: 48
english: 43
apple: 40
travel: 27
workplace: 23
unix: 23
electronics: 21
security: 21
gis: 20
drupal: 19
movies: 19
ell: 18
mathoverflow.net: 18
scifi: 17
dba: 17
salesforce: 17
wordpress: 15
ru.stackoverflow: 15
meta: 15
stats: 15
sharepoint: 15
arduino: 13
gaming: 13
magento: 13
android: 13
academia: 12
interpersonal: 11
diy: 11
graphicdesign: 11
softwareengineering: 10
politics: 10
webapps: 9
islam: 9
13:57
[ SmokeDetector | MS ] Username similar to website in answer: What is a non invasive, large, structural species of Bamboo? by Lewis Bamboo on gardening.SE
sd f
for now
RFC identifiers are becoming increasingly complex :P
@ArtOfCode I'm going to comment here because I think it needs a bit of discussion. Based on the responses to bluefeet's post about my bot (here) for reference, I don't think the community is going to support us having the ability to unilaterally nuke anything.
[ SmokeDetector | MS ] Username similar to website in answer: Claiming my own country by Guanduania on law.SE
I have the accuracy you are striving for and it's about comments, and the community still doesn't want it done automatically - unless it's something that SE runs and maintains
14:02
tpu- by Mithrandir
@Andy I think you're right... which is kinda why I was going to propose us discussing it, then taking it to Pops and surreptitiously updating our meta post after we've already been doing it for a while :)
it'd probably be good to at least have a show of being open about it
That said, I tend to think that if we go in with a mountain of data (which we have) showing a bunch of nines (or maybe some zeros?), it'd be pretty easy to shoot down the principled arguments
Or I'd hope so. Also, this time we could probably start on mSE :P
@Undo It hasn't helped in my case.
@Undo You don't want to have that fight again? :)
egads
well we're not about to post on every single meta site, sooo...
14:05
That one blindsided me. Like playing football and someone hits you in the face with a frisbee.
lol
@Andy True, although your case is slightly different - we've got a lot more visibility and public process built up around everything
I've got reservations about running the comment flagger without oversight too. We've got oversight galore.
I'd love to be wrong, but I think we'd hit the same community split - yup, automate all the things vs. nope, human brain required
It's a Big Deal when we autoflag a false positive, and we're really good at getting feedback on everything quickly. You could even do something like require feedback before actually killing it.
ultimately, I know you're right and I really want you to be wrong
That could work. If we went for 5 flags (with high enough accuracy, like 99.99%), then required feedback for the 6th...actually, that'd create a nice race condition between FIRE and MS
which I suspect MS would win
14:08
4, then feedback
One human involved to destroy something a trusted instance thinks is spam. Pretty safe.
Of course, we all live in this system and know how resilient it is. Other folks see "you want a robot to delete my stuff"
Okay, let's think about trusted instances. I like that idea and I don't like it at the same time.
I like it because oversight and code review and obvious accountability
but I don't because duplication and slower deploy cycles
That said, I don't have an issue with going to 4 without making a big deal out of it - it's a natural progression and doesn't change the dynamic much. 5 or 6 is different.
@ArtOfCode Don't know about the deploy cycles. It'd still be as fast as it is now to deploy a blacklist item to public and get 3 flags on it, and if something needs to be un-blacklisted removing it from the public instance would keep it from being flagged
(I'm seeing a system where the public instance reports to metasmoke, trusted one confirms)
Some timing things to work out there, but not too bad
@Undo Aye, you could get 3 flags on a post from the public instance, but you can't get a website blacklisted and eligible for 6 flags so quickly - that has to wait for the weekly review-and-merge
You'd just need to wait until the deploy cycle to jump from 3 to 4-6 flags. It wouldn't be too bad.
@ArtOfCode that
Which might be a good thing anyway
Can someone briefly explain what the trusted instances will be doing?
14:15
@Andy TL;DR: Run a headless SmokeDetector instance on a machine we trust, at a Git revision we trust, then require it to detect a post before we allow more than 3 autoflags.
To get around the whole "remote code execution as a service" thing
afk for a minute
Ah. Ok. That kind of makes sense. My issue with that is that our blacklists and such are in git too.
@Andy what issue does that create?
Also, rewinding a bit... I think opposition actually might not be as bad as we're dreading here. Our meta post had almost zero opposition - I think I remember one person seriously objecting), and that was after we already started doing it.
That's why we have two - one to keep our agility, the other to keep integrity.
@ArtOfCode aside from the frisbee lobbing, yeah
Now, we might get more opposition to 6 flags, but certainly 4 and possibly 5 might not meet too much more opposition
@Undo yeah, I was ignoring TL for now :)
@ArtOfCode I think we did a pretty smart thing there by allowing people to sign up and reap rewards from it. Made folks feel like they were part of it (hey, free flags) and thus less likely to dislike it
14:19
Also true
@Undo Does it get you that integrity though? I think I'm coming back to "blacklists shouldn't be in the code" argument. If the majority of our code updates are actually blacklist/watchlist updates, when the trusted instances are updated will each of those blacklists actually be checked? Or will we just say it's time to update? If we are just doing this to watch the code of smokey, I think it's a great idea.
4 mins ago, by Undo
To get around the whole "remote code execution as a service" thing
What does this mean?
@Andy I was thinking we'd review everything, including blacklists.
@Henders anyone with git privs, and to a lesser extent any code admin, can remotely execute code using Smokey on someone else's machine
@Henders !!/pull allows anyone with GH privs to immediately run anything they want. Which is terrifying
14:20
Git privs: commit some malicious code, !!/pull, and your code is live on the current host
So far, pallet-of-bricks has been a good deterrent. Having honest people helps too.
Right, gotcha
@ArtOfCode I had very little opposition to my announcement of what I was doing too. There is a difference between "Look what I can do! Someone needs to click that button now and confirm all the work I just made for them" and "Well...let's not make them click that button any more" apparently.
@Andy I think the idea is that we have a weekly (or other time-period-based) check where the trusted hosts check the entire diff from the last week, and merge only if they think it's good
This diff isn't too hard to read at all
Watched sites can be ignored there
@Andy This is also true. We do have more grey area between "bunch of humans involved" and "no humans involved" - might have to exploit that.
Ease folks into it, in tiny steps. 4, to 5, to 6 with human oversight, to straight 6.
(meaning 'at least 1 feedback')
14:25
...I don't think I'd be comfortable with a 6 unless the weight was 1,200 or so.
@Mithrandir What's your reasoning behind that?
Consider that 280 weight is 99.99% accurate
@Undo Agreed. So, now my question is why should the trusted instances be a week behind? What does that really get us?
@Andy trusted people not having to read tiny diffs a hundred times a day
(Um...I realized that may have come off as hostile, sorry)
It'd be good to keep an aura of importance around those reviews - if they're every day or two, we may risk people becoming complacent. Every week or two might keep it feeling like a Big Deal
Not at all sold on that, just thinking out loud
14:28
there'd be a very small number of those people - our current situation is okay, because there are plenty of people to split diff-reading between, but when you take it down to two or three and require each of them to independently read every diff and judge it... that's a lotta dedication
@ArtOfCode It's irreversible without a mod of that site. If there's a singe FP that slips through to that, the OP suffers a -100 rep penalty, and an IP block, and other assorted consequences. That 1 FP is a big deal. Spam flags are one of the most dangerous things on SE - they're almost the only way a few users can unilaterally delete a post and give other consequences without moderator oversight.
No reason everyone can't be invited to take a look, too
@Undo Sure, but your trusted people have to independently make a call on it
@Mithrandir I dug some data out on this a while back. Lemme see if I can find it.
Is it necessary for anyone with privilege to be able to !!/pull? Couldn't it be like a code_admin command insteaD?
In theory, this'd be a sanity check for "did someone blacklist spaces". Anyone throwing a red flag would probably shut it down while we discuss stuff.
@Henders Pulling is useless without ability to change code
I mean, it might be useful for irritating us, but not much more
14:31
Oh that's true, I didn't think about that...
Hang on. Metasmoke has a diff view for its own code. We could probably build a tool around that - let metasmoke collect the diff each week, and get trusted people to approve/reject/comment it, like PR reviews
A reject raises Big Red Warnings, tm.
Just automatically post a pull request on GitHub
Can't find my data... Anyway, @Mith, that data said that something along the lines of 95% of people whose posts got spam-nuked didn't get any penalty because they were already 1-rep; then something like 50% of the remaining 5% didn't get the full penalty because they were sub-100 rep.
@Undo time to resurrect GH required reviews and metasmoke CI?
@ArtOfCode That's irrelevant, though. If a single person gets the -100 when they didn't deserve it, that's too much, MO. Also, I don't want to have those sub-100 rep users lose all their rep either.
Someone impress me with their Metasmoke search capabilities: Which posts have we autoflagged as spam that are not spam?
(That'll be a question asked on any meta post we make)
14:37
we have a view dedicated to it :)
That's just cheating :P
5 in the last month
@Mith that seems extreme to me. Every spam detection system has false positives; yes, these consequences are pretty severe, but they're also easily reversed by a mod. I don't think one accident in ten thousand - or even in more, if we wanted, is too great a price to pay.
@ArtOfCode well, I may be being a bit too paranoid. But a single FP will make people lose some faith in us.
14:40
"I got -100 and IP blocked because of smoke detector"
Not a great headline :P
Some, yes. Our job is to accept that, and offset it by showing people what we can give them in return for that one false positive.
@ArtOfCode Good read some of the comments on bluefeet's MSO post about the comment flagger. Users are attached to their content. Deleting a comment is contentious and has no penalty on the poster. Spam deleting a valid post is very different from a comment. That's what the user's will see. They won't see your numbers.
@Henders "Yup, seen it, system dun goofed. Penalties reversed, and we're working on making the system better."
@ArtOfCode Repeat 5 times a month though.
Why not work on making the system better first? Are we in a rush to get to a full-smokey-nuke stage?
14:42
@Andy You're right, but I wonder if there might be some room for distinction between users' own content and spammers' content, which nobody likes.
Remember: You can't get a 100 rep penalty if you've got 1 rep to start with
@Andy less than that, because we'll require higher accuracy
Ah. True
could also lock it to 1 rep to avoid the rep penalty
280/1/1 gives us 99.99% 25117 tp v. 2 fp.
14:43
@ArtOfCode Sure there is, but we are talking about false positives here. It's valid content that we thought was spam.
@Henders We will, but it'll be continuous improvement. If we kept trying to make it better before launch, beyond a certain point we'd just never launch.
@Undo did we not have the same 2 fp when we started in January? So literally zero FPs actually autoflagged with those settings?
probably
@Andy Deleting comments is also seen as low-value by many users, I don't think Spam is seen in the same light
The solution, obviously, is to fly someone out to the homes of those posting false positives and yell at them so they learn not to post spam like content. I volunteer for these paid trips.
I like it
14:44
350/1/1 gives us 17.2k true positives, zero false positives. Hard to argue with that
@Undo Can I pick out a handful of users that will? :)
@Andy Aye. I'm just wondering if that's not slightly different to comments, which are always user content, as opposed to spam/spam FPs which are only sometimes user content?
Probably :P
@Undo Bet you can drop that to 300 and get pretty similar stats
one or two at 300. I tried :P
14:46
@ArtOfCode I'm not completely understanding.
He's saying that folks might not be attached to spam like they are with something they posted in good faith
@Andy With comments, a TP is user content. So is an FP. With spam, an FP is still user content, but a TP is not - it's trash.
Ah. My lightbulb has flickered.
310 weight for 1 FP
it's not even an FP, it's NAA
and absolutely terrible while it's at it
Hackles go up when you delete people's stuff. If you can make it clear that "if you're reading this, this will probably never touch you" maybe they'll de-hackle.
that... almost looks like spam
14:48
aye
yeah, that's spam. Deleted as such
And user destroyed.
What's going on here?
Autoflagging discussion
Heh, that was my feedback. Changing to TP.
14:48
Is this about autoflagging
probably doesn't quite count as spam because Patents is weird, but it's not good content
@ArtOfCode that looks... very, very, similar to the other one.
Looks like foreign chars from before we supported them
So we're considering increasing the amount of flags based on weight?
14:50
Yep
@quartata or some other metric, yeah
And how to easy folks into it
Hmmm
301 weight gets you 100% accuracy
lol
14:51
and 17462 TP
Presumably we don't want to use 6 flags
you're still looking at 30-40/day there
@quartata For now
Ultimately, the end goal has always been to delete spam. 6 flags is the way to do that, eventually
Also, this:
Mar 18 '16 at 19:33, by Undo
observation: projects stop growing when they become change-averse.
heh, the last part of this isn't quite so true any more
I think our biggest problem is going to be handling the community reaction. The technical side we've got figured out. It's just changing a few numbers and letting the system do it's thing.
14:55
Not exactly
it's a few people writing a few more bits of code, but it's not difficult
Pedants :P
code is technically numbers
numbers are technically electricity
My first thought was assigning a new threshold for each level of flags beyond the 98.5%/3 flags
14:58
99.5%
Yep, that's what I was thinking
But it doesn't fit with how we do criterion. Do we use 4 flags just because one user has a criterion that fits?
Check the post weight against the accuracy numbers we have.
The problen is that users have a criterion that determines accuracy
Basically do the same thing flag condition preview does
The criterion determines the minimum accuracy the user wants. Doesn't mean we can't be more confident about a single post
Take the post weight, rep, etc. and run it against previous posts to see what our track record with that post profile is. There's your accuracy number
15:00
if post.accuracy >= criterion.accuracy
  post.spam_flag
Then map that to a max flag count using whatever magic you want
Hmmmmm
actually, it'd make more sense to do it the other way around
@ArtOfCode More (post.accuracy * n).to_i.times do |i| { p.flag } or similar
We just set the number of times we're willing to flag.
afk, should get something done today. Cya folks :)
@Undo I'm going to get that on a T-Shirt. Although... I like my current T-Shirt so maybe I'll just stick with this one.
15:03
You should all be pleased to know that I horribly broke a system...and it wasn't Smokey.
You're welcome
standing ovation
J F
J F
@SmokeDetector k
In that case it no longer makes sense to flag based on available criterion for the 3 flag level and only use accuracy to determine extra flags
In effect what we're suggestinv really is that the system should maintain its own minimum criterion, and users canbe more conservative if they want to be excluded sometimes
this has always kind of implicitly existed
Oh, so the criterion we set don't matter much?
yes they do
they determine whether or not your flag gets used
they are quite literally one of the central tenets of the system
what quartata is describing is already how it works, but only in the fact that your conditions have to be at least 99.5% accurate - that 99.5% is the system-minimum accuracy
15:08
Yeah Art gets it
right, but I mean, I decided to bump up the required minimum weight in exchange for having a higher maximum rep, in case someone who was borderline at first got worse; if there is a minimum threshold for any flags to be cast, then that kind of tradeoff doesn't work the way I thought it did
But
From a code standpoint it's beneficial to maintain multiple sets of minimum criterion and check posts against that rather than "searching for available flaggers, then try to get more if we meet a certain accuracy threshold"
@Sconibulus When you're setting up your conditions, the percentage at the bottom that you get from hitting Preview is the ultimate governor of when your flags get used
if it's < 99.5%, it'll be rejected
above that, the higher it is the less your flags get used (but the more accurate it is when they do get used)
oh, huh
so the actual conditions don't matter much?
yes they do
15:14
Bonus points for if we make these new criterion visible so that people don't have to experiment until they get the lowest possible
@Sconibulus currently the system only autoflags if there's someone with the right criterion available
with no consideration for accuracy outside of when the criterion were originally set
now that accuracy matters at flagging time this doesn't make sense, hence my wall of text
We can still use the same condition model, we're just moving from matching the numbers to matching the accuracy
15:31
What command line email tool should I use for Linux servers? I'm looking for something that is widely available across the Linux distros.
SSH to Gmail :-P
I mean, IMAP
mutt if you want something interactive, mailx if you want to use it from scripts
mailx it is then. Thank you
@ArtOfCode elaborate?
15:44
if the concern is finding the actual criterion that's not hard
We keep the model we have, but instead of being a query for where weight, rep and reasons count are above the required, it's a query for where accuracy is greater than required
Accuracy of the user?
[ SmokeDetector | MS ] Username similar to website in answer: djago-rest-auth multi token by user by Raja Prasanna B on stackoverflow.com
naa- by J F
But that's accuracy of the user
And what are "required" in the first query
we don't have the minimum criterion as requirements that's the point
[ SmokeDetector | MS ] Username similar to website in answer: Multiple Token Authentication in Django Rest Framework by Raja Prasanna B on stackoverflow.com
15:54
Second time... Spam?
tpu- by J F
tpu- by Mithrandir on djago-rest-auth multi token by user [MS]
Here one second let me get off of mobile and then I can try to present my case a second time
This time with proper spelling
J F
J F
> Did you mean "speling"?
speeeling
OK here's the scoop
16:00
Currently when a user signs up for autoflagging, they put in whatever criterion they want and the system verifies that it has 99.5% accuracy before adding it
Then when a post is reported, Metasmoke checks to see if there are any users with criterion that match the posts, up to 3
@quartata So currently, when we get a post, we do a query that goes something like FlagCondition.where('min_weight <= #{post.weight} AND reason_count <= #{post.reason_count} AND user_rep >= '#{post.user_rep}')
When Metasmoke does this, accuracy isn't involved at all, it just implicitly knows that these criterion have to be good enough otherwise they wouldn't be here
In a new system, we'd be doing a query more like FlagCondition.where('accuracy <= #{post.accuracy}')
But that doesn't make sense
Oh yes it does :P
why does it not?
16:03
First off what is post.accuracy
a theoretical calculated value based on the post's reason count, weight, and user rep
We take those three, and find out how accurate that combination of values has been in the past
Restart: API quota is 18424.
OK
But then you're not actually enforcing the users' criterion
You have to do both
Calculate accuracy for how many flags and compare criterion for which users to pick
That's ugly
smashes reject button without looking
Just because it was red...and had "Do not push" on it
J F
J F
16:15
Huh?
@ArtOfCode Do you get my point?
If not I can construct an example
An example would be helpful
speaking of, my example didn't actually make much sense... lemme try again
Ah, well, my button smashing was correct then :)
Suppose a post is 180/2/1. Someone with 150/3/1 could flag it even though the number of reasons don't match
You have to check both accuracy and criterion
What I have in mind takes accuracy completely out of the picture except for a once a day cron job
Calculating accuracy every post is expensive anyways
16:25
@quartata what do you have in mind?
calculatinv the criterion that maximizes TPs caught for each accuracy threshold
that becomes the minimum
there you go, this makes more sense @quartata
some_formula_involving_accuracy - heh
Serious question, aren't the >= and <= backwards? (Or, maybe I don't know ruby well enough)
No, it's just counter-intuitive
(that's SQL, anyway ;) )
A flag condition has a minimum reason count, therefore the post reason count has to be greater than that value
post_reason_count > minimum_count
minimum_count < post_reason_count
Ah. Makes sense
16:52
What is the actual purpose of this channel?
You can't really make diamonds here, can you?
Is it a general chat room or what
spam, spam and spam
and diamonds
So it's general.
but spam is often used
well, there is a link, right? charcoal-se.org
ohh
So we just spam so that the bot knows what spam is?
or what
No. The bot in this room watches the network for new posts and determines if they are spam or not. If it is spam, it is posted here and elsewhere so that users can handle it
16:55
right...
¯_(ツ)_/¯
ciao!
oups one sec ¯\_(ツ)_/¯
there we go
awesome
Discord actually has a command for that emoticon (it's quite famous.) /shrug <text> = <text> ¯\_(ツ)_/¯
17:13
No such luxury here.
17:25
[ SmokeDetector | MS ] Offensive answer detected: Why is hibernate returning a proxy object? by Fuzz Nuts on stackoverflow.com
tpu- by Henders
17:44
[ SmokeDetector | MS ] Bad keyword in body: How to access JSON data in classic ASP by Ted Jang on stackoverflow.com
fp- by J F
J F
J F
sd - why
1. [:39429731] <skipped>
2. [:39429721] Body - Position 2063-2069: Sbobet, Position 2072-2078: Sbobet
J F
J F
15 hours ago, by tripleee
!!/blacklist-keyword sbobet
@tripleee why
@wolfboyft No, but we have some regulars here that became moderators, hence "where diamonds are made" :)
Does anybody know how many?
Jul 17 at 11:42, by Magisch
Plus there's like what 10 moderators in this project.
Some of them (but not many) were moderators already.
17:49
I suppose it's not surprising as mods hate spam ;)

« first day (1367 days earlier)      last day (2749 days later) »