Chloe Kudryavtsev 91a4f38871 backend: add automatic dead instance detection ... It works by having a day-long cache of "when did we last successfully communicate with this instance?" Anything over a specified threshold (1 month) will act as though the instance is suspended - all outgoing jobs are dropped on processing. The day-long cache is in place because the ordering is necessarily a linear scan. Once an instance comes back online, we will detect that is the case as soon as we receive an activity from them (which will update the "last communicated at") field. Potential future TODOs: * Improve the caching system, it's actually pretty inefficient as it is. CacheBox with a call override? * Think of ways to make it not-a-linear-scan, since the instances table can get pretty big. It's around 4500 on toast cafe. ChangeLog: Added		2022-10-16 12:16:04 +00:00
..
backend	backend: add automatic dead instance detection	2022-10-16 12:16:04 +00:00
client	add link to external CSS snippets	2022-10-14 17:11:06 +02:00
foundkey-js	feat: per-user renote muting	2022-10-11 10:42:39 +00:00
shared	client: fix some lints	2022-08-12 08:35:22 +02:00
sw	Revert "Use native shell commands for clean/clean-all"	2022-09-22 13:48:06 -04:00
meta.json	refactoring	2021-11-12 02:02:25 +09:00