• 0 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 1st, 2023

help-circle
  • https://www.bleepingcomputer.com/news/security/genetics-firm-23andme-says-user-data-stolen-in-credential-stuffing-attack/

    The information that has been exposed from this incident includes full names, usernames, profile photos, sex, date of birth, genetic ancestry results, and geographical location.

    The threat actor accessed a small number of 23andMe accounts and then scraped the data of their DNA Relative matches, which shows how opting into a feature can have unexpected privacy consequences.

    • Usernames Profile Photos DoB

    They can be linked to other online accounts. This allows for phishing, potentially scamming or getting additonal information on them which can lead to more sophisticated/personalised scams. Older, less tech savvy users are better targets for scammers.

    • Username Sex DoB Genetic Ancestry Location data

    Data aggregators can sell this info to Health Insurance Companies or any other system who can then discriminate based on genes sex age or location

    • All of this information

    Can contribute to people committing fraud with their information if they collect enough information from different sources.

    • DNA relatives

    Having enough information about a user to use it to target their now known relatives in personalised scams.

    The people that did this probably didn’t know what information they were going to get, maybe they were hoping for payment info, and settled for trying to just sell what they got.

    Any information, no matter how useless it might seem, is better than no information and enough useless information in the wrong hands can be very valuable.

    Theres countless data breaches every year and people will collect it all and link different accounts from different breaches until they have enough information. Most people use the same email address for every website and a lot of people reuse the same passwords, which is how this data leak occurred. Knowing that these users reuse the same email/password combination here means theres a very good chance they’ve reused it elsewhere.

    You can check out what data breeches have occured and if your email or password has been posted in any of these dumps here https://haveibeenpwned.com/

    Once the information is out there, its out there for good and what might seem trivial now to you could be valuable tomorrow to someone else



  • I’ve run into issues where a game will work with a specific version of wine but then not work with a newer version but then other games that don’t work with the older version, work with the new one.

    Theres also potentially issues of dependencies for one game breaking another game. Separate prefixes just make it easier to troubleshoot a game not working since you can just install/uninstall whatever dependencies that it might need without worrying about messing up other games.

    Its also just easier to delete the entire prefix when you realise you’ve installed too many useless dlls and you’ve finally found the one thing you do need to make the game work lol

    I also like to archive games I like since companies can just decide to remove their games from existence whenever they want. So I just add the separate prefix that has any extra dlls or tweaks to the archive so that the game should still work in 3 years without having to try and download dependencies that may not be as easy to find in the future

    But if you don’t have issues I don’t think its a big deal and if you do have issues with a game, you can just make a separate one for that anyway.



  • I use Lutris and set up my directories a “GameName” and then 2 subdirectories “game” “prefix” and point Lutris to these.

    All of the game files go in “game” and the prefix is created in “prefix” when I press play in Lutris. Any extras dlls that are needed can be installed with winetricks within Lutris to that specific prefix

    This way you can just compress and decompress “GameName” folder and point Lutris to these locations on whichever machine.

    You can choose which prefix version you want in Lutris and it will download that version for you. I’m pretty sure it saves the version to somewhere in ~.local/share/lutris I’m not at my PC now so not 100% sure of the path.

    It saves it to ~.local/share/lutris/runners/wine and you can put a custom wine build here and Lutris should recognise it when configuring the runner options

    So you could copy this over to the corresponding location on the deck and Lutris will automatically detect this version as installed and won’t have to download it again but its not necessary unless you don’t have internet on the deck, or you’re like me and want to keep an archive of the working prefix for the future in case the prefix version is no longer available for whatever reason and other version just won’t work.

    If you’re new to Lutris, I wrote a step by step guide on how I use Lutris on a different community

    https://sopuli.xyz/comment/9858101











  • I’ve been degoogled since 2019 so I have never actually used RCS so I’m not 100% sure.

    If I were to guess I would assume it has something to do with Apples support for RCS. The last time I checked, Apple won’t support end-to-end encryption in RCS and the messages are only encrypted in transit so maybe Android users that will use RCS with Apple users will have all of the chats saved unencrypted within the system folders and that would be no bueno for Google

    But I’m honestly not sure, I have no interest in learning about RCS unless GSMA helps open source apps integrate it so I’m not stuck with either Samsungs or Googles messaging apps



  • As of 2024, Google is now quietly blocking RCS messages on unlocked/rooted android devices. Even if your device only has an unlocked bootloader, it is now at risk of being quietly shadowbanned from sending RCS text messages.

    According to the OP that opened the issue with Google, it doesn’t work with devices with unlocked bootloaders so it would affect the majority of custom ROM users since very few custom ROMs and devices support relocking the bootloader, and I think it probably would still affect these devices too since the last time I relocked a bootloader with DivestOS I still had the error message about system integrity on boot

    Rooted users can probably bypass this issue with some Magisk modules the same way they do with GPay and banking apps.

    If Google really does want to push RCS then disabling access to the more technically inclined users now seems a bit silly.

    I thought they’d at least wait for wider adoption before locking it down like they’re doing with YouTube and ad blockers, especially with imessage and WhatsApp being such big competitors. At least in Europe, I don’t see anyone dropping WhatsApp for RCS anytime soon.


    • Less bloat ware/spy ware - custom ROMs don’t come prepackaged with random shady games from shady companies or random shady social media apps from shady social media companies.

    • Better privacy and security implementations along with DeGoogling - a lot of ROMs offer Gappless ROMs which is really important since Google is way to big and has too much influence on android OEMs and its easily the biggest ad company in the world and constantly refused to respect peoples privacy. e.g GrapheneOS https://grapheneos.org/features and DivestOS https://divestos.org/

    • Long term software support to help against e-waste e.g LineageOS supports so many phones who’s manufacturers have stopped supplying software updates. https://wiki.lineageos.org/devices/

    • Customization e.g Crdroid includes loads of custom settings from a variety of other custom ROMs and OEM ROMs that rarely get implemented by any stock ROMs. https://crdroid.net/

    • Rooting android phones gives users the ability to access system files that they may not have been able to backup if the apps don’t support it. It also allows for a full system backup and restore

    • It also allows users to block ads and unwated connections without using a local VPN e.g adaway

    Enabling Google to dictate what a user can do with their own device by limiting features is a slippery slope and the last thing we want to happen is for Android to end up like iOS with its walled garden approach.