Page MenuHomeMiraheze

Installing UserPageEditProtection for wlhmn.tk
Closed, ResolvedPublic

Description

Wiki URLlhmn.miraheze.org (or wlhmn.tk)
ExtensionUserPageEditProtection

Event Timeline

Unknown Object (User) edited projects, added Extensions; removed MediaWiki.May 10 2021, 15:15
Unknown Object (User) claimed this task.May 10 2021, 15:16
Unknown Object (User) moved this task from Backlog to Security Review Needed on the Extensions board.
Unknown Object (User) moved this task from Backlog to Short Term on the MediaWiki (SRE) board.

@PiscesKazeMGR Hi, is there any reason why you can't use AuthorProtect? Unless I'm missing something it's the same principle.

@PiscesKazeMGR Hi, is there any reason why you can't use AuthorProtect? Unless I'm missing something it's the same principle.

I think my members should have a separate area for them to describe themselves; At the same time, if the user who created the user page is not the corresponding user, they would still have "author" permission, which means they could prevent the corresponding user from editing their own User: page.

Anyway, for faster progress, I will show you the differences between AP and UPEP.

AuthorProtectUserPageEditProtection
AffectingLock any page as desired by the author of the page, including Main and User namespace.Only lock pages in the User namespace; only allow editing for the corresponding user and sysop.
Trouble happening?YES. Vandalism users can manually create a member page with content that defames others and then lock it to prevent the victim from modifying it.NO.
Conclude=> Not safe for a community wiki!=> Protect users from vandalizing User namespace pages.

@PiscesKazeMGR I see. There is also an easier option which would be to set a Special:AbuseFilter with the following configuration and set to disallow:

(
 article_namespace == 2 &
 !user_name == article_text &
 !"/" in article_text &
 !"sysop" in user_groups
)

Let me know if this would work, otherwise the extension can be reviewed and potentially be added.

@PiscesKazeMGR I see. There is also an easier option which would be to set a Special:AbuseFilter with the following configuration and set to disallow:

(
 article_namespace == 2 &
 !user_name == article_text &
 !"/" in article_text &
 !"sysop" in user_groups
)

Let me know if this would work, otherwise the extension can be reviewed and potentially be added.

Nope. It failed. I have created another account and test if it work, but nothing happened.
I guess you would need to install the extension manualy, do you? '_'

@Reception123 Does the AuthorProtect extension even work on Miraheze? I've been thinking for some time we should consider uninstalling it, since I believe the issue is it requires a separate editauthorprotected restriction level from being added to each wiki (which we can't do, at least not easily, in ManageWiki. I haven't been able to get it to work on testwiki, at least not without an LS.php change.

Not sure on the functionality differences, but UserPageEditProtection does seem to be a simpler, better extension than AuthorProtect, so I'd 👍 uninstalling AuthorProtect and installing UserPageEditProtection (after a security review, of course)

@Reception123 Does the AuthorProtect extension even work on Miraheze? I've been thinking for some time we should consider uninstalling it, since I believe the issue is it requires a separate editauthorprotected restriction level from being added to each wiki (which we can't do, at least not easily, in ManageWiki. I haven't been able to get it to work on testwiki, at least not without an LS.php change.

Not sure on the functionality differences, but UserPageEditProtection does seem to be a simpler, better extension than AuthorProtect, so I'd 👍 uninstalling AuthorProtect and installing UserPageEditProtection (after a security review, of course)

Great idea, Dmehus.
I was thinking so much about why did that extension even exist '_'

Unknown Object (User) added a comment.May 12 2021, 18:22
This comment was removed by Unknown Object (User).
Unknown Object (User) closed this task as Resolved.May 14 2021, 04:19
Unknown Object (User) moved this task from Unsorted to Short Term on the Universal Omega board.