Threadify - Modern Simple Extension for Threading & Nesting Replies

SyntaxOutlaw

I'm working on developing a new light extension that allows reply threads and thread nesting similar to reddit etc.

It's taking abit of work, so won't share the repo until it's in somewhat healthy state. But I'm wondering if there's anything specific that you want to see?

It requires the use of Flarum mentions extension but I think most people use it anyway and doesn't involve removing any other extensions etc. I know there were other attempts to do this that worked in the past I.E Evergreen but I think there's a need for this (I'm doing it for my own forum)

Let me know what you want to see! Here's my current work in progress:

watchmedash

I like this so much, please let me try it if you finish it

SyntaxOutlaw

watchmedash I absolutely will let you know. I'm very busy this weekend but hoping to have a V1 ready by end of next week. Really appreciate the enthusiasm!

luceos

There once was a tree based extension that might help you

https://discuss.flarum.org/d/24695-evergreen-comment-trees-for-flarum

Would be great having a a replacement. ✌️

SyntaxOutlaw

luceos I've seen this, it seems like it was very good back in the day. Hoping that Threadify will be lighter and easier to manage.

The plan is to build on top of the mentions plugin/extension instead of battling against it (which seems to be what evergreen did, they required you to remove plugins). But I won't say too much until I've finished my POC.

Watch this space!!

luceos

SyntaxOutlaw if extending mentions doesn't work, please do let us know how. You can also consider forking mentions and republishing it as a new extension. If you do, mark a conflict with mentions through composer though.

Good luck.

SyntaxOutlaw

luceos Great advice, I'll send updates here!

SyntaxOutlaw

First draft version is live, you can install with with composer. https://packagist.org/packages/syntaxoutlaw/threadify

Please install at your own risk as we're still in the throws of it, but I haven't had any bad outcomes personally.

Currently one issue created by me, with a workaround.

Would love some initial feedback! Seems to work so far!

Repo:
SyntaxOutlaw/threadify

(I've not a PHP/laravel dev so I've used cursor to help, so don't judge the code too much, once it's in a happy place I'll lint through and perfect it)

SyntaxOutlaw

P.S This will also threadify any old discussions too, and can be easily toggled on and off woohoo

luceos

The link to the flarum.org extension page

https://flarum.org/extension/syntaxoutlaw/threadify

SyntaxOutlaw

luceos thanks for this!

KBExit

Would be cool if you can get it to mimic what's already in discourse, where you will see the # of replies to a post and when you click it, it opens the thread.

SyntaxOutlaw

KBExit So rather than showing the entire thread depth, just show either none or a few, with a number of replies in a thread and a “Show more” button?

KBExit

SyntaxOutlaw Yes, my proposal for this is for the sake of organization. As the threads grow, I find it could get confusing.
The way I view Threads are a direct reply to that specific message. It won't contribute to the message as a whole, rather just that snippet for clarity etc.
Could be an option for the sake of more customizations or options to the beholder of said forum.

To elaborate, maybe Reddit would be the better option to compare this to.

SyntaxOutlaw

KBExit Yeah totally understand, I’ll consider this and some other settings for the next version.

I’d love if some of you would try it out and give me some feedback on how it feels etc

Cheers!

KBExit

SyntaxOutlaw I'll install a separate instance and check it out either tonight or tomorrow when I have time! Keep up the good work sir!

SyntaxOutlaw

Question for some more seasoned flarum devs:

For Threadify to work, I've added a new API which we use to pull posts in the correct order/format from the threadify_threads table:
(new Extend\Routes('api')) ->get('/discussions/{id}/threads', 'discussions.threads', ListDiscussionThreadsController::class)

This works fine when logged in as admin, but getting 403s when logged in as a normal user or not logged in at all, I'm going to guess this isn't to do with my specific api but how new APIs inherit permissions.

What is the correct way to make new APIs totally open for all to use?

Controller code: SyntaxOutlaw/threadifyblob/main/src/Api/Controller/ListDiscussionThreadsController.php
API definition:
SyntaxOutlaw/threadifyblob/main/extend.php

Any help on this would be great, it's a blocking bug

SyntaxOutlaw

SyntaxOutlaw Sorted this, realised I was checking for actor permissions but it's an open api/resource so absolutely no need - simply removed permission checks!