Hacker News
X / Twitter
The coolest thing I've seen today: a research project that lets you put in your room any artist you recorded with your phone!
The project is called 4DAnyone (https://t.co/DSiEsnfyph), and it is able to create a 4DGS, which is a volumetric video made with Gaussian Splats, by just starting from a monocular video, like the ones you shoot with your phone. Usually, shooting these videos requires a huge rig with many cameras, and it is an expensive process. The goal of this project is to let you use just your phone.
4DAnyone works by trying to infer the pose of the person pictured in the video at every frame, and then use the skeletal pose together with the visuals that are seen in the video to try to reconstruct what could be the video of the person if he/she were shot from many other points of view. Once many points of view have been simulated, the process of creating a 4DGS volumetric video is the same as it is now with the huge rig of cameras.
The demo videos shown in the article are impressive. It is still a research project, though, and I strongly believe that the videos reconstructed this way can't match today's stunning quality of the 4DGS created by @gracia_hq . But it is very promising research, and in a few years we could all have volumetric videos coming out of our phones...
#VirtualReality #MixedReality #artificialintelligence #gaussiansplatting #technology
https://t.co/apHFhWefzp
Looks like a cool project @TheoLundqvist!
Faster GitHub locally
They long, tedious grind of documentation and guides is almost over. This is definitely the most exasperating part of creating tools. I'm not going to wait for long form video guides to release this as that could push it out weeks more and most people won't need them. Trying to get to a minimum viable release asap!
Can the right design system output the map, the prototype, and ideally the build?
My thoughts at this point are theory coupled with emerging reality. If you're thinking about this too, would love your perspective. https://t.co/zRpS52VLMO
https://t.co/foMRuMmuGU
arch diagram built from poking around at latest commits https://t.co/QqFJZCBSfd https://t.co/XUJcUVB6tj
https://t.co/4E91KTbzDU
We finally cracked it!
We built an open-source video editor that turns every edit into code.
I got tired of agents:
→ Losing context
→ Giving me outputs I couldn’t modify
So we flipped it:
→ Code is the new database. https://t.co/Jx07qn9KJE
LightGlue ONNX
ONNX-compatible LightGlue: Local Feature Matching at Light Speed. Supports TensorRT, OpenVINO
https://t.co/Q1vDiknqVP
Open Neural Network Exchange (ONNX) compatible implementation of LightGlue: Local Feature Matching at Light Speed. The ONNX model format allows for interoperability across different platforms with support for multiple execution providers, and removes Python-specific dependencies such as PyTorch. Supports TensorRT and OpenVINO.
If you work on anything worthwhile, sooner or later ppl will want to know how it's going. You may need to send investor updates, updates to your boss, emails to adjacent teams, etc. Some hard earned tips:
1. understand your role, and with each update add to the body of evidence that you’re a good steward in that role. If ppl want your updates, they’ve entrusted you with something-- a successful delivery of a product or feature, investment capital, company budget, their reputation, something. Convey that you value their trust and take stewardship seriously
2. add a little randomness to the cadence. Ppl think they want regular cadence, but they’re happier with bounded irregularity. For example, if you send project updates every Tuesday they will seem transactional and no one will read them. If instead you send updates every 2-3 weeks, your audience will look forward to them because they’ll assume you have something new to say
3. know what your next update will be and work toward it (instead of coming up with an update when it’s time to send one). If you don’t have a headline you don’t have an update, and you can’t generate good headlines post-factum
4. always start with a one sentence TL;DR and a 2-4 sentence recap of the overall goals of the project. Assume your audience is smarter than you are, but is very busy and remembers nothing about your work
5. ppl love pleasant surprises, but these don’t come along often enough by chance. Within reason, deliberately engineer pleasant surprises so you can include them in your updates
6. ppl hate unpleasant surprises (obvs avoid these if possible.) Talk to each person privately before informing the group. Also this is controversial but it sometimes helps to deliver negative news in two phases. First express the possibility of a problem to give ppl time to adjust. The next time state the problem. (Don’t do this if there is a genuine emergency obvs)
7. acknowledge changes explicitly. If you said A the last time and B this time, you need to explain the inconsistency. Ppl perceive acknowledged inconsistencies as cost of doing business, but unacknowledged inconsistencies as broken promises
8. don’t insult anyone. I once wrote an update that said something along the lines of "our engineers don’t know anything and therefore can’t ship, we need better engineers", and sent it to everyone. Definitely don’t do that
9. ppl want a steady hand at the helm. Your tone should reflect that. You want the text equivalent of pilot radio voice (mixing metaphors, I know)
10. many ppl (correctly) worry they’re being personally evaluated so they sanitize every sentence to death. Don’t do this. Make it all about the work, not about you, and leave the rest to others
11. know the top three questions your audience wants answered, and state the answers as clearly as possible
12. add a dedicated section for worries and failures. Be honest, have good plans, and have no fear. Ppl are drawn to conscientiousness and vulnerability but repelled from haplessness and histrionics
13. “Elon yells at Wall St analysts in quarterly earnings calls, why can’t I?” If you build a company with a market cap greater than the rest of its industry combined, you have my blessings to ignore this advice
Note, these tips ^^ don’t work if you’re incompetent
122 algorithms behind pen #plotter art, each with a live demo you can run, reseed, and read the source of.
Flow fields, Voronoi stippling, Hilbert curves, differential growth, TSP path ordering, dithering, polygon clipping…
Free, in the browser:
https://t.co/2GLitLYw6q https://t.co/qq0jA8E7ii
Ponytail is a plugin that stops coding agents from over-engineering.
I wrote a deep dive on how it works, how to install it in ChatGPT, Codex, and Claude Code, and how I’d use it.
https://t.co/wAFp0akmZz
I'm happy to say that https://t.co/t7A0lA0YwA 2.0 has been released with brand new OPFS support. If you're building browser-based apps that heavily interact with the file-system this package is a must to have in your package.json!
A React hook that watches a directory and re-renders when a file is added, changed, or deleted. Point it at a folder the user picked and you're reading and writing their real files — no uploads, no endless file dialogs
New in 2.0: it watches the origin private file system too. No picker, no permission prompt, no user gesture — and, unlike File System API, it works in Safari and Firefox 😊
What's OPFS? A file store the browser gives each origin — real directories and files, but readable only by your own site through the File System API, never by the user's file manager or other apps.
lets goooo, just went back into the rabbit-hole of having distributed pi (@AmpCode orbs for the people) and apparently @pidotdev shipped the piece i was missing while i wasn't looking????
i thought the big server rewrite would never come!! https://t.co/UmvD8DZZKV
I promised to make a list of anti-slop for "coding". So here you have:
1. anti-slop - @dillon_mulroy
https://t.co/VecydIfAIQ
2. thermo-nuclear - @ericzakariasson
https://t.co/lKyjN52oA3
3. deslop - @brian_lovin
https://t.co/PcJbKHUejO
4. deslop - @poteto
https://t.co/Opgqzp7Y0H
5. deslop - @dani_avila7
https://t.co/lhVCi7A3Mt
6. desloppify - @peterom
https://t.co/5hRuarVQEb
7. code-slop - @asyrafhussin4
https://t.co/leUtwUWuYN
I was talking to a friend about serving customer-facing dashboards with just Cloudflare R2 & Hyparquet for range queries ~ no db required. Turns out it's fast!
first time I haven't reached for DuckDB for this use in while, though naturally I did use it to build the datacube https://t.co/wat8cJ7MQj