From 8c038558e4491ed1952486deabe95da412bc8b12 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Oskar=20Thor=C3=A9n?= Date: Thu, 27 Aug 2020 10:51:38 +0800 Subject: [PATCH] Update vac overview with fixed MVDS link --- _posts/2019-08-02-vac-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2019-08-02-vac-overview.md b/_posts/2019-08-02-vac-overview.md index 6b74d5e..3b4c77f 100644 --- a/_posts/2019-08-02-vac-overview.md +++ b/_posts/2019-08-02-vac-overview.md @@ -50,7 +50,7 @@ In terms of specific properties and trade-offs at each layer, we'll go deeper do With all the pieces involved, this is quite an undertaking. Luckily, a lot of pieces are already in place and can be either incorporated as-is or iterated on. In terms of medium and long term, here's a rough sketch of priorities and open problems. -1. **Better data sync.** While the current [MVDS](https://github.com/vacp2p/specs/blob/master/mvds.md) works, it is lacking in a few areas: +1. **Better data sync.** While the current [MVDS](https://specs.vac.dev/specs/mvds.html) works, it is lacking in a few areas: - Lack of remote log for mostly-offline offline devices - Better scalability for multi-user chat contexts - Better usability in terms of application layer usage and supporting more transports