That’s much better. Op turns into soup in the laser*(edit: damn autocorrect) scene

Did YouTube decrease the bitrate again?

This is not true. A17 pro is an existing chip that is slower than the A18. It wouldn’t make sense to call A18 A17 instead

Palwold dev talks too much

These are more like last 2 week but anyways:

• Finished Agent A after a year of hiatus.
• Got hdr to work in Dark Souls 2 with the graphics overhaul mod and finished getting the 4 big Souls.
• Got tired of the difficulty of Dark Souls 2 and decided to start a new random shooter from my library… Devil Daggers
• Had a management sim itch and gave another shot at FTL, never got to win. Half the time I lost in a single encounter to things like never landing a shot on the enemy ship due to shields + misses or 7 people teleporting to my ship and wrecking havok. Other times I got too greedy.
• Tried to figure out which way to go next in Dark Solus 2 by checking the wiki but kept getting sidetracked by things I might’ve missed.
• Also tried to quench the management itch with shapez, but didn’t like it much. Just made me crave the factorio dlc more. Amazing music though

I wasn’t defending the photo? Of course water is a bad thing

I was wrong about the hole, but I’d like to point out that full size camera lenses don’t need to be as thin as possible to keep the camera bump in check.

Now that I think about it it is a third microphone. When they came out there were many posts of S20Us’ and note20Us’ camera glasses spontaneously shattering and the consensus from what I read was sudden pressure change. The same thing happened to my previous phone while in my locker (galaxy c9 pro with a single small camera and no hole), so it sounded plausible. And it’s also believable that water doesn’t go in from surface tension alone since the hole is really small

Regardless I forgot that that it was supposed to be a microphone while posting my comments so nevermind

Edit: also phones do normalise air pressure, just get a barometer app and squeeze the phone

Wdym? Water has surface tension and dust is solid, air doesn’t have such limitations. My own phone (note 20 ultra) has an opening under the camera bump to allow air in to relive pressure despite having an ip68 rating.

That’s water and dust resistance, not air

It shouldn’t be air tight, otherwise it could break from pressure changes

Guessing from how this change required 3+ implementations before it became official according to the gitlab page, maybe it’s a chicken and egg situation. Hdr is a lot of work so maybe people don’t want to implement an unfinalized version that might change

Wow the icon saga is finished!?

If anyone wants to throw away a couple hours, there was SO much discussion (and initially drama) over it: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/269

Isn’t apple at 18W?

Source? This is using the same engine as Avatar frontiers and that can be played offline.

The eff passphrase generator has about 2.5 bits of entropy per character (without word separators). Eff recommends 6 word passphrases, and with an avg word length of 7, that’s (only) 79.45 bits of entropy that won’t even fit in the 32 characters. If there wasn’t a password length limit it would be possible to saturate the hash entropy with a 20+ word & 102+ char passphrase.

What scenario are you talking about?? From the article:

NGate malware can relay NFC data from a victim’s card through a compromised device to an attacker’s smartphone, which is then able to emulate the card and withdraw money from an ATM.
…
Masquerading as a legitimate app for a target’s bank, NGate prompts the user to enter the banking client ID, date of birth, and the PIN code corresponding to the card. The app goes on to ask the user to turn on NFC and to scan the card.

Physical card is involved, mobile payments isn’t.

No? The nfc sensor is next to the credit card, which is why it’s able to communicate with it to relay it.

Why would it need to create fake events? How would that even help?

There is nothing being subverted, nfc has applications other than contactless payments that require it acting as the reader, which is why it’s supported. It would be better if it was behind an explicit permission (just like other sensors would) but limiting it to only responding to readers is like limiting Bluetooth to audio transmission.

The fact you can trick the NFC system on the phone into reacting to “phantom” payment events and intercept the resulting token sounds like a pretty big problem.

That’s not what’s happening though? It’s relaying a physical card’s nfc not tricking mobile contactless payments