The first in a new walkthrough series: Add a working classifier to the Appetizer and host it as a dark service!

If you’ve spent time with the OpenZiti Appetizer, you may have noticed this response: you sent a message, but it can’t be qualified at this time for offensiveness There’s a hate-speech classifier on the path every message takes, and it’s been waiting for a classifier to talk to. On the September 18 Ziti TV episode, I got curious about it and went down the “How do I get this thing to work?” rabbit hole. It turned out to be a nice tour of how OpenZiti authorization actually works! Here’s the fun part. The first thing you notice is that the classifier URL has no instance prefix, while every other service name in the demo is scoped. That looked like the answer, but it wasn’t.Prepare tags the Appetizer’s own identity with an unprefixed classifier-clients attribute, deliberately, in a file where everything else goes through scopedName. The dial side was built with one shared classifier in mind rather than one per instance. The URL is right as written. What’s left to build is the network…