And just like Taco Bell when something goes bad you get to deal with all the diarrhea.
But seriously, shouldn’t this be in !programminghumor@lemmy.world and not technology?
And just like Taco Bell when something goes bad you get to deal with all the diarrhea.
But seriously, shouldn’t this be in !programminghumor@lemmy.world and not technology?
Context: I heard that lemmy will upvote anything. This is literally just a can of fucking beans
And then there was weeks and weeks of bean posts.
My guess: turn failing big companies into failing little ones.
Looks like someone tried to archive an archived page. You can see https://web.archive.org/...
is listed twice in the url. I just trimmed off the first one then it works: https://web.archive.org/web/20240229113710/https://github.com/polyfillpolyfill/polyfill-service/issues/2834
Embracer treats studios like they are disposable. They killed Volition (Saint’s Row), Free Radical (TimeSpltters) plus a bunch of other studios. All of that was because their $2 billion deal with the Saudi Government fell through. Some studios managed to escape when one of the Saber Interactive original owners bought back a bunch of studios. They recently killed Pieces Interactive (Alone in the Dark).
If a studio is owned by Embracer, they are lucky if they will be around in 5 years.
That depends. Are you looking at preserving the music without loss of information? Then you need to use a lossless format like flac. Formats like aac, mp3, opus can throw away information you’re less likely to hear to achieve better compression ratios. Flac can’t, so it needs more storage space to preserve the exact waveform.
You can use a lossy format if you want. On most consumer level equipment, you probably won’t notice a difference. However, if you start to notice artifacting in songs, you’ll need to go back to the originals to re-rip and encode.
Bad bot. Bad summary.
There’s talk on the Linux kernel mailing list. The same person made recent contributions there.
Andrew (and anyone else), please do not take this code right now.
Until the backdooring of upstream xz[1] is fully understood, we should not accept any code from Jia Tan, Lasse Collin, or any other folks associated with tukaani.org. It appears the domain, or at least credentials associated with Jia Tan, have been used to create an obfuscated ssh server backdoor via the xz upstream releases since at least 5.6.0. Without extensive analysis, we should not take any associated code. It may be worth doing some retrospective analysis of past contributions as well…
Wasn’t Gearbox hired to finish Duke Nukem Forever? I remember it being someone else’s turd they had to polish.
So basically, Saber and all studios under Saber won’t have to worry about suffering the same fate as Volition did under Embracer. Maybe?
This is an FYI for any Tribes: Ascend fans. Tribes 3 is basically being developed and published by Hi-Rez 2.0. Prophecy Games is a spin off of Hi-Rez Studio and is run by the owner.
For those not familiar with the history of T:A, Hi-Rez released the game as free-to-play, had some of the grindiest of grinds (took forever to unlock the spinfusor for just one class), and a monetization plan that was targeting whales. There were balancing issues that needed to be addressed, promised features left undeveloped like competitive, and they basically abandoned the game within a year. They moved their developers over to Smite while things degraded leaving the player base salty AF. You’ll have to visit that other site for the history, but this is probably a good starting point. And I can’t forget that the CEO never took responsibility for their horrible monetization plan.
Now I would hope that Hi-Rez Prophecy would have learned from their mistakes because Tribes is one of those games I hold a special place for. However, they released a pair of day 1 DLCs that each costs more than the game itself.
There’s one good news. Reddit didn’t want to pay to move all the old DMs to the new chat infrastructure. So they deleted them.
At this point I wouldn’t trust Reddit to actually delete posts. Just hide them then sell them as training data if the upvotes are decent.
Tom’s Guide has shit reporting. This was the same site that repeated the bogus DDoS smart toothbrushes story. And they’re at it again with more sensationalism.
From something more reputable:
The use of the victims’ faces for bank fraud is an assumption by Group-IB, also corroborated by the Thai police, based on the fact that many financial institutes added biometric checks last year for transactions above a certain amount.
It is essential to clarify that while GoldPickaxe can steal images from iOS and Android phones showing the victim’s face and trick the users into disclosing their face on video through social engineering, the malware does not hijack Face ID data or exploit any vulnerability on the two mobile OSes.
More from bleeping computer:
A new iOS and Android trojan named ‘GoldPickaxe’ employs a social engineering scheme to trick victims into scanning their faces and ID documents, which are believed to be used to generate deepfakes for unauthorized banking access.
Now, don’t get me wrong, you should take malware and social engineering attacks seriously. But get your information from sites that do real security journalism.
A few months back Ruud stood up a copy: https://searxng.world/
I’ve been using it, and it tends to be as good as or better than google’s search. There’s only been a handful of instances where I’ve explicitly used google’s.
They released two games. The first was just a game jam thing they threw together that established the core mechanics. The second was much more fleshed out and polished.
The Naz.API leak that was given to Troy Hunt is different from this leak. That’s also an aggregation, but smaller in size. What Troy has is probably more significant since about 1/3 of that is newly discovered. Right now, no one has published an analysis of the unique accounts in this larger aggregation.
It’s an aggregation of previous leaks. Malicious actors having all that information together is a big deal in and of itself, but it’s not the"mother of all breaches" some publications are trying to make it be.
Given their history of hostilities. Hell has a better chance of freezing over than a secret agreement existing.
Apple has a long history of working against right to repair and third party repair shops. This includes making it difficult for third parties to source the parts needed and changing the designs to requiring part pairing in the name of security. It got to the point where repair shops were buying broken Apple products so they could hopefully source the parts needed.
Looking through what they provided now, it’s basic stuff any third party repair shop could do if they could source the parts. It’s useful. However good electronic technicians can go beyond that and do board level repairs. But that requires schematics and diagrams. A lot of times they would have to get those through other parties who in turn got them through less than official means or violated NDAs.
Guess what Apple isn’t providing? Board level information. This is just doing the minimum the law requires them to do.
Bonus: Louis Rossmann talks about Apple’s history of right to repair [10 minute video]