privacyguides/privacytools.io
Archived
1
0
Fork 0
Code Issues 304 Pull Requests 47 Activity

Remove Riot beta warning badge #1004

Closed
Perelandra0x309 wants to merge 1 commits from PR-IM-Riot-Beta into master
pull from: PR-IM-Riot-Beta
merge into: privacyguides:master
Conversation 9 Commits 1 Files Changed 1 +1 -1
Perelandra0x309 commented 2019-06-22 12:19:03 +00:00 (Migrated from github.com)
Copy Link

Description

Resolves: #none

Riot is no longer considered in beta:
https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation

We are very excited to announce the first fully stable release of the Matrix protocol and specification across all APIs - as well as the Synapse 1.0 reference implementation which implements the full Matrix 1.0 API surface.

This means that after just over 5 years since the initial work on Matrix began, we are proud to have finally exited beta!! This is the conclusion of the work which we announced at FOSDEM 2019 when we cut the first stable release of the Server-Server API and began the Synapse 0.99 release series in anticipation of releasing a 1.0.

## Description Resolves: #none Riot is no longer considered in beta: https://matrix.org/blog/2019/06/11/introducing-matrix-1-0-and-the-matrix-org-foundation > We are very excited to announce the first fully stable release of the Matrix protocol and specification across all APIs - as well as the Synapse 1.0 reference implementation which implements the full Matrix 1.0 API surface. > > This means that after just over 5 years since the initial work on Matrix began, we are proud to have finally exited beta!! This is the conclusion of the work which we announced at FOSDEM 2019 when we cut the first stable release of the Server-Server API and began the Synapse 0.99 release series in anticipation of releasing a 1.0.
netlify[bot] commented 2019-06-22 12:19:43 +00:00 (Migrated from github.com)
Copy Link

Deploy preview for privacytools-io ready!

Built with commit c925e97368

https://deploy-preview-1004--privacytools-io.netlify.com

Deploy preview for *privacytools-io* ready! Built with commit c925e973682530b192c2fd45248a9560eeabd258 https://deploy-preview-1004--privacytools-io.netlify.com
ghost commented 2019-06-22 12:39:52 +00:00 (Migrated from github.com)
Copy Link

While Riot.im is the reference client implementation it is neither the Matrix specification or the reference server implementation (Synapse).

~~While Riot.im is the reference client implementation it is neither the Matrix specification or the reference server implementation (Synapse).~~
ghost commented 2019-06-22 12:45:04 +00:00 (Migrated from github.com)
Copy Link

While Riot.im is the reference client implementation it is neither the Matrix specification or the reference server implementation (Synapse).

Maybe I should have read things a bit more closely. From the quoted part my previous comment would have been correct but looking at the link there's a link to https://medium.com/@RiotChat/the-big-1-0-68fa7c6050be saying Riot.im is out of beta (back in February) so I guess the badge should be removed after all.

> While Riot.im is the reference client implementation it is neither the Matrix specification or the reference server implementation (Synapse). Maybe I should have read things a bit more closely. From the quoted part my previous comment would have been correct but looking at the link there's a link to https://medium.com/@RiotChat/the-big-1-0-68fa7c6050be saying Riot.im is out of beta (back in February) so I guess the badge should be removed after all.
Perelandra0x309 commented 2019-06-22 14:19:16 +00:00 (Migrated from github.com)
Copy Link

Yes it would have been more correct for me to write Riot/Matrix is out of beta, considering the entire system. Riot itself has been out of beta for a while but Matrix not until recently.

Yes it would have been more correct for me to write Riot/Matrix is out of beta, considering the entire system. Riot itself has been out of beta for a while but Matrix not until recently.
Mikaela (Migrated from github.com) requested changes 2019-06-22 15:50:30 +00:00
Mikaela (Migrated from github.com) left a comment

I don't think this can be merged until https://github.com/vector-im/riot-web/issues/6779 is resolved as the warning refers to it.

I don't think this can be merged until https://github.com/vector-im/riot-web/issues/6779 is resolved as the warning refers to it.
ghost commented 2019-06-22 17:06:04 +00:00 (Migrated from github.com)
Copy Link

I don't think this can be merged until vector-im/riot-web#6779 is resolved as the warning refers to it.

Wouldn't that more correctly be needing an experimental badge instead?

> I don't think this can be merged until [vector-im/riot-web#6779](https://github.com/vector-im/riot-web/issues/6779) is resolved as the warning refers to it. Wouldn't that more correctly be needing an experimental badge instead?
Mikaela commented 2019-06-22 20:24:02 +00:00 (Migrated from github.com)
Copy Link

Sure, I would be fine with changing it to experimental even if it would hopefully soon be removed if the Matrix/Riot people aren't being too optimistic.

Sure, I would be fine with changing it to experimental even if it would hopefully soon be removed if the Matrix/Riot people aren't being too optimistic.
erciccione commented 2019-06-23 10:15:06 +00:00 (Migrated from github.com)
Copy Link

I would still leave the warning. As @Mikaela pointed out, many privacy related concerns are still unresolved.

I would still leave the warning. As @Mikaela pointed out, many privacy related concerns are still unresolved.
Perelandra0x309 commented 2019-06-23 11:33:22 +00:00 (Migrated from github.com)
Copy Link

Here's a good update on what the developer considers outstanding issues.
https://github.com/privacytoolsIO/privacytools.io/pull/562#issuecomment-502681069

Perhaps it is best to change the badge text and tooltip to something besides beta, which at this point is not correct. It could be a "Warning" and a tooltip about E2EE having these issues from the above comment:

E2E search (which is almost done, as of last week)

This seems like just an ease of use issue, not a privacy concern.

Cross-signing to simplify verification (demoable as of last week)

Another ease of use issue which will be nice to have.

Support for non-E2E clients via a shim (working as of a few weeks ago).

This is a new feature which allows some intermediate server to act as the E2E endpoint that a non E2E enable client connects to.

Metadata is stored on servers. Fixing this is a long term project.

This is worth mentioning as a warning.

We need to better at helping users understand where their contact data goes, and hash contact data during lookups

Another thing worth mentioning.

Here's a good update on what the developer considers outstanding issues. https://github.com/privacytoolsIO/privacytools.io/pull/562#issuecomment-502681069 Perhaps it is best to change the badge text and tooltip to something besides beta, which at this point is not correct. It could be a "Warning" and a tooltip about E2EE having these issues from the above comment: > E2E search (which is almost done, as of last week) This seems like just an ease of use issue, not a privacy concern. > Cross-signing to simplify verification (demoable as of last week) Another ease of use issue which will be nice to have. > Support for non-E2E clients via a shim (working as of a few weeks ago). This is a new feature which allows some intermediate server to act as the E2E endpoint that a non E2E enable client connects to. > Metadata is stored on servers. Fixing this is a long term project. This is worth mentioning as a warning. > We need to better at helping users understand where their contact data goes, and hash contact data during lookups Another thing worth mentioning.
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Mikaela
Labels
Clear labels
🔍🤖 Search Engines
approved
approved, waiting for a PR
dependencies
Pull requests that update a dependency file
duplicate
feedback wanted
high priority
I2P
The Invisible Internet Project (I2P)
iOS
low priority
OS
Operating Systems
Self-contained networks
Social media
stale
A label for stalebot if it gets added
streaming
Anything related to media streaming.
todo
Tor
Anything covering the Tor network
WIP
active work in progress, do not merge or PR (yet)!
wontfix
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
XMPP
Extensible Messaging and Presence Protocol
[m]
Matrix protocol
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
Browser Extension related issues
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
Correction of content on the website
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
Firefox & forks, about:config etc.
💻 hardware
🌐 hosting
🏠 housekeeping
Anything primarily related to site cleanup.
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
Virtual Private Network
🌐 website issue
*Technical* issues with the website.
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
Domain Name System
🗨️ instant messaging (im)
🇦🇶 translations
Anything covering a translated version of the site
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
jonah
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: privacyguides/privacytools.io#1004
No description provided.
Delete Branch "PR-IM-Riot-Beta"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?