Simple feedback

Hello, if OS persons are peoples making projects, why not simply restrict #assets to OS-Developers group only to post?

1 Like

Beyond my control, you’d have to ask @Crcoli737

2 Likes

Good Recommendation, I’ll look into it.

1 Like

If it was restricted to only OS-Devs, then how would we get OS devs? The Whole reason I suggested the OS-Devs group was so that people who made a post in #assets could join it and get special permissions.

1 Like

os devs are peoples who make projects, but are still normal members, its a request to join group, only os devs could post, u could still read and comment the post (also like it)

1 Like

Good point… Not sure how we could fix that.

1 Like

at this point os devs could lock bad assets, but only lock?

for me that a special perk

1 Like

Locking posts and closing topics are two different things.

1 Like

what do closing do? delete the page? that mods jobs, os devs could pin, unpin, lock, unlock assets

1 Like

Close prevents new replies, locking prevents editing.

1 Like

lemme list all the os perks in the asset category:

1 Like
  • close
  • unclose
  • lock
  • unlock
  • pin
  • unpin
  • delete messages

kinda a category mod

1 Like

Only flag things that are breaking the rules. Otherwise just dm me.

And you can’t give those permissions to a group. The only to moderation groups are admins and moderators.

1 Like

uk what, i just wanna see what do the close post ui looks like, may u can send a screenshot?

2 Likes


1 Like

I know, but how would we determine if someone was a OS-Dev if they can’t post in #assets? Currently a TL2 lock is perfect for it, as that way we can find out if the user makes open source things.

1 Like