mre

How I built my own newsletter setup (and why)

A few people asked me how this newsletter is sent. The honest answer is: I'm still figuring it out. But here's the story so far, because the technical bits are less interesting than the path that got me here.

Tinyletter

I had a newsletter on endler.dev for years. It was a little form on the website that pointed at Tinyletter. I never thought about deliverability, bounce rates, suppression lists, SPF, DKIM, DMARC, or any of that. I wrote a thing, hit send, people got it. It just worked.

Then Tinyletter shut down.

mre

🔍 7336 Total (in 3m 26s) ✅ 4956 OK 🚫 767 Errors 👻 336 Excluded ⏳ 24 Timeouts 🔀 1253 Redirects

📊 Per-host Statistics
────────────────────────────────────────────────────────────
github.com                                         │   1052 reqs │   98.9% success │    593ms median │   19.5% cached
en.wikipedia.org                                   │    673 reqs │  100.0% success │     67ms median │   18.1% cached
ru.wikipedia.org                                   │    411 reqs │  100.0% success │     74ms median │   12.2% cached
img.youtube.com                                    │    232 reqs │  100.0% success │     56ms median │    3.9% cached
amzn.to                                            │    189 reqs │  100.0% success │    480ms median │   26.5% cached

mre

Sample Org File with Links

Web Links

Here are some external web links:

• Anthropic’s Website
• Org Mode Official Site

mre

Why you think it's an anti-pattern to have a "types" crate?

Discussion at: https://fosstodon.org/@ianthetechie/114517520321760826

That's a fair question. What I found is that "types" is a bit of a scapegoat for things that have a proper place yet, similar to "utils", "shared." The types crate tends to become a dumping ground for types that don't have a fixed place yet. Code in those crates is not really "discoverable" as in: I would have to look into the crate to see what's in there and how it relates to the rest of the codebase.

For example, the standard library has a bunch of primitive types, but they all live in their own module in the core crate. The rest lives close to the supporting code, e.g. see the structs in std::process (https://doc.rust-lang.org/std/process/index.html#structs). If these structs were all in the types crate, it would make the code and the documentation a lot harder to navigate in my opinion.

mre

// This is an algorithm, which creates an ID for a podcast episode.
// It is based on the  the podcast's title, episode's title, the episode number,
// the date of the episode and the episode's mp3 file name.
//
// All fields can change over time, but the ID should remain the same.
// Think of it more like a user agent string than a unique ID: it is "unique
// enough" for identifying episodes in most cases.
//
// It's used to identify episodes in the database.

mre

mre

[
  {
    "data": {
      "search": {
        "userCount": 2646,
        "edges": [
          {
            "node": {
              "login": "torvalds",
              "followers": {

mre

fn main() {
  println!("{}", foo);
}

mre

+ [pyenv:22] enable -f /usr/local/bin/../libexec/pyenv-realpath.dylib realpath
+ [pyenv:29] '[' -z '' ']'
++ [pyenv:31] type -p greadlink readlink
++ [pyenv:31] head -1
+ [pyenv:31] READLINK=/usr/local/bin/greadlink
+ [pyenv:32] '[' -n /usr/local/bin/greadlink ']'
+ [pyenv:54] '[' -z '' ']'
+ [pyenv:55] PYENV_ROOT=/Users/mendler/.pyenv
+ [pyenv:59] export PYENV_ROOT
+ [pyenv:62] '[' -z '' ']'

mre

#[cfg(test)]
#[macro_use]
extern crate proptest;

extern crate chrono;

use chrono::prelude::*;
use std::convert::From;
use std::num::ParseIntError;