We will check in on this in a few days

Will need to merge PR first

YAY

Sharing the blueprint per our team meeting https://image-suggestion-api.toolforge.org/?doc

Just wanted to update this task with a note. We recently received another request about this.

@Dbrant shared this helpful context on Android:
There's nothing "structured" about [accessing archived talkpages]. A user can put a link to their archived talk pages on their main talk page, or they may not. They can put a link to the archives inside a template at the top of the page, or not. If they put it in a template, the app won't display it, similarly to mobile web: https://en.m.wikipedia.org/wiki/User_talk:Jimbo_Wales.

We can use the same langauge.

Looks good, I'm moving this to ready for release until we have regression testing.

After talking to @ppelberg I'm going to decline this task for now. Sending people to webview isn't ideal and the impact of people replying at the bottom isn't very different than what is happening on mobile web.

I am referencing

Editing Tenure is a bucket in Turnilo, not sure how we are recording that information.

Shay shared:

Based on the[[ https://docs.google.com/spreadsheets/d/1N_PAVerw0AO-GWdGwEnLd2DhLkB_kvkVMxAqbeEb56A/edit#gid=0 | validation document ]], my first list of languages we should be deliberate in getting translations in for the copy as early as possible include:

• dewiki
• frwiki
• svwiki
• viwiki
• ptwiki
• plwiki
• cebwiki
• ruwiki
• arwiki
• fawiki
• cswiki
• trwiki
• euwiki
• hewiki

Hey @Dbrant we got the following questions about the above schema:

• Is instrumentation related to the editor tenure missing in the draft scheme because it will be found in existing instrumentation or via username?
• Is the lang identifying all the different languages the app is set to, or only the 1st app language or device language? For example, someone might speak Danish natively and have that set as the primary language, but also may have added English and Chinese as additional languages?

Ok @schoenbaechler is finishing up the designs so I am increasing the priority of this. After the offsite it should increase to high.

Marking this as low until we Robin finish designs

I agree it is worth the tradeoff and also would prefer taking the approach listed by Robin

Talked to Robin and he agrees

In T273262#6816861, @cooltey wrote:

Hi @JTannerWMF and @schoenbaechler

Looks like sometimes the title of the main talk page will be cut off if it's too long.
Just curious that should we need to handle this as well?

@Dbrant helped me sort out having the latest version of alpha and it works on alpha and in production. This is good to go.

Accidentally unassigned @Sharvaniharan 😆

Move subject line to the left and bottom. Do it like the Contributions page.

From @Miriam :

The image is not depicting the subject of the article
The image is of very low quality
The image is relevant, but we would not use it on our Wiki
There is not enough metadata to understand the goodness of the image match
I am not expert enough on the article subject to judge the goodness of the image match
The image is just a placeholder for missing images
The image is not available
I did not understand the task

It is fixed on our production app, I still see the problem on alpha, does that matter @ABorbaWMF and @Dbrant ?

We are not going to prioritize this at the moment but it isn't completely off of the table. The team is having discussions about the future and strategy of the app. In a world where Editing is a priority on the app we can see instances of leveraging such a feature. As for right now there isn't enough evidence to prioritize it given the social implications and technical workload.

In our Board Refinement meeting we discussed converting to webview in instances that we take users out of the app, once we do that it should fix this case.

I've added details to this. We won't need to look at this for a month in a half so 3 release cycles.

We have answered all of the questions in this task so we can close it out