@Magisch If we've got a few things that would help us pick up on spam, then they'd be useful to throw over to the team, yeah. Apart from that, I'd like to keep as much of this conversation focused on integration between the systems as possible
Ideas for integration would be awesome though, if y'all have got any
I think the biggest strenght of this project is not the keyword filtering itself, but the fact that we can cast a broad net to catch most possible things and then filter out the not-bad stuff per hand
Many times, when there's a report here and no feedback, other people will actually feedback because they think there isn't any yet, generating duplicate work
This tool on MS shows invalidated feedback. If you see the "invalidated by" column, you see some feedbacks have been invalidated by "system". I thought only users could invalidate feedback. What is "system"?
Namely, if your feedback is being ignored, you feed back on a post, and then another un-ignored user feeds back with the opposite feedback type, yours gets invalidated.
@Undo can you check access control headers on /api/w/post/:id/feedback - I think I've got them right to allow requests from anywhere, with creds, but maybe not. If they're right, I think metasmoke server needs restarting.
In other words, @Magisch, I wrote the rest of the script right first time, but the access control headers on the API route I need are screwing everything up :)
@Yvette "We're definitely going to fix this. Kevin and others will be discussing the particulars this week, though it may be a bit longer before anything gets rolled out (as the variety of suggested changes here demonstrates, there are a lot of factors that should be taken into consideration). Once changes are made, reputation will be recalculated for anyone affected and we'll post an announcement here on meta." source
Many people will lose over 3k rep from that, myself included
I'm not too fuzzed about that, but a whole lot of people will go ballistic
I earned only 79 rep, and that is 4 for two approved changes, and +60 from one and +10 from another, +5 from one citation. I spent approximately one hour on the +60, adding and rewriting four or five sections (which got approximately 2 upvotes each, and some of them got a little more)
@Undo another MS deploy when you've got a moment... I think the PUT request was throwing things off for some reason, so I'm just gonna switch the write API to POSTs.
It's done in config, so in theory if the server hadn't been restarted after the headers were configured, then it would fail - but the server has been restarted.
I've checked the header syntax, and that's correct
The only thing I could think of was using PUT requests might not have made it very happy.
So I switched to POST, which - in theory - shouldn't require a preflight request, and should be a simpler setup
@redredwine The one I tested above. First line is title.
@redredwine But it says "URL in title" although the URL in the tested text is several lines down. How can I tell the test command what is title and what is body?
