« first day (33 days earlier)      last day (601 days later) » 

Anonymous
1:04 AM
@Pavel Not yet, I don't think
 
Anonymous
@Pavel We'll probably end up switching. The great thing is, if the SQLAlchemy stuff is set up right, the DB engine doesn't really matter at all.
 
Downgoat
Downgoat
1:55 AM
@Pavel yes, but if you try to submit and you'll get a 403 rather than nice form validate
@Mr.Xcoder oh crap not this again
@Mego can you restart the server
 
Anonymous
Sure
 
Anonymous
Restarted
 
Downgoat
Downgoat
Google updates their public login keys every ~4 days-ish and right now the server doesn't update. I should probably have a job that updates them every 24 hours or so
 
Anonymous
Sounds like a job for a recurring Celery task
 
Downgoat
Downgoat
idk anything but celery but will google about this weekend if I have time
 
 
1 hour later…
Anonymous
3:18 AM
 
user202729
user202729
10:18 AM
Yes. But close votes are often not fast enough (how many votes are enough for closing?); and... close votes doesn't include comments. So if you see an unclear question, instantly VTC as unclear and then comment?
What about making Sandboxed questions at the same place on Main, but mark them as "currently in the Sandbox"? Even if we have sandbox.codegolf.stackexchange.com , I don't think it will be helpful if people don't know about it.
------
How long should questions be in sandbox? In the current state some questions in the sandbox are forgotten by the OP.
 
Anonymous
10:36 AM
@user202729 Sandboxed challenges will be viewable on main, but not answerable. They will become unsandboxed once a certain threshold of "looks good" reviews have been received - that threshold will lower over time so that abandoned sandboxed challenges can still make it to main.
 
Anonymous
If you have any suggestions for handing unclear close votes, I'd be happy to listen
 
user202729
user202729
That's also what I thought about.
How many close votes do you think is enough for question/answer?
 
Anonymous
5 seems to work OK on SE, but it doesn't have to be the same here
 
user202729
user202729
11:04 AM
Re "if an answer is good and it continues to get +1s, that's not a bad thing." - the bad thing is late answers are more likely to be forgotten about.
Do you think 5 vote is too much?
Because if someone VTC as unclear, probably they have their reason... (assuming users can be trusted)
 
Anonymous
I'm on the fence about giving hammer privs to users through rep
 
caird coinheringaahing
caird coinheringaahing
4:39 PM
@Mego IMO, it should take 2 hammers to close, whatever the reason, so that it isn't unilateral
 
 
3 hours later…
Poke
Poke
7:39 PM
@cairdcoinheringaahing then it's not really a hammer is it? May as well just leave it to votes
personally i don't think regular users need hammer privs
this website is specific to programming puzzles and code golf. we're not a community-driven question and answer shop
leave hammers to mods/admins
 
Anonymous
I could see a compromise: letting experienced users cast up to 2 close votes per challenge
 
Poke
Poke
I like what user202729 was hinting at. If someone votes to close, then they should be required to leave a comment or something
or upvote an existing comment
 
Anonymous
Yeah, I like that idea, too. Even if it's just the system posting a canned comment for the close reasons that don't need additional explanation.
 
Poke
Poke
and maybe if a challenge gets to like -5 rep, we pop up a little message reminding them to leave a comment or something
it's pretty crappy when you ask a question and have a -5 with no comments about why
 
Anonymous
I'm not sure how I feel about requiring comments alongside votes in any capacity. That detracts from the anonymity of voting.
 
Poke
Poke
7:46 PM
i wasn't saying require it
but have a little message pop up that recommends it or something
"You're the 5th person to downvote this challenge. Consider leaving a comment so the poster knows how they can improve"
something like that
 
Anonymous
The issue with that wording is, not everything can be improved. Some turds shouldn't be polished.
 
Poke
Poke
fair
 

« first day (33 days earlier)      last day (601 days later) »