Joël de Bruijn

  • 0 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle

  • I don’t know.

    • I don’t need formatting but it doesn’t get in the way either. So I am not bothered by it.
    • Also pdf and especially PDF/A standard is widely used for archiving and compliance regulation concerning archival and preservation.
    • If you want text the same tactic goes: just export in bulk to txt instead of pdf

    My main point is: Why would you want a mail specific stack of hosting, storage, indexing and frontends? If it’s all plain text anyway so the regular storage solutions for files come a long way.

    There is an entire industry (which has its own disadvantages) to get communication artefacts out of those systems and put it in document management systems or other forms of file based archival.


  • I had roughly the same goals ( archive search 2 decades of mail) but approached it completely different: I export every mail to PDF with a strict naming convention.

    • Backend: No mailserver, just storage and backup for files.
    • Search: based on filenames FSearch and Void tools Everything. I could use local indexing on pdf content.
    • Frontend: a pdf viewer.





  • As a #2 person, when my level-of-current-knowledge hits a ceiling and I ask for technical advice in forums or lemmy or even social media, it often comes from a #1 person.

    Assuming its specialized knowledge few other #2 have.

    Half the time I get an answer (about what and how) AND background explanation (giving context and WHY).

    But half the other time a #1 doesnt realize easy things for them are hard for me. When they are miles ahead their answer assumes I have a host of other skills already in place. But I dont know what I don’t know so I dont ask for them.

    But … every answer from a helpfull stranger is appreciated. Just bridging knowledge is hard.