Monteur vidéo pour Colas BIM France Rugby et IMPACT TRADING https://xitter.cf/t.co/WMHzhSkQGk
Joined March 2023
- Tweets971
- Following207
- Followers738
- Likes1.3K
Eddy retweeted
Introducing Kled Labs.
Every major AI model learned from the internet. We're betting on people instead.
One goal: train our own models to beat closed models at important human tasks, using our data alone.
All data is sourced from our data application layer and our network of 600,000+ contributors.
We're hiring: jobs.ashbyhq.com/kled-ai/6e9…
Eddy retweeted
Kled AI is extremely overlooked: AI data collection platform on the DATA Network reporting 1.5B+ uploads, 5M+ per day and millions in revenue.
@useKled pays people for photos, videos and targeted tasks, supplying AI labs with real-world training data, including household footage for physical AI.
Je n'aime pas trop la méta, beaucoup de créateurs critiquent les monteurs, j’en connais plein qui sont forts et qui rendent les projets en temps et en heure. La vérité c’est que personne ne veut payer le prix. (en particulier les fameux infopreneur)
Désolé @ClaraPeano rien contre toi et j’ai aucune idée de comment tu bosses je réagis plus à la masses qu’à ton message en particulier
Voilà les résultats, je suis globalement très content, ce n'est pas explosif comme on peut voir sur X mais c'est très ressemblant à ce que je faisais moi-même et ça garde ma DA pour mon client.
J'ai fait 10 Motion IA pour une vidéo de 17 minutes, j'ai gagné pas mal de temps 👍
Eddy retweeted
introducing kled studio. coming soon to desktop.
a playground for ai labs to explore marketplace data, evaluate their own models, and collect what they need next.
create custom tasks and deploy them directly into the kled app, targeting contributors by demographics and psychographics.
Eddy retweeted
say hi to kled v3, the data collection layer for agi.
any dataset a lab can describe, collected from the real world by 500,000 people in under 72 hours.
Eddy retweeted
This is Kled V3. We've solved data collection for artificial general intelligence.
Any consumer dataset that can exist, can now be collected from physical reality in under 72 hours.
All powered by the largest and most comprehensive data application layer on the planet. (Thread)
Eddy retweeted
To those who hold solana:1zJX5gRnjLgmTpq5sVwkq69mNDQkCemqoasyjaPW6jm , remember this:
At 30M, people will say, it's time to sell
At 50M, people will say, it's topping
At 100M, people will say, they should've held longer
At 300M, people will say, they've found another better competitor
At 500M, those who sold, are hating on it and FUD starts
At 1B the few who held, would be bull-posting daily
At 3B the entire world would be buying and shouting about it every day
Unless, AI dies tomorrow. Unless data becomes worthless tomorrow; Kled is in the process to mint the next generation of crypto-AI millionaires, and timeline wise, it might not be that far away. It's within grasp.
WARNING: It's not going to be easy to hold a coin through its peaks and troughs. Only conviction will get you to Valhalla.
But a stark (and constant) reminder is that your conviction is nothing compared to VCs who have committed over $14M to grow the business. Your conviction is nothing compared to the clients who had committed tens of millions of dollars worth of deal contracts to Kledco.
FACT: Data will eat the world. But Kled will feed the world. Think Axie, Think future jobs, and Think about holding for longer.
But you can sell here.
You asked for floor value? Kled's currently backed: nearly 1-1 equity-token marketcap.
You asked for confidence? Well, if the company is sold tomorrow, you'd still get your money back.
We can only say it'll go higher from here. Tons of users, flywheels being activated. By comparison, Axie MC - Sky Mavis Valuation was worth 15:1 ratio at its peak.
Kledco also holds a significant portion of the 1b total tokens (bought back using their revenues). So everything is aligned. It's in their interest to have the tokens worth something.
But you can sell here. It's okay. Not everyone deserves nice things. To us, it's a Tier-1 project. But you can make your own decision, Anon.
Je vais tester car j'ai un client qui me demande d'en intégrer dans les montages. Je vous tiens au courant si c'est bien ou si c'est un flop...
opus 5.5 is f*cking cracked at motion design
this entire video is code, 0 after effects
im open sourcing the prompt template for these motion designs
steal it to recreate these ↓
Ask me for: 8 to 12 UI states I want the shape to become (e.g. button, loader, player, slider, toggle, tabs, chart, command palette, toast), pure black and white or one accent color, and a royalty-free song around 120 BPM (e.g. Mixkit, free for commercial use).
Dribbble-level UI motion. One shape, never cut: every state is the same element morphing its size, radius and color while its content swaps with a short blur. A cursor drives every change with real clicks and drags. Light warm-gray canvas, black and white components, one clean UI font (Geist). Springs everywhere, a tiny overshoot at most. The camera zooms so each state fills the frame. The last frame is the first frame, so it loops.
Banned: bouncy easing, particle bursts, glows, gradients on UI chrome, mismatched icon strokes, dead time, anything that looks like a template.
120 BPM, 7 bars, something happens on every beat.
Button → loader → check → dynamic island → music player with a play/pause morph → scrub the progress bar → it becomes a volume slider that stretches when dragged past max → a toggle flips on the beat → the knob becomes a liquid tab indicator → the tabs open into a chart that draws itself, with a tooltip on hover → it collapses into ⌘K → type to filter → enter → toast → back to the button.
1. One HTML file, square 1440x1440. Every style is computed from time inside seek(t): no CSS transitions, no timers, no state carried between frames.
2. Springs are closed-form step responses. A value that changes target many times is the sum of one spring per change, so it stays a pure function of time.
3. The tab indicator's two edges ride different springs, so the leading edge stretches ahead of the trailing one. Same trick for the toggle knob.
4. Drags are direct manipulation: while the cursor is held, the value is computed from its position. On release it springs back from wherever it was.
5. Analyze the song with numpy for the beat grid and start on a downbeat. Place every UI sound by its measured peak.
6. Render with Playwright: 4 subframes per frame, blended with ffmpeg tmix for motion blur at 60fps.
7. Render one frame per beat before the full render. Fix anything off the grid, cramped or hard to read.
Never put will-change on anything the camera scales or the text renders blurry. Text that swaps inside a morphing container needs its own enter and exit timing or it overlaps. Make the last frame identical to the first, cursor position and speed included, or the loop stutters.
Ask me for the inputs, then show me the state list on the beat grid before you write any code.
