User talk:Tepples/Archive 6

From Pin Eight
Jump to: navigation, search
This page is an archive of old discussions from 2014. Do not modify this page. If you have anything to add to the discussion, start a new section on User talk:Tepples.

HTTPS on this site: further follow-up[edit]

Just a friendly reminder: I happened to notice that the certificate will expire within about a day.

This gives me the opportunity to bring up something else: What exactly is the technical problem that precludes issuing a separate certificate for pics.pineight.com? Does WebFaction only allow one cert per customer? Does StartCom require email addresses to be unique between Class 1 certificates? Or both?

Alternatively, what about moving pics to Amazon S3, which would at least allow some HTTPS Everywhere rule to be written for it? Of course, this isn't worth doing unless removing the domain's contents from WebFaction would reduce the WebFaction costs. Does WebFaction charge per domain, or is there some number of domains included with the standard account package? How does it matter whether a domain has content actually hosted on WebFaction or is just a CNAME pointing elsewhere? This wasn't entirely clear from their website. --Eighty5cacao (talk) 00:59, 6 December 2013 (UTC)

I'm nowhere near the domain and bandwidth caps set by WebFaction, and it appears each site can have its own certificate installed. It appears to be a limitation of free StartCom accounts. From the StartSSL.com Certificates Wizard: "Note: In order to add multiple domains and sub domains, your Identity must be at least Class 2 validated. Check your status at the 'Identity Card'." In any case, I've submitted the ticket to get the new cert installed. If you're worried about HTTPS Everywhere, currently pics.pineight.com is an alias for pineight.com/pics. --Tepples (talk) 04:43, 6 December 2013 (UTC)
So if I understand you correctly, <rule from="^http://pics\.pineight\.com/" to="https://pineight.com/pics/" /> should work? Should I go ahead and add this to the working copy of the ruleset, and if so, do you need to email the developers again? --Eighty5cacao (talk) 21:12, 7 December 2013 (UTC)
It should work until this technical detail of the hosting, namely the fact that pics.pineight.com is an alias for /pics, changes. I hadn't planned on permanently committing myself to a stable HTTPS URI just yet. Is there a way for a ruleset to mark rewritten URLs as not persistent, like the difference between an HTTP 301 "Moved" and a 302 "Found"/303 "See Other"? --Tepples (talk) 22:43, 7 December 2013 (UTC)
Not that I am aware. The best alternative is probably to put it in the corresponding default-off ruleset, then. --Eighty5cacao (talk) 22:56, 7 December 2013 (UTC)
Done. And to answer your question more thoroughly: Issues of the "this might break in the future" category are typically documented in <!-- comments --> within the ruleset. It might also be good (for the benefit of end users, not necessarily developers) for you to announce something on this site a few days before such breakage occurs. --Eighty5cacao (talk) 23:11, 7 December 2013 (UTC)
I added .7z coverage after noticing you used that compression format for Holy Diver Batman, and I subsequently decided to generalize further to include all possible file extensions. (For what it's worth, don't bother reminding the developers about my other rulesets the next time you email them.) --Eighty5cacao (talk) 01:41, 23 December 2013 (UTC)

Version 4.0development.15 of HTTPS Everywhere was released earlier today. Some relevant points:

  1. No ruleset for Pin Eight has been added yet.
  2. Support for user rulesets was mistakenly removed as part of a change that puts the built-in rulesets in an SQLite container. (Due to this, I reverted the update on my system.)
  3. This email confirms the existence of a ruleset freeze.

There's an existing ticket concerning HTTPS support for YouTube streams, but that's a topic for elsewhere. --Eighty5cacao (talk) 01:04, 7 February 2014 (UTC) (+ 04:22, 7 February 2014 (UTC))

Nibbles: follow-up[edit]

(Original discussion in archive 4)

Just a random note: I found the video of the famiclone device that includes Nibbles. (I was almost right about the number of games - it's a OneStation 99-in-1 device - and I was right about the uploader of the video. I just hadn't searched thoroughly enough back then.) No need to reply. --Eighty5cacao (talk) 07:32, 8 December 2013 (UTC)

Apparently some version of the Senario 101-in-1 device does also include Nibbles. --Eighty5cacao (talk) 05:20, 11 May 2014 (UTC)
There's my game, and there's Tengen Tetris. My Senario must be a later revision (© 2006) that doesn't have nearly as much pirated crap in it, apart from two Tetris clones. --Tepples (talk) 06:08, 11 May 2014 (UTC)

Another NESdev typo[edit]

In this post, there appears to be a sentence left incomplete between "allows" and "But." --Eighty5cacao (talk) 03:06, 16 January 2014 (UTC)

Privacy policy[edit]

The default link to Pin Eight:Privacy policy in the footer of each page is broken because we never bothered to write a privacy policy specifically for the wiki. It could just be a soft redirect to the terms of use (which contain a privacy policy) for Pin Eight as a whole, but I'd also like to mention something about best practices for handling violations, especially those made unintentionally in good faith. --Eighty5cacao (talk) 01:37, 29 January 2014 (UTC) (+ 04:16, 29 January 2014 (UTC))

Remove ohinternet:[edit]

As explained on ED, Oh Internet has been down for several months and is likely gone for good. We should remove the interwiki prefix so that any such links will appear red and will show up in Special:WantedPages, making it more obvious when fixes are needed. Any objections? --Eighty5cacao (talk) 03:10, 1 February 2014 (UTC)

It'd be easier if there were usage reports for IWs; I'll have to make my own from my backups. I've orphaned ohinternet:. If you could find any other dead IWs in the list, I'd appreciate it. --Tepples (talk) 16:02, 1 February 2014 (UTC)

Spam cleanup policy question[edit]

Is it okay for me to use Special:RecentChangesCleanup to hide spam edits after you have responded to them? (The key word is "after," and this obviously applies only to non-deleted edits.) --Eighty5cacao (talk) 07:37, 4 March 2014 (UTC)

I've already been RCC-hiding spam and reverts 24 hours after cleanup, so yes. --Tepples (talk) 14:26, 4 March 2014 (UTC)

Cookie Clicker project page[edit]

Miscellaneous comments and questions about [1]:

  1. Please make the reference to the stylesheet //fonts.googleapis.com/css?family=Kavoon protocol-relative, or else it will hit mixed-content blockers. This also applies to the differences.html subpage.
    (fonts.googleapis.com has officially supported HTTPS for a while, but a lot of other webmasters have made the same mistake. If it is not working for you, please explain.)
  2. What does "genetic modification controversy strikes cacao farmers" have to do with my username?
    (I do not own a NES or related hardware, and I've got too much going on in my life to be of much help testing anyway.)
  3. Why isn't anything mentioned on this wiki? Should we at least make a soft redirect from [[Cookie Clicker (NES)]] Cookie Clicker to that page?

--Eighty5cacao (talk) 22:09, 6 April 2014 (UTC)

  1. Will be pushed out as of next update.
  2. Absolutely nothing. The original quote from main.js was "News : genetically-modified chocolate controversy strikes cookie farmers!" but see the differences page under "Cosmetic" and DashNet Forums for why I changed some of the headlines.
  3. Haven't had time yet.
--Tepples (talk) 23:03, 6 April 2014 (UTC)
Ok, thanks. In response to #2, sorry for not playing the original. (This is one of maybe two things I was hinting at in the last sentence of that item.) --Eighty5cacao (talk) 00:16, 7 April 2014 (UTC)
As of now, the "Milca, the player character" box (directly below "[Mock] Upgrades with golden cookie notice") seems to be missing an image. Specifically, https://pineight.com/cookieclicker/milca_x2.png is returning 404; presumably it is meant to be one of the images that shows front, profile, and back views. --Eighty5cacao (talk) 01:13, 18 April 2014 (UTC)
Oops, broken duplicate, my bad. The figure will be removed next update, as I decided to put Milca's portrait higher on the page in the Story section. --Tepples (talk) 02:42, 18 April 2014 (UTC)

Dedupe[edit]

The protocol is mistyped in the Cracked link for Dedupe. --Eighty5cacao (talk) 17:08, 12 June 2014 (UTC)

Fixed. At the same time, I added the keywords from the Photoplasty entry to the description and made GNU and Python links protocol-relative. Let me know if anything else needs to be clarified. --Tepples (talk) 19:40, 12 June 2014 (UTC)

Maxx Wishful BG[edit]

As far as I have found, no version of StepMania from 3.9 onward successfully displays the initial background (winbg.png) in said simfile, because you placed it in the stills folder but didn't specifically tell StepMania to look there. I haven't checked whether StepMania supports a subfolder declaration in the background tag like #BACKGROUND:stills/winbg.png;.

As winbg.png is not referenced in the BGCHANGES, it could be moved to the simfile's root folder to solve this problem. However, as I know you're no longer maintaining those simfiles, would it suffice to add explanatory text to the /dwi/ page? --Eighty5cacao (talk) 06:17, 28 June 2014 (UTC) (+ 02:26, 29 June 2014 (UTC))

I've added a warning. Is it enough? --Tepples (talk) 02:32, 30 June 2014 (UTC)
I don't have StepMania 3.0 handy with which to verify whether anything actually changed. Only "Maxx Wishful" in particular was ever problematic for me (what prevents you from singling it out?)
The text itself looks fine, but it might be good to add a link to this discussion (either use an oldid or wait until you archive this). --Eighty5cacao (talk) 03:06, 30 June 2014 (UTC)
I'd need to install StepMania on one of my current PCs in order to evaluate how important the loss of winbg.png is to the overall effect of those background changes that are in place. --Tepples (talk) 11:41, 30 June 2014 (UTC)
I don't have Dance With Intensity either, nor do I know how well it runs on modern PCs, nor do I really care how it's behavior differs from SM's. Thus this is not about the .dwi file, only .sm.
As far as I know, only a text editor or command shell is needed to verify that "winbg.png is not referenced in the BGCHANGES." Or were you referring to some subjective opinion? --Eighty5cacao (talk) 17:27, 30 June 2014 (UTC) (+ 19:31, 30 June 2014 (UTC))
Yes, I was referring to subjective opinion, namely whether the (known) failure to display winbg.png had any negative effect on gameplay. I think the only reason I added it in the first place is because SM 3.0, which was current when I created the simfile, would add an implicit background change to the song's background image after the last note in a song.
But what prevents me from singling out "Maxx Wishful" is that if your finding a problem with "Maxx Wishful" causes me to post a specific notice about this issue, others who find problems with other simfiles (such as not already having the codecs needed for "Balloon Fever" and "fr018") might feel entitled to specific notices about their own pet issues. Such reports might end up being a comprehensive validation of each one of these old simfiles, something I hadn't planned on doing after having been out of the StepMania scene for years. So instead, I added a generic notice. --Tepples (talk) 19:53, 30 June 2014 (UTC)

To my knowledge, the "implicit background change" is still current behavior, and there is a magic word -nosongbg- to work around it (at least the SM3.9 editor adds it automatically in some circumstances).

StepMania removed the dependence on Windows-supplied codecs by providing its own DLLs beginning around 3.9; similarly, ffmpeg was statically linked in the Linux build process some time in the sm-ssc/5.0 Preview era. How does that affect your response? And how would permalinking to this discussion from /dwi/ be any more "validation" than singling out a particular simfile without a hyperlink? --Eighty5cacao (talk) 22:18, 30 June 2014 (UTC)

I was just trying to help by providing others with instructions for fixing the problem. If you don't want people to see the full discussion, you can link to a revision with just my original post; another benefit of a permalink is that any questions/complaints posted by other users will not be visible. You can just write "(more info)"; you don't have to make the text any more specific. --Eighty5cacao (talk) 23:05, 30 June 2014 (UTC)

Now I understand. This should fix it. --Tepples (talk) 00:02, 1 July 2014 (UTC)
Ok, looks good now. (I've added some information to the "Info on specific StepMania versions" box above; nothing's meant to be actionable, meaning you don't need to worry about doing anything further.) --Eighty5cacao (talk) 04:37, 1 July 2014 (UTC)

Privacy Badger false positive for TCRF content on NESdev[edit]

was: TCRF blocks image hotlinking

Seen on this NESdev post --Eighty5cacao (talk) 23:13, 12 July 2014 (UTC)

I don't see the misbehavior. I press Ctrl+Shift+R to bypass the cache, and the pic still loads. --Tepples (talk) 03:13, 13 July 2014 (UTC)
It was a Privacy Badger false positive, related to session cookies used by the MediaWiki software (same as I mentioned in this diff). Sorry for not checking that first. --Eighty5cacao (talk) 04:32, 13 July 2014 (UTC)

s vs. del[edit]

I seem to remember from some previous discussion that <del> semantically signifies "deletion" of some text, while <s> is just formatting, and so you prefer the former. (My own use of the latter is typically laziness.) Did something change? Did I misunderstand?

Sorry I'm too lazy to actually find the previous discussion nor to do any other research. --Eighty5cacao (talk) 18:13, 15 July 2014 (UTC)

HTML5 retconned the meaning of most of the old presentation elements that HTML 4 and XHTML 1 had deprecated. For example, the <s> element now means "contents that are no longer accurate or no longer relevant". The <del> element is more specifically for "text that has been deleted from a document" as the opposite of the <ins> element, and I think these two are more for diffs and the like. --Tepples (talk) 18:34, 15 July 2014 (UTC)
Yeah, I remember (now) that you described this issue as a "retcon" once before. I hope I haven't inconvenienced you too much. I will really make an effort to remember this next time. --Eighty5cacao (talk) 18:43, 15 July 2014 (UTC)

Wording on allthetropes:The Time Machine#The Book[edit]

In the "Attention Deficit Ooh Shiny" entry, the wording "All of them" should probably be removed.

You previously removed the same wording from TV Tropes, as discussed at User talk:Tepples/Archive 5#Wording on tvtropes:Literature/TheTimeMachine. Your TV Tropes edit summary was similar to, "A forum discussion (suggests|proposes|hypothesizes) that Weena may be less affected than others." --Eighty5cacao (talk) 07:31, 3 August 2014 (UTC)

Link capitalization in edit summary[edit]

This edit summary contains a red link due to incorrect capitalization; it appears that User:Tepples/Why consoles was intended. Should I create a redirect, or should I just note the issue via a dummy edit? --Eighty5cacao (talk) 06:41, 9 September 2014 (UTC)

Revert Encyclopedia Dramatica interwiki change[edit]

ED has moved back to the .se domain.

The .es domain resolves to some server, possibly a redirector, but all I tested is that that server lacks working HTTPS. (.se does have valid HTTPS.) --Eighty5cacao (talk) 19:14, 14 November 2014 (UTC)

Comments in my userspace[edit]

This is admittedly another (normally discouraged) knee-jerk WP:OWNership reaction to this.

As far as you should be concerned, there is no such thing as a needy edit by me to my own userspace. In particular, comments are the ultimate expression of sloppiness, but that doesn't mean I make them without consideration; I'm generally aware when I'm being more verbose than possible, and there's usually a reason for it.

I would prefer that you edit my comments only to correct blatant factual errors, in which case you should bring it up on talk as well.

I'm not saying to avoid editing my userspace at all; just try to leave a slightly longer cooling-off period for me to catch my sloppiness, and feel free to tweak anything that isn't commented out.

You succeeded in reminding me that this particular comment was unnecessary to begin with. However, I ended up replacing it with something even more verbose (basically commented-out wikitext); I hope you don't mind. No one's supposed to be scraping the wikitext of that page, as I mentioned in the lede.

At any rate, I'll try to avoid abusing comments for transient communication that would be better served by an edit summary or talk page. --Eighty5cacao (talk) 02:14, 18 November 2014 (UTC)

Twitter[edit]

nesdev:Action 53 manual#Credits: "@PinoBatch on Twitter"

What makes you think that the utility/privacy tradeoff of Twitter is acceptable? (I do agree that it's better than Facebook.)

You previously said about Google+ that Google already had your PII for AdSense, but I don't see how a similar circumstance applies to Twitter.

Is there anything important on that Twitter account that you aren't also posting on the Pin Eight homepage? Or did you protect the account? (I haven't bothered to check. I'm not on Twitter myself, and I would consider joining only if they added a "semi-protection" option that required login to view my tweets but allowed logged-in users to do anything that they could with a public account - never mind that I don't have enough to tweet about in the first place.)

(P.S. Reminder to renew SSL certificate) --Eighty5cacao (talk) 20:47, 2 December 2014 (UTC)

I see Twitter as more of a blogging platform than a social network. It's good enough for FSF (in its case as a mirror of its GNU social feed), unlike the Facebook. Twitter doesn't goad users into giving up an SMS number just to stay logged in, unlike Facebook that eventually puts up a "roadblock" for some accounts. (At least Facebook doesn't put its roadblock on the signup page like Yahoo does.) Also unlike Facebook, Twitter explicitly allows multiple accounts per person with distinct uses. There seem to be fewer switching costs than with Facebook, as I can download a list of all my tweets should I decide to jump ship for Pump or something. Besides, I realized I could no longer get any laughs out of the name coincidence with a known abuser of multiple Slashdot accounts, who didn't get my joke even when he was around. (It was "I'm not twitter; I don't even have an account there." Mostly I use @PinoBatch for posting things too small for a full-size blog post, and for things not quite as closely related to my software projects or philosophical essays. And I don't see any point for making tweets "free reg. req." the way NYTimes.com used to be before it adopted its current soft paywall; all that does is spawn Bugmenot-style workarounds. --Tepples (talk) 01:50, 3 December 2014 (UTC)
And it's good enough for EFF too... But on the point of "semi-protection," I admit my logic was a bit off. I was just trying to convey my awareness of basic privacy hygiene, but the unqualified word "only" was a bit too strong. I'm aware that an existing form of "semi-protection" is the option to flag media as sensitive by default, but I found that unsatisfying because even if I could produce enough text to make Twitter worth using, I might not share enough pictures for that option to have a meaningful impact.
I'm sure Twitter has been smart enough to block most Bugmenot-type services, but as with so many other things, I haven't personally verified that. I did not mean for Twitter to consider search-engine bots as logged-in users. --Eighty5cacao (talk) 06:56, 3 December 2014 (UTC)

Digression: Cert renewal process[edit]

Does StartCom send reminder emails about impending expiration, or is that feature not for free accounts?

Do I need to bother posting a reminder a year from now, or for future years in general? --Eighty5cacao (talk) 01:12, 5 December 2014 (UTC)

I'm not sure. Anyway, the CSR is (re-)submitted to StartSSL. It may take a few hours minutes for it to be issued, and then I'll need to send the certificate to WebFaction. And now I've submitted the new cert. --Tepples (talk) 02:06, 5 December 2014 (UTC) (update 03:18, 5 December 2014 (UTC))
I can confirm that the new cert is in place. Again, sorry for any annoyance caused. --Eighty5cacao (talk) 19:40, 5 December 2014 (UTC)
To which of my two questions was "I'm not sure" a response? --Eighty5cacao (talk) 05:20, 6 December 2014 (UTC)
Both. I haven't thought too much about the processes regarding keeping the hosting going. Just be glad I don't have to manage something as big as Orain ;-) --Tepples (talk) 19:53, 6 December 2014 (UTC)