Post-migration Twitter and Mastodon Thoughts

Note: While I recently dealt with my flight from Twitter, I’ve had some more time to think about my relative experiences, some of my motivations and changing expectations, and just where it is I feel I am heading. While originally meant as a series of Mastodon posts, it seemed to quickly outgrow that mode of expression. This topic remains, and may always remain, a work in progress for me…

I’ve been full time on Mastodon (here) since the deal closed, but had preempted that by registering soon after the deal was announced so I could start to settle in, and I fired up my own instance not long after that.

I couldn’t abide staying on Twitter (there) long term, even if the deal fell through, simply because of who the shareholders and board were choosing to approve the sale to.

Like many, I’d built a comfortable set of follows and followers on Twitter, and knew it would take a while to settle in here. I honestly resented the board for recommending the deal, although from a fiduciary standpoint I understood why they would pursue it given the tanking tech stock market.

While there are many I follow here (or am followed by here) who were on Twitter, it’s certainly not a complete overlap. But it’s certainly at least as interesting a mix!

I’m not sure if tools like Movetodon and Fedifinder will capture many more of the Twitter accounts I followed in their new home here if Twitter continues its URL ban. I may need to rely on others finding me while my Mastodon-referring Twitter account remains active, or just through mutual follows or serendipity.

As per my earlier Mastodon post, I struggle with potential rationalisations of people I followed on Twitter who it baffles me have not yet come over (or at least left Twitter).

I know for many disadvantaged folks the community there can be a literal lifeline (and I hope that can become the case here), but for those not facing those challenges, ignoring (or abetting) the cesspit that it’s becoming just seems like an especially wilful sort of ignorance to me.

And there’s certainly no point staying to try and fight the good fight – that fight is so heavily weighted in the opposition’s favour it’s no fight at all.

The “Mastodon’s too hard“ argument doesn’t cut it for me – Twitter was hard once (I can’t tell you how difficult it was for me to learn direct messages in the early days, or how to effectively use the . tagging method!), Facebook has a learning curve…in fact MySpace, Insta, Yahoo Groups – they all had learning curves!

For some, I think it’s a handy and especially wilful sort of laziness to just stay where they are. As in physical reality, inertia can be pretty powerful.

I’d originally intended on leaving my accounts there as zombie accounts to prevent my handles being overtaken, but that is seeming less and less useful as time goes by. If I’m never going back (and I am never going back), what do I care if my handles are snaffled? They weren’t even my first choices!

But I haven’t decided between just deactivating or deleting tweets then deactivating (would be interested in pros and cons). And I do want some more time for my inactive accounts to grab a few more of my contacts from there.

As it started to be the case on Twitter, I find I’m struggling to keep up with my timeline, but I think a not insignificant part of that is discussion about Twitter, so I’m going to filter relevant terms and obfuscations to improve the signal-to-Musk ratio. I don’t quite feel ready to unfollow anyone at the moment, so I’m hoping that brings things back under control. At least I’m not suffering the sort of low level anxiety I did on Twitter at not keeping up.

At least I can check in on my instance’s Federated Timeline every now and then in case I feel I’d like an update on Twitter goings on – I do still care about what’s happening over there, but I need some clearly delineated space, too.I

I very quickly settled on a strict rule that I don’t cross-post from my main account – Twitter gets nothing from me now.

And while I intended to extend this to phasing out posting to the Applesauce Fluxes Twitter account, I cut that offf early after one of the many egregious decisions Musk made (I think it was unbanning Trump, but it’s honestly all becoming a blur now).

I’ve seen so many interesting introduction posts here, not all overlapping my interests, but I’ve made an effort to boost as many as I remember to in case they overlap my followers’ interests. Now is the time for community building, and this seems a low effort contribution I can make towards that goal.

I still have to get in the habit of using more (don’t forget to !), but I think I’ve been remembering image descriptions/alt-text pretty reliably – CamelCasing hashtags and adding image descriptions are low cost (especially for what my time is worth!) ways of supporting accessibility here which I endorse wholeheartedly.

I know hashtags improve discoverability, but I’m not on a “get followed” drive, which is why I may have a lower impetus to actually utilise them more (for now).

I think that’s pretty well it at this stage. I’m enjoying Mastodon, recommend it wholeheartedly, and am still considering other fediverse usages. But for now, I really want to bed Mastodon down and feel as comfortable as I can.

P.S. Oh, and enough with the “John Mastodon” stuff already – I personally think owning that RWNJ would have been better by saying he either misread #JoanMastodon as , or, in typical RWNJ fashion, downplayed any role Joan Mastodon, John’s partner/mother/predecessor/whatever, had in establishing Mastodon the social network. And now I want to subvert the subversion, but it’s probably too late…

Flying free

Wow, what a year!

I’ll save you the boring details…well, most of them – I have something in particular I’d like to discuss today: joining The Federation.

No, not that Federation! Seriously! That Federation doesn’t even exist (yet).

I’m talking about the “federated universe”, or “Fediverse”, which has been in the news a bit recently with the shenanigans going on at Twitter (has it really only been 6 weeks since the takeover?!).

I’ve now abandoned Twitter and have hung out my shingle on Mastodon.

Note: don’t worry, I won’t provide a manifesto on why I’ve abandoned Twitter. Suffice it to say, I won’t be going back, and I’m very happy on Mastodon at this time.

For those new to the concept, the Fediverse is not a “Twitter replacement”, it’s really just all the servers online running an open protocol call “ActivityPub”, which is published/supported by the World Wide Web Consortium (W3C).

Similarly, Mastodon, while a microblogging platform like Twitter, is not a “drop in replacement” for Twitter. It has some very basic differences “baked in” at the design level which are beyond the scope of this post. Mastodon is also not the Fediverse – it is just a part of it.

The CliffsNotes version is that ActivityPub allows servers to talk to each other and clients to present a data model that allows sharing data across different server types.

Imagine if you could directly subscribe to/follow an Instagram account from Twitter, then like, repost, and respond to Instagram content from within your Twitter client.

For the various social networks which support ActivityPub, that sort of cross-network interaction is supported and designed into the protocol. Additionally, no single person or company (or group of people or companies) owns the Fediverse.

Me being me, I have created my own vanity Mastodon instance (server) which is the home for myself, WOzFest, and my Applesauce Fluxes image bot. I’ve actually consolidated that Mastodon server with my WordPress blog and image-posting bot code on the OCI instance I’ve discussed previously, in an attempt to simplify my life – of course, instead, it has introduced some complexities while I got things sorted, but it does make sense moving forward.

I honestly do feel better not being on Twitter and being on an open standard, non-algorithmic social network. Only about ⅓ of the accounts I followed on Twitter have migrated to Mastodon (or at least advertised the fact they’ve migrated), but I certainly feel it’s fulfilling my retro community social networking urges already.

I’m also considering the following ActivityPub servers (self-hosted or externally hosted) for my various needs:

  • OwnCast (streaming, to replace Twitch [WOzFest livestreams])
  • Write Freely (blogging, to replace WordPress [this blog])
  • Mobilizon (events, to replace Facebook Events [for WOzFest])

If I had the desire to post pictures or videos beyond the basic needs of this blog, I’d consider Pixelfed and PeerTube respectively, but I don’t foresee the need to do so in the near future.

For now, I’ll settle into Mastodon and possibly roll out the above useful (to me) instances/accounts, and hope to see many more do so as well across my many interests.

I’d love to hear about others’ experience with the Fediverse – feel free to comment here or reach out to me on the Fediverse: @europlus@europlus.zone.

Note: this blog is also available as a Fediverse account to follow: @europlus@blog.europlus.zone.

Update 8 December: manually reviewed my list of Twitter follows and I’ve found some more on Mastodon, so it’s not ¼, but ⅓ that have accounts there (out of a total of about 200).

WOzFest 23 Announcement (and 24, 25, 26, and 27!)

Wow, life sure is moving fast.

We now have frequent WOzFest attendee Dylan living with us (restarting Tween parenting in mid-late 50’s is proving…interesting), I have had to look for a job, and I found and started a new job – it’s just “Go! Go! Go!” here.

And, in two weeks I’ll have 2022’s first WOzFest, WOzFest 23 – start time is midday Sydney time (UTC+11), 2 April 2022. QFest 2022/1 will be held on the same day.

For the first time, I can actually announce the proposed schedule for all of a year’s WOzFests – after 2 April, the rest will be on the fourth Saturday of the odd months from May to November

This means the full scheduled looks like this:

WOzFest 281 April 2023
WOzFest 2920 May 2023
WOzFest 3022 July 2023
WOzFest 3123 September 2023
WOzFest 3225 November 2023

WOzFest 23 was going follow the “fourth Saturday of an odd month” scheme in March, but my son’s engagement party (!) is on 27 March, and we’re in voluntary pseudo-lockdown for the two weeks leading up to that to try and avoid being in isolation on the big day.

This means WOzFest 25 will align with KansasFest 2022, as has been the case with the July WOzFest for several years. In fact, this alignment is what I’m intending to use to determine the schedule moving forward for the 5 WOzFests I’m hoping to hold each year (which means, technically, I can announce the next year’s WOzFest schedule as soon as the next year’s KansasFest is announced).

I’ve not set a theme for any of 2022’s WOzFests yet – in the first instance, WOzFest 23 will just be a celebration of allowing attendees again into WOzFest HQ.

I will likely try to pick up some of my RetroChallenge 2021/10 projects, but may just be too caught up trying to catch up with my Apple ][ friends in person.

It’s highly unlikely there’ll be any government restrictions imposed between now and 2 April – however, if I get COVID before then and am isolating, I’ll have to postpone. There’s just no way I’m going to miss it!

Please note: even without a government stipulation on the vax status of visitors, I’ll be requiring WOzFest attendees to be double-vaxxed for the foreseeable future (don’t @ me).

WOzFest 23 or 24 will be the last WOzFest to use Google Meet to stream what I’m up to as Google is deprecating their free legacy edition I’ve been relying on – let me know if you’d like the link so you can connect up with us. I’ll be looking for an alternative as the year progresses.

I won’t be able to prepare the day before as I’ve not yet built up enough leave to do so, so for the moment I can just commit to the Saturdays being from 12:00 to 22:00 local time (if I can last that long) – UTC+11 for WOzFests 23 and 27 and UTC+10 for WOzFests 24-26.

As always, I’m continuing to raise funds via Ko-Fi. This allows small (or large!) donations to be made – check out my intro post there for the lowdown, and feel free to drop anything you can in the can to help me to run WOzFest moving forward.

New server, new look…new headaches!

Save some money, I thought.

Have some fun, I thought.

I’ll set up a free Oracle Cloud Infrastructure (OCI) instance and host this blog there, and, while I’m at it, I’ll set up another instance and post to the Applesauce Fluxes Twitter image bot account from that instance, I thought.

Easy-peasy, I thought.

Well…no, I discovered.

I know if I laid out what I did I’d be here longer than it took to set up(!), and, while I understand video guides can be really annoying, it actually makes sense for me to just post this handy video representation of what happened next:

Yes, this is really what happened 😞

In the end, I went through probably eight OCI instances, four WordPress setups/migrations, two nervous breakdowns, and one case of wine (only three of those facts are true, no matter how you swap the numbers).

I’m happy to discuss at length what I did/learnt throughout this process in direct messages or e-mail (or via a Zoom if [and I {very much} doubt it] there’s enough interest), but I won’t inflict every step I took on anyone who’s paying me the respect of reading this blog – I have too much respect for you.

However, I will offer some takeaways:

  • Nothing, and I mean nothing, is easy – OK, the decision to go down this path is way too easy, but after that, a big fat nope!
  • OCI works well and is performant enough for the tasks at hand – I would definitely recommend it for technically-savvy self-hosters;
  • Don’t bother if (often) being elbow deep in a Linux CLI scares you;
  • SSH key-based login is your friend;
  • Webmin is your friend;
  • OCI Boot Volume Backups are your friend;
  • Don’t expect to get it right the first (or second [or third {or…}]) time;
  • Unicode characters in WordPress posts don’t migrate via the Duplicator plugin I used (or its MySQL code is unable to cope with them);
  • twitterImgBot has bugs (and extraneous code for most uses) – but it’s generally clear enough to work through the code;
  • Custom Permalinks vs Virtual Hosts…OMFG, WHY?!;

Why did I inflict all this on myself (other than being a techno-masochist [of the geek {not perverted} kind])?

Well, I’d been forced to migrate my G Suite legacy free edition mail hosting services, and I chose to migrate them to iCloud+, so I was out AU$10/month more for the additional iCloud+ subscription…but I was saving about AU$2/month not needing extra Google Drive storage (I have a lot of archival e-mail)…and I would have been paying about AU$6/month for my hosting next year so I thought I could eliminate that and almost break even compared to my current setup…and I had unexpected free time (due to some dodgy employment shenanigans [not on my part])…and I’d done all this before at one time or another so it was going to be smoooooth.

NARRATOR: It was not “smoooooth”.

But I’m here now, I think I’ve squashed all the WordPress issues (Permalinks work, Unicode characters updated, incompatible table-generator replaced), I have the Applesauce Fluxes Twitter image bot humming on the same OCI instance (after a few glitches, some also Unicode-related, some bug-related) and I’ve even decided to update from the old Twenty Eleven WordPress theme to something much more modern – Twenty Sixteen!

Yes, I’m a techno-masochist luddite – put it on my gravestone.

Remembering Tony Diaz

Mid-afternoon during WOzFest Twenty BOO! 👻, frequent attendee Andrew, who had dialled into the Google Meet, announced in a shocked voice he’d just discovered Tony Diaz had passed away earlier in the week.

To say Andrew, Michael, and I were bewildered is an understatement. A real jolt, not only because Tony was only 54, but also because some of us had been in communication with him about a week before his passing.

Between then and now I’ve had time-consuming work and family matters to attend to, hence the delay in this post, but I was given the opportunity to contribute to the memorial for Tony published in the current issue of Juiced.GS, which can be found as a free download on the mag’s Samples page.

I’ve said much of what I felt I needed/wanted to say in that piece, so I’ll keep this short.

Tony was anti-exclusionary, loved to share his knowledge, and revelled in being around people who were enthusiastic about retro Apples and flying, his two great loves (actually, should extend that to three to include In-N-Out!).

I feel lucky to have met and known him, and to have seen him share his rare prototypes and knowledge, including at WOzFest-1 and WOzFest S7,D2.

He’ll be sorely missed at the next Oz KFest, and I’ll miss his virtual and occasional in-person WOzFest drop-ins. Take care, mate.

RetroChallenge 2021/10 Endgame, WOzFest Twenty BOO! 👻 Report.

What a month October was – while not a complete wash out, I certainly did not complete as much of my projects as I’d like (please put that on my gravestone). And I was subsequently swamped with work and family matters through into the New Year (Happy New Year, by the way!).

I’d pretty well done nothing between my last report and WOzFest Twenty BOO! 👻, so there are no missing updates to catch up on.

But progress is progress, so let’s get the lowdown on what progress there was last weekend…

  • europlus Refurbapalooza Resurrection – No progress. Work was just too busy to get to this one. I’ll have to save this Resurrection for another day (RetroChallenge 2022/04?!).
  • Lockdown WOzFests – Completed! Well, this was a sort of a cheat one, but I did get to chat with some people, which was especially comforting at WOzFest Twenty BOO! 👻 (see below).
  • Pirated software manual scans – Incomplete. The progress I made on this project was to finish removing all the hundreds of rusty staples holding each manual together. Now it’s just sheet feed scanning to follow – a pretty simple, if lengthy (there is a 13cm pile of paper to scan!), task.
  • Applesaucing – Incomplete. I did do some imaging at WOzFest Twenty BOO! 👻 for Call-A.P.P.L.E. of some of their original disks I had in one of my multitude of boxes which Bill Martens (a virtual attendee) suggested they didn’t have copies of, so at least what progress I did make on this was pretty targeted!
  • Citizen Science – No (effective) progress. I now have a funky magnetic field display film which I can use in conjunction with flux images of disks to get a sense of how the physical layout of magnets on modern devices relates to disk damage. When I get to work on this one, there’ll be some cool graphics to include in the findings.

WOzFest Twenty BOO! 👻, held on Saturday 30 October, was meant to see me get more done than staple removal and imaging 15 or so disks.

In my defence, the day was severely marred by the news received mid-afternoon that my friend, Tony Diaz, had passed away in America earlier that week.

I’ll leave my thoughts on Tony and his passing to a separate post, but sharing grief with other enthusiasts both locally and internationally was indeed comforting.

I had elected to keep WOzFest Twenty BOO! 👻 as (almost completely) virtual-only as my wife and I are keeping ourselves in an almost-lockdown for some time to come – only Michael from RCR was in attendance as he is in similar almost-lockdown circumstances at the moment, and he had a delivery for me. Sharing a 42m² room with one person who’s pretty well not seeing others seemed OK.

That meant I got to share pizza and ciders in real life, and remembrances of Tony in person and via Google Meet.

An additional project I took on for Saturday was setting up a 21″ iMac 2012 I’d been gifted the prior week – I have two 21″ iMacs I use for Applesaucing and scanning, and with the 2012 replacing a Mid-2010 machine, I was able to have the new one and the other one (2015) both set up for High Sierra and Catalina dual booting. This allows me to use 32-bit software (iWeb and scanner software) when needed, but also have more recent OSes on them.

Between OS installs and data and app migrations, that went on for much of Saturday, but the new machine is significantly lighter than the one it replaces, which makes puttering around in WOzFest HQ easier as I move things around for optimal placement when doing work.

I’m now trying to plan for this year’s five WOzFests – I think I have a schedule sorted, and will make an announcement as soon as I can.

RetroChallenge 2021/10 Days 2-3 Report: Progress, of sorts, and a WOzFest!

I’ll be honest – I didn’t get as much done during WOzFest RC 21/10 as I’d hoped – I did continue to set up WOzFest HQ for working on my projects, and I did get some Applesaucing done, but I hit a few roadblocks…

Firstly, I think one of my disk ][ drives with an Applesauce sync sensor is having issues, which I only fully appreciated after about 10 disks (with quite a few multiple attempts to capture some of them). At four plus minutes per attempt, well…

I put the “track 0 always coming up orange” as attributable to some sort of protection scheme Personal Software applied to the Visi* range of products, but I finally tried an unprotected disk and had similar issues.

Of course, that first unprotected disk I tried had actual track 0 issues when I tried a new drive, but fewer of them, and a second disk I tried worked first time.

And it wouldn’t be a RetroChallenge without further confounding issues – the first Visi* disk I went back to also had real issues on track 0! Gah!

Oh, and of course, in the mix was the drive’s head cable occasionally getting caught and making captures useless (the same data being captured as different tracks). Between all that, it took me a while to get in my groove!

Anyway, I was able to capture several disks, sometimes using multiple captures to create a single working image (a newer [and long desired] feature of the Applesauce software).

I still have a lot more disks to do, but am now feeling at least in a better position than mid-afternoon Saturday.

Today, I’ve just tided up a little and started to set up my second spare iMac so I can use my ScanSnap sheet feed scanner for the pirated software manuals. The scanner uses 32-bit software, so I’ve installed High Sierra and am just migrating the other spare iMac’s High Sierra apps and user so I don’t have to set everything up from scratch.

This will allow me to use either machine for Applesaucing or scanning, or a single machine for both in less busy times.

Google Meet worked OK once I installed and set up the “auto admit” extension – for some reason, even with the invite link, Google doesn’t allow attendees outside of the inviting domain to just enter the meeting. And the first “auto admit” extension I tried didn’t work. And you have to restart Chrome to make the settings stick.

For sharing my projects, I joined from the Applesauce-connected iMac to stream various windows as I captured disks, and from an iPhone above the disk ][ drive to watch the drive do its thing.

My first two attendees were international – RetroChallenge judge Eric and Josh “Get The Damn Batteries Out” Malone, both from the US, joined for a while at the start. We had a few Australians hooking in across the day and evening, and everyone just worked on their own projects or whatever and discussed whatever came to mind.

It was nice having the company throughout the day, and I can’t wait for WOzFest 22 when I’ll hopefully get a few updates on where everyone go to – and with the way our vaccine rollout is finally going, I’ll hopefully be allowed to have 10 attendees as well!

I also responded to a few posts on the Australian Computer Museum Society forums site in relation to our Team ACMS project – a AU$500 grant is up for grab for Australians who register an ACMS affiliation when entering RetroChallenge and post about their entry on the forum. There’s a large Aussie/ACMS contingent this RetroChallenge, which is great to see.

I can’t wait to get some more progress under my belt – the nice thing about the scanning especially is it’s pretty brainless for me to keep plugging away at (even during the week), while my other projects are more hands-on.

Catch up in a few days – will I be able to report useful progress?!

RetroChallenge 2021/10 Day 1 Report: Prep is all you need

Just spent the time after a morning work meeting prepping WOzFest HQ – mostly sorting and getting rid of rubbish.

Bought some chips and some booze, even if I will have to be a martyr and consume them myself!

Ready for a proper day or retro tomorrow during WOzFest RC 21/10 – DM me on Twitter for the Google Meet link.

WOzFest RC21/10 & WOzFest 22 Announcement

UPDATE: See details of a new project for my RetroChallenge 2021/10 entry below.

Firstly, an apology for forgetting to announce WOzFest ]20 HOME : GOTO 20 – life got in the way, and I just didn’t get around to posting here

And although it’s not far away, I’m very happy to announce the date for the next WOzFest: WOzFest RC 21/10 will be held on Saturday 2 October 2021, starting at midday Sydney time (UTC+10:00).

And, to top off the year, I can also announce that WOzFest 22 will be held on Saturday 30 October 2021, starting at midday Sydney time (UTC+11:00).

Why two WOzFests in one month? Well the name for ’21 should give the clue – I’m entering RetroChallenge 21/10, and it seemed a good way to bookend my efforts for the month.

The theme for WOzFest RC 21/10 and WOzFest 22 is, obviously, “RetroChallenge” – drop in, check out what I’m up to, and let me know your plans at WOzFest RC 21/10 and how you went at WOzFest 22.

My entry for RetroChallenge 2021/10 has four five parts:

  1. europlus Refurbapalooza Resurrection – my Apple ][ europlus refurbishment project has edged along since my last Retrochallenge entries, but I’ve started to kick up the pace. Can I get all my boards tested by the end of Retrochallenge 2021/10?!
  2. Lockdown WOzFests – to celebrate Retrochallenge 2021/10, I will schedule the next two WOzFests for 2 October and 30 October. Retrochallengers from around the globe should drop in to detail their plans at WOzFest RC 21/10, then describe the pain of how it went all awry at WOzFest 22! Share the love, pain, frustration, and triumphs!
  3. Pirated software manual scans – I have a 13cm pile of photocopied Apple ][ software manuals from WOzFest attendee Neville to scan and upload to the Internet Archive.
  4. Applesaucing – Similarly, I have a metric buttload of disks to image with my Applesauce, gotta just get back to it.
  5. NEW: Citizen Science – Floppy disks vs Magnets: I’ve seen discussion of magnets affecting disks, I’ve done it myself, and I jokingly place bad disks on WOzFest HQ’s fridge with HD magnets. But magnets are all around us now, and those into software preservation have to be careful. Join me as I test the effects of the various common (and maybe not so common) magnets in our modern lives on the media we’re here to preserve. If you have equipment to flux image a disk, and some magnets laying around, add your data to the pool so we can spread the warning far and wide – disks and magnets are not BFFs!

Yes, four five projects is a crazy an extra-crazy load to take on, but I’m crazy! Aim for the stars and you’ll blow up on the launchpad, I always say!

I encourage Australian entrants to also sign up at the Australian Computer Museum Society forums and detail your entries and progress in the RetroChallenge 2021/10 category there – a $500 grant is being offered by the Society for Aussie entrants to try and drive local engagement in the retro scene. Just make sure you tick the Australian Computer Museum Society affiliation tick box when entering RetroChallenge!

In addition, regular WOzFest attendee Andrew told me HacktoberFest 2021 is happening in October, so be sure to sign up to an open source project, and let us know what you’ll be working on during the month when you drop by.

Sydney is still in COVID lockdown, and will not see any easing of restrictions in relation to visitors until the Monday after 70% of the population 16 and over are double-vaxxed. This is currently due to happen towards the end of the first week of October, so WOzFest RC 21/10 will be a stream/virtual event only.

Once we hit 70%, five double-vaxxed visitors can attend, so that will be the minimum allowed for WOzFest 22 – but we’ll probably have achieved 90% double-vaxxed by 30 October, so the restrictions may have eased even further. Please note: even without a government stipulation on the vax status of visitors, I’ll be requiring WOzFest attendees to be double-vaxxed for the foreseeable future (don’t @ me). QR check in will be mandatory, as well.

I’ll be using Google Meet to stream what I’m up to and who I’m chatting to – let me know if you’d like the link so you can connect up with us.

As per recent WOzFests, I’ll be preparing the day before – the Google Meet link will work for all four days. Runtimes are Fridays from 11:00 local time to 17:00 local time (roughly), Saturdays from 12:00 to 22:00 local time (if I can make it that long) – UTC+10:00 for WOzFest RC 21/10 (and prep) and UTC+11:00 for WOzFest 22 (and prep).

As always, I’m continuing to raise funds via Ko-Fi. This allows small (or large!) donations to be made – check out my intro post there for the lowdown, and feel free to drop anything you can in the can to help me to run WOzFest moving forward.

I hope to (virtually) see you there!

Apple ][/][+ Motherboard Test Sheets v1.2

Not long after WOzFest 18 I released some test sheets for Apple ][ and ][+ motherboards, to help tracking the testing of components on a motherboard, with separate sheets for the major motherboard revisions from Rev0 to RFI.

I silently updated them to v1.1 after correcting a weird default in my layout program that saw much of what was supposed to be solid black set to a very dark grey. No actual content changed, so I didn’t make a hullabaloo about that minor revision.

Today, however, I’m proud to release v1.2 of all the sheets, with improved content and some rewording I think makes things a bit clearer. In the background, I’ve also re-organised the underlying Affinity Publisher file to make changing common components between motherboard revisions easier.

Importantly, I’ve also included a second page with more space for notes and a representation of the keyboard so you can quickly record which keys work and which don’t.

I appreciate the feedback I received from Mark and Ross here in Australia, which helped me to either include extra info or clarify existing info.

Using the sheets on a couple of my machines also helped, and drove me to prepare the keyboard representation as well.

Mark also pointed out that printing onto A3 (i.e. at about 140%) makes the board layout roughly life-size – he placed this enlarged printout over some anti-static foam and pushed the chip pins through the printout into the foam while cleaning the board – a great way to store chips while cleaning or working on a bare board!

So, give the below a squiz and let me know if there’s anything else I need to do – or just use them as you check your Apple ][s.

WOzFest Labs Apple II Motherboard Test Sheet – Revision 0Download
WOzFest Labs Apple II Motherboard Test Sheet – Revision 1-4Download
WOzFest Labs Apple II Motherboard Test Sheet – Revision 7Download
WOzFest Labs Apple II Motherboard Test Sheet – Revision RFIDownload