George

I'd rather no have this, similar to a mandatory or default SSL layer for log transport, it's a security measure that should be implemented by the server administrator[s] if desired....

The whole plugin crashing the agent will be fixed this week (plugins will just return a result with the error), it's just that I hadn't had the time to implement...

Hmh, receptor plugin that "tracks" what plugins are being used is a nice idea in general (though an endpoint/plugin for email alerts would have to be a separate entity). So...

Currently two independent threads handle the receptor plugin message processing and agent plugin message receiving, they could even work as separate entities, they could even be separate processes if needed...

Hmh, database as a plugin sounds doable and could actually be nice to be fully flexible there... I think it makes sense, I can see a setup where receptor plugins...

Before the stable release I think the convention will be: -> Major version should match receptor/agent -> Minor version should also match receptor/agent (since we could make API changes in...

Hmh... I'm not sure I understand your point here. If someone decides to write a plugin that's for both the receptor and the agent (E.g. collector piece and processor piece...

The basic idea I originally had around endpoints is that they would be separate entities, basically just a self contained binary that know how to use the receptor's API and...

This concept of endpoints can even be applied if the receptor doesn't store it's own state via SQLite, but rather stores it's state via plugins that create a database and...

Curious about this too - `expo-av` seems to be missing a lot of basic functionality or have it poorly documented and background play is one such thing.