It's "doing nothing" the same way the Secret Service is "doing nothing" when the President is out in public. It's busy making sure something underhanded isn't happening.
You can also get your liver #rekt by taking acetaminophen for your hangovers. Doing so multiplies the damage. Reminding people to take aspirin instead would do much the same thing -- except for the people who can't take normal NSAIDs (like my mother).
Why do so many people (other than the 1% expecting their tax cuts) continually vote against their own best interests? This is what happens when "punishing" some group is more important to the masses than prosperity. If a rising tide lifts all boats, a falling tide eventually beaches them all, but the aforementioned people don't care so long as "teh gays" hit the shoals before they do.
Other than spammers, nobody bothered us when we used alt.binaries.pictures.grotesque for this purpose.
For the record, I was in no way responsible for the "Di Death Pic" hoax... but I know who was, an a.b.p.g regular. It was an accidental hoax anyhow, it was not meant to be taken seriously. We didn't know lurkers would forward it without the disclaimer.
The provider is always and never cheating, simultaneously. They write the rules, and can OP and nerf items at their discretion. It's not cheating because it's their game of Calvinball. It's cheating because it violates the expectation of players that they are whomping on other actual players when they go to PvP land, and because it's inherently unfair to players. But remember, if you aren't paying, you're not the customer. In this case, you're just the background filler for the people who do put up money to roll over.
What exactly were they supposed to do? Disclosing this publicly wouldn't have gotten the 0-days closed any faster but would have started malicious actors scrambling to get their hands on that database. Some already had it -- publicly admit it exists and has been exfiltrated, and anyone with even a passing interest is going to want it.
Now if it had been a database of someone else's 0-days, then they could be expected to at least tell the vendors of the products in question. But when they are the vendor? It's an internal problem.
As I understand it, the Ferengi are a piss-take of Jewish stereotypes, developed by Jewish writers which were at the time about half the team. Failure to grasp satire is not the same as actual racism.
As for other races, I think the stereotyping exists because they just don't want to make the viewers work too hard. You may like grit and shadow and depth like DS9 (I do), but a whole lot of people just don't want to work that hard, or have moral quandaries put in front of them that can't be resolved in 43 minutes. Stereotyping whole races is similar to consolidating characters when books are turned into films. It's non-optimal, but it's also unavoidable.
You mean advice from people who spend more time hanging out on Stack Exchange and less time actually writing production code is turning out to be less correct than advice from people who talk less and do more? Color me surprised. (Not.)
1. Trivial ones. These lead to definitions of words and things like that. I prefer this over spending a paragraph defining terms the author may be afraid people will be unfamiliar with. If you don't need them, skip them. Even if one of these appears useless to you, it's not. It just saved you a few seconds of skimming explanatory text.
2. Fact verification. Sometimes these are pure CYA, so that if something dicey proves to be false, the author can say "it wasn't me that made it up, I was just going with my sources". Other times they are a defense against the troll hordes and autists looking to challenge the basic validity of an article based on "fake news" which really isn't. Unfortunately the only way to tell the difference is to look.
3. The author (or company's) back catalog. This can be perfectly legitimate – why should someone have to paraphrase themselves when expanding on a prior article if you can just read it? But other times it's little more than a scheme to drive more click-throughs. Unless it has a particularly clickbaity title, the only option here is also to look and see.
The solution I implement is to take or leave Type 1, and to launch Type 2 and Type 3 in the background and read them after the current article if indeed I read them at all. Sometimes it is sufficient merely to know where the link goes, to know what agenda is likely to be pushed. This still can result in a Wiki-Walk style vortex, but at least it only pulls me off topic after I've read the initial article.
Mattel doesn't actually build its own electronics, they farm everything out. This isn't unusual, but back when they had a separate Mattel Electronics division, they often rebadged products they hadn't even had a hand in creating. The Aquarius would be an example. If that was the case this time around, then they may have merely decided to cancel the contract, and you'll still see the product as soon as the manufacturer can get someone else to market it.
The Thinkpad remains a viable option when you don't quite need a Toughbook, but need something that can handle being lugged to random places daily and used on top of all manner of surfaces. Someone like an insurance adjuster, who does all of their real work at remote locations, is a good example of the Thinkpad demographic.
They're rugged, but not absurdly ruggedized like a pickup truck. If you need it to survive being handled like a briefcase, get a Toughbook.
The clitmouse is better than a trackpad for most things, especially when there is also a lot of typing involved. There is a learning curve, but it's worth it, and Thinkpads really do have the best Trackpoints. They suck for a few specific cases, like trying to draw, but that's when you would switch to the trackpad or a cordless mouse.
I really liked the old keyboard layout, non-standard as it was, and I'm sorry to see it changed. To me, that was part of the Thinkpad identity.
Everything else about them had good and bad points along the way. There were fast ones and slow, ones with nice IPS panels and some crap panels too (presumably to get the bargain segment -- not sure it worked out), and resolution anywhere from rather nice for the time to bare minimum acceptable.
If anyone is trying to figure out the "essence of the Thinkpad", there's my take on it.
"Squicked" basically means the same thing as "revolted" or "disgusted", except with the undertone that this feeling is irrational. This is the most common meaning, but it is not the first.
The word "squick" first seems to have appeared in alt.tasteless, with a meaning of "cutting a hole in a skull and fucking the brain inside", because it was imagined that this activity would sound like the word. In my mind, it still means this first, and the more common definition second, so I get a considerable amount of amusement whenever I see it in print.
Nope, they got it right in a somewhat awkward way. They aren't counting those lights, but rather mapping the overall intensity at given locations. If it's not a countable quantity but rather one of magnitude, then "less" is correct. The use of "lights" rather than "light" may be throwing you off.
Before a single line of code hits the IDE, you plan out what you're trying to solve, the problems you have to deal with, and how the logic will have to act. Coding happens after the "hard" work has been done, once you have a good idea of what has to be done and how to do it.
This is how even I operate, and I'm a shit coder. Unless the problem is trivial (like parsing a text file and spitting it back out in a modified form), I first write out what I'm trying to accomplish, then detail that out into an outline, which then gets detailed further in either plain English or in pseudocode or some combination of the two. Sometimes I discover my initial outline just won't work because of some major implementation detail I overlooked, and in that case I'll move the "painted into a corner" code to a separate file (in case it proves useful later) but remove it from the program. Then I'll update the outline and associated details to keep them in sync with what I think I want to write.
As I go, that outline becomes the code comments. Then anyone else who has to touch the code gets the benefit of my forethought as well.
BitDefender used to do that shit to me ALL THE TIME, but when the final straw was when it decided my development environment was malicious because it contained the gcc++ compiler, and utterly broke it. At least Windows Defender doesn't pop up over something that common.
Shit, I used to work in the same building as Velocity Networks. The only connection I had to them was to use the connection they supplied to the entire building, and the one time I had to de-pwn someone else's network and found that the pwners were likely Velocity employees based on the very much in-house IP addresses of the attackers. (Either that or Velocity itself was pwned, which I don't rule out.)
Does that mean I'm somehow "connected" to Velocity Networks, one of the more notorious (at the time) spammer-friendly ISPs? Of course not. The closest I got to them was befriending one of their techs (whose license plate read H4XOR3D).
Slashdot Mirror
A remote control vibrating butt plug, why, in all honesty just why?
Two words.
Camwhores.
Tips.
It's an extremely popular way to generate "activity", on both sides of the transaction.
Whoosh. It's the next line in the song APK was quoting.
I've looked at clouds from both sides now
From up and down, and still somehow
It's cloud's illusions I recall
I really don't know clouds at all
It's "doing nothing" the same way the Secret Service is "doing nothing" when the President is out in public. It's busy making sure something underhanded isn't happening.
You really don't know clouds at all.
You can literally have Hatsune Miku under your foot -- provided you can play an instrument. Maybe it's not a lost cause after all.
MIKU STOMP Stomp Effect
You can also get your liver #rekt by taking acetaminophen for your hangovers. Doing so multiplies the damage. Reminding people to take aspirin instead would do much the same thing -- except for the people who can't take normal NSAIDs (like my mother).
Why do so many people (other than the 1% expecting their tax cuts) continually vote against their own best interests? This is what happens when "punishing" some group is more important to the masses than prosperity. If a rising tide lifts all boats, a falling tide eventually beaches them all, but the aforementioned people don't care so long as "teh gays" hit the shoals before they do.
Other than spammers, nobody bothered us when we used alt.binaries.pictures.grotesque for this purpose.
For the record, I was in no way responsible for the "Di Death Pic" hoax... but I know who was, an a.b.p.g regular. It was an accidental hoax anyhow, it was not meant to be taken seriously. We didn't know lurkers would forward it without the disclaimer.
The provider is always and never cheating, simultaneously. They write the rules, and can OP and nerf items at their discretion. It's not cheating because it's their game of Calvinball. It's cheating because it violates the expectation of players that they are whomping on other actual players when they go to PvP land, and because it's inherently unfair to players. But remember, if you aren't paying, you're not the customer. In this case, you're just the background filler for the people who do put up money to roll over.
What exactly were they supposed to do? Disclosing this publicly wouldn't have gotten the 0-days closed any faster but would have started malicious actors scrambling to get their hands on that database. Some already had it -- publicly admit it exists and has been exfiltrated, and anyone with even a passing interest is going to want it.
Now if it had been a database of someone else's 0-days, then they could be expected to at least tell the vendors of the products in question. But when they are the vendor? It's an internal problem.
Relevant song. https://www.youtube.com/watch?v=Ml6FNJAiH8I
As I understand it, the Ferengi are a piss-take of Jewish stereotypes, developed by Jewish writers which were at the time about half the team. Failure to grasp satire is not the same as actual racism.
As for other races, I think the stereotyping exists because they just don't want to make the viewers work too hard. You may like grit and shadow and depth like DS9 (I do), but a whole lot of people just don't want to work that hard, or have moral quandaries put in front of them that can't be resolved in 43 minutes. Stereotyping whole races is similar to consolidating characters when books are turned into films. It's non-optimal, but it's also unavoidable.
dingoes to each your children.
Is that anything like keeping dire wolf pups? That has worked out so well for the Starks so far.
You mean advice from people who spend more time hanging out on Stack Exchange and less time actually writing production code is turning out to be less correct than advice from people who talk less and do more? Color me surprised. (Not.)
I see three classes of links in articles.
1. Trivial ones. These lead to definitions of words and things like that. I prefer this over spending a paragraph defining terms the author may be afraid people will be unfamiliar with. If you don't need them, skip them. Even if one of these appears useless to you, it's not. It just saved you a few seconds of skimming explanatory text.
2. Fact verification. Sometimes these are pure CYA, so that if something dicey proves to be false, the author can say "it wasn't me that made it up, I was just going with my sources". Other times they are a defense against the troll hordes and autists looking to challenge the basic validity of an article based on "fake news" which really isn't. Unfortunately the only way to tell the difference is to look.
3. The author (or company's) back catalog. This can be perfectly legitimate – why should someone have to paraphrase themselves when expanding on a prior article if you can just read it? But other times it's little more than a scheme to drive more click-throughs. Unless it has a particularly clickbaity title, the only option here is also to look and see.
The solution I implement is to take or leave Type 1, and to launch Type 2 and Type 3 in the background and read them after the current article if indeed I read them at all. Sometimes it is sufficient merely to know where the link goes, to know what agenda is likely to be pushed. This still can result in a Wiki-Walk style vortex, but at least it only pulls me off topic after I've read the initial article.
Next time try putting a mouse in the container and blame it on the brewery.
Mattel doesn't actually build its own electronics, they farm everything out. This isn't unusual, but back when they had a separate Mattel Electronics division, they often rebadged products they hadn't even had a hand in creating. The Aquarius would be an example. If that was the case this time around, then they may have merely decided to cancel the contract, and you'll still see the product as soon as the manufacturer can get someone else to market it.
The Thinkpad remains a viable option when you don't quite need a Toughbook, but need something that can handle being lugged to random places daily and used on top of all manner of surfaces. Someone like an insurance adjuster, who does all of their real work at remote locations, is a good example of the Thinkpad demographic.
They're rugged, but not absurdly ruggedized like a pickup truck. If you need it to survive being handled like a briefcase, get a Toughbook.
The clitmouse is better than a trackpad for most things, especially when there is also a lot of typing involved. There is a learning curve, but it's worth it, and Thinkpads really do have the best Trackpoints. They suck for a few specific cases, like trying to draw, but that's when you would switch to the trackpad or a cordless mouse.
I really liked the old keyboard layout, non-standard as it was, and I'm sorry to see it changed. To me, that was part of the Thinkpad identity.
Everything else about them had good and bad points along the way. There were fast ones and slow, ones with nice IPS panels and some crap panels too (presumably to get the bargain segment -- not sure it worked out), and resolution anywhere from rather nice for the time to bare minimum acceptable.
If anyone is trying to figure out the "essence of the Thinkpad", there's my take on it.
Again by alt.tasteless standards, skullfucking uses the eye socket, not a hole drilled for the purpose.
"Squicked" basically means the same thing as "revolted" or "disgusted", except with the undertone that this feeling is irrational. This is the most common meaning, but it is not the first.
The word "squick" first seems to have appeared in alt.tasteless, with a meaning of "cutting a hole in a skull and fucking the brain inside", because it was imagined that this activity would sound like the word. In my mind, it still means this first, and the more common definition second, so I get a considerable amount of amusement whenever I see it in print.
Nope, they got it right in a somewhat awkward way. They aren't counting those lights, but rather mapping the overall intensity at given locations. If it's not a countable quantity but rather one of magnitude, then "less" is correct. The use of "lights" rather than "light" may be throwing you off.
Before a single line of code hits the IDE, you plan out what you're trying to solve, the problems you have to deal with, and how the logic will have to act. Coding happens after the "hard" work has been done, once you have a good idea of what has to be done and how to do it.
This is how even I operate, and I'm a shit coder. Unless the problem is trivial (like parsing a text file and spitting it back out in a modified form), I first write out what I'm trying to accomplish, then detail that out into an outline, which then gets detailed further in either plain English or in pseudocode or some combination of the two. Sometimes I discover my initial outline just won't work because of some major implementation detail I overlooked, and in that case I'll move the "painted into a corner" code to a separate file (in case it proves useful later) but remove it from the program. Then I'll update the outline and associated details to keep them in sync with what I think I want to write.
As I go, that outline becomes the code comments. Then anyone else who has to touch the code gets the benefit of my forethought as well.
BitDefender used to do that shit to me ALL THE TIME, but when the final straw was when it decided my development environment was malicious because it contained the gcc++ compiler, and utterly broke it. At least Windows Defender doesn't pop up over something that common.
Shit, I used to work in the same building as Velocity Networks. The only connection I had to them was to use the connection they supplied to the entire building, and the one time I had to de-pwn someone else's network and found that the pwners were likely Velocity employees based on the very much in-house IP addresses of the attackers. (Either that or Velocity itself was pwned, which I don't rule out.)
Does that mean I'm somehow "connected" to Velocity Networks, one of the more notorious (at the time) spammer-friendly ISPs? Of course not. The closest I got to them was befriending one of their techs (whose license plate read H4XOR3D).
Well they're either That Far Up (geostationary), or they're moving. I'd actually prefer That Far Up, at least I'd always know where to aim.