blog|wiki ^ recoll #wpress comment

Posted on by tiger40490 rendered_on [ Thu, 6 Mar 2025 ] 08:52 UTC

 

See also [18]drawbacks of blog site for keeping notes

For work or learning, “Active scratchpads” can be implemented as a wiki, or as a file in a recoll folder tree.

— wiki/blog (like all web sites) are designed first and foremost as an info display system, so you can keep a page open forever, as one of 20 open browser tabs. If needed, you could start an hour-long edit session, but eventually, you must save and publish.

  • Most of the time every document is in Published mode, not Edit mode as in recoll
  • 🙂 long title and hyperlinks .. powerful features in blog/wiki not recoll
  • 🙂 Version history is comprehensive in wpress, limited in wiki but tricky in recoll

— A recoll is a data storage /system/. The Edit-GUI and Display-GUI are the same thing, not separate as on a web browser. Therefore, we rarely display a recoll file forever because there is a non-trivial risk of unwanted edit [fat-finger], and we don’t know how to roll back.

  • 👎 Instead of hyperlinks, recoll has softlink .. a feature in unix but not windows.
  • 🙂 frequent update .. much easier in recoll. With blog/wiki, we rely on comments (see below)
  • 🙂 A recoll has more flexible content-organization. A wiki tree is kinda similar, but my blog is not. My blog relies on categories (tree) and tags.

Email (including gmail) draft .. also a data storage.

== wpress comments .. Blog is not optimal/efficient for frequent editing of multiple bposts. The wpress discussion [i.e. reader comment] feature offers a quick-n-dirty solution.

To see all comments, wpress admin interface -> left menu -> Comments

— Traditional solution: push_front() as in STL .. add new content at top, then insert a <hr> before existing content.
— fend off outsider comments ..

  • AutomaticallyCloseCommentsOnPostsOlderThan … I put 1Y or 2Y to keep most of my older bposts less complicated when printed
  • .. Presumably, all approved comment continue to show on the bposts.
  • Each bpost has an AllowComment checkbox. Was a problem with a few bposts.
  • anti-spam plugins .. might be helpful
  • Right now, my blogs require visitors to log in. This is one separate, independent layer of defense against unwanted comments.