• 0 Posts
  • 16 Comments
Joined 7 months ago
cake
Cake day: April 21st, 2024

help-circle



  • Syndication is also called reruns, when the show is rerun out of order on TV at a standard Timeslot. Like for me TNG was on every night at 7pm M-F. It was shown in random order as far as I know with I believe them skipping less popular episodes, I honestly never noticed if they did hits for a bit then did a rerun through it or what.

    The first season of TNG is considered weak as a heads up, similar for DS9 though DS9 has some bangers in S1, TNG is mostly weak. That said if you like it, you’ll LOVE the rest.

    SNW is fantastic and I really recommend it, it is certainly New Trek but it’s a MUCH better successor to the legacy than Discovery.


  • jerakor@startrek.websitetoStar Trek@startrek.websiteWhere to start?
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    10 days ago

    Start with the best episodic episodes of TNG and DS9. Most of us were introduced to Star Trek out of order, it isnt like modern TV. 90s TV and prior was focused on syndication.

    My recommendations would be, TNG: Darmok, Tapestry, The Wounded, Inner Light, Cause and Effect, Lower Decks (The episode that inspired the show). For DS9: In The Pale Moonlight, Duet, Trials and Tribbleations, The Visitor (Rest in peace Tony Todd)





  • The we made some mistakes but we are proud of our heritage deal only works when you’re not massively losing due to being out of touch with the morals of your base. It’s easier for me to not see the parallels when they are not sending troops to cleanse Gaza. When you look at the votes for them and realize that it is a combination of both the people who want Democrats and the people who just don’t want Trump and they STILL can’t win it is a huge issue.

    It’s the oldest political party in the world, maybe it is time to rebuild it in a cleaner image.



  • The Republican party is policy wise to the right of both National and the NZ First party as a comparison. They will also control all arms of the government and it is potentially possible for them to amend the constitution without any recourse but it isn’t easy.

    So to be clear, they could change our Freedom of Religion and Speech to a Freedom of Christian Religions and “Truthful” Speech and there isn’t a ton that anyone could do to stop them just to give you an idea of the level of power they have taken in this election. It wouldn’t be easy, but the fact that it won’t be impossible should be terrifying.

    The goals they have of criminalizing providing abortion services in all cases for the entire country is entirely possible. They could round up every person in the country of a certain nationality and put them in camps like we did with the Japanese during WW2, Trump already cited this act as being something he is considering to deal with immigration.

    Historically we killed 90% of our indigenous population. When NZ was signing the Treaty of Waitangi, America was executing the Trail of Tears and rounding up 60,000 Native Americans and making them march 100km to live in a desert, a quarter of them died during the move. We’re not even starting in a similar place here and we’re moving far to the right.



  • This is a patch from the hardware vendor so I am assuming that the ask is not that the hardware vendor take responsibility but that they not release buggy hardware. That is what I mean about the validation issue.

    The attack vector is shared in the patch so it isn’t entirely a theory.

    There is a comment from Linus about how this patch is only needed for some hardware and doesn’t apply to others but I don’t get his relevance there as different hardware validates against different use cases and their source logic might be entirely disparate.

    So my validation talk is simply saying that bugs happen. My concern here is what more should a hardware vendor do beyond submitting a kernel patch? You can’t just not have the bug, and if you recall the part someone else will just keep theirs in the field and take all the market share and roll the dice that their bugs don’t get exploited.


  • Is this really the hardware vendor’s problem though? It’s the consumers problem.

    I bring up full validation because the concern here is putting in a speculative fix. If the ask is, why was the hardware like that in the first place the answer is because it can’t be fully validated. If the ask is why should a speculative fix go into the Kernel it is because the consumers are not on top of tree and if a fix has a chance of never being exploited it needs to be pulled in years ahead so it goes into an LTR that customers migrate to BEFORE the issue comes up.


  • Fully validating hardware is an insane task that hasn’t been really done in years. It would mean 5 years between chip releases and a 2-5X in cost to produce, and people wouldn’t follow the validated configs anyways. If we followed the validated hardware spec we would have 50 min boot times and not go past a 3.5Ghz clock.

    People have the choice today on if they want to run on validated hardware. You can opt in to get a 2.8Ghz part that supports 2666MT/s that is mostly tested and validated, or you can get a 5Ghz part that supports 6000MT/s that is only partially validated. They cost the same price. What do folks think people pick?