mirror of https://github.com/LemmyNet/lemmy.git
2c57f42022
* Relax timeout for sending activities Lemmy considers timeouts during activity sending as retryable errors. While it is frequently enough to retry sending the same activity again after the original submission attempt resulted in a timeout, allowing the receiving side to use more time for synchronous processing should reduce the number of retries needed overall and improve overall compatibility. Some ActivityPub software, such as Mastodon, implements a queue for processing received activities asynchronously, which allows immediately returning a response for activity submissions. Other software, such as Lemmy or Hubzilla implement synchronous processing of activities before returning a response. ActivityPub does not specify specific timeouts to be used: https://github.com/w3c/activitypub/issues/365 * Simplify usage of federation_sender_config Option |
||
|---|---|---|
| .. | ||
| api_routes_http.rs | ||
| code_migrations.rs | ||
| lib.rs | ||
| main.rs | ||
| prometheus_metrics.rs | ||
| root_span_builder.rs | ||
| scheduled_tasks.rs | ||
| session_middleware.rs | ||
| telemetry.rs | ||