A random person on lemmy. Banner art from Deemo switch version

Alt lemmy @Deemo@lemmy.world

Alt kbin: @Deemo@fedia.io

FMHY (archive): @Deemo@lemmy.fmhy.ml

  • 1 Post
  • 13 Comments
Joined 1 year ago
cake
Cake day: July 20th, 2023

help-circle






  • I know this isn’t YouTube’s fault but one thing that bugs me about yet premium is when creators dump baked in ads.

    As a user you have 3 options:

    1. Deal with it and manual skip (in a way this feels like skipping commercials on cable tv Dvr)
    2. Get ready to buy a ton of patreon subscriptions (kills the point of getting yt premium).
    3. Get a modded client/ use browser extensions and use sponsorblock

    Now the one exception to this is nebula where like YouTube you pay an all access fee but no baked in ads (I pay for this currently).

    I do wonder if creators had the option to make videos available via YouTube premium only (say early access and no baked in ads). Would more people pay and would creators use this system? (They wouldn’t have to worry about demonetization).

    Curious on your thoughts



  • Few problems:

    1. Safteynet (play integrity) and root detection

    There are magisk tweaks to help combat this but its a annoying game of cat and mouse. Some apps like chase have particularly annoying root detection to deal with. Also regaring safteynet once google fully enforces hardware attestation passing safteynet with tweaks will be borderline impossible (most tweaks try to spoof older phones that don’t support safteynet hardware attestation).

    1. Widevine

    Many streaming services (Netflix, Hulu, Disney, etc) will downgrade your video quality to 480p-540p due to L3 from unlocking the bootloader (a step thats usually required before you can root).

    1. Physical security (potential risk)

    Unlocking the bootloader is the first step to allowing for rooting and custom roms. One pro/con is when you unlock the bootloader you are partially at risk to a evil maid attack (some one with physical acess to your phone can compromise it). While difficult to do automatically (and probably very very rare) some one could hypothetically place a malicious bootloader that could steel data. The risk of this is mostly low but does exist.





  • Actually in your case our school has a BYOD program (bring your own device) in which you can bring your own laptop with whatever flavor of OS. Firewall would restrict you, your device would be considered untrusted, and in testing a loaner locked down chromebook would be provided. The issue comes with non BYOD devices.

    Now lets assume a school has 1k students. If they allowed os unlocking and allowed students to tinker with the os. Then they would need 2k chromebooks 1k unlockable 1k locked down for exam administration (assume the whole school needs to take it at the same time). From a admin/IT perspective why should the school need to pay double the number of chrome books just for a few students to install their favorite brand of linux.

    Even under the best circumstances where support queries aren’t increased (from students softbricking/ not knowing how to use linux) and say they are able to preserve 1k unlockable chromebooks, admins would still need to replace the other 1k locked down chrome books at end of software to stay in compliance with testing software (negating any financial benefit).


  • The problem comes down to education institutions. I remember when we got Chromebooks in my highschool (8 years ago) admins forgot to turn of developer mode and half the school unenrolled the Chromebook managing to bypass all restrictions. This went on for half a year until one day our school needed to run a state exam (more for measure of schools performance not as a college entrance exam or anything).

    The computerized testing program required deploying a specific chrome app accessible when chrome book is logged out (can’t just download from chrome web store). When they tried to push the client since half of Chromebooks were unenrolled it failed. This required the school it to recall pretty much all chrome books to manually re enroll all of them and disable developer mode (prevents unenrolling and prevents sideloading Linux).

    Problem is if older Chromebooks are used for Linux in an educational environment there would be nothing stopping a student from whipping up a bootable USB and dumping another distro (bypassing restrictions). I’m also not sure if there is a enrollment mode equivalent Linux (there may be but not sure).

    At least that’s my two cents (not a school it admin just a memory from the past 😉).