Idea
I think a good next functionality is allowing users to edit and delete via the web interface (and subsequently the cgi-bin API), rather than going into their system and editing/removing the raw files.
It should be as simple as replacing the BODY.md file for a certain post id.
Cgi-bin API
I propose a cgi-bin API command: 6{post_id}{new_body}{password} for edit and 7{post_id}{password} (or whatever the next command ids will be), both called on the poster's cgi-bin.
Edit will authenticate with the password on the poster's cgi-bin then replace BODY.md's text with new_body in the right folder (determined with post_id), and delete obv just deletes that whole folder.
Front-End Changes
On the front-end side, we could have a hidden form that appears when you click a new "Edit" button. Then if you submit that, it works much like the submit for a new post on the main page.
This goes on the post index.html, not the main towertalk index.html.
Idea
I think a good next functionality is allowing users to edit and delete via the web interface (and subsequently the cgi-bin API), rather than going into their system and editing/removing the raw files.
It should be as simple as replacing the BODY.md file for a certain post id.
Cgi-bin API
I propose a cgi-bin API command:
6{post_id}{new_body}{password}for edit and7{post_id}{password}(or whatever the next command ids will be), both called on the poster's cgi-bin.Edit will authenticate with the password on the poster's cgi-bin then replace BODY.md's text with new_body in the right folder (determined with post_id), and delete obv just deletes that whole folder.
Front-End Changes
On the front-end side, we could have a hidden form that appears when you click a new "Edit" button. Then if you submit that, it works much like the submit for a new post on the main page.
This goes on the post index.html, not the main towertalk index.html.