I did a woopsy, forgot to make the changes permanent, and my server auto-updated, won’t happen again
Skill issue, just click faster and more tomatoes will appear 🙄
I’m not quite sure how that could be done…
I can’t modify the contents of other websites embedded as iframes. The other option would be to make a request in my server and modify the content and then pass that, but then I’d be hosting an unsecured proxy which I don’t want to do.
The only good way to do this would be with a browser extension, which I haven’t got a clue on how to create. :/
Provide me with the catboy picture
Heat (1995)
Absolute must-watch
chsh does not modify /bin/sh
Maybe you’re thinking of a certain video from a certain YouTuber who linked /bin/sh to fish?
Gordon, you lousy motherfucker. Get your dork ass down to the test chamber, or I’ll shove the sample up your ass!
That’s… all stow does, there’s nothing more to it. If you need some other feature don’t waste your time trying to make it work with stow, It’s just a meme in my opinion.
About the “package manager” functionality, stow was originally supposed to be a development tool for the Perl programming language, you download a bunch of libraries into a directory, then use stow to merge those files into the root of your project (like a caveman), as it turned out some people started using it to manage dotfiles, and here we are.
When I started trying to organize my dotfiles, I started with stow, but quickly found it very limited.
After that I found dotdrop, which is considerably more involved, but gives you total control. My config with dotdrop quickly started growing insanely huge, at some point I even had system-wide systemd services declared.
Then I found out I was basically reinventing nixos and home-manager, so I switched to that.
I think there’s still something wrong with your setup… You should be able to have as many Firefox windows and tabs as you’d like without using too much RAM, since they should de “suspended”.
I regularly have hundreds of tabs running fine, on 32GB of RAM.
Most likely it’s a vscode extension that’s leaking memory, and this problem will still happen after your upgrade, just take longer.