Yes they can, but it doesn't really matter. They can't send you a faked dns response if you are connecting to the website via HTTPS, because a fake website won't have the correct certificate.
They may block your DNS queries so you can't connect to things, but they're your ISP, they can block all of your traffic anyway.
The worst they can do by injecting their own DNS server is to track your queries, but if you're not doing complicated stuff you are telling your ISP which sites you visit anyway (because of TLS Server Name Indication) and where your traffic goes (because the ISP needs a target IP to route your traffic).
A VPN "solves" all of these problems in so far as that now your ISP has a harder time tracking you, but you just moved the problem and now have to trust whoever is running the VPN server.
I understand that perspective, but does it really have to be advertising?
jxl can also do lossless compression and transparency, so the important features of png are there
You need like 14000 kcal for a whole week, there's no way that's enough
Game #145 Shortest path: 5 (Avg. 5) Total words: 10 (Avg. 10) 🟦🟦🟪🟥🟥 | 🔥 1
https://linxicon.com #Linxicon
I'm not sure spotifyd is just spotify (Edit: I checked, its some kind of spotify client meant to be run as a daemon? No idea what permissions that needs)
And the user that executes a service isn't determined by who owns the service file, there is a user option in the service config
I don't know much about systemd, but i assume the file should be owned by root? It looks like it isn't, so try chown root:root spotifyd.service
I don't like this explanation, because if you don't know what wormholes are before, you might think wormoles are represented by the hole stabbed through the paper by the pencil.
Correctly stretching the paper to make a 2D wormhole is hard, but maybe you should just use a bagel or something
What are the other options in the "Sort: Last Played Date" dropdown?
The site looks good, but it desparately needs content moderation
Boot from a live disc/usb, check the kernel logs. That should at least tell you where the boot process got stuck, what to do about it depends on what exactly broke.