migrations about social_stream HOT 7 CLOSED

Hi ehaselwanter,
Social Stream is not currently mature enough for a production environment. Besides, the database schema is still constantly (although decreasingly) changing, so it is currently a burden for us to maintain migrations.

Of course, we will support them when the schema becomes stable.

from social_stream.

I see. Just wanted to let you know. Another question. Why is the e-mail in the Actor rather than the User? I think it is ok to have it in the Actor but can't see the advantage. I think it would be better to have the user as the hub for his actors. and the user should have the e-mail for password reset, etc ...

from social_stream.

and i would suggest to use haml, sass and compass. much easier to maintain than erb (IMHO)

from social_stream.

what do you think about the friending and message/post part of social_stream. is this mature enough for production use. I would like to have something like that in one of my apps ..

from social_stream.

Hi ehaselwanter,

Email is in Actor because we think Actors (users, groups, institutions, departments, etc) usually have an email. So it is a common attribute for every actor type (subject).

The friending part has only one feature left to be stable, customizing relations and permissions (issue #25)

The message part is going to be released as a separate gem (#34), though it will be fully integrated in Social Stream. But the messages table will be replaced.

from social_stream.

This is based on Wasserman book,
Check it.
http://books.google.com/books?id=CAm2DpIqRUIC&printsec=frontcover&dq=social+networks+wasserman&hl=en&ei=kEF6TdqxCo3fsgbM5M3sBw&sa=X&oi=book_result&ct=result&resnum=1&ved=0CCsQ6AEwAA#v=onepage&q=social%20networks%20wasserman&f=false

from social_stream.

yes. it looks great and feels right. I try to include the friending (for user) and messaging into a small application of mine. at the moment just this parts. if this is running fine i'll try to extend on using groups

from social_stream.