New in Labs: Email Subscriptions

writeas

#21

I am not sure about that, because I only recently discovered the perks of posting anonymous (being able to ‘preview’ and edit before it shows on my blog). I am quite sure these scheduled post were not anonymous, but not 100% sure… sorry. But, if the issue is fixed I trust it will work. If not, I will let you know.


#22

Hi @matt - tested it again and the post I scheduled for today appears on my blog, but not in my e-mail. I created an anonymous post first, edited it, changed scheduled time and then moved it to blog. Hope this is of any help?


#23

Ok, it seems to be a spam-issue with G-Mail - it marks the messages as spam, but not always, which is weird? (But hey, why be surprised?)
Anyway, I have taken care of it now and told the mighty AI to treat this mail nice. I hope it will all be good now.
If not, I will let you know, of course.

@matt - edit: no, still the same regarding scheduled posts:

  • anonymous post, changing schedule time, moved to blog: does not appear in my inbox.
  • copied the post-txt, pasted it into a new blog-post, published straight away: 15 mins later it appears in my inbox.

#24

Hi @matt :wave:t2:

I’ve just signed up and immediately became a paid user just for this!
Made me incredibly happy to see this feature land in write.as :tada:

I’ve got one recommendation and one question.

:nerd_face:Recommendation :
Based on previous experience with other email subscription providers, if the initial confirmation email is sent using a different name than the blog’s name, people generally don’t confirm signing up to mailing lists.

Currently the confirmation email’s sender name is “Write.as Letters” instead of the blog’s own name, and this will leave many users confused about what’s going on, particularly with custom domain blogs. (Since the only write.as reference they’ll see if they’re attentive is going to be in the footer)

Ideally, it would be fantastic if you guys can use the blog’s own name in the sender-name field of the email, especially for custom domain blogs.

:thinking:Question :
Is the 500 subscribers limit a hard api limit? If not, can you increase it if I reach out to you with my username? I’ll be using write.as for my product’s announcements & news blog, and I have reasons to believe this quota will quickly fill up as soon as start pointing my users to the blog to follow product updates etc.

Many thanks for Write.as & the email subscription addition you’re are bringing. This is a fantastic service combination, and I hope branching out to multiple other mini-side/future-projects won’t slow you down / distract you from making write.as even better each and every day. :v:t2:

All the best,
John


#25

Hey @ozbay, that’s awesome to hear! :smile:

Great recommendation – I just changed it so the confirmation email now shows the name of the blog as the sender. Just note that for now it’ll still come from yourblog@writeasletters.com – we’re still working on full custom domain support.

That’s exciting that you’ll be using Write.as for your product news / announcements! The 500 subscriber limit is soft – no one will get cut off for going a little bit over it. But in the future, we’ll charge for having more subscribers than that, to cover our own costs, which go up with the amount of email we send out.

So if you want to be sure that you don’t hit any limits, I’d recommend upgrading to our Support tier. That’ll give you an essentially unlimited subscriber limit*, and we’ll pay special attention to your account to make sure your list growth goes smoothly. You’ll also get custom domain support on your emails when that’s available.

Thanks again for the input, and keep us in the loop with feedback as you keep trying everything out!

* As an early user of this feature, before we have a pricing model for >500 subscribers, I’m happy to keep the number of subscribers unlimited for anyone on the Support tier.


#26

Sorry for the delayed response – there is still an issue with posts not being emailed when following this flow: anonymous post -> move to blog. Working on a fix now.