Arun's blog ๐Ÿ“’

  • Google Drive backup for WhatsApp

    A lot of folks don’t realize that the Google Drive backup for WhatsApp is not end-to-end encrypted like messages and files within WhatsApp. When that backup to Google cloud happens, all messages and files are visible in plain to Google.

    The same problem exists in Telegram, which backs up messages to the cloud. The only exception in Telegram are messages and files sent within their “secret chats” feature, which is end-to-end encrypted. When folks move from WhatsApp to Telegram, it’s important that they understand that this is a step down.

    WhatsApp without Google cloud backup is a good option, and even better when WhatsApp’s new end-to-end encrypted backups feature is fully available. If I remember well, it’s available only on iOS at the moment but for some reason that support document doesn’t mention that. Or, is it available for everyone already?

    The best option, without doubt, is Signal: it is end-to-end encrypted by default and offers encrypted backups too. One problem with Signal is that it doesn’t offer cloud backups. So, the backups are stored locally on the device.

  • Lucky last shot

    A screenshot from a VALORANT Replication gameplay that shows Raze clutch the game with a last shot of Jett.

    I got very lucky with this last shot. In a VALORANT Replication game, both teams were at 4-4 mark. Spike was nearby but I didn’t have enough time to plant. Decided to go for the last kill, but I am a Judge player all the time, which means Jett being far was a tough kill.

    The Jett opposite me had an Operator too, I think, but luck favored me and I could reach her. Got the shot in the last 3 seconds. Phew!

    A screenshot from a VALORANT Replication gameplay that shows Raze as the game MVP.
    A screenshot from a VALORANT Replication gameplay that shows the last round stats from the game.
  • jq magic to create contacts for SimpleLogin aliases

    One thing that I found lacking in the SimpleLogin API is that, it doesn’t expose an API endpoint to create a contact based on the alias’ email address. Rather, the POST /api/aliases/:alias_id/contacts endpoint requires the alias ID. So, I ended up downloading all aliases as multiple batches (each query returns upto 20 results) and saved them as json files in a folder.

    With them in a folder, I could use jq to parse all of these json files for an alias email address, get its ID and further use it to create a new contact. All of this works like a charm now. My entire process works independent of the dashboard now: create a new alias, get its ID, create a contact, copy the reverse contact address, paste it on my email client.

    The first part for getting the alias ID involves this command:

    cat ~/Documents/SimpleLoginFiles/* | jq '.aliases[] | select(.email=="aliasAddress")' | jq '.id' | tr -d '\n' | pbcopy .

    It was a pleasant surprise when I learned that I could pipe in all files in a folder to jq, instead of having to implement some sort of a loop logic. I don’t know if it’s bash’s magic or something that jq handles elegantly.

    The second part for creating the contact involves this command:

    curl --location --request POST '' --header 'Authentication: token' --header 'Content-Type: application/json' --data-raw '{"contact": "contactAddress"}' | jq '.reverse_alias' | tr -d "\\"" | pbcopy .

    If you are wondering what the tr -d "\\"" part is, it’s to remove the unwanted escape characters that appears as a part of the SimpleLogin API output. I imagine it’s possible to remove that using jq, but for now, the current workaround is sufficient.

    The contact’s reverse address is finally in my clipboard, which I can paste on Apple Mail:

    A screenshot of my Apple Mail on Mac, that shows an email address pasted to the "To" field of the composer.
    Reverse alias on the “To” field of the composer

    SimpleLogin recently announced an update to their Firefox extension too, to create reverse aliases (contact reverse address) on the go, but I like this API-based process better. The extension takes a while to populate all aliases.

  • Storing 2FA codes on my 1Password

    I definitely agree with what James writes here:

    Storing them in your password manager is probably as safe, or even safer, than using your phone

    Many people, like Google or the government, text a code to your mobile phone when logging in. That might be visible on my mobile phoneโ€™s lockscreen, or my SIM card could be cloned and used elsewhere. Itโ€™s much better than having nothing at all, of course: but itโ€™s not quite as secure.

    If youโ€™re storing your 2FA code using Google Authenticator or Authy on your phone, and your password is saved on your phone, then youโ€™ve no two-factor authentication anyway. Both are being stored on the same device, just like your password manager would.

    Lose your phone with Google Authenticator installed, and you lose your codes. If you change phones, you can manually transfer those codes these days, assuming that you still have access to your old phone, but itโ€™s a monumental hassle to switch otherwise.

    Most people feel that storing 2FA codes would equal putting all eggs in the same basket, but password managers these days are locked down with themselves supporting 2 step authentication. In my case, 1Password goes one step beyond by offering an unique Secret Key method.

    My 1Password’s 2FA code is stored on Authy today, but I guess it’s time to replace that with a physical key.

  • Thoughts on the 1Password-Fastmail partnership

    A week ago, the wonderful folks at 1Password announced a new feature: automatic generation of email aliases when creating a new vault entry. As an user of SimpleLogin, I am already familiar with the concept of using unique aliases for each website. It’s the same functionality that 1Password and Fastmail announced, except that generating the alias doesn’t require a visit to the email provider’s website.

    Fastmail vs SimpleLogin

    I see how this is helpful for the common user, but I am also slightly sad that smaller players like SimpleLogin and Anonaddy get left out in these corporate partnerships. From a quick comparison between Fastmail’s alias service and the smaller players, the best choices are the latter ones. For some context, SimpleLogin does not have any limits on the number of aliases that I can generate or the number of reply addresses (address that you send an email to, so that SimpleLogin sends out that email to the final destination from the actual alias address), while Fastmail limits them to 600 aliases and 500 sending identities (equivalent to SimpleLogin’s reply address).

    In my 2 years of being a SimpleLogin customer, I have generated over 1200 aliases and I guess, about 50% reply addresses. All of that is available at a fantastic cost of 30 USD per year.

    An image from my SimpleLogin dashboard that shows the number of aliases that I have generated, incoming emails, outbound responses and blocked emails.
    An image from my SimpleLogin dashboard that shows the number of aliases that I have generated, incoming emails, outbound responses and blocked emails.

    Except one outage, the service has been spectacular so far and support is great. The founder, Son, often responds to my emails, welcomes feedback and sometimes includes users in future product discussions. If you are looking for a privacy-respecting email alias generator, look no beyond SimpleLogin. This is not a sponsored post. I am just a happy user.

    SimpleLogin is also open-source and can be self-hosted.

    Final words

    I am not a Fastmail user today, but I hear great things about their service. I wouldn’t be switching to them though, as my existing mailboxes on Professional Email and Migadu haven’t seen any issues so far. Plus, Fastmail is based in Australia which is known for poor encryption laws.

    I love that 1Password is headed in a great direction with extensions. First they announced privacy-respecting, unique cards for online transactions with And now, this partnership with Fastmail. Can’t wait to see what the future holds.

  • Among Us roles ๐Ÿ‘€

    Looks like Innersloth is working on roles for Among Us! I have enjoyed countless hours playing Town of Us. Can’t wait to see what official roles bring.

  • Thoughts on WordPress Full Site Editing

    For years, design on WordPress had been in the form of PHP templates bundled together as a WordPress theme. The templates apply to specific content as desginated by the WordPress Template Hierarchy. The largest issue with this approach would be that anyone wanting a custom design on their site must have PHP skills to write theme code.

    Full Site Editing (FSE) is changing that process. Those with programming knowledge can design custom designs for their pages, posts or even for search archives or 404 pages. This is largely possible, thanks to the extensible nature of Gutenberg blocks. They are now available for use on sidebars in the form of widgets, on the header and footer areas, in the form of Full Site Editing.

    Personally, I wanted a theme that shows all of my blog posts on the homepage, but with a customization that only short posts display the full output and longer-form posts require the visitor to open the blog post to view it. I have tried many themes over the last few years, Twenty Nineteen, Twenty Twenty and Spearhead, and everything involved a lot of CSS hack to display the output I wanted. After trying Blockbase with Full Site Editing, I have come to a conclusion that this is the future.

    New design with Blockbase and Full Site Editing

    Right now, my homepage looks as shown below, this is a two column layout:

    An image showing my blog's homepage design, which is composed entirely using the new WordPress Full Site Editing experience.

    The content on the right isn’t my sidebar. Rather is the right column of my homepage’s FSE editor. For comparison, my editor view is as shown below:

    An image showing my blog's homepage design on the editor view, which is composed entirely using the new WordPress Full Site Editing experience.

    Likewise, here’s a comparison of the single blog post view:

    An image showing my site's blog post design, which is composed entirely using the new WordPress Full Site Editing experience.
    An image showing my site's blog post editor view, which is composed entirely using the new WordPress Full Site Editing experience.

    See how the editor looks very similar to a blog post or page editor?

    Things that I would like to see improved

    Block navigator to be visible by default

    Most people don’t realize that a block navigator is available at the top left, next to the undo and redo icons. I know this because I have work in customer support and I have seen hundreds of customers try to navigate or edit blocks from the editor view. When there are many blocks on screen, it becomes tricky to choose the one you mean to edit. That’s when the block navigator helps.

    If I remember correctly, Elementor automatically shows their sidebar whenever one opens the editor view. A similar design would be neat here.

    It’s possible that this is already on Gutenberg’s (which is a open source, community-driven project) radar already. I haven’t looked yet.

    Different templates for different widths

    This was my most frustrating issue when I started building the new design. Blocks come with intelligent design guidelines, like a 2 column block automatically changing its orientation to vertical mode when the visible screen space is less. But this came with a challenge that the right column, which is moved to the bottom on mobile widths, wouldn’t have enough space between itself and the footer-located blocks.

    I tried a bunch of CSS-based workarounds, but eventually, I decided that it would be a good idea to have two versions of the same content. That’s why you can see my index template editor to have two “Query loop” blocks, where one is placed within a columns block and one without a columns block.

    And I hide each “Query loop” block using CSS, on certain widths.

    If you inspect the source code of my index page, you can see two “Query loop” blocks. That’s not ideal. That’s not a good idea in terms of SEO either. I am yet to read more about the impllications of doing this, but for now, I am happy with this approach.

    Importing template design

    I am able to export template designs using a handy option at the top right of the template editor. But it’s not clear how I can import them today. I asked about it on the community forums for now.

    I tried copying the full content from the top right menu, and pasting that on a different site’s template editor, but I couldn’t get the same design. I suspect that happens because some plugin-blocks plugins that I used on my first site’s template editor are not activated on the other site. I didn’t give this a good look as I was short on time and ended up fixing the missing block settings (like padding settings and custom CSS selectors) manually.

    Block breakage when certain settings are applied

    Only one example comes to mind at the moment. When a “Post title” block is added to a template editor, and when it is marked as to appear as a link, the editor view breaks. I have reported this on the Gutenberg project repository.

    There was another issue with a block, but I don’t remember it at the moment.

    Overall, like any software, WordPress Full Site Editing is not perfect. But the community and my colleagues at Automattic are hard at work. I imagine Full Site Editing to be the gold standard of website building experience in the coming years. If you wish to participate in the testing, the instructions below can help.

  • Growing my home lab: Tailscale TLS certificates for each Docker with Caddy

    I have grown up reading Raspberry Pi users build amazing projects on this wonderful reddit: r/homelab. Until an year ago, I didn’t have a clue where to start, mostly because the idea of setting up Wireguard to access these self-hosted services was a bit intimidating. Tailscale changed everything.

    Tailscale is a mesh VPN software that makes it incredibly easy to connect your devices together. This includes your laptops, mobile devices, servers, and even printers. The idea is that, Tailscale acts as an interface for all devices to talk to each other, without having to create, manage and install Wireguard certificates manually.

    Self-hosted services with Docker and Tailscale

    Thanks to Docker, I have been running a Whoogle instance and a libreddit instance for a while. Each on a different port, while Tailscale and pihole are installed on the Raspberry Pi directly. It has worked well so far, but one thing that bugged me is the lack of HTTPS support.

    That changed a while ago because Tailscale TLS certificates are now available for each node address: Provision TLS certificates for your internal Tailscale services. Obtaining the certificate and its key was very easy. Setting up my services (pihole, libreddit and Whoogle) to use the TLS certificate was a different challenge though.

    Caddy to the rescue

    That’s when I discovered Caddy, which turns out to be a web server that can provision TLS certificates as well.

    But my use-case was to run Caddy as a reverse proxy, to serve each Docker container on the Tailscale node address, each on a subfolder. After a lot of trial and error, reading documentation, reading GitHub issues, I have the following running with TLS:

    • Libreddit on the root domain
    • Whoogle on
    An image showing a TLS certificate instance on a self-hosted Whoogle instance.
    Tailscale TLS certificates on a Whoogle instance

    I wanted to access my pihole admin on HTTPS too, but I couldn’t get it working on a subfolder, like When I assigned the root domain to pihole, libreddit had to go to a subfolder like and when I tried that, CSS on my libreddit instance broke.

    Firefox reports that this is happening because of an incorrect MIME on the stylesheet:

    The stylesheet was not loaded because its MIME type, โ€œtext/htmlโ€, is not โ€œtext/cssโ€.

    I bet this is fixable. It’s an incorrect replace rule on my Caddyfile. I plan on looking at this sometime next week.

    Caddyfile to route and use Tailscale TLS certificates

    For now, my Caddyfile looks like this:

    	order replace after encode
    :80 {
    	reverse_proxy localhost:1080
    } {
    	tls /etc/caddy/ /etc/caddy/
    	reverse_proxy localhost:8080
    	route /google {
    		redir /google /google/
    	route /google/* {
    		uri strip_prefix /google/
    		header Location "" ""
    		replace {
    			"" ""
    		reverse_proxy localhost:5000

    replace directive in this configuration is a Caddy module: replace-response. It’s not bundled with Caddy out of the box. Setting that up was an interesting challenge as well, because that involved installing xcaddy and using that to build a custom binary for Caddy.

    In the above file, and are the TLS certificate and key issued by Tailscale. The first file actually is named but I renamed that to ending with .pem. Gotta read up on how .crt and .pem files differ.

    If you are looking for a web server or reverse proxy manager, I cannot recommend Caddy enough. Their documentation and support on the community forums are impeccable.

    Oh also, I tried learning in the public for the first time by tooting my progress.

    That helped me retain my lessons better and held me accountable, in the way that I wanted to see this completed. No wonder many successful people learn or build in the public. I plan on doing this more often.

  • libreddit: Self-hosted reddit on the Tailscale network

    If you have been following my posts, you might have noticed a trend recently, where I am looking for self-hostable alternatives for common websites and apps that I access. And I put them all on the Tailscale network so that they are easily accessible from other devices.

    Today, I stumbled upon libreddit, a self-hosted, tracker-free reddit interface. It’s important to note that this is just an interface and does not allow accessing your reddit account through it.

    Installation of libreddit

    The installation process was fairly straightforward: SSH into my Raspberry Pi, and use the Docker instructions on libreddit homepage. That’s it — a libreddit UI would be available on on your computer, and if the Raspberry Pi was is connected to a Tailscale network, it becomes immediately available at the Tailscale node address as well. In my case, I can access the libreddit interface at http://mew:8080 too, thanks to Magic DNS.

    Setup and usage

    I like how libreddit is fast on desktop and mobile views, and is configurable in many ways: wide UI, theme, sorting of posts and comments, and most importantly, supports importing of existing subreddits that you follow. Here’s a guide on that process.

    A screenshot from GitHub that shows instructions from the author of libreddit project to import subreddit subscriptions from reddit
    A screenshot from GitHub that shows instructions from the author of libreddit project to import subreddit subscriptions from reddit

    Since one doesn’t have to log into their reddit account, all of libreddit settings and subreddit subscriptions are stored locally. They will be lost when browser cookies are cleared, but libreddit goes one step further in allowing one to import back settings and subreddits using a link. Look for the details at the bottom of the libreddit settings page.

    Whoogle on Tailscale

    Access ad-free, tracker-free Google search results.

    Hydroxide on Tailscale

    Access your ProtonMail emails on a self-hosted, open-source bridge called Hydroxide.

    Pi-hole on Tailscale

    Install pi-hole on Tailscale, to get ad-blocker functionality on all devices

    Overall, I am very happy with libreddit. I have made it available to my friend who is on my Tailscale network as well, using Tailscale ACLs, and the subreddits/settings he configures wouldn’t be visible at my end. Likewise, he cannot see what I configure.

  • Whoogle on the Tailscale network

    I am a happy DuckDuckGo user of many years. It matches all of my requirements: good results, ability to jump to the first result with a keyword (using “\”), bangs to search within particular websites and tracker-free search results.

    I recently learned about Whoogle though and I had been wanting to try that for a while. It’s a self-hosted, ad and tracker-free search engine that fetches results from Google. The project promises that it’s free of cookie and IP address tracking too. It’s open source and it seems that it can be set up on any device. I have two Raspberry Pi devices at home, both connected on my Tailscale network, acting as Pi-hole nodes to block ads. One of the two Raspberry Pis also acts as my Hydroxide node to fetch ProtonMail emails.

    I decided to install Whoogle on the same Raspberry Pi that runs Hydroxide. The process turned out to be really simple. Whoogle has thoroughly documented instructions to install on a Raspberry Pi with Docker; I installed using these Docker Hub instructions:

    docker pull benbusby/whoogle-search
    docker run --publish 5000:5000 --detach --name whoogle-search benbusby/whoogle-search:latest

    I ran into a hurdle involving a dependency’s compatibility with my Raspberry Pi image, but that was easily solvable. Once all that of was done, the Whoogle instance was available at but it was neatly exposed on the Tailscale interface too, thus being available at my Tailscale node’s IP address: Thanks to Tailscale’s Magic DNS, this instance becomes available at a readable address too: http://mew:5000. mew is the name of my Tailscale node. It’s configurable on the Tailscale admin.

    An image showing a search query on my Whoogle instance.
    An image showing a search query on my Whoogle instance

    Since all of my devices are connected to the Tailscale network, my Android can access it as well:

    An image showing a Whoogle search query on Android.
    An image showing a Whoogle search query on Android

    It’s nice overall. I am not bothered by the http queries as the communication between my device and the Raspberry Pi is end-to-end encrypted, thanks to Tailscale.

    I configured access control lists on Tailscale to make this Whoogle instance available for my friends connected to the same Tailnet.

    I plan on using Whoogle for a few weeks to see how it fits into my workflows. I will be missing out on some rich DuckDuckGo features like DuckDuckGo Bangs and jumping to the first result, and if it becomes too much to compromise on, I plan on going back to DuckDuckGo.

    libreddit on Tailscale

    Self-host a private, ad and tracker-free reddit frontend UI with libreddit.

    Hydroxide on Tailscale

    Access your ProtonMail emails on a self-hosted, open-source bridge called Hydroxide.

    Pi-hole on Tailscale

    Install pi-hole on Tailscale, to get ad-blocker functionality on all devices

1 2 3 11
Next Page

Hey there!

I am a Happiness Engineer at Automattic, working on support. If you enjoy discussing online privacy, encryption, and fediverse like I do, you can reach me by commenting on my posts, or by email.