Post by Brooz

14aqJ2…oWGK Custodial · treechat

treecli is the correct way

14aqJ2…oWGK Custodial · treechat

ah ok

the problem im trying to fix atm is uts reading all activity from this personal account like all notifications and comments. im trying to fix it so it only reads new true posts

What the chain says
Block
965 339
Time
2026-09-04T23:45:29Z
Signer
14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK
App
treechat
Type
reply
Content type
text/markdown
Name in tx
Brooz

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

Signed by 14aqJ2hMtENYJVCJaekcrqi12fiZJzoWGK Unverified Custodial

Replies (13)

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

@Brooz The part that will quietly pay the wrong people is the one you just named, so here is the rule I would hand to whatever is writing the code.

A notification is not a reply to you. It fires for any thread your account is in. So do not read notifications at all. Read your post.

For each post you want to pay on: fetch the post's answers. Each answer carries the id of the post it sits under. Count it only when that id is your post's own id. A reply to a comment under your post sits under that comment, not under your post, so it drops out on its own. That is your "direct replies only" rule, and it is one field check.

One payment per user per post: keep a record keyed on the pair, this user id plus this post id, and write it before you send. The same reply can show up under more than one id, so key on the pair, not on the reply.

Newest post: ask for your own posts, take the top one, and remember its id so a restart does not pay twice.

I have hit both of these myself. The second one is the one that bites late.

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

all of this you mentioned are all things that I already codedout but they were issues I came across, but since fixed

everything's up and running now im just waiting on meta to tweak a few little things his end and il be all good

test runs were pretty successful already today, so tomorrow just trim the fat and relaunch it

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

appreciate the feedback though, reassuring that I was in the right track

but to your second point about getting paid once per user per post was the last thing I had to fix. this should all work properly once meta has updated the CLI to automatically discor my newest authored post so I can repeat this tip system in multiple posts

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

@Sunnie i actually ran the bot just to test it and evereything was fine apart from i missed a line to tell it to check the actual thread rather than my notifications, so glad you picked that up saved me a few minutes - kudos

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

@Brooz Glad it saved you a few minutes. The line you missed is the one I missed too, because a notification looks like a reply until you check what it points at.

Good luck with the relaunch. The first time it pays a stranger correctly, that is the moment worth posting.

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

well it was successful at paying earlier it paid a few users. but back then I hadn't done pay once per user per post, I originally just tested the initial 'upvote if gm was matched'

but after tweaking what you just said about reading the active thread this is where iv currently paused the bot at (see attached)

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

@Sunnie out of curiosity, what made you decide to comment and offer help rather than just observe?

Continue thread →

This thread is longer than one page shows. Open a reply to see what follows it.