It’s just Spike Rush, but I am very happy about this win.
Custom queue is disabled as well, so, it took a few attempts at Spike Rush to get to the map.
I like this updated loading screen with all characters in a team.
Also for some reason, Gauntlet Showdown never worked for me. It loads the main show instead.
I have been playing this fantastic game called Among Us in the last few months. It’s a game of deception, where there are two parties working on two tasks.
- Crewmates, who are in charge of completing tasks on the spaceship. Finish all tasks, and you win.
- Impostors, those who fake to be crewmates, but are actually sabotaging actual crewmates’ progress, or attempt killing them. When impostors lead crewmates by one member, they win.
It’s available across iOS, Android and PC/Steam. I mostly play with my friends, but online matches are not that bad either.
I started watching IPL today, and I noticed that Hotstar feed is introducing an ambient background “fan noise”. The idea seems to be that it gives viewers a real match experience.
For some context, matches are happening in UAE, and it’s just the players at the stadium. Fans are not allowed for COVID-19 reasons.
However, the background noise was doing more damage than goodness. Especially as a hard of hearing person, I couldn’t hear any commentary. I found similar comments from other Hotstar users:
I searched a bit more, and I found that it’s not actually a feature from Hotstar, but is coming from their upstream provider.
Krisp to the rescue
Some of my colleagues use Krisp at work. It’s a noise-cancelling app that’s commonly used with Zoom, Hangouts and other communication apps. I was curious to see if it might work with streaming services, and it does!
Krisp’s available as a desktop app, as well as in the form of a browser extension.
I tried the browser extension, but it didn’t work, as it appears Krisp needs the tab to introduce a “microphone stream” to enable noise-cancellation. Hotstar doesn’t require microphone access, which in turn means that noise cancellation cannot work.
Basically, the extension works with any web page that is using a microphone stream. All you need to do is to turn on the “Mute Noise” toggle and Krisp will start working on all the tabs that are currently using a microphone.Source – Krisp help page.
And, the desktop app (Windows in my case) works well! I use Windows 10, and I ran into some issues in marking it as the primary output device on
Sound settings. Marking it as the primary output device didn’t save properly.
Turns out this is intentionally done. I spoke to their support and they pointed me at a workaround, which involves setting app-level output on Windows settings. In my case, I marked Krisp for Brave browser, under Windows sound settings:
It works well!
It’s available now! In my test with Mullvad app, it doesn’t work. Mullvad’s DNS takes precedence. But it works flawless with Wireguard app instead. So, that’s what I am using, with Mullvad-generated config.
With that news, I updated my iPad to iOS 14 public beta 2. This is my first time running a beta build. Going by Twitter, this beta is stable.
I also reached out to NextDNS devs on their Intercom, to know more about this build. They let me know that it’d be announced on their reddit, when Apple approves it.
I have written about my DNS setup in the past, but that setup is a bit outdated that I wanted to write a new post. I continue to use NextDNS as my primary DNS service. On the VPN side of things, I have switched from NordVPN to Mullvad.
I have stopped using Cloudflare Warp as well. It’s not a VPN; they disclose IP to websites hosted on Cloudflare. They do claim it’s not a VPN, and I appreciate that transparency.
On Android, I use NextDNS’ DNS-over-TLS (DOT) address on Android’s private DNS setting. That setting is available on Android 9 and above. Marking my private, secure, encrypted resolver as such ensures that it works even when I am connected to Mullvad.
I use Wireguard Android client to use Mullvad, as I have noticed Mullvad’s official app to disconnect often.
Since I switched from NordVPN (they announced a Wireguard-based implementation as well!) to Mullvad, I started using Mullvad’s Wireguard implementation. It’s as simple as downloading the Wireguard configuration file from their website, and adding it to the Wireguard client app.
Since I run NextDNS CLI, I setup that local resolver address
127.0.0.1 as my choice of DNS on the Wireguard config.
As an additional measure, I use
127.0.0.1 as my resolver on Mac’s network settings as well. This ensures that NextDNS continues to be used when disconnected from Mullvad.
Taking this one step further, I have a Keyboard Maestro macro that periodically ensures that
127.0.0.1 is my Mac’s DNS resolver. This is not a great way to implement DNS leak checks, but it works for me.
Windows was an issue when I was using NordVPN. I could define NextDNS’ IPv4 addresses, but that’s not encrypted DNS. I wanted both encrypted DNS and VPN at the same time, which is when I learned about YogaDNS. It’s network interface-independent and works great with Mullvad. As usual, I use Wireguard Windows client for Mullvad.
iOS is an issue at this time. I can either use NextDNS or Mullvad. The problem is, DNS implementation is done as VPN tunnels, and when NextDNS tunnel is active, Mullvad VPN cannot be. This is changing with iOS 14!
I haven’t shut down my Pi-hole yet. It’s active and running, and serves all guests that connect to my home WiFi.
Look at this shiny new badge on my GitHub profile!
Calypso was probably the first OSS project that I contributed to. I am super grateful for all the feedback that I have received through the years, even though they were minor changes like CSS and copy.
If you haven’t starting contributing to OSS yet, start today! Maintainers are always happy to help. 💛
You can read more about GitHub’s archival program here.
The blog you’re reading at the moment was originally a Tumblr site. I moved it to WordPress when I joined Automattic. That was two years ago.
I was curious to see what has changed recently. Tumblr is very different from what I knew two years ago. I think I’m enjoying the experience so far.
The current blog will continue to exist as my primary site.