polkadot VS ruffle

Polkadot (6400 GitHub Stars) https://github.com/paritytech/polkadot

I don't think asynchronous backing has any direct effect on the number of parachains, no (I mean, there likely is an effect, but it's not the goal and my understanding is that any effect on that would be minimal, although I'm not involved in the deep engineering here). It increases throughput, correct, by decreasing the time between blocks by not needing to do a "roundtrip" to the relay chain to build new blocks. See https://github.com/paritytech/polkadot/issues/3779 for an overview.

"The 27 waiting day is unavoidable and a very important security measure to protect against certain attacks and vulnerabilities of PoS. I totally understand that it is annoying, but arguably it is for the benefit+security of the overall network, which includes you as well at the end of the day as DOT-holder." - from this GitHub discussion.

Ref: Kianenigma @ https://github.com/paritytech/polkadot/issues/2418

Polkadot 0.9.37 has been released with MEDIUM upgrade priority. https://github.com/paritytech/polkadot/releases/tag/v0.9.37

Specifically, it was this PR that changed it: https://github.com/paritytech/polkadot/pull/6230

Actually it looks like you can! It's just not recommended. This is from the official documentation: "Starting with runtime version v23 natively included in the client version 0.8.23, payouts can go to any custom address. If you'd like to redirect payments to an account that is neither the controller nor the stash account, set one up. Note that setting an exchange address as the recipient of the staking rewards is extremely unsafe.*

A particular validator sent out a LOT of dispute reports (i.e., saying that other validators did something incorrectly) last night (for reasons unknown). It looks like other nodes "choked" reading all of these disputes, and one subsystem died, stalling nodes but NOT killing the process. It's still being investigated, but you can look at the issue on Github to see it being discussed here: https://github.com/paritytech/polkadot/issues/6412

The memories…

I often wondered what would happen to those wonderful Orisinal mini games after Flash's death, without actually checking out the site. Would Ferry Halim find the time to port them to "HTML5"? Would they just… disappear forever?

It turns out that they know run in Ruffle[1], a Rust/WASM based Flash Player emulator I've never heard of (or forgotten about). The handful of them that I have tested work flawlessly.

[1] https://ruffle.rs/

shrug It finds its uses. It's just not that overstated.

sandspiel is quite popular and is built using WASM: https://sandspiel.club/

Google Earth - https://blog.chromium.org/2019/06/webassembly-brings-google-...

Ruffle (the "make Flash run safely" tool) - https://ruffle.rs/

Ableton's Learning Synths - https://learningsynths.ableton.com/

etc etc. It's just hard to tell when something is using WASM when it "just works" and is indistinguishable from optimized JavaScript

I was amazed that the site still runs, apparently still using the same engine.

But it seems that it was a flash site (of course), and archive.org seems to replace Flash Player with "Ruffle" [1]. Either that, or someone of Tobin's team replaced Flash with Ruffle >= 2019.

[1] https://ruffle.rs/

Out of curiosity a couple months ago I wondered if I could play my old Proximity flash game on Newgrounds from the browser within the Quest 3 VR headset, and it worked great!

That led me to do a little searching, and I discovered that originally the game didn't work in Ruffle, as I apparently did something with the play game button that wasn't normal. But someone put a fix in it back in 2020[1] in order to get my game working again. That was pretty neat. Felt kind of nice that people still cared enough about my old game to make sure it still works in an emulator.

Still working on a more in-depth sequel (using Monogame), and I'm way overdue to make a new web version of the original. Might knock that out once I get closer to getting the sequel out there.

[1]: https://github.com/ruffle-rs/ruffle/pull/1024

i believe it's using Ruffle[0] and that's already happened[1]

[0] https://github.com/ruffle-rs/ruffle

This is all using a really cool Flash emulator called https://github.com/ruffle-rs/ruffle