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

help-circle










  • The one group I can think of that actually tests burn in is rtings and they do that for TVs and monitors.

    Phone reviewers just cycle through multiple phones so are the least reliable not using one phone as often or as long as regular people. Especially even more now that how long people retain phones has gone up with price increases.

    Which actually has me wondering. How long do you typically use phones. Some upgrade every year. Some every 2. I’ve upgraded maybe on average 3 years or longer. So long it was the reason I shifted to custom roms in the past as security updates stopped. And getting nav burn taught me to try things like auto hide it.

    I still have a oneplus 6 I use as a back up which is a phone that came out 7 years ago. Not sure how many years I’ve had it, but that’s got burn in couple years ago. Do you use phones that long?


  • During normal use I wouldn’t notice until I started reading webtoons and manga on my phone which shows a lot of white color that you don’t typically see. And that’s when I’d see the burn in my screen had picked up.

    As for why there is more fuss about monitors than phones is because people use monitors for many more years than phones. And can use them for many more hours with lot of static elements with sometimes one program being used day in and day out. Its same reason why there is less talk of burn in for TVs versus monitors where TVs are more likely to have constantly changing visuals than monitor use case.



  • Even when well meaning sometimes malicious code can slip through like with smarttubenext due to a compromised machine.

    So I think people forget that just because something is foss doesn’t mean it is automatically safe and caution can be thrown to the wind. Skepticism and being overcautious is still good practice before installing things.

    I like to wait a while before installing new updates just to see if anything is caught by the community to try to reduce potential risk.


  • It’s just the process of the handover that is making people skittish with the github going private then reappearing with a new maintainer.

    I think best route would have been for researchxxl to just fork syncthing-fork to put on F-droid, and catfriend1 just leave their branch archived with an endorsement of researchxxl.

    After some time passes and researchxxl gains trust in the community I’m sure people will trust their work. The transition just wasn’t handled well.