we need to rethink how we are using this state param. in this diff, we have no way of setting it back to true

for now -- this param should just be dropped. We get the goal of having registrations disabled if server is down by failing to authenticate alias availability.

imo action here is

1. In a separate diff, remove isAliasServerOnline from everywhere in the app
2. Rebase this diff onto that one, not including any new use of isAliasServerOnline

We don't really want to throw errors in this loop ... this just prints errors to the dev console.

It's probably easiest to simply lock the UI of the Alias.js screen until we get a good response from the server, similar to the way we lock the UI of Send.js during a chronik error.

We can't expect the user to see errors in the dev console, but we don't want them to be able to interact with the Alias screen if the server is down.

We don't want to lock the UI if there is no way for it to become unlocked

Looking at this functionality, imo the best option for handling errors is

1. Error notification
2. Disable ability to register aliases
3. Instead of displaying registered aliases of address, display some kind of warning that server contact failed

As long as alias registration txs are disabled when the server is unavailable, keeping the UI unlocked is okay.

won't this just become true again if the input changes? Need to make the alias registration button also dependent on server errors, not just valid input.

We don't need this state field. disabled prop of the button should depend on aliasServerError state, disabled if aliasServerError is not ''

Going forward -- we should probably run this useEffect block every time a new block is found and not just on page load. That way we would get confirmed alias registrations in real time. But, we don't need that for launching.

Also an option to implement a websocket in alias-server and have Cashtab subscribe directly to the websocket.

this is not the correct approach here. the button should be disabled or not based on aliasServerError state field

This works when aliasServerError is false. However this condition is not picking up when aliasServerError is a string.

To resolve issue from my last comment (if no response from alias server, registration button is still not disabled if alias input is valid) -- need to make this check more specific