by xero updated 10.29.24
| // Go to: https://<team>.slack.com/customize/emoji | |
| // Open Developer Console | |
| // Copy/Paste and Run this in the console: | |
| var spans = document.getElementsByTagName('span'); | |
| var basharray = "( " | |
| for (var i=0;i<spans.length;i++) { | |
| var link = spans[i].getAttribute("data-original"); | |
| if(link != null){ | |
| basharray = basharray.concat(link, " ") |
| #!/usr/bin/env xcrun swift -O | |
| /* | |
| gen.swift is a direct port of cfdrake's helloevolve.py from Python 2.7 to Swift 3 | |
| -------------------- https://gist.github.com/cfdrake/973505 --------------------- | |
| gen.swift implements a genetic algorithm that starts with a base | |
| population of randomly generated strings, iterates over a certain number of | |
| generations while implementing 'natural selection', and prints out the most fit | |
| string. | |
| The parameters of the simulation can be changed by modifying one of the many |
| # List of English and Spanish Obscenities for Moderation | |
| 'anus', | |
| 'apestoso', | |
| 'arrogante', | |
| 'arrombado', | |
| 'arse', | |
| 'arsehole', | |
| 'ass', | |
| 'ass-hat', |
| /* | |
| * Taken from http://stackoverflow.com/questions/5867534/how-to-save-canvas-data-to-file/5971674#5971674 | |
| */ | |
| var fs = require('fs'); | |
| // string generated by canvas.toDataURL() | |
| var img = "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAUCAYAAACNiR0" | |
| + "NAAAAKElEQVQ4jWNgYGD4Twzu6FhFFGYYNXDUwGFpIAk2E4dHDRw1cDgaCAASFOffhEIO" | |
| + "3gAAAABJRU5ErkJggg=="; | |
| // strip off the data: url prefix to get just the base64-encoded bytes |
| scp -r prod:/path/foo /home/user/Desktop #where 'prod' is the name of the ssh bookmark | |
| scp -r [email protected]:/path/to/foo /home/user/Desktop/ |
| # The blog post that started it all: https://neocities.org/blog/the-fcc-is-now-rate-limited | |
| # | |
| # Current known FCC address ranges: | |
| # https://news.ycombinator.com/item?id=7716915 | |
| # | |
| # Confirm/locate FCC IP ranges with this: http://whois.arin.net/rest/net/NET-165-135-0-0-1/pft | |
| # | |
| # In your nginx.conf: | |
| location / { |
| module.exports = function(grunt) { | |
| // Configuration | |
| grunt.initConfig({ | |
| pkg: grunt.file.readJSON('package.json'), | |
| concat: { | |
| dist: { | |
| src: [ | |
| 'source/js/libs/*.js', // All JS in the libs folder |
- Install Hubot locally
- Install Slack Adapter
- Configure integration on Slack
- Go to
[your-slack].slack.com/services/new/hubot
- Go to
- Deploy to Heroku
If you want to rename the automatically generated heroku domain name:
Sass 3.3 is coming soon, and along with it several major new features. It supports source maps, SassScript maps, and the use of & in SassScript. In preparation for its release, we've put out a couple of release candidates to be sure that everything was set and ready to go. Unfortunately, it wasn't.
Release candidates often turn up small bugs and inconsistencies in new features, but it's rare that they find anything truly damning. In this case, though, several users noticed an issue with using & in SassScript that rendered a sizable chunk of our plan for that section of 3.3 unworkable. It's not a fatal issue, and we think we have a good plan for dealing with it (I'll get to that in a bit), but it is a problem.
To understand what's wrong, first you need to understand the reason we decided to make & accessible to SassScript in the first place. One thing users want to do pretty often is to add suffixes to classes. Sometimes this takes the place of nest