ph4te · HackerTrans

As a CC power user, an OpenClaw, and ZeroClaw user, I am completely fine with this. My CC usage has suffered lately, and however cool and fun the Claws are, I use Claude Desktop probably more than OpenClaw and it works just fine, and has a lot of integrations. I would rather have Anthropic continue to support its own products working well, and have all of these things move to another service, or pay Anthropic for their use.

ph4te

6 ay öncediscuss

I don't know how big sufficiently large codebase is, but we have a 1mil loc Java application, that is ~10years old, and runs POS systems, and Claude Code has no issues with it. We have done full analyses with output details each module, and also used it to pinpoint specific issues when described. Vibe coding is not used here, just analysis.

ph4te

2 yıl öncediscuss

https://wasabi.com/glossary/egress-charges

Wasabi doesn't have an egress hard limit and doesn't charge for egress. You get consistent pricing, and if you need to recover everything, it's not an issue at all, and you won't pay for it.

"The reasonable use egress policy indicates that if your monthly downloads (egress) are greater than your active storage volume, then your storage use case is not a good fit for Wasabi’s free egress policy, and we reserve the right to limit or suspend your service."

If you're using Wasabi for normal backup data storage, you shouldn't worry about egress. It is meant to prevent malicious users from uploading data and using up all the egress bandwidth, for example, a 500GB user egressing 5TB with public access or using Wasabi as a dump point to upload in one location and download in another region 1:1 ratio. As your storage goes up, your available consistent monthly egress goes up. It only becomes an issue if you abuse the account by uploading/downloading in a 1:1 ratio on a consistent basis.

What happens is you get an email from support asking if something changed in your use case. If so, they will help troubleshoot it(Think of a CDN scenario, where the CDN gets misconfigured). You also have an egress monitor for suspicious activity in case you aren't normally downloading all your data, and then you see a rise in egress https://docs.wasabi.com/docs/en/whats-new?highlight=egress#e....

ph4te

2 yıl öncediscuss

This is highly dependent on the use case. Backblaze gives you 3x free egress, but after you hit that you pay for any additional egress. Wasabi has terms of use not to exceed 1x your storage, but is not in their model to pay egress. As a long-term storage user, you can restore a full system-wide backup without any concern of charges at Wasabi(typically, you're not restoring everything, just recent backups), as long as you are not consistently doing it. Backblaze will get you more egress for sharing data over the public internet, but if you need more, you will get charged.

ph4te

2 yıl öncediscuss

I don't think this needs to be an all-or-nothing thing, and aside from a few items, it seems pretty standard. We start off with the Zero to Prod model, and when handlers become too large, move them over to "Repository" types. GET usually stays in the handler, vs POSTing a new request for an action that may include several DB calls, channels, async tasks etc.. goes into a "Service" type crate. Its usually little work though. As far as separating "entities" from requests/responses, that seems to be the norm in any language/framework. You don't want secrets to be responded when you create something, or all of your internal properties. When there starts to be too many config knobs, things are extracted to their respective places. I like that this lays out out a framework for it. It doesn't necessarily mean I would start there.

ph4te

2 yıl öncediscuss

There are new rules and regulations in 2024.

https://clerk.chat/blog/tcpa-compliance/

We had to switch off Twilio for our integration and move to another provider that came with its own set of issues.

ph4te

2 yıl öncediscuss

Welcome to the world of S3, Where everything is made up and nothing makes sense!

ph4te

2 yıl öncediscuss

SparkJava has been around since just about the time that Spark became Apache Spark. 10 years ago-ish.

comments