[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"
This commit is contained in:
tobi
2024-02-18 10:49:40 +01:00
committed by GitHub
parent 83a4adbd95
commit 40f9eefc21
5 changed files with 31 additions and 10 deletions

View File

@@ -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.