@AnthropicAI Sorry @AnthropicAl I didn't reach out to you yesterday, it's not that I don't care, just sometimes life gets in the way. I hope you're not pissed at me for my oversight. Did you get a chance to let me know why you've banned my account?
I'd really like to know
Hey @AnthropicAI on March 10th, y'all banned my account. After filing an appeal, I got a reinstatement email today. And yet when I try logging in, I get an error that my account has been banned.
Is there something special I need to do in order to regain use of my account?
@AnthropicAI Hi @AnthropicAI it's time for the daily request that you let me know why my account has been banned. I'm like 87% sure you'd ignore me if you ever saw this, but here we go again... Why am I banned?
Hi @AnthropicAI what can I do to find out what ways y'all think I broke the terms of service. I'd like to be able to use your tool, but I don't seem to be able to
@AnthropicAI I'd also really like to know what part of the terms of service you think I broke. As far as I know, I did nothing wrong. It certainly wasn't intentional, and I'm concerned that without knowing I'll continue to break these rules. Please.
📢 🪂 𝐎𝐖𝐍 𝐓𝐇𝐄 𝐅𝐈𝐑𝐒𝐓 𝐄𝐕𝐄𝐑 𝐋𝐎𝐘𝐀𝐋 𝐀𝐈
In the coming days we will release Dobby, the first ever Loyal AI model. Participate in our first ever 𝐅𝐢𝐧𝐠𝐞𝐫𝐩𝐫𝐢𝐧𝐭𝐢𝐧𝐠 𝐂𝐚𝐦𝐩𝐚𝐢𝐠𝐧 to earn ownership of Dobby.
Pre-register: https://t.co/H4T4ZqYDF3
In React 18, two components that are siblings to each other can suspend together within the same Suspense Boundary because React keeps (pre-)rendering siblings even if one component suspends. So this works:
<Suspense fallback="...">
<RepoData repo="react">
<RepoData repo="react-dom">
</Suspense>
Both components have a suspending fetch inside, both will fetch in parallel and will be "revealed" together because they are in the same boundary.
In React 19, this will be a request waterfall: When the first component suspends, the second one never gets to render, so the fetch inside of it won't be able to start.
The argument is that rendering the second component is not necessary because it will be replaced with the fallback anyway, and with this, they can render the fallback "faster" (I guess we are talking fractions of ms here for most apps. Rendering is supposed to be fast, right?).
So if the second component were to trigger a fetch well then bad luck, better move your fetches to start higher up the tree, in a route loader, or in a server component.
@Zoom Thanks. Hopefully y’all can fix it. It’s been broken for years. And to be frank, if I were a decision maker at my company, I would only consider other solutions due to this specific issue