WilliamWDTK

A user has got in contact to suggest: > that requests made to a particular body could be sorted from oldest to newest or vice-versa with options for successful/unsuccessful/ unresolved...

> > This ensures that requesters still have access to at least know the existence of their request. Individual messages can still be hidden from the requester as needed. >...

This appears to have happened again. We'll see if there are any developments. I think it possibly is a plain-text issue. Here, the link had been fully rendered in the...

> This appears to have happened again. We'll see if there are any developments. I think it possibly is a plain-text issue. Here, the link had been fully rendered in...

Mentioned [here](https://www.railforums.co.uk/threads/dlr-timetables.139517/post-2827430)

See https://github.com/mysociety/alaveteli/issues/5999#issuecomment-1192312260 by @garethrees: > > I think a less intimidating link would be better > > At the moment the link needs to be as-is so that users are...

Are there any other actions where this could apply? (I assume excluding the emailed tokens used to verify email addresses.)

> Are there any other actions where this could apply? > > (I assume excluding the emailed tokens used to verify email addresses.) - Alter track subscriptions (currently `https://www.whatdotheyknow.com/profile/sign_in?r=%2Fuser%2FUSERNAME%23email_subscriptions`) Where...

I'd say ideally on CSV too, but I imagine that would increase timeouts on WDTK, which is a separate issue.

One could also have a lower limit for a point at which there is little benefit to an "add all" button, and the benefit of the user (perhaps more consciously)...