from https://api.github.com/emojis
- 👍 +1
- 👎 -1
- 💯 100
- 🔢 1234
- 🎱 8ball
🅰️ a- 🆎 ab
- 🔤 abc
package main | |
import ( | |
"bytes" | |
"io/ioutil" | |
"log" | |
"net" | |
"os" | |
"golang.org/x/crypto/ssh" |
#!/bin/bash | |
# ================================================================== | |
# | |
# server-status.sh | |
# | |
# Retrieves current status of the server and sends it to Slack. | |
# | |
# https://github.com/TrueFurby/f48cc2acb58370bd1109ec55c9820439 | |
# |
from https://api.github.com/emojis
# This file is intended as a starting point for a customized makefile for a Go project. | |
# | |
# Targets: | |
# all: Format, check, build, and test the code | |
# setup: Install build/test toolchain dependencies (e.g. gox) | |
# lint: Run linters against source code | |
# format: Format the source files | |
# build: Build the command(s) for target OS/arch combinations | |
# install: Install the command(s) | |
# clean: Clean the build/test artifacts |
This utilizes blns to cram strings through the 'widen' gem. | |
The first line is the original string, the second, the 'widened' string, the third, the 'narrowened' string | |
Test strings | |
Scunthorpe General Hospital | |
Scunthorpe General Hospital | |
Scunthorpe General Hospital | |
$100% true |
My friend Michael Jackson turned off github issues on one of his smaller projects. It got me thinking...
Maintainers getting burned out is a problem. Not just for the users of a project but the mental health of the maintainer. It's a big deal for both parties. Consumers want great tools, maintainers want to create them, but maintainers don't want to be L1 tech support, that's why they
As a freelancer, I build a lot of web sites. That's a lot of code changes to track. Thankfully, a Git-enabled workflow with proper branching makes short work of project tracking. I can easily see development features in branches as well as a snapshot of the sites' production code. A nice addition to that workflow is that ability to use Git to push updates to any of the various sites I work on while committing changes.
A running example of the code from:
This gist creates a working example from blog post, and a alternate example using simple worker pool.
TLDR: if you want simple and controlled concurrency use a worker pool.
package utils | |
import ( | |
"net/http" | |
) | |
func BasicAuth(handler http.Handler, username, password string) http.HandlerFunc { | |
return func(w http.ResponseWriter, r *http.Request) { | |
if u, p, ok := r.BasicAuth(); !ok || !(u == username && p == password) { | |
w.Header().Set("WWW-Authenticate", "Basic realm=\"ZorkIrc\"") |