Bureaucrats, ninja, Administrators
67,565
edits
User talk:TheTechnician27: Difference between revisions
Jump to navigation
Jump to search
→123
No edit summary |
(→123) |
||
| Line 24: | Line 24: | ||
P.P.S. It works if no cloudflare check is involved. It seems to be a bit random, but you have to save any other smaller page w/ cloudflare check, then the middleman lets you save w/o checks (for a time). --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 11:05, 16 March 2024 (UTC) | P.P.S. It works if no cloudflare check is involved. It seems to be a bit random, but you have to save any other smaller page w/ cloudflare check, then the middleman lets you save w/o checks (for a time). --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 11:05, 16 March 2024 (UTC) | ||
:Regarding the guide, that was mostly me finding it intensely difficult to balance old 1.6.0 stuff and new 1.7.X stuff at the same time. Every few sentences throughout the article I would need to place side-by-side screenshots for both versions, and I would need to make constant, awkward disclaimers that something only applies to one version. I can't remember two years later if I simply gave up or if I decided to wait until the Qt version was properly out. I think at this point (given the website even walls off access to 1.6.0 now) that if a new guide is created, it'd be reasonable to create it around the Qt interface. But regarding Wikipedia, that actually still is a licensure issue. Wikipedia operates under a sharealike license for (what was at the time) CC-BY-SA 3.0, whereas we're CC-BY-NC-SA 3.0. That 'SA', sharealike, means it needs to stay under the same license, i.e. that we can't suddenly make it 'non-commercial' (that 'BY' also means attribution, which it seems we didn't do). And the GameFAQs issue does, I agree, become even more complicated because those descriptions may have been ripped from elsewhere. My broader point isn't that something bad will definitely happen with these descriptions; it's that it isn't proper to redistribute this content under a license it doesn't support. The main purpose behind the serials isn't so that there's a result in the searchbar (although I feel that is quite nice); it's that it makes for a way to automatically, from the outside, index every single game on the wiki just by its serial number. Because every page name serves as a unique global identifier, this would mean for instance that https://wiki.pcsx2.net/SCUS-97429 would link directly to the corresponding article for Jak X. Although I'm aware of the amount of time this would take, I feel like I was progressing quickly enough that it could've been completed solo within a couple months even had the pace fallen off. [[User:TheTechnician27|TheTechnician27]] ([[User talk:TheTechnician27|talk]]) 18:35, 16 March 2024 (UTC) | :Regarding the guide, that was mostly me finding it intensely difficult to balance old 1.6.0 stuff and new 1.7.X stuff at the same time. Every few sentences throughout the article I would need to place side-by-side screenshots for both versions, and I would need to make constant, awkward disclaimers that something only applies to one version. I can't remember two years later if I simply gave up or if I decided to wait until the Qt version was properly out. I think at this point (given the website even walls off access to 1.6.0 now) that if a new guide is created, it'd be reasonable to create it around the Qt interface. But regarding Wikipedia, that actually still is a licensure issue. Wikipedia operates under a sharealike license for (what was at the time) CC-BY-SA 3.0, whereas we're CC-BY-NC-SA 3.0. That 'SA', sharealike, means it needs to stay under the same license, i.e. that we can't suddenly make it 'non-commercial' (that 'BY' also means attribution, which it seems we didn't do). And the GameFAQs issue does, I agree, become even more complicated because those descriptions may have been ripped from elsewhere. My broader point isn't that something bad will definitely happen with these descriptions; it's that it isn't proper to redistribute this content under a license it doesn't support. The main purpose behind the serials isn't so that there's a result in the searchbar (although I feel that is quite nice); it's that it makes for a way to automatically, from the outside, index every single game on the wiki just by its serial number. Because every page name serves as a unique global identifier, this would mean for instance that https://wiki.pcsx2.net/SCUS-97429 would link directly to the corresponding article for Jak X. Although I'm aware of the amount of time this would take, I feel like I was progressing quickly enough that it could've been completed solo within a couple months even had the pace fallen off. [[User:TheTechnician27|TheTechnician27]] ([[User talk:TheTechnician27|talk]]) 18:35, 16 March 2024 (UTC) | ||
If you really want to spent ours of your life to implement such (imo, unnecessary) feature, who am I to stop you? Everyone sees fun differently. Two things to add on this: this will mess the wiki's Google index a bit (Google stores a limited amount of pages for a certain website, so these redirect pages will somewhat affect the visibility of real game articles); to make the work easier/faster I suggest writing a simple program, which would to take next line from a text file, parse it to URL and page text, start URL (opening another tab in your browser), emulate Alt+Shift+E keypress (or your Linux equivalent), wait until the browser window changes its title to "Creating ...", emulate Tab, put the page text into the clipboard (or your Linux equivalent), emulate Ctrl+V, wait a bit and emulate Alt+Shift+S. I used such simple scripts in the past to make a lot of semi-automatic changes (you can even modify pages this way). 10-15 pages at a time and some manual work in stubborn cases. You can also try and find real robots/crawlers on the internet, I prefer to use my own soft when I can help it. --[[User:Ngng|Ngng]] ([[User talk:Ngng|talk]]) 17:19, 17 March 2024 (UTC) | |||