Would be kinda funny if the lone bananas have been removed from the training dataset because they are not part of the depicted item but are merely in the picture for scale :)
So, what's the solution to pairing socks? Buying many pairs from the same. Sure. That makes sense. But what happens when half of them are lost or damaged and you can't buy the same kind?
Do you end up as someone pairing socks again or do you throw away half of your socks?
You can always demote the other half of socks to cleaning supplies. They are really useful to stick your hand into and start going to all those hard to reach places all around the house, gathering dust. When done, just turn them inside out to trap the dust inside and THEN throw them away.
If you rotate your socks appropriately the other half is probably about to be damaged anyway, so just throw them out. The savings on using each sock until the very end are marginal.
Even nice socks are pretty cheap. Time spent thinking about socks is almost certainly negatively valued due to when factoring in opportunity costs. So yeah, toss the orphan socks.
In my 20s I used to think it was awesome to have all the same cheap white tube socks, just a drawer full of them that I didn't have to pair. Then somehow I got interested in merino wool socks and liked them. So eventually (expensive!) I built up a collection of them and most are different which means they all get paired after drying. Now I don't mind pairing them.
Maybe as one gets older they are less likely to mind pairing socks? Maybe as they get wealthier (as employment became much less immediately necessary to my comfort, something "snapped" and now I enjoy working (working hard) on things around the house). Maybe just having more expensive socks means one doesn't mind spending time with them.
I tend to get white socks or black socks. Over time, yes, different brands are not an exact match but in general, it's close enough for me and I just don't worry about it.
write a backdoor :)
A kernel module that drops the user into a root shell if they call an obscure kernel functionality with a secret value in some registers.
This should be somewhat easy to start and self-contained. If you want, you can easily extend it if you want things to become more fancy. E.g., hiding the secret constant. Implementing a challenge response protocol, limiting access to other global state (hardware dongle? ip address?) and so on.
Frankly, it's surprising how long they managed to drag it along given they build on top of a weird fork of Firefox ESR. Their foundation is crumbling for years and years. They really need to get off of it.
I recently used Ruffle [2] to get some Flash applications [0] working in the Pro version of my web browser [1], which is specifically designed to be remotely accessible and embeddable in an iframe. To run Ruffle on pages that require it, I utilize the Chrome Remote Debugging Protocol [3], similar to how a Chrome extension content script operates. Ruffle itself relies on WebAssembly and runs smoothly. It's been exciting to see the audio and video functionality of these old games restored and being able to play them again.
They did mention it. They use it for some of their older games but it seems like Ruffle isn't yet feature-complete with Action Script 3 and thus cannot be used to run their newer games
While Ruffle's AS3 support is still lacking a lot of features, since a couple months ago it's been able to play some simple games that require it. The build used on author's site is from 2021, and I just checked that the latest build is able to play several more AS3 games hosted there.
That's great news! I've been meaning to write a cron script or something to fetch the latest Ruffle every week or so, so thanks for reminding me to do that. Thanks also for your work on Ruffle, it's really great.
I'm waiting for it to develop further, I'm very excited, especially because I still play Crystal Saga everyday, I don't know why, but it's got something that I haven't been able to find in any other games.
But sadly, I haven't been able to make Crystal Saga work using Ruffle
MMOs are pretty much the last game Ruffle or any in-browser emulator will get to support - not just because it's likely some of the most complex piece of code you can find, but also because MMOs are likely to use sockets, which AFAIK can't really be accessed in modern browsers at all.
It sounds like adding those features to ruffle would have been three order of magnitudes easier than writing a flash player from scratch
I understand contributing to OSS is a pain (I often end up with half implemented features in my own branch and never manage to merge them upstream) but he could have saved himself some trouble.
It seems to me like a very different skillset required to reimplement a runtime like the SWF player vs hacking together an alternative FLA compiler that's just good enough to work on your own games.
Ruffle still doesn't support Actionscript 3.0, I suspect the task is not that straightforward.
> Runtime agnostic. ESLint should be able to run in any runtime, whether Node.js, Deno, the browser, or other. Runtime agnostic. ESLint should be able to run in any runtime, whether Node.js, Deno, the browser, or other. […]
Yeah, you're right, it doesn't quite apply here. But I think the general idea applies. JavaScript is supported, used and known by more developers than TypeScript, no matter if it's in the browser or not.
