Roadmap#
Schemas & Config#
-
Add
notifytop-level variables - allow notification channels to be added and configured, e.g. slack message or email - Secret storage Allow users to store encrypted secrets in their config, e.g. protect webhook endpoint
- Stabilize config API for existing features
Crates#
-
The top-level
__tera_contextobject (for templating) is weird and sort of mysterious. There should be a__r3ply_contextobject within it that can be documented. It will be easier to remember plus__tera_contextcould still be useful for other things in the future and it might be bad design to expose the full context and not have a more focused option.
Library#
- Add ability to "replay" comments through different stages of the pipeline as starting points. This could be very helpful if people need to do migrations. E.g. Let's say you've made changes to your comment template, but you need to make sure all the old comments have those changes as well. You should be able to reprocess the old comments and then diff them with version control to check that everything worked as expected.
- Add support for email attachments (this could be a good path towards allowing sites to implement user icons)
- Add other comment sources. Perhaps a magic link or even a POST comment source?
Commenting Sources#
- POST + Magic Link?
- ActivityPub?
- AT Protocol?
- Text??
- Each commenting source's shared config should be broken out in the config's schema (see how moderation is done for inspiration)
CLI#
-
For
re simulate emailmake sure that only validSubjectlines are generated. To do this will require the intersection of the site's sitemap.xml and the site's[comments.path*]config variable. -
Add synonyms for the stage names to be used by the
--filter/--quietoptions. For example, currentlycommentis used instead ofprocessedbut it should technically permit both. - Rewrite in rust
r3ply Apps & Infrastructure#
- Email server
Moderation Channels#
-
Email based moderation (Approve/Add to
block*/approve*lists) from within email - Add the cache as a moderation channel?
GitHub Moderation#
- Add support for public repos via a fork + new PR flow in the GitHub bot.
Webhook#
- Better testing.
Notification Channels#
- Build library support
- Email notifications to site
Site/Docs#
- Add search
- Tutorial section: for example, how to allow people to support aliases (will also be good for when attachments are supported)
──𓆝𓆟𓆞𓆝𓆟 𓆝𓆟𓆞──
Comments (0) #
Write Comment Comment [-] Collapse All Collapse [+] Expand All ExpandCommenting Info:
This is a demo of commenting using r3ply. You can leave comments on this website by sending an email.
Your email address will be anonymized, and can never be shared with anyone.
To try it out click the Write Comment button, or draft an email manually 1. Your email client with a template already filled out that looks as follows:
To send an email manually, just compose it exactly like the code snippet above. To respond to a comment append
#<Comment-ID>to the path, e.g.Subject: /docs/getting-started/#abcd1234(please note the trailing slash). You can also respond to text fragments the same way, e.g.Subject: /docs/getting-started/#:~:text=You%20should%20see%20a%20bunch%20of%20text%20representing. ↩Pending Comments (0)
This comment shouldn't actually normally be rendered. It's used to by the base.html template to render one instance of a templat… root / parent .. # . next ⭣ prev. ⭡
This comment shouldn't actually normally be rendered. It's used to by the base.html template to render one instance of a template that's wrapped in
<template>tags. That template is then later cloned and appended to the page for each comment that's pending in the comment cache. To view this comment go to /debug-comment-template/.