The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Depression, substance abuse, family violence, or a lifetime of pain; whereas all the youth enjoys using words that their elders find offensive, and behaviour being modelled since you're raised.
I "would like to hear what study you based this statement on" (I won't go into detail about how making that demand of everyone one responds to is generally indicative of trollish behaviour).
I'd also like you to define what you believe to be the causes of most instances of "Depression" and many of "substance abuse".
I think you'll find that the two main causes are those given in my posting (I simply expressed them in a way that avoids overly emotional connotations), so "firmly disagreeing" with those statements equally firmly disagrees with your own.
And that's not to mention that "family violence" falls very, very clearly under the heading of "being forced by others to behave how one does not want to behave."
Eddy Vluggen wrote:
we can prevent the messy ones and give those who would a dignified end. Still, that's not allowed
In whatever (I will resist saying "backward or fanatically religious") place you inhabit, that may be the case, but it is perfectly legal here -- I personally know two people with one parent each who has felt compelled to follow that route.
I was not in a position to discuss their decision with either of them -- but discuss it is all I would have done; I most certainly would not have argued against it.
And I think that it is entirely clear that I was talking of being ostracised by peers, on- and off-line. Parents rarely ostracise their children for a psychologically harmful length of time.
But how about we have a CP New Year's resolution not to discuss such bloody miserable topics in a forum "for those who code"? Discussions of such matters between non-experts (i.e. those of "a little learning") are rarely useful or constructive.
I wanna be a eunuchs developer! Pass me a bread knife!
A few days ago I asked if anyone would be interested in an article/tip about setting up WSUS. The response was somewhat underwhelming (and focus quickly turned to the fact that I use a 10-year old version of OneNote) so I decided not to bother.
Anyway. I've been struggling with getting clients to connect to it ever since. Until this morning, when I changed the policy that names the WSUS server to include the port at the end of the string (:8530). After making that change, and then refreshing the policy on client endpoints, they started trickling in almost immediately.
This wasn't necessary before. The port hasn't changed. Why it's suddenly needed in this version, I don't know. Or when it became a requirement, I don't know (it could've been introduced in 2012, 2012 R2, 2016 or 2019...and I'm not about to review the documentation for each to try to find out).
The lesson, I guess, is don't take anything for granted...like assuming newer versions work the same as old versions (even though, based purely on the UI, you'd think MS hasn't done any change to WSUS).
Of course I know the difference between a URL and a name. I simply wrote that the server was "named" in that string because the URL happens to identify the server...by its name...
The change was made in version 6.2 from the default of 443 to 8530. The reason the URL did not need the :8530 before is because HTTPS defaults to 443.
I'm not following. The default (non-https) port was always 8530, and that's how I've always had it configured (by omission).
Are you claiming my older server, by not having any port specified, was therefore defaulting to an https connection, and not using port 8530, and now the newer version is enforcing https over port 8530 and effectively no longer using https over 443...? I'd love to see the page documenting that. Even that doesn't make sense, since the policy for my previous server had always been set to:
•On WSUS 3.2 and earlier, port 80 for HTTP and 443 for HTTPS
•On WSUS 6.2 and later (at least Windows Server 2012 ), port 8530 for HTTP and 8531 for HTTPS are used
So...even though WSUS has been widely known to be using port 8530 since day one, if you don't specify the port, it'll default to 80...
I've always made the assumption that if it "uses port 8530 by default", then if not specified, then that's the port it'll use. Meaning, even though I didn't specify one, the initial handshake might be done over port 80, but then switch over to port 8530. What the docs infer is that even though 8530 is the default, if not specified, then it'll implicitly use 80 and stick with that. That's a confusing definition of "default" if that's the case. And if it is, then I'm not sure how it would be technically wrong to instead say it's using port 80 by default. To me, "by default" has always meant "this is what will be used if omitted".
Anyway...again, the bottom line remains, don't take anything for granted.
When I win the new year lottery, I promise to treat myself on a trip with the Rocky Mountaineer[^]
Otherwise I will have to settle for a week in the Belgian Ardennes, which is the closest to mountainous terrain we have nearby.
Turkey white meat is unappealing; I eat (devour) the back half -- this goes for chickens as well.
White meat is good only for sandwiches.
When I were a lad my mother cooked a turkey once a month. (No, not the same turkey.)
Turkey was great for us; after my dad and I came back from our annual hunting trip(s) we would have moose (or caribou) in all the variations possible: steak, roast, sausage, ground, pot roast - my dad actually made corned moose a couple of years - even he couldn't stand it (800 lbs of moose takes a while to process and eat - we did our own butchering). Caribou was closer to elk, but still generally the same. One year I got a largish black bear on bow and arrow, that was pretty good.
A human being should be able to change a diaper, plan an invasion, butcher a hog, navigate a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects! - Lazarus Long
Last Visit: 2-Apr-20 3:22 Last Update: 2-Apr-20 3:22