to/cc/bto/bcc not supported on activities

[Jessica Tallon]

As of #905 we now have activities in GMG. Activities however should have 4 extra fields which they currently do not have. These should specify who the activity goes to.

The fields are to/cc/bto/bcc. In these fields they can take Lists which need to be created. Lists can be user defined or a special type which are:

• Public (everyone including those not logged in)
• Following (those who are following the user posting)
• Followers (those who the user posting is following)

The concept of following a user currently doesn't exist in MediaGoblin however for this issue such a spcialised list should exist so that we can record who the user wants to show the media to but currently just be an empty list of users.

Discussions with Chris and Elrond about implementing this as it's a many to many for two types would be to have a Reciever model which User and List inherit from. The id would be on reciever and then you would have a foreignkey to the reciever

e.g.

class Reciever(Base):
    """ Model which represents person(s) who might recieve something """
    __tablename__ = "core__recievers"

    id = Column(Integer, primary_key=True)

class User(Reciever, UserMixin):
    # This would be the existing user model without the id as that's been moved to reciever.
    pass

class List(Reciever):
    # This would the representation of a List
    pass

I'm unsure how the special cases should be represented.

[JanKusanagi]

For the record, this is reversed:

• Following (those who are following the user posting)
• Followers (those who the user posting is following)

'Following' is the list of people the user is following.
'Followers' is the list of people who follow the user.

Also, Pump.io's webUI doesn't offer "Following" as a recipient (it'd make it easy to spam people who isn't following you), though another client could potentially use it (not sure if the server would distribute to it).

[Jessica Tallon]

I shall have to investigate what pump.io does when "Following" is specified through the API.

[Jessica Tallon]

I have largely done this, I have the changes needed on the models and mixins to have audience targeting. This just needs the migration I wrote to be fixed to work on SQLite, not sure how best to do that on alembic, maybe our old tooling will work.

I'm still actively working on this, hope to get it merged soon.