tobyzerner

5 ms·

1. 1.▲
   Show HN: Waterhole – modern community forum software(waterhole.dev)

   2 points by tobyzerner 3y ago|0 comments
2. 2.▲
   by tobyzerner 11y ago

   It's buggy, prone to spam, probably not secure, missing features, etc. Probably should've named it an alpha, almost. But if you're game you could give it a spin - we're running our support forum on it currently. Will fil
3. 3.▲
   by tobyzerner 11y ago

   Thanks! Technology stack is PHP, JavaScript (Mithril), Less. More info here: http://flarum.org/docs/extend/
4. 4.▲
   by tobyzerner 11y ago

   Just made one: https://github.com/flarum/core/issues/274
5. 5.▲
   by tobyzerner 11y ago

   Mind reporting an issue for this? ( https://github.com/flarum/core/issues ) I can't test directly because I'm using a Mac, but it would be great if we can continue investigating on GitHub :)
6. 6.▲
   by tobyzerner 11y ago

   This is something we haven't tackled yet, but we definitely want to make this kind of thing easy at some point in the future.
7. 7.▲
   by tobyzerner 11y ago

   Thanks for the feedback! 1. Fixed. 2. https://github.com/flarum/tags/issues/10 4. Haha, I don't want to pay for Pusher right now. Will be working on a self-hosted push solution soon. 6. https:/&#x2
8. 8.▲
   by tobyzerner 11y ago

   Fair points. I guess I consider esoTalk to be somewhat of a lost cause in terms of the way it's built. It's a pain to implement fixes and features, maintain, and is pretty limited in what it can do (and how it can be extended). Si
9. 9.▲
   by tobyzerner 11y ago

   Flarum automatically redirects to the non-JS version if there's an error booting up the JS app. What browser are you using?
10. 10.▲
    by tobyzerner 11y ago

    We built Flarum to be highly extensible, so something like this could easily be implemented! Eventually we'll probably make an official Q&A extension too. If you want to learn more about Flarum's extensibility, check out http
11. 11.▲
    by tobyzerner 11y ago

    On the other hand, Flarum has a fully-functional JSON API which can fulfill some of those use cases. See http://flarum.org/docs/api for more info - and you can see it in action at http://discuss.flarum.org&#
12. 12.▲
    by tobyzerner 11y ago

    We output a copy of the page's data within <noscript> tags. (e.g. http://discuss.flarum.org/?nojs=1 ) Admittedly it's currently pretty bare-bones and not actually very optimized, haha
13. 13.▲
    by tobyzerner 11y ago

    It doesn't at the moment! D: That's something we plan to address very soon though. Not sure what specific strategies we'll implement – will sit down and nut it out in the next week or two. https://github.com/f
14. 14.▲
    by tobyzerner 11y ago

    Can I ask specifically what you don't like about the direction Discourse/Flarum are taking? I can't hope to compete with Discourse on features (yet!), but I think Flarum's elegance sets it apart. Out of the box, it'
15. 15.▲
    by tobyzerner 11y ago

    Thanks! The compiled source ( http://flarum.org/download ) should run on shared hosting no problems. The bash scripts are only for building that ZIP that we put up for download, and setting up a Vagrant development environmen
16. 16.▲
    by tobyzerner 11y ago

    The JS framework change (Ember to Mithril) was a great decision for us, especially given our focus on being fast and lightweight. The codebase ended up being far simpler too. I've been meaning to write a blog post about all the details
17. 17.▲
    Show HN: Flarum – Delightfully simple open-source forum software(flarum.org)

    163 points by tobyzerner 11y ago|78 comments