• 0 Posts
  • 157 Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle









  • I like self checkout. I struggle with talking to people and it can really drain on me so it’s a godsend to have if I only need to run in for a few things.

    Valid take.

    That being said, I’d probably prefer human checkout unless we can get a more-automated form of self checkout. Self checkouts have gotten a lot better since the early days, but human checkers are still faster than I am at the self-checkout and if a human is doing the checkout, I can dick around on my phone or whatever.

    Cost savings are nice, but cost savings on my groceries just aren’t a massive concern for me. There just isn’t that much human time being expended on checking my back out. I don’t have strong feelings about the human interaction one way or another.

    Maybe one day, we can get some sort of robotic arm setup that can do checkouts as well as a human checker, and then I’d quite happily be in the “machine” camp.


  • If you had the wedding photos in question professionally taken, it might be that the photographer, if they’re still around, might have copies. I don’t know whether they retain copies, but I suppose asking can’t hurt.

    This place says up to a year:

    https://www.wanderlustportraits.com/how-long-photographers-keep-photos/

    Photographers typically keep photos of their clients for a minimum of 90 days and up to a full year as part of standard practice; however, if this is important to you, review the contract and ask your professional.

    This guy says forever:

    https://old.reddit.com/r/WeddingPhotography/comments/96ckow/how_long_do_you_hold_on_past_wedding_photos/

    I keep ALL files on two 16tb drives drives. Those drives never get wiped and I will always keep two copies even when they fill up. One internal on sata for reference and one off site. When I first started shouting, I was cheap and deleted RAWs and just kept high res jpegs. I have clients coming back for albums and I am stuck re-editing the jpegs to match in the albums. Lesson learned. If you do want to consolidate, then keep the RAWs of the editor we jpegs and delete the unused. But that’s more hassle than the cost to store unused raws. You can also rely on cloud source but you never know if you’ll ever switch cloud servers or move onto another business on want to stop paying cloud fees. For the high volume photographers it becomes wise to invest in tape drives. HDD have lives of 10 years. So eventually all those old drives will need to be transferred to newer drives. Budget this into your bottom line


  • I was consolidating data from multiple old drives before a major move—drives I had to discard due to space and relocation constraints. The plan was simple: upload to OneDrive, then transfer to a new drive later.

    I’m assuming that the reason that he didn’t just do the transfer to a new drive instead of to OneDrive (which seems like it’d be more-straightforward) is because the new drive was going to also be a system disk, not just hold his data.

    I think that it would have been a good idea to get a second new drive and have done that transfer just so that there’s a backup. I mean, it doesn’t really sound like the user was planning to wind up with a backup of his data, or for that matter, that he had a backup to start with.

    Maybe OneDrive locking the account was unexpected, but drives can fail or be inadvertently erased or whatever. If you’ve got thirty years of irreplaceable data that you really badly want to keep, I’d want to have more than one copy of it. The cost of a drive to store it is not large compared to the cost involved in producing said data.



  • It’d theoretically be possible to run a straight GNU/Linux tablet or laptop

    “GNU/Linux” is the full way to say what sometimes gets shortened to “Linux” — a family of operating systems based on the Linux kernel and a lot of software from the GNU project. This explicitly distinguishes it from Android, which also used the Linux kernel.

    The former is not, in 2025, typically used to run smartphones. The latter is the most-common smartphone operating system in the world. If you buy a smartphone that isn’t an Apple smartphone, it almost certainly runs Android.

    with a 5G cell modem for data

    5G is the current generation of cell phone radio protocols. Communicating directly via voice over this protocol is not something that I believe is available to GNU/Linux in 2025. However, it can send non-voice data.

    , use SIP service

    SIP is a protocol for running voice over a data connection to the Internet. If you have an Internet connection, you can use SIP. There are companies, SIP service providers, which will, for a fee, provide a phone number at which one may be called or call others from a computer that can make use of SIP.

    and a GNU/Linux dialer,

    A dialer is the piece of software that on a smartphone, a user would probably call something like “the phone app”.

    and then run Waydroid for any specific Android apps that one has to run.

    Waydroid is a piece of software to run Android apps on a GNU/Linux system.

    Idle power usage is gonna be a lot higher than on a phone, though.

    Phone hardware and software has had a lot of work put into optimizing it for very low power usage. A larger device, like a laptop or tablet, will probably also have a larger battery, but it will consume more power as well.

    And a lot of Android apps are made with a touch interface

    Smartphones, due to physical space constraints in one’s pocket, typically have an entire side be a touchscreen. They do not have a keyboard. In general, software optimized for this works somewhat differently from software optimized for use with a keyboard and mouse.

    Most GNU/Linux software is written with the intent that it be used on a system that almost certainly has a mouse and keyboard available. Most Android software is written with the intent that it be used on a system with a touchscreen available.

    This means that even if one can run GNU/Linux software on a phone, much of the (large) collection of GNU/Linux software available will not be designed with an interface ideal for use on a phone.

    and small screen in mind and are aware of things in a cell environment, like “only update X when on WiFi”. Not really common for GNU/Linux software to do that.

    Smartphones have two widely-used mechanisms of accessing the Internet — connecting to the often slower cell network, or to a much-shorter range, but faster, WiFi network. Many people connect their smartphone to a WiFi network at some times and a cell network at others. Because this is so common, a lot of Android software has behavior designed to support this and act more-appropriately, like having an option to only transfer lots of data when on a WiFi netwprk. This is not the case for most GNU/Linux software.







  • I tried to try llms but my 4GB VRAM is just not at all enough, what’s the minimum you need in your opinion?

    For just using Wayland, 4GB should be fine. I’m using, uh, 801M right now, and it doesn’t change that much. I think I’ve seen it get over 1GB, not to 2GB.

    For current 3D games, yeah, I agree, 4GB is very much not enough. If I were getting a card to play 3D games on in 2025, I’d probably aim for 16 GB. Could live with 12GB. 8GB is IMHO not what I would go with for PC gaming in 2025. Lots of stuff can run, but games might need to have texture resolution turned down or something.

    For LLM stuff, the sky is the limit. I mean, right now, I have image generation models on my computer that will blow past that, need to live partially in main memory. And I can certainly do things, like generation of images at the full resolution of my screen without upscaling using more-memory-intensive models that will exhaust 24GB of VRAM.

    If you’re running into problems with 4GB just running normal Wayland apps, something is wrong.

    kagis

    I see several people using Nvidia GPUs claiming that various scenarios cause their VRAM to be consumed under Wayland. I’m using an AMD GPU on sway myself, so maybe that could be a factor.

    https://forums.developer.nvidia.com/t/multiple-wayland-compositors-not-freeing-vram-after-resizing-windows/307939/12

    https://github.com/NVIDIA/egl-wayland/issues/126#issuecomment-2379945259

    This is talking about reports of two separate problems that Nvidia is working on related to VRAM usage under wayland. The guy here, one of the NVidia Linux driver guys, is working on one, says that there’s a manual fix for one of them, Wayland compositors using a lot of VRAM, and gives it in his comment.

    He also says that there are reports of some other issue with Xwayland apps (X11 apps running under Wayland) using a lot of memory, and he hasn’t been able to identify that problem.

    He made that post nine months ago, so I’d think that they may have rolled the fix he was talking about out to users. I do see several users saying that the manual fix solved their issue at the above links.