Couple quick things about the current-state for folks reading this and planning to test:

I'd like to ask more folks to report or deny issues in low RAM environments, in my testing everything has worked well in containers with as little as 1GB of RAM... 2GB burstable probably best though for the initial LND sync... 4GB has been ok with a full (headless) linux operating system such as a VPS

RAM speed is also a factor, 2GB of DDR4 is like 4GB of DDR3 and so on...

Good call, it's biggest feature is that no networking setup is required at all since Nostr punches out. I actually recommend NOT using Tor ever, it'll just make your Lightning node unreliable.

It can really be either, but yea optimizing for routing is a different game.

That said, if you run a pub with a bunch of high quality channels it will route as any other LND instance would (and the Pub dashboard hidden in ShockWallet for administrators helps provide a little insight into what is routing without the command line)

Yes, this option is currently done by the env (see readme on github if you're unsure what an env is), but the wizard for start9 etc will make it graphical

Will add some tool tips around this, but it's fully automated currently in the wallet

When you connect to any Pub, whether its ours or your own, the wallet takes the CLINK noffer and enrolls it at a LNURL bridge. This makes the Lightning Address trustless when a payer also supports CLINK since its using nostr for comms instead of the bridge serving any unverifiable invoice (NIP-05 serves the clink offer directly in that case, regular LNURL is still trusted since it has to be translated)

Darth didn't mention this but I saw @k00b inquire about it on SNL

There's a trusted "custodial" credit mode for either Wallet or a Self-Hosted Pub:

If you use wallet in bootstrap mode it's using our Pub as a back-end, the next phase of this however is that when the balance is adequate the wallet will upgrade itself to a cloud node (or prompt you to connect your own) such that you can then invite your friends and family to it and get some ROI on hosting/channel costs.

With Lightning.Pub, bootstrap liquidity provider is enabled by default, but can be disabled via the env or in the forthcoming wizard.

This is similar to Phoenix's LSP service credits, the difference being is you're not locked in to us. You can re-point the liquidity provider to any other Lightning Pub, not just ours. This is currently modified via the env.

There's a roadmap for bootstrap to use Web-of-Trust to identify other Pub admins you know via Nostr and localize/decentralize any trust.

Our terms on bootstrap balances are that these are service credits consistent with CFPB guidance.

If you've already set up a Pub and want to keep it updated with latest fixes, the same one-liner used to deploy it can be added to cron for unattended upgrades.