Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)M
Posts
6
Comments
1083
Joined
3 yr. ago

  • Are we talking about "Into Darkness"?

    I figure there, Kirk wasn't in trouble for saving the species, he was in trouble for revealing the Enterprise just to save one officer.

    If we're not talking about "Into Darkness", then I've just illustrated how often Trek goes for this plot point, lol.

  • I actually think they nailed it, in Strange New Worlds.

    The plot in Strange New Worlds had been my head canon for decades, because of Majel Barret's performance as Nurse Chapel in TOS.

    Once or twice, nurse chapel gives Spock "fuck me" eyes, and isn't bothered by his lack of reaction.

    I always thought this was Majel Barret's way of intentionally implying a scandalous tumultuous past relationship that would never be approved on 1960s TV.

    The fact that TOS Spock has virtually no reaction, other than obvious fondness for her, is largely due to Spock being TOS Spock.

    I think a lot of folks assumed that Nurse Chapel was pining for the exotic aliens unrequited love - which I think is certainly part of Majels intent n in her performance.

    But TOS Nurse Chapel is very emotionally intelligent. (Mainly to contrast Bones and Spock who are not.) Due to her high emotional intelligence, I was always inclined to believe that TOS Chapel probably knew what she was doing when she threw "we could still fuck (again?) sometime" eyes at Spock.

    We all think she has no chance, but Nurse Chapel knows Spock better than we do.

    And TOS Spock is incapable of acknowledging it, but probably still appreciates the gesture.

    Edit: The SNW Spock and Chapel story makes me happy, because I think it's exactly what Majel Barret intended to imply, during filming of TOS. I agree it doesn't fit everyone else's creative vision, but it makes me happy that hers became official canon.

  • So the only reason Picard is alive is because Q snap-fixed his artificial heart?

    I've always thought so. Q is quite fond of Picard. They have a strong one way bromance going. It's why Q won't leave him alone.

    Of course, in Picard Season 2,

    Q's entire grand scheme is, while perhaps also to fuck up history for fun, primarily to set the entire timeline to one where Picard doesn't suicide against the Borg.

    So Q has canonically saved Picard's life twice. Possibly more, assuming that Q's "gift" to Picard of early knowledge of the Borg also resulted in saving Picard's life during other encounters.

  • It happens.

    Here's a happier tale to balance the vibe.

    When traveling with my family, we often stop for a light meal midway to break up the monotony of the trip.

    One time we stopped at a place we don't care for the food, and bought a particularly light meal to settle our stomachs for the remaining minutes on the way to our favorite food stop.

    Toward the end of our quick stop, a stranger offered my oldest an unopened burger from his own meal that he wasn't going to finish.

    I think he probably noticed our order was on the small side and maybe worried whether my oldest got enough to eat.

    My kid was fine, of course, he got as much as he wanted and knew we were stopping soon somewhere he liked better.

    But that guy's compassion stuck with me.

    So now there's a line item in my budget for donations to a local food shelter. My intent is to always maintain that recurring donation, in honor of that guy's compassion.

  • Holy shit! Avatar is about capitalism? How did I miss that?! I better rewatch it and see if it's a recurring theme.

  • Lol.

    There was something magical when a mean kid would realize that my brothers' and my idea of a rollicking good time was a serious ass kicking on their scale.

    I'll admit, it doesn't speak well to my brothers' or my intellect, but I guess messing with us was particularly stupid.

  • "Java/Cobol is dead like Latin"

    I love that. I'm going to steal it.

    Edit: And I acknowledge that when I say that about Java, I'm just trying to wind people up. Java is losing popularity fast, but is still a pretty common first language.

  • Cobol is dead.

    And I think it's about time to start telling people Java and Perl are dead, so they can marvel at how much Cobol and Java and Perl are still doing in production after death.

  • This is delicious. I hope they hurry up, and I hope they do it in a really large really public context.

    I've had this conversation, but today's generation of AI won't:

    "No, I can't just do a one for one translation. Some of the core operating principles of the language are different, and the original intent needs to be well understood to make the appropriate translation choice. If I just translate it one to one, with no understanding of the business context. you're going to suffer from years off debugging subtle but impactful bugs."

    Get on with it IBM. Let's light this dumpster fire so we can all bask together in it's glow (and smell).

    There may be a day coming in the next 100-1000 years when a learning algorithm is a suitable replacement for an expert engineer, but that day has not arrived (and the early evidence of that impending arrival hasn't arrived, either. I haven't seen evidence of AGI experiments with even toddler reasoning levels, so far. Toddler level reasoning wil come before AGI with infrastructure deployment skills, which itself is probably coming before AGI with expert business logic diagnostic skills. This could all be 20 years or 1000 years away. But we will probably see LLMs running deeply insightful life changing management workshops sometime roughly next week, since a trained parrot could do that. If we have an AGI that can meaningfully reason with small numbers in the next 20 years, we will be making great progress and on track for the rest to arrive - someday. If not, then we're probably waiting on a missing computational breakthrough.)

  • Right. At least 70%. I've heard it estimated as high as 97%.

    And it's losing popularity with new development, (and with new developers) while WordPress, Drupal and WikiMedia are everywhere.

    Perfect recipe to be the next Cobol.

  • Hang in there. CORS is a huge pain in the ass on the best day.

    That said, if the issue is CORS, there should be a pretty specific message in the browser debug menu. Note that, if I've read that page correctly, the error won't be available to JavaScript runtime, as an intentional security "feature".

  • Yeah. There's always at least one mission critical Prel script that no one can read.

  • My money is on PHP.

  • Now we're making progress towards a plan.

  • CORS is just an ask for browsers specifically to stop cross domain communication, it protects the users not you.

    A minor point of clarification to this point.

    CORS also provides substantial protection to the server admin against innocent users being manipulated into taking malicious actions.

    So there is some value to the server admin as well.

    Sure, any malicious actor can assault the back end directly, but often they have no ability to attack from a context of authenticated trust.

    A CORS misconfiguration makes the system more vulnerable to attacks that manipulate legitimate users into taking malicious actions.

    So a CORS misconfiguration can lead to malicious actions coming in through highly trusted contexts, which can sometimes be substantially more harmful that random unauthenticated attack spam.

  • I have never done this before and I’m wondering if it’s secure enough to host the backend on some server and allow a CORS header to let the Frontend generate requests?

    As long as you can get it working without putting any wildcards (asterix *) in your CORS headers, you're using CORS as intended, and should be fine.

    The alternative would be to host Frontend and backend on a VPS and then route my domain that I bought on Cloudflare there, but then I’m thinking that in case my Frontend is insecure somehow the whole instance would be compromised, no?

    Back in my day we almost always hosted the front end and the back end on the same host. Of course, we also did a lot of stupid shit back then.

    It's not a disaster to host them the same place, but it's certainly not a best practice. It's better to get the CORS headers working, if you can. But just hosting them the same place isn't, by itself, a security issue. It enables a shit ton of other security mistakes to be cause a lot more harm. But it's not, itself, a problem.

    Edit: Bonus tip. You probably know this, but lots of newbies miss it. Every piece of code and config in your front end app is optional to me and to all bad actors. So take care you don't put any important secrets or critical defensive decision logic there.

  • A "real answer" is rarely as credible as an article with quotes including time and place, as well as citing statistics and peer reviewed studies.

    Depends what kind of learning is needed. Fixing a car, I have found rando-on-the-Internet to be a far more effective resource, than peer reviewed sanitized but irrelevant information.

    Different tools for different needs, and all that.

    People are even writing entire fanfictions about current events to fit their narrative.

    Impossible!

    (This is sarcasm, meant to purposefully demonstrate your point.)

  • His butt is one of today's lucky 10,000!