• 1 Post
  • 102 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle

  • The vast majority of what YouTube does on a technical level is ingesting a ton of uploaded user video, encoding it in dozens of combinations of resolution, framerate, quality, and codec, then seamlessly choosing which version to serve to requesting clients to balance bandwidth, perceived quality, power efficiency in the data center, power efficiency on client devices, and hardware support for the client. There’s a lot of stuff going on behind the scenes, and there’s a reason why the user experience is much more seamless on YouTube on a shitty data connection than, say, Plex on a good data connection.

    No, it doesn’t need to be realtime, but people with metered or throttled bandwidth might benefit from downloading just in time video at optimized settings.







  • Someone figured out a way that could hijack iMessage through sending a special malicious PDF that took advantage of a flaw in some legacy font rendering code unique to Apple, that even Apple hadn’t used in decades.

    Then, that PDF launched a JavaScript debugger that is built into iPhones, and took advantage of a flaw in that to jump into putting some code into the parts of user memory, that the system doesn’t fully trust.

    Then, that code takes advantage of another flaw to bypass the system’s protections for not fully trusting that code, to secretly launch a web browser and navigate to a secret webpage that runs a much bigger piece of malware.

    That malware can read and modify basically anything on the system, and was used to read all sorts of sensitive data: message history, location information, app data, etc.

    Because the whole exploit chain was so advanced and involved so many different previously unknown vulnerabilities, basically the list of possible suspects is very, very short: some kind of nation state with advanced hacking capabilities.



  • According to the article, attackers used automated scanning software, which strongly implies they brute-forced cameras connected to the Internet with default or weak credentials. That has nothing to do with whether or not the service is based in the cloud.

    This is a known problem with popular brands of security cameras sold in Vietnam, that the default configuration has an admin password of “admin” or “12345” accessible from the public Internet. They’re basically sold insecure, and rely on customers to consciously adopt a custom configuration to be secure.

    Although, in order to be publicly accessible, one would imagine that they’ve had to configure their firewall to let outside signals to the devices themselves. Or maybe some kind of ddns setup.

    Either way, it doesn’t have anything to do with the cloud, and the parent comment is basically right about that.





  • When I share a google doc, it’s not only over a email service of the same vendor, it’s just a link I can send anywhere.

    Well you’re sending a link to a Google hosted service. The other side necessarily needs to interact with a Google service in order to make sense of that link, and, if they so choose, make edits directly in that Google service or export with Google’s export functionality. If you send that link, a Microsoft Office user won’t simply be able to open it in Microsoft Word (and even if Microsoft implements that functionality it would require Microsoft to actively maintain an API key with the Google service).

    If you’re sharing a calendar entry between the current big 3 (Microsoft Outlook, Google Calendar, Apple Calendar), it sends an email to the other. From the users perspective, a Google user never has to interact with Apple’s servers, or a Microsoft server (whether a local Exchange server or a cloud-based 365 one), because everything necessary comes to that users own server through a federated messaging service (email). You just send an invite to user@domain and it just works, but the protocols all simply assume that user@domain is an email address and that sending email to that address will cause the other user’s email service to process and process that calendar invite for that user.


  • He did sell the stock, like $23 billion worth. He entered the agreement to buy Twitter to show that he had another use for that cash, so that Tesla investors didn’t get spooked and sell off when they see the biggest shareholder selling (along with the downward price pressure that comes from selling a significant percentage of a company’s stock).

    There was some speculation at the time that he entered the agreement with Twitter with no intention to close, just to cover his desire to cash out of Tesla at its high. Then the courts actually held him to that.