Post #2279989
2026-04-15 09:29 UTC
@karolherbst@chaos.social It needs to be rather more nuanced. We have so much code where 'someone made the same security cockup' because nobody will fix an API or piece of architecture. Not being willing to fix bad design at some point ends up as nothing more than dumping the cost of mistakes on others
Most small things though absolutely. Pleading 'well it always technically undefined behaviour' rather than keeping a behaviour is usually bad
Replies (1)
-
@karolherbst@chaos.social 2026-04-15 11:44
@etchedpixels@mastodon.social yeah, and I'm just saying we need to be responsible. If you break behavior, make a new API, call it v2 and drop the old one after X years. Not only if parameter change, but for behavior. There are ways of doing this properly.