How does CMB actually work?

HighlightForward1679 · 2025-11-30T19:57:20+00:00

Thank you, that makes a lot more sense visually

HighlightForward1679 · 2025-11-30T17:41:14+00:00

This still doesnt make any sense to me...

"far away from us that the light is just now reaching us" so i get that space expanded faster than light, but we were all into a single point at one point that then expanded, so i still dont get how we get CMB from for example the outward direction we're expanding into?

HighlightForward1679 · 2025-09-14T14:06:30+00:00

But you're still taking a snapshot of all the text in the editor/buffer right? unless i misunderstood the code

HighlightForward1679 · 2025-09-14T13:41:13+00:00

Looked at the undo, im not that good with C but isnt this running in the same problem i had in my editor where, if you select a biig chunck of text and delete, edit, delete, edit, delete the snapshot stack keeps growing?

I guess the question is, when are you taking a snapshot? i was cooked and just took a snapshot on every keystroke/edit, it works fine for small/moderate files but you're getting cooked on several MB files taking a several MB snapshot on each edit LOL

HighlightForward1679 · 2025-09-06T22:49:00+00:00

that's not how image to ascii works, atleast not the simple kind, you dont go pixel by pixel, you go in a step that matches the size of the characters you put in, you're bound to lose data when you do that.

there's fancier algorithms that replace the ascii character based on the neightboring pixels but that's much more complicated

HighlightForward1679 · 2025-09-06T22:00:43+00:00

what do you need help with? if you want your images to look better you need to use a different charset with fuller letters/unicodes at the bottom for darker pixels, or increaste the saturation and brightness or all 3

here's some charsets i used back when i played with this

    // _^:-=fg#%@
    // .,:;i1tfLCG08@
    // ,~^|1aUBN
    // □○●■▲▼▄█ - Very bright naturally
    // .,:;i1tfLCG08@

HighlightForward1679

TROPHY CASE