Open source maintenance comes with a burden of a ton of hard decisions related to design, technical aspects, user interface, even coding styles.
When software gains mass adoptation and gets its spot in workflows of the large audience additional considerations should be taken into account.
Things like backwards compatibility and intuitive UX for new features are now on table.

By sharing experiences of rapid adoptation and hurdles through the lifespan of ffuf, this talk is aiming to shed some light on these issues, as well as answering questions like:

Feature requests and even some large contributions where the contributor might have worked for weeks for a feature might not be compatible with the software philosophy or roadmap, how to deal with those?

How much hand holding is necessary and should it be implemented if the cost is flexibility?

How far the responsibility of the software maintainer reaches when the tools are used in a harmul way and what they can do to mitigate it?