No description
7173373330
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> |
||
|---|---|---|
| .docker | ||
| .forgejo/workflows | ||
| .idea/.idea.Iceshrimp.NET/.idea | ||
| Iceshrimp.Backend | ||
| Iceshrimp.Frontend | ||
| Iceshrimp.Parsing | ||
| Iceshrimp.Shared | ||
| Iceshrimp.Tests | ||
| .gitignore | ||
| .noai | ||
| CHANGELOG.md | ||
| Directory.Build.props | ||
| Dockerfile | ||
| FEDERATION.md | ||
| global.json | ||
| Iceshrimp.NET.sln | ||
| Iceshrimp.NET.sln.DotSettings | ||
| LICENSE | ||
| Makefile | ||
| NuGet.Config | ||
| README.md | ||
| SECURITY.md | ||
Iceshrimp is a decentralized and federated social networking service, implementing the ActivityPub standard.
- Highlighted features:
- Don't like the Web UI? We test our Mastodon-compatible API against the following clients:
- Project goals:
- Provide a community-centric alternative to the big ActivityPub SNS projects
- Strong focus on maintainability, stability & performance, as well as user choice and configurability
- Prioritization bug fixes over features
- Project anti-goals:
- Flashy marketing
- Commercialization of any kind
- Want to set up an instance?
- Have a look at the documentation & the feature comparison matrix!
- Please note that we do not operate a "flagship instance", the only project-affiliated domains are
iceshrimp.devandiceshrimp.net.
- Want to join development efforts?
- Have a look at the knowledgebase and join the chat room!
- Want to donate to the project?
- Our frontend dev (Lilian) needs help paying for healthcare costs. You can contribute here. Money from the fund will be used for co-pays, and medical expenses not covered by insurance.
Note
This is beta software. The Mastodon client API is relatively complete, the frontend is rapidly improving. Nonetheless, we don't recommend to upgrade existing Iceshrimp-JS instances quite yet. Setting up new instances and reporting bugs is very appreciated, however, and will help us ensure eventual upgrades go as smoothly as possible.
If everything goes well, we estimate that there'll be a stable release by the end of 2024.
Shoutouts to JetBrains for providing us with free access to their awesome developer tools.