Archived
Improve EteSync: add iOS link, improve description and change links #1490
Merged
tasn
merged 1 commits from 2019-11-22 05:26:07 +00:00
etesync into master
Labels
Clear labels
:mag:🤖 Search Engines
approved
dependencies
duplicate
feedback wanted
high priority
I2P
iOS
low priority
OS
Self-contained networks
Social media
stale
streaming
todo
Tor
WIP
wontfix
XMPP
[m]
₿ cryptocurrency
ℹ️ help wanted
↔️ file sharing
⚙️ web extensions
✨ enhancement
❌ software removal
💬 discussion
🤖 Android
🐛 bug
💢 conflicting
📝 correction
🆘 critical
📧 email
🔒 file encryption
📁 file storage
🦊 Firefox
💻 hardware
🌐 hosting
🏠 housekeeping
🔐 password managers
🧰 productivity tools
🔎 research required
🌐 Social News Aggregators
🆕 software suggestion
👥 team chat
🔒 VPN
🌐 website issue
🚫 Windows
👁️ browsers
🖊️ digital notebooks
🗄️ DNS
🗨️ instant messaging (im)
🇦🇶 translations
approved, waiting for a PR
Pull requests that update a dependency file
The Invisible Internet Project (I2P)
Operating Systems
A label for stalebot if it gets added
Anything related to media streaming.
Anything covering the Tor network
active work in progress, do not merge or PR (yet)!
Issues or bugs that will not be fixed and/or do not have significant impact on the project.
Extensible Messaging and Presence Protocol
Matrix protocol
Browser Extension related issues
Correction of content on the website
Firefox & forks, about:config etc.
Anything primarily related to site cleanup.
Virtual Private Network
*Technical* issues with the website.
Domain Name System
Anything covering a translated version of the site
No labels
Milestone
No items
No Milestone
No due date set.
Dependencies
No dependencies set.
Reference: privacyguides/privacytools.io#1490
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.
The dav bridge install instructions will soon be moved so better to
use the new links now already (for now, they are just a redirect).
Description
As the commit message says it improves the EteSync entry by adding a link to the new iOS app, improving the description and changing the soon to be deprecated DAV installation instructions links.
Check List
I have read and understand the contributing guidelines.
The project is Free Libre and/or Open Source Software
Netlify preview for the mainly edited page: https://deploy-preview-1490--privacytools-io.netlify.com/software/calendar-contacts/
Code repository of the project (if applicable):
The project is already on privacy-tools, though anyhow, here's the source code: https://github.com/etesync/
Deploy preview for privacytools-io ready!
Built with commit
99331c9c0dhttps://deploy-preview-1490--privacytools-io.netlify.com
LGTM 👍🏼
I am not happy with this PR.
How does journaled change to privacy-respecting?
I think this looks a bit clumsy.
What are the CalDAV/CardDAV bridges?
I think there is a conflict with the ease of use criteria.
Thanks or your feedback.
Journaled was the old language we used to use, we stopped using it a while ago. The current language from the website is: "Secure, end-to-end encrypted, and privacy respecting sync for your contacts, calendars and tasks.", so it was just adjusted accordingly.
I agree, a second attempt below:
Fair enough, I agree it's still not clear, but before it looked as if DAV was required for all platforms instead of just the desktop.
Could you please elaborate? Not sure I follow.
Second attempt at writing a description:
EteSync is a secure, end-to-end encrypted, and privacy-respecting cloud backup and synchronization software for your personal information (e.g. contacts and calendars). There are native clients for Android, iOS, and the web, and a CalDAV/CardDAV bridge for integration with DAV clients. It costs $24 per year to use, or you can host the server yourself for free.
There's CONTRIBUTING.md that states this under Software Criteria:
@Mikaela
Also, for Nextcloud on the same page, we already mention "CalDAV and contacts sync via CardDAV". (I don't have experience with CalDAV/CardDAV, but if this is an ease-of-use issue, then we should also reword/remove that part from the Nextcloud entry.)
Thanks for the clarification @djoate. I misunderstood @Mikaela, and didn't realise the point was about the bridge comment.
As you said, it's also used in the above with NextCloud. I can maybe rephrase that part to "and an adapter layer for most desktop clients.". How would that sound?
Thanks for taking the time to review this.
@Mikaela, any thoughts on the above?
Thanks again for taking the time to review this.
I have lost my train of thought during this time, but I am fine with the second description if you commit it.
I cannot promise when I will be able to look into this for the next time though.
Done, thanks for your comment.
Thanks a lot everyone.