imap-backup: "Backup GMail (or other IMAP) accounts to disk." Saves to mbox. Actively maintained. Ruby. HN discussion.
Postsack: "A high level visual overview of swaths of email." Think GrandPerspective for email. Rust.
NodemailerApp: "App includes local SMTP and POP3 servers, a sendmail replacement, catchall email domain service, AMP4Email renderer and it imports emails from EML files, EMLX files, large MBOX files from Gmail takeout, Maildir folders and Postfix queue files for inspection and preview. Ever wanted to view the actual HTML source of a nicely designed email instead of some garbled rfc822 text? Just open the HTML tab of an email to see it." [emphasis added] Electron.
/misc | Jan 10, 2022
The mainstream media continues to gaslight the public with stories like this one from AP News on January 4, 2022 titled Why are so many vaccinated people getting COVID-19 lately?:
"People might mistakenly think the COVID-19 vaccines will completely block infection, but the shots are mainly designed to prevent severe illness, says Louis Mansky, a virus researcher at the University of Minnesota."
Whatever could've given people such a mistaken impression?
President Joe Biden, July 21, 2021:
"[Y]ou're not going to get COVID if you have these vaccinations." 📺
CDC Director Dr. Rochelle Walensky, March 29, 2021:
"[O]ur data from the CDC today suggests, um, you know, that vaccinated people do not carry the virus, don't get sick, and that it's not just in the clinical trials but it's also in real world data." 📺
Rachel Maddow, March 29, 2021:
"Now we know that the vaccines work well enough that the virus stops with every vaccinated person." 📺
Dr. Anthony Fauci, May 17, 2021:
"The risk is extremely low of getting infected, of getting sick, or of transmitting it to anybody else, full stop." 📺
"The Pfizer-BioNTech COVID-19 vaccine has not been approved or licensed by the U.S. FDA but has been authorized for emergency use to prevent COVID-19 in individuals 16+." [emphasis added] 📺
/misc | Jan 04, 2022
export SSLKEYLOGFILE=~/Desktop/sklf && open /Applications/Firefox.appsudo tcpdump -i en0 -s 0 tcp port https -w ~/Desktop/capture.pcappbpaste /mac | Jan 03, 2022
returning errors like "The document 'foo.pdf' could not be saved as 'bar.pdf'." and "The file couldn't be saved." Previous and succeeding versions of macOS/Preview do not suffer from this bug, saving the same PDF file without complaint, albeit with significant bloat even when simply duplicating:
Preview's "Export as PDF..." or the print dialog's "Save as PDF" are often cited as solutions, but those methods resulted in the largest PDFs of all, at 974KB and 975KB respectively.
Iman Mahmoudinasab's unjustifiably-low-scoring answer on Ask Different contained the necessary clue: "Another common reason for this issue is the PDF file is password protected." Rather than relying on the recommended cloud-based service ("Try 7 days free"), I used qpdf:
%qpdf --show-encryption in.pdf... modify document assembly: not allowed modify other: not allowed modify anything: not allowed %qpdf --decrypt in.pdf out.pdf
The resultant PDF (which could be freely duplicated, saved, etc.) was actually smaller than the original, at just 269KB.
While Acrobat PDF owner passwords are easily bypassed as in this case, user passwords require decryption:
The standard security provided by Acrobat PDF consists of two different methods and two different passwords: a user password, which encrypts the file and prevents opening, and an owner password, which specifies operations that should be restricted even when the document is decrypted, which can include modifying, printing, or copying text and graphics out of the document, or adding or modifying text notes and AcroForm fields. The user password encrypts the file, while the owner password does not, instead relying on client software to respect these restrictions. An owner password can easily be removed by software, including some free online services. Thus, the use restrictions that a document author places on a PDF document are not secure, and cannot be assured once the file is distributed; this warning is displayed when applying such restrictions using Adobe Acrobat software to create or edit PDF files.
/mac | Dec 28, 2021
/mac | Nov 21, 2021
Appends ".jpg" to files dragged and dropped onto the saved script's icon:
@echo on
for %%I in (%*) do ren %%I "%%~nI.jpg"
pauseFrom Microsoft's 'for' documentation:
Simple, but perhaps a trifle cavalier, without any sanity checks or filetype awareness. By leveraging exiftool, we can improve on things a bit:
@echo on
for %%I in (%*) do exiftool.exe "-filename<$filename.$filetypeextension" -r -ext . %%I
pauseH/T:
/windows | Nov 20, 2021
/misc | Nov 18, 2021
Proposed solutions abound for "Run-time error '1004': PasteSpecial method of Range class failed", which, intermittently yet relentlessly, plagued an XLSM spreadsheet when pasting user-selected rows via VBA.
Buried in a previously 0-rated Stack Overflow question and answer pair, PASUMPON V N graciously unveiled the mystery:
Since you are copying large amount of data, you need to clear the memory after...pasting the values.
Please use the below code at the end of pastespecial line
Application.cutcopymode = False
Application.cutcopymode = True
It appears that the second line can, and probably should, be excluded:
Application.CutCopyMode = Trueeither does nothing at all or it does the opposite of what you think it does.
/windows | Oct 28, 2021
If you've replaced the Apple SSD in your Mac with a third-party model and attempt to install Monterey, you may receive an error like:
To resolve, reinstall an Apple SSD, install Monterey, reinstall your third-party SSD, and install Monterey:
Results of some cursory testing with a MacBook Air (13-inch, Early 2015) which was still running macOS 10.12 Sierra with Boot ROM version MBA71.0166.B02:
Maleficent_Stranger's reddit comment, the bulk of which is reproduced here verbatim, offers more detail:
If you already changed your ssd back in early mojave or high sierra time, you firmware was not updated since that time, because, only after 195.xxx BootRom version (which came together with Catalina 10.15.7) Apple enable firmware upgrade through third party ssd. Prior to that, you can't update firmware using third party, only through original apple ssd. So, something like 122.xxx , 162.xxx, or something older like MBA.xxx & MBP.xxxx , you won't be able to update to Monterey right away, because the firmware wont't allow new version installation on 3rd party ssd. Installing Catalina or BigSur first won't help, since it won't update your firmware either.
You should have no problem installing Monterey if your BootRom version is already on 4xx.xxx digit. Regardless what SSD is installed in your Macbook.
I do several Monterey upgrade on my customer's macbook which already have my custom branded 3rd party ssd inside, and all installed just fine. Key is, all those units already on BigSur firmware version (4xx.xxx)
If you already in 195.xxx BootRom , you can manually upgrade your firmware through terminal as well. As long as you have the firmware file (can be extracted from BigSur/Monterey installer itself)
Xaphier and others have reported frequent crashes after installing Monterey on a third-party SSD:
My Mid 2015 15" MBP with 1TB Sabrent SSD (Sintech adapter) started to crash a lot after upgrading to Monterey. I had almost 0 crashes during Big Sur, but now I get 3 to 4 crashes a day, very frustrating. I updated to Monterey by swapping the drive to original Apple SSD and update to Monterey, swap to Sabrent SSD with adapter and update to Monterey again.
OWC support suggests same workaround (reinstall Apple SSD, install Monterey, reinstall OWC SSD, install Monterey)
Manually updating firmware:
This tweet claims that the original SSD (not just any Apple SSD) must be used because, "Apple BridgeOS right now verifying original SSD." However, Alexandre Torres points out that:
The tweet about iMac 2017 and BridgeOS is wrong in so many levels, from the start, the 1st iMac to have T2 is 2020 iMac 27". Without T2, no BridgeOS at all. Even if he is talking about iMac Pro, the SSD from MBP won't even fit (iMac Pro uses NAND modules, same as 2019 Mac Pro).
/mac | Oct 27, 2021
Deark is a portable command-line utility that can decode certain types of files, and either convert them to a more-modern or more-readable format, or extract embedded files from them. It also has an option (-d) to display detailed information about a file’s contents and metadata. It’s free and open source.
The demo digs through Inception-like layers in fbm-1.2.tgz to identify and convert a Sun raster image to PNG.
~250 formats, from obscure (BMI, TN3, etc.) to common (MP3, PNG, etc.), are supported:
/nix | Oct 22, 2021