Micro.blog

In reply to
amit
amit

What are the recommended, non-tech, non-news newsletters? Other than NextDraft, of course. I have realised the newsletters I subscribe to tend to get repetitive. I do not want to know of the thoughts on same tech/non-tech US news 🙂

alans
alans

@amit I appreciate Charlie Loyd’s newsletter: tinyletter.com/vruba/. He writes about maps, climate, and lots of interesting things. He publishes less regularly than he did a couple of years ago, but there is a lot of good stuff in his archive.

amit
amit

@alans Nice, thank you Alan. I had not heard about the newsletter - I just browsed through the archive, they do look interesting 👍

vasta
vasta

@amit I love Austin Kleon's newsletter on creativity, Bello Collective's newsletter on podcasts, Gastro Obscura's newsletter on food history, Laura Olin's newsletter on lovely things, LitHub's newsletter on literature, and so many more! And of course, my favorite newsletter of all: Pome.

ChrisJWilson
ChrisJWilson

@vasta oh some new ones to check out!

kordumb
kordumb

@amit Craig Mod's new Ridgeline, Warren Ellis' Orbital Operations, and Robin Sloan's Year of the Meteor are my current favorites. Also notable, Patrick Tanguay's Sentiers, Kai Branch's Dense Discovery, and Electric Eelfrom MCD x FSG publishing.

amit
amit

@vasta Ah, that's a great set of recommendations. I am already following Austin Kleon's newsletter. All others are new to me. And talking about really diverse interests. Thank you Sameer! 🙂

amit
amit

@kordumb Thank you Kevin. All these are new to me. I heard about Dense Discovery recently, I guess via @patrickrhone. But everything else I never did. I really like the list 👍🙂

patrickrhone
patrickrhone

@amit FWIW, I have a newsletter too: tinyletter.com/patrickrh...

amit
amit

@patrickrhone Oh yes, of course. Thank you for reminding me, Patrick. Subscribed 👍🙂

amit
amit

On the topic of recommended newsletters, I know a lot of people I interact with on micro.blog also publish their own newsletters. I am keen to know about and subscribe to them. They always come across during discussions, but I miss to note them then. I would like to fix that.

vasta
vasta

@amit I have a newsletter I send fortnightly, but it’s just a repost of my fortnightly “weekend reading” blog post. :)

nathanrhale
nathanrhale

@amit My newsletter reads kind of like a personal letter/journal, with some links and resources. I’m just getting started and figuring it out as I go.

Gabz
Gabz

@nathanrhale ha! I need to play with this idea.

juliansummerhayes
juliansummerhayes

@patrickrhone and it’s excellent 👌

cm
cm

@amit I really like the Studio Neat Gazette. It's a short weekly newsletter from some nice product design type folks.

patrickrhone
patrickrhone

@juliansummerhayes Thank you.

jw
jw

@vasta yay Pome! I wonder if perhaps I got that from you, originally? 😍

vasta
vasta

@jw Maybe? I’ve been extolling its virtues on Twitter, and in my weekend reading posts occasionally, for about two years now. Such a lovely burst of joy in my inbox.

stevepbrady
stevepbrady

@kordumb I'll second Warren's. One of my favorites as well

herself
herself

@amit I have a question about this too...how do you all (who run a newsletter) differentiate between your blog and your newsletter? How do you decide what goes into the blog and what you save up to write about in the letter? I’m keen as hell to start one but I’m stumped by this seemingly simple block 🤔

Cheri
Cheri

@kordumb I love Orbital Operations!

amit
amit

@herself Yeah, am curious about the same. My intention behind the weekly digest was very much to explore if I can draft weekly newsletter-like posts. But it indeed is tricky to decide. Any inputs welcome.

amit
amit

Thank you all for the wonderful recommendations for newsletters - the community here never disappoints. As I had noted earlier, I did capture all the recommendations from this discussion at Micro.threads so that it can be referenced in future too.

vasta
vasta

@amit Oh, thank you! Very glad you captured them all in one place—great place to discover new newsletter.

vasta
vasta

@herself I made the decision that only my "weekend reading" posts would be shared on the newsletter. (They are, in essence, my fortnightly recaps.) For everything else, I encourage people to visit the blog, but also link to my previous blog posts in the fortnightly weekend reading recaps. Was a natural delineation between blog and newsletter for me, but still alleviated the need for a whole other thing to write. :)

jeremycherfas
jeremycherfas

@herself Some people send the newsletter out before posting to the web. I more or less duplicate. Mine is all links, and I am thinking of saving my view of them for the newsletter.

herself
herself

@jeremycherfas interesting! So it’s more of a blog-digest, I guess?

jeremycherfas
jeremycherfas

@herself Not quite. It is related to my podcast. So that goes out every two weeks. I'm scanning all sorts of places for interesting stories every day. Some of those I accumulate and send out as a newsletter in between podcast episode weeks. So, here it is on site and almost identical content goes out via email. I'm thinking of just posting the bare links on site and giving slightly more context via email.

I'd be interested to learn what you think of that idea.

herself
herself

@vasta I like that idea! So you can stay on-topic that way, never getting to the point where you can’t decide where to put something.

herself
herself

@jeremycherfas that’s a nice point of distinction, I think. The newsletter can be more “newsy.” :) As an aside, your podcast looks really cool! Will have a listen today.
https://micro.blog/amit/2178369
micro.blog
crawl=CC-MAIN-2019-18
56031
application/http; msgtype=response
sha1:RVR4JXSCRHY5QFPRGILTITHGWE4ST3IX
<urn:uuid:d5b012ca-b06c-4b14-a143-3524dbe7be25>
2019-04-24T19:58:17Z
104.200.22.215
text/html
sha1:XBBJVHI5KEUFXC373MW2YR6BE2GOJCDV
<urn:uuid:4de48b09-e5e6-4b1e-90a3-716d62e6ec7a>
https://micro.blog/amit/2178369
response
<urn:uuid:e5a4c8be-5df7-4d58-b623-4f312f70eea6>
isPartOf: CC-MAIN-2019-18
publisher: Common Crawl
description: Wide crawl of the web for April 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-150-136-47.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/