Collaborative Tools Project

I'm feeling a shade nostalgic today, because later I'm running a digital creativity session on coding with Livecode, which could be said to be an evolved descendent of my first geek love, HyperCard. https://docs.google.com/presentation/d/e/2PACX-1vSMsJFylC4xTI3St0LQa_tk9Z8YZnmh0yLWbJbU3cALsDheoSzzqVCVi1dOiimZdNLAggqF0goM9at9/pub?start=false&loop=false&delayms=3000 The ideas and values I originally fell for,  its ease of use, a "you can too" approach to coding, open sauciness and a community of edu-focussed sharing, and it being free (or cheap) still hold true today. There are still enough of the things I remember in Livecode to make it worth sharing with the world, make Livecode worth learning even today. Like a cult movie, it's always a pleasure to return to.

PLEASE DON'T ASK ME TO DO THIS FOR YOU :-) THIS IS JUST PROVIDED FOR INFO... At the University of York we have had an issue with Blogger for years , in that, when a user leaves the university and their account is deleted, although a blog post's text remains, and the blog itself, every blog post's image is LOST because they are stored somewhere in that user's account. I tried using command-line based scraping tools, like HTTrack to get a blog as static HTML files, but could never quite configure them to get all the content, the local images, the remote images but control the crawler enough not for them to wander off and try and download the entirety of YouTube. I tried scraping tools . I tried half a dozen aggregator tools. I tried process-oriented tools like IFTT. No joy. I tried writing my own scraper in python and failed. They moved the oAuth goalposts. I tried using Google Picasa (which they then shut down). I wanted to maybe use another servi