In the same post where the author of this blog article says they "don't like getting notifications about activity in my repo, and instead prefer to 'work offline' and 'only check in when I want' to... the author also details how they lost their domain which was bought by an ad spamming site guy.
I mean, are the scripts writing themselves here, boys?
I modified a library card software (Blacklight) into a searchable PDF industrial manual system awhile back on a one-off basis. It couldn't go any further than a contract project that delivered the source code because it's hard to do anything programmatically (at the time) to a PDF without Ghostscript.
I've often thought of rewriting it with Python (and Postgres, to get rid of Solr or Elastic as the search backend), maybe now's the time...
I trust you long enough for a second look because I ctrl-f'd the readme and found "pdfium" so I know I don't have to retread old ground in your github issues about how there's really only a couple of ways to parse a PDF with a semblance of reliability, lol...
(for anyone else reading this getting started with documents.. Adobe and Chrome are really the only PDF rendering libraries that work. PDF.js aka Firefox has always been broken, and Apple's is problematic as well, in both cases rearing their heads in terms of incorrect word / letter spacing).
In New Orleans they called it the "Katrina cough".
People would just get sick from random things and die 6 months or a year after they'd survived the hurricane. Happened to one relative on my father's side of the family. He just never shook the cough, right up until the day he died.
I will say that while I was in my 30s at the time, I took advantage of the architectural salvage goldmine that was New Orleans after Katrina. You could get priceless lumber, flooring, etc from salvaged 18th and 19th century houses that got flooded, which was great... until you didn't wear enough protective equipment while cleaning them up, and then you also got the cough.
The difference in 35 and 75 is the old uncle on my father's side of the family died from it, while I just suffered the worst sinus infection I ever had, and was fine after a few weeks.
As the article mentions, I can tell you that there is a stark divide between people who flew airplanes / helicopters in the civilian world before 1990 and after 1990, when noise cancelling headphones became prevalent.
Old guard can't hear anything, and has weird preferences for what small airplanes are 'good' or 'bad', whereas the younger crowd doesn't.
I personally owned a small airplane a few years ago that never made it as a viable product and wound up bankrupt, but for the remaining fleet still flying around and needing parts support. The company that made them went bankrupt in the late 1990s / early 2000s and one of the biggest knocks against it was how loud it was inside the cabin.
But with noise cancelling headphones all of that disappears and it's really a wonderful, comfortable little bird, and has had a resurgence in popularity as noise cancelling headphones became ubiquitous.
Even when I owned one I had no idea how loud it was inside the cabin until I inadvertently sat on the noise cancelling on/off switch on the cord of my headset one day and suddenly couldn't understand what the air traffic controller was saying, lol.
1. No, generally speaking corporate management in the 21st century does not make decisions based on effectiveness of their product or their workforce. They make decisions based on finance centered around the upcoming year or quarter. Tesla isn't interested in making good cars. Tesla is interested in selling tax credits. Period.
2. Even if #1 isn't true in an edge case, don't care.
I'm coming from the other side of the equation. I work for a (small-ish, niche) CRM company, and have insisted that all new customers be very explicitly told that they have to set up SPF and DKIM properly during their migration/implementation.
It would be nice to have something to send them to point out "here's where X% of your emails will go to spam if you don't do this, plus you're Y% of an annoyance on our mail server's reputation, too" but there's not any hard data to be found.
> It would be nice to have something to send them to point out "here's where X% of your emails will go to spam if you don't do this, plus you're Y% of an annoyance on our mail server's reputation, too" but there's not any hard data to be found.
If you are going to offer CRM to your customers that relies on sending email, then I suggest you read more on how email works, and how SPF, DKIM and DMARC work.
None of the three mentioned standards are anti-spam. They are anti-impersonation. If you are hosting the CRM, and your CRM is going to send email on behalf of your customer's domains, then your customers will have to include your services in their SPF poliy at the very least. But since SPF is horribly broken and shouldn't be relied on, you should always offer DKIM as well.
At the very least, the email you send should be DKIM signed with the rfc5321 domain, which is your domain, the one that matches the reverse-DNS of your host (because you should always setup reverse DNS). If the CRM is hosted by you (not your customer) then you should also generate DKIM keys per customer domain, and have the customer publish the DKIM public key under their domain. This is because you want DKIM alignment, which is especially important if the customer domain uses DMARC (which they should).
So TL;DR: your customer has to allow your CRM to send email on behalf of their domain by means of SPF and DKIM. If the CRM is hosted by you, you'll need to take extra care of alignment. SPF and DKIM are never optional, don't offer your customer a way to skip these steps, ever. If you don't want to deal with email issues, use a third party solution such as Mailgun, but even if you do, your customer will still have to set up SPF and DKIM.
I mean, are the scripts writing themselves here, boys?