Disappointed to not see this in the core to be honest. An audit log is a fundamental part of any application and virtually all applications have this embedded as part of the core and it's free - at least, in every application I've ever written (and there's quite a few of those 
)
[deleted] Yep i totally agree, i am super disappointed. Stuff like this should be in core. Honestly i dont expect any features from flarum until the next 3 releases.. or maybe 4.
[deleted] Mark73 yes - WordPress has this baked into the core, and it's free to extract these logs with the Simple History plugin. I fully understand the desire for devs to be paid for the work they do - I'm one myself, so completely support that - but not for something that should be part of the core.
The argument here is that permissions are part of the core, so auditing and associated logs should be also.
[deleted] Its super important to have logs on your forum software. Overall flarum is still plain in user management.
[deleted] Its super important to have logs on your forum software
It's super important to have them in ANY software.
[deleted] True 
We've split the conversation into it's own thing as it's become off-topic from the extension itself.
Something I want to note here is that I agree it should be in core at some point. However as of today our focus is on stable, adding any feature to core at this point will delay the release possibly into next year which is something we are trying to avoid.
An audit log is currently not a priority right now. In the future, we'll most likely have one that extensions can hook into themselves (do not quote me on this, there are NO guarantees that any feature will make it into core, specially with the view we have for a simple base).
Until we get to that point (if we ever do), this extension is an alternative to that potential core feature. Similar to my admin dashboard extension - while that one is not paid, it sprung from a core issue about revamping the admin UI.
I understand people want many features to be included in the core software and/or not have to pay for them. But we have to remember that we can't include too many features in core or we risk over complicating it and making it less extensible. We also have to remember that Flarum core is not supposed to be your regular forum software.
I'm not saying we should or shouldn't have an audit log in core - I'm just pointing out the reasons why we don't yet and may never do.
Exactly what i meant 
I only hear stable
[deleted] Exactly what i meant
Would you prefer that flarum remain in beta forever?
askvortsov There is just stuff where flarum lacks that you cant put into the stable argument in my opinion.
[deleted] the stable argument
I'm a bit confused by what you mean by 'the stable argument'. Please do remember that flarum is developed by volunteers, each of whom have jobs, families, social lives, and other commitments as well. In addition to development, time also goes to moderation, community support, marketing, organizational infrastructure, IT systems, legal matters, etc. We are doing our best to make as much progress as we can, and in recent months, we have been accelerating even. That being said, there are limitations to what we can do, and our current priority is stable.
If you would like progress to happen faster (as we all would), the best ways to do that are to support us financially, find and report bugs, and/or if you're a developer, to contribute PRs and code review.
[deleted] We consider stable to be "people can use this for a longish period of time without worrying about extension breaking every release" not "we have all the same features as X" or "have all the main features our community has asked for"
The core of forum will probably add features at some point after stable, however as @datitisev pointed out Flarum is not like other software and core will ALWAYS remain minimal.
tankerkiller125 The point is, the goal of getting to stable is here for several years now, it kinda takes the trust for the users.
Circling back to the original point - any application, regardless of production state, should have an audit log or similar functionality. I'm in fact writing a PHP / jQuery based application for work right now, and the first function I wrote is a logging utility that captures all activity.
I'm not saying that stable should be delayed - far from it - but I am saying that audit logging should have been factored in at the outset.
[deleted] I am saying that audit logging should have been factored in at the outset.
You're probably right, it would have been very good to have this earlier on. But considering our code base, it should be pretty easy to implement (and it's definitely something I want to have in core as well). That being said, we're in the position we're in, and our current priorities need to focus on stable (especially the frontend rewrite).
askvortsov Understood. But a "paid" extension for what should be in core isn't something I'm willing to entertain. I completely understand paying for extensions that actually "extend" the core such as ReCache, Websockets, WordPress Integration, etc, and provide functionality outside of what the core is designed to do, but audit logging isn't a premium extension in my view.
