For tasks either: shaking paradigms, related with deep technical debt, misty specifications or unidentified implementation

For changes relying on an external / unstable predicate: - specific usage - content platform current implementation / API and TOS

Not heavily relying on external or fragile predicate but will probably break or change at some point

For stable changes or improvements that would survive: - usage shift - platforms mutations - legal evolutions

Could impact ethics aspects or allow misusages. Need caution: it is not because something is doable that it should be done.