Post

Kudos for the awesome feature! PS: Nanoseconds, huh? Seconds seem to suffice for: • YT, Vimeo, Twitch (#t= params) • Tiktok, Twitter (snowflake IDs) Is there an editing use case where that many extra zeroes worth of granularity are useful, or is this just convenient? dfir.blog/tinkering-wi...

Haha yeah I'm uncertain of that myself. I would want this API to be sufficient to do framexact precision for splicing but milliseconds are probably sufficient for that; not a lot of 10,000 FPS videos out there. I wouldn't want to do seconds for atproto though 'cause you're not supposed to do floats

Consider me nerd sniped What's your max limit on a single stream? 24 hours? If so, then milliseconds + a max timestamp value of 86,400,000 would give you frame-exact precision splicing for a day's worth of raw footage up to 1000 FPS