Skip to content

implement replacement listening history logging for client-side mixing #400

@hburgund

Description

@hburgund

could just be some kind of polling of apache logs?
or implement POST events/ in the client-side mixing code?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions