Consume long the Content, and the Content will also consume thee
7349 stories
·
148 followers

Office of Alberta Premier Smith responds to her comment about chemtrails

1 Comment and 2 Shares
A woman's profile is shown.

Alberta Premier Danielle Smith's office says her recent comments about chemtrails don't mean she believes the United States government is spraying them in the province.

Read the whole story
DMack
13 days ago
reply
If the US department of defense is spraying mind-altering chemicals onto Alberta, that would explain a lot
Victoria, BC
ReadLots
13 days ago
The following exchange at the town hall focused on flat-earth related initiatives.
dreadhead
15 days ago
reply
Vancouver Island, Canada
Share this story
Delete

The Terror fan helps scientists solve nearly two-century archeological mystery

1 Share

A new study published on Tuesday resolved an archeological mystery that dates back almost two centuries. As depicted in AMC's critically acclaimed series The Terror, an English expedition led by Captain John Franklin ended in disaster when its two ships became stuck in the ice of the Canadian Arctic. All 129 crew members of the HMS Terror and HMS Erebus perished as a result of various maladies and afflictions, and the remains of bodies that were eventually found went largely unidentified. But researchers have now been able to match the DNA of a descendant to the remains of James Fitzjames, captain of the Erebus, and they've got a Terror fan to thank.

Literally: Fabiënne Tetteroo, herself a historian, is mentioned in the acknowledgments of the paper outlining the identification of Fitzjames' remains (via The Verge). Tetteroo first became interested in Franklin's lost expedition after watching the AMC show, and in particular developed an interest in Fitzjames. According to her website, she's now writing her own biography of Fitzjames. The archaeologists who identified Fitzjames thanked Tetteroo "for generously sharing the results of her investigations of Fitzjames’ family history and for her efforts to identify possible candidates for our Franklin expedition DNA research. It was through her efforts that we were connected with the descendant donor."

The site where Fitzjames—who was played by Tobias Menzies in the show—and at least a dozen others died was found in the 1860s, per The Guardian. It wasn't until 2013 when a team led by Douglas Stenton, adjunct professor of anthropology at the University of Waterloo, was given permission to bring some of the remains back to England. That team put out a call for possible relatives of members of the expedition to donate DNA samples for the identification process. Until now, only one other member of the expedition (John Gregory, an engineer aboard the Erebus) had been identified back in 2021. The DNA of a descendant, apparently found through Tetteroo's research, was matched to a molar from one mandible (a jawbone). The molar was etched with knife marks, indicating cannibalism, one of the many gruesome fates that befell the Franklin expedition, also depicted in the series. "The identification of Fitzjames’ remains provides new insights about the expedition's sad ending," Stenton told the BBC.



Read the whole story
DMack
19 days ago
reply
Victoria, BC
Share this story
Delete

Sunken superyacht believed to contain watertight safes | CNN

2 Comments and 3 Shares

Specialist divers surveying the wreckage of the $40 million superyacht that sank off Sicily in August, killing eight people including British tech tycoon Mike Lynch, have asked for heightened security to guard the vessel, over concerns that sensitive data locked in its safes may interest foreign governments, multiple sources told CNN.

Italian Prosecutors who have opened up a criminal probe into multiple manslaughter and negligent shipwreck think the 56-meter (184-foot) yacht, the Bayesian, may contain highly sensitive data tied to a number of Western intelligence services, four sources familiar with the investigation and salvage operation said.

Lynch was associated with British, American and other intelligence services through his various companies, including the cyber security company he founded, Darktrace.

That company was sold to Chicago-based private equity firm Thoma Bravo in April. Lynch, whose wife’s company Revtom Limited owned the vessel, was also an adviser to British prime ministers David Cameron and Theresa May on science, technology and cyber security during their tenures, according to British government and public Darktrace records.

The sunken vessel, lying on the seabed at a depth of some 50 meters (164 feet), is thought to have watertight safes containing two super-encrypted hard drives that hold highly classified information, including passcodes and other sensitive data, an official involved in the salvage plans, who asked not to be named, told CNN. Specialist divers with remote cameras have searched the boat extensively.

Initially, local law enforcement feared that would-be thieves might try to reach the wreckage to find expensive jewelry and other objects of value still onboard the yacht, according to divers with the Fire Brigade who spoke with CNN. Now they are concerned that the wreckage, expected to be raised in the coming weeks as part of the criminal investigation into the tragedy, will also be of interest to foreign governments, including Russia and China. They have requested that the yacht be guarded closely, both above water and with underwater surveillance.

“A formal request has been accepted and implemented for additional security of the wreckage until it can be raised,” Francesco Venuto of the Sicilian Civil Protection Agency confirmed to CNN.

Lynch, his 18-year-old daughter Hannah, American attorney Chris Morvillo and his wife Neda, British banker Jonathan Bloomer and his wife Judy, and the yacht’s onboard chef Recaldo Thomas died when the ship sank in a violent storm in the early hours of the morning.

Preliminary results from autopsies suggest that the Bloomer and Morvillo couples died of suffocation or “dry drowning” when the oxygen in an air bubble in a sleeping cabin ran out. Autopsy results for Lynch and his daughter were less clear.

The chef, whose body was found outside the vessel, died by drowning, the coroner said. Toxicology reports on the dead have not yet been released, but none had suffered any physical injuries when the boat went down.

Lynch’s wife Angela Bacares and 14 others survived, including the captain James Cutfield, who, along with a deckhand and the yacht’s engine room manager, is under investigation for multiple manslaughter and causing a negligent shipwreck. They have all been allowed to leave Italy.

Some of the 15 survivors, of whom nine were crew members and six were passengers, including a 1-year-old girl, reportedly told prosecutors that Lynch “did not trust cloud services” and always kept data drives in a secure compartment of the yacht wherever he sailed, a source with the prosecutor’s office told CNN. None of the crew or passengers who survived the incident were tested for drugs or alcohol because they were in a “state of shock,” authorities said during a news conference following the recovery of the bodies.

Morvillo represented Lynch when he was acquitted in a criminal fraud case in the US in June tied to the takeover by Hewlett Packard of his software company Autonomy, and survivors told investigators that the cruise was a celebration of that acquittal, according to the assistant prosecutor, Raffaele Cammarano. Though Lynch was acquitted of any criminal wrongdoing in the US, Hewlett Packard has indicated it will not drop its bid to collect a $4 billion civil payout from Lynch’s estate, awarded by a British court in 2022.

In what appears to be a tragic coincidence, Lynch’s business partner Stephen Chamberlain — who was his co-defendant in the US fraud case and the former chief operating officer of Darktrace — died on August 19, the same day the Bayesian sank, after being hit by a car while out jogging two days earlier. A spokesperson for the prosecutor’s office told CNN that Cutfield told them Lynch had learned of Chamberlain’s serious condition and had planned to cut the cruise short to return to the UK to see his business partner, who had been on life support.

The Bayesian sank a few hours before Chamberlain died in the hospital, his lawyer said. Lynch would not have known of his partner’s death, and Chamberlain was in a coma so would not have known about the shipwreck, Chamberlain’s legal counsel said.

Local prosecutor Ambrogio Cartosio said no personal effects, including computers, jewelry or Lynch’s hard drives had been recovered from the vessel. However, the onboard hard drives and surveillance cameras tied to the yacht’s navigation system have been brought to investigators to determine if there is any usable data that might indicate how the yacht sank within 16 minutes of the storm hitting. The vessel did not have a traditional black box or voyage data recorder to record navigation data or audio on the bridge.

After divers complete surveys of the wreck this week, they will make suggestions for how to best raise the 473-ton vessel without spilling any of the 18,000 liters of oil and fuel still onboard, and how to make sure any sensitive data does not fall into the wrong hands. The costs of raising the ship will fall to its owner, Lynch’s widow, as is mandated by Italian maritime law.

Read the whole story
DMack
20 days ago
reply
Superyacht owners, they're nothing like us!
Victoria, BC
fxer
23 days ago
reply
> In what appears to be a tragic coincidence, Lynch’s business partner Stephen Chamberlain — who was his co-defendant in the US fraud case and the former chief operating officer of Darktrace — died on August 19, the same day the Bayesian sank, after being hit by a car while out jogging two days earlier

!!!
Bend, Oregon
Share this story
Delete

Celebrity Number Six was found

1 Comment
the low-stakes internet mystery to identify the only unknown celebrity on a shower curtain pattern is solved after four years #
Read the whole story
DMack
37 days ago
reply
peak reddit is cracking a mystery like this but not saying who it is
Victoria, BC
denismm
37 days ago
Agreed but if you scroll down a little: “The person depicted in the picture is the spanish model Leticia Sardá. A few days ago, I got in touch with the photographer Leandre Escorsell asking if he knew something about the image. I asked him because he took the photograph that served as a cover of the supplement of Woman Nº162 spanish magazine that features Leticia. He claimed that he recognised the photo and sent me the picture.”
Share this story
Delete

Announcing Vue 3.5

1 Comment

Today we are excited to announce the release of Vue 3.5 "Tengen Toppa Gurren Lagann"!

This minor release contains no breaking changes and includes both internal improvements and useful new features. We will cover some highlights in this blog post - for a full list of changes and new features, please consult the full changelog on GitHub.


Reactivity System Optimizations

In 3.5, Vue's reactivity system has undergone another major refactor that achieves better performance and significantly improved memory usage (-56%) with no behavior changes. The refactor also resolves stale computed values and memory issues caused by hanging computeds during SSR.

In addition, 3.5 also optimizes reactivity tracking for large, deeply reactive arrays, making such operations up to 10x faster in some cases.

Details: PR#10397, PR#9511

Reactive Props Destructure

Reactive Props Destructure has been stabilized in 3.5. With the feature now enabled by default, variables destructured from a defineProps call in <script setup> are now reactive. Notably, this feature significantly simplifies declaring props with default values by leveraging JavaScript's native default value syntax:

Before

ts
const props = withDefaults(
  defineProps<{
    count?: number
    msg?: string
  }>(),
  {
    count: 0,
    msg: 'hello'
  }
)

After

ts
const { count = 0, msg = 'hello' } = defineProps<{
  count?: number
  message?: string
}>()

Access to a destructured variable, e.g. count, is automatically compiled into props.count by the compiler, so they are tracked on access. Similar to props.count, watching the destructured prop variable or passing it into a composable while retaining reactivity requires wrapping it in a getter:

js
watch(count /* ... */)
//    ^ results in compile-time error

watch(() => count /* ... */)
//    ^ wrap in a getter, works as expected

// composables should normalize the input with `toValue()`
useDynamicCount(() => count)

For those who prefer to better distinguish destructured props from normal variables, @vue/language-tools 2.1 has shipped an opt-in setting to enable inlay hints for them:

inlay hints for destructured props

Details:

  • See docs for usage and caveats.
  • See RFC#502 for the history and design rationale behind this feature.

SSR Improvements

3.5 brings a few long-requested improvements to server-side rendering (SSR).

Lazy Hydration

Async components can now control when they should be hydrated by specifying a strategy via the hydrate option of the defineAsyncComponent() API. For example, to only hydrate a component when it becomes visible:

js
import { defineAsyncComponent, hydrateOnVisible } from 'vue'

const AsyncComp = defineAsyncComponent({
  loader: () => import('./Comp.vue'),
  hydrate: hydrateOnVisible()
})

The core API is intentionally lower level and the Nuxt team is already building higher-level syntax sugar on top of this feature.

Details: PR#11458

useId()

useId() is an API that can be used to generate unique-per-application IDs that are guaranteed to be stable across the server and client renders. They can be used to generate IDs for form elements and accessibility attributes, and can be used in SSR applications without leading to hydration mismatches:

vue
<script setup>
import { useId } from 'vue'

const id = useId()
</script>

<template>
  <form>
    <label :for="id">Name:</label>
    <input :id="id" type="text" />
  </form>
</template>

Details: PR#11404

data-allow-mismatch

In cases where a client value will be inevitably different from its server counterpart (e.g. dates), we can now suppress the resulting hydration mismatch warnings with data-allow-mismatch attributes:

vue
<span data-allow-mismatch>{{ data.toLocaleString() }}</span>

You can also limit what types of mismatches are allowed by providing a value to the attribute, where the possible values are text, children, class, style, and attribute.

Custom Elements Improvements

3.5 fixes many long-standing issues related to the defineCustomElement() API, and adds a number of new capabilities for authoring custom elements with Vue:

  • Support app configurations for custom elements via the configureApp option.
  • Add useHost(), useShadowRoot(), and this.$host APIs for accessing the host element and shadow root of a custom element.
  • Support mounting custom elements without Shadow DOM by passing shadowRoot: false.
  • Support providing a nonce option, which will be attached to <style> tags injected by custom elements.

These new custom-element-only options can be passed to defineCustomElement via a second argument:

js
import MyElement from './MyElement.ce.vue'

defineCustomElements(MyElement, {
  shadowRoot: false,
  nonce: 'xxx',
  configureApp(app) {
    app.config.errorHandler = ...
  }
})

Other Notable Features

useTemplateRef()

3.5 introduces a new way of obtaining Template Refs via the useTemplateRef() API:

vue
<script setup>
import { useTemplateRef } from 'vue'

const inputRef = useTemplateRef('input')
</script>

<template>
  <input ref="input">
</template>

Prior to 3.5, we recommended using plain refs with variable names matching static ref attributes. The old approach required the ref attributes to be analyzable by the compiler and thus was limited to static ref attributes. In comparison, useTemplateRef() matches the refs via runtime string IDs, therefore supporting dynamic ref bindings to changing IDs.

@vue/language-tools 2.1 has also implemented special support for the new syntax, so you will get auto-completion and warnings when using useTemplateRef() based on presence of ref attributes in your template:

inlay hints for destructured props

Deferred Teleport

A known constraint of the built-in <Teleport> component is that its target element must exist at the time the teleport component is mounted. This prevented users from teleporting content to other elements rendered by Vue after the teleport.

In 3.5, we have introduced a defer prop for <Teleport> which mounts it after the current render cycle, so this will now work:

html
<Teleport defer target="#container">...</Teleport>
<div id="container"></div>

This behavior requires the defer prop because the default behavior needs to be backwards compatible.

Details: PR#11387

onWatcherCleanup()

3.5 introduces a globally imported API, onWatcherCleanup(), for registering cleanup callbacks in watchers:

js
import { watch, onWatcherCleanup } from 'vue'

watch(id, (newId) => {
  const controller = new AbortController()

  fetch(`/api/${newId}`, { signal: controller.signal }).then(() => {
    // callback logic
  })

  onWatcherCleanup(() => {
    // abort stale request
    controller.abort()
  })
})

For a comprehensive list of changes and features in 3.5, check out of the the full changelog on GitHub. Happy hacking!

Read the whole story
DMack
41 days ago
reply
Vue's got reactive prop destructuring now 🎉 What's next? If statements in React?
Victoria, BC
Share this story
Delete

Departure Mono

1 Comment
free monospaced pixel font with a very nice website to promote it #
Read the whole story
DMack
45 days ago
reply
Reminds me of the "Dina" bitmap font I used to use for many years. (Until monitor resolutions and my aging eyes meant I couldn't read it anymore!)
Victoria, BC
dreadhead
45 days ago
Reminds me of "papers please"
Share this story
Delete
Next Page of Stories