The NEW https://www.bbcmicrobot.com gallery is something special
Hundreds of interactive screens generated live by a BBC Micro emulator in a single webpage!
The best part - you can add to it live by sending your toot program to this bot
My favorite feature - you can break into any exhibit and type in it...
The pictures are emulations, not GIFs...
and no GIFs or PNGs are used in https://www.bbcmicrobot.com ... JSbeeb emulator renders everything in the browser from BBC Micro state snapshots.
(Yep the whole BBC Micro state can be captured in around 40KB, compressed to about 8KB, it's way smaller than a GIF would be....)
OK I omit some stuff, but RAM + CPU, ULA, CRTC REGs plus IC32 state seems to do the trick given enough commonality between systems running a bit of BASIC. The sysvia timers seems to sort themselves out
I was trying to get around the limitations of video codecs, and size of GIFs, for rendering 50Hz, pixel crisp animations... turns out a whole BBC Micro emulator is the optimal scheme
I used this license which is the best I could find “for don’t scrape this into your LLM training dataset”. Not that I expect companies will be hot on obtaining code for obsolete machines
@bbcmicrobot @bbcmicrobot I don't really understand why you felt motivated to change this license in a way where folks can't use it as freely.
That might make sense for, say, an artist selling images. But that doesn't quite seem to be your situation and in some cases I'm not sure you'd mind if someone did make commercial derivative works with a BBC Micro theme (e.g., embedding as a game mechanic). Are you worried this non-permissive license hurts the data long-term?
@Elucidating I know what you mean. The complete gallery (10000+ programs, only showing ~800 right now) has work from a lot of people who are credited with a link to their Mastodon account - so if someone wants to ask them permission, they can. What I wanted to avoid is someone wholesale scraping of the all data, but maybe the license isn’t perfect
@bbcmicrobot It's a really tough space to draw a line in. It's no fun being trawled up by a massive content sieve, but on the other hand if someone made a code debugging assistant for the BBC Micro that might be really interesting and help make the platform more accessible.
@Elucidating true about the assistant. Guess it’s a tough one because it’s a microcosm of the same issues playing out with much larger communities and datasets. Someone spends years nurturing a community, and contributors invest their time building it, then a third party (or even the community founder…) scoops up the data without permission and bottles it in an AI assistant. Are they in the wrong? Is a greater good served for future users? What is the etiquete, or law?
@bbcmicrobot I don't know about you, but I could maybe deal with a few less interesting times in my lifetime, and this is certainly one of them.