User Details
- User Since
- Mar 15 2024, 2:51 PM (36 w, 4 d)
- Availability
- Available
- LDAP User
- Antonkokhwmde
- MediaWiki User
- Anton Kokh (WMDE) [ Global Accounts ]
Yesterday
We discussed the implementation with @dang .
It's not possible to remove the link and the title above the announcement without touching the parent repository.
Another problem is that the announcement will show up twice - pinned to the top of the page and directly in the history of announcements (it has to be assigned to a certain date and time).
This seems confusing to me.
Maybe, what would make it less confusing is if this announcement would just be added every Monday morning and then disappear (physically adding and removing the pinned-announcement.md on schedule).
{F57749268}
Would it be possible/meaningful, @Tarrow ?
Mon, Nov 25
Fri, Nov 22
I reached out to the user on Telegram, but haven't received a reply.
The use case remains interesting, I will park it for now to have it in mind.
Thu, Nov 21
@Charlie_WMDE Could you please create design for this setting?
Wed, Nov 20
@Charlie_WMDE Small question: is clearing the entered password some kind of UX best practice for these kinds of situations?
I'm thinking of a situation where the password was entered correctly, but the typo was in the login, for example, but then I have to re-enter the whole password again cause it got cleared.
I checked MediaWiki - it behaved like you described, so I'm not questioning it, just curious why this is considered an expected behavior rather than, for example, highlighting the entire password, so I could start typing right away
@Tarrow Is this the same as the one we discussed before - https://phabricator.wikimedia.org/T298896 ?
The user need is similar to T379272
Import seems to work?
@Tarrow says he hasn't seen this, and the person who reported it is not here anymore to ask about it
We want to remove the limit of instances.
We believe that all data on Cloud must be available to everyone under an open license.
We could clarify the use case and think of other ways to address it.
This is not necessary anymore because we've covered all instances in T375384
Tue, Nov 19
@Lucas_Werkmeister_WMDE @Ifrahkhanyaree_WMDE
The results that the graph builder on query-main and query-scholarly will actually come from query. So it wouldn't break, but the results won't be the same as you see in the table view, which I guess is not the expected behavior?
I agree
Mon, Nov 18
Depending on the scope that was meant for this ticket, this may or may not have been addressed by https://phabricator.wikimedia.org/T378627
Fri, Nov 15
Hi @Harej !
Could you please share the input you provide on the form?
Thanks!
Confirmed in T380018 that feature is still in use by Wikidata.
Asked @Lydia_Pintscher about the data on usage of this feature:
Will be resolved at the weekly :)
Wed, Nov 13
Wikibases are now in a shared index and there is no overhead.