Notes

I got this 3M Whisper Writer 1000 today but it was not able to advance the paper properly. I took it apart and found a cracked plastic piece on the stepper motor, modeled a replacement part, 3D printed it, and it works again.

WHO
ARE
YOU

VCF Midwest, Wikipedia Reader, and Subterm

https://jcs.org/2022/09/29/vcfmw

Assembling a laptop on stage as you are demoing it to the crowd feels like something only @FrameworkPuter@twitter.com could get away with now (though @gassee@twitter.com does it without any tools)

https://www.youtube.com/watch?v=ZzlQdWKmPuE

Well, it was this Z-Wave power control thing. When it's connected inline, it causes a buzzing through what I assume is the speaker.

How annoying that I swapped everything except the outlet it was plugged into. It was too loud at VCFMW to hear that it wasn't buzzing.

I've been getting an annoying buzzing from my Mac Plus BBS server for the past few weeks and it sounded like a bad flyback, so I replaced it but it didn't fix the problem. I just swapped CRTs, analog boards, and the logic board but it still buzzed. Any guesses what it was?

Someone walked off with one of my Mac Plus brochures while I was away from my table :(

My networking setup wasn't working here because the 10baseT DaynaPort ethernet adapters wouldn't negotiate with stuff I brought, so luckily someone was selling this janky old VolksNet 10baseT hub that made everything work to get
http://klud.ge back online from VCFMW

I am at @vcfmidwest@twitter.com, stop by and say hi (and take a cyberpals sticker)

Getting the kids all packed up for @vcfmidwest@twitter.com

wait what

It wouldn't be a Wiki without hyperlinks...

Vultr finally resolved the problem this morning, 49 hours after I initially reported it.

"We found and issue on one of the upstream switches that had a failing process. We have corrected the issue and now I see no more errors accumulating."

Seconds_Behind_Master: 94658

🥴

Going on 27 hours of downtime now. @Vultr@twitter.com support staff have only updated my ticket to tell me to stop opening new tickets. No update on the actual packet loss problem or when it will be resolved.

The only way I can get them to respond at all is to open a new ticket each time (I now have 3 open). Their only response beyond "we are currently working on your ticket" is this gem, telling me I'm SOL because it's the weekend (!)

Two of Pushover's @Vultr@twitter.com bare metal servers in their Seattle POP have been essentially down for going on 16 hours now due to ~60% packet loss on their network. They haven't provided any updates to my ticket or updated their network status page to reflect any outage. \

How about a live search box...

Well, it's a start...