I am adding this idea scribble for discussion - would be great to aim for this with the v1.5 version:

To align the HTML-Website-Setup with the SSH-Setup the setup process of the RaspiBlitz would need a small refactoring.
The idea is to collect all user setup settings into one file up front - basically producing a raspiblitz.conf file and then the RaspiBlitz just runs thru its recovery/update process and installs everything.
This raspiblitz.conf gets either produced by that HTML-Website you setup thru the TOR-Browser or the thru Dialogs on the command line thru SSH. Some info (like the seed words) needs to get stored during the process and when the setup/recovery is finished it will get displayed to the user and deleted/shredded from the Raspiblitz.
And dont worry that WIFI option is just there as possible idea for the future. The button can stay empty.
I really like the idea of using the Tor browser as default.
There could be also an option (maybe instead of the wifi) to show a QR with a TorV3 address and pasted to the mobile Tor Browser for initialization.
The wifi process is tricky especially if using other boards. Some need extra drivers or lacking a wifi module, but they can be still set up securely via HDMI through Tor or SSH. Would need to test to show the status screen on HDMI for those.
Storing the seed words temporarily does increase the attack surface so best would be to avoid if possible by default. When setting up through SSH the seed could come straight from the LND terminal like now and only be stored ( temporarily ) in case of a HTML setup.
There could be also an option (maybe instead of the wifi) to show a QR with a TorV3 address and pasted to the mobile Tor Browser for initialization.
On the TOR screen behind the written onion-address there could ne a small "show as QR-Code"-Button (QR-Code icon) that will show the address as QR code .. so need to give it an extra button on the side.
The wifi process is tricky especially if using other boards. Some need extra drivers or lacking a wifi module, but they can be still set up securely via HDMI through Tor or SSH. Would need to test to show the status screen on HDMI for those.
Forget for the WiFi-Option for now - having TOR & SSH is the next goal. For non-LCD setups we can leave it as now - that you find the IP of your raspiblitz manually and login with the standard password raspiblitz (like the the RaspberryPi does) - I dont think a HDMI info is needed.
Storing the seed words temporarily does increase the attack surface so best would be to avoid if possible by default. When setting up through SSH the seed could come straight from the LND terminal like now and only be stored ( temporarily ) in case of a HTML setup.
Maybe to avoid having the the seed words stored on disk they can be stored in memory. That means that the creation of the LND wallet during setup has to be after the final reboot. We have to see what works best here.
@rootzoll regarding vanity addresses https://opensource.com/article/19/8/how-create-vanity-tor-onion-address - according to the table I would say 4 characters is fine.. 5 ("1 minute") might be acceptable... would give "blitz".. :-D
./mkp224o -B -s -d onions blitz raspi
set workdir: onions/
sorting filters... done.
filters:
blitz
raspi
in total, 2 filters
using 4 threads
>calc/sec:286416.398617, succ/sec:0.000000, rest/sec:39.957645, elapsed:0.100106sec
raspii5nyods2sidnyf7oyz7567gbrtxhnwx4mrb5j6m3dd2j6mwanid.onion
>calc/sec:578978.351925, succ/sec:0.099055, rest/sec:0.099055, elapsed:10.195461sec
>calc/sec:605969.691837, succ/sec:0.000000, rest/sec:0.000000, elapsed:20.114901sec
blitzx6p64zjajzbc5z2blx74t5hn3ykzcw25fgbvdpfhvenbikir7ad.onion
>calc/sec:594269.723662, succ/sec:0.099374, rest/sec:0.099374, elapsed:30.177941sec
Edit: This is on a Raspiberry Pi 3
With having @frennkie prepared the web interface basics for v1.6 release ... working then for v1.7 on coming closer to the goal of this issue seems possible ... so moving to v1.7 release.
BTW on last discussion we were in favor of not neededing an "extra password" when connecting thru TOR to a RaspiBlitz waiting for setup - the address is "code" enough and makes sure that you really talk to this node. But IF a second user opens that setup page (can be simulated with making a request from a second TOR browser) the page should say "setup in progress - if this is not you then power down RaspiBlitz and make a fresh sd card".
About a future WIFI option on that start screen see: https://github.com/rootzoll/raspiblitz/issues/1432
Most helpful comment
On the TOR screen behind the written onion-address there could ne a small "show as QR-Code"-Button (QR-Code icon) that will show the address as QR code .. so need to give it an extra button on the side.
Forget for the WiFi-Option for now - having TOR & SSH is the next goal. For non-LCD setups we can leave it as now - that you find the IP of your raspiblitz manually and login with the standard password
raspiblitz(like the the RaspberryPi does) - I dont think a HDMI info is needed.Maybe to avoid having the the seed words stored on disk they can be stored in memory. That means that the creation of the LND wallet during setup has to be after the final reboot. We have to see what works best here.