aboutsummaryrefslogtreecommitdiff
path: root/content/en/docs/Overview
diff options
context:
space:
mode:
Diffstat (limited to 'content/en/docs/Overview')
-rw-r--r--content/en/docs/Overview/_index.md11
1 files changed, 7 insertions, 4 deletions
diff --git a/content/en/docs/Overview/_index.md b/content/en/docs/Overview/_index.md
index 9e648b0..00d0467 100644
--- a/content/en/docs/Overview/_index.md
+++ b/content/en/docs/Overview/_index.md
@@ -79,10 +79,13 @@ accessible on [arXiv](https://arxiv.org/pdf/2001.09707.pdf).
The best place to start understanding a bit what Ouroboros aims to do
and how it differs from other packet networks is to first watch this
-presentation at
-[FOSDEM 2018](https://archive.fosdem.org/2018/schedule/event/ipc/)
-but note that this presentation is over three years old, and
-very outdated in terms of what has been implemented.
+presentation at [FOSDEM
+2018](https://archive.fosdem.org/2018/schedule/event/ipc/) but note
+that this presentation is over three years old, and very outdated in
+terms of what has been implemented. The prototype implementation is
+now capable of asynchronous flows handling, doing retransmission, flow
+control, congestion control...
+
The next things to do are to have a quick read of the
[flow allocation](/docs/concepts/fa/)
and