Open source nerd

Reddit refugee. Sync for Reddit is dead, all hail Sync for Lemmy!

https://thurstylark.com/

  • 0 Posts
  • 113 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle






  • I mean, random NFC tags, I can understand. But, isn’t advising someone to avoid QR codes obsolete by now? It was a pretty worthwhile attack vector at one point, but nowadays most phones will ask “Do you want to <handle> <contents in full>?” before actually doing anything with it…

    Although, now that I think about it, it is best practice to advise to the lowest common denominator… Sometimes I overestimate users’ ability to avoid doing stupid things…







  • I’ll bite: Arkansas (and probably some other states that I’m less aware of)

    It’s an old law from the westward expansion days which says that any establishment that sells food and/or drink is not allowed to charge for the serving of water itself. Some businesses get around this by automatically upcharging for a larger size than their “standard” drink serving size (read: anything beyond “small”), or by charging for the cup, but the vast majority still follow the spirit of the law and don’t charge for water because of the cultural momentum.

    You’re still right, though. There are costs associated with acquiring and maintaining a supply of potable water, so this law effectively forces businesses to eat the cost of the water they serve to customers. However, that’s such a small percentage of a restaurant’s water use that it’s trivial to cover by other means.



  • Thurstylark@lemm.eetoLinux@lemmy.mlItag alternative?
    link
    fedilink
    English
    arrow-up
    4
    ·
    1 month ago

    There’s probably a better way to do this, but I’ve just started using BLE Radar (F-Droid, Play Store), which can be set up to (among other things) tell you where your phone last saw a particular bluetooth address.

    You don’t get the benefit of the tracking network that iPhones, and now Androids, are a part of, and it’s not built into the base system, but it’s FOSS, and your location data stays local.




  • I agree that if there was enough space in the recovery partition to begin with, this wouldn’t be a problem, but the user isn’t the party that specified that size or the party that decided to add enough stuff to the recovery partition to exceed that spec.

    MS knows that this is a widely-deployed configuration (they deployed it), but they’re going ahead with an automatic update that is incompatible with that configuration anyway, failing to communicate to the user why the failure occurred, and refusing to automate a fix to the thing their automation broke in the first place.