Also, I'll throw this out there: Apple is not incented to start forced obsolescence. Part of the reason they can sell a $1000 new phone is because the previous generation can't be had used for much less than that anyway. Obsolescence would break that cycle.
They could be in the near term, but they generally look fairly far ahead.
Regarding the core requirements, I think that if you have it... there should be an extra grace period in case you are away for a week or two in a month... you don't lose it from lack of feedbacks. Possibly, you only need to meet the requirements every other month or something.
@WELZ eh, 60 a month was kinda designed to do that anyway. You can do 60 in a day if you want to, so being away for a week or two shouldn't affect you much
@HyperNeutrino Body - Position 1727-1749: sites.google.com/site/, Position 1839-1861: sites.google.com/site/, Position 1936-1958: sites.google.com/site/
@HyperNeutrino The !!/blacklist command has been deprecated. Please use !!/blacklist-website, !!/blacklist-username,!!/blacklist-keyword, or perhaps !!/watch-keyword. Remember to escape dots in URLs using \.
@WELZ Because there was a comment war going on under my post, because someone fixed the spelling and grammar and the OP had a massive rant in several comments under my answer, I think it was deleted to avoid massive arguments and to stop things escalating
well yeah but like was wondering as a general case (or specifics) how much slower :P because i know Charcoal speeds up spam handling a lot but idk by how much
@JakeSymons The most it can go up to is defined by the weight of all of our reasons combined. (as every thing they add to a post that triggers another reason will add to their "score"...)
the only way it'd get that high is someone really trying to make a weight that high (they would have to know all the triggers etc.)
@WELZ I need to be a core to use that, although I do the 60 flags a month :)
Is there like a !!/test sandbox thing so you don't have to put it through the chat. I don't want to get nuked for spamming smokey with !!/test all the time
> Would not be caught as a post, title or username.
> Pattern-matching website in body, pattern-matching website in title ---------- Title - Position 3-20: supplementhelp.co Body - Position 3-20: supplementhelp.co
@WELZ If I had like infinite rep, I would do it. Like Jon Skeet, I was trying to work out how many spam posts he would have to write to get into second place but it was such as large number :)
@HyperNeutrino I'll now send messages with types debug,all,experimental to room 1 on stackexchange.com. (Note that this will not persist after restarts.)
@WELZ Never mind, I'm sure it will work, I've got to go out in a bit anyway :)
@Art what about a separate room for Smokey to keep it out of the chat so you don't get annoyed, but us bunch of noobs can still play around with !!/test in relative safety of breaking the system and spamming this chat?
This is the highest reason weight according to MS. Put the autoflagging threshold to 1200 and its the only one that comes up
@ArtOfCode Maybe Shog9 got bored of being so All Powerful and All Knowing so he split his form into two, both of which only knew half of the original and only had half as much power, but then they both became All Powerful and All Knowing :P /s
@NogShine IMO, no. It appears to include an actual attempt at an answer. The website appears to be a misguided attempt to provide an example, or at least that's how it's phrased. Editing out just the non-linked domain would make it definitely non-spam.
> Bad ns for domain in body, bad ns for domain in title ---------- Title - idealchoose.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com. Post - idealchoose.com NS suspicious dns1.namecheaphosting.com.,dns2.namecheaphosting.com.
@JohnDvorak I'm not seeing that here, generally. I've seen two things which might be what you're describing: A) AIM doesn't account for the possibility that a user will change their feedback. For example, a single user can be shown as having both a fp and a tp feedback, whereas new feedback from the same user should overwrite an existing feedback.
B) Due to the MS WebSocket and SD reports referencing posts by URL, there's ambiguity when there's more than one report for the same URL. This affects both AIM and FIRE (maybe other scripts). I'm working on resolving this for FIRE ((A) is done, (B) requires significantly larger changes, but is partially done). I haven't looked at doing so for AIM, but (A) should be easy to resolve.
In a battle of "Which would Andy rather mess with in his house?" between water and electricity, I pick electricity. It's easier to clean up. If I screw up, I don't have to clean up. Water just sucks.
I've given up with that Smokey thing now after all I don't want to get nuked out the room because I am trying to avoid Breaking Everything. It's turned into an office for me now, as you can't delete stuff :)
@HyperNeutrino I'll now send messages with types debug,all,experimental to room 1 on stackexchange.com. (Note that this will not persist after restarts.)
(feature)
@thesecretmaster figured out a pretty good solution:
def connection_completed
@api_queue = EM::Queue.new
...
@api_queue.pop(&:api_fetch)
end
def api_fetch(item)
...
@api_queue.pop(&:api_fetch) # resume listening
end
