“You’re wrong. I’m very likable.”

Futurama warned us about this!

You’d be fucked like a choirboy at a Viagra-sponsored catholic-con.

Especially if they let the domain expire and you didn’t have time to migrate all those accounts that can be reset with just an email and a bad actor then registers the domain - or even just a slightly dumb actor that allows someone else to use what was your old email address.

deleted by creator

Obsidian looks interesting.

Thanks for the suggestion, but it seems like the challenges with Komga would be similar to those when using Mylar. I’ll probably just go for a spreadsheet.

That was my first idea too, but last I checked it didn’t scrape much other than English editions (using Comicvine AFAIR) and had no way of manually adding stuff it can’t scrape.

Scraping metadata. Wish/purchase/pull lists. Keeping track of multiple editions. Perhaps even scraping entire collections/storylines into manageable lists?

At the very least a quick way to use my phone to check if I already have a specific comic when I’m at the store.

Grist might be useful if I end up setting more than a spreadsheet up, thanks.

Thanks for the suggestion. I think that might be too much work for my needs though.

Pro. I WILL FIGHT YOU!

Sadly, I can not explain this to you any better.

DNS leaks normally occurs when your OS decides to use the wrong interface for DNS queries. It’s not magic, sorry.

There is a decent explanation here: https://www.top10vpn.com/what-is-a-vpn/vpn-leaks/

By doing a traceroute to the DNS IPs, you only confirm that traceroute goes through the VPN interface, not your DNS resolution.

Traceroute won’t show if you leak DNS requests outside of your VPN. (Unless you coincidentally also leak traffic, but then you’re pretty much just not using your VPN).

To confirm you’ll need to analyze your traffic-flow using a tool like tcpdump or Wireshark and check the source and destination for DNS traffic. If you see incoming DNS responses on an interface that is not your VPN-adaptor or maybe a loopback interface then you’re probably not tunnelling DNS through the VPN.

To answer the question in the headline: Regular DNS is unencrypted and quite easy to snoop on, so any node on the route between you and the DNS server will be able to read it if not using a VPN (i.e. DNS leak). Not sure what you mean by adversary, but it’s not like anyone on the internet can see your traffic. The DNS server may log your request and if you’re not on VPN, your IP address may be logged too.

Why? The ending was pe

Then you’re working in an idiotic repo. You could just as well have have a master and an actual_master branch. Similar idiocy.

Jethro Tull doesn’t romanticize Aqualung (the old man that sits on a park bench and eyes little girls with bad intents). Quite the contrary actually.

Thanks drug users :-)

Your average smartphone user definitely can’t. I mght, but I strongly doubt it is worth the effort for now.