Archived
instant-messenger: change Riot privacy conern link to #1049 #1050
Closed
Mikaela wants to merge 3 commits from
riot-tracking into master
pull from: riot-tracking
merge into: :master
:master
:dependabot/bundler/nokogiri-1.13.6
:dependabot/bundler/addressable-2.8.0
:freddy-m-patch-3
:pr-add_RemoveMyPhone_sponsor
:pr-browser_cleanup_1257_1328_1430
:freddy-m-patch-2
:freddy-m-patch-1
:pr-vpn_hated_one_video
:cdn
:update-nitrohorse-image
:promote-metager-to-card
:hardware
:pr-add_azirevpn
:pr-add_mailfence
:shop
:1673
:pr/1658
:i18n-simple
:sponsorship-edits-nov2019
:i18n
:ipfs
:blacklight447-ptio-patch-3
:blog
:remove-windows-icons
:pr/1147
:i18n-testing
:add-beautify
No Reviewers
Dismiss Review
Are you sure you want to dismiss this review?
Labels
Clear labels
:mag:🤖 Search Engines
I2P
OS
Self-contained networks
Social media
Tor
WIP
XMPP
[m]
approved
dependencies
duplicate
feedback wanted
high priority
iOS
low priority
stale
streaming
todo
wontfix
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
🆕 software suggestion
🆘 critical
🇦🇶 translations
🌐 Social News Aggregators
🌐 hosting
🌐 website issue
🏠 housekeeping
🐛 bug
👁️ browsers
👥 team chat
💢 conflicting
💬 discussion
💻 hardware
📁 file storage
📝 correction
📧 email
🔎 research required
🔐 password managers
🔒 VPN
🔒 file encryption
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🚫 Windows
🤖 Android
🦊 Firefox
🧰 productivity tools
The Invisible Internet Project (I2P)
Operating Systems
Anything covering the Tor network
active work in progress, do not merge or PR (yet)!
Extensible Messaging and Presence Protocol
Matrix protocol
approved, waiting for a PR
Pull requests that update a dependency file
A label for stalebot if it gets added
Anything related to media streaming.
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
Browser Extension related issues
Anything covering a translated version of the site
*Technical* issues with the website.
Anything primarily related to site cleanup.
Correction of content on the website
Virtual Private Network
Domain Name System
Firefox & forks, about:config etc.
No labels
Milestone
No items
No Milestone
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1050
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Deploy preview for privacytools-io ready!
Built with commit
eb0221b554https://deploy-preview-1050--privacytools-io.netlify.com
TODO: change this part to something actually reflecting the issue, like the most important problems. I think that would be in general metadata like with Wire and the removed messages never getting removed.
I tend to be in favour of this PR and against #1047. But i have to catch up on the discussions before giving a fully informed opinion.
I have removed the description from this PR and the first commit as this appears to be more popular PR and in another commit I fixed the tooltip text that was leftover from the old link.
My personal preference would still be delisting Riot until they have gotten their privacy issues resolved and then listing them again.
I agree. Based on the issues listed in https://github.com/privacytoolsIO/privacytools.io/issues/1049 I think we should remove Riot for now. We could also bump it to the "Worth Mentioning" section with the "privacy conerns" tooltip warning users but that wouldn’t be my first choice.
You are missing a closing element on your second anchor link:
<a href="https://github.com/privacytoolsIO/privacytools.io/issues/1049"<span
Do I understand correctly that you are requesting changes to block merging of this and will be giving an approving review to https://github.com/privacytoolsIO/privacytools.io/pull/1047 ?
I disagree as Riot is not an instant messenger for people, but teams, and would be blocked by https://github.com/privacytoolsIO/privacytools.io/issues/1065.
Could you clarify what is wrong in the file and what should it be instead? I looked at it a few times, but I don't spot the issue. I find the code too confusing :(
Yeah 👍🏼 I’ll make an approving review of 1047.
Ah I see, that makes sense.
I think it's actually an inherited error from the existing version, but the html should be this:
<a href="https://github.com/privacytoolsIO/privacytools.io/issues/1049\"><spanAdd a ">" before the "<span" so it is valid HTML.
I would be fine merging this immediately if the syntax issues mentioned here were fixed, although I'm equally fine with not fixing this if we were to merge #1047 instead.