• 0 Posts
  • 96 Comments
Joined 1 year ago
cake
Cake day: November 7th, 2023

help-circle

  • scrion@lemmy.worldtoMemes@lemmy.mlTime to admit defeat
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    1 day ago

    I do in fact use unrefined, brown cane sugar, although I have not tried panela specifically.

    The one I use pretty much looks like this:

    It’s an organic fair trade brand, but I’d have to look up where it is imported from.

    As I said, I can’t imagine making it with any other kind of sugar any more. Sorghum seems like an interesting idea, might have to experiment with that.



  • It’s not like Bluetooth started demanding location permissions, the conceptual model of the permission was revised: having access Bluetooth means an app could determine your location via a form of lateration.

    In earlier versions of smartphone operating systems, this was not transparent to users lacking the technical background, so Bluetooth also requiring location access is actually an attempt at making users aware of that. I’m not an iOS developer, so I can’t comment on iPhones, but on Android versions prior to 11, having access to Bluetooth meant an app would be able to determine your location.

    Today, you can require the permission ACCESS_FINE_LOCATION, which expresses that your app might use Bluetooth to obtain location information on Android. Also, if you’re just scanning for nearby devices to connect your app to, but don’t want users to be confused why your smart fridge app needs to know your precise location, you can declare a permission flag (neverForLocation) and Android will strip beacon information from the scan results, better asserting your intentions.

    So, overall: no, there is nothing nefarious going on, it was always possible to determine your location via Bluetooth, and the update to the permission model was an honest improvement that actually benefits you as user.

    Now, there are still plenty of shady apps around, and apps that are poorly written - don’t use those.









  • NewPipe stops working whenever Google updates YouTube with a breaking change that NewPipe needs to integrate then, e. g. renaming parameters, changing URLs and the like.

    NewPipe has been steadily working for years, with the expected interrupts as they have to play catch up with YouTube. That typically only lasts a few days, sometimes hours, though.









  • I think you’re falling into a bit of a trap here: perfect is the enemy of good. Not everything has to be automated, instead of growing pains, there can also be gains.

    Remember, we are currently aiming to get these vehicles on the road, alongside regular drivers. They use sensors and computer vision to read street signs, detect people etc., all with the reaction speed of a machine. What if the in-between product is simply a better driver with faster reaction times? That is the current goal, really - no one wants to automate everything, simply because that wouldn’t be feasible anytime soon.

    Yes, again, we’re not there yet and these things are far from perfect. But let’s first just aim to get them good enough, and then maybe just a little better than your average driver.

    As for the your proposed business model: we have capable drivers now, why do these business models don’t exist right now? Why is there no fast lane that allows me pay to get to my destination faster? What would the technology of driverless cars introduce that would enable these regulations?