lemmyvore

joined 1 year ago
[–] lemmyvore@feddit.nl 2 points 2 weeks ago

Yeah you don't want your computer to be stable for 5 years going, that's very un-Arch.

[–] lemmyvore@feddit.nl 4 points 2 weeks ago (8 children)

I like to call it Arch for the lazy.

[–] lemmyvore@feddit.nl 1 points 2 weeks ago

Because AI reversed the ratio.

[–] lemmyvore@feddit.nl 2 points 2 weeks ago

It's much worse. Generally speaking projects in large corporations at least try to make sense and to have a decent chance to return something of value. But with AI projects is like they all went insane, they disregard basic things, common sense, fundamental logic etc.

[–] lemmyvore@feddit.nl 5 points 2 weeks ago

They typically use internal personnel and being parcimonious about it so you're right about that.

[–] lemmyvore@feddit.nl 9 points 2 weeks ago (3 children)

Well probably not just Nvidia but the next likely beneficiaries are in the same range (Microsoft etc.)

[–] lemmyvore@feddit.nl 29 points 2 weeks ago (4 children)

Ah it doesn't work on Android? A pity, that's where I need dark mode the most.

[–] lemmyvore@feddit.nl 1 points 2 weeks ago

In that case I call bullshit. What I described can work (relaying banking apps on the victim's phone to authenticate to ATM), with cards it should not. If you read the comments on the site you'll see people are just as confused as to how this can work.

[–] lemmyvore@feddit.nl 0 points 2 weeks ago (2 children)

There's no credit card involved in this scenario.

  1. The attacker uses phone A and touches the ATM NFC reader. This creates a NFC event on phone A that requests a token.
  2. Phone A sensds the request data to the malware running on victim's Phone V.
  3. The malware on phone V creates a fake NFC event that makes it look like the phone V was touched against the ATM. <-- this is the huge security issue IMO
  4. The app on phone V that's currently associated with NFC contactless payments responds to the fake NFC event by issuing a token.
  5. The malware on Phone V sends the token to phone A.
  6. Phone A uses the token to "prove" to the ATM that the real customer is in front of it.
  7. The ATM asks for the PIN and the attacker supplies the correct PIN (which they've previously obtained via social engineering).
  8. Attacker can now withdraw cash from the ATM from the victim's account.
[–] lemmyvore@feddit.nl 3 points 2 weeks ago (1 children)

The most successful ML in-house projects I've seen took at least 3 times as long than initially projected to become usable, and the results were underwhelming.

You have to keep in mind that most of the corporate ML undertakings are fundamentally flawed because they don't use ML specialists. They use eager beavers who are enthusiastic about ML and entirely self-taught and will move on in 1 year and want to have "AI" on their resume when they leave.

Meanwhile, any software architect worth their salt will diplomatically avoid to give you any clear estimate for anything having to do with ML – because it's basically a black box full of hopes and dreams. They'll happily give you estimates and build infrastructure around the box but refuse to touch the actual thing with a ten foot pole.

[–] lemmyvore@feddit.nl 6 points 2 weeks ago

TBF in most cases forced app obsolescence is on the developers. Some of them are super aggressive and will force you to update without really needing it. Like, come on, package tracking app, I really don't believe you're unable to show me the package pick-up barcode without updating. 🙄

But yeah, on iOS it's completely impossible to get older versions, once you've updated something that's it. And even on Android I've noticed that it's become impossible to downgrade some apps even if I have the old apk, the Google installer simply fails to install it if I've ever had a newer version installed.

view more: ‹ prev next ›