http://ngdk7ocdzmz5kzsysa3om6du7ycj2evxp2f2olfkyq37htx3gllwp2yd.onion fixes this

Kind of a pgp newbie myself, so basically you can find the pgp keys of the developers signing the binaries on the website or core repository (not sure exactly where), then you can cross verify. Many devs have their key fingerprint in github profiles, slides of talks in yt videos, meeting them in person. We can also exchange our key lists here to cross check if we have the same keys, I guess that increases the probability they are legit and we didn't get served wrong keys by the website. Best is probably to verify keys in person with someone in the web of trust that signed other developers keys so there is a chain of signatures between you and the actual devs. Meetups might be a good place to start this.

See the release notes section https://bitcoincore.org/en/releases/30.0/

Running Core V30

When NWC?

This really is a game changer for conference dinners

Wenn du die event ID teilst anstatt des primal links können andere Clients den Artikel nativ rendern

From a sender perspective UX is nice but to receive in a trustless way you basically need to run a full node

No the one I mean is already integrated, no need for any external code to use it. Can be enabled in the desktop GUI or via the CLI. Like you say, for NWC its best to run it as daemon on some server. https://github.com/spesmilo/electrum/tree/master/electrum/plugins/nwc