• 0 Posts
  • 12 Comments
Joined 1 year ago
cake
Cake day: June 14th, 2023

help-circle
  • You can see other people in a reflection without them being able to see you.

    It is not possible to see someone else’s eyes (except from the side, so it’s only seeing their eyes in profile) in a reflection without them being able to see you too.

    It’s literally not possible via reflection, as everything is equal and opposite. If light can go from their eyes to yours, it’s also possible to go the opposite direction.

    This is what everyone has been saying but instead of thinking through everything clearly, you resorted to bullying.

    The only way to accomplish this one-way vision is by adding something that is not reflection to the system (like a one-way window), but that’s breaking the premise under which everyone else has been commenting in good faith.



  • Google still controls the source, and so they have influence over the rest.

    It’s like Ungoogled Chromium. Sure, it’s open source. Sure, if might have Google crap removed. Google still calls the shots on the direction of the browser.

    Same still meaningfully applies to Chromium-based browsers.




  • To be fair, Apple made audio sharing an absolute nightmare. I have never gotten my remote control software audio to work on Mac and have tried multiple non-Crapple solutions.

    Discord won’t even make it as painless as possible though, and getting it set up requires downloading a third party thing now (from outside the app, before I could at least click a button inside the app).

    I totally gave up a few months ago on Discord on Mac because I was sick of booting into safe mode. I’m not sure who is to blame for this but I imagine it’s Apple.



  • A more granular view of your actual traffic/usage habits.

    Let’s say a page you visit embeds a Tweet, you’ll end up firing off a DNS request for twitter.com, and at least one request to load data from Twitter.

    Now let’s say you actually use Twitter. The DNS request will be the same, and you will have many requests to Twitter to load data.

    In both situations a DNS request is sent off, so the DNS provider knows you probably loaded something but they are going to have a harder time understanding if you are a Twitter user or if you are just frequenting a website with Twitter embeds. However the network provider that can see to what servers the HTTPS request for data are going will see just how often you are actually connecting to Twitter and the size of the transferred data and can build an incomplete but still far more detailed picture of your habits, and they would be able to tell the difference between an only-embed viewer and a regular Twitter user.

    Additional dystopian future possibility:

    Also, for anyone with objectively nefarious future goals, even if the data is encrypted, if one day we are indeed able to break encryption en masse the DNS provider can’t decrypt data they don’t have but the network provider definitely could.