> when highlighting over the icons on the left it would be cool to have a hover explaining what you're potentially clicking on
Yes

> Adding different themes so everyone can customize their own page client side with different colors or very simple code like the matrix rain or a bash shell flashing.
Yes, but not a priority. We need a good looking default theme first

> was thinking it would be cool if I could write @Wate and your name would come up and i could complete it with tab?
Yes, do it before end of this month

> Private group chat would be exceptional. 
Yes, but it's challenging from both technical perspective and design perspective. I need to address other common issues first.

> within group chats it would be excellent to have a voice chat function akin to discord or perhaps impervious and their P2P functionality.
Yes, also technically challenging

> communities that can be created or are pre-made among trending topics/subjects so discussion can hopefully be healthy and in one spot
Yes, but instead of "communities", I am thinking about a different design that solves the problem of "topic oriented chat"

> maybe the ability to add emoji responses (nostr ones of course) to peoples sentences?
Yes, once we have a better editor implementation! Maybe next month?

> perhaps the function to /gif or /tenor to bring up easy gifs for more memeing (option to be turned off per channel basis of course too)
Pretty much the same as Emoji feature

> screen sharing in time.
Technically challenging, but yes!

> integration with private channels/groups on 0xchat (? no idea how feasible this is or if it's even likely to happen)
The private groups features implemented by 0xChat, Coracle and Amthyst works. But it is more complex than I would like it to be. I am still weighing it.

Interoperability means limited flexibility. Nostr clients' interoperability does not need to happen at every level in every NIP. I believe it's valuable to have unique features implemented by only 1 client.

People naively think that as long as clients produce the same data format (event), they interop. I believe this is total ignorance of the importance of design.

Some data format only makes sense for certain design. If the design goal is different, the data format could be different.

The design goal of Blowater is, from most important to least
1. Having a great chat software for both individuals and organizations.
  a. chat is important
  b. social media is not, that's why Blowater does not implement follow-list
2. Secure and Privacy
  a. user opt-in security by doing DM
  b. but it can not sacrifiace user friendliness (No.1)
  c. therefore, it will never shoot for extreme secure and private use cases
3. Very cheap to operate servers and great admin features
  a. we have to implement our own relay
  b. strfry is fast, but not so friendly for non-tech operators
  c. blowater's relay implementation will be as easy as creating a Discord server
  d. performance is less important
4. Interop with other clients
  a. if not harm other 3