The following was probably introduced by rMWc0107b8. Consider the following scenario:
- Block a single IP (say, 255.255.255.255)
- Block a CIDR range containing that IP (say, 255.255.255.254/31)
 |
On Special:Contributions/255.255.255.255, we get a block notice box like:
 |
I think the block for 255.255.255.255 should be prioritized here since it's most relevant. For other things:
- The remove block and change block links point to the (indirect) block for 255.255.255.254/31.
- Users (especially sysops) viewing the contributions page are most likely interested in whether the specific IP (255.255.255.255) itself is directly blocked.
However, the caveat is:
- If we change this behavior to show the direct block, the displayed log entry will no longer necessarily be the most recent one, even though the notice includes the message The latest active block log entry is provided below for reference:.
I think we can disregard the last point, prioritizing relevance over recency, but feedback on this trade-off would be appreciated.