Welcome to Friendica.Eskimo.Com

Home of Censorship Free Hosting

 Eskimo North Linux Shells, E-mail, Virtual Machines, Web Hosting.

E-mail, Web Hosting, Linux Shell Accounts terminal or full remote desktops.

Sign Up For A Free Trial Here

Please tell your friends about federated social media site that speaks several fediverse protocols thus serving as a hub uniting them, hubzilla.eskimo.com, also check out friendica.eskimo.com, federated macroblogging social media site, mastodon.eskimo.com a federated microblogging site, and yacy.eskimo.com an uncensored federated search engine. All Free!

lemmy - Link to source

Preventing Asian Citrus Psysllid

I have a small lemon tree that was bought from a local grower and came with the extra bonus of an Asian Citrus Psysllid infestation. The tree is dead now and I'd love to get a new tree, but want to make sure I've done everything I could to prevent a new tree from getting infested by any Psysllid still in the area.

Is there anything I can do to treat my soil or surrounding plants to make sure those little buggers aren't going to keep coming back? I'm in California where the sale of IMIDACLOPRID products is banned, which was previously the primary treatment for this.

in reply to anticonnor

lemmy - Link to source

just_another_person

In all seriousness, you need to contact your local university agriculture extension. Like right now.

This is a huge problem this generated from unlicensed growers, and they are shipping this all over the country, causing massive outbreaks.

Unless you live in an area with an abundance of Mantids or Wasps, I don't think there are any other means of control aside from harsh pesticides.

Call your local extension immediately, tell them where you got it, and have them come visit to treat if necessary.

in reply to WoodScientist

lemmy - Link to source

Hacksaw

She said collisions with motor vehicles is definitely the most dangerous aspect, but in all situations, these scooters require a certain level of skill and balance.


I love how they're going out of their way to not admit this whole article is actually about cars running over kids on scooters.

I hate how much we protect drivers from accountability for their actions. If I go out and stab a kid for no reason I'm in jail for decades. If I run over enough kids on scooters they'll write whole-ass articles arguing that "scooters are unsafe"

in reply to Auli

lemmy - Link to source

Hacksaw

It doesn't take a genius to figure out that cars are running over these kids. Kids are naive and trust that cars aren't trying to run then over so they'll make stupid decisions (for our car brained society that lets people drive until they drop dead without annual testing).

Then look at the types of injuries, you're not cracking your skull or lacerating your abdomen falling off a kid's scooter that basically go human running speed (18-30km/h) MAX.

Then we have doctors taking about "sprains" and "concussions" typical falling off your e scooter injuries, but that the worst injuries are car related and it's pretty easy to see what's happening even with the blatant pro car bias this article has.

in reply to Davriellelouna

lemmy - Link to source

faxed

kids never even pretending to wear helmets on these things

someone i know was going for a walk and chanced upon a mangled child waiting for EMS to show up

52 per cent of all e-scooter injuries we’re seeing involve riders below the legal age


Do they at least give these people and their kids some sort of traffic rules class or something?

I don't know what the answer here is, it seems like a job for Public Health.

Give away free bicycles? What was wrong with bicycles?

in reply to faxed

lemmy - Link to source

Arondeus

Everything around them is built for cars. When that's the case, and you have no car (are underage to drive) you essentially have no freedom because you can't go anywhere or do anything. Bikes are great, they are also exhausting and impractical to cover the distances that cars can. An e-scooter can get you there faster than a bike and without being exhausted. I think it gives these kids a taste of freedom and independence that they crave.

lemmy - Link to source

Weird line tearing on KDE

Hi there, I've got these really odd issue where certain windows will cause random lines like the one in the screenshot appear on my screen. They will often flicker a bit and will dissapear if I hover my mouse over them. The lines will display what is beneath the window itself. These occour quite frequently and are frankly getting quite annoying to deal with.

Is this a known issue with KDE right now? It does not happen while using Gnome on the same machine + screen. If it matters I am running CachyOS.

If there is anythign I can do to fix this then I'd greatly appriciate some pointers!

lemmy - Link to source

GrapheneOS version 2025070300 released
Tags:
  • 2025070300 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, emulator, generic, other targets)

Changes since the 2025070100 release:

  • increase virtual memory reserved for Binder buffers from 1MiB to 8MiB due to Android 16 having a very large Binder transaction scaling up based on the number of apps and profiles which can go beyond the total size limit and break fully booting the OS, which occurred for a tiny number of our Alpha testers (if you were one of the tiny number of Alpha channel testers running into this, you can sideload this release to resolve the issue)
  • fix issues with display of the end session button to avoid it being wrongly displayed for Owner or not displayed for secondary users (we may remove this part of the upstream end session UI or make it optional since the functionality is also in the power menu)
  • update Pixel USB HAL to Android 16 (this was omitted in the initial port due to needing special handling for our USB-C port and pogo pins control feature)
  • always use UTC as the time zone for build date properties
  • kernel (6.6): update to latest GKI LTS branch revision

Release 2025070300 · GrapheneOS/platform_manifest

GitHub

lemmy - Link to source

GrapheneOS Foundation Commentary On ICEBlock's False Claims About Push Notifications
ICEBlock is making incredibly false privacy claims for marketing. They falsely claim it provides complete anonymity when it doesn't. They're ignoring both data kept by Apple and data available to the server but not stored. They're also spreading misinformation about Android:

iceblock.app/android

Their claims about push notifications on Android compared to iOS are completely false. Both Firebase Cloud Messaging (FCM) and the Apple Push Notification service (APNs) function in a similar way with similar privacy. However, Android does not force using FCM and apps can use other push systems.

iOS forces uses Apple services including getting apps through Apple where they have a record of which apps each person and account has installed and using their push notification service. Both FCM and APNs have tokens. Android doesn't allow apps to access device IDs. Push tokens aren't device IDs.

Apple and Google can identify devices/users based on push tokens obtained by law enforcement from services. Unlike Google, Apple only recently began requiring warrants:

reuters.com/technology/apple-n…

ICEBlock's claims about this are highly inaccurate and they haven't acknowledged corrections.

GrapheneOS (@GrapheneOS@grapheneos.social)

Apple and Google can identify devices/users based on push tokens obtained by law enforcement from services. Unlike Google, Apple only recently began requiring warrants: https://www.reuters.
GrapheneOS Mastodon
in reply to spujb

lemmy - Link to source

spujb 

           MY ANTI DEPRESSANTS JUST KICKED
                 IN ! FANTASTIC !
                   __      _______ ______
                ╱    /\__/\       //     ╲╲
        ______⊂╱    ( ´∇`  )     // ⊃     ||╲ フ 🡖
      ,´__▔▔▔▔╱  ▔╱▔  ⌒▔▔▔▔╱▔▔▔▔ 🡖▔ ▔▔▔▔▔🡖 ▔▔▔▔ |
    ,╱_ _╱   /-o—/ ___ ╱▔▔╱ ___/\  |     ▔ | /\__|
   ,========————´=============/⌒ ╲=/=======||🡖 ||
   | __  |  GAY!  |   __ "    |⌒| |/    ___/|  )╯
   )|🞕|_∈≡≡≡≡≡≡≡≡≡∋__|🞕|"  __|| ╯ ╯__ -‒‒‒‒‒┘  ╯
   ▔╲ ▔╲__╯▔▔▔▔▔▔▔▔三三三▔╲  ╲__╯ ▔▔     三三三三╯
     三三三三三三三三三三三三三三三三三三三三三三三三三三三三
       三三三三三三三三三三三三三三三三三三三三三三三三三三三三

OOP tweet (they explain in this thread that it’s from circa 2012): web.archive.org/web/2022090606…

pastebin archive (mildly unsatisfactory recreation, for example uses the wrong character for the headlights instead of perhaps 日): web.archive.org/web/2023061201…

recreation credit: web.archive.org/web/2022031512…

work of a fellow archivist: web.archive.org/web/2025021621…

have given up looking for older versions to archive but
~~if anyone knows how to search usenet communities that might be where the forum OOP got this from lives~~ actually i’m pretty sure 4-ch.net/dqn/index.html is the forum as it perfectly matches the description—all posts are timestamped 1993-09

cute redraw:

quiet quitting my job at the birthday factory on Twitter

“this image is from 1993”
Twitter
This entry was edited (6 days ago)

lemmy - Link to source

US consultancy firm [Boston Consulting Group] involved in GHF aid scheme modelled plans to 'relocate' Palestinians

US consultancy firm involved in GHF aid scheme modelled plans to 'relocate' Palestinians

A consulting firm involved in the scandal-plagued Gaza Humanitarian Foundation entered into a multimillion-dollar contract to develop the initiative and modelled a plan to "relocate" Palestinians from Gaza as part of its work, a Financial Times inves…
MEE staff (Middle East Eye)

lemmy - Link to source

The spy, private equity baron and ghost of a Trump donor: The revolving door behind a Gaza mercenary firm

The spy, private equity baron and ghost of a Trump donor: The revolving door behind a Gaza mercenary firm

The US mercenary firm overseeing a controversial Gaza aid programme is the creation of a bespectacled Chicago private equity baron and a CIA spy with old ties to a Donald Trump ally who participated in one of the Middle East's nastiest diplomatic rif…
Sean Mathews (Middle East Eye)
in reply to cheese_greater

lemmy - Link to source

grue

It depends on the transit service, and how much their IT people suck. I'm pretty sure there have been multiple attempts to make standardized APIs for this sort of thing, but you shouldn't necessarily expect them to be widely used except maybe in Europe.

Do a web search for "[transit service name] API" and start from there.

Edit: My local transit service apparently publishes a GTFS feed, which may be more widespread than I assumed, but I'm honestly kinda surprised they didn't try to roll their own or something stupid like that.


defines a common format for public transportation schedules and associated geographic information

Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)
This entry was edited (5 days ago)

lemmy - Link to source

BlackRock Halted Ukraine Fund Talks After Trump’s Election Win
archive.ph/xZJXi

BlackRock Halted Ukraine Fund Talks After Trump’s Election Win

BlackRock Inc. halted its search for investors to back a multibillion-dollar Ukraine recovery fund earlier this year after Donald Trump’s election victory saw the US sour on the eastern European country, people familiar with the discussions said.
Jenny Leonard (Bloomberg)

lemmy - Link to source

Wafrn: a tumblr clone that federates with fedi and now also has opt in native bluesky
Hello, its me gabbo the creator of this hellsite. I am totaly not making this post to make sure that lemmy federation works properly
in reply to gabboman

lemmy - Link to source

Angry_Autist (he/him)

Sure would be nice if the fediverse realized that part of what is holding back adoption is your nonsensical gen alpha service names.

don't like this

in reply to Sunshine (she/her)

lemmy - Link to source

pickman_model

Among his lengthy criminal record is a conviction of assault with a weapon from 2013 that Crown argued on Friday is very similar to the 2023 event, where Johnson used his car as a weapon, aiming to hit two men he was angry with, but hit a woman instead, breaking her leg.

Crown noted that since the 2023 incident, Johnson’s violence has continued, with a conviction of assault and obstruction of a police officer in 2025.


This person looks to me more like a threat to the public than anything else.

in reply to Imhotep

lemmy - Link to source

InfiniteGlitch

Bit confused, what would they even do with a report of downvote? Doesn’t make sense.

Plus don’t even understand why someone cares so much about downvoting that they would message you and report it. The upvote/ downvote means seriously nothing. It’s “thin air”.

Put down your device and it has no impact on your live. Continue using Lemmy and it will have no impact on how you use Lemmy.

lemmy - Link to source

Initial feedback on Bazzite 42 NVIDIA Edition (KDE / Plasma 6)

So I've been using it for a week or so, tried some other distros on the side, also tried some very dangerous things like rebasing from KDE to Gnome. I'll present my impressions as lists of good and bad things. Also keep in mind I've been mostly using Gnome in the past, so some of this feedback might be more about KDE / Plasma 6 in general, rather than Bazzite itself.

Bad:
- The most shocking issue I figured only yesterday is that games didn't use my NVIDIA GPU and instead used integrated one, I simply didn't expect NVIDIA edition of gaming-tailored distro could fuck up this, until I tried some heavier games yesterday and checked glxinfo after being unsatisfied by performance - only to find out it was indeed the case, workaround/fix can be found here.
- Transparency and blur work in a rather tricky way and by default blur is set to maximum that makes transparency not visible at all, took me a while to figure this out.
- Aurorae window decoration themes don't support "draw border on maximized and tiled windows" and there are no workaround without doing things that are very unsafe/unstable in context of atomic distro like Bazzite so for the rice I wanted I had to stick with builtin Breeze theme which is old and limited in many ways, I pretty much had to achieve everything with color scheme + panel colorizer alone.
- I don't remember how exactly this happened, but killswitch option in Linux ProtonVPN client somehow got broken in a way that I couldn't connect to internet at all because killswitch was activated and couldn't disable killswitch at the same time, I had to create another user and remove previous one. It also bombarded me with some errors regarding "kdewallet" that I don't understand. Worth noting, I've been using this client with killswitch on many Gnome distros before and never had this issue anywhere else.
- When using external monitor, some apps and games don't perform the same. For example, Blender's viewport feels less smooth/snappy than on internal monitor.
- By default mouse acceleration is on, which makes it feel weird/bad in some games and graphic programs, I believe it makes more sense to have it off by default and I'm not sure why even include that option in gaming-focused distro, I can't imagine anyone wanting to use it. Gaming is all about raw input (imo).
- Builtin terminal is rendered in its own style completely ignoring theming, I didn't like it at all. I was able to install alacritty via rpm-ostree though and it works just fine.

Good:

  • All my favorite windows-only games installed from the first try with zero workarounds. And after fixing the issue with wrong GPU, performance in games is awesome, feels like it might actually be slightly better than on Windows.
  • After discovering panel colorizer and figuring some quirks of Plasma 6 theming, especially in context of immutable distro, I was able to achieve look and feel I'm very happy about.
  • I really like the idea of immutable/atomic distro, and ecosystem for using it here is solid and mature. It feels like system is very safe and bulletproof.
  • Even though it's not recommended but rebasing from KDE to Gnome did work well with maybe some minor issues which I'm not even sure weren't just Gnome issues. In the end I didn't like Gnome version more than KDE one and decided to clean up my partitions and reinstalled KDE version again.
  • I also briefly checked some alternative distros like Nobara, but nothing impressed me more than Bazzite.
  • Volume and brightness controls, bluetooth, network manager, disks utility, and after some tweaking dolphin - everything works smooth, everything supports scenarios I want to use, and most of those feel better and more advanced than Windows or Gnome alternatives.
  • Builtin ujust utility is neat and has a lot of optional tools installable in one command, like "ujust bazzite-cli", which installs and intergrates other utilities like atuin, fzf, ripgrep.
  • I feel rather happy about it now, and I don't expect it to break anytime soon or have any major issues for me. Time will tell though.

NVIDIA GPU not being used (Bazzite 41 NVIDIA Edition)

I had the same problem on my system with AMD Ryzen 5 7600 NVIDIA GeForce RTX 3060 I solved the it by first following Secure Boot Instructions - Bazzite Documentation to enroll the NVIDIA driver & KMOD signing key for secure boot and then creating …
Universal Blue
in reply to hisao

lemmy - Link to source

HayadSont

I don’t remember how exactly this happened, but killswitch option in Linux ProtonVPN client somehow got broken in a way that I couldn’t connect to internet at all because killswitch was activated and couldn’t disable killswitch at the same time, I had to create another user and remove previous one. It also bombarded me with some errors regarding “kdewallet” that I don’t understand. Worth noting, I’ve been using this client with killswitch on many Gnome distros before and never had this issue anywhere else.


FWIW, the thing with killswitch it not due to Bazzite, nor KDE. There's a f*ck load of user reports all over the internet with different systems that have experienced the same thing; e.g. this one by a GNOME user on Pop!_OS. As for your criticism on kdewallet, I was also bothered by it the last few times I engaged with KDE Plasma. I suppose I was doing something wrong. Regardless, it was an unpleasant experience.

Reddit - The heart of the internet

www.reddit.com
in reply to HayadSont

lemmy - Link to source

hisao

FWIW, the thing with killswitch it not due to Bazzite, nor KDE. There’s a f*ck load of user reports all over the internet with different systems that have experienced the same thing; e.g. this one by a GNOME user on Pop!_OS.


My bad, so it's probably ProtonVPN client doing tricky hidden things that can break.

As for your criticism on kdewallet, I was also bothered by it the last few times I engaged with KDE Plasma.


I also got a kdewallet problem with flatpak VS Code authenticating to github, but that one is so widely known, they even included guidelines in docs on how to solve it.

in reply to LadyButterfly

lemmy - Link to source

cheese_greater

All of these things can be helped by using a tracking app that projects all your balances and recalculates every time you put in more information or you simulate various choices you're about to pull the trigger on. You will get instant feedback and see how it screws up your bills money and hopefully learn to heat that feeling so its not such an active effort to stick to the plan ans go with the flow

lemmy - Link to source

What is the supposed workflow for vanilla Gnome for keyboard users?

Question is in the title: What is the supposed workflow for vanilla Gnome for keyboard users?

Is there any video/design documents which explain, how the workflow is supposed to be?

Assume, I have a full screen web browser on workspace 1. Now I want to have a terminal... I hit the super-key, type terminal, hit enter ... and then I have a terminal which does not start maximized on workspace 1, so I can either maximize the terminal and switch between the applications, arrange them side by side... or I can navigate to workspace 2, start the terminal there (the terminal will not start maximized again on an empty workspace 2) ... and switch between the two workspaces (AFAIK there are no hotkeys specified by default to navigate directly to a workspace)...

What I simply do not understand: Does the vanilla Gnome workflow expect you to use mouse and keyboard? Like hit super, use mouse to go to next workspace, type terminal, click to maximize terminal (or use super-up)?

It just seems like a lot of work/clicks/keys to achieve something simple. And to my understanding Gnome expects you to use basically every application with a full screen window anyway, so why does it not open a new application on the next free workspace full screen by default?

in reply to wolf

lemmy - Link to source

hello_hello [comrade/them]

Keyboard -> Keyboard shortcuts from Settings will show all the available keyboard shortcuts. You can also create your own custom keybindings

These seem like a lot of personal design complaints rather than actual issues with GNOME itself.

And to my understanding Gnome expects you to use basically every application with a full screen window anyway


You misunderstood, that's not what GNOME expects at all. Your app not maximizing on startup is because the app doesn't maximize on startup. GNOME doesn't have a setting to maximize all apps by default since that should be the app's responsibility.

If you want the auto-tiling window manager experience, you'll need to install an extension (Paperwm, tiling shell, Forge, Pop shell). Extensions are like applications, there's no shame in using them.

This entry was edited (3 days ago)

lemmy - Link to source

Moving to the US in the worst of times…
I’m a teen from Turkey. I’m moving to the US at the end of this month with my mom to live with her fiancé, so we’re going on a K-1 visa. He lives in Los Angeles County. I’ve been following the news regularly and I’d be lying if I said I wasn’t nervous by what’s happening in the country these days… such a bad time to move there.
in reply to Pro

lemmy - Link to source

confusedpuppy

Last month I spent most of my time writing a long and complex rsync script and was looking for something like this. I skimmed threw a few articles already and I've already found a bunch of things that I thought about adding but had difficulties finding before while I was writing the script.

The script I wrote is fully functional but I had already planned to revisit and rewrite parts of it because I enjoy knowing my script is solid, simple and reliable. But right now I have a couple other goals I want to finish before returning to my script.

This resource has lots to add on top of what I already learned.

lemmy - Link to source

‘The vehicle suddenly accelerated with our baby in it’: the terrifying truth about why Tesla’s cars keep crashing
It was a Monday afternoon in June 2023 when Rita Meier, 45, joined us for a video call. Meier told us about the last time she said goodbye to her husband, Stefan, five years earlier. He had been leaving their home near Lake Constance, Germany, heading for a trade fair in Milan.

Meier recalled how he hesitated between taking his Tesla Model S or her BMW. He had never driven the Tesla that far before. He checked the route for charging stations along the way and ultimately decided to try it. Rita had a bad feeling. She stayed home with their three children, the youngest less than a year old.

At 3.18pm on 10 May 2018, Stefan Meier lost control of his Model S on the A2 highway near the Monte Ceneri tunnel. Travelling at about 100kmh (62mph), he ploughed through several warning markers and traffic signs before crashing into a slanted guardrail. “The collision with the guardrail launches the vehicle into the air, where it flips several times before landing,” investigators would write later.

The car came to rest more than 70 metres away, on the opposite side of the road, leaving a trail of wreckage. According to witnesses, the Model S burst into flames while still airborne. Several passersby tried to open the doors and rescue the driver, but they couldn’t unlock the car. When they heard explosions and saw flames through the windows, they retreated. Even the firefighters, who arrived 20 minutes later, could do nothing but watch the Tesla burn.

At that moment, Rita Meier was unaware of the crash. She tried calling her husband, but he didn’t pick up. When he still hadn’t returned her call hours later – highly unusual for this devoted father – she attempted to track his car using Tesla’s app. It no longer worked. By the time police officers rang her doorbell late that night, Meier was already bracing for the worst.

Customers described their cars suddenly accelerating or braking hard. Some escaped with a scare; others ended up in ditches

The crash made headlines the next morning as one of the first fatal Tesla accidents in Europe. Tesla released a statement to the press saying the company was “deeply saddened” by the incident, adding, “We are working to gather all the facts in this case and are fully cooperating with local authorities.”

To this day, Meier still doesn’t know why her husband died. She has kept everything the police gave her after their inconclusive investigation. The charred wreck of the Model S sits in a garage Meier rents specifically for that purpose. The scorched phone – which she had forensically analysed at her own expense, to no avail – sits in a drawer at home. Maybe someday all this will be needed again, she says. She hasn’t given up hope of uncovering the truth.

Rita Meier was one of many people who reached out to us after we began reporting on the Tesla Files – a cache of 23,000 leaked documents and 100 gigabytes of confidential data shared by an anonymous whistleblower. The first report we published looked at problems with Tesla’s autopilot system, which allows the cars to temporarily drive on their own, taking over steering, braking and acceleration. Though touted by the company as “Full Self-Driving” (FSD), it is designed to assist, not replace, the driver, who should keep their eyes on the road and be ready to intervene at any time.

Autonomous driving is the core promise around which Elon Musk has built his company. Tesla has never delivered a truly self-driving vehicle, yet the richest person in the world keeps repeating the claim that his cars will soon drive entirely without human help. Is Tesla’s autopilot really as advanced as he says?

The Tesla Files suggest otherwise. They contain more than 2,400 customer complaints about unintended acceleration and more than 1,500 braking issues – 139 involving emergency braking without cause, and 383 phantom braking events triggered by false collision warnings. More than 1,000 crashes are documented. A separate spreadsheet on driver-assistance incidents where customers raised safety concerns lists more than 3,000 entries. The oldest date from 2015, the most recent from March 2022. In that time, Tesla delivered roughly 2.6m vehicles with autopilot software. Most incidents occurred in the US, but there have also been complaints from Europe and Asia. Customers described their cars suddenly accelerating or braking hard. Some escaped with a scare; others ended up in ditches, crashing into walls or colliding with oncoming vehicles. “After dropping my son off in his school parking lot, as I go to make a right-hand exit it lurches forward suddenly,” one complaint read. Another said, “My autopilot failed/malfunctioned this morning (car didn’t brake) and I almost rear-ended somebody at 65mph.” A third reported, “Today, while my wife was driving with our baby in the car, it suddenly accelerated out of nowhere.”

Braking for no reason caused just as much distress. “Our car just stopped on the highway. That was terrifying,” a Tesla driver wrote. Another complained, “Frequent phantom braking on two-lane highways. Makes the autopilot almost unusable.” Some report their car “jumped lanes unexpectedly”, causing them to hit a concrete barrier, or veered into oncoming traffic.

Musk has given the world many reasons to criticise him since he teamed up with Donald Trump. Many people do – mostly by boycotting his products. But while it is one thing to disagree with the political views of a business leader, it is another to be mortally afraid of his products. In the Tesla Files, we found thousands of examples of why such fear may be justified.
Illustration of bashed up and burned cars in a car park
‘My husband died in an unexplained accident. And no one cared.’ Illustration: Carl Godfrey/The Guardian

We set out to match some of these incidents of autopilot errors with customers’ names. Like hundreds of other Tesla customers, Rita Meier entered the vehicle identification number of her husband’s Model S into the response form we published on the website of the German business newspaper Handelsblatt, for which we carried out our investigation. She quickly discovered that the Tesla Files contained data related to the car. In her first email to us, she wrote, “You can probably imagine what it felt like to read that.”

There isn’t much information – just an Excel spreadsheet titled “Incident Review”. A Tesla employee noted that the mileage counter on Stefan Meier’s car stood at 4,765 miles at the time of the crash. The entry was catalogued just one day after the fatal accident. In the comment field was written, “Vehicle involved in an accident.” The cause of the crash remains unknown to this day. In Tesla’s internal system, a company employee had marked the case as “resolved”, but for five years, Rita Meier had been searching for answers. After Stefan’s death, she took over the family business – a timber company with 200 employees based in Tettnang, Baden-Württemberg. As journalists, we are used to tough interviews, but this one was different. We had to strike a careful balance – between empathy and the persistent questioning good reporting demands. “Why are you convinced the Tesla was responsible for your husband’s death?” we asked her. “Isn’t it possible he was distracted – maybe looking at his phone?”

No one knows for sure. But Meier was well aware that Musk has previously claimed Tesla “releases critical crash data affecting public safety immediately and always will”; that he has bragged many times about how its superior handling of data sets the company apart from its competitors. In the case of her husband, why was she expected to believe there was no data?

Meier’s account was structured and precise. Only once did the toll become visible – when she described how her husband’s body burned in full view of the firefighters. Her eyes filled with tears and her voice cracked. She apologised, turning away. After she collected herself, she told us she has nothing left to gain – but also nothing to lose. That was why she had reached out to us. We promised to look into the case.

Rita Meier wasn’t the only widow to approach us. Disappointed customers, current and former employees, analysts and lawyers were sharing links to our reporting. Many of them contacted us. More than once, someone wrote that it was about time someone stood up to Tesla – and to Elon Musk.

Meier, too, shared our articles and the callout form with others in her network – including people who, like her, lost loved ones in Tesla crashes. One of them was Anke Schuster. Like Meier, she had lost her husband in a Tesla crash that defies explanation and had spent years chasing answers. And, like Meier, she had found her husband’s Model X listed in the Tesla Files. Once again, the incident was marked as resolved – with no indication of what that actually meant.

“My husband died in an unexplained and inexplicable accident,” Schuster wrote in her first email. Her dealings with police, prosecutors and insurance companies, she said, had been “hell”. No one seemed to understand how a Tesla works. “I lost my husband. His four daughters lost their father. And no one ever cared.”

Her husband, Oliver, was a tech enthusiast, fascinated by Musk. A hotelier by trade, he owned no fewer than four Teslas. He loved the cars. She hated them – especially the autopilot. The way the software seemed to make decisions on its own never sat right with her. Now, she felt as if her instincts had been confirmed in the worst way.

We uncovered an ominous black box in which every byte of customer data was collected – and sealed off from public scrutiny

Oliver Schuster was returning from a business meeting on 13 April 2021 when his black Model X veered off highway B194 between Loitz and Schönbeck in north-east Germany. It was 12.50pm when the car left the road and crashed into a tree. Schuster started to worry when her husband missed a scheduled bank appointment. She tried to track the vehicle but found no way to locate it. Even calling Tesla led nowhere. That evening, the police broke the news: after the crash her husband’s car had burst into flames. He had burned to death – with the fire brigade watching helplessly.

The crashes that killed Meier’s and Schuster’s husbands were almost three years apart but the parallels were chilling. We examined accident reports, eyewitness accounts, crash-site photos and correspondence with Tesla. In both cases, investigators had requested vehicle data from Tesla, and the company hadn’t provided it. In Meier’s case, Tesla staff claimed no data was available. In Schuster’s, they said there was no relevant data.

Over the next two years, we spoke with crash victims, grieving families and experts around the world. What we uncovered was an ominous black box – a system designed not only to collect and control every byte of customer data, but to safeguard Musk’s vision of autonomous driving. Critical information was sealed off from public scrutiny.

Elon Musk is a perfectionist with a tendency towards micromanagement. At Tesla, his whims seem to override every argument – even in matters of life and death. During our reporting, we came across the issue of door handles. On Teslas, they retract into the doors while the cars are being driven. The system depends on battery power. If an airbag deploys, the doors are supposed to unlock automatically and the handles extend – at least, that’s what the Model S manual says.

The idea for the sleek, futuristic design stems from Musk himself. He insisted on retractable handles, despite repeated warnings from engineers. Since 2018, they have been linked to at least four fatal accidents in Europe and the US, in which five people died.

In February 2024, we reported on a particularly tragic case: a fatal crash on a country road near Dobbrikow, in Brandenburg, Germany. Two 18-year-olds were killed when the Tesla they were in slammed into a tree and caught fire. First responders couldn’t open the doors because the handles were retracted. The teenagers burned to death in the back seat.

A court-appointed expert from Dekra, one of Germany’s leading testing authorities, later concluded that, given the retracted handles, the incident “qualifies as a malfunction”. According to the report, “the failure of the rear door handles to extend automatically must be considered a decisive factor” in the deaths. Had the system worked as intended, “it is assumed that rescuers might have been able to extract the two backseat passengers before the fire developed further”. Without what the report calls a “failure of this safety function”, the teens might have survived.
'I feel like I'm in the movies': malfunctioning robotaxi traps passenger in car – video

Our investigation made waves. The Kraftfahrt-Bundesamt, Germany’s federal motor transport authority, got involved and announced plans to coordinate with other regulatory bodies to revise international safety standards. Germany’s largest automobile club, ADAC, issued a public recommendation that Tesla drivers should carry emergency window hammers. In a statement, ADAC warned that retractable door handles could seriously hinder rescue efforts. Even trained emergency responders, it said, may struggle to reach trapped passengers. Tesla shows no intention of changing the design.

That’s Musk. He prefers the sleek look of Teslas without handles, so he accepts the risk to his customers. His thinking, it seems, goes something like this: at some point, the engineers will figure out a technical fix. The same logic applies to his grander vision of autonomous driving: because Musk wants to be first, he lets customers test his unfinished Autopilot system on public roads. It’s a principle borrowed from the software world, where releasing apps in beta has long been standard practice. The more users, the more feedback and, over time – often years – something stable emerges. Revenue and market share arrive much earlier. The motto: if you wait, you lose.

Musk has taken that mindset to the road. The world is his lab. Everyone else is part of the experiment.

By the end of 2023, we knew a lot about how Musk’s cars worked – but the way they handle data still felt like a black box. How is that data stored? At what moment does the onboard computer send it to Tesla’s servers? We talked to independent experts at the Technical University Berlin. Three PhD candidates – Christian Werling, Niclas Kühnapfel and Hans Niklas Jacob – made headlines for hacking Tesla’s autopilot hardware. A brief voltage drop on a circuit board turned out to be just enough to trick the system into opening up.

The security researchers uncovered what they called “Elon Mode” – a hidden setting in which the car drives fully autonomously, without requiring the driver to keep his hands on the wheel. They also managed to recover deleted data, including video footage recorded by a Tesla driver. And they traced exactly what data Tesla sends to its servers – and what it doesn’t.

The hackers explained that Tesla stores data in three places. First, on a memory card inside the onboard computer – essentially a running log of the vehicle’s digital brain. Second, on the event data recorder – a black box that captures a few seconds before and after a crash. And third, on Tesla’s servers, assuming the vehicle uploads them.

The researchers told us they had found an internal database embedded in the system – one built around so-called trigger events. If, for example, the airbag deploys or the car hits an obstacle, the system is designed to save a defined set of data to the black box – and transmit it to Tesla’s servers. Unless the vehicles were in a complete network dead zone, in both the Meier and Schuster cases, the cars should have recorded and transmitted that data.
Illustration of bashed up and burned cars in a car park
‘Is the car driving erratically by itself normal? Yeah, that happens every now and then.’ Illustration: Carl Godfrey/The Guardian

Who in the company actually works with that data? We examined testimony from Tesla employees in court cases related to fatal crashes. They described how their departments operate. We cross-referenced their statements with entries in the Tesla Files. A pattern took shape: one team screens all crashes at a high level, forwarding them to specialists – some focused on autopilot, others on vehicle dynamics or road grip. There’s also a group that steps in whenever authorities request crash data.

We compiled a list of employees relevant to our reporting. Some we tried to reach by email or phone. For others, we showed up at their homes. If they weren’t there, we left handwritten notes. No one wanted to talk.

We searched for other crashes. One involved Hans von Ohain, a 33-year-old Tesla employee from Evergreen, Colorado. On 16 May 2022, he crashed into a tree on his way home from a golf outing and the car burst into flames. Von Ohain died at the scene. His passenger survived and told police that von Ohain, who had been drinking, had activated Full Self-Driving. Tesla, however, said it couldn’t confirm whether the system was engaged – because no vehicle data was transmitted for the incident.

Then, in February 2024, Musk himself stepped in. The Tesla CEO claimed von Ohain had never downloaded the latest version of the software – so it couldn’t have caused the crash. Friends of von Ohain, however, told US media he had shown them the system. His passenger that day, who barely escaped with his life, told reporters that hours earlier the car had already driven erratically by itself. “The first time it happened, I was like, ‘Is that normal?’” he recalled asking von Ohain. “And he was like, ‘Yeah, that happens every now and then.’”

His account was bolstered by von Ohain’s widow, who explained to the media how overjoyed her husband had been at working for Tesla. Reportedly, von Ohain received the Full Self-Driving system as a perk. His widow explained how he would use the system almost every time he got behind the wheel: “It was jerky, but we were like, that comes with the territory of new technology. We knew the technology had to learn, and we were willing to be part of that.”

The Colorado State Patrol investigated but closed the case without blaming Tesla. It reported that no usable data was recovered.

For a company that markets its cars as computers on wheels, Tesla’s claim that it had no data available in all these cases is surprising. Musk has long described Tesla vehicles as part of a collective neural network – machines that continuously learn from one another. Think of the Borg aliens from the Star Trek franchise. Musk envisions his cars, like the Borg, as a collective – operating as a hive mind, each vehicle linked to a unified consciousness.

When a journalist asked him in October 2015 what made Tesla’s driver-assistance system different, he replied, “The whole Tesla fleet operates as a network. When one car learns something, they all learn it. That is beyond what other car companies are doing.” Every Tesla driver, he explained, becomes a kind of “expert trainer for how the autopilot should work”.

According to Musk, the eight cameras in every Tesla transmit more than 160bn video frames a day to the company’s servers. In its owner’s manual, Tesla states that its cars may collect even more: “analytics, road segment, diagnostic and vehicle usage data”, all sent to headquarters to improve product quality and features such as autopilot. The company claims it learns “from the experience of billions of miles that Tesla vehicles have driven”.
‘Lidar is lame’: why Elon Musk’s vision for a self-driving Tesla taxi faltered
Read more

It is a powerful promise: a fleet of millions of cars, constantly feeding raw information into a gargantuan processing centre. Billions – trillions – of data points, all in service of one goal: making cars drive better and keeping drivers safe. At the start of this year, Musk got a chance to show the world what he meant.

On 1 January 2025, at 8.39am, a Tesla Cybertruck exploded outside the Trump International Hotel Las Vegas. The man behind the incident – US special forces veteran Matthew Livelsberger – had rented the vehicle, packed it with fireworks, gas canisters and grenades, and parked it in front of the building. Just before the explosion, he shot himself in the head with a .50 calibre Desert Eagle pistol. “This was not a terrorist attack, it was a wakeup call. Americans only pay attention to spectacles and violence,” Livelsberger wrote in a letter later found by authorities. “What better way to get my point across than a stunt with fireworks and explosives.”

The soldier miscalculated. Seven bystanders suffered minor injuries. The Cybertruck was destroyed, but not even the windows of the hotel shattered. Instead, with his final act, Livelsberger revealed something else entirely: just how far the arm of Tesla’s data machinery can reach. “The whole Tesla senior team is investigating this matter right now,” Musk wrote on X just hours after the blast. “Will post more information as soon as we learn anything. We’ve never seen anything like this.”

Later that day, Musk posted again. Tesla had already analysed all relevant data – and was ready to offer conclusions. “We have now confirmed that the explosion was caused by very large fireworks and/or a bomb carried in the bed of the rented Cybertruck and is unrelated to the vehicle itself,” he wrote. “All vehicle telemetry was positive at the time of the explosion.”

Suddenly, Musk wasn’t just a CEO; he was an investigator. He instructed Tesla technicians to remotely unlock the scorched vehicle. He handed over internal footage captured up to the moment of detonation.The Tesla CEO had turned a suicide attack into a showcase of his superior technology.

Yet there were critics even in the moment of glory. “It reveals the kind of sweeping surveillance going on,” warned David Choffnes, executive director of the Cybersecurity and Privacy Institute at Northeastern University in Boston, when contacted by a reporter. “When something bad happens, it’s helpful, but it’s a double-edged sword. Companies that collect this data can abuse it.”
Illustration of bashed up and burned cars in a car park
‘In many crashes, investigators weren’t even aware that requesting data from Tesla was an option.’ Illustration: Carl Godfrey/The Guardian

There are other examples of what Tesla’s data collection makes possible. We found the case of David and Sheila Brown, who died in August 2020 when their Model 3 ran a red light at 114mph in Saratoga, California. Investigators managed to reconstruct every detail, thanks to Tesla’s vehicle data. It shows exactly when the Browns opened a door, unfastened a seatbelt, and how hard the driver pressed the accelerator – down to the millisecond, right up to the moment of impact. Over time, we found more cases, more detailed accident reports. The data definitely is there – until it isn’t.

In many crashes when Teslas inexplicably veered off the road or hit stationary objects, investigators didn’t actually request data from the company. When we asked authorities why, there was often silence. Our impression was that many prosecutors and police officers weren’t even aware that asking was an option. In other cases, they acted only when pushed by victims’ families.

In the Meier case, Tesla told authorities, in a letter dated 25 June 2018, that the last complete set of vehicle data was transmitted nearly two weeks before the crash. The only data from the day of the accident was a “limited snapshot of vehicle parameters” – taken “approximately 50 minutes before the incident”. However, this snapshot “doesn’t show anything in relation to the incident”. As for the black box, Tesla warned that the storage modules were likely destroyed, given the condition of the burned-out vehicle. Data transmission after a crash is possible, the company said – but in this case, it didn’t happen. In the end, investigators couldn’t even determine whether driver-assist systems were active at the time of the crash.

The Schuster case played out similarly. Prosecutors in Stralsund, Germany, were baffled. The road where the crash happened is straight, the asphalt was dry and the weather at the time of the accident was clear. Anke Schuster kept urging the authorities to examine Tesla’s telemetry data.

Every road user trusts the cars around them not to be a threat. Does that trust still stand when a car is driving itself?

When prosecutors did formally request the data recorded by Schuster’s car on the day of the crash, it took Tesla more than two weeks to respond – and when it did, the answer was both brief and bold. The company didn’t say there was no data. It said that there was “no relevant data”. The authorities’ reaction left us stunned. We expected prosecutors to push back – to tell Tesla that deciding what’s relevant is their job, not the company’s. But they didn’t. Instead, they closed the case.

The hackers from TU Berlin pointed us to a study by the Netherlands Forensic Institute, an independent division of the ministry of justice and security. In October 2021, the NFI published findings showing it had successfully accessed the onboard memories of all major Tesla models. The researchers compared their results with accident cases in which police had requested data from Tesla. Their conclusion was that while Tesla formally complied with those requests, it omitted large volumes of data that might have proved useful.

Tesla’s credibility took a further hit in a report released by the US National Highway Traffic Safety Administration in April 2024. The agency concluded that Tesla failed to adequately monitor whether drivers remain alert and ready to intervene while using its driver-assist systems. It reviewed 956 crashes, field data and customer communications, and pointed to “gaps in Tesla’s telematic data” that made it impossible to determine how often autopilot was active during crashes. If a vehicle’s antenna was damaged or it crashed in an area without network coverage, even serious accidents sometimes went unreported. Tesla’s internal statistics include only those crashes in which an airbag or other pyrotechnic system deployed – something that occurs in just 18% of police-reported cases. This means that the actual accident rate is significantly higher than Tesla discloses to customers and investors.

There’s more. Two years prior, the NHTSA had flagged something strange – something suspicious. In a separate report, it documented 16 cases in which Tesla vehicles crashed into stationary emergency vehicles. In each, autopilot disengaged “less than one second before impact” – far too little time for the driver to react. Critics warn that this behaviour could allow Tesla to argue in court that autopilot was not active at the moment of impact, potentially dodging responsibility.

The YouTuber Mark Rober, a former engineer at Nasa, replicated this behaviour in an experiment on 15 March 2025. He simulated a range of hazardous situations, in which the Model Y performed significantly worse than a competing vehicle. The Tesla repeatedly ran over a crash-test dummy without braking. The video went viral, amassing more than 14m views within a few days.
Mark Rober’s Tesa test drive

The real surprise came after the experiment. Fred Lambert, who writes for the blog Electrek, pointed out the same autopilot disengagement that the NHTSA had documented. “Autopilot appears to automatically disengage a fraction of a second before the impact as the crash becomes inevitable,” Lambert noted.

And so the doubts about Tesla’s integrity pile up. In the Tesla Files, we found emails and reports from a UK-based engineer who led Tesla’s Safety Incident Investigation programme, overseeing the company’s most sensitive crash cases. His internal memos reveal that Tesla deliberately limited documentation of particular issues to avoid the risk of this information being requested under subpoena. Although he pushed for clearer protocols and better internal processes, US leadership resisted – explicitly driven by fears of legal exposure.

We contacted Tesla multiple times with questions about the company’s data practices. We asked about the Meier and Schuster cases – and what it means when fatal crashes are marked “resolved” in Tesla’s internal system. We asked the company to respond to criticism from the US traffic authority and to the findings of Dutch forensic investigators. We also asked why Tesla doesn’t simply publish crash data, as Musk once promised to do, and whether the company considers it appropriate to withhold information from potential US court orders. Tesla has not responded to any of our questions.

Elon Musk boasts about the vast amount of data his cars generate – data that, he claims, will not only improve Tesla’s entire fleet but also revolutionise road traffic. But, as we have witnessed again and again in the most critical of cases, Tesla refuses to share it.

Tesla’s handling of crash data affects even those who never wanted anything to do with the company. Every road user trusts the car in front, behind or beside them not to be a threat. Does that trust still stand when the car is driving itself?

Internally, we called our investigation into Tesla’s crash data Black Box. At first, because it dealt with the physical data units built into the vehicles – so-called black boxes. But the devices Tesla installs hardly deserve the name. Unlike the flight recorders used in aviation, they’re not fireproof – and in many of the cases we examined, they proved useless.

Over time, we came to see that the name held a second meaning. A black box, in common parlance, is something closed to the outside. Something opaque. Unknowable. And while we’ve gained some insight into Tesla as a company, its handling of crash data remains just that: a black box. Only Tesla knows how Elon Musk’s vehicles truly work. Yet today, more than 5m of them share our roads.

Some names have been changed.

This is an edited extract from The Tesla Files by Sönke Iwersen and Michael Verfürden, published on 24 July by Penguin Michael Joseph at £22. To support the Guardian, order your copy at guardianbookshop.com. Delivery charges may apply.


‘The vehicle suddenly accelerated with our baby in it’: the terrifying truth about why Tesla’s cars keep crashing

Elon Musk is obsessive about the design of his supercars, right down to the disappearing door handles.
Guardian staff reporter (The Guardian)

lemmy - Link to source

How do you safely film a group of masked armed men while they are in the process of committing a crime, without them knowing that you are recording? [USA]

For Context: theguardian.com/us-news/2025/j…

How to document these events safely?


US man arrested while filming Home Depot Ice raid sues government for $1m

Photographer Job Garcia, a US citizen, seeks recompense after reportedly being tackled and thrown to the ground
José Olivares (The Guardian)

lemmy - Link to source

Christopher Street Day in Köln: Das mulmige Gefühl bleibt
Vermehrt greifen Rechtsextreme queere Veranstaltungen an. Der CSD in Köln hat auch deshalb ein striktes Sicherheitskonzept erarbeitet. Die Teilnehmenden wollen sich nicht einschüchtern lassen - das fällt ihnen aber zunehmend schwerer.

Christopher Street Day in Köln: Das mulmige Gefühl bleibt

Vermehrt greifen Rechtsextreme queere Events an. Der CSD in Köln hat ein striktes Sicherheitskonzept erarbeitet. Die Teilnehmenden wollen sich nicht einschüchtern lassen - das fällt aber immer schwerer.
tagesschau.de

lemmy - Link to source

Anyone else hear about this Canadian Facebook alternative
I just found this when looking for Canadian alternatives.
Anyone else hear about gander? I'm doing my best to support home grown and open alternatives but I have to choose what I am doing on the platform.
It's unlikely that my older family will ever leave Facebook, but honestly, what do I miss by not being present there? Birthday posts on my wall and the latest vacation picture...

Gander: The Social Media You Want, Built for Canada

Fun, private, and ethical. We're changing the way social media is done around here, all without your personal data taking an unexpected trip down south.
Gander Social

lemmy - Link to source

The sign says Saugeen Beach but a Supreme Court of Canada challenge looms in land dispute
The day lawyers submitted paperwork to the Supreme Court of Canada, another group quietly set up ladders in the dead of night to change a sign symbolic in a decades-long legal dispute in an Ontario beach town.

The red retro-lettered sign at the end of Main Street in the town of South Bruce Peninsula read "Welcome to Saugeen Beach" when sun seekers woke up on Canada Day this week to look out at Lake Huron.

The sign had previously ushered people to "Sauble Beach," a tourist hotspot since the 1920s. Sporting restaurants and cottages, and town and private land are squeezed between two sections of reserve territory belonging to Chippewas of Saugeen First Nation.

The band declared victory at the end of 2024 when the Ontario Court of Appeal sided with Saugeen First Nation, saying the federal government had breached the treaty it signed in 1854. It ruled that roughly 2.2 kilometres of shoreline land incorrectly surveyed in 1855 should be returned to the First Nation.

in reply to HellsBelle

lemmy - Link to source

Peppycito

No mention of the fact the it was the Saugeen Peninsula long before it became the Bruce Peninsula. Or that Queen Vicky declared the Saugeen Peninsula the property of the Saugeen people "in perpetuity" to reward their service in the war of 1812. Or that the federal government has tried to lay all this on the Town of South Bruce Peninsula which didn't exist in any form when the treaties were written. Or that a previous council had good relations with SON and were working on a deal before the racist hicks in the area elected a bunch of shit heads that launched decades of legal fights to the tune of something like $6 million.

Them changing the sign in the middle of the night on Canada day eve is the funniest thing ever. Good on them for the brilliant idea and excellent execution.

The next lawsuit will be the band suing the town when the beach gets closed for poor water quality because everyone over there shits in a hole in the sand and it all trickles out into the lake.

lemmy - Link to source

Explore the emergency room closures in your area with our interactive map

cross-posted from: rss.ponder.cat/post/222240

This project aims to document every instance in which a hospital emergency department (ER) in Canada closed its doors – temporarily or permanently – since 2019. For each closure, The Globe and Mail captured the ER’s name, start and end times, and the reason for the disruption.

Explore the interactive map below to browse ER closures across Canada, as compiled by The Globe and Mail.

From The Globe and Mail via this RSS feed


Canadian ERs closed their doors for at least 1.14 million hours since 2019, records show

A Globe investigation finds burnout since the onset of the pandemic has led to hospital staff shortages across the country, with rural communities hit the hardest
Kelly Grant (The Globe and Mail)

lemmy - Link to source

Poilievre's Wife Wants Us to Consider Banging Less? Tradwives and Conservative Women's Media

Poilievre's wife wants us to consider banging less? Tradwives and conservative women's media

Pierre Poilievre’s wife has a question for you: has society become too promiscuous?To hear her tell it, women should “stop pretending that more s*x equals mo...
YouTube

lemmy - Link to source

[2025] Canvas in ONE WEEK

it's time to get hyped!

July 12th, 2025 @ 4am UTC


you can now open the Canvas to setup your templates and preview how it's going to work!

2025 Canvas Size: 500x500

Related posts:



what is Canvas?


Canvas is a collaborative pixel canvas that includes everyone apart of the Fediverse! Any fediverse platform that supports direct messages is able to login and participate for this 48 hour live event

socials


Matrix - Decentralised and secure communication

You're invited to talk on Matrix. If you don't already have a client this link will help you pick one, and join the conversation. If you already have one, this link will help you join the conversation
matrix.to

don't like this

in reply to Eager Eagle

lemmy - Link to source

just_another_person

Because they choose not to go full idiot though. They could make their top-line cards to compete if they slam enough into a pipeline and require a dedicated PSU to compete, but that's not where their product line intends to go. That's why it's smart.

For reference: AMD has the most deployed GPUs on the planet as of right now. There's a reason why it's in every gaming console except Switch 1/2, and why OpenAI just partnered with them for chips. The goal shouldn't just making a product that churns out results at the cost of everything else does, but to be cost-effective and efficient. Nvidia fails at that on every level.

in reply to Eager Eagle

lemmy - Link to source

just_another_person

Actually...not true. Nvidia recently became bigger in the DC because of their terrible inference cards being bought up, but AMD overtook Intel on chips with all major cloud platforms last year, and their Xilinix chips are slowly overtaking the sales of regular CPUs for special purposes processing. By the end of this year, I bet AMD will be the most deployed brand in datacenters globally. FPGA is the only path forward in the architecture world at this point for speed and efficiency in single-purpose processing. Nvidia doesn't have a competing product.
in reply to just_another_person

lemmy - Link to source

tormeh

If you're on Windows it's hard to recommend anything else. Nvidia has DLSS supported in basically every game. For recent games there's the new transformer DLSS. Add to that ray reconstruction, superior ray tracing, and a steady stream of new features. That's the state of the art, and if you want it you gotta pay Nvidia. AMD is about 4 years behind Nvidia in terms of features. Intel is not much better. The people who really care about advancements in graphics and derive joy from that are all going to buy Nvidia because there's no competition.
in reply to FreedomAdvocate

lemmy - Link to source

just_another_person

Low rent comment.

First: corsair.com/us/en/explorer/gam…

Second: you apparently are unaware, so just search up the phrase, but as this article very clearly explains...it's shit. It's not innovative, interesting, or improving performance, it's a marketing scam. Games would be run better and more efficiently if you just lower the requirements. It's like saying you want food to taste better, but then they serve you a vegan version of it. AMD's version is technically more useful, but it's still a dumb trick.


RTX 5090, 5080, and 5070 series GPUs: Everything you need to know

The new GPUs from NVIDIA have been announced and are on their way. Here's the lowdown on the 5090, 5080, 5070 Ti, and 5070.
Corsair Gaming (www.corsair.com)
in reply to just_another_person

lemmy - Link to source

FreedomAdvocate

First: corsair.com/us/en/explorer/gam…


What exactly am I supposed to be looking at here? Do you think that says that the GPUs need their own PSUs? Do you think people with 50 series GPUs have 2 PSUs in their computers?

It’s not innovative, interesting, or improving performance, it’s a marketing scam. Games would be run better and more efficiently if you just lower the requirements.


DLSS isn't innovative? It's not improving performance? What on earth? Rendering a frame at a lower resolution and then using AI to upscale it to look the same or better than rendering it at full resolution isn't innovative?! Getting an extra 30fps vs native resolution isn't improving performance?! How isn't it?

You can't just "lower the requirements" lol. What you're suggesting is make the game worse so people with worse hardware can play at max settings lol. That is absolutely absurd.

Let me ask you this - do you think that every new game should still be being made for the PS2? PS3? Why or why not?


RTX 5090, 5080, and 5070 series GPUs: Everything you need to know

The new GPUs from NVIDIA have been announced and are on their way. Here's the lowdown on the 5090, 5080, 5070 Ti, and 5070.
Corsair Gaming (www.corsair.com)
in reply to FreedomAdvocate

lemmy - Link to source

just_another_person

Like I said...you don't know what DLSS is, or how it works. It's not using "AI", that's just marketing bullshit. Apparently it works on some people 😂

You can find tons of info on this (why I told you to search it up), but it uses rendering tables, inference sorting, and pattern recognition to quickly render scenes with other tricks that video formats have used for ages to render images at a higher resolution cheaply from the point of view of the GPU. You render a scene a dozen times once, then it regurgitates those renders from memory again if they are shown before ejected from cache on the card. It doesn't upsample, it does intelligently render anything new, and there is no additive anything. It seems you think it's magic, but it's just fast sorting memory tricks.

Why you think it makes games better is subjective, but it solely works to run games with the same details at a higher resolution. It doesn't improve rendered scenes whatsoever. It's literally the same thing as lowering your resolution and increasing texture compression (same affect on cached rendered scenes), since you bring it up. The effect on the user being a higher FPS at a higher resolution which you could achieve by just lowering your resolution. It absolutely does not make a game playable while otherwise unplayable by adding details and texture definition, as you seem to be claiming.

Go read up.

in reply to just_another_person

lemmy - Link to source

FreedomAdvocate

I 100% know what DLSS is, though by the sounds of it you don't. It is "AI" as much as any other thing is "AI". It uses models to "learn" what it needs to reconstruct and how to reconstruct it.

What do you think DLSS is?

You render a scene a dozen times once, then it regurgitates those renders from memory again if they are shown before ejected from cache on the card. It doesn’t upsample, it does intelligently render anything new, and there is no additive anything. It seems you think it’s magic, but it’s just fast sorting memory tricks.


This is blatantly and monumentally wrong lol. You think it's literally rendering a dozen frames and then just picking the best one to show you out of them? Wow. Just wow lol.

It absolutely does not make a game playable while otherwise unplayable by adding details and texture definition, as you seem to be claiming.


That's not what I claimed though. Where did I claim that?

What it does is allow you to run a game at higher settings than you could usually at a given framerate, with little to no loss of image quality. Where you could previously only run a game at 20fps at 1080p Ultra settings, you can now run it at 30fps at "1080p" Ultra, whereas to hit 30fps otherwise you might have to drop everything to Low settings.

Go read up.


Ditto.

This entry was edited (5 days ago)
in reply to FreedomAdvocate

lemmy - Link to source

just_another_person

I 100% know what DLSS is, though by the sounds of it you don't. It is "AI" as much as any other thing is "AI". It uses models to "learn" what it needs to reconstruct and how to reconstruct it.


No, you don't. en.m.wikipedia.org/wiki/Deep_L…

This is blatantly and monumentally wrong lol. You think it's literally rendering a dozen frames and then just picking the best one to show you out of them? Wow. Just wow lol.


Literally in the docs: raw.githubusercontent.com/NVID…

What it does is allow you to run a game at higher settings than you could usually at a given framerate, with little to no loss of image quality. Where you could previously only run a game at 20fps at 1080p Ultra settings, you can now run it at 30fps at "1080p" Ultra, whereas to hit 30fps otherwise you might have to drop everything to Low settings.


No it doesn't. It allows you to run a game at a higher resolution for no reason at all, instead of dropping to a lower resolution that your card can handle natively. That's it.

Keep claiming otherwise, and you're just literally denying reality and the Nvidia link to the docs right in front of you.

suite of real-time AI image processing technologies by Nvidia

Contributors to Wikimedia projects (Wikimedia Foundation, Inc.)
in reply to just_another_person

lemmy - Link to source

FreedomAdvocate

Linking to an 81 page document isn’t helpful. What specifically in there are you referring to?

No it doesn’t. It allows you to run a game at a higher resolution for no reason at all


Other than the reasons like I said - running it at higher settings while maintaining a playable framerate. The point is you don’t have to lower settings as much with DLSS.

You fundamentally don’t understand what it is and what it allows you to do.

lemmy - Link to source

Energy minister leans on oil industry talking points in carbon capture announcement
Avoid Paywall

Energy minister leans on oil industry talking points in carbon capture announcement

On Friday, the federal government announced $21.5 million for a handful of carbon capture projects in Alberta, and while the amount isn’t going to move the needle, Energy and Natural Resource Minister Tim Hodgson’s choice of words and tone signal how…
Canada's National Observer

lemmy - Link to source

Clean Energy Canada responds to reports that the federal government is considering updating its EV Availability Standard

Clean Energy Canada responds to reports that the federal government is considering updating its EV Availability Standard - Clean Energy Canada

TORONTO — Clean Energy Canada executive director Rachel Doran and director of public affairs Joanna Kyriazis drafted the following response to reports that the federal government is considering updating its Electric Vehicle Availability Standard.
Clean Energy Canada
in reply to Sunshine (she/her)

lemmy - Link to source

Yaztromo

I truly hope Prime Minister Carney doesn’t drop the mandate.

There are two very important parts of the enabling legislation that too many people just don’t seem to know, and it’s skewing the online discussions everywhere:

  1. PHEV’s are still going to be allowed after 2035. So if you are so enamoured with giving your hard earned money to the oil and gas companies you’ll still be able to do so for decades to come;
  2. The mandate doesn’t affect used vehicles at all;
  3. Companies that miss the legislated targets can instead get credits by building out EVSE (charging) infrastructure. So for all those online pundits who think we should drop the mandate because we don’t have enough charging infrastructure, we get that infrastructure by keeping the mandates, and it gets paid for by the companies selling too many gas powered cars (and not taxpayers).

PM Carney needs to tell the automotive executives who say they can’t sell enough EVs/PHEVs to start building out infrastructure. It may be worthwhile to re-balance some of the timelines and how much the infrastructure credits are worth, but dumping them entirely is bad for Canada as a whole.

⇧