Properly federate "like" objects
<!-- Please use a concise and distinct title for the issue --> <!-- Consider: Could it be implemented as a 3rd party app using the REST API instead? --> ### Pitch 1. Incoming `like` objects are applied to posts, and posts are fetched for newly seen ones (similar to how `announce` objects are handled. 2. Any generated `like` objects are federated to all followers (and of course the poster), similar to how replies work. ### Motivation Many Fediverse softwares, for example, Prismo and PeerTube, threat likes as important information, so Mastodon should properly handle them. Also, this would further fill out federated timelines, since you'd see all posts that anyone followed on your instance likes, as opposed to only the ones they boost or reply to.
Posted by ealgase on Jul 17, 2019, 7:35 PM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
Properly federate "like" objects
<!-- Please use a concise and distinct title for the issue --> <!-- Consider: Could it be implemented as a 3rd party app using the REST API instead? --> ### Pitch 1. Incoming `like` objects are applied to posts, and posts are fetched for newly seen ones (similar to how `announce` objects are handled. 2. Any generated `like` objects are federated to all followers (and of course the poster), similar to how replies work. ### Motivation Many Fediverse softwares, for example, Prismo and PeerTube, threat likes as important information, so Mastodon should properly handle them. Also, this would further fill out federated timelines, since you'd see all posts that anyone followed on your instance likes, as opposed to only the ones they boost or reply to.
Comments (0)
No comments yet. Start the discussion.