>on a late night hacking rampage
>get paged at 10:27PM
>oh crap
>they caught me hacking
>its mallace
>gotta make some shit up, own it
>tell them: Ah yup. That was indeed me.
>No mallace intended.
>ask Claude what to do
>”let’s blame the clankers anon”
>say I've been agentic testing. Just halted the harness. It’s off the rails.
>founder is getting tagged on X formerly known as twitter
>founder pretends he didn’t know
>”tell them the agentic swarm did it”
>says: Woof! Looks agentically ‘off the rails’ to me!
>who needs lawyers when we can blame clankers
>crisis averted lol
In reading a lot of the individual thoughts of participants from this years' DEF CON CTF finals, one understand some feelings of defeatism.
However, I'm actually personally very interested in the actual design/etc. of teams' tooling this year, despite the frustration.
@adamdoupe@Zardus@pwncollege Realistically, one for @ctfradiooo. I'm not paying for this platform for premium, so I can't edit. My apologies for a possible double-at.
@hugeh0ge If I may generally ask, is it also a general question regarding and individual's proficiency/scaffolding in "play testing" your problems; e.g. you as the author understand the route to your solution/unintended bias, or is this the symptom more generally/player assumptions?
@vxunderground Give yourself a carbohydrate-rich source that isn't necessarily sugar.
Along with that, eat/consume something with a higher fiber content to minimize blood-sugar spikes.
@dudcom3 Reasonably, the more you do now at your age, the easier maintaining good habits vs. trying to form them AND do the hard work is much more difficult (life obligations, etc.).
If you ever wish for some assistance, I'd be happy to help.
@dudcom3 The simplest method is just being honest with your caloric intake. If you want an easy-to-follow and decent approach:
- Find any TDEE calculator online, subtract a reasonable amount of calories, and track over time
- Invest in a $10 food scale, it makes it easier to estimate
@Octoberfest73 The primary differentiator(s) are the gateways in which it's being employed.
The routes mentioned are ones in which the APIs themselves are being accessed, and currently not subsidized by a subscription.
It's the headless/swarming workflows that are expensive by comparison.