• 3 Posts
  • 1.14K Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle

  • if you need new things before it’s ready for a new version it’ll be pain

    Like what?

    Also if you need something before Debian is ready for it… you’re weird. I don’t mean this in a derogatory fashion, solely that you are doing something our of the ordinary. Consequently you should first question WHY you do that in the first place.

    Finally if you do need something very specific, containers are there to … contain that. Running Debian as the host distribution doesn’t mean you’re limited to it for your applications, servers included.








  • Few seem to address the issue here : it does not work 100% of the time for you.

    It might work for everybody else but that doesn’t help you much. You have your setup, no theirs.

    So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check https://lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and journalctl logs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g. dmesg.

    They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate :

    • what’s your crime scene? Your laptop and it’s log files
    • what’s the crime? It didn’t suspend properly
    • where are the traces? In the logs
    • where are the logs? Using journalctl or dmesg and typically in /var/log/
    • what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using grep and other tools

    You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window.

    TL;DR : grep logs


  • They can revoke usage. Say if you use app version 7 and the required app is version 8 then no transaction can be done. The app can be installed yet unusable. So it’s not because the app is installed and outdated that functionalities have to remain usable. Gaming servers do that all the time.

    I’m pretty sure they already do that, not “just” warnings.


  • Banks sole business is making money by managing others people money, consequently I do imagine that they estimate that whatever they put online is safe enough and insured enough not be pragmatically speaking creating any risk for their consume. I imagine, and maybe naively so, that it’s a well enough regulated business so that if “shit happens” it’s on the bank to cover, not the customer.



  • If I need more installation I can install Aurora back. I do not know how frequently you install apps for me it is very, once a month at most.

    Regarding critically typically apps do warn you when it’s the case, including financial apps. Usually if it’s truly critical they’ll stop working until you do update.



  • Ordered by preference, cascading down when it’s not present

    • F-Droid : I’m used to it and know it relatively well
    • Accrescent : comes from GrapheneOS but very few apps
    • Obtainium : works well, very interesting principle, but limited shared configuration
    • .apk from Website or repository : no reviews so have to do due diligence, updates also manual but just works
    • Aurora : that’s my ultimate fallback. I install it, use anonymous mode then uninstall it.

    And yes FWIW I do believe obtaining apps for GrapheneOS is the most challenging part. Installing it with the Web installer was trivial. Using it is great, very convenient. Getting apps which are not in F-Droid, not straightforward.





  • Yes, they do. Most users, even young kids, are freaking out when you tell them anybody at Facebook (or Microsoft, or Google, or whatever, or whomever they delegate access to, can be school superintendent, boss, sysadmin, etc) can access their data. They either don’t know about it, or knew about it once but decided it wasn’t “right” enough to keep in mind and ignored it since.

    Most users DO care and are concerned but they are so convinced there are no possible alternatives they convinced themselves no matter how terrible it is, there is just nothing they can do about it.

    Please ask around, take a random person, close or not, stranger or not, technical or not, and ask them (explain if you most) if they do have such concerns. I bet they do. If they don’t I’ll apologize for my naivety.


  • A lot of already great advice here, often clarifying that a computer that is not yours… is not yours.

    What I would still add though is that you are NOT, and I’m very confident in saying this, the only one there, in your very school, to ask that question. In fact I would argue MOST users have the exact same concerns but they might even be aware that alternatives exist.

    So… do not push back, or even just avoid, all this alone. Find others who have similar problems and solve them together.

    There might be a Linux User Group already, join them. If there isn’t one, consider making it. It might just be you for few weeks, even month, but at least you will dedicate time and space to improve YOUR situation. Chances are though that others, even if only curious at first, might check what you are up to, if they can replicate that, etc.

    Don’t feel isolate, move the needle for yourself first, in your corner, but be welcoming to others who are eager to contribute.

    It’s a challenge, but it’s a fun challenge while trying to tackle it with others.