Is there anyone I can talk to regarding Thalassa and Seaport

[miner-ops]

At my company Miner Labs, I have set out to create a microservice distributed infrastructure.
I have been working on a ton of technologies and use a modified version of Seaport as the base registry system.

There are a couple of major issues I have experienced in production, and would love to know if Thalassa can help. I cannot justify the time investment to switching right now, unless I talk to someone.

Some issues:

1. Case: Web1 and Web2 are registered with Seaport. Seaport goes down. Web1 goes down. Seaport Comes back up. Web2 reconnects to seaport, and tells seaport that Web1 and Web2 are still up.
   Seaport does not bother to check Web1 for validity.
   1a. I wrote a sort of Mark and Sweep collector for services, but due to the distributed nature of this system, and without going into too much depth, it sometimes sends the system into an unstable state, where everyone starts to register and deregister constantly.
2. Seaport Peers, dont always work super well, does Thalassa solve this.

Also if you could tell me what issues you were solving with Seaport, by creating Thalassa and your intention behind it, that would be great.

Sincerely,
Michael Hernandez

And thanks for the great work in distributed services.

[miner-ops]

Just realized I posted as miner-ops user. My correct github name is
@miketheprogrammer