Difference between revisions of "User talk:Tepples"

From Pin Eight
Jump to: navigation, search
m (Typo in an old NESdev post - GBA speaker frequency response: brain dump commented out for now, as I can't be bothered to find a proper venue and post more neatly)
(Typo in an old NESdev post - GBA speaker frequency response: clarify what is actionable here)
Line 131: Line 131:
  
 
Look carefully at the unit in [https://forums.nesdev.com/viewtopic.php?p=137425#p137425 this post]; did you mean 800 Hz? --[[User:Eighty5cacao|Eighty5cacao]] ([[User talk:Eighty5cacao|talk]]) 20:48, 24 August 2019 (UTC)
 
Look carefully at the unit in [https://forums.nesdev.com/viewtopic.php?p=137425#p137425 this post]; did you mean 800 Hz? --[[User:Eighty5cacao|Eighty5cacao]] ([[User talk:Eighty5cacao|talk]]) 20:48, 24 August 2019 (UTC)
<!-- TODO: I came across this post in the course of a brute-force manual "search" in response to the deletion of a GitHub repository that contained an encoder implementation of a "D+PCM" idea: one byte of raw PCM alternating with one byte of delta samples. The TODO is to find any fundamental flaws in this idea, and I don't just mean the fact that a decoder would need to write $4011 twice in a row. I didn't manage to find a relevant thread either -->
+
<!-- If you are wondering, I came across this post in the course of a brute-force manual "search" in response to the deletion of a GitHub repository that contained an encoder implementation of a "D+PCM" idea: one byte of raw PCM alternating with one byte of delta samples. The TODO is to find any fundamental flaws in this idea, and I don't just mean the fact that a decoder would need to write $4011 twice in a row. I didn't manage to find a relevant thread either -->
 +
:I understand if the post cannot be edited due to age; I do not need a reply if that is your only objection. --[[User:Eighty5cacao|Eighty5cacao]] ([[User talk:Eighty5cacao|talk]]) 04:06, 27 August 2019 (UTC)

Revision as of 04:06, 27 August 2019

For older discussions, see archives: 1 2 3 4 5 6 7 8 9.

Interwiki table maintenance

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)

index.php?diff= gives internal error on user scripts and stylesheets

For example, Special:Diff/15702 (which redirects to https://pineight.com/mw/index.php?diff=15702, an edit to User:Eighty5cacao/common.js) and Special:Diff/15139 (which redirects to https://pineight.com/mw/index.php?diff=15139, an edit to User:Eighty5cacao/common.css) show:

MediaWiki internal error.

Exception caught inside exception handler.

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

The longer URLs for the same edits, https://pineight.com/mw/index.php?title=User:Eighty5cacao/common.js&diff=prev&oldid=15702 and https://pineight.com/mw/index.php?title=User:Eighty5cacao/common.css&diff=15139&oldid=15111, work fine.

Special:Diff/15754, an edit to App Store Review Guidelines, works fine. --Eighty5cacao (talk) 00:52, 5 January 2018 (UTC)

Can you get it to happen for any pages that aren't user CSS or user JS? If not, it's probably the same problem as User talk:Tepples/Archive 7#Extensions causing problems with user script and stylesheet pages?. When I get a chance to use the computer on which LocalSettings.php is maintained, I'll try to find time to disable TwitterCards on all diff pages. --Tepples (talk) 18:17, 5 January 2018 (UTC)
The answer as of now to the question in your first sentence is no. --Eighty5cacao (talk) 01:11, 6 January 2018 (UTC)

I have just confirmed that this is still an issue. What are your plans as of now? --Eighty5cacao (talk) 22:32, 15 August 2018 (UTC)

I have excluded TwitterCards from pageviews containing a nonempty diff query parameter. But for anything more substantial, I'll first need to dig up which computer has my hosting provider credentials so I can upgrade PHP from 5.6 to 7.x and then upgrade MediaWiki to latest stable. --Tepples (talk) 02:09, 17 August 2018 (UTC)

Archive Team now supports HTTPS

For example, https://archiveteam.org/index.php?title=Main_Page for archiveteam:Main Page --Eighty5cacao (talk) 04:26, 5 January 2018 (UTC)

NESdev issues, March 2018

RPG assets by Chasersgaming

The link from this thread that you posted here needs to be fixed to point to https://chasersgaming.itch.io/tile-set-pack-7-nes (determined by carefully examining Chasersgaming's full list of projects for those that specifically mention NES).

The original link currently returns 404 with what looks like a standard itch.io error page; please let me know if I need to describe the symptom in more detail. --Eighty5cacao (talk) 05:31, 2 March 2018 (UTC)

Both the old link and the new link work for me at the moment. Thank you for suggesting an addition to nesdev:Placeholder graphics. --Tepples (talk) 15:06, 4 March 2018 (UTC)
I can confirm that the old link now works for me as well. Sorry to bother you for what could have been a temporary problem. --Eighty5cacao (talk) 23:02, 4 March 2018 (UTC)

The end of Recent Changes Cleanup

I seek to upgrade to MediaWiki 1.30 until such time as I can switch my hosting to PHP 7. But mediawikiwiki:Extension:Recent Changes Cleanup states that the extension is no longer maintained, and the archived version states that the extension no longer works with any supported version of MediaWiki. This means RCC will cease to be available on this wiki sometime between now and the end of August. --Tepples (talk) 02:55, 18 August 2018 (UTC)

Make that now. Welcome to MediaWiki 1.30. --Tepples (talk) 03:40, 18 August 2018 (UTC)
I apologize for the rude edit summaries and for not reading this sooner. I had been away from my computer for a little over a day and only found out the upgrade had been performed for other reasons.
How does this affect the project-scope policy concerns that led to the original use of RCC? I guess that edits to user scripts and stylesheets never really needed to be hidden in the first place, but the more pressing concerns are spam, cleanup of spam, and my WMG materials.
I was planning to register on All The Tropes in the near future anyway; I am willing to move my WMG content there, but I cannot promise any particular timescale, especially because my activity is likely to be erratic for a month or more due to real life.
The quick but heavy-handed fix would be to flag my account as a bot until such time as either I complete any migration of content or we find an alternative MediaWiki extension of similar utility.
Alternatives that would avoid hiding any future mainspace edits I make include:
  1. Configure RecentChanges not to show edits to the user namespaces (is this still possible?)
  2. Redefine the guidelines for the minor-edit flag to include everything we were previously RCCing, then configure RecentChanges not to show minor edits by default
--Eighty5cacao (talk) 06:24, 20 August 2018 (UTC) to 06:48, 20 August 2018 (UTC)
Project scope issues were mostly in play when this wiki was averaging a dozen or more edits a day. Now that it's slowed down a bit, they're not quite so pressing. --Tepples (talk) 13:16, 20 August 2018 (UTC)
I still plan to do my share of #2: Unless I am requesting deletion or other administrator assistance, I will mark all edits to non-preferred userspace topics as minor, whether or not they would be minor under our prevailing guidelines.
I agree that no change to the wiki's default configuration is needed, however. --Eighty5cacao (talk) 17:14, 20 August 2018 (UTC)

Reevaluating definition of NES 2.0 mapper plane 2

Again, sorry for not registering directly on NESdev; I will do that ASAP (read: in a few days) and let you know.

It has apparently been decided that the original Unicode-inspired names are so thoroughly unwarranted that they should not be mentioned in nesdev:Mapper even as hidden anchors.

It is not clear to me that the criterion "released only in the East Asian market" is being interpreted literally or researched thoroughly for every game, based on a look through the existing mapper assignments.

The original motivation for following the Unicode definition was the technical requirements for displaying ideographic characters on the NES (e.g. CHR RAM), but it's not clear that this correlates strongly with hardware usage in existing games.

In light of the above, it is possible that the current definition of plane 2 discriminates geographically in a way that provides no benefit, and perhaps we should impose a moratorium on new assignments in plane 2 until plane 1 fills up. Comments?

Digression: Should mapper 310 be marked as bad until it is reassigned? Should 380 be marked in some way until a public ROM exists? --Eighty5cacao (talk) 16:51, 3 September 2018 (UTC)

Mapper 380 is a worthless redirect, and should probably be deleted. If you think it should be marked, make it a "weak reservation": anyone other than zzo38 is discouraged from using that number unless the rest of the plane is full, but it is not mandatory to avoid it (although it may be decided that "weak reservations" are not helpful, in which case just delete it). (Other "weak reserverations" may also be possible.) Mapper 310 looks worthless too (it is also a redirect), and can probably be called a "bad" mapper until it is reassigned. --24.207.47.161 05:25, 4 September 2018 (UTC)
You may take this to be my deletion request for the "INES Mapper 380" redirect (not 310), but please consider userfying any useful history to Zzo38 if this hasn't already been done.
Everything else, I will repost on NESdev myself when I register within a day or so. One more clarification I now see: "interpreted literally or researched thoroughly" is not meant to be a dichotomy; it means "It is not clear...that the criterion...is being interpreted as literally as possible in every case nor that every regional release of every game has been researched thoroughly." --Eighty5cacao (talk) 21:24, 4 September 2018 (UTC)
Given the lack of uptake of SMP/SIP distinction in existing assignments, I've edited it out of the page. As for zzo38's proposals, might something like nesdev:File:Mfr icon reserved.png be useful for cases like this? --Tepples (talk) 22:20, 4 September 2018 (UTC)
No objection. (To clarify further: 310 is "bad" because it was genuinely assigned in error, while 380 is the only candidate for the new "reserved" status) --Eighty5cacao (talk) 16:35, 5 September 2018 (UTC)

Wikia's redirection script no longer works

I noticed this when I found that an editor on nesdev:CPU unofficial opcodes attempted to use nesdev:Template:Dead link, which does not exist yet.

The behavior appears to be that the www.wikia.com/wiki/c:wikiname:pagename URLs no longer redirect, instead showing what is presumably the same error page the MediaWiki software generates for direct links to any nonexistent page (I stupidly panicked and hit stop before it finished loading).

Assuming this isn't a temporary problem, I see two solution approaches (for both Pin Eight and NESdev):

  1. Remove the wikia: interwiki prefix before any cleanup effort, so that Special:WantedPages can be used to find the offending links. This may be undesirable for readers.
  2. Create a self-hosted PHP script that performs the desired redirection, similar to trope.php but preferably with no interstitial page. Reconfigure the wikia: prefix to point there.

Be aware that Pin Eight's wikia: prefix is configured to include the c:, while NESdev's is not and therefore requires editors to include c: in the link manually.

In the meantime, I will change any links here on Pin Eight to use external-link format to point directly to the desired target. The specific link on NESdev should probably be changed to point to a category (http://bootleggames.wikia.com/wiki/Category:Aladdin_games) rather than a special page. --Eighty5cacao (talk) 03:07, 29 October 2018 (UTC)

To clarify: No, I haven't registered on NESdev (or All The Tropes) yet; I got busy with real life, again. I do acknowledge that I should perhaps have raised this issue on the talk page of the NESdev article. --Eighty5cacao (talk) 15:26, 5 November 2018 (UTC)
Do wikia:bootleggames:Category:Aladdin games and wikia:c:bootleggames:Category:Aladdin games go where you expect? (Neither of them has anything to do with a Deck Enhancer though.) --Tepples (talk) 03:17, 9 November 2018 (UTC)
They appear to work; it appears that some character encoding is not fully undone (specifically, I get redirected to http://bootleggames.wikia.com/wiki/Category%3AAladdin_games), but Wikia's servers/MediaWiki installation accept that to refer to the same page, if it is even technically considered a different URL. --Eighty5cacao (talk) 05:35, 9 November 2018 (UTC)

fandom.com

The reason for this deprecation was apparently that (ahem) FANDOM powered by Wikia is moving its preferred second-level domain from wikia.com to fandom.com.

There is cool-URI redirection in place, and the new domains allow HTTPS without a requirement for login.

This migration appears to have been completed for at least the few wikis we are linking from here, though the official documentation page at wikia:community:Help:Fandom domain migration states that it will not be completed until February 4, so I recommend against taking any action on interwiki configuration until then.

As mentioned there, Wikia also owns wikia.org for more educational uses, though no wikis exist under wikia.org yet, and any migration or creation requires review by Wikia staff.

P.S. No one has yet addressed the original NESdev issue that prompted this discussion. --Eighty5cacao (talk) 20:36, 26 January 2019 (UTC)

To clarify, the main action is not on "interwiki configuration" per se; it should suffice to modify wikia.php to redirect accordingly. It's up to you whether to create fandom: as an alternative alias for wikia.php. --Eighty5cacao (talk) 02:06, 31 January 2019 (UTC)

My original investigation was not thorough enough; for example, timemachine.wikia.com has not been migrated, and the warning banner it displays contains the verbiage "Over the next few weeks." --Eighty5cacao (talk) 03:29, 5 February 2019 (UTC)

10.2.2.

As I foolishly raised in a deep corner of my userspace here, what can you publicly disclose about the inspirations for "10.2.2."? Can you at least point me in the direction of the most informative NESdev thread, if it isn't the one I found? --Eighty5cacao (talk) 03:10, 26 February 2019 (UTC)

My writing a piece in the "piano ambient" genre was indeed inspired by "5.1.1." from IIDX. Doubling all numbers was because I originally intended it to accompany a StepMania etude simfile that teaches the more varied gallop patterns in dance-double (8 panels). It got put on hold by various things, such as dance pads wearing out and the overall decline of the StepMania community in the late 2000s decade. I'm not sure what role Konami v. Roxor played in the latter. --Tepples (talk) 13:51, 26 February 2019 (UTC)
I was hoping you would name some additional song other than "5.1.1.," but I'll drop it for now.
As for the sloppy, backhanded, belated (!) report of the {{spoiler box}} problem, I apologize for not actually debugging the issue myself; I still make no promises. --Eighty5cacao (talk) 15:55, 26 February 2019 (UTC)

Closure of YTMND

Do you have any plans to rehost the assets of your YTMND pages within Pin Eight? (If you don't have backups, I'm sorry I can't help you.) --Eighty5cacao (talk) 01:33, 3 July 2019 (UTC)

My YTMND use was three computers ago. I probably have backups on an external USB HDD, though I haven't tested them in years. Archive Team reportedly has backups as well per archiveteam:YTMND. But YTMND subdomains appear to be back up, such as my "Tetris is ridin' spinnaz" <http://infinitespin.ytmnd.com/>, "PP2P2P2PP2P" <http://p2p.ytmnd.com/>, "YTMND is cheaper" <http://cheap.ytmnd.com/>, and "Lil Movers Fire Truck" <http://lpfireman.ytmnd.com/>, even though search, comments, and detailed sourcing are unavailable. --Tepples (talk) 15:49, 6 July 2019 (UTC)
I apologize for the sloppiness yet again. Perhaps I jumped to conclusions because the last time I checked archiveteam:YTMND, it stated that the Archive Team had not yet (successfully) received the backups.
However, I am also concerned about lack of HTTPS support, in particular the fact that YTMND is likely never to support HTTPS in its present state. The best solution to this would probably be for YTMND to start allowing Wayback Machine access. (TODO for me to look up: Did Let's Encrypt ever implement wildcard support? What is their policy on that?) --Eighty5cacao (talk) 18:51, 6 July 2019 (UTC)
Good news: LE's ACME v2 endpoint has been issuing certificates with wildcard SAN since March 2018 (source). --Tepples (talk) 02:08, 10 July 2019 (UTC)
Note to self: Admitting to sloppiness doesn't fully excuse it. (What did you think I meant by "TODO for me to look up"?) Yes, I knew that Let's Encrypt had been in discussion about wildcards for a while; the question is the detailed policies. Also, even if I had a good way to communicate this to YTMND's administrators, they might be unwilling to act. --Eighty5cacao (talk) 04:59, 10 July 2019 (UTC)

Harry Potter WMGs on All The Tropes

This is months-old news, but your WMG about the PlayStation Super Disc existing in the Harry Potter universe seems to have gotten lost in some reorganization of All The Tropes's Harry Potter WMG subpages. You may wish to ask someone whether it was removed intentionally. (I admit that my investigation was itself months old and based primarily on manual link clicking rather than the search box. Sorry if I missed something.) --Eighty5cacao (talk) 01:33, 3 July 2019 (UTC)

Typo in an old NESdev post - GBA speaker frequency response

Look carefully at the unit in this post; did you mean 800 Hz? --Eighty5cacao (talk) 20:48, 24 August 2019 (UTC)

I understand if the post cannot be edited due to age; I do not need a reply if that is your only objection. --Eighty5cacao (talk) 04:06, 27 August 2019 (UTC)