| // https://stackoverflow.com/questions/30757193/find-out-if-character-in-string-is-emoji | |
| import Foundation | |
| extension UnicodeScalar { | |
| var isEmoji: Bool { | |
| switch value { | |
| case 0x1F600...0x1F64F, // Emoticons | |
| 0x1F300...0x1F5FF, // Misc Symbols and Pictographs | |
| 0x1F680...0x1F6FF, // Transport and Map | |
| 0x1F1E6...0x1F1FF, // Regional country flags |
🚨 2020 Update: I recommend using mkcert to generate local certificates. You can do everything below by just running the commands brew install mkcert and mkcert -install. Keep it simple!
This gives you that beautiful green lock in Chrome. I'm assuming you're putting your SSL documents in /etc/ssl, but you can put them anywhere and replace the references in the following commands. Tested successfully on Mac OS Sierra and High Sierra.
sudo nano /etc/ssl/localhost/localhost.conf
| on run | |
| set imessage_id to "" -- leave blank to skip sending periodic iMessage progress updates, put your iMessage ID here to get updates as the script runs | |
| set delay_seconds to 5 -- Don't set to 0, it runs too fast. 0.75 is a good setting for "go fast". | |
| set computer_name to do shell script "scutil --get ComputerName" | |
| set os_version to do shell script "sw_vers -productVersion" | |
| set os_build to do shell script "sw_vers -buildVersion" | |
| set _uptime to do shell script "uptime" | |
| set url_list to {"http://techmeme.com", "http://www.consumerreports.org/laptops/macbook-pros-fail-to-earn-consumer-reports-recommendation/", "https://twitter.com/panzer/status/812367550734401536", "http://www.politico.com/story/2016/12/foreign-travelers-social-media-232930", "http://www.macworld.com/article/3153384/gaming/nintendo-plans-to-release-2-or-3-mobile-games-a-year-after-super-mario-runs-success.html", "http://www.wsj.com/articles/cyber-experts-cite-link-between-dnc-hacks-and-aggression-against-uk |
| on run | |
| set imessage_id to "" -- leave blank to skip sending periodic iMessage progress updates, put your iMessage ID here to get updates as the script runs | |
| set delay_seconds to 5 -- Don't set to 0, it runs too fast. 0.75 is a good setting for "go fast". | |
| set computer_name to do shell script "scutil --get ComputerName" | |
| set os_version to do shell script "sw_vers -productVersion" | |
| set os_build to do shell script "sw_vers -buildVersion" | |
| set _uptime to do shell script "uptime" | |
| set url_list to {"http://techmeme.com", "http://www.consumerreports.org/laptops/macbook-pros-fail-to-earn-consumer-reports-recommendation/", "https://twitter.com/panzer/status/812367550734401536", "http://www.politico.com/story/2016/12/foreign-travelers-social-media-232930", "http://www.macworld.com/article/3153384/gaming/nintendo-plans-to-release-2-or-3-mobile-games-a-year-after-super-mario-runs-success.html", "http://www.wsj.com/articles/cyber-experts-cite-link-between-dnc-hacks-and-aggression-against-uk |
In experience to get a proper working multiple wan configuration using mwan3 starting from scratch you should:
Important: this works well on OpenWRT 15.05.1, on newer versions there was some breaking changes, for example, the wan ifaces have ipv6 capability and now are named with letters ("wan, wanb... , wanc" instead of "wan, wan2... wan3" so wanb6 means 2nd wan ipv6.): https://github.com/openwrt/packages/blob/master/net/mwan3/files/etc/config/mwan3
The official documentation seems to be very detailed and up to date, I recommend reading those first: https://openwrt.org/docs/guide-user/network/wan/multiwan/mwan3 but I recommend to give a look at my config file below, since my approach for policyes is very nice.
First of all: Activate conntrack, docs says that is important and neccesary to get MWAN3 work properly, and it is needed to reboot:
| { | |
| "AWSEBDockerrunVersion": "1", | |
| "Image": { | |
| "Name": "<AWS_ACCOUNT_ID>.dkr.ecr.us-east-1.amazonaws.com/<NAME>:<TAG>", | |
| "Update": "true" | |
| }, | |
| "Ports": [ | |
| { | |
| "ContainerPort": "443" | |
| } |
| #!/bin/sh | |
| # Use AWS CLI to get the most recent version of an AMI that | |
| # matches certain criteria. Has obvious uses. Made possible via | |
| # --query, --output text, and the fact that RFC3339 datetime | |
| # fields are easily sortable. | |
| export AWS_DEFAULT_REGION=us-east-1 | |
| aws ec2 describe-images \ |
| // The name of the Gmail Label that is to be autopurged? | |
| var LABELS = ["alerts-disk-space", "alerts-sensu", "backups", "cron", "janitor-monkey", "nagios", "push", "security-alerts", "svn-git-updates"]; | |
| // Purge messages automatically after how many days? | |
| var PURGE_AFTER = "31"; | |
| // This is the largest batch size moveThreadsToTrash supports | |
| var BATCH_SIZE = 100 | |
| var DELAY_BETWEEN_MS = 1000 |
| # This task will notify Sentry via their API[1] that you have deployed | |
| # a new release. It uses the release timestamp as the `version` | |
| # (like 20151113182847) and the git ref as the optional `ref` value. | |
| # | |
| # This task requires several environment variables be set (or just | |
| # hardcode the values in here if you like living on the edge): | |
| # | |
| # ENV['SENTRY_API_ENDPOINT'] : API endpoint, https://app.getsentry.com | |
| # ENV['SENTRY_ORG'] : the organization for this app | |
| # ENV['SENTRY_PROJECT'] : the project for this app |
