(Author here.) Development has been paused for ~1y as I've been at work creating a vehicle to take this forward.
The protocol specifics (e.g. identifiers & types) aren't polished, because I focused on features in working code. Thanks for the feedback!
You can't have alias collisions; it checks whether the string you propose is acceptable & available :)
A sender's alias is (or will be) checked against their recorded aliases.
The reason why lack of E2EE in email is a serious problem is that email traverses at least two "federated" services, which are typically third parties with whom you have no intrinsic need for a relationship. A TMTP message passes through a single service which you explicitly joined.
I don't see how your feedback justifies "poorly thought out"; it's merely an unpolished preview.
The protocol specifics (e.g. identifiers & types) aren't polished, because I focused on features in working code. Thanks for the feedback!
You can't have alias collisions; it checks whether the string you propose is acceptable & available :)
A sender's alias is (or will be) checked against their recorded aliases.
The reason why lack of E2EE in email is a serious problem is that email traverses at least two "federated" services, which are typically third parties with whom you have no intrinsic need for a relationship. A TMTP message passes through a single service which you explicitly joined.
I don't see how your feedback justifies "poorly thought out"; it's merely an unpolished preview.