This will be extremely useful for getting new users on board right away, so we don't want to charge for it. It's also not necessary for already-launched 2.0 / #collections_sprint

No current demand for webhooks.

Finished a manual import utility for Ghost tonight. Should be able to use it as a starting point for future integrations.

This wouldn't really solve anything significant, so closing.

Still fairly low-impact at the moment. No recent reports of this being a problem.

This isn't really necessary; even Tor users usually have JS enabled, and we haven't heard any requests for this in 1.5 years. Plus it would diminish the future-editing features, and just create a worse product we really don't need to have.

Still really needs attention, but is second to our other current tasks.

This is fairly straightforward to implement, so will be one of the first new Pro features to go with our new (higher) pricing.

Available here: https://guides.write.as/security/

Synced posts functionality mentioned here moved to {T402}

Paging functionality mentioned here moved to T401: Post list paging

Serious usability issue.

This doesn't match the product vision and would add unnecessary complexity. Might be better for another product.

This will be great, but will require some deliberate thought (and ideally some input from someone who knows what they're doing).

Our more privacy-focused users definitely want this, so boom.

Now that T306: Use Piwik for analytics is done, we know we're compliant.

As of today, 13 out of 5,355 active posts have at least one embed view. We're going to remove the links from posts and keep supporting embeds, but not offer any extra functionality around it.

Actually occurs before publishing. But this is finished.