You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
Phil Lembo
plembo
Enterprise Architect, sysadmin, identity management engineer now focused on collaboration solutions for a global Fortune 200 company.
Alexandre Lotte, the author of icsp describes it as a "Small, fast and simple command-line tool to conver calendar exports (.ics files) into TSV/CSV files for easy analysis and usage in broader use-cases."
And so it is.
I had accidentally imported a holiday calendar into my default Proton Calendar, when I realized two very horrible things: (1) I had no backup; and (2) no one really provides tools for removing entries from calendars in bulk. Later, I would add "Proton Calendar doesn't have a versioning system". But then, no one else does either.
I was screwed.
A few minutes (OK, about a half hour) of searching the Internet, and I found icsp: which turned out to be everything its author wrote that it is.
Custom settings for Vivaldi browser on the desktop
This is a relatively short list for a reason: at least as of version 7, Vivaldi's default settings are reasonably secure, private AND ergonomic. Note that the settings available for the mobile versions of Vivaldi differ considerably from those in the desktop versions.
Also keep in mind that I'm currently using four extensions with Vivaldi on my desktops: uBlock Origin Lite, Bitwarden password manager, Raindrop bookmark manager, and Dark Reader to apply dark mode to web pages.
Only my changes to the defaults appear below.
General > Homepage > Specific Page > your favorite homepage
NOTE: This was written while I was experimenting with using podman in lieu of docker, something I've finally returned to.
Not all docker images are compatible with podman, and some still require root even under podman. Approach with fear and trembling (and a willingness to do your own research).
Going rootless is one of the main reasons for switching to podman. But if you're running shared services on server for internal users and don't want a separate account for each app, creating a special (non-privileged) account for all pods may be the answer.
This work was done on Ubuntu 22.04 LTS using the shipping Ubuntu package for podman (podman-3.4.4+ds1-1ubuntu1).
Prerequisites
Install podman and enable the podman.socket service (I'm using the version in my distro's official repository):
Auto start podman containers on reboot as systemd services
NOTE: This was written while I was experimenting with using podman in lieu of docker, something I'm now looking at again.
Not all docker images work with podman, so be prepared to struggle with the system and to engage in many fruitless Internet searches.
Intro
OK, so who knew podman containers won't automatically start on reboot? Yeah. Me neither.
Found out after a family member complained about getting a 500 error when trying to reach a PiGallery2 instance I had set up on the home server.
Fixing this is easy, as detailed in Pratham Patel's "How to Autostart Podman Containers?" over on Linux Handbook: A systemd servic
These settings choices follow the advice on Privacy Guides for Brave, except where they don't. And yes, these were my personal preferences: no judgement if someone disagrees. NOTE: I no longer use Brave.
Brave Shields are disabled in favor of uBlock Origin Lite for tracker and ad blocking.
Here is my modified list of changes beyond Brave's defaults:
UPDATE: According to the Ubuntu bug history cited below, this problem was fixed with an update of ubuntu-drivers-common on September 10, 2024. After removing the workaround udev rule and verifying the package was updated on my system, I confirmed that the troublesome behavior didn't return for me. That said, at least one other person has advised that they're still experiencing it even with the workaround.
Got bit by Ubuntu Linux bug #2060268 on the latest kernel update for 22.04 LTS (6.8.0-40-generic).
As in the bug report (and many forum posts across the Internet) this appears to be due to a collision between the simpledrm kernel module and NVIDIA drivers. The symptom is a nonexistent display device being assigned as card0. The practical effect is to throw off any previous configuration of the display system (display 1 becoming display 2, display 2 becoming display 3). As a result, customization