Well we could easily solve that problem by mandating big whirly spinning blades at all coal, solar, nuclear, and other facilities! Seriously, if we have moved from "won't someone think of the children" to "won't someone think of the birds" we have clearly run out of reasonable counter-arguments to the approach.
What the hell are you talking about? The photographs clearly show Franken not touching the reporter. Trying to claim it is a photo of molestation is phenomenally stupid given that we have all seen it.
In the 1980s a single person could be solely responsible for the development of a great product. Those times are well behind us. The best developers are orders of magnitude better than the worst, and are few and far between. But the number of software projects that can be successful as sole console cowboy efforts is minimal in 2017. There is nothing in the claim made in the OPs post that has any kernel of truth in it.
I wasn't wrong dumbfuck. You tried to claim that being modded up was some kind of proof your post was insightful even though you should know that there is often no such correlation. I tried to give you a pass for being too stupid to understand that and let it drop, but you just couldn't rest until you proved you were an idiot one more time.
I'm not sure what job you had where you can underestimate time like you have, but the fact that you thought there was a possibility that the management objecting was a problem makes it clear that it was a very low level position. When you grow up and get a job with responsibility, if you ever do, it will be because you exhibit the kind of good judgement and focus to know how to best use your time.
Your first sentence makes it clear that everything you have to say is nonsense spouted by a clueless noob. Stick around kid. You have not just lots, but everything, to learn.
It's all fun and games until someone gets hurt. If someone had done this and just showed it off on their blog it would be a "fun project", but as it stands it has affected us all, so we have every right to criticize it if we don't like the impact it is having.
Or another option the clearly unemployed OP didn't consider is that maybe the guy has a job where he gets paid to be productive, not to walk across the street and stand in line with a bunch of people who have nothing better to do than stand in line while not figuring out that some people have jobs, and that job isn't pizza delivery.
You have been around here long enough to know that ridiculous drivel gets nodded up and informative and insightful posts get nodded down regularly. I am not commenting one way or another on the quality of your post, but merely saying that you should know better than to try to claim that upmods are proof of quality.
OK buddy. You clearly said. com for domains you own, even though you didn't say "for domains you own", and in that case it isn't limited to.com but you were specific about.com. You are a master communicator and there is no way anyone could have interpreted your statement any other way than how you meant it even though that's not how you said it. Good for you. Enjoy living in your own little world!
No, I'm saying you still don't grasp what is going on. Google owns *.dev and *.google.com. Using any of those for your internal network named is wrong. For domains you own, so a VERY limited subset of.com, you can do that, but for 99.99999% of the cases using.com is wrong. I think you get that and we just got our signals crossed.
You are big on making up your own rules aren't you. Read it backwards instead of forwards, ignore the standards and do it my way. Which reminds me that you absolutely do support "doitmyway", you just want the rest of the world to do it the way you want to rather than the way it is supposed to be done. Google owns the.dev TLD, just as they own *.google.com. If they want to force HTTPS on their domains they have every right to do so. You seem to have serious trouble grasping this simple concept.
Are you on drugs? The.dev TLD is not available. They won't issue you a cert for it. If they have done so in the past they will revoke it. You CAN'T use.dev as an internal TLD legitimately. This is well known, was announced a long time ago, and it is the fault of any organization if they do so now. This shit isn't complicated. It is no different than if you try to tie a.com address to a local address. If you do it your shit is broken and you can fix it or leave it broken and cry like a little girl that things work the way they are supposed to today instead of the way they used to before the change.
I don't give a shit if you pride yourself on your ignorance. Have a ball. Run your own DNS server and add an entry for *.com to 127.0.0.1 for all I care.
Slashdot Mirror
" ... And if he can't do it, nobody can!" What are you, a fucking high school cheerleader?
It would not be legal to convince a child to get into porn. I'm not sure how you ever got the idea it might be.
That's not true. A lot of cats have their food and housing provided by the welfare state and don't need to work anymore.
Well we could easily solve that problem by mandating big whirly spinning blades at all coal, solar, nuclear, and other facilities! Seriously, if we have moved from "won't someone think of the children" to "won't someone think of the birds" we have clearly run out of reasonable counter-arguments to the approach.
What the hell are you talking about? The photographs clearly show Franken not touching the reporter. Trying to claim it is a photo of molestation is phenomenally stupid given that we have all seen it.
In the 1980s a single person could be solely responsible for the development of a great product. Those times are well behind us. The best developers are orders of magnitude better than the worst, and are few and far between. But the number of software projects that can be successful as sole console cowboy efforts is minimal in 2017. There is nothing in the claim made in the OPs post that has any kernel of truth in it.
enough said ... Have a nice day.
I wasn't wrong dumbfuck. You tried to claim that being modded up was some kind of proof your post was insightful even though you should know that there is often no such correlation. I tried to give you a pass for being too stupid to understand that and let it drop, but you just couldn't rest until you proved you were an idiot one more time.
I'm not sure what job you had where you can underestimate time like you have, but the fact that you thought there was a possibility that the management objecting was a problem makes it clear that it was a very low level position. When you grow up and get a job with responsibility, if you ever do, it will be because you exhibit the kind of good judgement and focus to know how to best use your time.
No, but it's really not that important.
Your first sentence makes it clear that everything you have to say is nonsense spouted by a clueless noob. Stick around kid. You have not just lots, but everything, to learn.
It's all fun and games until someone gets hurt. If someone had done this and just showed it off on their blog it would be a "fun project", but as it stands it has affected us all, so we have every right to criticize it if we don't like the impact it is having.
Or another option the clearly unemployed OP didn't consider is that maybe the guy has a job where he gets paid to be productive, not to walk across the street and stand in line with a bunch of people who have nothing better to do than stand in line while not figuring out that some people have jobs, and that job isn't pizza delivery.
You have been around here long enough to know that ridiculous drivel gets nodded up and informative and insightful posts get nodded down regularly. I am not commenting one way or another on the quality of your post, but merely saying that you should know better than to try to claim that upmods are proof of quality.
If you create a server called anything ending in a domain owned by someone else you are a moron. Check mate. Off you go now ...
OK buddy. You clearly said. com for domains you own, even though you didn't say "for domains you own", and in that case it isn't limited to .com but you were specific about .com. You are a master communicator and there is no way anyone could have interpreted your statement any other way than how you meant it even though that's not how you said it. Good for you. Enjoy living in your own little world!
No, I'm saying you still don't grasp what is going on. Google owns *.dev and *.google.com. Using any of those for your internal network named is wrong. For domains you own, so a VERY limited subset of .com, you can do that, but for 99.99999% of the cases using .com is wrong. I think you get that and we just got our signals crossed.
.dev isn't your private network name anymore than google.com is, and that's the part you need to understand if you ever want to get a clue someday.
You are big on making up your own rules aren't you. Read it backwards instead of forwards, ignore the standards and do it my way. Which reminds me that you absolutely do support "doitmyway", you just want the rest of the world to do it the way you want to rather than the way it is supposed to be done. Google owns the .dev TLD, just as they own *.google.com. If they want to force HTTPS on their domains they have every right to do so. You seem to have serious trouble grasping this simple concept.
You just confirmed that .dev isn't available and so you can't use it. That was the topic, and that was the point. Have a nice day.
Yes, because it is my responsibility to teach you what I, ICANN, Google, and every competent person already knows. Plonk.
I don't doubt you don't see any. That would require a basic technical competence you clearly lack.
Are you on drugs? The .dev TLD is not available. They won't issue you a cert for it. If they have done so in the past they will revoke it. You CAN'T use .dev as an internal TLD legitimately. This is well known, was announced a long time ago, and it is the fault of any organization if they do so now. This shit isn't complicated. It is no different than if you try to tie a .com address to a local address. If you do it your shit is broken and you can fix it or leave it broken and cry like a little girl that things work the way they are supposed to today instead of the way they used to before the change.
I don't give a shit if you pride yourself on your ignorance. Have a ball. Run your own DNS server and add an entry for *.com to 127.0.0.1 for all I care.
No it wouldn't because your corporate CA would be installed as a trusted CA.