The browser extension version of #Ruffle lacks proper support for transparency... Or image blending?
But the latest nightly build of Ruffle? Pixel-perfect!

I just landed FLV support in #Ruffle. This only applies to the video data.

All FLVs are currently silent because I also need to do some refactoring of Ruffle's audio backends (right now they only accept bare MP3 and muxed SWF audio streams). As for video codecs, H.263, VP6, and ScreenVideo v1 FLVs will all work.

#Ruffle tradotto in italiano. Letteralmente la frase "0 to 100 real quick".
Aspettatevi le prossime versioni in supporto italico. #flashgames

Aaaand #GitHub turned the dashboard view I already don't use into an algorithmic social feed because... why?

Like, I don't need it to recommend me projects my friends are working on, or at the very least it should be rare. I'm pretty sure there's a lot of shit I work on that nobody else cares about (e.g. if you follow my #Ruffle repo that doesn't mean you want to know about #PDDiffusion )

https://wicg.github.io/direct-sockets/

My first reaction: Oh my god is #Google playing around with new ways to design security vulnerabilites into the web?

My second reaction: Can we use this in #Ruffle to emulate RTMP and PeerConnection?

(We can't, this is only for a very specific kind of isolated webapp.)

@gentlemangeek I already use that app on an M1 Mini I bought last year to do #Ruffle things with. (Specifically so that Parsec can grab a 4K display off of it.)

Didn't think to try it on the M2 Macbook, though I wouldn't be surprised if the M2 just refuses to drive the 4K monitor because it's chroma-subsampled at 144hz.

I'm extremely happy to announce that #Ruffle is finally back on addons.mozilla.org! If you switched to the manual-install builds for #Firefox you may now switch back.

It took about a month of back-and-forth with #Mozilla staff. I'll do a full write-up later.

The good news is that we have reproducible builds now! And I was able to remove a lot of old cruft in our extension code too.

For today on #Ruffle I'm working on reproducible builds.

Why am I putting myself through hell? #Mozilla demands it. Anything other than hand-written JS has to be buildable by them and produce *bit exact* output from source.

So far, there's some simple, low-hanging fruit type stuff. Our build system includes version and Git commit data that Mozilla won't have. But we also have a problem with WASM itself: occasionally building WASM generates a file that's got a few exports shuffled around.

Adrian sent me some tests for #Ruffle that were supposed to be relatively easy to fix. Just allocate display objects before enterFrame.

Several days in and I'm already tearing off several "this is subtly wrong but SWFs can't see it so its fine" band-aids that only worked because we were doing everything a little too late.

@LunaFoxgirlVT On #Ruffle we recently had a scare where all our Ubuntu builds would consistently segfault, and all we added was safe Rust code.

Turned out the actual bug was... a Mesa update

On the #Ruffle side of things, I'm currently tracking down a bug that prevents Mochicrypt protected SWFs from running in Ruffle. Everything works (modulo some other fixes that Adrian hasn't PR'd yet) but the movie doesn't actually start; it just plays music and hangs.

Caught another bug in #Ruffle with Adrian today: https://github.com/ruffle-rs/ruffle/pull/8667

Implementing AS3 textfield scrolling in #Ruffle makes Tower of Heaven go in-game

Trying to merge in a bunch of #Ruffle PRs and I get this really helpful #GitHub notice.

It's a one-commit PR and I just used the normal update PR button that works fine for a rebase workflow. What is it even trying to tell me?