There’s been a bug for a week or two where we were failing to properly handle some Stripe webhook events. I’ve now ported that hook from the Python API to the new Node API and confirmed that it works, which should mean our registration process isn’t subtly broken anymore. (Yikes!)
This morning I pushed some updates to our charge email handler to get us better debug info in cases where we fail to mark tasks as contested when users reply to charge emails. Also I think I may have fixed a bug with said worker from a previous attempt.
Updated the meta description for TaskRatchet.com so it includes relevant text when shared on Discord, etc. Though seems like Discord has cached the previous site description, so may take a while to display properly.
Updated the “why don’t you have x feature?” section on the faq to say it’s built and maintained by two part-time devs instead of one dev like it used to say
Added Forfeit to our Friends & Competitors page
Changed the wording under “Calling a Charge Not Legit” from “I’ll” to “we’ll”
Updated “When does TaskRatchet charge me?” in the FAQ to stop referring to me in the singular
Added Amazing Marvin to the Commitment Contracts section now that they’ve added a monetary stakes feature.
Updated the last paragraph in How It Works:
Made some minor copy edits to the API, FAQ, and How It Works pages
Corrected links to full document history on the privacy policy and terms of service pages
Set up basic Honeycomb observability, and added it to the list of subprocessors in the privacy policy
Made an embarrassingly small punctuation fix.
Removed an outdated link to the old docs repo from the Open Source page. The docs are now stored in the same repo as the landing page, taskratchet/taskratchet.com
With the help of a user (thank you so much!) I fixed a bug where making POST requests to create new tasks was sometimes not working via the API.
The “Enable Beeminder integration” link in the web app was nearly unreadable in dark mode. It should now be much better.
There was a bug that prevented the login screen from immediately appearing when you were logged out. Now fixed!
Could you tell us what changed in the API for this? I’ve had no success with POST requests over the past couple of days and I think it may have started about the time you made this change.
I used to be able to use code like the sample below, but now it tells me “Missing task
, due
, cents
field(s)”
curl -X POST \
-H "X-Taskratchet-Userid: xx" \
-H "X-Taskratchet-Token: xx" \
-d "task"="task_name_here" \
-d "due"="8/7/2024, 11:59 PM" \
-d "cents"=500 \
https://api.taskratchet.com/api1/me/tasks
Yikes yikes yikes! Will try to get on this today. Thank you for letting me know it broke for you now!
@alys I’ve pushed a fix which I think should address the problem you’re running into. Can you try again and see if it’s still broken?