• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2023

help-circle


  • Why? Why ask for this from the creator?

    If someone can create new software and offer it for free, they should not also be expected to also create a comprehensive analysis of what other people did and list of differences.

    Just take it or leave it, it’s that simple. No need to act as if you’re trying to waste some door-to-door salesman’s time.

    Edit: I expected some downvotes but not that many.

    To my defense, the question in this thread is “you could elaborate what exactly you did different than all the others”. Look, I’m not a native English speaker either but I feel we could agree that is still pretty far away from simply being curious about design choices or “what led you to create this” sort of exploratory question.

    I might have overreacted, though, so sorry for that.









  • Can’t help but think of a “senior dev” “explaining” (hing: brain-dumping) some bizarre reasoning why his unusable untested undocumented untyped API uses floats for item counts or something, and expecting the “junior dev” to just nod and keep that in their mind and adapt to it.

    (Instead of making every possible excuse not to work with that API and instead doing something else where they can make some progress without going insane.)


  • If so many people weren’t leaving the field entirely due this issue (the chief complaint ALWAYS being under-staffing / low nurse-to-patient ratios, THEN pay), there would be plenty of nurses to go around

    I think both can be true.

    From expenses point of view, Isn’t under-staffing almost the same thing as low pay? What’s preventing hospital administrators from hiring more nurses? If it’s just money, then I don’t think the complaint of under-staffing all that different from the complaint of low pay; I suspect it’s even affected by sort of preference (some nurses would prefer working more for better pay, others would prefer sharing the workload.)

    Of course from administration / governance point of view it boils down to money, what I’m saying is that I find it unlikely is that it’s “just hire more nurses”. It’s also doctors, other staff, etc. It’s more likely the whole system.





  • Again, perhaps with more clarity:

    With imapfilter you can

    1. choose where you will host your “actual” e-mail, let’s say you choose according to best spam filter.
    2. choose where you will store your e-mail long-term.
    3. choose where you will access the e-mail for everyday use (this could be several separate accounts if you wanted to eg. use one on your phone and another one on your workstation)
    4. choose where you will run imapfilter and any script hooks
    5. start building your rules.

    1-3 could be same provider or different providers, including your custom dovecot instance, you will simply choose based on convenience and limits. If you ever need to change one of the endpoints (providers), you just need to rewrite them in your ~/.imapfilter/config.lua. (And migrate, which can be done using imapfilter or manually using any sane client, eg. Claws Mail…)


  • Whatever hosting service you’re going to use, if you’re not afraid of a little bit of Lua coding, consider using imapfilter – it’s a swiss knife for backups, pre-sorting, hooks and migration.

    imapfilter is a (criminally underrated, IMO) tool for writing e-mail rules in Lua, which allow you to do tons of things, but my favorite is migrating e-mail, regardless of account.

    See, unlike most filtering/sorting systems which are either completely proprietary or limited to single account (exportable as Sieve, if you’re lucky), imapfilter does not care where each “end” of the rule is: you can write rule that migrates from account1/folder1 to account2/folder3.

    This allows you to completely decouple any sorting, pre-processing, hook or backup system from the actual locations or providers you happen to be using, as well as it allows you to combine any number of locations in any simple or complex way you need. Whatever system you will end up creating will stay with you as long (as you can use IMAP locations), so you can really focus on making it work long-term and have it fit into the big picture.

    I’ve been using it for almost 10 years and ever since it has changed my whole world of e-mail. I have constant set of rules that take e-mails from set of inboxes (each box for different purpose, each on different provider, for reasons) and sort them to folders on my “actual” account, where I get to read them on my terms. I also have several of rules that run custom scripts exporting CSV’s, etc. (The rules are Lua programs, after all, so sky is the limit.) If I ever need to migrate my domain to another service (believe it or not, happened more than once in 10 years), all I need to do is set up the new account as base for the rules, but all of my rules are always going to be preserved.

    In my past work I actually used imapfilter to move all IMAP from company Gmail to a locally maintained (on company laptop) Dovecot instance so that I could eventually use a sane client to get my work done. (And because the instance was local, I could access my e-mail offline with best possible speed.) One could do a similar thing with personal/freelance e-mail – just run Dovecot somewhere at a trusted place (you won’t be sending/receiving e-mails here, you will be only using IMAP to IMAP commands, so none of the horrors of self-hosting e-mail apply) and use imapfilter to route all email there, then back up your dovecot folder and you’re all set.

    Except for need of coding, the disadvantage is that, I need an independent machine that runs 24/7 in order to keep sorting the e-mail (I do it cron-based but you can also do it continually) but that has not been a problem for me as I’m the self-hosting-nerd that’s going to have such machine anyway.