Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add parent submission field for reply threads #386

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

askmeaboutlo0m
Copy link
Contributor

This adds a new "parent submission" field to the default submission section, letting the user pick a submission's parent from a drop-down. After posting a submission, website services get a chance to react to this and manipulate the child's part however they feel is useful.

Currently, this is implemented for Bluesky, Mastodon and Pleroma, which will set the "reply to post URL" field to the source URL of the parent post, removing the necessity to manually copy those over.

Other uses could be implemented if someone feels like it, different websites have various flavors of post relationships that could be handled this way.

The only time the application acts on parent-child relationships is right after a submission has been posted. That means invalid parents that reference removed submissions cause no harm, they're presented to the user as being unassigned. That means we don't need to bother maintaining the validity of these fields when removing submissions. We also don't need to check for circular dependencies, since those circles will break themselves as soon as one submission out of them is posted.

This adds a new "parent submission" field to the default submission
section, letting the user pick a submission's parent from a drop-down.
After posting a submission, website services get a chance to react to
this and manipulate the child's part however they feel is useful.

Currently, this is implemented for Bluesky, Mastodon and Pleroma, which
will set the "reply to post URL" field to the source URL of the parent
post, removing the necessity to manually copy those over.

Other uses could be implemented if someone feels like it, different
websites have various flavors of post relationships that could be
handled this way.

The only time the application acts on parent-child relationships is
right after a submission has been posted. That means invalid parents
that reference removed submissions cause no harm, they're presented to
the user as being unassigned. That means we don't need to bother
maintaining the validity of these fields when removing submissions. We
also don't need to check for circular dependencies, since those circles
will break themselves as soon as one submission out of them is posted.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant