Last modified: 2013-11-04 21:12:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T58028, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 56028 - Show Echo web notification to users who don't have an e-mail address associated with their account
Show Echo web notification to users who don't have an e-mail address associat...
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Echo (Other open bugs)
master
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-23 00:14 UTC by Matthew Flaschen
Modified: 2013-11-04 21:12 UTC (History)
6 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Matthew Flaschen 2013-10-23 00:14:36 UTC
Notify users a month after signup if they still don't have a confirmed email, warning them that they will not be able to reset their password.

Jared suggested this at https://www.mediawiki.org/wiki/Talk:Password_reset#Action_Items .
Comment 1 Kunal Mehta (Legoktm) 2013-10-23 00:21:48 UTC
Would this be sent to any user who creates an account and never confirms the email? I think that would be some pretty useless email in that case.

I'd narrow it down to users who are active past the 30 day mark and haven't confirmed their email yet. Also, I'm not sure if this belongs in Echo or whether it should go into it's own extension.
Comment 2 Jared Zimmerman (WMF) 2013-10-23 00:36:01 UTC
Steven and I were talking about this one and we came to the conclusion the notification should actually be triggered after 48 hours or first edit, whichever comes first. As for how the notification is sent? Echo. No question, we need to stop inventing new notification methods in every feature and start relying on each for this kind of thing. 

Confirmation email doesn't play into it at all since the whole point is that the user has not entered an email for their account…?
Comment 3 Jared Zimmerman (WMF) 2013-10-23 00:37:44 UTC
@Kunal, ah! I understand what you meant, a user who has entered an email address but not verified it. That is a separate but related issue. Can we either log it or link it to this one please.
Comment 4 Kunal Mehta (Legoktm) 2013-10-23 00:42:36 UTC
(In reply to comment #2)
> Steven and I were talking about this one and we came to the conclusion the
> notification should actually be triggered after 48 hours or first edit,
> whichever comes first. 

I think after the first edit might be a bit too quick, if the confirmation email hasn't made it yet (or they're more concentrated on editing!), then the notification isn't very useful. I like the time period idea better.

> As for how the notification is sent? Echo. No question,
> we need to stop inventing new notification methods in every feature and start
> relying on each for this kind of thing. 

Agreed, but that's not what I was talking about. I was asking whether this feature should live in the Echo extension or if it should be in a separate extension that integrates with Echo, like how Thanks is.

> Confirmation email doesn't play into it at all since the whole point is that
> the user has not entered an email for their account…?

D'oh. I wasn't thinking.
Comment 5 Jared Zimmerman (WMF) 2013-10-23 00:49:57 UTC
Basically the rational for after first edit is that now you've "done something worth saving" that can even be the call to action in the echo notification. e.g. Protect yourself from account access issues, and make sure you are alerted to changes on $articlename, add an email address to your account now for password resets and notifications."
Comment 6 Jared Zimmerman (WMF) 2013-10-23 00:51:00 UTC
Basically the rational for after first edit is that now you've "done something worth saving" that can even be the call to action in the echo notification. e.g. Protect yourself from account access issues, and make sure you are alerted to changes on $articlename, add an email address to your account now for password resets and notifications."
Comment 7 Matthew Flaschen 2013-10-23 23:57:59 UTC
I was originally thinking this bug would cover both people without any email and people without a confirmed email.  In either case, I was thinking only web notifications, since sites generally don't email a non-confirmed address more than once (the initial confirmation email).

However, I've created bug 56074 for the case where they have one, but it's not confirmed.
Comment 8 spage 2013-10-31 17:00:13 UTC
The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/385, but people from the community are welcome to contribute here and in Gerrit.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links