| // You don't want to serve HTTPS supporting for SSL3.0 any longer, see: | |
| // http://googleonlinesecurity.blogspot.de/2014/10/this-poodle-bites-exploiting-ssl-30.html | |
| import ( | |
| "crypto/tls" | |
| "net/http" | |
| ) | |
| // This code supports SSL3.0, TLS1.0, TLS1.1 and TLS1.2 | |
| // Chances are you currently do this but want to stop due to the POODLE | |
| err := http.ListenAndServeTLS(addr, "crtfile", "keyfile", handler) |
| package errch | |
| import ( | |
| "sync" | |
| ) | |
| func New() (<-chan error, func() chan<- error) { | |
| var ( | |
| src = make(chan error) | |
| wg sync.WaitGroup |
git-prebase improves on 'git rebase -i' by adding information per commit regarding which files it touched.
Add the executable to your path and git will automatically expose it as
Search engines, spam filtration, and p2p protocols - all need to rate the value of information. Search engines need it to provide good results; spam filtration needs it to exclude noise; and p2p networks need it for security and efficiency.
What is "value?" I'll use two dimensions:
It's hard to quarrel with that ancient justification of the free press: "America's right to know." It seems almost cruel to ask, ingeniously, "America's right to know what, please? Science? Mathematics? Economics? Foreign languages?"
None of those things, of course. In fact, one might well suppose that the popular feeling is that Americans are a lot better off without any of that tripe.
There is a cult of ignorance in the United States, and there always has been. The strain of anti-intellectualism has been a constant thread winding its way throughout political and cultural life, nurtured by the false notion that democracy means that "my ignorance is just as good as your knowledge."
Politicians have routinely striven to speak the language of Shakespeare and Milton as ungrammaticaly as possible in order to avoid offending their audiences by appearing to have gone to school. Thus, Adlai Stevenson, who incautiously allowed intelligence and learning and wit to peep out of his speeches, found the American people
| // Most components are defined fully by their render function, | |
| // and all they need to access is the props | |
| var myComponent = createComponent(function (props) { | |
| return React.DOM.h1({}, "Hello " + props.name); | |
| }); | |
| // ...which can be done very succinctly with ES6: | |
| const {h1, div} = React.DOM; | |
| const myComponent = createComponent(({name}) => h1({}, `Hello ${name}`)); |
| ## | |
| ## Put me in ~/.irssi/scripts, and then execute the following in irssi: | |
| ## | |
| ## /load perl | |
| ## /script load notify | |
| ## | |
| use strict; | |
| use Irssi; | |
| use vars qw($VERSION %IRSSI); |
| # Edit this configuration file to define what should be installed on | |
| # your system. Help is available in the configuration.nix(5) man page | |
| # and in the NixOS manual (accessible by running ‘nixos-help’). | |
| { config, pkgs, ... }: | |
| let | |
| # Get the last working revision with nvidia 460.x | |
| nixos-unstable-pinned = import (builtins.fetchTarball { | |
| name = "nixos-unstable_nvidia-x11-470.57.02"; |
Hi there!
The docker cheat sheet has moved to a Github project under https://github.com/wsargent/docker-cheat-sheet.
Please click on the link above to go to the cheat sheet.
this is a rough draft and may be updated with more examples
GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?
Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to
