Use const

In D10992#318515, @inka wrote:

This code is quite complex in the case you were not able to test - when we connect to a different keyserver, and even mo so when we connect to a couple of keyservers. I can see that it would be hard to test now, but it would be great if you could create a linear task describing how this should be tested once it's possible, and set it as blocked by appropriate tasks.

Rebase

Revert unnecessary changes

Check regexes and refactor

Use join data

Clear the timeout on unmount

Clear the timeout on unmount

Fix a couple of bugs

Fix Flow

Rebase

Rebase

Use auth headers

We will patch the specialRole field back in to minimally encoded RawThreadInfos for future clients (where shouldMinimallyEncodePermissions AND includeSpecialRoleFieldInRoles are true).

With the new approach we no longer need this

Simplify the approach

In D10931#315340, @ashoat wrote:

I wonder if there's a more generic way we could handle this... I could imagine defining this similar to keyserver actions, where "Comm service actions" are defined as functions that take functions as input. The inner function would be something like callAuthenticatedCommService, and it would allow the "Comm service action" to abstract away the details of authentication. Then we would have a hook (eg. useCommServiceCall) that takes the "Comm service action" function as input, and binds in the callAuthenticatedCommService function.

It would be helpful if you linked a Linear task describing why we need to change that or explain what the plan is. I guess we're going to introduce a new, similar hook, but I can't be sure.

Await more promises at once