Never change, Stack Exchange.
Never change, Stack Exchange.
If you look honestly at humanity, the motivations of the average person are selfish and unenlightened. An internet mod enjoys authority and an elevated sense of self worth by putting other people down.
There really are some people genuinely enthused by virtues such as intellectual discovery and shared dignity, but they're in short supply and likely to be outnumbered in the population clamoring to become internet mods.
I've had a few posts removed from a SO site after I corrected someone who happened to be a mod there. And the Innocence Project fights to give innocent people their lives back because some prosecutors don't want a scratch on their resume.
I think it would be better if we acknowledged these realities more-often rather than pretending all the evil people in the world died in Nazi Germany, or wherever, and they weren't just normal people.
I think this is also why I always retreat into nerdy or intellectual endeavors. Not because I am particularly intelligent, but because the real world is so ugly.
There is no real excuse here as far as human cognitive ability goes. The problem is with morality.
I think these examples show that as humanity goes forward I think moral integrity/intelligence/bravery is more important to develop than our purely technological and scientific capabilities.
The third or fourth cover actual use case like solutions, of course that leaves more room to quibble and vote down, but you learn more from it.
It's the difference between answering a trivia question about a car vs actually fixing a car.
https://serverfault.com/questions/966765/private-network-dns...
Closed due to "off-topic". With a comment that basically says "I don't like your problem, try to be more normal."
I suggest having a look at dnsmasq [1]:
> -S, --local, --server=[/[<domain>]/[domain/]][<ipaddr>[#<port>][@<source-ip>|<interface>[#<port>]]
> Specify IP address of upstream servers directly. Setting this flag does not suppress reading of /etc/resolv.conf, use --no-resolv to do that. If one or more optional domains are given, that server is used only for those domains and they are queried only using the specified server. This is intended for private nameservers: if you have a nameserver on your network which deals with names of the form xxx.internal.thekelleys.org.uk at 192.168.1.1 then giving the flag --server=/internal.thekelleys.org.uk/192.168.1.1 will send all queries for internal machines to that nameserver, everything else will go to the servers in /etc/resolv.conf.
[1]: http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
Side note: I find a similarity between SO and HN. Both can feel pretty hostile and over-the-top with penalizing you for not saying things "the right way." But as much as it does annoy me sometimes, these are two of the most useful websites for my purposes.
Working around other people's hangups is a real pain, but that's basically what a large portion of participating in a pseudo-anonymous internet forum is about, unfortunately.
has a long discussion of this problem.
Not sure if the curators are unaware or simply don't care as long as they're still getting fresh questions for whatever's shiny and new.
In practice, nonetheless, it is now the last place I look, not the first, and also the last place I contribute. There are plenty of other forums for relevant and current answers, and without dripping poison.
Would you mind listing a few examples?
In quite a few cases the official dev forums for a particular vendor or technology are actually very active, and I think that's because forums just got a lot easier to implement. For example I get a lot back from the Apple Developer forums (not the public discussion community, which is hot garbage) and Vue.js's own forum.
A fair chunk of what I previously used Stack Overflow for (finding code snippets to learn from) has been replaced by the ease of browsing public repositories on Github.
For the first 5 years or so, Stack Overflow was amazing. For newer subjects that haven't changed significantly in a the last couple years, it's probably still amazing, but the shelf life on this is much shorter in general, because new subject generally change quite quick (conversely, when Stack Overflow was first filling up, all the C/C++.Perl/Python/Bash etc stuff were long past their high churn stages).
When all these sites were new and shiny and still filling in the gaps, this wasn't a problem. Now that we've gotten a decade or more of some of them, they have the problem of being filled with information that was highly relevant at one point, but as it's lost relevancy over time is still treated as relevant.
As the timeline of major changes to these crowd-sourced repositories of knowledge goes, I think the next major advance will be a good algorithm to degrade relevancy (points?) over time with the ability for people to "vouch" for data as still accurate, or to "refine" data to limit the scope it applies to when the subject has expanded and it no longer is as accurate as it was because of that.
E.g. an answer for a Python which works only for Python 2.X but at the time applied generally because Python 3 had not been released. After Python 3 comes out, that answer either needs to be less relevant because it's only sometimes correct, or refined to note where it does and does not apply, in which case it retains its relevancy and should hopefully not crowd out data for the portions of the subject it does not apply to (Python 3 in this case).
I'm convinced this, or something like it, is the next big thing for crowd sourced data, as it becomes more and more important as our collective online data ages.
Edit: It's worth noting Google has likely already solved this, at least for their problem space. Then again, the way Google could be considered to be a repository of crowd sourced data is slightly different than most sites. That said, I wouldn't be surprised to hear they have a solution, either in place or planned, for how to deal with this affecting the knowledge graph.
- [python-2.x] https://stackoverflow.com/questions/tagged/python-2.x
- [python-2.6] https://stackoverflow.com/questions/tagged/python-2.6
- [python-2.7] https://stackoverflow.com/questions/tagged/python-2.7
- [python-3.x] https://stackoverflow.com/questions/tagged/python-3.x
- [python-3.6] https://stackoverflow.com/questions/tagged/python-3.6
- [python-3.7] https://stackoverflow.com/questions/tagged/python-3.7
- [python-3.8] https://stackoverflow.com/questions/tagged/python-3.8
and so on.
Part of the problem is that at the time of the question the tags might be entirely sufficient but become less so as the the subject changes over time and new tags are available.
Also you could try retag a question with the appropriate version tag, e.g. [python-2.x] or [python-3.5], so other people will know that when using a newer version of Python there might be other (better) answers.
I use python versions to illustrate the point. That doesn't.meannit encapsulates all the nuances. For example, take a question that asks about the best way to handle HTTP client needs in Python that doesn't include an answer suggesting the requests module[1] because it predates it? Its not strictly tied to a python version, but it does.auffwr for being older, and adding a new, better answer years later may take years more to be ranked high in the answers (if ever). Can.that problem. Be solved with tags? Maybe. Can it. Be solved well by fairly free-form community decided tags? I doubt it.
> Also you could try retag a question with the appropriate version tag, e.g. [python-2.x] or [python-3.5], so other people will know that when using a newer version of Python there might be other (better) answers.
Yes, and people could instead just volunteer their time to accurately rate every question and answer on some absolute scale, say 1 to 1000. Unfortunately systems like that don't scale because it requires too much effort from the individual, and people tire of it.
What sites like Stack Overflow and Reddit spearheaded was to instead give users many tiny, easy, and individually insignificant decisions which when taken in aggregate allowed for the emergent behavior to show its value.
I suspect we'll see a similar solution (at least in part) to this, where some small behavior is incentivized to not just generate and rate the data, but curate it over time. Tagging may be part of that solution, but I think it's fairly inadequate in its current incarnation.
1: I'm assuming requests is still popular. I'm not really a python programmer, but it's more common than my preferred languages so I figured it would convey the point easier.
For instance, Ember.js is still seeing lots of development and has changed drastically in some ways, but every time I've searched SO it almost always brings up questions from ~2013. I'm convinced that a lot of the so-called "learning curve" would go away if Stack Overflow was wiped out of existence, which is a weird thing to say having once been a big fan of Stack Exchange.
A better way to find solutions is to just join Slack/Discord/IRC servers for different software communities and ask questions there.
Don't even get me started on the toxic attitudes on SE.