Hello Zyga,
On Wed, 11 Jan 2023 at 17:50, Zygmunt Krynicki <me@xxxxxxxxx> wrote:
>
> Hey everyone!
>
> I have a question about the proosal:
>
> > * Only users with an EF account will be able to join any chat channel since
> > everyone needs to comply with the EF legal and IP frameworks.
>
> Does this mean that someone using another matrix server will be unable to join our channels without using an EF account explicitly?
That is correct. This channel will be like any other channel or
resource provided by EF. You need an EF account to participate.
A couple of remarks:
* The chat service will have SSO. This is one of the strength of
matrix vs other chat services (most of them only offer this feature
under paid packages).
* I am already testing the chat instance. I can participate in our
current libera.chat channel #oniroproject from the EF matrix testing
server.
All communications need to be covered by the EF legal and IP
frameworks so people affiliated to different organizations are covered
by it and they can share knowledge/information using their corporate
accounts among them and with non-affiliated individuals.
If there is a strong demand to communicate with external people, the
solution could be to keep using the existing channel at libera.chat,
in addition to the ones proposed. Participants will need to assume the
legal/IP risks associated with such practice. My recommendation is to
join EF as an individual in order to actively participate.
Sadly that would not be usable for people already in this ecosystem. We have discussed this in the technical meetings before and I am sad to hear that our agreement at that point was changed. I will explain in more detail the issue with this approach (at least for me).
The concern stems from the fact that none of the clients I know (especially none of the official clients) support multiple accounts and all of us already have accounts on
matrix.org or other synapse instances that we use regularly for other purposes too. For me personally, given that there is no "multiple users" support in the clients, I would have to constantly sign out and sign in based on when I want to discuss with the Oniro team. That is not only an obvious overhead coupled with the usability issue of missing events from the logged-out instance, but it is also a security overhead as new crypto keys will be generated and each new client (login) will have to get validated with each login. I propose to evaluate this from the perspective of a person who doesn't use the Eclipse account as the one and only identity he/she has in the ecosystem. I suspect that this is the case for the majority of us - but feel free to tell me otherwise.
I'm pretty sure that Zyga's concern is along the same lines but I'll let him expand.
Cheers,
Andrei
