Missing certificates from community owner

[kingalg]

Version: 2.0.0-alpha.12

System: it happened on Mac, but it may not be system related

Below you will find all steps that I did on this community:

1. Owner created on Windows
2. Linux joined from link generated on Windows with unique user lin2009
3. Owner was turned off
4. Link was send from Linux to Mac
5. Mac joined with unique user mac2009
6. Linux user lin2009 left community
7. Link was send from Mac to Linux
8. Linux joined with already existing user mac2009
9. Everything synced fine, both users were flagged as duplicated
10. Owner on Windows was turned on and on general everyone get message that users joined

11. Both mac2009 on Linux and Mac left community 12. Owner on Windows send new invitation link to Mac 13. Mac joined with unique user test2009

Issues:

1. System messages are flagged as unregisteres.
2. Messages are not fully replicated.
   Below you can find views from test2009 and from community owner:

3. Channel name is not visible on test2009 (for all previous user it was visible)

Additional info: as per @EmiM this is an issue with missing certificates.

[EmiM]

To clarify: user saw messages before all certificates has been replicated. Because Quiet Bot ("System messages") is just an owner in disguise, its messages were flagged as 'unregistered' for a moment.
Similar thing with community name not being visible - community metadata (which contains community name) needs to be replicated by user first. We were discussing on displaying community name placeholder (something like "unknown", tbd) until real name arrives.

[kingalg]

@EmiM strange thing is that everything else (like community name in left top cornerr) was in place. Maybe I should have add this detail.
So far I wasn't able to reproduce this on any system even following exactly the same steps with the same systems.

[vinkabuki]

Except system messages being displayed as unregistered - everything else is an inherent part of the new joining design and the only thing we can do is to explain it to users @kingalg @EmiM @holmesworcester
Also as Emi said - we'll add placeholder with 'unknown' community name for a little better UX.

[holmesworcester]

When is community name unknown?

[vinkabuki]

When you do not replicate metadata for some reason

[holmesworcester]

Maybe it should be ... instead of unknown. Or something less buggy looking.

[Kacper-RF]

#1875

[kingalg]

Version: 2.0.1-alpha.7

I don't have a screenshot because registration and getting certificates was rather fast but I saw "..." as a name of community. Also other problems didn't reoccur so I consider it fixed.