code for review :
Prompt :
Create a 2D anime short for the web. It must look completely like real Japanese anime, as if it were taken directly from a finished theatrical anime film. This is traditional-looking, hand-drawn 2D anime, not a 3D animation, a moving illustration, or a stylized web graphic.
Deliver the final result as a single, self-contained HTML file that plays offline, with a synthesized soundtrack. Use any tools, libraries, references, guides, literally anything etc.
Use theatrical mecha and kaiju anime as the art style reference for the design, line work, painted backgrounds, color, and atmosphere. The film is 83 seconds long, in 39 shots. Its characters are a colossal silver archer robot, a fleet of container ships, and a leviathan. No people appear in the film. Use any tools or techniques you want, including 3D, as long as the final result looks 100% like hand-drawn 2D anime.
SCENE
A blazing sunny day on a coast. A massive armored archer robot, a hundred meters tall, stands in a deep lunge on a headland and draws a bow taller than itself. Close-ups: the hand on the grip, the limb and cable, the foot planted in the surf. Blue energy crawls along the arrow into the chest armor until the arrowhead blazes like crystal. The string snaps forward and a shockwave flattens the sea. The arrow is a harpoon trailing a thin cable. It tears the clouds into two walls above a ship's deck, climbs through the cloud tops, and reaches the edge of space in a blue flash along the planet's limb.
Out at sea, container ships cross a colossal shadow. Four humpback whales breach beside a ship, with real arcs and full tail flukes, and dive tail last. From below, shapes move under the bright churning surface. Four whale heads rise from a boiling sea, and a ring of teeth rises around them: they are lures inside a mouth. They drop in and the jaws shut. The leviathan breaches through the fleet in one slow, enormous arc. Its belly slides past the bridge windows. The swell it leaves lifts the ships and stands one on end, spilling containers. Its ridged back and flukes sink into spray fog.
High above, the arrow turns over and comes back red-hot through the atmosphere. Below the surface, the leviathan crawls through a luminous canyon on clawed forelimbs and swallows a fleeing whale. A thin streak meets the sea on the horizon and a white plume swells up. The harpoon drives through its back in a blue-white flash, lightning runs along its body, and the barbed tip punches out of its belly into the rock, which bursts apart. The cable stays attached the whole time, rising to the surface. A mountain of water swells from the sea. The dying leviathan erupts, rolls over between the ships and falls, and a wall of water takes the fleet.
ANIME QUALITY STANDARD
Every frame must look as if it was drawn by professional anime animators and painted by master background artists for a finished theatrical film.
Archer: A massive, heavy anime mecha with sculpted overlapping armor plates, panel lines, bolts, markings and a faceted chest reactor that glows blue. Hands really grip the bow and string. The arrow never passes through the armor. Keep it on-model from every angle.
Leviathan: Whale-like and colossal, always dwarfing the ships. Rough, dark grey-teal wet hide with barnacles and scars, a pale ribbed throat, a spined back, huge clawed flippers, and a cavernous maw with uneven teeth. A real bending body with weight, never a stiff model hanging on pillars of water.
Whales: Real humpback anatomy with tail stock, big notched flukes and long curved flippers rooted in the body.
Ships: Detailed container ships with corrugated multicolor containers, lashing bars and a white bridge tower.
Line art: Confident, delicate, hand-inked anime line work with subtle variation in thickness and pressure.
Coloring: Traditional anime cel coloring with clean color areas, hard-edged cool lavender-blue shadows, crisp highlights, and a bright, high-key, saturated palette. Never gloomy, grey or muddy, even in the darkest moments of the story.
Backgrounds: Richly detailed, hand-painted anime backgrounds in a gouache style: towering white cumulus, a cobalt-to-turquoise sea at kilometer scale, a painted coast with a far town, Earth from orbit, a port city from the stratosphere.
Underwater: Luminous cyan depth with god rays, a rippling surface seen from below, jagged canyon rock, silt and fish. Bright, not black.
Lighting: Summer sun with colorful shadows, and a separate character key light so that nothing sinks into shade.
Effects: Bold drawn anime FX on twos and threes. Sharp lightning with a white core, plasma trails, sheets of water pouring off the body, plumes, spray and a wall of water with real mass. Never particle mush or cotton-wool clouds.
Animation: Authentic hand-drawn anime timing, with characters on twos, strong key poses, natural holds, and overlapping movement. Huge things move slowly and heavily. Nothing clips, slides or floats.
Sound: An original epic score with ominous drones, brass and choir, near silence before the impact, then a colossal hit. Add a recurring whale-song motif, bow creak, charge whine, sonic boom, thunder and the sea, muffled underwater, all timed to the picture.
Direction: Cinematic shots, macro close-ups against huge wide shots, thoughtful staging, and pacing that builds from quiet tension to a devastating climax.
IT MUST NOT LOOK LIKE
- 3D: No plastic materials, CGI shading, visible polygons, game-engine lighting, or computer-perfect perspective.
- Blocky "Minecraft" shapes: No plain boxes, empty flat surfaces, or toy-like proportions. Every surface carries design detail.
- SVG or vector art: No simple geometric shapes, perfect curves, uniform outlines, flat corporate illustration, or basic gradients.
- Web animation: No sliding layers, constant bobbing, floating parts, smooth software easing, or puppet-like joint rotation.
- Pasted-on elements: No 2D sprites floating in a 3D scene.
- AI art: No warped shapes, melted details, flickering, or changing designs.
- Non-anime art: No Western cartoon designs, realistic rendering, soft painterly shading on the characters, or generic digital illustration.
- Amateur work: No stiff poses, empty backgrounds, muddy colors, clip art, placeholders, or unfinished details.
You are free to change any part of the prompt, if it would result in better results.
The result should feel enormous, terrifying and beautiful, a blockbuster in bright anime colors.
Before finishing, inspect random frames as still images. If any frame does not look completely like real 2D anime, keep improving it.
Do not stop until every frame could pass as a still from a theatrical anime film.
显示更多
Claude's watermark probably doesn't work how you think. As the CTO of GPTZero, I'll explain how Anthropic, Google and OpenAI are building text watermarking in this brief explainer and whether it can be defeated.
Almost all forms of watermarking that are fast and cheap enough for a frontier lab have the same formula, following the KGW method:
In generation:
1. Let's say you've generated n tokens so far. Take those n tokens + a secret key to generate a random hash
2. Use that hash to randomly reweight the probabilities for the n+1 token, and then sample from that new distribution. In the simple case, you could split 50% of all English words into a green or red set based on your hash, and boost the probability of words in the green set.
For watermark detection:
1. For each token, see if it was in the green or red set.
2. To do this, recreate the hash based on the secret key and the text preceding the current token. Then, recreate the green and red set of words.
3. Once you've checked all the words in the text, if the next token is selected disproportionally from the green set more than 50% of the time, you claim the text has the watermark.
I can tell you want to ask the following:
1) Isn't it easy to mess up the hash if you paraphrase the text? The answer is mostly yes, however, you can use a statistical model to get your hash instead of a deterministic function (SIR, Adaptive Watermark). Since the entire watermark is probabilistic, this is fine.
2) Doesn't this make the text much worse? The answer is yes, it does - Yes, it does – but for most people, it's imperceptible (Google claims in human feedback study with 20,000 texts), since there are exponentially many ways to write the same paragraph. DiPmark does something more sophisticated to avoid shifting the text distribution on average. Of course, watermarks fail on short text or highly predictable texts like "2+2=4".
3) Shouldn't it be easy to figure out the green and red sets? The answer is no. You would need an exponentially large number of samples from the watermarker to reconstruct those sets exactly, but it's a risk if the detector is open to the wild (Watermark Stealing)
Still, there are couple challenges that a frontier lab needs to overcome:
1. Their watermark needs to work token-by-token because they are streaming their text to users. Many watermark methods plan sentences or paragraphs at a time, or change the text after its entirely written, in order to make their watermark robust to paraphrasers, and a frontier lab cannot afford to do this yet (SemStamp, PostMark)
2. If the secret key leaks, the watermark is busted. To avoid a large blast damage from this, you need to have a couple secret keys in rotation.
3. There are some texts, like code, that cannot be arbitrarily changed, otherwise the code will break. In those cases, the watermark needs to selectively change words in parts of the text that can tolerate synonyms (i.e. like variable naming) - see SWEET, EWD, Invisible Entropy.
4. They will need to educate their users on how to deal with false positives and false negatives of a detector, which is a big challenge (one we put a lot of effort into)
So, how do I see this playing out in the next 6 months?
1. If Anthropic releases the watermark detector publically, I think they defeat their own watermark. People find reliable watermark removal strategies by testing against Anthropic (AI detectors like GPTZero have an advantage here because they can train against these adversaries once they become popular).
2. If they keep the detector private to the government, like Google has done, it's "safer". However, there are some papers showing trained approaches that work robustly to zero-shot break watermarks without any data, simply because they try to write the text just like a human (Zhang et al. 2024, Watermarks in the Sand). Also, making your detector makes it battle-tested and stronger long-term (my experience).
3. In my testing, the watermarks don't survive intense paraphrasing (especially if you combine word choice and syntax attacks), or human text substitution (rewrite your AI text by plagiarizing human authors). The free paraphrasers I've tried have quickly bypassed Google Deepmind's SynthId for what it's worth.
4. All-in-all, frontier labs are likely okay with this because they expect most users to not attack the watermark, and also because they + European regulators likely don't care past a certain point - its good enough.
5. Overall, I think users of frontier LLMs will not really care about this, because 1) they don't realize watermarks are there, 2) EU will force everyone to conform, 3) this seems more like regulatory hoop-jumping than an earnest effort from frontier labs to expose LLM use
Lastly, people's first concern shouldn't be watermarking, it should be AI detectors!
If you're posting, "its not X, its Y!!", I don't think the watermark is going to make a difference :)
显示更多