Asked: https://en.wikipedia.org/wiki/Wikipedia_talk:The_Wikipedia_Library#Incorrect_username%2Fpassword

Yes that's fine.

Sure :)

Taking this off the Kanban now that it's split into component tasks.

Splitting the work up to match the PRs. First PR ready for review at https://github.com/WikipediaLibrary/externallinks/pull/54

@John_Cummings Unfortunately not. What related task, out of interest?

Do I have to remove whole helper.py?

Yes :)

I've made an attempt to list every area where there is code relating to the activity feed or the 'hide application from activity feed' field. I may have missed something.

We don't have a clear understanding of what the problem is here so I would suggest you work on something else. Perhaps you could take up T213202? I'll update that task description with more technical details.

Checked my account and I can use Bundle access as expected, so this isn't a high priority issue.

I wonder if this has something to do with their username containing an ampersand.

Hi Yash - please see my comment in the PR. We don't have anyone with the availability to help with this at the moment, sorry.

Solution isn't obvious here and we don't have engineer bandwidth to provide guidance.

We've had some encouraging conversations with AJOL, and are awaiting their feedback on how & when we can move forward. They're a small organisation with lots of other work ongoing.

Update: This is currently going through license agreement discussions.

This is paused while we rework our generic MOU.

KCVelega's last email was on November 12, and highlighted 7 pending applications. This is a little confusing because the email doesn't specify which publishers those applications are for. In this case it's Termsoup, but he thought it was for Economic & Political Weekly. We don't send emails about those applications, however, because the partner is waitlisted. This is confusing in and of itself.

Unfortunately this coordinator doesn't have their email history to investigate.

I've asked the coordinator to check when they last received an email.

According to me only in pending and Under Discussion status withdraw button is required.
If you want withdraw button in the status other than pending and discussion then tell me.

It looks like there's no way to make a pull request or suggested edit on the Wiki. I'll make these changes soon, don't worry about this one Yash :)

Perhaps this should be documented at https://github.com/WikipediaLibrary/TWLight/wiki/Local-setup, with that page linked more prominently from the main README? :)

This feature was added by @Yash4357 in T243137 - perhaps you'd like to work on this? :)

This is waiting on a further round of exploration from Prateek.

We're moving ahead with a broader redesign of these tiles.

We've identified that the previous fixes were really only solving specific edge cases, and we have a broader underlying problem with the way we're calculating recent edits.

Right - so there's no database tracking the individual link additions and removals? That's what I'm interested in with this task.

this data should already be stored in MW.

Hi @Yash4357 - we had a quick chat about this and while the original ticket description mentions that we might want to keep Sent in some places, we think we could keep this simple and simply update the text everywhere. Let me first confirm that 'Finalized' is the text we want to go with and I'll give you the go ahead to start working on this :)

Coretheapple confirmed this is now working for them as expected.

User:Coretheapple is reporting that this issue persists, even after logging out and back in both yesterday and today.

Another user just reported a likely similar situation, username Coretheapple.

Looks like this could be similar to the issue I highlighted in https://phabricator.wikimedia.org/T265146#6542141, whereby we're sometimes not comparing data 30 days ago, but to 'previous data' that's more recent?

In this case, the user has a Bundle authorization with an expiry date of yesterday (https://wikipedialibrary.wmflabs.org/admin/users/authorization/11162/change/) implying they were Bundle eligible in the past and the Authorization got expired today due to an apparent lack of eligibility.

Moving this back to Ready for Dev.

Can I work on this issue ?

I think it should be at the top, under the "What resources do you want to access?" title.

Thanks! Our engineers are quite busy at the moment and this is a very low priority task, so apologies if it takes some time for review.

Sure! I'd recommend the following text:
"Library Bundle partners are not shown as eligibility is determined automatically."