This account could easily become "the alt where I kvetch about social media"

This account could also become "the alt where I post my own art because it would feel so wrong to post such crap art alongside art that I consider good", but not quite as easily

This account could also become "the alt where I talk about what to do with this alt"

This account could also get deleted, how do you like that option

@dustin I'm sorry, I forgot to tell you about The Monks! Well, I didn't know you didn't know. That's my excuse.

I first learned about The Monks when our scrum master asked, "OK, what band should we name this week's release after?" and I proposed "The Monks!" and they consulted the Internet and they were like "Do you mean The Monks or The Monks?" and I consulted the Internet and I was like "Oh wow. They're both good choices actually."

If anyone asks "They lost $119 billion? But... but where did all that money *go*?", it may help to remind them that "stock market" is kind of just a fancy way of saying "guesstimate".

@bb010g Disclaimer: I basically don't know Rust, so this is basically a guess.

Isn't "pub fn expose() -> Leak { Leak }" a public function that returns something of type Leak?

Ergo, Leak can't be private?

Ergo removing "pub" from its declaration results in an error?

I have no idea, I'm completely guessing because as I said I basically don't know Rust.

@bb010g In the context of web frameworks, a middleware is (roughly speaking) a pair of functions: one transforms the request before your handler handles it, while the other transforms your response before it is sent back over the network.

Either of these may of course just be the identity function.

So, for example, looking up the logged-in user based on the cookies in the request, and providing that object somehow to the handlers - that's a common use case.