recentpopularlog in

kme : stackoverflow   19

Brothers, I must go… - Christianity Meta Stack Exchange
There is one text from 1980-s, linking to it was allowed in early SO days, but banned later. It was the self-induced prophecy: "Community standards do not maintain themselves: They're maintained by people actively applying them, visibly, in public. Don't whine that all criticism should have been conveyed via private e-mail: That's not how it works. Nor is it useful to insist you've been personally insulted when someone comments that one of your claims was wrong, or that his views differ. Those are loser attitudes..... – Arioch Oct 1 at 11:00
.....There have been hacker forums where, out of some misguided sense of hyper-courtesy, participants are banned from posting any fault-finding with another's posts, and told “Don't say anything if you're unwilling to help the user.” The resulting departure of clueful participants to elsewhere causes them to descend into meaningless babble and become useless as technical forums.". They made this choice, it took half decade to make it surface to mods, another half-decade to make it surface to users. "Transactional costs" of saying something would eclipse costs at the very message. – Arioch Oct 1 at 11:02
stackoverflow  community 
7 weeks ago by kme
Keyboard Glyphs - Meta Stack Exchange |
You need to use the <kbd> HTML tag:
<code class="language-html">
becomes CTRL+
stackexchange  stackoverflow  markdown  formatting  keypress  hotkey  solution 
february 2019 by kme
-fstack-protector-strong « codeblog |
The Perl module Net::SSLeay requires this feature of GCC 4.9:
There will be a new option in gcc 4.9 named “-fstack-protector-strong“, which offers an improved version of “-fstack-protector” without going all the way to “-fstack-protector-all“. The stack protector feature itself adds a known canary to the stack during function preamble, and checks it when the function returns. If it changed, there was a stack overflow, and the program aborts. This is fine, but figuring out when to include it is the reason behind the various options.
gcc  compiler  security  stackoverflow  stacksmashing  errormessage  solution 
february 2018 by kme

Copy this bookmark:

to read