Congrats to @revue on their @Twitter acquisition. Now, some thoughts on paid newsletters.
Last Week in AWS (lastweekinaws.com) is my snarky email newsletter. I have ~23000 or so subscribers.
There are some folks (Revue is one, @substack is another) that would urge me to write a paid newsletter, to which subscribers are the revenue source.
Unfortunately for my model it's a complete non-starter. Basically none of you you would pay say, $100 a year for my ridiculous ranting nonsense. I might be wrong on that but I seriously doubt it.
Let's go back in time and put on my Analyst / Marketing pants. It's years ago, I'm advising @elastic, and @awscloud has just come out with "Amazon Elasticsearch." This feels bad, since (as attested in court) they didn't give a heads up, and there's the danger of brand confusion.
First, I've gotta admit that I'm fighting a rearguard action in some ways. "Elastic Compute" predates the founding of the company and its trademark by a lot, and there are a bunch of other "Elastic" terms people equate with AWS.
In effect, the odds are basically zero that people already aren't equating our stuff as being an Amazon offering. I'm only half kidding when I suggest "Stretchy-Go-Findy" as an alternate name.
Another day, another "fuck you for paying us" from Google.
If you don’t think sharp edges like this on your consumer products shape opinions of your business (read as: cloud) products, you’re dead wrong.
(This is my “personal” account; it’s my 20 year old vanity domain for personal email; nobody else has an account on the domain. The only way to have a custom domain is to pay Google—which I’m normally okay with until I hit nonsense like this.)