3 ms·
Interesting :- ) That one should have been in the list too yes. — I'd be worried about Denial-of-Service attacks & moderation. What if the blog gets popular? An
by KajMagnus 9y ago
Interesting :- ) That one should have been in the list too yes. — I'd be worried about Denial-of-Service attacks & moderation. What if the blog gets popular? And "angry people" posts 9999 spammy comments. Even if one deletes them from the blog, they'd sill be in the commit history? (but I want a somewhat clean commit history that is readable to me)
And what if someone illegally post personally-identifiable-info (PII), even if one deletes it, it'd still be in the commit log, which I think would be illegal? Maybe StaticMan could rewrite the Git history to delete flagged & deleted comments (e.g. comments with PII)... But if it does that, the rebased history will cause problems when you try to push your next blog post to the repo.
Maybe if blog comments were in a separate repository whose history could be rewritten, without interfering with the main repo to which one pushes one's new blog comments.
- WorldMaker 9y agoStaticman supports GitHub PRs so you can vet/flag/delete comments as a PR and they don't end up in main branch commit history if you don't merge the PR. If you delete the PR branch eventually git gc in sync with GitHub's branch cleanup process will cleanup the dead commits, so there's a window when where that PII will be available, but it would eventually get tossed.
- KajMagnus 9y agoOk, that seems like a lot safer, thanks for explaining