Cloudflare’s 1.1.1.1 DNS
For my future self,
Cloudflare’s primary DNS server is
1.1.1.1
Cloudflare’s secondary DNS server is
1.0.0.1
Sincerely,
Present self
Sync iCloud Contacts and Calendars with Thunderbird
There are only two add-ons needed to sync iCloud contacts and Calendars with Thunderbird: Provider for CalDAV & CardDAV and TbSync. Together, both of these add-ons provide everything necessary to enable iCloud Contact and Calendar syncing for Thunderbird.
Setup of both these add-ons is straightforward. In Thunderbird, navigate to Tools -> Add-on Preferences -> TbSync. In the TbSync Account Manager, click Account Actions -> Add Account -> CalDAV & CardDAV. Select iCloud for the account type and follow the wizard to completion.
Once finished, enable the account, and select which calendars and contacts to sync. Be sure to set a synchronization time as well.
Another useful add-on is CardBook. CardBook’s iCloud sync is independent from TbSync. TbSync puts iCloud contacts in the Thunderbird address book, while CardBook uses its own address book which opens in its own tab.
Setting up TRIM under Manjaro Linux
Manjaro Linux is based on Arch Linux, and Arch includes a package "util-linux" which provides two services for TRIM, "fstrim.service" and "fstrim.timer".
From my brief research I found that it is reccomended by the Linux community to run "fstrim" no more than once per week. This is to prevent excessive wear and tear on the SSD.
To enable automatic Trimming, run the following commands in a terminal.
systemctl enable fstrim.timer
systemctl start fstrim.timerTo check the status of "fstrim.timer", run the following command.
systemctl status fstrim.timerThe status output should show:
Active: active (waiting)That’s it! TRIM is now enabled and will run once per week with the fstrim.timer service.
Source: Arch Wiki – Solid state drive
O’ahu, Hawai’i
Cameras And Cases And Straps, Oh My!
I have recently become the proud owner of a Micro Four-Thirds, mirrorless digital camera, the Olympus OM-D E-M10 II. Like with any new hobby of mine, I tend to go overboard with searching for and purchasing accessories.
Straight away I had realized that I don’t care for the mediocre neck strap that was included with my camera. I wore it for a day or two while shooting, but I quickly found that I could not continue utilizing the strap.
Minimalism is usually my preference when traveling, and I had intended to do a fair bit of traveling with my camera. At first, I was considering the Op/Tech camera sling. This sling is an exceptional price and offered almost everything I was looking for to carry my camera. However, the more I considered the alternatives, the more I recognized that I wanted a minimal camera pouch.
After some more web and Amazon searching, I stumbled upon the National Geographic vertical camera pouch. What initially drew me to the NatGeo pouch was the uncomplicated design and modest size. Since I prefer to have my camera covered when not in use, I felt that this pouch would be the ideal compromise between a neck sling and a larger camera bag. The pouch’s strap is long enough to be comfortable across the chest of my 6’2” frame with additional adjustment length to spare. The EM-10 II fits quite snug in the pouch with the 14-42 EZ pancake lens attached. If the lens was much longer, the camera wouldn’t fit.
Now that I had found a suitable pouch for carrying my camera, it was time to find a wrist strap. I had never honestly considered buying a wrist strap; the idea never crossed my mind. I would rather make a strap of my own, so I did. Below is what I have created.
I used approximately 10 feet of blue 550 paracord that I had leftover from previous projects. For the bracelet, I utilized a snake knot weave, and a cobra knot to attach the strap to a small Nite Ize s-biner that I had around the house. I am quite satisfied with the way my wrist strap turned out, and in the future, I plan to explore other color options and clip hardware.
Cutting the ribbon
What the FBI is really asking of Apple.
The government is asking Apple to hack our own users and undermine decades of security advancements that protect our customers — including tens of millions of American citizens — from sophisticated hackers and cybercriminals. The same engineers who built strong encryption into the iPhone to protect our users would, ironically, be ordered to weaken those protections and make our users less safe.
Sherman
