That doesn't make any sense because the revenue is already booked for the sale which has nothing to do with when the delivery truck actually arrives.
Cash vs Accrual
Readit Newsanxman commented on US SEC preparing to scrap quarterly reporting requirement reuters.com/business/fina... · Posted by u/djoldman
anxman commented on Dulce et Decorum Est (1921) poetryfoundation.org/poem... · Posted by u/bikeshaving
anxman commented on Your Supabase is public if you turn off RLS skilldeliver.com/your-sup... · Posted by u/skilldeliver
To store application-specific data about users. The Supabase doc or examples show this. Where else would you put such data?
But what the docs don't cover is the provided Users table. Missing documentation is why I gave up on Supabase; and the Users table was one of the first problems I encountered. I could find no details on what to expect in each column at any given time.
Upon creating a new user, values get set in this table for no apparent reason. So if your application depends on knowing the verification status of a new user (for example), good luck... Supabase claimed every user was verified upon creation.
https://supabase.com/docs/guides/auth/auth-hooks
These have gotten much less annoying to use now that it’s controlled through the config.toml.
anxman commented on Your Supabase is public if you turn off RLS skilldeliver.com/your-sup... · Posted by u/skilldeliver
To store application-specific data about users. The Supabase doc or examples show this. Where else would you put such data?
But what the docs don't cover is the provided Users table. Missing documentation is why I gave up on Supabase; and the Users table was one of the first problems I encountered. I could find no details on what to expect in each column at any given time.
Upon creating a new user, values get set in this table for no apparent reason. So if your application depends on knowing the verification status of a new user (for example), good luck... Supabase claimed every user was verified upon creation.
The auth schema is intentionally not exposed to the rest api for security reasons. You need to use an auth hook to put data where you need, or an RPC with appropriate privileges, and of course RLS on any tables.
anxman commented on Your Supabase is public if you turn off RLS skilldeliver.com/your-sup... · Posted by u/skilldeliver
Supabase doesn’t make a public users table by default. The user schema is in auth and secured. The problem is that unskilled developers bypass those controls out of convenience and put data into Public without RLS. Even the Supabase docs warn against this.
anxman commented on Ask HN: My mother was scammed out of all her savings. What should I do? · Posted by u/scapbi
I think this problem should be solved politically/legally first, technology can easily track money as you know.
How are scammers able to operate bank accounts without leaving any traces, and why don’t the police and banks have the power to reverse transactions that are obviously fraudulent.
It's actually more complicated, but the draining of scam money at scale (ie: billions) is done with the help of collaboration of the Triads and Mexican cartels. IE: Chinese scammers rob the world of billions. They ultimately end up with tons of crypto but still need to launder it. They collaborate with the Mexican cartels to buy USD cash from them paid via crypto. Then the Triads re-launder that cash or sell it to other Chinese nationals in the USA.
anxman commented on Ask HN: My mother was scammed out of all her savings. What should I do? · Posted by u/scapbi
I think this problem should be solved politically/legally first, technology can easily track money as you know.
How are scammers able to operate bank accounts without leaving any traces, and why don’t the police and banks have the power to reverse transactions that are obviously fraudulent.
Crypto
anxman commented on Microsoft won't let me pay a $24 bill, blocking thousands in Azure spending · Posted by u/Javin007
Do you have to use Azure? Maybe Azure is nice and signaling this way the state of the internals and how things will work from here on. So it's sneakily trying to help you move to somewhere else, before things become worse and you spend the thousands and then end up stuck.
If you want to sign Windows binaries, Azure is the best way now.
On Aug 27th 2025, Braintree (owned by PayPal) introduced a policy that forces merchants to accept pre-arbitrations for disputes under $1,000:
https://developer.paypal.com/braintree/articles/risk-and-sec...
I’ve been a PayPal/Braintree merchant for over 10 years, and this feels like a pretty big shift in risk.
For anyone not deep into disputes:
- A customer files a chargeback. - The merchant can submit evidence and may win that first round. - The customer can then file a second dispute, which goes into pre-arbitration. The merchant can again submit evidence and, historically, sometimes win.
If either side pushes further, it goes to arbitration, where there’s usually a few-hundred-dollar fee for the losing side.
Under this new policy, for transactions under $1,000, Braintree will automatically accept the pre-arbitration in favor of the customer. There’s no second chance to present your side as the merchant; the dispute is simply closed and refunded to the cardholder.
Practically, this means:
- A customer can lose the first dispute, - Immediately escalate, - And automatically win the pre-arbitration if the transaction is under $1,000.
I’ve already had multiple cases where bad-faith customers was awarded the full amount at pre-arbitration solely because of this rule. At that point, the only remaining recourse is to pursue the customer directly (legal action, collections, etc.), which is usually not realistic for sub-$1k orders.
For anyone running ecommerce on Braintree, this effectively creates a “free second shot” at a dispute for customers under $1k, with the merchant guaranteed to lose the second round by policy.
Has anyone else run into this yet?
Use Stripe?
Not sure if the op is reading, but I also detected the same Coinbase hack around the same timeline. From what I can tell, literally everything was compromised because even their Discord channel's api keys were compromised and were finally reset around April or May. This means their central secrets manager was likely compromised too.