throwaway125
This isn't entirely true. All the quest text, monster says, NPC interactions and more are sent by the server. Sure, the models and sounds are part of the client, but the server tells your client where to place which mobs, how much health they should have, how they react to you, etc.
>The content that is available on Nostralius is literally not available on any live server any more
Yeah, hosting a game server that is no longer available because the company that used to host them stopped offering that option should probably not be against the law. Even single player games are being created as "multiplayer" nowadays, so it's bound to become an even bigger problem in the future.
For your particular example if you search for 'usb type c "resistor"' you get (what I assume to be) reasonable results: https://duckduckgo.com/?q=usb+type+c+"resistor"
Ideally duckduckgo should recognize which of the search terms are defining, but until that happens quoting should help you out.
>am I required to make my application code public?
The exact details depend on multiple factors (are you linking to libraries? Are they considered system libraries?) and if you are actually thinking of doing this you should invest some time in investigating this, and probably in consulting a lawyer.
Note that this is all based on my layman's understanding of the law and the license, and I'm definitely not a lawyer.
Browsers should probably not allow that kind of interaction between javascript and the password field.
At some point privacy is no longer a choice, not a real choice anyway. You get to chose between participating in society or keeping your privacy. It shouldn't have to be this way, but it is.
Either way, the first few videos I've watched so far are great, thanks.
I do think people recognize the fact that these two are different things (e.g. when comparing C to a language with a richer standard library it's one of the points that are often specifically and separately mentioned.), but it's just not very useful to separate them explicitely in a comparison of languages from a user's point of view (as opposed to a language designer's point of view).
The problem with disabling all these features on a case by case basis is that you contribute to a richer fingerprint this way. Browsers will become increasingly more vulnerable to fingerprinting and there doesn't seem to be a way to stop it without going back to the dark ages of the web.
The language often (always?) has facilities to remove those warnings on a case by case basis. For example when you don't want to use a parameter you can actively let the compiler know without assigning the variable to itself: you can only include the type and not the name:
int fn(int, void*);
int fn(int num, void* /*extra*/) {
// If the name extra is commented out the compiler will
// not warn that you are not using it. Now it is very
// clear that not using this variable was an active choice
// and not a mistake.
return num;
}
edit: as pbsd pointed out commenting out extra is not portable C code, though I believe the wider point still stands. These warnings can be very useful and should be be reviewed before ignoring them.Breaking out of virtual machines is a really interesting process but it's important to remember that a hypervisor can be attacked with pretty much the same techniques you can attack any other program. Virtual machines aren't a magic contain-all-the-hackers solution. There was an interesting talk on DEFCON 19 about breaking out of KVM: http://www.youtube.com/watch?v=tVSVdudfF8Q
2048^4 = 17592186044416
2^44 = 17592186044416 add_header Strict-Transport-Security max-age=31536000;
add_header X-Frame-Options DENY;
The first one tells browsers it should never try to visit the http version of this site, even if the user clicks on a http link the browser will visit the https version. This helps prevent ssl stripping attacks.The second prevents browsers from including this site in an iframe or frame, which helps prevent clickjacking attacks. If your site depends on those you can also set the option to SAMEORIGIN.
https://developer.mozilla.org/en-US/docs/HTTP/X-Frame-Option... https://developer.mozilla.org/en-US/docs/Security/HTTP_Stric... https://en.wikipedia.org/wiki/SSL_stripping#SSL_stripping