Being a copyright license and not a contract (at least not intentionally,) it only is “viral” to derived works and not aggregate works. It allows commercial use of unmodified and modified instances of the licensed code, as long as you provide the modified code, just like GPL. It is only intended to “trigger” when distribution occurs under some legal copyright law definition of “distribution.” To my knowledge, with the way AGPL works, there are some interesting wrinkles: This is a particularly interesting use of AGPL because it appears to contain a RESTful HTTP server built-in. You let a decent number of bad emails through but it's an improvement over nothing. reject all emails with a score between 0 and 0.1) then your precision is really good (almost every email address you reject is invalid, as measured by actually sending an email to them and the email hard-bouncing or being otherwise undeliverable). I've used Sendgrid's email verification service in the past, and the actual scoring is basically garbage but if you set the threshold really low (e.g. Most businesses believe (probably accurately I don't have the stats) that this creates too much friction. actually emailing the address in question. The best way to do this is obviously double opt-in, i.e. (It can also help with bots a little bit, although most bots are smart enough to use or something). a soft paywall), I find that it's reasonably sensible to filter out the absolute spammiest-looking of email addresses in order to collect more real email addresses and prevent people just rolling their face across the keyboard and calling it a day. If you're asking for an email address in exchange for some piece of content (e.g. If only the tools get better, people will find new ways to be wasteful. People need to understand that we can't use more natural resources than get replenished. That one is easier to solve with certain (technical) tools available, but that won't be enough. People need to understand that world hunger is a distribution problem. But the overall problems are social in nature. For example, how to store more energy in a battery, or how to grow certain crops with less water. These are then technical (sub)problems though. Technical means can help solving certain components needed for the overall solution. If you think you can, you have already lost the fight.Īnd so on, and so forth. If you think you can, you have already lost the fight.Ĭlimate change is not a technical problem. Is it? In my dayjob I'm solving technical problems with technical means. Amazon's guidelines say they might cut you off when you hit 10%, so we cut it pretty close. ![]() Ended up with something like an 8% bounce rate that eventually fell off our record as our normal sending patterns resumed. We ended up unpausing the emails and just hoping for the best. (Edit: thinking back - this was several years ago - I think it wasn't saying that they were valid emails, just that it couldn't tell whether they were valid or not - the service was able to detect that the server wasn't rejecting non-existent addresses.) It was reporting every email as valid, even ones we knew were invalid since they'd already hard bounced. ![]() It turns out that this technique doesn't work for all mail servers. Meanwhile they were breathing down our necks to get these emails out ASAP, and they were a large enough client that our management wanted to keep them happy, so we tried out one of these email validation services. We asked the client to give us a better list, but due to internal issues they couldn't get that to us any time soon. Just under 1/10th of the emails in our first batch were invalid. We stopped sending and investigated the issue, and it turned out that the email list we were given was a mess - it included all current employees, but also a huge number of former ones. Our system sends these emails in batches, and as soon as the first batch went out we got an alert from our monitoring system that our bounce rate was surging - high enough to risk a sending pause from Amazon SES. (Where they'd be able to set up their password.) This process involved creating accounts for all of their employees (tens of thousands) and sending emails with an activation link. We were onboarding a large new client to our SAAS product.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |