I found drivers for Linux and MacOS and the plan was to just share using cups once I could establish a connection. I'll come back to it at some point, I'm currently upgrading/cleaning up my home network.
The papd included with netatalk is broken with older LaserWriter drivers (and doesn't work with the GS/OS driver at all). You need to use LaserWriter 8 on the client side. The CUPS integration needs to be updated to compile against newer versions of CUPS as well. Once its "working", papd will automatically share any CUPS printer queues you have and cups-filters will convert the PostScript output from the Mac automatically.
I'm wondering if this could be adapted to a RPi0W, using the GPIO to interface with the Mac serial over AppleTalk, and NAT to the network using WiFi... Would the Mac serial port be able to provide the 5V power the RPi0W needs?
This would likely be the cheapest physical adaptation to get a classic Mac onto a WiFi network, while possibly providing more services also.
Wi-Fi and DDP AppleTalk is problematic. Apparently the issue is with access points not properly translating the packets. All Apple Airport units should work (naturally), but everything else is hit or miss.
Hrm, according to https://whitefiles.org/tec/pgs/h10b.htm the 5V power is only on pin 9, which my Classic and SE/30 don't have, so it would mean pulling power from a different port like ADB, SCSI, or floppy.
While I've been mostly talking about this project in the IRC channel, it occurred to me that 68kmla has (or, by some definitions, is) a forum, so I thought I'd better make a thread about it to document it and see what folks think. Introducing... TashTalk! Elevator Pitch It's a LocalTalk...