Still fairly low-impact at the moment. No recent reports of this being a problem.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jun 7 2017
May 31 2017
May 2 2017
May 1 2017
Tracking on GitHub: #9
This is probably more trouble than it's worth. Since I've only heard from one user seeing this, solving is probably better spent on better documentation than a technical solution.
Tracking on GitHub #10
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.
Maybe this should be more of a "preview" button, instead.
Accessible at /photos for now.
Still really needs attention, but is second to our other current tasks.
In T234#6480, @matt wrote:Growing Paste.as isn't in line with our current larger vision for our products anymore, especially for becoming financially sustainable. Creating a Tor hidden pastebin service isn't where we want to go or spend our time.
This is fairly straightforward to implement, so will be one of the first new Pro features to go with our new (higher) pricing.
This was feedback from only one person (when I created this task), but we haven't heard of anyone else having this problem. So closing for now.
Available here: https://guides.write.as/security/
Oct 31 2016
Oct 30 2016
Oct 16 2016
Synced posts functionality mentioned here moved to {T402}
Paging functionality mentioned here moved to T401: Post list paging
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.