A triumph has turned into a tragedy. Some days ago, I discovered
Neopets Classic. When a specific Flash asset on its site failed due to Ruffle shenanigans, I reported the bug, but the administrator responded by forcing Ruffle emulation everywhere. This simply will not do, for reasons I trust anybody here should understand. Regrettably, the kind administrator seemed not to recognise that Pale Moon
is a modern browser which happens to retain NPAPI support, and that it apparently caused no problems hitherto to offer native SWF alongside Ruffle for those who need it. I feel quite bad about myself, since asking for help from the Neopets Classic staff ended up making things objectively worse.
A demo page exists for testing. Rather like how we have found ways to make the Internet Archive display true Flash instead of Ruffle, I hope this could be done for Neopets Classic. (Until then, I have self-frozen my NC account, so no Aishas starve while studying this.) On the Internet Archive, the µBlock rules
Code: Select all
||web.archive.org/_static/js/ruffle.js[/ic]
||https://web-static.archive.org/_static/js/ruffle/ruffle.js
||web.archive.org/_static/js/ruffle/ruffle.js$script,domain=web.archive.org
have served admirably since 2024. On Neopets Classic, my own inferred
||neopetsclassic.com/*/ruffle.js or
||neopetsclassic.com/static/images/swf/ruffle/ruffle.js simply replace the buggy Ruffle blocks with the message
Ruffle failed to load. I sincerely hope a remedy can be found, for I feel it is my fault for breaking the Flash assets in the first place.