Comments by "Winnetou17" (@Winnetou17) on "Louis Rossmann" channel.

  1. 24
  2. 17
  3. 13
  4. 13
  5. 12
  6. 11
  7. 11
  8. 10
  9. 10
  10. 7
  11. 7
  12. 6
  13. 5
  14. 5
  15. 4
  16. 4
  17. 4
  18. Hey Louis, thanks and congrats for all the work you do, especially this thing: contributing for a common sense law to be passed, aka working for a better world. Now, I feel the need to express some things: 1) Even though things like the right to repair don't have much sense to be something to be taken into account just on a local scale, I do feel that the senator is entitled to ask anyone from where it is, even if it sounds totally dumb. For all they care maybe the people from Nebraska actually don't want this law, but somehow a lot of people from other states come to plead for it. Surely there can be nebraskians found to come and plead so this is no longer an issue. 1.a) When the senator had nothing to good to say about that satisfied customer from Nebraska... I see that as perfectly normal. He is not there to congratulate anybody. It's normal, given the time constraints, to only ask/talk only about the things that he doesn't like/know etc. I'd say, if all he had to say/point was a stupid argument, then all for the better, as that seems that everything else was ok, and that stupid argument can be cleared with ease. 2) In general I think that in order for a law to be passed, or at least for it to pass further, after this kind of talk (I don't know exactly how it works in US, I'm from Romania), the senators DO have to ensure that all aspects are taken into account. You can think of them to be the devil's advocate. However a dumb question might be asked, you guys should be prepared to answer it so the thing you're pleading for is without a benefit of a doubt good/better for all people, especially law and politics people. Think of them being like "ok, so you want this law that seems pretty common sense. But, you know there's big companies (or anyone else for that matter) that might not want that, and we're not technical enough to call bullshit on their part. How will you tackle this?" Aka is your job to provide as much evidence as possible that this will have no secondary effects or unforseen situations or abusable situations or affect unrelated parties etc. And that the things affected are with a reason (repair right will lower Apple's income, but will provide the consumer their right of ownership over the bought part or their human right dunno). It does sound a little like you'll have to do their work, but ... such is life. 3) As AkolythArathok said in this comment section, there needs to be a more serious pose. Talking about Repair Family is kind of distracting from the point aswell. Or things like "hey I have here a customer which is so happy, yay!". You actually did her job here with very clearly and shortly/on point saying "we do data recovery for which the customer has no option to do at the manufacturer, for any amount of money". That is how I think a point should be made. All in all, it was kind of sad, but totally not surprising to see this. And I have to congratulate for your speech. It was very on point, with clear arguments and examples. Now all you have to do for next year is to have everybody supporting this be as efficient and articulate as you :) And have everybody be able to totally demolish all (dumb) counterarguments presented here. And as you very well observed, to have this lobbying prior to the talk. The talk is just a showcase.
    3
  19. 3
  20. 3
  21. 3
  22. 2
  23. 2
  24. 2
  25. 2
  26. 2
  27. 2
  28. 2
  29. 2
  30. 2
  31. 2
  32. 2
  33. 2
  34. 2
  35. 2
  36. 2
  37. 2
  38. 1
  39. 1
  40. 1
  41. 1
  42. 1
  43. 1
  44. 1
  45. 1
  46. 1
  47. You can't call something the "greatest OS of all time" if it doesn't work in the majority of devices (phones in this case) on the current landscape. Fight me! For real though, I want it, but don't want to buy a Pixel phone, neither new nor SH. And saying it's supported just on Pixel because it has extra hardware security features - bullshit! I mean, I don't challenge that it's not, but I want to point out that it's a very stupid argument. Maybe in alpha and pre alpha stages it would be ok. But on the full release, it's MUCH MUCH more important to have people onboard and even with just like 90% of the privacy and 50% of the security (and still much better than what the original phone has) than to have only one line of phones that limit the exposure to 10% of the potential users. That's bad prioritisation at this point. At least if they care more about raising the global security and privacy. It's not an easy decision to make, and I can't fault them, I'm just saying what I think would be more important (maybe a bit in a harsh matter, but, meh). I do think a lot of people would rather actually be able to use Graphene on their current phone, without the full security suite, than to have the Graphene OS team develop 3 security features extra, but keep the Pixel limitation (which means that people have to wait more until they try it, or switch to a Pixel phone - and maybe lose some features, like Louis does now) Other than that, I agree, it's awesome! Won't try it on a Pixel, sorry. Can't wait for it to become more popular and branch into other models, hopefully Fairphone and Pinephone.
    1
  48. 1
  49. 1
  50. 1
  51. 1
  52. 1
  53. 1
  54. 1
  55. 1
  56. 1
  57. 1
  58. 1
  59. I think that what they wanted to avoid (but put 0 effort into explaining it) that's actually understandable, is using the CT to be used as a home battery a lot, and still try to have the 8 years of warranty, because you're driving 0 miles, but degrade the battery as if you drove 1,000,000 miles in those 8 years, then ask for a replacement after 7.5 years. 1,000,000 miles sounds too much ? Let's do some math if it's possible. Let's assume that the battery has 100 kWh energy capacity. It's good to not use 0% to 100%, so let's say the usable capacity is 60 kWh. 11,5 kW, means that if full, it will discharge in, say, 6 hours, rounding up a bit. If recharging from 20% back to 60% again, it would mean it needs 10 hours just for the discharge part to cover 100% of the battery capacity. That means it's totally doable to have a full charge-discharge cycle in a day. Also, that would be like driving about 300 miles What does 7 years mean in terms of days ? 7 * 365.25 = 2556.75 days. Let's round that to 2500 So, 2500 days means potentially 2500 battery cycles. I read somewhere that they officially said that their batteries can be used for 1500 cycles. So that's already over the limit. Also, 300 miles * 2500 = 750,000 miles. Ok, so I was off, but it's still 5 times over what they would've covered, if you used it to drive, not to power a home or whatever. And it is over its expected life time. To put it in another way, 150,000 miles would mean it only needs 150,000/300 = 500 cycles, about 1/3 of the battery lifespan. Still doesn't excuse what they wrote. Or Elon being a gigantic jerk that needs to be jailed, along with the many people that enabled him to go this far.
    1
  60. 1
  61. 1
  62. 1
  63. 1
  64. 1
  65. 1
  66. 1
  67. 1
  68. 1
  69. 1
  70. 1
  71. I agree that the supply chain is the motive that they cannot repair in a reasonable timeframe. BUUUT, it's completely their making, their choice, their problem, their mistake for having this. I do not see this as a good enough argument. Legislation should not care about this. If you can produce new cars, then you should be able to provide parts for the SAME FREAKING CARS. If you have "very lean supply chain" that's a you problem not a me problem. Overall, I think that a legislation stating that whatever you make, you cannot have license to sell unless you can provide service in a timely manner and provide replacement parts in a timely manner (I know, I know, timely is too subjective, I'm only saying the idea). If you do not provide them, then you are forced to release the schematics for the product and all of its parts. In case of service, those who still have warranty should be able to get a full refund. If you do not have the ability to fully provide the schematics for the product and all of its parts, then you cannot get the license to sell, easy. Ok, I know what I wrote above is currently impossible. Some parts cannot be made inhouse and also cannot be had with schematics, as they're 3rd party vendors who do not care. In this case there can either initially be made specific exceptions and b) longer term - the manufacturers of those parts be liable under the same as above, if they don't provide the parts for general sale, then they are forced to release the schematics. I think that in both cases, when aquiring a license to sell, the schematics should be provided upfront to the a government entity. So when needed, the schematics can be made public without interference or possible "accidents" from the original company. You know, sometimes I cannot not think how far we'd have reached if we weren't so petty. What I described above is so much extra work just because we cannot have common sense and a bit of moral integrity to not steal and profit from others. Sigh
    1
  72. 1
  73. 1
  74. 1
  75. 1
  76. 1
  77. 1
  78. 1