Chris Guida

@MattDHill I don't remember, I believe I tried one .onion and it was also down

Right, the difference is that the .locals don't come back up after the crash loop is resolved.

Would maybe be cool to have services in the list be expandible/collapsible with more/less details

Yes, I think most UIs just stack them up somehow

Perhaps we should turn this into 2 tickets: "test building embassy-os on x86", "make a build guide for x86"?

I'm guessing embassy-os will know which architecture to request based on where it's running

We actually had something like this but it was sort of a mess server side. Should probably reimplement though, this is definitely useful data to have. Are you proposing this...

@ProofOfKeags does that just work for basic auth things like Spark? Or are there other uses?

Can you list some use cases?

Wouldn't it be pretty useless to hook up a hw wallet to the embassy? You'd want it connected to the client device, not the server, right?