Dear "Just pipe this script to bash" application installer developers,

Do provide detailed installation instructions as well. It's not that I can't read/inspect your bash script, it's that I hate doing it.
You force me to inspect your bash script, because I use my own methods at home to keep everything installed the way I want it.
It's really not helpful to only supply said script, and since you've already written the bash, writing detailed documentation should be a piece of cake.

Signed,
Everyone that prefers to install things their own way and not your way.

@Firesphere mandatory to mention the calibre project here, which lists, under the notes section:

If you get an error about an untrusted certificate, that means your computer does not have any root certificates installed and so cannot download the installer securely. If you still want to proceed, pass the --no-check-certificate option to wget, like this:
sudo -v && wget --no-check-certificate -nv -O- https://download.calibre-ebook.com/linux-installer.sh | sudo sh /dev/stdin

they do, however, provide manual install instructions too

calibre - Download for Linux

calibre: The one stop solution for all your e-book needs. Comprehensive e-book software.

@Firesphere one of the things I wish more devs did is initialize variables at the start of the script like "here's where things get installed to" so if I want to edit it, it'd be really easy. But prompting the user for those locations directly would be a great solution
@Firesphere I don't understand how install scripts were ever acceptable in the first place, especially given root permissions
@Firesphere i am probably preaching to the choir but in particular i hate this because half the time it side-steps using distro package managers and when a distro package is available for software i would much rather do that and have a sample configuration that i can inspect and manually instantiate with my preferred settings be prominently linked. a lot of times with this kinda crap i either have to find third-party guides, inspect the script to see where it's pulling the config from, or just boot up a virtual machine and run the damn install script if i can't immediately find where the config is pulled from