I flagged this answer as Spam.
The user answering the question is named Ammar Al Hashmi, and in his answer, he links to a blog with the same name at the top, and the link to the blog also includes the folder name "@ahashmi06", which was what clued me in to the undisclosed relationship.
My Spam ...
@ArtOfCode I am aware of 30 code admins. Currently in this room: ArtOfCode, Zoe, Henders, DavidPostill, doppelgreener, WELZ, Mithrandir, bwDraco, Ferrybig, paper1111, John Dvorak, Makyen, Thomas Ward, Andy. Not currently in this room: iBug, Byte Commander, angussidney, K.Dᴀᴠɪs, Suraj Rao, tripleee, Glorfindel, Yvette Colomb, CalvT, ProgramFOX, Ashish Ahuja, user5389107, Paul Stenne, Undo, quartata, NobodyNada.
@Zoe That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
@Makyen That pattern looks like it's already caught by Toxic body detected, Bad keyword in body, Bad keyword in answer, and Toxic answer detected; append -force if you really want to do that.
@Makyen Added penis\Wbe\Wupon\W*him to watchlist
CI on b891941 succeeded. Message contains 'autopull', pulling...
@WELZ FIRE only checks new messages from SmokeDetector. The edit removed the changes FIRE made to add the FIRE button and the new text isn't checked to re-add it.
@ArtOfCode Yep, FIRE completely relies on those links being in the format of having an explicit URL. The changes to get away from using it (which it should, because the URLs aren't unique) are quite significant.
Is there an MS API which allows us to access the information directly using that information (i.e. without knowing it's an answer or question in order to construct the full SE URL)?
Right now it looks like there isn't a way to figure out the MS post ID without either using the SE API to determine if it's a question or answer, or to fetch the page and scrape for the SE URL.
You could hit the /posts/uid route and read the Location header back from the 302, that'll contain the ID. But given that there'll be an API for it pretty shortly... probably not entirely worth it
Okay, @Makyen not deployed yet, but you can assume there'll be an /api/v2.0/posts/uid/:api_param/:native_id route that you can use. Identical output to the URL-based route, filters available.
I flagged this answer as Spam.
The user answering the question is named Ammar Al Hashmi, and in his answer, he links to a blog with the same name at the top, and the link to the blog also includes the folder name "@ahashmi06", which was what clued me in to the undisclosed relationship.
My Spam ...
