• 36 Posts
  • 1.69K Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle



  • Avid Amoeba@lemmy.catoTechnology@lemmy.worldWhat the hell Proton!
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    17 hours ago

    The OS interfaces provided to apps (generally POSIX) have no idea what HTTP is. They’re much lower level than that. If an OS is to control what protocols are used by apps, it has to offer some functionality that does HTTP for the apps and apps have to use it. Unfortunately the only way to force that would be to disable the general OS interfaces so that apps can’t just use existing libraries that use those. If you did that your OS would become useless in other ways that rely on the basic interfaces.

    The other way the OS could do anything about it is to inspect network traffic going over its network interfaces. That would be a significantly different can of worms and it’s not free in terms of processing power and therefore battery. Then you’d have the screams of privacy people that Android or iOS is looking at all network traffic.

    So all in all, the OS isn’t very well suited to police application level protocols like HTTP. At least not on devices whose primary purpose isn’t network traffic related.





  • Apps don’t use the system browser to connect to REST endpoints. Neither do they use the OS. Apps typically use a statically linked library. There are use cases for HTTP-only connections so it’s unlikely that those libraries would mess with forcing or even warning its users that they’ve used HTTP instead of HTTPS. Point is Google and Apple can do little in this regard. Unless they scan apps’ source code which could be possible to some extent but still difficult because URLs are often written in pieces.


  • Avid Amoeba@lemmy.catoTechnology@lemmy.worldWhat the hell Proton!
    link
    fedilink
    English
    arrow-up
    70
    arrow-down
    2
    ·
    edit-2
    1 day ago

    Yup. You can grab any unencrypted data passed between the user’s browser and a server literally out of thin air when they’re connected to an open access point. You sit happily at the Starbucks with your laptop, sniffing them WiFi packets and grabbing things off of them.

    Oh and you have no idea what the myriad of apps you’re using are connecting to and whether that endpoint is encrypted. Do not underestimate the ability of firms to produce software at the absolute lowest cost with corners and walls missing.

    If I was someone who was to make money off of scamming people, one thing I’d have tried to do is to rig portable sniffers at public locations with large foot traffic and open WiFi like train stations, airports, etc. Throw em around then filter for interesting stuff. Oh here’s some personal info. Oh there’s a session token for some app. Let me see what else I can get from that app for that person.






  • I haven’t seen any report of missiles targeting populated areas. Only military targets. So I think we can scratch that from the equation. Either they let everything that was targeting the base fall or they were defending it and some got through. Doesn’t make sense that they intentionally let some hit the hangars and runways if they were defending the base. I doubt they can tell exactly where every projectile is gonna fall. It’s possible that they focused more on the other base that was being targeted. But I find it unlikely that they didn’t defend this base given they use it for their F35 fleet. At the very least there could have been enough damage to put it out of service for a while.








  • Posting this further up for visibility.

    Maybe I’m stupid but there’s this table:

    It seems like they’re not just counting the combustion emissions in that number.

    Then there’s also this, which explicitly talks about fuel development emissions:

    The carbon-dioxide emissions just from combustion are substantially greater for coal, 99 g CO2/MJ versus 55 g CO2/MJ for LNG. Total carbon-dioxide emissions from coal, including emissions from developing and transporting the fuel, are also greater than for LNG, but the difference is less, 102.4 g CO2/MJ for coal versus 83.1 g CO2/MJ for LNG (Table 4). This is because of greater energy costs and, therefore, higher emissions of carbon dioxide for developing and transporting the LNG compared with coal. Methane emissions for LNG are substantially larger than for coal, 76.5 g CO2-equivalent/MJ for LNG compared with only 17.3 g CO2-equivalent/MJ for coal (Table 4). As presented in Section 2, this result for methane emissions for coal is quite robust across regions, including China and Poland.55, 56 Consequently, total greenhouse gas emissions are 33% larger for LNG than for coal for the cases of average tanker-cruise lengths, 160 g CO2-equivalent/MJ for LNG versus 120 g CO2-equivalent/MJ for coal (Table 4).

    Did you look at the paper or am I grossly misunderstanding something?