9 ms·
This is covered early on in the article.
by devin 5y ago
This is covered early on in the article.
- millerm 5y agoIt’s sad when most people discuss things based on a one line title of something they haven’t read. Many questions here were answered in that article. I recently asked someone on a different site “didn’t you read the article?”. The obvious answer I alluded to was “No, I don’t have time.” Yet they managed to post about 15 different comments asking more questions about the article (title). I really wish there was a way to have a public forum with proper discourse with the caveat that people must read the material before they comment on it.
- 5cents 5y agoThe technical blog of the public broadcaster of Norway has implemented exactly this: https://nrkbeta.no/2017/08/10/with-a-quiz-to-comment-readers-test-their-article-comprehension/ https://nrkbeta.no/2017/08/10/with-a-quiz-to-comment-readers... The quiz module is open-source (https://nrkbeta.no/2017/03/06/our-comment-quiz-module-is-now-open-source/ https://nrkbeta.no/2017/03/06/our-comment-quiz-module-is-now...) and available on github https://github.com/nrkbeta/nrkbetaquiz https://github.com/nrkbeta/nrkbetaquiz
- millerm 5y agoThanks for the links. :-)
- thomascgalvin 5y agoIt's mentioned briefly in the article, but no instructions are given on how to properly configure busy_timeout and WAL to scale above more than a few concurrent writes per second.