Instead of backfilling every note we come across that has a reply
collection, only schedule a backfill job if someone wants to see the
replies (on GET MastoAPI /context, or Iceshrimp API /descendants)
Reply backfilling is also done on a ThreadIdOrId basis as opposed to the
previous way of backfilling individual notes. This allows us finer
grained control over the recursion and frees up the job queue, alongside
allowing for easier implementation of context collection backfill in the
future (by mapping each context collection to a thread)
---
Currently, note threads are implicit based on the "threadId" column of a
note, which can be null (where it's the same as the note's "id")
This commit turns note threads into an actual entity, and as a part of
that, makes "threadId" non-nullable (by specifically setting it to "id"
for those cases)
This is done to attach extra metadata to the entire thread, currently
just the time of when it was last backfilled, but more may be added in
the future (the context collection associated with this thread, for example)
---
The data format for backfill jobs have backwards-incompatibly changed
since the introduction of the feature. We can drop all old jobs without
causing too much trouble as they will be re-scheduled on demand
---
Signed-off-by: Laura Hausmann <laura@hausmann.dev>
This is a bit difficult of a situation as Akkoma does not have quote
notifications. This is the closest thing we have and the frontend seems
to handle it well.
While perusing through Glitch's PRs, I came across the patch from Chuckya
that lifts this restriction[0].
The patch exposes this restriction has been lifted with an extra flag in
the /api/v1/instance endpoint. Since Iceshrimp.NET does not have such a
restriction, signal the same flag so clients can adjust themselves
accordingly.
Clients don't seem to be aware of this flag just yet so this likely
won't have any immediate effects.
[0]: https://github.com/glitch-soc/mastodon/pull/2524
This commit lays the groundwork for a user-configurable image processing pipeline. It has exactly the same behavior as the old ImageProcessor, just modular & compartmentalized. It also adds support for AVIF & JXL encoding, though no code paths call it just yet.
