AllAstronauts

If y'all need an after-action for this stuff: <I'm, hand-waiving away a lot here, just go with it> There was HTTP and everyone said this web stuff is fun. Then someone came along and said "you realize all our comms over the wire are more or less in plain text that anyone can listen in on" so they added an S to the end and came up with HTTPS. When you connect to secure sites your comms are encrypted both ways and no one can snoop <for values of 99.999% excluding NSA and other three-letter and/or international agencies>. They could record all the traffic between you and here, but not much they can do about it. It took ages for people to get religion and for use to ramp up but then someone said "great, the comms are encrypted, but how the hell do I know you and this site are who you say you are. You could be lying?" so we got security certificates. We can create these certificates ourselves directly on the server but these are the equivalent of you making your own drivers license as an 18 year old to try to get into a bar. So instead, you contract out with other organizations that "verify" you are you and that you control the actual server and control the actual domain and the domain name is kosher and etc. etc. Then you the site owner receive two bits of cryptology which you add to your site's web server so when you, yes you the user, connect to a website that purports to be secure, your browser checks that these bits of cryptology check out and match x, y, z and so on, so forth. All good, connect away. You can trust all this. Certificates do expire. Sites move servers, things change, etc., so its built into the system to have these time-limited. When a cert expires, you get you a new one, upload the bits, things carry on as normal. Note the site and your comms between you and here REMAIN SECURE even when the certificate is self-signed or expired. Always secure. But can you "trust" that nothing bad has happened? So... When the browser detects that a certificate has expired or is self-signed it now tells you something is up! And for about the last five years or so they really try to stop you from visiting the site at all to "protect you" from yourself. So, what happened here? The certificate expired a few days ago. The certificate was renewed at the external org that does this stuff. Note this is a paid-for certificate and needs to be manually applied to the server. Nobody told me this was going on. Your browsers cache tons of stuff, so as your browsers collectively started to detect the expired certificate, and the underlying services (image hosting, etc.) did the same, stuff started to "break". And then at 1230am my time I got pinged :) Short story short, the site owner got texted and I poked around the server to see where the certs were. No txt back but I noticed a free solution was set up but was never configured or used, and just used that to generate the new certificates, then went to bed :) The free solution, for those that need closure, is that about 10 years ago some people realized that paying for another org to verify you are who you are and so on was just an un-needed tax on the entire web. All that is needed for kosher certificates is for the person controlling the domain (site name) records and the actual server itself to match up <hand-waiving here again>. So something called LetsEncrypt was born, a free service, that automatically renews everything, hands-off excellence. Verifies domain and server and so on are all correctly, truthfully linked together and issues the certificates directly on the server. As for the janky site-width and font-size stuff chalk that up to a bad site-cache clear internally sometime over the last 24 hours or more and some javascript was skipped and not cached correctly. These probs go away with the new tech stack in version 5x of this software which the dev site for the new version of this site goes live... uhhh... whenever the site owner makes a tiny change in an account file so the dev site can go live. You should be nice to @CM-BlueButterfly, some users will get to play early for test purposes. Everything is working, verified, width-font buttons too. All down to caching and time on your end now.

Certificate is valid again, if you accepted the not-secure stuff to browse it will take a bit before your browser validates (whatever) the new cert but if you open the site in another browser or an incognito mode it will be secure. You can check the cert status by clicking that little box next to the start of the site url up top. It will say secure now and if you click that to view the details you'll see a LetsEncrypt cert that will "expire" in March and subsequently be automatically renewed at that date and we'll never speak of this again.

There is a bad advertising provider in the mix. Report this in the bad ad thread. Note: Any place can get caught out on this. ESPN still lets through ad that will swap the page I'm viewing for some random Comcast offer thing.

As far as I know there have been no updates to the site in ages (a few months at least) Check your Account Settings and Content View Behavior to be sure nothing has changed there:

This came up before when I tossed this feature in for kicks. Yes, easy to do. Was not done at the time for the above reason. Could be done with a cookie toggle like screen width and light/dark and so on. Again, easy. This is just an info dump, should not be taken as will-happen, might-happen, etc.

hmmm Now?

CSS files stalled when built for cache. All better.

Just gonna pop-in and say that what you (all) are starting to do is shape what will be the next version of the Shows app. The show header image was just a derpy throw-in while I was doing <redacted> for mods a few months back. The external API stuff is all there with episode counts and previews and summaries and etc, etc, and is available in the backend already. Just throwing these things in willy/nilly into what is here right now is not ideal (albeit easy though). I'd actually automate the whole thing. Adding a show sets up all the automatic data pulls and presentation with mods allowed to over-ride as needed/wanted. As this is a business, there are generally costs for APIs when there is a profit to be had so there is that consideration as well when backend things spill into public things. Given the closure of the main PT site I imagine changes of the overhaul/wholesale variety will be measured and planned so as to anchor things going forward with the next version of the software AND to last a fair number of years going forward. Do not take anything I said as to mean "there will be a new shows app", "this site is going to upgrade the software soon", "this thing I want is going to be added". None of that in any way, shape, or form is true as it simply has not been discussed yet. Right now, only possibilities; until they are not.

Not for nothing, but Yahoo email (and I can see this directly in the email logs on the server) can get really grumpy with too many emails from one source over a short period of time. It's not so much an "us" problem but a "Yahoo" problem. It still goes through, but they (Yahoo) purposely delay accepting the email. This site is going to use a trusted email provider for outbound-from-the-server emails in the near future to maybe smooth this over but Yahoo might still Yahoo if you know what I mean... Email is a hellscape on the provider side these days and trust is hard to come by (or create) and so here we are.

Believe it or not the system allows you to adjust the editor buttons available when displayed at desktop, tablet, and phone sizes. The idea being some things are just not going to be done in an editor with a phone so no need to show those options. Note: I have not configured the editor on this site. It's either the defaults you are getting or changed before my time. <clicks a few button in the administrators center....> There you go.

There is/was some conflict with the jump-to-top button and the bottom corner video ad. I've adjusted it to always display ABOVE the ad now. It may have just been inadvertent finger stuff in the corner with the jump button buried beneath the ad. Also if you are on a phone AND have some crappy throughput (this happens to me in the grocery store even if I flip to the store internet) I would not be surprised that the browser jumps to a certain location after the page fully loads (for any variety of reasons) Provided my change is not reverted by the advertiser ghosts we can let this ride and see what happens.

How it works: The image is set to "cover" which centers the image vert and horz, and then ALWAYS fills the space that is available. The space available is 220 pixels in height, and the width is covered automatically with what is available. Very wide screen to phone views in descending order. I could set the height a little bit higher but then you are really pushing the content down the page. This was a derpy little perk I threw in when building out <redacted>. There are ways to set the thing more rigidly - your profile pages - the full page - you have a "cover photo" you can apply that allows you to adjust the positioning of the image and that could be done here but its really a feature that can, and should, wait for the next version of the shows app.

Guys, don't worry so much about the exact pixel whatevers. If its like 600x400 that's just too low of resolution. Tiny thing. Blah. On the other hand, 4000x2000 is overkill. Just be reasonable. Landscape views. Try and keep the size of the image down as well. Anything north of 600k is not exactly ideal. Yes, your browser will cache the image and all that but still... For those in the know, these images are just set to cover, so expect so cropping when the proportions are way off. Now that said... This is tied up in a mod tool from the before-the-changes time. The only reason, more or less, nothing is happening with these images right now is that there are only <redacted> mods available. So its not a priority. I can throw a few on if you have them (takes two seconds) but I'm also pinging lead mod on this now. Done.

Relatively well-sized (400x300 pixels won't cut it). More wide than tall. The rest is not my call (but the feature is still live and available for use)

No but you are going to have to eat this one for now. Its a server configuration hitch or the plugin that is altering search stuff. This is, honestly, small beans right now so imma gonna note it and leave for when I make a bunch of server adjustments in the near future.