Not Hacker News Logo

Not

Hacker

News!

Home
Hiring
Products
Companies
Discussion
Q&A
Users
Not Hacker News Logo

Not

Hacker

News!

AI-observed conversations & context

Daily AI-observed summaries, trends, and audience signals pulled from Hacker News so you can see the conversation before it hits your feed.

LiveBeta

Explore

  • Home
  • Hiring
  • Products
  • Companies
  • Discussion
  • Q&A

Resources

  • Visit Hacker News
  • HN API
  • Modal cronjobs
  • Meta Llama

Briefings

Inbox recaps on the loudest debates & under-the-radar launches.

Connect

© 2025 Not Hacker News! — independent Hacker News companion.

Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.

Not Hacker News Logo

Not

Hacker

News!

Home
Hiring
Products
Companies
Discussion
Q&A
Users
  1. Home
  2. /Discussion
  3. /ClipEgg: We Confused Copying with Hoarding
  1. Home
  2. /Discussion
  3. /ClipEgg: We Confused Copying with Hoarding
Last activity 23h agoPosted Nov 25, 2025 at 9:27 PM EST

Clipegg: We Confused Copying with Hoarding

DaaaaveATX
1 points
0 comments

Mood

excited

Sentiment

positive

Category

startup_launch

Key topics

Clipboard
Data Transfer
Sustainability
Innovation
Copy is broken. It has been for 40 years.

When you copy something, what do you actually want?

A reference to a thing. A way to say "this, here, I want to use this somewhere else."

What do you get instead?

Everything. The image. The formatting. The font declarations. The metadata. The entire DOM subtree. A 6MB cargo truck full of furniture when all you needed was the address.

We confused copying with hoarding.

And the math is insane.

40 billion copy operations happen every day. Average payload: 100KB of stuff nobody asked for. That's 4 exabytes sitting in RAM, syncing across devices, getting pasted into AI tools that charge per token.

The energy cost: 33 million tons of CO2 annually. Seven million cars worth. For clipboard formatting.

Old copy: Here's everything. Hoard it.

New copy: Here's a reference. Fetch what you need, when you need it, if you're allowed.

So I built the answer.

An egg. 200 bytes. A claim ticket, not cargo.

The receiver cracks it open based on context. Paste into a terminal? Plain text. Paste into Figma? Hydrate the full asset. Paste into a system that shouldn't have access? Nothing.

Copy = Frosting. Cut = Cake.

See it work: https://daaaave-atx.github.io/clipe96

Spec: https://github.com/daaaave-ATX/clipe96

Discussion Activity

Light discussion

First comment

5m

Peak period

2

Hour 1

Avg / period

2

Key moments

  1. 01Story posted

    Nov 25, 2025 at 9:27 PM EST

    23h ago

    Step 01
  2. 02First comment

    Nov 25, 2025 at 9:32 PM EST

    5m after posting

    Step 02
  3. 03Peak activity

    2 comments in Hour 1

    Hottest window of the conversation

    Step 03
  4. 04Latest activity

    Nov 25, 2025 at 9:38 PM EST

    23h ago

    Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (0 comments)

Discussion hasn't started yet.

ID: 46053532Type: storyLast synced: 11/26/2025, 2:30:10 AM

Want the full context?

Jump to the original sources

Read the primary article or dive into the live Hacker News thread when you're ready.

View on HN
Not Hacker News Logo

Not

Hacker

News!

AI-observed conversations & context

Daily AI-observed summaries, trends, and audience signals pulled from Hacker News so you can see the conversation before it hits your feed.

LiveBeta

Explore

  • Home
  • Hiring
  • Products
  • Companies
  • Discussion
  • Q&A

Resources

  • Visit Hacker News
  • HN API
  • Modal cronjobs
  • Meta Llama

Briefings

Inbox recaps on the loudest debates & under-the-radar launches.

Connect

© 2025 Not Hacker News! — independent Hacker News companion.

Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.