hi there! it’s thursday again. this week was a little light because colin took a couple days off for the first time in [colin thinks very hard about how long it’s been since he last took vacation] probably not good that he can’t remember, but we still made some progress:
- we added filtering for notifications! you can turn on and off different categories of notifications (likes, shares, replies, comments, follows) separately from your notifications page.
- we shipped two-factor authentication! you can turn it on in your user settings if you haven’t already. we can’t emphasize enough that we think you should turn this on if you can.
- we fixed a couple of unexpected issues resulting from the CORS image upload bug that were causing people to be unable to change their avatar or profile pic.
- we made a change to how we generate RSS feeds to improve our compliance with the appropriate standards.
that’s all for this week; one note for anyone writing bots against our unofficial API below the fold. thanks for using cohost!
advance warning of API deprecation
hi there, API users! we’re doing some work to get stuff in shape for our public API release. as part of porting our old APIs to our new API framework, we’re auditing them for which ones are actually used and by whom. we don’t think the following APIs are used by any of the major unofficial cohost API clients (eggbug.rs + cohost.js + cohost.py), so we’re planning to remove them soon:
- GET
/api/v1/project/[handle]/tagged/[tag] - POST
/api/v1/project/[handle]/posts/[post ID]/(publish | unpublish) - GET
/api/v1/project_post/[post ID] - GET
/api/v1/project_post/[post ID]/comments - GET
/api/v1/attachments/[attachment ID]
if we’re incorrect about any of these, or if you have a bot or userscript which uses its own custom API client that uses any of these APIs, please reach out to support@cohost.org to make sure we don’t break it!
