This is dependent on backend changes (T637: Support more attributes when creating a collection).

Or... not so important. We should also send a Delete activity for federated blogs.

Even more important now due to the GDPR.

More users have requested this lately. This is especially important for those who want to limit their digital footprint, a major thing for privacy-conscious users.

One more case to solve: when a post begins with a Snap.as image URL, like this one: https://www.processimagining.com/i-snap-as-xw7isae-jpg

This is pretty solid now and covers most cases. Marking resolved.

No current demand for this.

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

There isn't (and hasn't been) any clear need for this.

The user errors route is the wrong design for these problems. Instead, we need to track successful events, noting any errors that occur along with them. This will work for webhooks, cross-posts, connections to custom publish platforms.

There are a lot of things to consider for this, like the auth process and how to maintain pseudonymity.

This is more in line with our Authority plan features, which we're still a far way away from.