[...] it would be nice if the number of notifications on a user's Notifications page was adjustable in the same way as on Revision history pages. Searching 500 notifications at a time would be (in some ways) easier than 50.
See also T137862: Make Notification page filters bookmarkable
Personally, I think power-users know how to 'hack' a URL, so a frontend UI change is probably not even needed (but would of course be an optional bonus). Just surface the parameter=value in the URL (as T137862 is also asking for), and editors can hack it when they need to.
I'm the one who actually requested the change (see here: https://en.wikipedia.org/wiki/Wikipedia_talk:Notifications/FAQ#Searching_old_notifications?), but I'm not a "power user", so I wouldn't have known that. [sheepish] And after checking just now, I still don't know exactly to what you are referring, though I am familiar with hacking URLs—I can't find the URL in question to hack.
[...] though I am familiar with hacking URLs—I can't find the URL in question to hack.
That's precisely what I meant. :-) The URL https://en.wikipedia.org/wiki/Special:Notifications does not currently contain any additional info, beyond the name of the page. It never changes.
Most other special pages have URLs that change when [various things happen, e.g. going to page 2 of the results, or changing a filter]. That's what T137862: Make Notification page filters bookmarkable is asking for (to make those bits of information, each parameter=value pair, be visible and change directly in the URL for each page load)
That's precisely what I meant. :-) The URL https://en.wikipedia.org/wiki/Special:Notifications does not currently contain any additional info, beyond the name of the page. It never changes.
Oh—sorry. Definitely not a power user, at least as far as the underlying coding goes.
Edit: I'm actually looking for a specific notification from some years back. I know which user and the subject field, but not which article or when.
Oh—sorry. Definitely not a power user, at least as far as the underlying coding goes.
Hmm, I think maybe I'm explaining it badly? I should've used an example! I just mean that you would know (I think?) how to tweak this example link https://en.wikipedia.org/w/index.php?title=Special:Contributions/Quiddity&limit=50&target=Quiddity so that it showed 500 results instead of 50. And that you might remember to check the URL if you didn't see controls on the page itself.
My apologies if I'm mistaken, and it would be good to know if my assumption is wrong. :-)
(As you're someone with over 100k edits, I would instinctively refer to you as a power-user, though I understand that term might have more technical insinuations in other contexts, and hence it's ambiguous!)
Oh—sorry. Definitely not a power user, at least as far as the underlying coding goes.
Hmm, I think maybe I'm explaining it badly? I should've used an example! I just mean that you would know (I think?) how to tweak this example link https://en.wikipedia.org/w/index.php?title=Special:Contributions/Quiddity&limit=50&target=Quiddity so that it showed 500 results instead of 50. And that you might remember to check the URL if you didn't see controls on the page itself.
Oh, that I understood. It was here that I got a little lost:
That's what T137862: Make Notification page filters bookmarkable is asking for (to make those bits of information, each parameter=value pair, be visible and change directly in the URL for each page load)
I meant I'm not a power user when it comes to Phabricator, and what goes on here.
My apologies if I'm mistaken, and it would be good to know if my assumption is wrong. :-)
(As you're someone with over 100k edits, I would instinctively refer to you as a power-user, though I understand that term might have more technical insinuations in other contexts, and hence it's ambiguous!)
I'm pretty good with Wikipedia article layout, proof reading, and references/citations, but I'm less familiar with what goes on behind the scenes/in the wings.
I did take a look at the "Related Objects" topics linked above, but did not delve very deeply into them.