Page MenuHomePhabricator

Echo: Ability to link accounts for notifications
Open, LowestPublicFeature

Description

I have just logged into my bot account on en wiki and I have found that I have many many notifications, some are useful, some are not.

I think it would be a great idea to be able to 'forward' echo notifications from one account to another, i.e. it would be great if my main account got get a notification when my bot is mentioned.

Rather than forwarding this could also be done with a 'stalk' option where you can choose to stalk a users notifications (all of which link to publicly viewable info as far as I know)


Description from merged task:

Some users have multiple accounts, e.g. one for normal work and other for mobile.
When somebody mention other account, user have no information about this mention unless he use other account.

The same situation is when user's bot is mentioned/reverted/...

There should be some way how to receive notification for another accounts


See Also:
T16409: Allow user accounts to be 'linked' to a master account

Details

Reference
bz48892

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 1:36 AM
bzimport added a project: Notifications.
bzimport set Reference to bz48892.
bzimport added a subscriber: Unknown Object (MLST).

Few thoughts...

There are two options, "forwarding", in which the target user gets the notifications (with some indication that it has been forwarded) and the actual user does not, or "stalking" where both users get notifications and mark them as read individually.

I think stalking is a better option here, and opens up more uses.

To implement stalking we need:

  • An interface where users can link accounts together
    • We could re-use the token system, but I think that would be icky.
    • Way to store linked accounts...?
  • An interface to unlink accounts.
  • Internal changes to detect if a user is being stalked, and create additional notifications for that
  • Some way to annotate that a notification is a "stalked" one.

mano.queixo wrote:

It would help when an user is renamed, and in "historic pages" is needed to link to the old name.

Prioritization and scheduling of this bug is tracked on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/215

pinkampersand.wikimedia wrote:

Just giving this a more clear title.

Restricted Application added a project: Collaboration-Team-Triage. · View Herald TranscriptJun 3 2015, 1:04 AM
Stryn added a subscriber: Stryn.Jul 25 2015, 7:54 AM

Rather than forwarding this could also be done with a 'stalk' option where you can choose to stalk a users notifications (all of which link to publicly viewable info as far as I know)

They are not all public info.

E.g. which edit you are thanked for is not public, we just added excerpts of Special:EmailUser emails you received (even the *fact* that you received an email is not public).

However, the forwarding (with approval from both source and destination users) could potentially work.

If people want to receive notifications for accounts that they don't log into often, they can just set the notifications for those accounts to be emailed. I don't see any reason why we would need to build a new feature to address this case.

Quiddity updated the task description. (Show Details)
Quiddity set Security to None.
Quiddity added a subscriber: JAnD.
Aklapper lowered the priority of this task from Low to Lowest.Aug 24 2016, 9:33 AM

Lowering priority as per T50892#2033411

Lea_WMDE moved this task from Incoming to Other on the TCB-Team board.Aug 24 2016, 8:02 PM
Jony added a subscriber: Jony.Aug 22 2019, 3:56 AM
Restricted Application added a project: Growth-Team. · View Herald TranscriptAug 22 2019, 3:56 AM
kostajh changed the subtype of this task from "Task" to "Feature Request".
kostajh added a subscriber: kostajh.

The Growth-Team doesn't plan to work on this in the short-to-medium term but patches are welcome. Before a patch is submitted it would be a good idea to seek consensus on the approach, though (see T50892#525096).