Features
Feature requests across all Fernpost products
Paid SubscriptionsAnonymousI'd move over tomorrow if I could charge for the Sunday issue. Free issues public, paid issues for members, and Fernpost handles the payment side.
FernpostUnder ReviewExport Signup SourceTomExport gives me emails and dates but not where anyone came from, which is the one thing I actually want to look at.FernpostUnder ReviewA Second WriterHanaMy partner writes about a third of the issues and at the moment that means sharing my password, which I know is wrong and do anyway. I don't need roles or permissions. Two people, both able to write and schedule, would be plenty.Support Team Sharing a password because the product left you no other option is a product problem, not a you problem. I'm doing the simple version you described rather than a permissions system: invite by email, they get their own login, and the issue records who wrote it. That last part matters more than it sounds when you're looking back at something from six months ago.FernpostIn ProgressBring Back AutopostRosaThe old version posted each issue to my socials when it sent. It disappeared in 1.6 and nothing in the release notes explained why.Support Team You're right that removing it without a word was poor, so let me correct that here. Autopost worked for about four months and then stopped, twice, because two of the networks changed how posting works and both times I found out from a customer rather than from a changelog. Between the outages it was the most complained-about part of Fernpost, and it was never the reason anyone bought it. So it is not coming back. What is there instead is a webhook on send, which anything like Zapier or Make can pick up, and that keeps the breakage on a service whose whole job is to keep up with these changes. I should have written this in the 1.6 notes rather than letting you find it missing.FernpostDeclinedPause a SchedulePriyaI go quiet in August. At the moment the only way to stop the queue is to delete every scheduled issue and build the whole schedule again in September, which is an evening gone. A pause switch that keeps the queue would save all of it.Support Team Most-asked thing on the board, and I agree with it. Planned for the autumn. The reason it isn't done already is that "paused" has to mean something sensible for an issue whose send time passes while you're away. I'd rather decide that properly than ship a switch that quietly drops things.FernpostPlannedOpen Rate TrackingDeleEvery other tool I've used reports opens. I'm not chasing the number for its own sake, I just want to know whether the Sunday issue lands better than the Thursday one.Support Team No to this one, and I'd rather say why than leave it sitting open. Open tracking works by hiding an image in your issue and logging who loads it. Your readers don't know it's there and can't turn it off, and the number is wrong often enough to be misleading either way: an image blocker reads as unopened, a preview pane reads as opened. The question underneath it is a good one though. Sunday against Thursday is answerable from clicks, which are something a reader actually chose to do, and those are already in your export. If a chart would be more use than a spreadsheet, open that as its own request and I'll look at it properly.FernpostDeclinedBuilt-in AI DraftingAnonymouswould be good if it could write the issue from a few bullet pointsSupport Team I'm going to say no to this, and I'd rather explain than leave it sitting open for a year. Fernpost is one person. If I add drafting then I'm maintaining a writing tool as well as a scheduling tool, and the scheduling is what gets worse for it. There are good tools for the writing part already and everything you write in them pastes in fine. If that changes I'll come back to it. I just don't want to leave this open and imply it's coming.FernpostDeclinedRSS for the ArchiveLarsSome of us still read in a feed reader. Every other newsletter tool publishes a feed and it's usually two lines of code.Support Team Agreed, and it should have been there from the start. Adding it.FernpostCompleted
FernpostUnder ReviewExport Signup SourceTomExport gives me emails and dates but not where anyone came from, which is the one thing I actually want to look at.FernpostUnder ReviewA Second WriterHanaMy partner writes about a third of the issues and at the moment that means sharing my password, which I know is wrong and do anyway. I don't need roles or permissions. Two people, both able to write and schedule, would be plenty.Support Team Sharing a password because the product left you no other option is a product problem, not a you problem. I'm doing the simple version you described rather than a permissions system: invite by email, they get their own login, and the issue records who wrote it. That last part matters more than it sounds when you're looking back at something from six months ago.FernpostIn ProgressBring Back AutopostRosaThe old version posted each issue to my socials when it sent. It disappeared in 1.6 and nothing in the release notes explained why.Support Team You're right that removing it without a word was poor, so let me correct that here. Autopost worked for about four months and then stopped, twice, because two of the networks changed how posting works and both times I found out from a customer rather than from a changelog. Between the outages it was the most complained-about part of Fernpost, and it was never the reason anyone bought it. So it is not coming back. What is there instead is a webhook on send, which anything like Zapier or Make can pick up, and that keeps the breakage on a service whose whole job is to keep up with these changes. I should have written this in the 1.6 notes rather than letting you find it missing.FernpostDeclinedPause a SchedulePriyaI go quiet in August. At the moment the only way to stop the queue is to delete every scheduled issue and build the whole schedule again in September, which is an evening gone. A pause switch that keeps the queue would save all of it.Support Team Most-asked thing on the board, and I agree with it. Planned for the autumn. The reason it isn't done already is that "paused" has to mean something sensible for an issue whose send time passes while you're away. I'd rather decide that properly than ship a switch that quietly drops things.FernpostPlannedOpen Rate TrackingDeleEvery other tool I've used reports opens. I'm not chasing the number for its own sake, I just want to know whether the Sunday issue lands better than the Thursday one.Support Team No to this one, and I'd rather say why than leave it sitting open. Open tracking works by hiding an image in your issue and logging who loads it. Your readers don't know it's there and can't turn it off, and the number is wrong often enough to be misleading either way: an image blocker reads as unopened, a preview pane reads as opened. The question underneath it is a good one though. Sunday against Thursday is answerable from clicks, which are something a reader actually chose to do, and those are already in your export. If a chart would be more use than a spreadsheet, open that as its own request and I'll look at it properly.FernpostDeclinedBuilt-in AI DraftingAnonymouswould be good if it could write the issue from a few bullet pointsSupport Team I'm going to say no to this, and I'd rather explain than leave it sitting open for a year. Fernpost is one person. If I add drafting then I'm maintaining a writing tool as well as a scheduling tool, and the scheduling is what gets worse for it. There are good tools for the writing part already and everything you write in them pastes in fine. If that changes I'll come back to it. I just don't want to leave this open and imply it's coming.FernpostDeclinedRSS for the ArchiveLarsSome of us still read in a feed reader. Every other newsletter tool publishes a feed and it's usually two lines of code.Support Team Agreed, and it should have been there from the start. Adding it.FernpostCompleted