Hacker Newsnew | past | comments | ask | show | jobs | submit | Metaboat's commentslogin

104 :nth-child(3n){list-style:"Fizz"}:nth-child(5n){list-style:"Buzz"}:nth-child(15n){list-style:"FizzBuzz"}

data:text/html,<style>:nth-child(3n){list-style:"Fizz"}:nth-child(5n){list-style:"Buzz"}:nth-child(15n){list-style:"FizzBuzz"}</style><ol id=o><script>o.innerHTML='<li>'.repeat(99)</script>


89: :nth-child(3n)::marker{content:"Fizz"var(--b,)}:nth-child(5n){list-style:"Buzz";--b:"Buzz

with help from @bulmenisaurus


103 :nth-child(3n){list-style:"Fizz"}:nth-child(5n){list-style:"Buzz"}:nth-child(15n){list-style:"FizzBuzz"

98 :nth-child(5n){list-style:""}:nth-child(3n){list-style:"Fizz"}:nth-child(5n)::after{content:"Buzz"

95 :nth-child(5n){list-style:}:nth-child(3n){list-style:"Fizz"}:nth-child(5n)::after{content:"Buzz

68 :nth-child(3n){list-style:"Fizz"}:nth-child(5n)::after{content:"Buzz

This version fails for numbers like 5, showing "5. Buzz". In the case of a number divisible by 5 but not 3 nothing prevents the 5 in the ::marker from rendering.

Edit: it looks like your version can be fixed into a working 85:

  :nth-child(5n){list-style:'';&:after{content:"Buzz"}}:nth-child(3n){list-style:"Fizz"

67 :nth-child(3n){list-style:"Fizz"}:nth-child(5n):after{content:"Buzz

thank you sir! i can improve the html op css was 152, we have the whole page at 144

data:text/html,<ol id=o><script>o.innerHTML='<li>'.repeat(100)</script><style>:nth-child(3n){list-style:"Fizz"}:nth-child(5n):after{content:"Buzz


Your code is showing the numbers 5, 10, 20. that's not correct, is it?

Yours prints 1. 2. Fizz 4. 5. Buzz Fizz 7.

But it should be 1. 2. Fizz 4. Buzz Fizz 7.


Most transcription tools feel like they were designed around business models, not actual usage. High per-minute pricing, unnecessary features, multi-step onboarding, rate limits, and a long list of things you don’t need before you get the one thing you do: text. We built MetaBoat Transcription because the essentials were missing everywhere else. A transcription system should do a few things extremely well: run reliably on real GPU infrastructure handle long audio without falling apart stay cheap without surprise billing return clean, structured output let you see what’s happening inside the queue throw work at any available compute without user involvement delete the audio immediately get out of your way So that’s what we built. MetaBoat Transcription is an English-only pipeline backed by a distributed GPU scheduler that moves work to wherever capacity is available. Jobs run in disposable workers, failures resolve automatically, and the dashboard shows you every step without trying to hide the machinery. Pricing is $0.02/hr because that’s what the underlying compute actually costs — not because we’re playing margin games. It isn’t positioned as a “platform,” and it isn’t pretending to be an AI product with layers of abstraction. It’s a purpose-built system that treats transcription as infrastructure, not a luxury service. The pricing model is intentionally simple: 10 hours free per day, then $0.02 per hour after that. No tiers, no credits expiring, no fine print. We’re adding diarization, speaker identification, word-level timestamps, and streaming — not to pad a feature list, but because they make the core system more complete. If you want transcription that behaves like a well-designed backend service instead of a SaaS maze, it’s here: https://transcribe.metaboat.io Happy to hear thoughts from anyone who’s built (or fought with) similar pipelines.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: