Yes, that's true. I just linked to it for context, since MS doesn't have a record of it. I assume that if someone wants to see the source, any 10ker can provide it. Should I be adding an image anyway?
Ah, I see. It's not very interesting. Here's the full source of the answer "My team and I have been working on an early-stage startup solvery.us. This is a service for technical mentorship which allows mentees gain experience in any IT aspect with help of an experienced mentor. We'd be happy to help you!"
@Makyen check. i'll start digging a little on my end, but unless I know where we're going to cache the requests from a Python object perspective it'll be more of me just puttering around heh.
i did put my 'prototype' of a queue and request object with timestamp for the queue into the bug on SD thouggh :P
Yeah, I know that feeling. I actually took yesterday off, planning to work on SD. Unfortunately, I then got blind-sided by a real-world issue which required I perform a 2 minute task every 6 minutes (or so) for 6–7 hours, which was ... not conducive to concentrating on, well, anything, including coding.
@ThomasWard Writing to disk should be moderately easy. As you've already mentioned, a pickle is appropriate. Writing to disk when MS is down, or while the queue is being flushed after MS was down, is good. We just don't want to be writing to the disk when MS is up and the queue isn't filling (i.e. we shouldn't write to disk when we are/were able to immediately, successfully send whatever it might have been that we would queue if there was a failure or MS was down).
@Makyen correct. we'd have to pickle the Queue object among other things. But it shouldn't be toooo hard to implement. I just have to figure where to implement it.
@Andy Can you submit feedback through metasmoke with a confirmed account, or is metasmoke just for read-only stats?
I've been trailing along in this chat and submitting flags for too long, it's probably time I actually contribute something to the charcoal flagging system :)
@MaximillianLaumeister Yes, you can you can submit feedback through metasmoke. You can do so from post record pages or from the post review queue.
You should be able to do so now, as well as through userscripts and use in-chat feedback via SmokeDetector (as a moderator, you are automatically granted SmokeDetector command and feedback rights). The most commonly used userscripts (GitHub) which interface in chat with SD/MS are FIRE and AIM.
You needed to be given the Flagger and Reviewer roles on metasmoke (done), which is something which isn't set up to happen automatically, mostly due to nobody having written the logic to do so based on somewhat more restricted criteria wrt. the user's associated SE account, and that we can't reasonably do it for all new accounts, due to sporadic spammer and troll attacks on metasmoke.
