e11sync

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | LICENSE

commit 55015a045603dfba3cb9d952a42799e4e95ce1dd (tree)
parent 0f9bcba307d86f8383e2f28270d82c5f7369e362
Author: Motiejus Jakštys <motiejus@jakstys.lt>
Date:   Thu, 25 Jan 2024 16:47:17 +0200

decentralization

Diffstat:
Mapp/signup/templates/signup/index.html | 19+++++++++----------
1 file changed, 9 insertions(+), 10 deletions(-)

diff --git a/app/signup/templates/signup/index.html b/app/signup/templates/signup/index.html @@ -323,26 +323,25 @@ </div> </article> - {% comment %} <article> <input type="checkbox" id="ac-62" checked="checked" /> <label for="ac-62"><h2>Isn’t Syncthing all about decentralization?</h2></label> <div> - Here is a comment from Syncthing Foundation about 11sync.net: + Yes, Syncthing indeed champions decentralization, and we fully embrace + it. At 11sync.net, our role is to complement this decentralized system by + offering a resilient peer that also does back-ups for you (separately + from <a + href="https://docs.syncthing.net/users/versioning.html">versioning</a>). - <blockquote> There is also a feeling that the centralisation of - Syncthing services contradicts the project goals of individuals - running decentralised syncing; we (as the project/foundation) will - likely not recommend your service as best practice.</blockquote> - - <p>We understand and value the position of Syncthing Foundation. Our - goal is to offer a resilient peer to those who need it. + <p>For those who are adept at handling their own backups or already + possess a reliable, always-on peer, 11sync.net might not be necessary. + We’re here to provide an additional layer of reliability and convenience + for those who need it. <div></div> </div> </article> - {% endcomment %} <article> <input type="checkbox" id="ac-65" checked="checked" />