Fix "burn-in" issue for "always on" screens that are directly connected to devices running HAOS.

[GittyScott]

Describe your idea

After extensive research, I believe I have uncovered the HAOS console splash screen’s canon event:

Why is this exciting?

+10,000 console aura.
The pixels yearn for motion.

Potential use cases

• Solve world hunger? No
• Solve burn-in for those out there who have (or want to have) always-on screens connected to HAOS? Ab-so-lutely

Anything else?

If you really want to please the people, you could give them what they crave and provide bountiful options:

curl ascii.live/parrot
curl ascii.live/dvd
curl ascii.live/earth
curl ascii.live/coin

Full endpoint list at: ascii.live/

It would be worth noting these practical points when considering implementing:

• If using CLI on the HAOS device itself, you need to firstly type "exit" as the HA CLI does not have Curl.
• This would need to be restarted after a server reboot/update
• This animation should probably be captured, stored locally and replayed to reduce bandwidth/promote local first. ChatGPT has your back here 👌
• It might be worth adding a note underneath the animation to say "Press Ctrl+C to use terminal" - But then again if someone's doing this they probably know.