User talk:Tepples

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

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)

ATT and explain xkcd[edit]

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))

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)

NESdev issues, Nov. 2016[edit]

Why does nesdev:Special:AbuseLog now apparently require login to view? This wasn't the case as of about 24 hours ago.

I understand that this may be intentional due to recent spam attacks, but I don't see any relevant or recent posts in the "nesdevWiki" subforum. It should be clearly documented on-wiki if so. (You don't need to go into detail about the reason; it suffices to make the link text read Failed changes (login required).)

Or is my IP address blocked or otherwise sanctioned? (Special:Log and Special:BlockList seem to suggest not, but I haven't specifically tested this by editing a talk page.) --Eighty5cacao (talk) 06:09, 10 November 2016 (UTC)

If there was a change to policy, I didn't make this change. Currently nesdev:Special:ListGroupRights does not reflect any policy change, as "View the abuse log (abusefilter-log)" and "View detailed abuse log entries (abusefilter-log-detail)" still appear to be granted to "(all)". Is this something I'll need to elevate to Memblers, who appears to have made all the recent anti-spam changes? --Tepples (talk) 15:17, 10 November 2016 (UTC)
After further review of the evidence: An IP address on the same /30 as what I get when I nslookup wiki.nesdev.com itself was blocked. This means MediaWiki appears to be seeing a reverse proxy's IP address, not the public IP address of the user who actually made the edit. I have unblocked this IP address and will raise this issue with Memblers once I have a chance to phrase it usefully. --Tepples (talk) 17:18, 10 November 2016 (UTC)
I can no longer reproduce the problem I originally reported. That is, the fix seems to have worked. It explains why I couldn't recognize any of the blocked IPs on a quick glance.
Sorry for not following up sooner. My Internet connection was experiencing temporary slowness at the time of the OP, and I pressed Stop soon after seeing "Permission error" as the page title. Ordinarily I would have made sure to copy the entire error message. --Eighty5cacao (talk) 04:15, 11 November 2016 (UTC)

NESdev issues, Jan. 2017[edit]

analytics.example.com?[edit]

An apparently broken link to a tracking script was revealed by the browser's view-source feature on nesdev:CHR ROM vs. CHR RAM (but this seems to affect all articles):

<script type="text/javascript" src="https://analytics.example.com/tracking.js"></script>

I assume this was part of some configuration template that we haven't edited adequately, and I assume we intended simply to remove it. --Eighty5cacao (talk) 22:23, 21 January 2017 (UTC)

I'm aware of the forum discussion stating that this is from a MediaWiki extension related to Google Analytics, but wiki.nesdev.com already seems to be embedding Google Analytics from its official Google-sanctioned URL, via a Google-official JS snippet. Whether it should be doing this (as opposed to using a self-hostable analytics script like Piwik, or none at all) is another story. --Eighty5cacao (talk) 02:09, 23 January 2017 (UTC)

NESdev issues, Apr. 2017[edit]

NesCartDB issue[edit]

I can't reproduce this either.

Assuming you are still experiencing a problem and you were not trying to play an April Fool's prank on the NESdev community:

"Access denied" implies either that bootgod has banned your IP or (less likely) that some part of your setup is caching DNS excessively, causing bootgod.dyndns.org to resolve to an unintended server. I've never seen the exact error message, though, so I can't offer more specific guidance. --Eighty5cacao (talk) 04:03, 3 April 2017 (UTC)

During the brief period that the error was still occurring, it was obviously a MySQL error message, not an error generated by the NesCartDB application itself. I forget some of the details, but I'm fairly certain that it was SELECT command denied to user '%s'@'localhost' for table '%s'. This doesn't reflect application-level security unless perhaps NesCartDB is implementing bans by mapping particular IP risk profiles to particular MySQL users. And if so, that's something I'd expect to see on The Daily WTF. --Tepples (talk) 18:16, 3 April 2017 (UTC)
As a reminder, I was not seriously suggesting that bootgod would engage in such outrageous coding practices. I was merely guessing because I had not seen the error message myself.
(Yes, I saw your post right after you made it. The problem was not with MediaWiki basics but rather that it took me several days to decide whether this clarification was worth making at all.) --Eighty5cacao (talk) 15:01, 17 April 2017 (UTC)

encyclopediadramatica.rs[edit]

...is now the correct domain where Encyclopedia Dramatica can be found. (See Archive Team article.)

However, I am in doubt whether we should maintain an interwiki prefix at all, given the generally adult nature of the site and the fact that Urban Dictionary and Know Your Meme often suffice to describe Internet-culture topics. --Eighty5cacao (talk) 19:58, 4 June 2017 (UTC)

Fun with acronyms[edit]

ProfessAdeath said of my Twitter and Discord handle: "Perfectly Integrated Navigation Of Brilliant Analytical Thought Creating Heroism" --Tepples (talk) 13:26, 19 June 2017 (UTC)

Broken HTTPS on Uncyclopedia[edit]

It appears that Uncyclopedia's TLS certificate expired sometime between a fortnight and a month ago (excuse the sloppiness; just recalling my memory of previous tests).

If I recall correctly based on previous incidents, they are using Let's Encrypt but have not set up any automation of the relevant scripts.

Since they don't enforce https, the obvious fix from our end is to change the uncyc interwiki prefix back to http. It would be better to treat this as a tech-evangelism issue, but I'm not sure which of several Twitter accounts they consider to be official, and the relevant subreddit has not been actively posted to for about a year. (My general disdain for online social networking should not need reiterating.)

If you want to make any changes to interwiki prefixes, I suggest thinking about removing dram at the same time. --Eighty5cacao (talk) 23:33, 24 August 2017 (UTC)

The issue appears to be resolved...for now. (Digression: I think this is just another spambot.) --Eighty5cacao (talk) 23:59, 18 September 2017 (UTC)

Interwiki table maintenance[edit]

Are you running some kind of script to validate the interwiki configuration? If so, it would be nice to post the code publicly, as long as the license is at least as Free as the rest of the wiki. --Eighty5cacao (talk) 00:47, 27 September 2017 (UTC)

It's not scripted. I'm just following a random IW link and seeing if it responds. (And now that you're aware of this project, I can RCC what I've done so far.) --Tepples (talk) 00:52, 27 September 2017 (UTC)
It doesn't look like you've RCC'd anything yet. Should I do so myself? I assume that RCC of interwiki maintenance should be subject to the same 24-hour delay as RCC of spam posts; does this make sense? --Eighty5cacao (talk) 04:03, 30 September 2017 (UTC)
I did RCC some from about a day before my last reply, those before your "headscratcher hooks" edits. But go ahead and apply the same rule. --Tepples (talk) 19:07, 30 September 2017 (UTC)