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
I am guessing Gosling will break support with the legacy Ricochet protocol. Should there be a URI change, for example, to "gosling:" or "refresh:" or something else? With likely breaking changes, it may even be time to rename the software. Once renamed, the new URI could be set accordingly.
The text was updated successfully, but these errors were encountered:
100% agree. Regardless of whether we change the name or not, the next v4 protocol (which will be a breaking change from v3) will use a different string to mitigate some user confusion.
I am guessing Gosling will break support with the legacy Ricochet protocol. Should there be a URI change, for example, to "gosling:" or "refresh:" or something else? With likely breaking changes, it may even be time to rename the software. Once renamed, the new URI could be set accordingly.
The text was updated successfully, but these errors were encountered: