Daniel McKnight

Thanks to @JarbasAl for this one here: https://github.com/NeonGeckoCom/neon_ww_plugin_efnet

> At one level - should we architect Mycroft in a way that a single instance could be used in the cloud by thousands of clients. There is a clear...

> Signal manager be something that lives in the messagebus-client module? Since one of the things we do there is setup standard ways of communicating over the messagebus with helper...

> Gotcha, sounds simpler than what I proposed :) > > But maybe the signal class may be a good fit over there if the SignalManager is a feature of...

> I think the status quo, where skills are just applets under a specified directory and the rest is Mycroft's problem, is ideal for newbies. I think tools are obstacles....

> I think **if** there is a switch to pip installable plugins there would likely be a time where the "old style" is supported before being removed completely. > >...

> My approach linked above (WIP) is to assume a user skill is meant to override a system skill, in case of conflicting ids the system skill should not load/be...

> I'm personally not a fan of having two ways to create skills either. The argument that the current system is easier for "newbs" is imo not a good one,...

> Just wanted to throw an extra line of thought into the mix... > > One of the big problems that I'd love to solve with "the next version of...

If an active intent is re-registered, it raises an exception that wasn't previously there which results in a spoken error. I think this could be safely caught in the `mycroft_skill`...