uksys144

I've read an introduction blog post ("What's wrong with instant communication"). While I agree with points on instant messaging, impermanence and depth of communication etc... The part regarding e-mail is quite debatable. Hence, the app looks like ersatz e-mail with randomized delivery :-/

One person can keep a secret, but not two.

In my opinion, the idea of limiting access for a group of friends looks controversial. Your friends, relatives have not signed up to not redistribute the content to other folks/friends. Taking that into consideration, it is reasonable to edit out all private content and then make the posts public.

The other rationale for public posting is that hidden, close circle posts do not bring you more friends or co-thinkers. Hidden posting is not about being social, IMO.

However, in case of closed, invite-only community with some kind of regulation enforced or in case of company staff bounded with NDA, your approach sounds reasonable. Maybe your project should target corporate segment. All that crypto ciher gears, preventing data leaks, would be much more relevant there.

What decent reviews. So precise. However, I should note there is lack of reviews for MS Windows Servers (there is for server 2003 only).

Author should pay attention to server edition of recent (8,10,11) versions of MS Windows. There are not such silly advertisement and are much less annoying garbage apps and other spyware. I try to switch to server editions as the lesser evil where possible.

This dynamic content is normally a part of a multipart MIME message. Should be opened with an external viewer in case the e-mail client program can not display it inline.

Regarding the MS teams, plain text messaging covers a huge part of use cases, provided the third party client implementation warns the user about limited rendering support, allowing fallback to genuine MS client.