search

sstephenson / hector

A private group chat server for people you trust
MIT License
131 stars 15 forks source link

Implement channel access controls #5

Closed clintecker closed 10 years ago

clintecker commented 14 years ago

This is kind of a big thing, but it would entail Hector talking to some sort of relational database to store persistant channel permissions. Ultimately I believe usernames and passwords themselves would be stored here.

Probably the easiest solution would be to use sqlite.

raws commented 13 years ago

I would probably implement channel access controls as authorize(username) on Hector::Identity.adapter.

In fact, even though channel access controls seem out of Hector's proper scope, Hector's default YamlIdentityAdapter could simply return true for everyone, leaving finer-grained controls for others to implement.

P.S. I know this issue is hella old and nobody except for Clint cares about it. I just happened to be looking at the list. Don't judge!

clintecker commented 13 years ago

:+1:

You would be passing in username + channel, though, right?

raws commented 13 years ago

Hmm, yeah. authorize_join(username, channel) or something. I can envision other authorize_ methods for decidedly un-Hector-like events such as kicking, opping, or even sending messages.

clintecker commented 13 years ago

How.... primitive.

raws commented 13 years ago

Your face is primitive

clintecker commented 12 years ago

hm!!

raws commented 12 years ago

GitHub is racist against eggplants and refuses to let me post one

jyotty commented 12 years ago

I think you mean AUBERGINE

GOD