@thesecretmaster Rude/abusive. User is aggressively resisting editing. Perhaps You're probably right that fp is appropriate feedback for SD, but it should be flagged, either as R/A or a custom flag. Note that the user deleted their identical answer, which was accumulating downvotes and flags.
@thesecretmaster I agree that post can be edited, Rob has done edited that. If that user rolled back again and starting edit war, just use custom mod flag as last measure.
@thesecretmaster It depends on where you want to draw the line. If it was just this answer, I would wholeheartedly agree that they shouldn't be blacklisted. I'm kind-of on the other side due to the other actions of the user.
do you know if it has stuff for parsing nested JSON structures
as opposed to like building them
hmm just realized a problem with using EventMachine here
firing off a request that will eventually return with a backoff, then doing another one while waiting for that one will lead to a violation without us knowing that we got the backoff
well it's just that have about 200 lines of hell spawn ruby that has a lot of this:
types = config['types']
if !types
raise 'No post types specified'
end
Subscription.delete_all(:bot => bot)
types.each do |type, params|
type_sym = PostType.post_types[type]
if !type_sym
raise "Unknown post type #{type}"
end
...
end
woops indentation came out wrong
substitute types and type_sym for basically any field
lots of validation and looping over things
now I could make my own thing that creates a schema for the JSON
but I was wondering if something else had and jbuilder sounded like the same thing but in reverse
If you have data from AR (or elsewhere, I guess) that you want to turn into JSON in a well-defined schema, then yes jbuilder is what you're looking for
well you can either JSON.parse it in the controller and pass that to jbuilder
Or - jbuilder files are still Ruby files, just with jbuilder injected into them, so you can actually just do standard Ruby JSON parsing in a jbuilder view file
@quartata If you're talking about the SE API, then other requests which were fired prior to receiving backoff may: A) also get a backoff; or B) be rejected with an error. You either need to handle both the cases, or fire off requests sequentially, which will result in significantly lower performance. Note that the hard restriction is 30 requests/s. If you do more than that, then you will be blocked. Also note that backoff is per method (endpoint). ref
I can't look in detail now, but I'll have a look in the morning. I suspect you want a jbuilder file, if/else the error handling, and json.propertyname the fields you want or nulls
@K.Dᴀᴠɪs nope, it's just a report. The idea is that you manually report it, then let others check it and make sure it's spam, and they feed back on it.
[ SmokeDetector | MS ] URL-only title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +5 more: skincaresfreetrial.com/tryvix-australia/ by cujg on askubuntu.com (@ThomasWard @quartata @TetsuyaYamamoto)
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, bad keyword in body, blacklisted website in body, +4 more: basicsnutritionfacts.com/bellanu-cream/ by jayefjeuq on askubuntu.com (@ThomasWard @quartata @TetsuyaYamamoto)
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more: lumalifteye.com/tryvix/ by windhoex on english.SE
[ SmokeDetector | MS ] Bad keyword in body, blacklisted website in body, link at end of body, pattern-matching website in body, potentially bad keyword in body, +1 more: Tryvix The eyes are generally the first by user798611 on askubuntu.com (@TetsuyaYamamoto)
[ SmokeDetector | MS ] URL-only title, bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, +4 more: basicsnutritionfacts.com/bellanu-cream/ by preseven on askubuntu.com (@TetsuyaYamamoto)
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, link following arrow in body, +4 more: www.muscle4supplement.com/tryvix-it/ by pyanaldi on apple.SE
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-7: tryvix Body - Position 1-7: tryvix Username - Position 1-7: tryvix
[ SmokeDetector | MS ] Bad NS for domain in body, bad NS for domain in title, blacklisted website in body, blacklisted website in title, link at end of body, +1 more: onlinehack8ball.website/ by bohirojjer on askubuntu.com (@TetsuyaYamamoto)
[ SmokeDetector | MS ] Bad keyword in body, bad keyword in title, blacklisted website in body, link at end of body, pattern-matching website in body: Ultimate slim pure select by mesiehare on meta.SE
tpu- by iBug
CI on 54efa5a succeeded. Message contains 'autopull', pulling...
[ SmokeDetector | MS ] URL in title, bad keyword in body, bad keyword in title, blacklisted website in body, blacklisted website in title, +4 more: rhinorx90eveningblog.com/instarect/ by Qjtzsloi on graphicdesign.SE (@TetsuyaYamamoto)
> Potentially bad keyword in body, potentially bad keyword in title, potentially bad keyword in username ---------- Title - Position 1-11: L-Arginine Body - Position 1-11: L-Arginine Username - Position 1-11: L-Arginine
> Would not be caught as a post, title or username.
> Bad keyword in body, bad keyword in title, bad keyword in username ---------- Title - Position 1-12: gain xtreme Body - Position 1-12: gain xtreme Username - Position 1-12: gain xtreme
CI on f4535c3 succeeded. Message contains 'autopull', pulling...
