deletePost does not broadcast over the firehose

Open Beginner friendly
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
javascript
Domain
api, backend

Research direction

Start in rssnetwork.js at deletePost around line 1593, then compare its notification flow with updateItem around line 657 and the likes handler around line 1908. Confirm the deletion notification format, update the firehose behavior so subscribers receive a deletion event, and verify that deleted posts can be removed by consumers such as the WordPress mirror.

Written by the indexing model from the issue text.

Description

Summary

The /deletepost endpoint sets flDeleted = 1 in the database and updates S3, but never calls notifySocketSubscribers. As a result, firehose subscribers do not receive any notification when a post is deleted.

Expected behaviour

When a post is deleted, the firehose should broadcast an updatedItem (with flDeleted: true) or a new deletedItem verb so that subscribers can react — for example, by removing the mirrored post from a WordPress site.

Relevant code

rssnetwork.js, function deletePost (line ~1593). Compare with updateItem (line ~657) and the likes handler (line ~1908), both of which call notifySocketSubscribers after modifying an item.

Context

Found while building rsschat-wordpress-service, a server-side firehose subscriber that mirrors posts to WordPress. The mirror handles newItem and updatedItem correctly, but deletions on rss.chat are invisible to it.

Dominant language
JavaScript
Stars
37
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/rss.chat

All issues in scripting/rss.chat

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.