i_am_not_a_robot
In theory, running a serverless function can provide adequate response times at costs that are unreachable with private servers. It’s basically those services that would run your application for few minutes every time it received a request, but with theoretically lower overhead since it’s supposed to be a function instead of a full application.
Apple doesn’t want it to be VR. They want people to buy this expensive VR headset and wear it all day, but you can’t wear it in public because of how silly it looks, and you can’t carry it around everywhere because it doesn’t fit in your pocket and you can’t just toss it in a bag without damaging it, and you can’t even just wear it around your house unless you’re moving from outlet to outlet. The Vision Pro is an impossible cross between Facebook’s Quest Pro and Smart Glasses products. The technology to make a successful product out of it doesn’t exist yet.
There are ways to use the Vision Pro as a regular VR headset, but then you’re paying for things you’re not using.
That Pentum is a budget CPU from just over 10 years ago. It has PCIe 2.0. Maybe the “gigabit” ethernet is connected to the CPU by a single 500Mbit PCIe lane.
The link is broken, but this is apparently an issue with Signal Desktop, not regular Signal. The proposed solution does not work on Windows: https://www.electronjs.org/docs/latest/api/safe-storage
[…] content is protected from other users on the same machine, but not from other apps running in the same userspace.
It’s unfortunately about the best you can do on Windows.
How is the drone going to determine that it is being used to commit a crime?
Calling an unspecified gender person anything other than “they” was until recently considered to be incorrect. “They” is plural but now is used to refer to singlar persons because writing “he or she” everywhere is too much. Calling a user “he” does not imply that users are male or can only be male. Not using “they” or “he/she” or obscure gender neutral pronouns does not make something inherently transphobic. Closing PRs that unnecessarily change pronouns as spam is not inherently transphobic, but the accompanying comment is not very inclusive.
The post talks about “white suppremacist language,” but the proposed change did not remove white suppremacist language. It was just a generic anti “woke” message, possibly motivated by people brigading after the original PR to change “he” to “they.” White suppremacists may use also use similar language, but you can’t just pick things that a white suppremacist has done and decide that anyone else who does the same is a white suppremacist. He’s not blameless, but people are intentionally provoking the developer and exagerating the responses for drama.
Built bundles are not affected. The service is supposed to figure out which polyfills are required by a particular browser and serve different scripts. Because it’s serving different scripts, the scripts cannot be bundled or secured using SRI. That would defeat the purpose of the service.