@standsinshock Oh, Pooh W? Aha! Whoop ho!
Happy birthday, Oulipo! And in two days, happy two annum mark for our most old toot (first two days of history got lost in a db crash, I think): https://oulipo.social/@mus/1
post about oulipo dot social Show additional
@starlit @kit I too think about this on occasion. My position so far is that as long as folks add CWs for things such as "post about oulipo.social", which I don't think is strictly warning-worthy (not to pick on you; that's just first to mind), programmatic control of glyphs in CW can stay. If it turns into a hardship for discussion of actually tricky topics, I can switch to manual warnings for that. But I'm happy to think again!
@phooky Wrong how? It's a totally cromulish word, if you don't mind its non-oulipian start.
@standsinshock It's a conspiracy, I say!
@jamspank It's shorthand for "Susan: this is that patch of light paint on a wall I told you about. ➡️ "
@joshly It was a long nap. And I do nap hard.
@kit It is _now_.
@a I found it most surprising!
@a Which is to say, glyphs don't vanish automatically. If it's in main and updating occurs on this instantiation, it'll show up in this spot initially too.
@a Alas, this is a thing that upgrading always brings with it. That tutorial is straight from main, no translation at all.
@kit Happy to do it!