User talk:Tepples

From Pin Eight
Jump to: navigation, search
For older discussions, see archives: 1 2 3 4 5 6.

BootlegGames Wiki inclusion criteria[edit]

My understanding (as a non-member) is that the prohibition on creating new articles about "fan work" could be construed to exclude articles about recent commercial homebrew releases, though it may have been originally intended to exclude articles on PC fangames and non-commercial ROM hacks.

To the extent that recent commercial homebrew would be expected to meet stronger (that is, Wikipedia-like) notability criteria than other types of releases, your question about print run size is relevant. However, the fact remains that Sunday Funday is a reprint of an older unlicensed game. Anything I am misunderstanding here? --Eighty5cacao (talk) 02:58, 27 December 2014 (UTC)

About "older" and "recent": If they want to make it about date of first publication, then let them say so. But there are a lot of post-1996 productions on that site too because, as I understand it, famiclones stayed popular in BRIC-tier economies even into the N64 era. And if they're going for Wikipedia-like notability, you're not going to find a lot of stories in the anglophone MSM about Russian- and Chinese-langauge bootleg games either. --Tepples (talk) 16:24, 27 December 2014 (UTC)
I'm aware of the reply by KingPepe2010 at Help talk:Contents/Articles, which appears to hint at WP:CORP and/or Nintendo's hiring policies. However, upon rereading WP:CORP, I find that it would have the same problem as the general notability guideline when applied to pirate game companies. --Eighty5cacao (talk) 06:51, 28 December 2014 (UTC)
It appears that KingPepe2010 is currently uninterested in continuing the discussion. I'm guessing xe may be applying a couple criteria that I previously thought were too obvious to mention:
  1. A person or organization whose main public presence is on one or more non-notable websites (such as BootlegGames Wiki and Pin Eight themselves) is presumed to be a "fan"/"hobbyist" and therefore unsuitable for inclusion. (The idea is to avoid conflicts of interest by hobbyists who could document their own releases on their own website. For comparison, most well-known pirate companies have no active website nor any other public presence.)
  2. If the development process of a commercial release involves public non-commercial prototype builds, that may also weigh against inclusion. (This is the case for Action 53, which IIRC hasn't even been completed under that exact name.)
Comments/questions? --Eighty5cacao (talk) 22:26, 9 January 2015 (UTC)
Does Waixing really not have a website? See wikia:bootleggames:Fuzhou Waixing Computer Science & Technology Co.,LTD#External links. If COI is the real issue, I'd appreciate if they put in place something analogous to Wikipedia's COI processes, including explicitly defining COI and instituting a "Requested articles" process. I might try back after several more weeks of silence. --Tepples (talk) 16:44, 10 January 2015 (UTC)
In all fairness, I did say "most." (As usual, I haven't bothered to verify the liveness of any links.) Also, if I had realized from the beginning that COI was the most relevant/analogous policy, I could have kept this section a lot briefer. --Eighty5cacao (talk) 17:54, 10 January 2015 (UTC)

Full-time is the deciding factor now. --Tepples (talk) 23:58, 25 February 2015 (UTC)

Discontinuing rulewip[edit]

I just want to make sure you are aware of User talk:Eighty5cacao/misc/HTTPS Everywhere/rulewip#Discontinuing this project (as I will be performing the aforementioned "delayed RCC" of that page shortly).

I believe I am currently ready to proceed with deletion. Any decision on MW extensions and/or bot accounts? --Eighty5cacao (talk) 02:53, 27 December 2014 (UTC)

After seeing the edit summaries for the deletions performed so far, I feel that "Project may move to GitHub" needs clarification. If you meant my project, that wording is a bit misleading, as I have not yet registered on GitHub (theoretically Gitorious, BitBucket, or any sufficiently-public Git host could work); also, I am still somewhat too busy with education & personal life to give a timetable for such work. If you meant HTTPS Everywhere as a whole, its official presence on git(web).torproject.org and trac.torproject.org isn't going anywhere; the GitHub copy is provided merely for convenience. --Eighty5cacao (talk) 06:37, 28 December 2014 (UTC)
No objection to the current edit summaries. (What I meant above was that the wording in question should simply be removed, but it looks like you figured that out already.) --Eighty5cacao (talk) 02:43, 30 December 2014 (UTC)
While changing Talk:Eloi language to link to a free trope wiki, I discovered an alternative to RCC on its equivalent of Signpost. I might consider adding it come next time I upgrade MediaWiki, and no, I don't know exactly when that will be. --Tepples (talk) 20:18, 1 January 2015 (UTC)
That sounds useful for mass deletions like this one, but RCC would still be needed for project-scope issues with edits to existing pages, if I understand correctly. I know you have no intention to remove RCC; let's just hope there are no compatibility issues. --Eighty5cacao (talk) 21:53, 1 January 2015 (UTC)
To change the topic slightly, why did you undo (that is, re-show) my RCC of the deletion of the BuzzFeed subpage? Was this another mis-click? Do you legitimately need that action as a test case for RCLF or some other reason? Is it okay for me to RCC any other deletions in the meantime? --Eighty5cacao (talk) 22:09, 1 January 2015 (UTC)
I reshowed it because of the punny edit summary. Go ahead and RCC anything that uses a boilerplate summary if you have the time. And yes, RCC is staying. --Tepples (talk) 22:24, 1 January 2015 (UTC)

Well That About Wraps It Up for Bag[edit]

Is bag+SRS sustainable? Playing Forever V3.1 (5-bag loop) --Sisu (talk) 02:47, 4 January 2015 (UTC)

Thanks. That'll give me something to think about should Mr. Pajitnov stop hating free software. Should "The legend of BAG" by SuperRetardo9 be the new Tetris theme? --Tepples (talk) 19:29, 4 January 2015 (UTC)

TCRF HTTPS support[edit]

Announced on Twitter; my tests show enforcement via redirection and HSTS; just trivially change the scheme to https

(If I should post interwiki maintenance requests elsewhere in the future, please explain.) --Eighty5cacao (talk) 04:43, 20 January 2015 (UTC)

TVT vs. AtT category implementation[edit]

Regarding allthetropes:Thread:Talk:Enforced_Method_Acting/Long_term:

Since "category" is a "page type" on TV Tropes but a namespace in the MediaWiki software, AtT apparently chose to require the use of the Category namespace for all pages that were tagged as categories on TV Tropes, with the corresponding mainspace title as a redirect. (Were I starting AtT from scratch, I would have done this differently, having the trope description in mainspace and a separate category page containing only {{main}} in its lede.) Whether an AtT page is in the category or main namespace does not necessarily mean anything as to whether it is a valid trope.

Am I understanding correctly? --Eighty5cacao (talk) 02:09, 11 April 2015 (UTC)

TV Tropes drew a distinction between supertropes, which contained examples that didn't fit into any subtropes, and indexes, which contained no direct examples. If it changed the terminology in the past year, I wasn't aware. The "index" page type also triggered special behavior similar to that of MediaWiki categories, putting the index title at the bottom of all pages in the index. I think that's why All The Tropes used Category: to reflect indexes. Technically it's the inverse, as TV Tropes indexes specify category members on the index page, while MediaWiki categories are specified on each category member's page, but they appear the same to readers. --Tepples (talk) 03:07, 11 April 2015 (UTC)
Whoops. When I said "category" in my OP in reference to TVT, I obviously meant "index" - I had avoided visiting TVT for so long that I had forgotten the proper terminology, which is also why I forgot about supertropes. I know what a TVT index looks like; it's just the term that I had forgotten. --Eighty5cacao (talk) 18:04, 11 April 2015 (UTC)

A couple NESdev issues[edit]

While looking at this, I noticed that the link to the Taito L System driver should be changed to use GitHub.

Also, it seems some users are objecting to the Unicode-inspired naming of the NES 2.0 planes. --Eighty5cacao (talk) 20:55, 18 April 2015 (UTC)

Sorry for bumping this here, but it looks like the .cpp fix never made it into the article's GitHub link. --Eighty5cacao (talk) 19:10, 22 May 2016 (UTC)

PGCX864[edit]

I believe that this user may not be a native English speaker and that some other users may be confusing that with a different type of competence issue. It's probably best to start by giving him/her a proper welcome on the user talk page.

This person's native language may be Japanese, but I have no proof; although the same username is in use on YouTube and has some Japanese text in its avatar, there is no substantial Japanese text in the video titles or descriptions, and the user has not posted in the Japanese section of the NESdev forum.

(Not posting this directly on NESdev for various information-security reasons which I've mentioned before) --Eighty5cacao (talk) 23:05, 12 May 2015 (UTC)

Extensions causing problems with user script and stylesheet pages?[edit]

When I try to view any of my user scripts or stylesheets, I get:

MediaWiki internal error.

Exception caught inside exception handler.

Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information.

That is the entirety of the displayed text, and it is displayed in the generic serif font that the browser normally uses for HTML documents without stylesheets. Attempting to add &action=edit manually to the end of the URL does not change the message. &action=history and diffs are similarly broken for such pages.

My user scripts and stylesheets still exist and work correctly in the sense that they are loaded successfully on other pages. Could this be related to one of the Open Graph-related extensions you just installed?

(P.S. If you're wondering about this edit summary, I had misunderstood OG as something like "Original Google" because I hadn't read the site news yet.) --Eighty5cacao (talk) 01:23, 9 June 2015 (UTC)

I have configured LocalSettings.php not to load TwitterCards on pages whose title begins with User: and ends with .css or .js. Thank you for reporting this issue. --Tepples (talk) 03:00, 9 June 2015 (UTC)
I can confirm that the problem is fixed now. --Eighty5cacao (talk) 04:56, 9 June 2015 (UTC)

"Corrected the link to All The Tropes wiki"[edit]

Apparently Zzo38 was unfamiliar with protocol-relative links and/or the existence of HTTPS support on Orain.

(What sort of guidelines should be established about this?) --Eighty5cacao (talk) 18:39, 16 August 2015 (UTC)

Done. --Tepples (talk) 20:52, 16 August 2015 (UTC)
Protocol-relative extlinks make more sense on Pin Eight itself, where HTTPS is optional, than on a site like NESdev where only one protocol is provided. In the latter case, I would prefer just to hardcode https as long as there are no major problems. (This is just a note for future reference; I am not expecting any prompt action or reply.) --Eighty5cacao (talk) 04:05, 14 September 2015 (UTC)

The link in nesdev:User:Tepples that we were discussing here appears to need updating for the move to Miraheze. --Eighty5cacao (talk) 15:02, 30 September 2015 (UTC)

forum.gbadev.org[edit]

"Is forum.gbadev.org still running?" No.

www.gbadev.org still seems to work, but that isn't relevant to the question. --Eighty5cacao (talk) 01:11, 15 September 2015 (UTC)

The forum is back up as of this edit. --Eighty5cacao (talk) 06:52, 27 October 2015 (UTC)

Drakon[edit]

On another forum, Drakon has made some claims of having reformed his ways, but there is still much controversy. nesdev:User:Tepples/Drakon Shut Up and Glue was mentioned there.

This is not a request to modify or discontinue the project; I am neutral. Just letting you know. --Eighty5cacao (talk) 01:34, 16 September 2015 (UTC)

Status of AtT[edit]

Apparently there was some hacking involved in Orain's current downtime, and All The Tropes has decided to move to a new host. See this forum thread (found via Twitter and Reddit).

The allthetropes: interwiki prefix eventually needs to be updated to https://allthetropes.miraheze.org/wiki/$1; I'd be fine with it being pointed to Wikia in the meantime. (Pages on allthetropes.miraheze.org currently return 404; this is intentional, as the site has been closed to the public until the admins are done importing the backed-up data.) --Eighty5cacao (talk) 23:53, 22 September 2015 (UTC)

From the SiteNotice on https://allthetropes.miraheze.org/wiki/Main_Page: "The text import of All The Tropes wiki is done. The import itself is not done yet (e.g. images and some extensions need still need my attention). The wiki won't be deleted again now, so you are free to read and edit pages. Sorry for any inconvenience, and thank you for your patience. -- Southparkfan, Miraheze system administrator" A quick look reveals that at least the extension responsible for <choose> and <option> is still broken.
Miraheze appears to use HSTS, and it does not appear to use any CDN that would require SNI, so the interwiki prefix should probably be hardcoded to https.
As a reminder, no account information was transferred from Orain, so you will need to re-register manually. --Eighty5cacao (talk) 04:42, 25 September 2015 (UTC)

WikiWikiWeb[edit]

I'm aware of what's going on with WikiWikiWeb and the AHBL shutdown affecting it. Yes, if it is no longer open to editing, then it has ceased to be a "wiki" in the strict sense of the word. However, describing it as "dead" or "[no longer] in operation" implies to the average reader that it is closed to reading as well. Would you wish to consider a more descriptive wording?

Has Cunningham & Cunningham publicly stated a plan to shut down the server? Or are the pages already not loading for you? (I cannot reproduce any such problem.) --Eighty5cacao (talk) 20:41, 29 September 2015 (UTC)

The article on ATT is about markup, and markup of a UGC site is irrelevant to a site that has ceased to accept UGC. I wonder what wording would be better. --Tepples (talk) 14:42, 30 September 2015 (UTC)
I was aware of the context but didn't think it would overcome my fundamental objection. I regret that I don't have a specific suggestion. --Eighty5cacao (talk) 14:53, 30 September 2015 (UTC)

Custom domain[edit]

From the sitenotice: "All The Tropes is moving to its own domain on Christmas Day or Boxing Day (Dec 25 - 26), depending on your location (and when we actually do it). You'll be able to access us at https://allthetropes.org/ instead of https://allthetropes.miraheze.org/ after that time. Old links should automatically redirect to the new site, so you won't have to worry about link breakage." --Eighty5cacao (talk) 05:14, 21 December 2015 (UTC)

I can confirm that the redirection in question is now active. (They are still hosted on Miraheze; all they did was set up a custom domain.) It is now appropriate to reconfigure the interwiki link. --Eighty5cacao (talk) 19:20, 26 December 2015 (UTC)

Since I don't have any better place to dump this: This is an edit on explain xkcd by someone unfamiliar with the history of AtT, attempting to "fix" an Orain!AtT link by pointing it to TVT. I haven't bothered to take any action on this myself yet. --Eighty5cacao (talk) 22:03, 2 January 2016 (UTC) (+ 00:46, 3 January 2016 (UTC))

I know it's about to expire[edit]

WebFaction is running a clone of a very old version of Stack Exchange, from before upvoting and commenting required reputation. It has two questions about Let's Encrypt: Using Let's Encrypt to get SSL certificates and Planned support for Lets Encrypt. But there's "no ETA" and no mention in the official blog. So I'm going to have to go with StartSSL yet again. --Tepples (talk) 21:34, 3 December 2015 (UTC)

...and done. --Tepples (talk) 02:01, 4 December 2015 (UTC)

Edits by APK[edit]

I blanket-reverted some non-conforming edits on Talk:Hosts.

I don't see how APK (or meatpuppet thereof) is arguing effectively about the kernel-mode stuff (NB: I haven't bothered to read any of the linked Slashdot posts). However, the edit mentioning that APK Hosts File Engine sorts entries on disk seems to be in good faith, so perhaps it should be un-reverted and appropriate clarification provided in the article. --Eighty5cacao (talk) 21:20, 13 December 2015 (UTC)

I ended up responding to the second round with this instead of reverting. A little help please...? (I mentioned an "editnotice" in that edit summary; if further measures are warranted, my complete list of suggestions includes an editnotice, ABUSE filter, or protection with interstitial page à la Talk:Main Page, in roughly decreasing order of preference.) --Eighty5cacao (talk) 20:29, 15 December 2015 (UTC) (+ 17:33, 16 December 2015 (UTC))

NESdev issues, January 2016[edit]

freem's Neo Geo builds[edit]

I'm not clear to what extent you were being sarcastic here. Just in case you weren't:

MAME has a convention of using file extensions to indicate the labeled positions of ICs on the PCB where known. By #, freem presumably meant what is called \d in regular expressions (i.e., a digit). --Eighty5cacao (talk) 04:47, 2 January 2016 (UTC)

After I'd seen Mike Kohn's JVM for the Genesis, another 68000-based platform, a joke about a CLR on Neo Geo sounded almost plausible. I'll go back and edit in a clarification. --Tepples (talk) 13:37, 2 January 2016 (UTC)

GitHub Pages[edit]

Regarding a discussion about a website formerly operated by thefox, my understanding is that a GitHub Pages domain is necessarily tied to a GitHub repository, but GitHub does not actively police the contents of GitHub Pages to enforce any restriction to "documentation"; indeed many people use GitHub Pages for blogs related to general computing. --Eighty5cacao (talk) 00:57, 3 January 2016 (UTC)

FT to Pently[edit]

In this post, "all drums in Pently" appears to be an incomplete sentence. --Eighty5cacao (talk) 23:36, 4 January 2016 (UTC)

Interwiki: HTTPS for Sonic Retro[edit]

https://info.sonicretro.org/ --Eighty5cacao (talk) 23:54, 21 January 2016 (UTC)

Ok, perhaps I shouldn't have been so curt; I should have used this as a test case to develop a policy, as I will now explain. Don't revert your change for now.
By "policy," I mean that I need to write down some ideas on how much mixed content is acceptable, as well as how many of link rel="canonical", redirection, HSTS, and HTTPS-E rulesets need to be present (none apply to this case as far as I know).
Compromising by using a protocol-relative URL would be pointless in this case, as the site is using a paid CloudFlare service tier that doesn't require SNI.
As far as I know, any broken images you may have seen are a temporary problem that recently also affected segaretro.org, and they have nothing to do with the state of HTTPS support. --Eighty5cacao (talk) 04:37, 22 January 2016 (UTC)

Capitalizing my username[edit]

Regarding this NESdev post about Dot clock rates:

MediaWiki limitations notwithstanding, I normally prefer my username to be written in all lowercase. Don't bother editing that post though; I acknowledge that the capitalization was justified by English language rules. --Eighty5cacao (talk) 21:53, 30 January 2016 (UTC)

NESdev issues, February 2016[edit]

4961S[edit]

In this post, the link target for said TASVideos submission is correct, but the displayed text contains a typo.

Also, to answer the question you literally asked: I don't think so, because the SMW exploit depends on sub-frame input to allow execution out of the controller ports; no emulator supported this prior to the lsnes fork of bsnes.

P.S. See also Castlevania: Symphony of the Night, which is more analogous to the Pokémon exploits than Mario, in that it uses save corruption on an in-game inventory area. However, it's not so relevant to this discussion because no substantial payload has been constructed yet and your focus was clearly on Nintendo consoles. We should not expect to see a payload demonstrated before AGDQ 2018 at the earliest (perhaps "never"), as the focus for AGDQ 2017 is on chaining multiple consoles together. (Full category of exploits)

P.P.S. Do I understand correctly that you used submission numbers rather than movie numbers due to the distinction between published and rejected submissions paralleling that between accepted and rejected bug reports? --Eighty5cacao (talk) 02:29, 6 February 2016 (UTC)

Yes, that was my rationale for using S numbers. Thanks for pointing out the typo. --Tepples (talk) 04:34, 6 February 2016 (UTC)
Upon re-reading a bit more, the use of sub-frame input is not quite as essential (due to the WAI instruction) as the use of bits in the controller port that are not mapped to any physical button on the standard controller. Again, ZSNES does not support that. (Even that is not necessary if the only goal is to jump into the ending, but real-time speedrunning deviates significantly from this use case.) --Eighty5cacao (talk) 06:40, 18 February 2016 (UTC)

There has since been a human demonstration of a nontrivial SMW payload. However, what brings me here is another game: It was shown at SGDQ'16 that SMB3 can be exploited within a couple seconds by using rapidly-oscillating input to hang the DMC-tolerant controller routine long enough to force the NMI handler to reenter itself. There is no TASVideos submission because no existing NES emulator supports sub-frame input in its movie format. --Eighty5cacao (talk) 07:50, 10 July 2016 (UTC)

I'm giving up[edit]

This is what your current NESdev avatar appears to say. I couldn't find any explanation of it within NESdev or Pin Eight. Is this a temporary issue like your previous "Publicity Stunt Race FX," or is it something more serious (in which case I apologize for any perceived insensitivity and extend my sympathy)? --Eighty5cacao (talk) 02:39, 13 February 2016 (UTC)

Temporary stunt during Lent as I attempt to consolidate certain aspects of my online presence. I guess Ash Wednesday wasn't enough of a clue. Watch my microblog over the next few days to see what all I'm giving up, both on- and offline. --Tepples (talk) 04:52, 13 February 2016 (UTC)
I do read your Twitter account; sorry for not making the connection and instead showing a more general concern for your well-being. This reminds me of something I've been wanting to ask: Why do you often describe Twitter as if the audience would be unfamiliar with it, starting with the word "microblog"? Is it because of some offense Twitter has committed against the principles of free software and/or privacy? --Eighty5cacao (talk) 05:18, 13 February 2016 (UTC)
Thanks for the concern. I guess I'll have to start hinting more strongly because viewers aren't geniuses. If there's someone who needs help, it's Robert Pelloni.
As for use of "microblog": I'm trying to emphasize that I see my Tweets as a blog, just shorter, and it'd likely be of a similar nature even if I move it off Twitter to some host running Pump or GNU social. It's the same way that a full-length blog is a blog is a blog, whether it's on LiveJournal, Blogspot, WordPress.com, Tumblr, or your own domain. I'm also trying to use generic terms because I'm aware that trademarks are adjectives and to remind others subtly that other brands are available, as another country's public broadcaster often does. As for the free software advocacy angle, Twitter uses non-free JavaScript, and that's one reason the FSF uses tools other than Twitter's web interface for posting, but I'm not quite that fanatical about avoiding non-free JavaScript. Yet. Perhaps I might give up proprietary software for Lent some year, but not this year. --Tepples (talk) 13:50, 13 February 2016 (UTC)
Yeah, I was aware of the "trademarks are adjectives" angle (i.e. you would still have to say "my Twitter microblog" even if you mentioned Twitter by name), but sloppiness struck again.
If by Pump(.io) you meant specifically the instance on identi.ca, be aware that their HTTPS support is incomplete: Some(?) user avatars are on the domain avatar3.status.net, which used to support HTTPS but no longer does. It would probably be better to run said software on your own server if at all. --Eighty5cacao (talk) 18:03, 13 February 2016 (UTC)

PM?[edit]

I just got an email notification about a private message you allegedly sent me on the NESdev forums. The topic is "Re: Front Far East copier," and the message was addressed to my old username (which looks like my Uncyclopedia username), not my newer username (which looks like the one here).

As a reminder, I had stupidly registered a new account instead of properly requesting a username change. I no longer remember the password for either account, and I have no intention at present to resume activity. (I gave up editing Uncyclopedia a few years back too, but I digress. For either site, I will not reconsider my activity until HTTPS support is provided.)

I am aware that the NESdev forums have had problems sending email, so I assume this is a delayed notification of something that happened years ago. If it was in fact recent and not a glitch, I would appreciate you conveying the message to me by some other means. --Eighty5cacao (talk) 19:24, 21 February 2016 (UTC)

"no intention at present to resume activity" answers my question. --Tepples (talk) 00:32, 22 February 2016 (UTC)
But what do Front Far East copiers have to do with this? Perhaps this thread reminded you of some older post I made about the FFE mappers? Or did you just randomly choose an old PM to which to reply? --Eighty5cacao (talk) 00:45, 22 February 2016 (UTC)
I was indeed searching for old posts about FFE mappers to compose a reply to t=13863, and I found your Uncyc username. Anyway, though the forums mail issue has been fixed, wiki mail was broken last time I checked. And now that Let's Encrypt exists, I've requested HTTPS. --Tepples (talk) 00:57, 22 February 2016 (UTC)
I know it's been a bit inconvenient for you to pick through and relay my NES-related comments from here to NESdev. My post was an attempt to ascertain the meaning of "bad" mappers, which I misleadingly worded as a half-serious proposal for emulators to drop FFE support.
However, I again emphasize the word "(re)consider": Even with HTTPS, I may still not begin contributing immediately, in light of various real-life obligations and a lack of an actual NES development project. Anyway, thanks. --Eighty5cacao (talk) 03:53, 22 February 2016 (UTC)

As for Uncyclopedia, it now appears to have HTTPS. It doesn't yet enforce HTTPS on its own, but we haven't required such a standard for the configuration of interwiki links. I'm still a bit busy in my life, so I won't resume participating just yet. --Eighty5cacao (talk) 06:30, 26 June 2016 (UTC) (+ 07:59, 10 July 2016 (UTC))

Hatris in geod's emulator[edit]

"I'm not entirely sure anything will" appears to be an incomplete sentence. --Eighty5cacao (talk) 00:42, 22 February 2016 (UTC)

NESdev issues, April 2016[edit]

Interwiki configuration on NESdev[edit]

"change Wikipedia links to use interwiki syntax"

...reveals that the wikipedia interwiki prefix is still configured to be http. Is it practical to change this, given that NESdev doesn't seem to have Extension:Interwiki? --Eighty5cacao (talk) 04:38, 30 April 2016 (UTC)

Through /usr/bin/mysql, I ran this:
update mw1_interwiki
set iw_url = concat('https', substring(iw_url from 5))
where iw_url like 'http://%wikipedia%'
   or iw_url like 'http://%wiktionary%'
   or iw_url like 'http://%wikibooks%'
   or iw_url like 'http://%wikimedia%';
Then I edited that page (and another IW-heavy page) to update them to HTTPS. --Tepples (talk) 16:39, 30 April 2016 (UTC)

Incomplete sentences[edit]

"Did I handle this poorly by not ." --Eighty5cacao (talk) 05:55, 30 April 2016 (UTC)

Tvhack[edit]

Conventions that I am aware of on other wikis, especially Wikimedia Foundation projects, do not justify assuming so much good faith with what I consider an obvious spammer. I would have simply blanked the user page with an edit summary requesting deletion, but I hadn't gotten around to it. Can we agree that the user may be treated as a spammer if we receive no reply within a week from now? --Eighty5cacao (talk) 18:58, 22 May 2016 (UTC) (+ 00:55, 23 May 2016 (UTC))

At the time I welcomed the user, I thought it was my only hope to seek quality counterarguments to the disadvantages of Netflix VOD. But now that I think about it, if the user fails to voice an intent to provide a rebuttal but doesn't otherwise misbehave, "promotional username" might be the most gentle grounds for a block. --Tepples (talk) 14:44, 24 May 2016 (UTC)

NESdev issues, May 2016[edit]

ShaneM wonders whether extraterrestrial civilizations exist in the Milky Way[edit]

In this post, the link with said name appears to be a duplicate of the one below it.

I assume (but haven't verified) that I need to be logged in in order to search, so I haven't attempted to find the fix myself. --Eighty5cacao (talk) 05:25, 26 May 2016 (UTC)

Fixed. "Open Link in New Private Window" showed that search does not require login, though enumerating users does. --Tepples (talk) 12:29, 26 May 2016 (UTC)

Disagree(?) with "trimming conjecture"[edit]

Regarding this edit by Rainwarrior to CPU unofficial opcodes, which rendered the GitHub link fix moot, I agree that mentioning the PC Engine port is unnecessary clutter until such time as it is disassembled to determine whether it actually shares code.

I feel that if we mention anything whatsoever about "sharing code," we still need to emphasize that it is unknown what the "65C02 port" is and that the arcade version isn't it. We could remove the mention from the body text entirely and put it in a footnote instead, perhaps.

As for the parts not related to Puzznic, I disagree mainly with the removal of the sentence containing "as it became clear that the Super NES was not going to be backward compatible..." The rest seems okay though. --Eighty5cacao (talk) 23:09, 29 May 2016 (UTC)

I am aware of the talkpage post from Rainwarrior which suggests at least that a deliberate NOP-patching of the code is more likely than either a corrupt master or a direct port from any other system. Sorry for the bikeshedding. --Eighty5cacao (talk) 01:36, 31 May 2016 (UTC)

MediaWiki upgrade[edit]

I assume that the MediaWiki upgrade here and on NESdev is on hold due to objections raised on NESdev to the necessity of MobileFrontend and possibly personal reasons. Anything else that should be clarified? --Eighty5cacao (talk) 02:31, 13 June 2016 (UTC)

Mostly I ended up not getting around to it, with family recreation intervening. I still plan an upgrade sometime soon, MobileFrontend or not, to take advantage of security fixes. --Tepples (talk) 03:39, 13 June 2016 (UTC)

Since NesCartDB is back[edit]

...we should probably revert the interwiki change and instead provide an alternate prefix for the MimeoNES version. Just a friendly reminder --Eighty5cacao (talk) 07:21, 5 September 2016 (UTC)

Also, HTTPS for the nesdev prefix. --Eighty5cacao (talk) 01:07, 14 September 2016 (UTC)