• 0 Posts
  • 112 Comments
Joined 1 year ago
cake
Cake day: August 4th, 2023

help-circle





  • That’s why Pixels and some others have a “smart charge” feature that will wait to charge your phone until just before your alarm time so that it will finish right before you take it off the charger.

    why am I going backwards to needing to babysit my phone when it’s charging, and why would anyone want to charge their phone when they want to be using it vs when they’re asleep?

    I honestly don’t understand why people have such trouble with this. I can throw my phone on a charger when I go to shower and it’s at 80 percent when I get out, and that’s enough for my day. I could leave it while I get dressed and eat or something and it’d be at 100 if I needed. I don’t need my phone 24 hours a day. And there are many points in my day where I’m not using my phone for an hour that I could spare to charge it. I don’t need to leave it burning away permanent battery capacity for hours and hours every night.


  • Yes, the battery doesn’t charge to “dangerous - could explode” levels. But they very much do still charge to levels that are damaging to long term health/capacity of the battery.

    Yes, they tune the batteries so that 100% isn’t the absolute cap. But even with that accounted for, many batteries will be above values that would be considered good for the long term health of a lithium cell. 80 percent on most phones is still very much at levels that are considered damaging to lithium batteries.

    To put it another way, the higher you charge a lithium battery, the more stress you put on it. The more stress you put on it, the fewer charge cycles those components will hold. It’s not like there’s a “magic number” at 80 percent, it’s just that the higher you go the worse it is. Yes, some manufacturers have tweaked charge curves to be more reasonable. But they’ve also increased limits. Many batteries now charge substantially higher than most people would consider sustainable.

    And after such changes, 80% lands pretty close to the general recommendations for improved battery longevity. Every percent will help, but it’s not a hard and fast rule.

    Calibrations have gotten a little better in some ways, but all you have to do is look at basic recommendations from battery experts and look at your phones battery voltage to see that almost every manufacturer is pushing well past the typical recommendations at 90 or even 85 percent.



  • Can’t answer the rest of your question because I don’t use a one plus but:

    aren’t you supposed to charge the phone overnight?

    No, you aren’t “supposed” to charge your phone overnight. Leaving your phone on the charger at 100% is actually pretty bad for long term battery health. Hence why the notification exists in the first place. Modern phones also full charge in like an hour, so this leaves your phone in that state for many hours.

    The longer story is it’s actually best to stop charging your phone at 80 percent unless you really need the extra juice, because any time your phone spends above that is potentially damaging, but that tends to be hard to deal with for most people.

    Most of the phones I’ve seen with this feature have a “battery warning” or “charge notification” or “protect battery” type setting somewhere you can turn off. But again, I’ve never used a one plus so Idk if they do or where it is.


  • I had a programmer lead who rejected any and all code with comments “because I like clean code. If it’s not in the git log, it’s not a comment.”

    Pretty sure I would quit on the spot. Clearly doesn’t understand “clean” code, nor how people are going to interface with code, or git for that matter. Even if you write a book for each commit, that would be so hard to track down relevant info.



  • As an introvert, as much as I feel weird aroind people, I feel even weirder video chatting with people I’ve never met in person. In that situation, I have no idea how to read people and the expectations are way harder to try to meet. This makes meetings even worse until I meet them.

    While I agree that forced in person work daily is insane, the OP is complaining about meeting people in person once after many years, which feels equally as ridiculous. IMO even for widely dispersed teams, meeting a few times a year seems ideal.



  • I’m actually shocked to find how many people agree with the OPs sentiment, but maybe there’s something about the demographics of who’s using a FOSS Reddit alternative or something. I’m not saying everyone is wrong or has something wrong with them or whatever, but I entirely agree with people finding this valuable, so maybe I can answer the OPs question here.

    I’ve been working remotely long since before the pandemic. I’ve worked remotely for multiple companies and in different environments. I am extremely introverted and arguably anti social. I tend to want to hang out with many of my friends online over in person. But that doesn’t mean I think there’s no advantage at all. To be honest, when I first started remote work, I thought the in person thing was total bullshit. After a few meetings my opinions drastically changed.

    I’ve pushed (with other employees, of course) to get remote employees flown in at least a few times a year at multiple companies. There are vastly different social dynamics in person than over video. Honestly, I don’t understand how people feel otherwise, especially if they’ve experienced it. I’ve worked with many remote employees over the years and asked about this, and most people have agreed with me. Many of these people are also introverted.

    I think one of the big things here is people harping on the “face” thing. Humans communicate in large part through body language - it’s not just faces. There’s also a lot of communication in microexpressions that aren’t always captured by compressed, badly lit video. So much of communication just isn’t captured in video.

    Secondly, in my experience, online meetings are extremely transactional. You meet at the scheduled time, you talk about the thing, then you close the meeting and move on. In person, people slowly mosy over to meetings. And after the meeting ends, they tend to hang around a bit and chat. When you’re working in an office, you tend to grab lunch with people. Or bump into them by the kitchen. There’s a TON more socializing happening in person where you actually bump into other people and talk them as people and not just cogs in the machine to get your work done.

    I find in person interactions drastically change my relationships with people. Some people come off entirely different online and it’s not until meeting them in person that I really feel like I know them. And then I understand their issues and blockers or miscommunications better and feel more understanding of their experiences.

    Maybe things are different if you work jobs with less interdepencies or are more solo. I’ve always worked jobs that take a lot of cooperation between multiple different people in different roles. And those relationships are just way more functional with people I’ve met and have a real relationship with. And that comes from things that just don’t happen online.

    Im honestly really curious how anyone could feel differently. The other comments just seem mad at being required to and stating the same stuff happens online, but it just doesn’t. I do wonder if maybe it has to do with being younger and entering the workplace more online or something. But I’ve worked with hundreds of remote employees and never heard a single one say the in person stuff to be useless. And I’ve heard many say exactly the opposite.




  • No, this does actually sound like a solution. But it’s a solution that should be scattered all throughout the process, and checked at multiple steps along the way. The fact that this wasn’t here to begin with is a bigger problem than the “client library failure” as it shows Wyze’s security practices are fucking garbage. And adding “one layer” is not enough. There should be several.

    To give a bit better context, which I can only be guessing at by reading between the lines of their vague descriptions and my first hand experience with these types of systems…

    Essentially your devices all have unique ids. And your account has an account/user ID. They’re essentially “random numbers” that are unique within each set, but there appear to be devices that have the same ID as a some user’s user ID.

    When the app wants to query for video feeds it’s going to ask the server “hey, get me the feed for devices A, B, and C. And my user ID is X”. The server should receive this, check if that user has access to those devices. But that server is just the first external facing step. It then likely delegates the request through multiple internal services which go look up the feed for those device IDs and return them.

    The problem that happened is somewhere in there, they had an “oopsie” and they passed along “get me device X, X, X for user ID X”. And for whatever reason, all the remaining steps were like “yup, device X for user X, here you go”. At MULTIPLE points along that chain, they should be rechecking this and saying “woah, user X only has access to devices A, B, and C, not X. Access denied.”

    The fact that they checked this ZERO times, and now adding “a layer” of verification is a huge issue imo. This should never have been running in production without multiple steps in the chain validating this. Otherwise, they’re prone to both bugs and hacks.

    But no, they clearly weren’t verified to view the events. Their description implies that somewhere in the chain they scrambled what was being requested and there were no further verifications after that point. Which is a massive issue.


  • It doesn’t even need to go that far. If some cache mixes up user ids and device ids, those user ids should go to request a video feed and the serving authority should be like “woah, YOU don’t have access to that device/user”. Even when you fucking mix these things up, there should be multiple places in the chain where this gets checked and denied. This is a systemic/architectural issue and not “one little oopsie in a library”. That oopsie simply exposed the problem.

    I don’t care if I was affected or how widespread this is. This just shows Wyze can’t be trusted with anything remotely “private”. This is a massive security failing.


  • Amongst many other reasons, my biggest is it’s not searchable by search engines.

    Well gee, I hope you don’t use texting, phone calls, emails, private forums, social media DMs, or talk to anyone IRL, because those aren’t searchable either!

    This argument seems like reaching for something to complain about rather than having a legitimate problem with discord. If anything, you don’t like the “large group chat” paradigm, but that’s like hating a screwdriver because it’s not a hammer.


  • Ottomateeverything@lemmy.worldtolinuxmemes@lemmy.worldditch discord!
    link
    fedilink
    arrow-up
    12
    arrow-down
    5
    ·
    9 months ago

    I think discord is primarily just useful for voice chat, yes.

    But:

    It’s a closed ecosystem that locks what would otherwise be searchable knowledge on the web, with an unsearchable, proprietary lockdown of that information.

    Yeah, no. Proprietary, sure, but you can say that about almost communication mechanism that’s not a website with an API. It’s not like people would otherwise be posting these things somewhere else if discord didn’t exist. If it wasn’t discord it’d be slack or something. Discord is an entirely different medium and complaining that it isn’t a forum is just not a legitimate argument. They’re entirely different things.