Add a parameter to the following messages:
*noarticletext
*noarticletext-nopermission
*newarticletext
$1 should be true it it's a user or user talk page and the current user is identical to this user.
This parameter isn't used by default, but it can be utilized with ParserFunctions to add a warning when the user is editing a user page of someone else.
Version: unspecified
Severity: enhancement
@Bawolff: That's true, I guess. In case that feature is disabled, we can add the parameter again.
@Platonides: That only works for once specific use case of this parameter. I could think of different messages for user talk pages, perhaps even a use in other namespaces (e.g. check if <username> is the current user in Project:Request_for_Adminship/<username>). A parameter is more flexible (it wouldn't be used by default, though).
I a more general matter, we should reconsider having one standard message for all namespaces. Sure, every project can use {{#switch: {{NAMESPACE}} | ... }} to include different messages, but it duplicates a lot of efforts (as every wiki has to implement that itself). Maybe we should create specific messages for some namespaces (article, talk, user, user talk, category, file) and one default message (for all other + any custom NS)?
I proposed it considering that it may be a usecase common enough, as opposed to providing different messages for each namespace + username, which most wikis may not want to perform.
Well, I didn't suggest to provide a different message for all namespace+username combination :)
However, I think for a newbie it'd be nice to have a message like "this is your user page, you can write something about yourself", "this is a user talk page. Use it to leave someone a message", "this is a talk page, you can discuss the article here". Namespaces is a concept that newbies are often confused of – accurate descriptions in messages could help.
The reason why those messages don't exist on every wiki is because they require some knowledge and time to set them up, not because they aren't useful. If we supply *some* of them by default, that could help. (Although I will admit that translating them would be a bit of work)