thanks, these are great!

prompt injection is more close to an exploit. a sequence of input that leads to unexpected behavior, exploited to perform malicious behavior.

many exploits are hosted on websites. called exploit kits even. i think prompt injection match such classification. its very similar. a piece of data on the site's side exploits a program or interface on client side.

wrapping your pitch with the word manifesto and writing in poems to try to make it so can be considered a bit cringe.

its a taste ofc., but calling things cringe is also subjective isnt it.

"we beleive information and coms should be free. we provide as non profit. reach out for more info on specifics. services include xyz. we do it from idealist standpoint so not everyone is rendered services. manual review."

cant beleive how many words flew by before i reached that conclusion. if it was stamped 2026 people would call it AI slop.

Your rights do not matter. Laws do not matter.

If your technology is used by someone for bad, then someone trying to prevent that bad will some day come knocking. Law or not. Rights or not.

The only thing you can thus do is protect yourself. If you get taken out, that is you relying on your Rights and Laws. They dont exist and wont protect you.

can you give some idea on if and how your model reason about visual bugs though? this is where i find human testing to be more logical. what if a buton click flickers the button instead of 1 time lightup and darken? can it see all the frames and catch it?

this seems where i think a lot of effort is likely still going to be spent so if in some what it could get a description from the code or a person and then reason correctly about visual behaviors in the game.

another tricky area is mandatory testers for appstores. those you can trick perhaps using your AI into thinking someone is testing it really but i am not sure if it would be against their terms... (likely? maybe could be material for exploring market opportunities)

from a business perspective, this might be considered the only way, but it is not. at large volume scale it becomes more, but often large scale is lacking optimisations in the first place.

its not wrong in my eyes, but definitely not the only path to take.

one team uses AI to create larger volume of work, but another does not use AI for whatever reason.

its really asking for problems.

either both should use it or neither.

if both is not perceived to be ok for quality reasons, then use neither.

a lot of applications for humanoid robots i've seen people make other accurate and , despite being very complex, much more simple machines for.

they are for a specific purpose ofcourse, where such a humanoid robot might be more general purpose. but general purpose things usually mean less good at specific things.

if it becomes good at everything and cheap enough it invites the next more economic problem (which i think is more real than 'AI' simply doing it. its robotics that will do it..) that people will lose jobs. those people cant purchase things anymore which their replacements produce, and thus there is a problem that now the robots do nothing anyone needs anymore?

i can think of specific jobs no one should need to do, like handling nafta or other insane scenarios, radioactive stuff etc. but those are so specific you could think a specific robot would be better at it and theres no need for a general purpose device to do that specific job.?

seeing how much is invested in this, i am quite sure i am missing an insight, and would be thankful if someone in robotics applications might enlighten me!

why does it matter that it is not 'visible' for anyone?

it also depends on the prompting, which true to your comment could likely use some finetuning to get it more 'readable' (its a difficult word initself being subjective. like 'clean')

looks like a lot of fun to explore and learn from thank you

ugh.

lets not become actual drones, ever attentive to what gets chucked down our feeds. never for anything else.

second is on a smaller timescale. so many features and crap that is never asked for and never used is crammed into software so the systems that execute it are just juggling pretty much dead code in and stale data in their caches all days long.