From fb8eea7ced5c5ad63418729be7170310b9970cd1 Mon Sep 17 00:00:00 2001 From: MadLittleMods Date: Wed, 6 Apr 2022 21:35:09 +0000 Subject: deploy: 350062661cbc402c089ce7a20b72d83073ed8fec --- develop/development/room-dag-concepts.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'develop/development') diff --git a/develop/development/room-dag-concepts.html b/develop/development/room-dag-concepts.html index c206cce3d8..a03d34be03 100644 --- a/develop/development/room-dag-concepts.html +++ b/develop/development/room-dag-concepts.html @@ -176,7 +176,8 @@ yet correlated to the DAG.

Outliers typically arise when we fetch the auth chain or state for a given event. When that happens, we just grab the events in the state/auth chain, without calculating the state at those events, or backfilling their -prev_events.

+prev_events. Since we don't have the state at any events fetched in that +way, we mark them as outliers.

So, typically, we won't have the prev_events of an outlier in the database, (though it's entirely possible that we might have them for some other reason). Other things that make outliers different from regular events:

-- cgit 1.5.1