I mean, are the scripts writing themselves here, boys?

"it's too slow" is a thing a lot of customers have mentioned to me over the years.

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).

...didn't get any, but I found some via an unfortunate client, who was doing this via a CRM without setting any sort of domain authentication up for their sender (I do data migrations at my day job, so I see everyone's skeletons...)

tl;dr: bounce rate will be about 45-50% over time if you don't set up any sort of DKIM or SPF records, varying slightly depending on your recipients, but it's the IMPORTANT PEOPLE you can't email.

Excerpt below, <-- email domain sent to, --> email server which rejected the message.

Email Bounced | Email Server

---------------------------------------

@cbmove.com usb-smtp-inbound-1.mimecast.com.

@pattonboggs.com eu-smtp-inbound-1.mimecast.com.

@montgomerycollege.edu mx0a-0016b401.pphosted.com.

@iri.org us-smtp-inbound-1.mimecast.com.

@stemedcoalition.org us-smtp-inbound-2.mimecast.com.

@bipc.com us-smtp-inbound-1.mimecast.com.

@dickblick.com us-smtp-inbound-1.mimecast.com.

@student.american.edu mx0a-00240c01.pphosted.com.

@cbf.org us-smtp-inbound-1.mimecast.com.

@binghamt.gannett.com us-smtp-inbound-1.mimecast.com.

@hhlaw.com eu-smtp-inbound-2.mimecast.com.

@pattonboggs.com eu-smtp-inbound-1.mimecast.com.

@iri.org us-smtp-inbound-1.mimecast.com.

@tmgcustommedia.com us-smtp-inbound-1.mimecast.com.

@washington.goethe.org mx02.goethe.de.

@nbcuni.com mxb-00176a04.gslb.pphosted.com.

@jonesday.com mxb-00393202.gslb.pphosted.com.

@intelsatgeneral.com mxb-0056a401.gslb.pphosted.com.

@qga.com mxa-00173601.gslb.pphosted.com.

@wpost.com mxb-001a3c01.gslb.pphosted.com.

@nbcuni.com mx0a-00176a04.pphosted.com.

@tr.com mxb-00160c04.gslb.pphosted.com.

@arts.ri.gov mx0b-00137801.pphosted.com.

@readexpress.com mxa-001a3c01.gslb.pphosted.com.

@icloud.com mx02.mail.icloud.com.

@readexpress.com mxa-001a3c01.gslb.pphosted.com.

@nbc.com mxa-00176a04.gslb.pphosted.com.

@wellsfargoadvisors.com mxa-00004003.gslb.pphosted.com.

@american.edu mx0b-00240c01.pphosted.com.

@chron.com mxa-0018d701.gslb.pphosted.com.

@na.ko.com mxa-0037a502.gslb.pphosted.com.

@bbandt.com mxb-0058fb01.gslb.pphosted.com.

@exxonmobil.com mxa-00016305.gslb.pphosted.com.

@dcist.com mx0a-00240c01.pphosted.com.

@k12.com mxa-00678201.gslb.pphosted.com.

@stanford.edu mxb-00000d07.gslb.pphosted.com.

@ge.com mx0a-00176a02.pphosted.com.

@american.edu mx0b-00240c01.pphosted.com.

@dynetics.com mxa-00336402.gslb.gpphosted.com.

@washpost.com mxa-001a3c01.gslb.pphosted.com.

@pnc.com mxb-000ade01.gslb.pphosted.com.

@vh1staff.com mxa-00262c01.gslb.pphosted.com.

@hosthotels.com mxa-00320801.gslb.pphosted.com.

@dc.gov dc-gov.mail.protection.outlook.com.

@dc.gov dc-gov.mail.protection.outlook.com.

@arenastage.org arenastage-org.mail.protection.outlook.com.

Comments URL: https://news.ycombinator.com/item?id=38527140

Points: 1

# Comments: 0

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.

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.

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.

Anyone have something with numbers on this topic bookmarked somewhere? Or that they can share from internal studies at larger email providers?

Comments URL: https://news.ycombinator.com/item?id=37127604

Points: 4

# Comments: 3

(Twitter's auth flow is entirely broken if you had SMS 2FA before the Musk takeover and pay-to-play. It won't let you log in with the only 2FA method you have, and redirects you to a form to reclaim a locked account after the failure which... requires you to be logged in).

If Patreon is charging users for access to content, Patreon is obligated to serve it to those users, which in turn means Patreon is obligated to provide the hosting. Content creators on Patreon aren't users, they are content creators. The end user is the user. The end user is the one paying the money here.

If Patreon wants to, in turn, bill content creators for that hosting that's between them and the content creators, but the end user has absolutely ZERO reason to care whether Joe Schmo YouTube influencer paid his video hosting bill.

If I am a user and I've paid for content on Patreon which disappears, my legal recourse is with Patreon, not the content creator. I didn't pay the content creator, Patreon took my money and if the videos aren't there, Patreon has failed to provide the service for which the money was paid. Whether or not the content creator has a claim against Vimeo or Patreon is immaterial to this.

This isn't rocket science, I don't know why you are struggling to figure it out. Replace "Patreon" with "Netflix". Imagine Netflix's customers paying for access to their movies and TV shows, but Netflix decides that movie producers have to pay for the hosting because they don't like the size of their AWS bills. When the movies disappear because the movie producers don't like the size of the AWS bill either, do you think Netflix would get away with keeping the money but telling their own end user "oh sorry the movie producer was supposed to pay the AWS bill for their film's downloads, but they didn't pay the hosting bill so it disappeared, not my problem."

Or if you prefer, replace "Patreon" with "Cambridge University Press." Imagine you bought a book from said book publisher's website, and it never arrives in the mail. When you inquire about where your book is, Cambridge University Press says "oh yeah we have rights to print and distribute that book, but printing presses cost a lot so we told the book author to just print them himself. If he didn't pay for the printing and send it to you, that's not our problem, piss off."

Obviously these are ridiculous scenarios, and would land Netflix and/or Cambridge University Press in their attorneys' offices to take a look at the claims filed against them bright and early tomorrow morning if they tried to do such things.

The first post has a mention further down in the tweet thread about that particular creator also getting a ~$3000.00 invoice from Vimeo.

https://twitter.com/hate5six/status/1481511608979533826?s=21

Patreon needs to be a publisher or be a payment processor, but don't charge people for both while only actually doing one or the other.

I suspect a lot of content people have paid for is going to start disappearing next week, it seems that these guys got one-week notices to pay up to Vimeo.

It will be interesting to see what Patreon does then, because your analysis is mistaken in that their hands are not clean here. All the EULAs in the world don't absolve them from charging for a service and then failing to deliver it. By refusing to publish the videos themselves, if Vimeo pulls any of the content down Patreon has opened themselves up for a class action, I would think. The end user subscriber does not have a reason to care about Patreon's subcontracting status, all they would need to know is they paid for content and it did not arrive.

When Vimeo came calling to look for the payment for excess bandwidth that particularly popular creators used, Patreon just passed the invoice right on through to the content creators, some of whom have been notified that they have a week to pay Vimeo thousands of dollars or have all of their content deleted.

https://twitter.com/hate5six/status/1481500463317012482?s=21

https://www.patreon.com/posts/vimeo-is-holding-61514364

Comments URL: https://news.ycombinator.com/item?id=30130387

Points: 20

# Comments: 6