Archived
Merge im, teamchat and video-voice into real-time-communication #1136
Merged
Mikaela
merged 8 commits from 2019-08-12 03:18:19 +00:00
real-time-communication into master
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#1136
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.
Resolves: #1078
Closes: #746
Preview: https://deploy-preview-1136--privacytools-io.netlify.com/software/real-time-communication/
Deploy preview for privacytools-io ready!
Built with commit
98bca69952https://deploy-preview-1136--privacytools-io.netlify.com
Commentary on why I did what I did
@@ -5,6 +5,7 @@ sass:style: compressedplugins:- jekyll-sitemap- jekyll-redirect-fromI think @JonahAragon said that he would do this with nginx which is more elegant, but I guess it won't hurt being here too as Nginx is going to take a preference and in case nginx got forgotten, the user wouldn't see that much of a difference.
Better icon suggestions?
@@ -0,0 +6,4 @@- /software/voip/- /software/teamchat/title: "Real-Time Communication"description: "Discover secure and private ways to communicate with others online without letting any third parties read your messages."I thought that this was the best applying description to them all together.
@@ -0,0 +11,4 @@{% include sections/instant-messenger.html %}<hr/>I wish to have some separator between the different sections, even if they are on the same page.
And I think this ordering makes the most sense as I think people are most often looking for instant messengers, then VoIP and team chat is a bit rarer scenario as I think that is mostly forced on people from whichever the team founder prefers.
Minor suggestions but otherwise lgtm!
What if we updated the title to "Real-Time Communication"?
"Real-Time Communication"?
@@ -0,0 +6,4 @@- /software/voip/- /software/teamchat/title: "Real-Time Communication"description: "Discover secure and private ways to communicate with others online without letting any third parties read your messages."That sounds good to me.
@@ -0,0 +11,4 @@{% include sections/instant-messenger.html %}<hr/>Yeah the breaks work well in my perspective.
Changed to Real-Time Communication as requested by @nitrohorse
I forget which issue but I thought @JonahAragon had a recommendation for this...
LGTM
I would rather do redirects with Nginx only I think, so as to not require too many Jekyll extensions on both the server and on local dev machines.
If we want, we could add an Nginx config file to this repo that would then be “include”d in the server config, so we can add redirects and other server-side configs here directly?
Oh nice, that sounds helpful 👍