adam/nntpchan
1
0 Fork 0
mirror of https://github.com/tomoko-dev9/nntpchan.git synced 2026-11-08 11:32:32 +01:00
Code Issues 10 Packages Projects Releases Wiki Activity

Successful posting gives 200 OK #39

New Issue
Closed
opened 2026-10-05 03:09:24 +02:00 by adam · 10 comments
adam commented 2026-10-05 03:09:24 +02:00
Owner
Copy link
Copy source

It should be sending back 201 CREATED, this makes it hard to differentiate between an incorrect CAPTCHA and a successful post.

It should be sending back 201 CREATED, this makes it hard to differentiate between an incorrect CAPTCHA and a successful post. <!-- github-sync-id:179725354 -->
adam closed this issue 2026-10-05 03:09:24 +02:00
adam commented 2026-10-05 03:09:25 +02:00
Author
Owner
Copy link
Copy source

try latest revision of backend, run ./build.sh

try latest revision of backend, run `./build.sh` <!-- github-comment-id:250144676 -->
adam commented 2026-10-05 03:09:25 +02:00
Author
Owner
Copy link
Copy source

I would but postgres is giving me a headache, I'm assuming you've already fixed this though? In that case, when will the fix be pushed as an update to the nodes?

I would but postgres is giving me a headache, I'm assuming you've already fixed this though? In that case, when will the fix be pushed as an update to the nodes? <!-- github-comment-id:250935471 -->
adam commented 2026-10-05 03:09:26 +02:00
Author
Owner
Copy link
Copy source

the only meaningful change iirc was for this issue.

the only meaningful change iirc was for this issue. <!-- github-comment-id:250937208 -->
adam commented 2026-10-05 03:09:27 +02:00
Author
Owner
Copy link
Copy source

Can you get at least the biggest nodes to change over? Because right now not knowing if a CAPTCHA has gone through is a bit of a problem for the client I'm writing. Sure, I could check the text of the response but that's hacky and might change between nodes.

Can you get at least the biggest nodes to change over? Because right now not knowing if a CAPTCHA has gone through is a bit of a problem for the client I'm writing. Sure, I could check the text of the response but that's hacky and might change between nodes. <!-- github-comment-id:250939897 -->
adam commented 2026-10-05 03:09:28 +02:00
Author
Owner
Copy link
Copy source

Honestly if you can figure out how to get everyone to upgrade religiously that would help a LOT.
at the moment it's not a reasonable thing to ask of me since people are sticking to "working" revisions.

I can upgrade oniichan and/or 2hu but the others you'd have to figure out when they'll upgrade.

Honestly if you can figure out how to get everyone to upgrade religiously that would help a LOT. at the moment it's not a reasonable thing to ask of me since people are sticking to "working" revisions. I can upgrade oniichan and/or 2hu but the others you'd have to figure out when they'll upgrade. <!-- github-comment-id:250940155 -->
adam commented 2026-10-05 03:09:28 +02:00
Author
Owner
Copy link
Copy source

If 2hu and oniichan are updated that'd be good enough for me for now, I'll just go complain to the other node owners.

If 2hu and oniichan are updated that'd be good enough for me for now, I'll just go complain to the other node owners. <!-- github-comment-id:250940214 -->
adam commented 2026-10-05 03:09:29 +02:00
Author
Owner
Copy link
Copy source

both have been updated

both have been updated <!-- github-comment-id:250942025 -->
adam commented 2026-10-05 03:09:30 +02:00
Author
Owner
Copy link
Copy source

That works, thanks 👍

That works, thanks :+1: <!-- github-comment-id:250957874 -->
adam commented 2026-10-05 03:09:30 +02:00
Author
Owner
Copy link
Copy source

Honestly if you can figure out how to get everyone to upgrade religiously

Botnet a la Microsoft obviously.

> Honestly if you can figure out how to get everyone to upgrade religiously Botnet a la Microsoft obviously. <!-- github-comment-id:251437457 -->
adam commented 2026-10-05 03:09:31 +02:00
Author
Owner
Copy link
Copy source

adding an update hook may work but it adds centralization and needs to be opt in.

looks like this bug is fixed tho

adding an update hook may work but it adds centralization and needs to be opt in. looks like this bug is fixed tho <!-- github-comment-id:251451251 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/nntpchan#39