Many websites use tracking elements in the URL (e.g. https://example.com?utm_source=newsletter1&utm_medium=email&utm_campaign=sale) to mark your online activity. All that tracking code is not necessary for a website to be displayed or work correctly and can therefore be removed—that is exactly what ClearURLs does.
Stops URL based tracking and improves the readability of URLs. Perfect. 👌
There seems to be an increasing number of services that require a specific app for two-factor authentication. In the last week I needed to install both Authy and Symantec VIP Access.
I’d prefer, however, to keep all my Time-based One-Time Passwords (TOTP) in one place. Having secret keys scattered over multiple apps makes them hard to backup. Thankfully I found solutions for both:
SYMC in most cases (vipaccess provision -p --token-model SYMC).A clever dynamic solution to the unpivot problem from Thomas Kellerer:
WITH data_percentiles AS (
SELECT
month,
percentile_disc(0.50) within group (order by count) "50p",
percentile_disc(0.80) within group (order by count) "80p",
percentile_disc(0.99) within group (order by count) "99p"
FROM data
GROUP BY 1
)
SELECT
p.month,
d.series,
d.amount::numeric
FROM data_percentiles p
CROSS JOIN LATERAL jsonb_each_text(to_jsonb(p) - 'month') as d(series, amount)
ORDER BY 1, 2
Always open the right browser
Unlike the alternatives, Finicky can edit URLs and open them with anything. This is great for stripping trackers from URLs, and opening Figma link directly in the Figma app.
(Initial configuration: jamesramsay/dotfiles:finicky.js)
SoundSource is “sound control so good, it ought to be built in.” It is a menu bar app that makes it easy to switch input and output devices, adjust levels, and add effects like an equalizer.
Regular video calls and recordings mean I want to hear and be heard - SoundSource makes that easier for me. Two features I particularly appreciate:
This is the custom profile I created for my CalDigit dock because the audio output was too loud at even the lowest setting.
Preamp: -15.0 dB
Filter 1: On PK Fc 0 Hz Gain 0 dB Q 1
It would make my day if SoundSource would remember the last used Headphone EQ for each output device so that I don’t switch profile manually.
Control your external monitor brightness, contrast or volume directly from a menulet or with keyboard native keys.
Why isn’t MonitorControl a built-in feature of MacOS?
Update: No need to compile MinIO yourself anymore — MinIO is available on SynoCommunity.
I use Arq to backup my computer to Dropbox (off-site backup) and a Synology NAS (on-site backup). The most obvious approach is to use a folder stored on your NAS. I previously explained how using Autofs can make this easier, but I’ve still found it unreliable and slow.
Arq calculates checksums when performing a backup to verify uploads, and when validating backup data every 60 days. When using the folder approach, Arq needs to download the data to calculate a checksum. S3-compatible storage, however, can calculate the checksum, allowing this work to be offloaded to the NAS making backups and validation faster.
Arq supports S3-compatible storage including MinIO, which can be run on a Synology NAS using Docker. Unfortunately, only Synology devices with an x64 CPU can run Docker. My DS216play has an ARMv7 CPU, so I can’t use the Docker package.
Here’s how you can compile MinIO to run natively on an ARMv7 Synology NAS without Docker. 🎉
Before you begin, you need Git and Docker to be installed.
Clone the MinioSPK repository, which contains build scripts for creating a Synology MinIO package.
# Clone the project
git clone https://github.com/darkmuggle/MinioSPK.git
# Change directory
cd MinioSPK
Two commands are needed to compile MinIO.
# Download the MinIO source and logos
make init
# Build the MinIO package for Synology
make arm7
With our newly built package, we are ready to install MinIO.
From Synology DiskStation, the web interface for managing your Synology NAS, open Package Center.
Next, from the Installed section (top left), select Manual Install (top right) to launch the installation and upgrade wizard.
Click Browse to locate the package you compiled, likely similar to minio-2020.04.04-arm-7.spk. Then click Next.
After a short while you’ll be shown a warning because package hasn’t been signed. You will need to click Yes to proceed.
The wizard will prompt you to set the MINIO_ACCESS_KEY and MINIO_SECRET_KEY, and then install MinIO. Once installed you will be able to open MinIO from Package Center. Use the access key and secret key you set during the installation to login.
Now that you’ve installed MinIO, you can use the guide on the Arq blog Backup to Synology NAS using Minio and Arq.
(Summarized from my post for GitLab, One simple trick to make your screenshots 80% smaller)
When you capture a screenshot on your Mac, it will be saved in the PNG-32 format, with support for 16 million distinct colors and transparency. This means that the screenshot will perfectly capture every pixel on your screen, but having four 8-bit channels for red, green, blue and alpha (transparency) for every pixel makes the file very large. If you’re interested, you can verify this yourself using pngcheck.
In practice, the subjects of my screenshots are buttons and forms, not photographs. Since we don’t need 16 million colors, we can take advantage of the PNG-8 format with it’s more compact 256 color palette.
The first step is to reduce the color palette of the screenshot. This is a type of lossy compression called color quantization, which will reduce the number of distinct colors in the image. The pngquant command line utility is the perfect tool for this job, and if you’ve used the popular ImageAlpha tool, you’ve already used the pngquant library.
# Install pngquant using Homebrew
brew install pngquant
# Quantize 32-bit RGBA PNG to 8-bit (or smaller) RGBA-palette
# pngquant [number of colors] [options] input.png
# --skip-if-larger only save converted file if they're smaller than original
# --strip remove optional metadata
# --ext=.png set output filename to be same as input filename
# --force overwrite existing output files
pngquant 256 --skip-if-larger --strip --ext=.png --force example.png
I’ve observed for most screenshots you can comfortably reduce the color palette to as few as 64 colors before it becomes noticeable. If you frequently take screenshots of gradients or more complex images, you may want to stick with 256 colors to avoid noticeable artifacts.
The PNG file format uses DEFLATE compression internally for an added layer of lossless compression, but most PNG libraries do not implement aggressive lossless compression. This provides another opportunity to reduce the file size further.
In 2013, Google released zopfli, which claimed to improve compression by 3-8% compared to zlib. The trade off for this improvement: waiting an extra 1-2 seconds. (There is no decompression penalty when viewing the compressed image).
# Install zopfli using Homebrew, which includes zopflipng
brew install zopfli
# Optimize PNG compression
# zopflipng [options] input.png output.png
# -y do not ask about overwriting files
zopflipng -y example.png example.png
Relative to the massive savings from color quantization, improving lossless compression provides a much smaller reduction, but in the context of pages with many images these marginal gains do add up to worthwhile savings.
The trick is to make this happen automatically every time I capture a screenshot using Automator. This allows you to run commands based on file events, like every time a new screenshot is added to a directory.
I create a dedicated Screenshots directory, so that they don’t clutter your desktop.
# Create a Screenshots directory in the current users Home directory
mkdir -p "$HOME/Screenshots"
# Configure macOS to capture screenshots to this location
# If you want to revert this change, and save screenshots to your desktop,
# instead use "$HOME/Desktop"
defaults write com.apple.screencapture location "$HOME/Screenshots"
Using Automator, create a new Folder Action that receives notifications from the Screenshots folder. Add a Run Shell Script block, and make sure to Pass input as arguments. Combining the commands above, and this time using $@ syntax to handle multiple arguments, and absolute paths for pngquant and zopflipng, the final script is:
for f in "$@"
do
# Quantize to PNG-8 with 64 colors (lossy, fast)
# Majority of file size savings come from this
/usr/local/bin/pngquant 64 --skip-if-larger --strip --ext=.png --force "$f"
# Rename to communicate the majority of file size savings complete
# Allows me to grab the file faster
new_f="$(dirname "$f")/$(date -r "$f" +"%Y-%m-%dT%H.%M.%S").png"
mv -n "$f" "$new_f"
# Improve deflate compression for an extra 10%
/usr/local/bin/zopflipng -y "$new_f" "$new_f"
# Copy to clipboard (optional)
# osascript -e "set the clipboard to (read (POSIX file \"$(perl -e "print glob('$new_f')")\") as {«class PNGf»})"
done
Finally, I add the Screenshots folder to my Dock for easy access. This is achieved by dragging the Screenshots folder from Finder to your Dock.
Update, 2020-04-08: I now use Arq with MinIO, which I find faster and more reliable.
I use Arq to backup my Mac both to Dropbox and to my Synology NAS, but I’ve had difficulty keeping the SMB network share mounted and available for Arq. The solution to this problem is Autofs (Apple White Paper).
Autofs is an automounter, a program for ‘automatically mounting directories on an as-needed basis’, that was first released in Solaris 2.0, and comes preinstalled on MacOS since 10.5. This means, once configured, Autofs will automatically mount network shares and reconnect them if my NAS is disconnected for whatever reason. Here’s how I setup Autofs (jamesramsay/dotfiles cf11730).
The mount point is the directory where Autofs will mount the network share. We will mount the share in /mnt/Synology.
From the Terminal, create the /mnt directory:
sudo mkdir /mnt
Each map in the master map consists of a mount point (/mnt/Synology) and a mount map file. We will create the mount map file (auto_synology) in the next step.
Add the map to the master map:
echo "/mnt/Synology auto_synology" | \
sudo tee -a /etc/auto_master
Refer to auto_master documentation for more details.
The mount map file must be located in the /etc directory. To open the new mount map file for editing, execute:
sudo $EDITOR /etc/auto_synology
The mount map file is a list of trigger folders and network shares that will be mounted automatically. Add a line for each share to be mounted automatically:
Arq -fstype=smbfs,rw,noowners ://user:[email protected]/Arq
The mount map file above has only one mount. Autofs will mount our network share ://user:[email protected]/Arq at /mnt/Synology/Arq. The arguments between the trigger location and network share specify the SMB protocol (smbfs), to mount the share for read and write access (rw) and to mount the share with permissions inherited from the mount point (noowners).
Refer to the mount documentation for all the supported options.
To finish setting up Autofs we need to flush the cache, which will cause Autofs to reload the /etc/auto_master file. Using automount, execute:
sudo automount -vc
The cache will be flushed and the share we configured should be mounted. Autofs will now automatically mount the network share at boot and whenever it is needed by Arq.