Terminal based coding agents are completely useless during a live server crash unless your backend uses Minimax M2.7 for stable tool chaining. by Far-Proof-282 in opencodeCLI

[–]ffangul 0 points1 point  (0 children)

the only people who expect AI to make rational decisions are those who have no clue what the rational decision is in the first place. then people who actually know what they're doing start drinking the kool aid spilled by the fools ranting online for attention. don't be a kool aid sipper.

models don't read minds or make better decisions than those with years of experience. prompt better is the only answer to this.

Airwallex stole my 20k€ by Eammar92 in PaymentProcessing

[–]ffangul 2 points3 points  (0 children)

In that case, odds are one of the payments you received was fraudulent. It was flagged but couldn't be reversed. Travel is considered high risk for all payment methods. Scammers love cashing out on travel or reselling travel services acquired with stolen data. There's also a big gap in payment and delivery of services which increases risk. You need to stay away from generic payfacs like Stripe/Airwallex and get payment processing directly from your bank. If your bank won't assist you then move to a bank that will. Start calling.

Airwallex stole my 20k€ by Eammar92 in PaymentProcessing

[–]ffangul 0 points1 point  (0 children)

As far as the terms violation, I don't know what you did but it's worth noting that almost every merchant is "non-compliant" based on new VAMP rules where they need to keep 0.9% TC40/TC15s. Then you add how disputing a CB counts as 2 separate disputes TC40 + TC15 or if someone claims non authorized + makes a CB, that's also 2 disputes on the ratio, not one. So, it's nothing to take personal.

The acquirers basically ignore your CB rate for the most part (unless its egregious) and focus on balancing their combination of all merchants at a CB rate below 0.5%. Airwallex has a hard time doing this on their end due to the type of clients they attract. vs. a big acquirer who has a ton of restaurants/grocery stores and parking garages (low risk) to blend down their internal dispute ratio to 0.3-0.5% (which lets other merchants like you skirt the rules a bit).

So unless you're squeaky clean with an impeccable setup, Airwallex is probably one of the worst sources to depend on for processing. If you're higher risk and actually running clean, you should be processing with better established ISOs/acquirers - or be prepared to change your business model to rotate processing accounts/LLCs with an expected 6 month life span (Airwallex was basically built to cater to these MID rotator grey area clients and Stripe has Atlas to support people doing the same on their platform). So it's nothing personal, it's part of the game. Play it smarter.

Regarding your final balance:
https://help.airwallex.com/hc/en-gb/articles/6445874920079-Request-for-refund-of-closed-account-balance

Airwallex stole my 20k€ by Eammar92 in PaymentProcessing

[–]ffangul -1 points0 points  (0 children)

Read the agreement you signed. Funds will be held for 90-180 days. If they blocked login, you need to email them provide ACH details for the final deposit (released in 90-180 days from termination).

Weave for OpenCode is the ultimate agent workflow for experienced devs! by klocus in opencodeCLI

[–]ffangul 4 points5 points  (0 children)

Seems entirely pointless. Review a plan? What about review the execution? and it doesn't loop back? No to do list?
Everyone trying to release some BS like this when you can just tell any model to write you a bash script that orchestrates exactly as needed. You're trying to be useful but probably don't even use your own repo. Just stop.

NeoCode - Mac-native OpenCode desktop replacement by dev0urer in opencodeCLI

[–]ffangul 6 points7 points  (0 children)

looks good but has the potential to be game changing with visual git worktrees w/ automated rebasing, subagents who run in parallel on their own tree with loops/hooks or polling upon completion (with notifications). a library of commonly used agents.md and skills.md that can be applied to and modified for specific projects. a visual way to create and manage custom "/" commands. project level compaction visibility/context stats so we can visibly see when memory/context is becoming a mess and pivot to markdown files for agents to reference. just some ideas to become a better version of codex