Yes each input requires a different signature (even if they spend from the same address),
There are no signatures on the outputs. The full transaction, including its outputs, is covered by the signatures on the inputs. But you can somewhat modify (using sighash flags) what the signature covers (commits to) when you make the signature.
The sighash flags are set in the signature itself. The user that signs an input sets eg SIGHASH_ALL when signing. This means that any changes among the outputs will render the signature invalid.
More in my book Grokking Bitcoin:
I’ve been oversharing lately but nostr:npub1cj8znuztfqkvq89pl8hceph0svvvqk0qay6nydgk9uyq7fhpfsgsqwrz4u picked these wildflowers for me and nostr is where I share whatever the hell I want so ENJOY THE BEAUTY! 
Nice! The orange dotted thingy on the right is in our yard! I think they call it "brandgul lilja" (roughly firey yellow lily) here.
I continue to make my home network even more complicated. The cool thing about having dedicated hardware for each function (modem, router, Wi-Fi) is that I'm now at the point where I can add arbitrary Wi-Fi access points as nodes to my mesh network and my client devices seamlessly switch between them while still automatically being protected by the DIY VPN I described in this article.
https://blog.lopp.net/how-to-protect-your-home-network-with-a-gigabit-vpn/
I really like your article! Isn't a drawback of running your own VPN server that the size of your anonymity set decreases to 1? If twitter knows you're behind 1.2.3.4, then they know all traffic from that ip is yours. They can sell/share/leak that info to anyone.
Isn't that a good reason to use Mullvad or other shared VPNs?
Bitcoin Core question:
Am I missing something here, or?
There is no longer a static example bitcoin.conf, so you have to generate it dynamically using a script (contrib/devtools/gen-bitcoin-conf.sh), but that script is not part of the binary distribution? (right?)
And there isn't documentation listing the meaning of all the configuration options to put into the file (which is what you get by running the above script, I believe)? (maybe I'm wrong? my searching is drawing a blank). As an example of that, see this:
https://github.com/MrChrisJ/fullnode/blob/master/Setup_Guides/bitcoin.conf
.. but that's very old, and obv it's better to be able to create your own.
It used to be the case a long time ago that running bitcoind would autogenerate a bitcoin.conf, but that's no longer true either.
How does someone running bitcoind from the binary distribution, figure out how to set config options?
You can figure out a lot from running:
bitcoind --help
But I'm not sure that answers your questions, because I guess you already knew the --help flag.
How do I setup NIP-57 for receiving zaps? I run LNbits on top of a Core Lightning node. I'd expect there's some LNbits extension for this, but can't find any.
10000 sats reward to the best (according to me) answer. #[0] #[1] #[2]
Thanks for the tip! However, I have no clue on how to enable zaps on my LNURL server (LNURLp on LNBits). Maybe you have some pointers? I run LNBits on top of a Core Lightning node. I'd expect some lnbits extension to do this for me, but can't find any.
There is one now: https://github.com/bitcoin/bitcoin/issues/27655
I don't think so. Maybe I should open one?
Thank you nostr:npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4c for your work on https://github.com/bitcoin/bitcoin/pull/26076
It's going to be an absolute life-saver in nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r when I do a workshop on using Bitcoin Core as an air-gapped signing device. Too bad the PR didn't make it into v25.0, so I'm afraid I'll have to do the workshop on master.
h > '
Sure enough, I downloaded bitcoin 0.8.6 and sure enough, I could double click to start it (though it fails due to missing legacy lib). It has mime type application/x-executable instead of application/x-sharedlib
This seems to be the issue: https://fostips.com/double-click-run-elf-ubuntu/
But seriously, why???
Turns out I can't start any program (not even my fav xeyes) by double clicking it. I must have messed something up, or debian locks it down for some reason.
It's downloaded from bitcoincore.org. Running ./bitcoin-qt from the command line works fine.
Debian 11. Unpacked the tar dot gz file and clicked myself into the bin folder and and double clicked the bitcoin-qt file.
Decided to try Bitcoin Core GUI. Kinda disappointed. This is what happens when I double-click bitcoin-qt:
So in order to run the GUI you have to open a *terminal* and run
$ bla/bla/bla/bitcoin-24.0.1/bin/bitcoin-qt
Is there some good reason why double-clicking it doesn't work?
Congrats Hampus! Well deserved. I'll topup that with a zap.
I'm severely uninterested in AI. I don't know why. Everyone else seem super jazzed about it.
What a wonderful day! Enjoy!
Glad someone found my spamming session useful!