ROPP: Portal/2025 Goals: Difference between revisions
From RO Wiki
No edit summary |
No edit summary |
||
| Line 51: | Line 51: | ||
| colspan="3" |RagNews has had an alpha and has had feedback from ROPP contributors which needs to be addressed before it can be launched to the public. Which then again needs to be re-launched once we're certain it's in a good position. | | colspan="3" |RagNews has had an alpha and has had feedback from ROPP contributors which needs to be addressed before it can be launched to the public. Which then again needs to be re-launched once we're certain it's in a good position. | ||
|} | |} | ||
[[Category:ROPP Pages]] | |||
[[Category:ROPP Governance]] | |||
Revision as of 23:34, 24 June 2025
Goals
| Goal | Progress |
|---|---|
| Growth - Opening Wiki To The Public | 0% |
| Currently due to spam we have a large volume of garbage e-mail addresses which are signing up to the wiki and posting spam. This is because the wiki in a sense has become a victim of its own success -- as our rankings have become higher in Google, we have immediately been hit with Spam from various locations. Balancing this has been difficult with the small resources we have had, due to the fact that we don't want to blanket ban areas like Russia from visiting the site, but we also don't want to open up signup because then so much junk would end up getting posted which would take up most of our resources to remove to get rid of it.
At the moment MediaWiki doesn't have great plugins which can be used for this purpose, so we'd need to roll our own and share it with the MediaWiki community so they can use it too. We do have plugins we have used which have stemmed most of the spam when we did have signups open, which had custom rules to prevent new accounts from creating new pages but, spam adapted so we have to, too. | |
| Stability - Migrating and improving Infrastructure | 15% |
| Even though we only have 50 or so articles, the demand on the service is getting higher. Currently it is not using a great deal of resources but we are getting a decent amount of traffic through to the site. To make updating and upgrading easier, this is starting to be migrated through onto aa different service to ensure that when more people are using it, the service can handle the load. | |
| Content - Launching RagNews | 0% |
| RagNews is the Ragnarok-Based news service which is written in GO and uses Facebook's LLaMa LLM to summarise content which is going on within the ragnarok community. Currently this is scraping all of the relevant sites within the RO universe and then outputting content. This needs to be systematised and then rolled out in the existing domain name. | |
Actions
| Action | Goal | Progress |
|---|---|---|
| Adding additional restrictions to account creation to gmail.com and requiring e-mail validation | Growth - Opening Wiki To The Public | 0% |
| Spammers can certainly create gmail accounts but much harder than just creating their own accounts. Until the plugin can be created (which is a significantly longer process) restricting to gmail, hotmail, protonmail is an easier restriction to ensure that genuine accounts can register, while garbage spam is nipped in the bud. | ||
| Creating plugin to lookup from various bot APIs before allowing account signup | Growth - Opening Wiki To The Public | 0% |
| If there is already an existing plugin when we come to review this, then we certainly will use it, but for the moment it appears that we'll need to create it and share back with the MediaWiki gang. | ||
| Migrate server to ansible-created infrastructure | Stability - Migrating and improving Infrastructure | 25% |
| Currently the main priority is moving the infrastructure to Infrastructure As Code so it can be reliably recreated. At the moment this is partially the case, but this needs to be completely moved to IaC. This will pave the way for then later migration to Kubernetes. | ||
| Tweak RagNews algorithm | Content - Launching RagNews | 0% |
| RagNews has had an alpha and has had feedback from ROPP contributors which needs to be addressed before it can be launched to the public. Which then again needs to be re-launched once we're certain it's in a good position. | ||