1,834 karma · joined August 13, 2012
There's also the following copy on the same page:
"Repeated, crippling DDoS attacks from the following countries has caused me to block their access. Apologies to the innocent.
Brazil, Singapore, Angola, Seychelles, UAE."
My guess is that the geolocation Gods placed GP in Singapore.
This is certainly something many people I know have cared a lot about - and again, I'm not a football enthusiast myself, but still the vast majority of the people I know are, because, not being one really is an outlier.
[0] https://www.topendsports.com/world/lists/popular-sport/fans....
> There are plenty of stoppages in game already which take as much time.
Well. Not really. And those "stoppages" are part of the game. Actually watching the players quarrel with the referee and whatnot is something football fans want to do. It's not comparable.
I'd say this is very, very common knowledge in huge parts of the world. It's not something only enthusiasts and purists know.
> Who is this good for? Is it good for you?
Well, as a global population reduction is sorely needed, this is good for pretty much everybody. There's absolutely no way we can keep extracting resources and polluting at the rate demanded by our current enormous population (which has more than doubled in my life time).
Unfortunately, your theory isn't working, as the population still grows.
Why was it tax-exempt? Why should it be?
What sets it apart from any other service where you pay someone to do something for you - such as cook you a meal, transport you somewhere or build you a house?
But of course, it's only "propaganda" when you don't like it.
So the options are:
1) Use Polish, with the risk of being rude if you happen to speak to the Spanish priest
2) Use Latin and ask "do you speak Polish?", and both the Polish and the Spanish priest will understand.
You could of course argue that it's not so very rude to accidentally try to strike up a conversation with someone in a language they don't know, but apparently Tade0's father thinks it is.
How does that matter? The point isn't that the reader should know that "oh, this is a reserved address". The point is that there should be no room for the address that's actually being used by someone to end up being used incorrectly just because it showed up in some random documentation.
Much like how you probably wouldn't be thrilled if your phone number was used as an example in some random documentation somewhere.
Not sure how long you're a startup...
Of course, if your problem is "/usr won't mount", then it's likely that the ftp server isn't running either, so the advice still makes sense.
But giving birthdate (available to anyone via a single query in a public database) and (sometimes?! - what?!) PIN over the phone wouldn't really be considered good enough here. Birthdate is, as I said, public knowledge. And a phone is too insecure a medium for transmitting a password.
I'm not super interested in an long argument about whether it's reasonable that this isn't considered secure or not. I'm just letting you know what reality looks like. And the reality is that "just call them" is not a solution, because such information will simply not be handed out over the phone.
Are you comfortable with anybody being able to ring up the hospital and say "yo, it's majorchord, how are my gonnorhea results?"
At least when i encountered the discussion initially (some thirty years ago) I'd say we usually talked about how many requests the system was capable of handling. Then requests per second was the obvious unit since a request usually took less than a second to process (obviously depending on the system and so on - but mostly), so using that unit often gave a fairly low, comprehensible number.
Was it ten? A hundred (very impressive)? Perhaps even a thousand (very, very impressive!)?
Multiply those numbers by 60, and there's suddenly a lot more mental gymnastics involved. By 3600 and you're well into "all big numbers look the same" land.
Not sure I agree. I've been gaming on Debian since 2005, and while it certainly was some work in the beginning, it's been pretty painless for the last five years or so. I'm on Debian stable (mostly) at the moment, and don't really know what "bleeding edge" packages I would be missing.
Of course there were people raising concerns, though. I figured that was pretty obvious in my original post. If there hadn't been any people raising concerns, nobody would have had to dismiss them - condescendingly or not.
So yes, I (incorrectly) used the word "everyone" to mean "a lot of people" in a sentence where I figured it was quite obvious that that's what I was doing, and in a way I've seen it used before in English so many times that I thought it was a common and accepted pattern. Perhaps I am wrong about the last bit though. ESL speaker, so that's quite possible.
-- ca. everyone here, during the GitHub acquisition
Emacs does foo~ by default, not ~foo.
In either case, you're not really supposed to edit files in sites-enabled. That directory is expected to contain symlinks to files in sites-available. I'm not going to say with any certainty that one of the reasons for this indeed is that the pattern (which was used by apache as well - and perhaps other things before it) protects against accidentally reading backup files, but it's not impossible.
So there's definitely a case of holding it wrong if you end up with backup files in that directory.
"Move the pypy trunk into its own top level directory so the path names stay constant."
PyPy migrated from Subversion to git at some point. Not sure how much of the history survived the migration.
Somehow I can imagine that a world where a the brightest minds of a generation didn't spend their prime optimizing ad clicking wouldn't necessarily be a complete disaster.
Presumably this. Coffee terminology is (apparently) not global. I've never seen the term "long black", and I visit cafés quite a lot. Wikipedia lists it as a thing primarily in Australia/New Zealand.