I was doing that for a while until I came across this. I liked the idea of completely removing Roku better.

https://www.howtogeek.com/884818/what-are-tracking-cookies-really/

For a second I thought tastykakes was your cat’s name.

The android app blocks unidentified callers and blacklisted numbers. This doesn’t affect calls from spoofed numbers, and I haven’t found the app’s spam detection to be effective enough.

How are you seeing ads at all, then?

We’re gonna need… a bigger shirt.

Imagine your brain triggering a phantom itch but you having no limbs to scratch with.

It’s not “exactly like” physical media. The license portion is a similar concept. But the difference is that the variables that determine whether I can keep watching the content whenever I want, in perpetuity, lie solely with me as the person who physically possesses the media. The corporation from which I purchased the license can’t unilaterally decide to revoke my access to the content.

They may not all be pedos, but a lot more are assholes who hate homosexuals and trans persons, or assholes who want to deny women their reproductive rights, or assholes who keep voting for far-right extremists. Just because a lot of Christians are “nice people” doesn’t mean that their ideology causes any less harm.

I saw Serenity before I knew Firefly existed. Love that movie but couldn’t agree with you more about the show.

Since I don’t know your level of expertise, I’ll go step by step. Forgive me if you already know how to do some of this.

In terminal, type “sudo nano /etc/fstab” (without quotes). This brings up a file where you can add the mount point so it mounts at boot and set options for the mount. Go to the end of the file and enter a line like the following, substituting your info in the appropriate places:

//[static ip for nas]/[top level folder on nas you want to mount] /[mount point in Linux] [file system type for mount] [mount options, nas login credentials, permissions] 0 0

Mine looks like this: //192.168.1.0/Media /mnt/Media cifs _netdev,user=anonymouse,password=*****,uid=1000,file_mode=0777,dir_mode=0777 0 0

The “_netdev” option is the one that delays the mount until after your network is up. The “file_mode” & “dir_mode” set the mount permissions. There is info out there showing how to insert a reference to a credentials file instead of placing them in fstab in plain text, but I didn’t bother since I have my computer and user profile pretty well locked down.

To get _netdev to work, I had to enter the following in terminal (without quotes): “sudo systemctl enable systemd-networkd-wait-online”.

I couldn’t find all the sites I visited while setting this up, but here are a few:

https://unix.stackexchange.com/questions/98707/how-do-i-mount-a-cifs-share-so-i-can-fully-control-the-mounted-volume-on-the-cli

https://unix.stackexchange.com/questions/429604/fstab-not-automatically-mounting-smb-storage?rq=1

https://help.ubuntu.com/community/Fstab#Options

Hope this helps!

I’ll look up the exact info when I get home and provide links if I can find them again.

The summary is that I had to add a line to /etc/fstab with the ip and folder route of the nas drive and folder, then the mount point in linux, the file system type for the mount, options that give login creds/group id + establish permissions I want to apply to the mount, and an option that keeps the drive from trying to mount until my network is connected.

Finally, for that last option to work, I had to enable a process that I forget the name of. I think it was in systemd, but I was able to initiate it from the command line.

Those eyes are fucking haunting.

Your version of the 8th would literally undo all religion (and a bit of science).

The commandment so nice he wrote it twice.

On mine, the piece that shoots water extends when in use and retracts out of the way when not.

So that’s what Mannheim Steamroller’s been up to.

It’s worse than the mic. They’re taking screenshots and sending them to a server that analyzes the image to determine what you’re watching.

*bake a little longer.

C’mon man. It was right there.

“There are several ways to exploit LogoFAIL. Remote attacks work by first exploiting an unpatched vulnerability in a browser, media player, or other app and using the administrative control gained to replace the legitimate logo image processed early in the boot process with an identical-looking one that exploits a parser flaw. The other way is to gain brief access to a vulnerable device while it’s unlocked and replace the legitimate image file with a malicious one.”