OmniTalk WIP AIO AppleTalk Router, MacIP Gateway and AFP Server

[davecom]

I actually think “OmniSlop” is the most appropriate name for this project, specifically because it’s AI-generated.


If you look at what this system is doing—combining an AppleTalk router, MacIP gateway, AFP server, and potentially more—it’s not something that emerged from a single, clean architectural vision. It’s the result of aggregating patterns, protocols, and implementations from many different sources and eras, then synthesizing them into a single tool. That’s exactly how modern generative AI systems operate: they don’t invent from first principles, they compose from a large body of existing material.


In that context, the name breaks down in a meaningful way:

• “Omni” reflects the breadth of functionality—multiple services, multiple layers of the stack, all unified.
• “Slop” is an increasingly common shorthand for AI-generated output: something derived from a mixture of sources, not handcrafted line-by-line in the traditional sense.

Rather than being dismissive, the name is accurate and transparent about the methodology behind the project. It signals that this is a system built through synthesis—potentially fast-moving, highly capable, but also shaped by the quirks and inconsistencies of its inputs.


Compared to something like OmniTalk, which sounds polished and product-like, “OmniSlop” communicates something more honest: this is an ambitious, all-in-one tool produced through modern generative techniques, not a conventional, tightly scoped software product.


In a space like retro networking—where you’re already bridging decades-old protocols like AppleTalk and layering things like MacIP—that kind of transparency is actually valuable. It sets expectations correctly and acknowledges the unconventional way the project came together.


So taken seriously, “OmniSlop” isn’t a joke—it’s a precise description of both the scope and the process behind the project.

This is a super ironic post, because it's obviously written by an LLM.

 

[CC_333]

This is a super ironic post, because it's obviously written by an LLM.

Or cleverly written to mimic one....

c

 

[cheesestraws]

i've always thought of Fink more as a sort of middling language model

 

[mikes-macs]

middling language model

He wasn't paying attention. Omni in the name was ruled out because it's been taken.

 

[superpete]

For everyone who has not tried this yet, it is working (more or less). I've tried AFP over LToUDP on macOS. LToUDP needs a little fix though to allow the use of e.g. Mini vMac on the same machine.

Oh interesting. I haven't tested MacOS. It seemed to work fine with Minivmac on Windows. The LToUDP implementation in snow emu is much more robust.

 

[superpete]

I actually think “OmniSlop” is the most appropriate name for this project, specifically because it’s AI-generated.


If you look at what this system is doing—combining an AppleTalk router, MacIP gateway, AFP server, and potentially more—it’s not something that emerged from a single, clean architectural vision. It’s the result of aggregating patterns, protocols, and implementations from many different sources and eras, then synthesizing them into a single tool. That’s exactly how modern generative AI systems operate: they don’t invent from first principles, they compose from a large body of existing material.


In that context, the name breaks down in a meaningful way:

• “Omni” reflects the breadth of functionality—multiple services, multiple layers of the stack, all unified.
• “Slop” is an increasingly common shorthand for AI-generated output: something derived from a mixture of sources, not handcrafted line-by-line in the traditional sense.

Rather than being dismissive, the name is accurate and transparent about the methodology behind the project. It signals that this is a system built through synthesis—potentially fast-moving, highly capable, but also shaped by the quirks and inconsistencies of its inputs.


Compared to something like OmniTalk, which sounds polished and product-like, “OmniSlop” communicates something more honest: this is an ambitious, all-in-one tool produced through modern generative techniques, not a conventional, tightly scoped software product.


In a space like retro networking—where you’re already bridging decades-old protocols like AppleTalk and layering things like MacIP—that kind of transparency is actually valuable. It sets expectations correctly and acknowledges the unconventional way the project came together.


So taken seriously, “OmniSlop” isn’t a joke—it’s a precise description of both the scope and the process behind the project.

Yes, it definitely has smell of AI Slop, but I'm not hiding the fact that a substantial amount has been AI coded. Rather, it was the reason I started the project: to understand the limitations and capabilities of the various models and agents (and on something that should have few implementations go by). There's code generated by Sonnet, Opex, Codex and Gemini via Google Jules/Claude CLI and Github Co-pilot. To be honest I'm stunned it works at all! That said, there's been a lot of testing, guiding and suggestions back to the interfaces, going through Inside AppleTalk to correct mistakes, etc.

Anyway, as far as names go, I think I'm going to settle on ClassicStack. I plan to add IPX + Lanman/SMB 1.0 once I'm satisfied AppleTalk and AFP are working.

 

[Durosity]

Yes, it definitely has smell of AI Slop, but I'm not hiding the fact that a substantial amount has been AI coded.

I don’t think it’s fair to call all AI work slop. Stories and artwork created by ai, with all those usual tell tale signs and show low effort.. yeah, they definitely count as slop.. and frankly are becoming quite a problem. Applications and utilities that work as they’re expected to, and help solve a problem that existed and do so.. can we really call that slop?