Recommended Posts

Just now, Matthew S. said:
  Reveal hidden contents

You did, Starfleet has been compromised by the Romulans.

 

Spoiler

No, I got that part, just wondering how, which we're probably going to find out later.  But most of all where's Section 31 who should be all over this type of stuff?    

 

I actually think the compromise is limited and not wide spread so that should explain it to a degree.

 

Just now, George P said:
  Hide contents

No, I got that part, just wondering how, which we're probably going to find out later.  But most of all where's Section 31 who should be all over this type of stuff?    

 

I actually think the compromise is limited and not wide spread so that should explain it to a degree.

 

Spoiler

Don't forget the way these ops are being run appear to be S31 ops...

 

Just now, Matthew S. said:
  Hide contents

Don't forget the way these ops are being run appear to be S31 ops...

 

Spoiler

True, wonder if they're working together for a shared goal.  S31 to get rid of most of the Romulans and these dudes to take out any advanced federation synthetic tech.  Guess we'll see how deep it all goes.

 

On 1/30/2020 at 8:16 AM, Matthew S. said:
  Reveal hidden contents

Did anyone notice the disease Picard has been diagnosed with is eerily similar to the one Prof. X had in Logan?

 

Spoiler
This goes back to the episode, "All Good Things" where Picard is experiencing the future and he's living on the family vineyard and is suffering
from a neurological disorder called "Irumodic Syndrom".
 
Also, wonder why Crusher isn't his personal doctor.

 

Overall, another good episode and great to here some cursing in Star Trek ;)

 

Spoiler

I loved the sign in the Borg cube (around 25:36), "This Facility Has Gone 5843 Days Without An Assimilation"

 

  • Haha 2
3 hours ago, primortal said:
  Reveal hidden contents
This goes back to the episode, "All Good Things" where Picard is experiencing the future and he's living on the family vineyard and is suffering
from a neurological disorder called "Irumodic Syndrom".
 
Also, wonder why Crusher isn't his personal doctor.

 

Overall, another good episode and great to here some cursing in Star Trek ;)

 

  Reveal hidden contents

I loved the sign in the Borg cube (around 25:36), "This Facility Has Gone 5843 Days Without An Assimilation"

 

Spoiler

I believe she's just too busy and still in active duty, not retired etc.  And the show just doesn't want to make this TNG again, so they're going to find ways to make room for the new cast instead of relying on the old guard.

 

Starfleet looks like utter garbage right now. I’ve never really liked them, but wow, the degradation they have suffered (regardless of current conspiracy) really paints them as bad guys in this series. Thinking they have the power to end a species and justify it? No wonder Picard left. Definitely some major prime directive violations happening.

 

We had warning signs of this in TNG when Picard could of used Hugh to end the Borg, and he got called out by starfleet in a later episode for not doing it.


Not to mention s31 trying to wipe out the Founders, granted a war was occurring.

 

This degradation has been happening for far longer than only after Nemesis. 

 

Loving this series so far. Episode 2 ended so abruptly, really wish episode 3 was available lol. 
 

I do wish we could see some fresh starfleet starship designs. We saw some weird ones orbiting Mars this episode, but those looked more like construction vessels. 
 

I also hope they fill in more of what happened to the Enterprise E, as well as new vessel we saw him command in the comics.

 

I am interested to see if this conspiracy results in the pulling out of member species in the federation, as been alluded to in Discovery/31st century. 

Edited by shockz
  • Like 2
16 minutes ago, George P said:
  Reveal hidden contents

I believe she's just too busy and still in active duty, not retired etc.  And the show just doesn't want to make this TNG again, so they're going to find ways to make room for the new cast instead of relying on the old guard.

 

Spoiler

I do get that, but sort of throws their history away IMHO.  I'm not looking for a full fledge reunion, but a few minutes of air time wouldn't kill and they easy could have sent Crusher on away mission (command of a medical ship or something) to "writer her out" off the series.

 

2 minutes ago, shockz said:

Episode 2 ended so abruptly

Yeah, the episode did end a little weirdly.

He's probably fully aware that shes off on her own missions on the USS Pasteur and didn't even think to pester his ex wife for a fitness report. It's probably against protocol to have your ex wife to perform the exams in an official manner as well.

4 minutes ago, Louisifer said:

He's probably fully aware that shes off on her own missions on the USS Pasteur and didn't even think to pester his ex wife for a fitness report. It's probably against protocol to have your ex wife to perform the exams in an official manner as well.

That's if it's still true.  Being Picard changed the future in All Good Things, they might not have ever married or she's not even on the Pasteur.  Hopefully we'll get a answer this season being they didn't comment on that she's not in this season like they said for Worf and Geordi.

28 minutes ago, FloatingFatMan said:

Just putting this out there, purely as my own opinion... Those synths didn't rebel... they were hacked.

I hope they weren't hacked by the secret section of the Tal Shiar (I'm not even going to attempt to spell it without looking at the closed caption), who apparently has hated synths and that hate being a bedrock of their org. It'd be predictable if they were ultimately the one behind the Mars attack in an attempt to end sentient synth development. The most obvious answer to me is Maddox flipped a switch on them. 

 

I have a feeling data's daughters didn't just happen upon Daystrom and a Borg Cube by chance, Maddox sent them there for tech recon and gathering I feel.

 

Granted the synths on mars were treated like slaves/badly. I also remember the VOY episode that revolved around the photons be free concept, and how it spread to the other EMHs that were reprogrammed to be salves in dilithium mines, wonder if Zimmerman or the Doc had something to do with it, although that'd be a shocking twist. Doc has gone rogue before with the Hirogen holograms.

 

Robert Picardo is rumored to be in S2 though.

7 minutes ago, shockz said:

I hope they weren't hacked by the secret section of the Tal Shiar (I'm not even going to attempt to spell it without looking at the closed caption), who apparently has hated synths and that hate being a bedrock of their org. It'd be predictable if they were ultimately the one behind the Mars attack. 

 

I fully expect this to turn out to be the answer.  CBS's writers just ain't subtle...

7 minutes ago, shockz said:

The most obvious answer to me is Maddox flipped a switch on them. 

If it was Maddox, then he's truly lost his mind to have killed so many just because his synths ended up as slaves, as predicted by Picard.

 

7 minutes ago, shockz said:

I have a feeling data's daughters didn't just happen upon Daystrom and a Borg Cube by chance, Maddox sent them there for tech recon and gathering I feel.

This much is obvious.

 

 

7 minutes ago, shockz said:

 

Granted the synths on mars were treated like slaves/badly. I also remember the VOY episode that revolved around the photons be free concept, and how it spread to the other EMHs that were reprogrammed to mine dilithium, wonder if Zimmerman or the Doc had something to do with it, although that'd be a shocking twist.

  Hide contents

Robert Picardo is rumored to be in S2 though.

 

The Doctor can do no harm, it's in his core programming.

10 minutes ago, FloatingFatMan said:

 

I fully expect this to turn out to be the answer.  CBS's writers just ain't subtle...

If it was Maddox, then he's truly lost his mind to have killed so many just because his synths ended up as slaves, as predicted by Picard.

 

This much is obvious.

 

 

The Doctor can do no harm, it's in his core programming.

I'd have to agree, however we've had those ethical subroutines deleted before, the doctor also has grown as an individual and also has the ability to modify his subroutines. He's also aligned himself with enemies before, assisted in abduction of Torres, while severely damaging Voyager, intentionally sickened someone when he was kidnapped, etc... I'm just saying it wouldn't be impossible, albeit highly unlikely.

16 minutes ago, FloatingFatMan said:

 

If it was Maddox, then he's truly lost his mind to have killed so many just because his synths ended up as slaves, as predicted by

Look at Zimmerman though, back with the EMH2, 3, 4, etc... he was furious that they ended up as slaves. Embarrassed even. He'd rather of died of a sickness than being treated by a disgraced program he created, Granted it's one thing to be upset that your creations ended up as slaves vs actually blowing up an entire planet in retribution. 

23 minutes ago, shockz said:

I hope they weren't hacked by the secret section of the Tal Shiar (I'm not even going to attempt to spell it without looking at the closed caption), who apparently has hated synths and that hate being a bedrock of their org.

It begs the question on why are they doing reclamation on a Borg cube?  Granted they are selling the technology which could possibility lead to a new generation of synths/AI.

16 minutes ago, primortal said:

It begs the question on why are they doing reclamation on a Borg cube?  Granted they are selling the technology which could possibility lead to a new generation of synths/AI.

There is also the Discovery factor with Control. This type of AI almost ended existence as they knew it. While it was classified at the highest level, it's also hard to keep things like under wraps for almost 150-200 years, and perhaps it will be brought up again with covert ops running around on Earth ending things all AI.

 

Side note: There was an interview I read once about Enterprise Season 5, where the writers were going to revisit the events of the Enterprise episode, Regeneration, and Alice Kurge was to be called back to act as a Starfleet science officer continuing research of the sphere wreckage, who was ultimately assimilated by said wreckage and became the queen we see prior, and the tech created would of been similar to that of the control AI, when attempts to return the 24th century went wrong, She ended up back thousands of years in the past in the Delta quadrant and she begun their expansion with existing Borg who apparently were struggling and only assimilated a handful of systems.. the typical Star Trek paradox. Post Season 3 enterprise was amazing, and it sounded like Season 5 would of continued. Too bad.

Edited by shockz
14 minutes ago, shockz said:

There is also the Discovery factor with Control. This type of AI almost ended existence as they knew it. While it was classified at the highest level, it's also hard to keep things like under wraps for almost 150-200 years, and perhaps it will be brought up again with covert ops running around on Earth ending things all AI.

 

Don't be too surprised if Control makes a return...

On 1/23/2020 at 10:10 AM, George P said:

It could just be a different Q, or Q could just change his look.  I don't think anything in the canon says he/they can't.

Q is not human nor he is humanoid or mortal. He can take the look he wants.

OK, here is the question: Picard keeps referencing that Data sacrificed himself. Did this happen in any of the movies, or is this something that they have added for shock value/story builder? I asked my brother-in-law whom is obsessed with anything Star Trek, and he could not recall it happening. 

Just now, jnelsoninjax said:

OK, here is the question: Picard keeps referencing that Data sacrificed himself. Did this happen in any of the movies, or is this something that they have added for shock value/story builder? I asked my brother-in-law whom is obsessed with anything Star Trek, and he could not recall it happening. 

See Star Trek Nemesis.

13 minutes ago, LaP said:

Q is not human nor he is humanoid or mortal. He can take the look he wants.

Sure, but anyone else playing Q just ain't Q to the viewing public. We DEMAND DeLancie! Only he has the right level of snark necessary for the King of Chaos!

 

  • Haha 1
6 minutes ago, jnelsoninjax said:

OK, here is the question: Picard keeps referencing that Data sacrificed himself. Did this happen in any of the movies, or is this something that they have added for shock value/story builder? I asked my brother-in-law whom is obsessed with anything Star Trek, and he could not recall it happening. 

 

  • Thanks 1
4 minutes ago, FloatingFatMan said:

See Star Trek Nemesis.

Sure, but anyone else playing Q just ain't Q to the viewing public. We DEMAND DeLancie! Only he has the right level of snark necessary for the King of Chaos!

 

Thanks for the reference!

I also 100% agree with you, you can't replace DeLancie!

1 minute ago, jnelsoninjax said:

Thanks for the reference!

I also 100% agree with you, you can't replace DeLancie!

TBH, I think (hope) that we WILL see Q, but not until Picard finally reaches his end and the Irumotic Syndrome takes him.  It truly would be fitting if Q took Picard away to the Continiuum or something like that.

8 minutes ago, FloatingFatMan said:

See Star Trek Nemesis.

Sure, but anyone else playing Q just ain't Q to the viewing public. We DEMAND DeLancie! Only he has the right level of snark necessary for the King of Chaos!

 

For sure but him appearing older would just make sense (contrary to data). The Q Continuum always wanted to make human comfortable while interacting with them (outside of Q craziness). They always appear in a form understandable by humans. So him appearing to people he already know as 30 years older because 30 years has passed (from a human perspective) just make sense from a lore perspective.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
  • Recent Achievements

    • First Post
      BizSAR earned a badge
      First Post
    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      598
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      80
    4. 4
      Michael Scrip
      76
    5. 5
      Steven P.
      69
  • Tell a friend

    Love Neowin? Tell a friend!