👋 FYI: is proposing some minor revisions to the Salty IM Spec to clean things up a little and make things even simpler. It also clarifies the Message Format as well as a way to support Events. Please comment if you have something to add, otherwise I'll make the revision and publish a new Salty IM Spev v1.1 👌

(#kvnawmq) cc @xuu and @mckinley (whom have both had a hand in helping with the spec so faro 🙇‍♂️)

(#kvnawmq) @prologic I'm having a hard time understanding this. If I wanted to create the ID `mckinley@mckinley.cc`, would I have to run an instance of the broker *on* mckinley.cc or could I use any broker server? If the latter is true, it's a little misleading to say I'm mckinley *at* mckinley.cc.

(#kvnawmq) @mckinley The later. But why do you think this is misleading? 🤔

(#kvnawmq) @mckinley Do you have time to jmp on a quick video call to hash this out? 🤔

(#kvnawmq) @prologic It's misleading because my communications aren't coming from the server that the domain mckinley.cc points to. Here, I'm mckinley@twtxt.net because my twtxt feed is on twtxt.net. I wouldn't really be McKinley *at* mckinley.cc using Salty. I would be McKinley, somewhere else. All it would signify is that I am somehow affiliated with the domain. That isn't necessarily a bad thing, it's just strange to me and I've never seen a service do that.

(#kvnawmq) @prologic I'm sorry. At the moment, I'm set up for neither videos nor calls. I'm going to bed in a few minutes, anyway.