From 40f9eefc2153ee8811abb750e07064c4f98f549c Mon Sep 17 00:00:00 2001
From: tobi <31960611+tsmethurst@users.noreply.github.com>
Date: Sun, 18 Feb 2024 10:49:40 +0100
Subject: [bugfix] Fix dereferencing ancestors on new status create (#2652)

* [bugfix] Pass `latest` to dereferenceThread instead of barebones status

* only mark status orphaned if visibility suggests parent is really deleted

* tone down "not deref'd" warnings, since they represent a legit visibility situation

* remove FAQ entry for "status not deref'd yet"
---
 docs/faq.md | 4 ----
 1 file changed, 4 deletions(-)

(limited to 'docs')

diff --git a/docs/faq.md b/docs/faq.md
index 219932078..23403d363 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -50,10 +50,6 @@ Take a look at the [list of open bugs](https://github.com/superseriousbusiness/g
 
 These warnings are caused by Mastodon forgetting to take query parameters into account when signing HTTP requests. Fixes on both Mastodon and GoToSocial sides are in the works, and other instance software is expected to follow.
 
-## Warnings “status not yet deref'd” in the logs
-
-The warning is mostly to say that the derived visibility of the given status may not be entirely accurate due to a parent not being dereferenced yet, so do not worry about it.
-
 ## Will you support tables in Markdown?
 
 Not at the moment, as most clients handle them terribly.
-- 
cgit v1.2.3