Allow forum Post Owners more authority.

[void fossil]

Meaning if a Forum Post owner requests the Post to be deleted it should be. Regardless of what anyone else thinks.

[paper mountain]

I have an opinion on this, if for example somebody post something in #1072983602821861426 why should they be able to remove it without going through the moderators, unless there is a partcular reason things posted in there should never be removed.

However for forum post in showcase, yeah. I agree people should be able to delete post, notv really sure why they couldn't?

[hazy veldt]

Yeah, I agree on this. This is something us moderstors cannot really experience, but if that's the case, which it seems, i'm assuming it is some old system that was implemented with the addition of forums to discord. I'll bring this to the team.

It seems it is a restriction still, yeah. Discord does not allow forum post owners to close their posts.

Users can request their posts to be deleted through a ticket, that's how we can adress this issue.

[void fossil]

Well if they choose to not share it anymore why should they not have the authority to say they want it removed. They created the templates and such afterall.
Just saying

[hazy veldt]

They already have the authority to remove it. All users are able to delete their messages, even though discord limitations restrict post owners from deleting their posts.

[round raft]

It'd be helpful to at least be able to close the forum in help channels

[crimson helm]

Well, what about bot that will be able to close posts or delete them, bot can check if given user is original poster or not

[hazy veldt]

I don’t think that’s necessary

[round raft]

BB has it

[void fossil]

Was gonna mention that. They have it where you as the poster types a command afterwards and it closes the post. It's simple but works.

[crimson helm]

what is BB?

[void fossil]

I've seen a server that has a bot that people can type a command to close a forum post and it then makes it so nobody else can talk in it

[crimson helm]

ya, its called locking/archivation

i have done that for my server as well, but only moderators are able to lock it, its like optional parameter

[round raft]

Blockbench

[hazy veldt]

I still don’t think a bot for such a small addition would make sense to have

[void fossil]

Then integrate it with one already here

[crimson helm]

Ya, i also was thinking about it

[hazy veldt]

Why not just open a ticket if you want to close the post?

[void fossil]

And potentially wait an extended amount of time... when a simple /close and it's done right there and then

[hazy veldt]

I wouldn't take action on assumptions

[crimson helm]

but tickets are managed by moderators right so you are forced to do it on your own or its like automated?

not sure how tickets works

[hazy veldt]

Yeah, that's correct. Tickets are menaged by our staff team.

[crimson helm]

ya, so is it good idea solving x posts per hour by hand?

i mean if that could be implemented in bot?

[void fossil]

The issue with involving a staff is they could refuse to close a post. Nobody should have a say in if a post should be closed or not besides the one who made it.

Unless it's contents violate the discords rules then that's an exception

And then the rights of the post owner is overriden

[hazy veldt]

We won't refuse to close a post if the post owner request it to be closed.

[hazy veldt]

The thing is, we don't want to have a bot/s for everything, specially when it is not a need.

I can see how this could be useful, yes, but seeing how small of a problem this is, I don't think we need to invest time in creating or implementing a solution like a bot for something we can handle through tickets.