You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
Matrix the protocol and Synapse the reference server implementation came out of beta recently but if we want to be technically correct the recommendation is for Riot.im specifically and then we should have removed the beta badge back in February and that just seems wrong when the protocol spec and reference server implementation isn't out of beta.
The text was updated successfully, but these errors were encountered:
Nice idea, a green badge for servers and a red one for clients will make File Sharing section more clear (with only Firefox Send with a red badge). Instant Messaging section will be improved, dividing green decentralized services from red centralized services.
IMO the tags should represent the full stack of software a tool is using. So because Synapse is the only server-side software for that particular application and was in beta, and because the protocol the client is built on was in beta, the tag should say beta.
I'm not even sure if we should list "beta" at all and stick with "experimental" for tools we have concerns about: #1007
https://github.com/privacytoolsIO/privacytools.io/pull/1004 made me think about if we should have some way to telling the difference between protocol, client, and server wrt. badges.
Matrix the protocol and Synapse the reference server implementation came out of beta recently but if we want to be technically correct the recommendation is for Riot.im specifically and then we should have removed the beta badge back in February and that just seems wrong when the protocol spec and reference server implementation isn't out of beta.
The text was updated successfully, but these errors were encountered: