• 0 Posts
  • 39 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle


  • Apartments have apartment numbers, so different apartments would constitute separate billing/shipping addresses. For multiple people living in the same apartment/house (i.e. roommates at the exact same address), they may be SOL.

    Edit: Although, on second reading, the address check may only be to prevent multiple entries per account. Emphasis mine:

    Multiple registrations from any Steam account holder will be void.

    We will use information such as shipping address and/or payment information to eliminate multiple entries.

    Those restrictions could be done per account, so multiple Steam accounts at the same shipping/billing address might be fine as long as each account has different payment information (i.e. the accounts don’t have the same owner name and/or credit card). Could still be an issue for someone trying to register a whole family at the same address, if all the accounts are using Mom’s credit card.


  • It’s covered in the terms and conditions of the sign-up process. Here are the key bits:

    • You and your partner need separate Steam accounts. Newly created accounts aren’t eligible. Each account needs to have made a Steam purchase “prior to April 27, 2026.”
    • Valve uses “information such as shipping address and/or payment information to eliminate multiple entries.” Unless you and your partner have separate residences, Valve’s probably going to be able to spot that you’re in the same household. Even if one of you temporarily changes the account’s shipping address, billing address information will likely reveal that you two live in the same household.




  • Oof, yeah, that sounds painful. It does sound like some kind of hardware-related issue, maybe the default settings in the Fedora kernel are seriously aberrant when mixed with one or more of your hardware components? Given the broad range of issues (GPU, network speed, audio), I’d be inclined to suspect the problem was related somehow to something core/common like CPU or mobo. Almost certainly not a pure hardware fault, given the problems didn’t follow the hardware when you changed distros.

    Sorry but I just don’t like it. Not to say I think it’s a bad distro it’s just clearly not one for me.

    I totally get it. Doesn’t take much of that kind of frustration to leave a bad taste in your mouth. I had some perplexing intermittent lockup issues years ago that turned out to be BTRFS, or at least the issue went away when the VMs were rebuilt with a different root FS. I’m still leery of BTRFS, even though it was a fairly esoteric stack (SLES, ESX, NFS datastores served from a ZFS-backed storage server), so entirely possible the fault didn’t lie exclusively with the filesystem. But I still avoid it, just because I’ve been burned once.





  • This is it. A 2006 Ford F150 has a hood height of 51 inches, or just over 4 feet. Getting hit by one of these would be bad, but for many people it wouldn’t likely result in a head injury. A 2026 Ford F150 has a hood height of 75 inches, or more than 6 feet tall. Getting hit by one of these as a pedestrian is practically a guaranteed head injury.

    I’m sure there are other factors. Higher speeds, lack of investment in infrastructure, political unwillingness to make any changes that might increase congestion or slow down drivers. But I believe hood height is playing a huge role in the type and severity of pedestrian injuries in the US and Canada.