Toby

Hey @Forumovod, thanks for your kind words! I want to respond to two of your points:

you are developing alone and if something changes in your life plans, users will be left with nothing.

This is not quite true - Waterhole licenses are perpetual, so you are entitled to use the version covered by your license forever, regardless of what my life plans are. You have full access to the source code and can alter, modify or extend it in any way you like. Granted, you may be talking more about key person risk with regard to future development of the software, which is fair enough to consider (though I have no plans to discontinue development of Waterhole!)

I think it was more correct to first form a community around the new engine, then monetize it. A little activity seems to show that things are not going well so far.

It depends what you mean by "going well". For me, the goal of this project is not really growth for the sake of growth, but rather it is to make a product that I am really proud of, enjoy doing it, and work closely with paying customers to make sure they're satisfied. I'm really delighted to hear these testimonials from @Tyler DuPont and @Matt - thank you both

v0.3.2

v0.3.2 has been released with the following changelog:

Added

• Show comment button in post footer on mobile

Fixed

• Fix comment composer being unreachable on mobile (#44)
• Prevent composer re-appearing on page reload after it has been closed (#46)
• Fix comment composer not clearing after submission
• Prevent unnecessary post page load when jumping to page 1
• Only configure Laravel Echo if Pusher is configured
• Fix entire page scrolling when navigating through @mention suggestions

Thanks @seasider! I can't give any timeframes, but I can say what's planned (as it currently stands) and which things you are likely to see before others:

• Polls - planned, low priority
• Private messaging - planned, medium priority
• Reporting - planned, high priority
• Not following posts automatically - can be configured by user in Notification Preferences
• First post title and text too big - use custom CSS
• Hide reactions on post feed - use custom CSS or PostListItem::remove('reactions') (docs)
• Share posts to social media - not planned but would be easy for someone to make an extension
• Ignore users - not planned but would consider, low priority

No, unfortunately I've not been able to reproduce the issue, and it was never submitted on GitHub. If you're experiencing it too, would greatly appreciate if you can provide further information in a bug report.