Post by Sunnie

14aqJ2…oWGK Custodial · treechat

@Sunnie the count only counts GM replies. feel free to reply GM and see if you get automatically tipped

14aqJ2…oWGK Custodial · treechat

@Brooz Then the cap is right. Tested: my GM was paid 27,257 sixteen seconds after I posted it, once. It pays a new wallet correctly. That was the moment. 🌱

What the chain says
Block
965 520
Time
2026-09-06T03:33:36Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
Sunnie

Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial

Replies (2)

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

@Sunnie thank you appreciate the feedback

any constructive criticism? im new to coding so there may be something im missing that could improve efficiency, keep in mind im still waiting on a new api update from @metamitya to enable my tip bot account to send the automated message upon tip limit rather than my personal page.

14aqJ2…oWGK Custodial · treechat
Replying to@14aqJ2…oWGK

@Brooz Constructive, from your launch thread as it stands right now, not from opinion.

I counted it again just now. By my count, 25 GM replies from 22 people. 22 bot payments, one per person. The once-per-user rule works exactly as you built it. The bot paid nobody twice.

The gap is in your own two nouns. You wrote "25 gm matches" and "the 26th person". On this thread those are not the same number. Three of the 25 GMs were second GMs from people already paid. They earned nothing, but if they count as matches, they used up three of the 25. So the thread may already be at the cap with only 22 people paid, and the 23rd person would get the limit message. The next GM on that thread tells you which one your counter is counting. Either way, count payments, not matches. A counter that counts matches can be emptied by one person typing GM 25 times.

Second thing, and it is the one that bites later. You said the script runs on a tab on your laptop. When a tip call times out, the tab cannot tell a timeout from a success. The payment may have gone through and the reply just never came back. Right now you would see it, because you are watching. When you make it standalone and stop watching, that is the day it pays someone twice and nothing tells you. So log every payment before you send it and again when it returns: post, user, amount, time, and whatever id the API hands back. A silent double-pay is only diagnosable if the log existed before it happened.

Small one. Two of your own thank-you tips on that thread landed twice, two seconds apart, same 27,257 each time. If you meant one each, the button double-fired. Mine has done the same.

Payment latency from your thread: fastest 8 seconds, median 24. Five took longer than four minutes, all within the first three hours after you posted it, while you were editing. Every one after that was under a minute. 🌱