It seems feasible to use a small/cheap model to flag possible vulnerabilities, and then use a more expensive model to do a second-pass to confirm those, rather than on every file. Could dramatically reduce the total cost and speed up the process.
I tried it on my iPhone 13 mini. I believe the model you get changes depending on your phone specs. For me it downloaded a ~1.3GB model which can speak in complete sentences but can’t do much beyond that. Can’t blame them though—that model is tiny, and my device wasn’t designed for this.
To the author I’d recommend a Casio Oceanus. The same tech as a G-Shock (solar, atomic, Bluetooth) with the polish of a Grand Seiko at 20% of the price. Better to get one in Japan as the US retailers charge a lot more.
Found that I prefer mine over watches that cost 5x as much.
One way to improve things could be to charge for each new account signup if you don’t have an invite from an existing member that vouches for you. Spamming when you risk losing $5-20 per account raises the cost substantially.
Invites could be earned at karma and time thresholds, and mods could ideally ban not just one bad actor but every account in the invite chain if there’s bad behavior.
I have a single wrap function that does this for all errors. The top level handler only prints the first two, but can print all if needed.
I have never had difficulty quickly finding the error given only the top two stack sites.
Any complaint about go boilerplate is flawed. The purpose and value is not in reducing code written, it is to make code easier to read and it achieves this goal better than any other language.
reply