4 ms·

You were banned because you would not stop pinging me about implementing multi-floor support. Frankly, you're one of these people that are utterly incapable of

by hypfer 4y ago

You were banned because you would not stop pinging me about implementing multi-floor support. Frankly, you're one of these people that are utterly incapable of accepting a "no" and would rather change the laws of physics then ever admitting that they're in the wrong. It's concerning to say the least. Not to start another discussion here though, but I won't allow you to continue this abuse by attempting to control the narrative.

hdjjhhvvhga 4y ago
I wish you guys both cooled down. One added mutli-map, another refused to merge it. This would be a conflict story 20 years ago, today you just develop your fork on Github and the community takes care of the rest - if many people need multimap, some changes will happen sooner or later. I take the opportunity to thank both of you for your work as I plan to use it as soon as I find some free time to root my device.
- hypfer 4y ago
  I have yet to see someone implement that feature in a non-hackish way that fully works reliably and future proof on all supported robots while also not introducing crippling technical debt that will hurt the project in the long run. All I've seen so far is people greatly reducing the scope by focusing on their single robot with their specific subset of use-case and then saying "hey look it's so easy". Yes, it is indeed easy if you drop most of the requirements. Who would've thought. That said, yes, that's exactly what open source is for. Someone can take the code and add modifications that cater to their specific need. Isn't it great. Anyway, the main issue here is not technical but human: You don't solve trust issues with your proposals by just adding more pressure to whoever it is that you're trying to get to do something for you.
  - aliqot 4y ago
    > I have yet to see someone implement that feature in a non-hackish way that fully works reliably and future proof on all supported robots while also not introducing crippling technical debt that will hurt the project in the long run. Don't let perfect be the enemy of good. BDFL starts with the letter B.
    - hypfer 4y ago
      Well at the end of the day, yours truly will be responsible to clean up that mess. Why would I do that? Why would I consciously move into a situation that will be harmful to me? Also, the project is in a great state with lots of options in regards to robots. If you have multiple floors, just buy a second robot used for 60€ Why add any risk whatsoever just to save 60€? It makes no sense. It's a downright terrible idea to do that.
      - aliqot 4y ago
        I'm saying this to provoke you, and possibly push you toward the light, so please don't take too much offense, but do help yourself to some: Do you have any preference for what the community will call the open fork of your project? I must add a sidenote because I didn't anticipate it reading as such a scathing rebuke as when it was conceived but, your behavior might be earned, you might be the Linus of motor-bins, but like the way you're acting here in front of your target audience is pretty much like every other BDFL who turned on their community. You are blessed that anybody shows any interest in submitting any code to your project, and I'm not saying that means you have to go merging every CoC that lands in your PR's, but I am saying that even though someone may be misguided, or may not share your vision, it doesn't mean they lack the potential to be swayed. obviously you know your stuff on motor-bins, and obviously you're passionate about that. Rather than ignoring and then shunning those who are incongruent in their vision, perhaps you could mentor them on the things you've learned over this time about what makes their idea suck. last but not least, when someone's giving you unsolicited advice that sounds like complete and utter shite, you respond with "thanks, I'll take that into consideration and keep it in mind". The dev equivalent of that is merge it to a branch, let them polish that turd until they succeed or fail, and then you can be validated in both cases and you've not alienated anybody. The way you act today, since I've been here about ohhh 2006ish maybe, is in line with every other BDFL who watched their project flourish as a fork instead. You might be cool with that, idk, we only just met, but if that is something you're cool with, you should be up front about that.
        hypfer 4y ago
fxtentacle 4y ago
Sorry, that was not my intention. I posted the screenshots to the Telegram group because you had written before that you are only interested in seeing forks that bring new ideas. And I thought the fact that I redesigned the map and settings screens to make them more user-friendly would make for an interesting perspective.
deleted 4y ago
[deleted]
fxtentacle 4y ago
I can't believe I got a Telegram message (by a person unknown to me) trying to confront me about this a day later... Everyone, please calm down, our disagreement was merely about communication style! The presumed "abuse" was posting these 2 screenshots https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/master/Screenshot_20221225-213228.png https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/... https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/master/Screenshot_20221225-213236.png https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/... into this https://t.me/+uGuDHt0dNCVmODli https://t.me/+uGuDHt0dNCVmODli telegram group with a polite but lengthy text about which UI changes were made between this fork https://github.com/DeutscheKI/dreame-w10-valetudo-fork https://github.com/DeutscheKI/dreame-w10-valetudo-fork and this master branch https://github.com/Hypfer/Valetudo/ https://github.com/Hypfer/Valetudo/ and what the motivations for each UI decision were. That Telegram group has 1000+ users. But Hyper found it annoying that I @ tagged him in that message. That's it - no need for pitchforks :) Everyone, please calm down, our disagreement was merely about communication style !!!!!one1111oneone!1!!11!one1!

by hypfer 4y ago

hdjjhhvvhga 4y ago

I wish you guys both cooled down. One added mutli-map, another refused to merge it. This would be a conflict story 20 years ago, today you just develop your fork on Github and the community takes care of the rest - if many people need multimap, some changes will happen sooner or later. I take the opportunity to thank both of you for your work as I plan to use it as soon as I find some free time to root my device.

hypfer 4y ago
I have yet to see someone implement that feature in a non-hackish way that fully works reliably and future proof on all supported robots while also not introducing crippling technical debt that will hurt the project in the long run. All I've seen so far is people greatly reducing the scope by focusing on their single robot with their specific subset of use-case and then saying "hey look it's so easy". Yes, it is indeed easy if you drop most of the requirements. Who would've thought. That said, yes, that's exactly what open source is for. Someone can take the code and add modifications that cater to their specific need. Isn't it great. Anyway, the main issue here is not technical but human: You don't solve trust issues with your proposals by just adding more pressure to whoever it is that you're trying to get to do something for you.
- aliqot 4y ago
  > I have yet to see someone implement that feature in a non-hackish way that fully works reliably and future proof on all supported robots while also not introducing crippling technical debt that will hurt the project in the long run. Don't let perfect be the enemy of good. BDFL starts with the letter B.
  - hypfer 4y ago
    Well at the end of the day, yours truly will be responsible to clean up that mess. Why would I do that? Why would I consciously move into a situation that will be harmful to me? Also, the project is in a great state with lots of options in regards to robots. If you have multiple floors, just buy a second robot used for 60€ Why add any risk whatsoever just to save 60€? It makes no sense. It's a downright terrible idea to do that.
    - aliqot 4y ago
      I'm saying this to provoke you, and possibly push you toward the light, so please don't take too much offense, but do help yourself to some: Do you have any preference for what the community will call the open fork of your project? I must add a sidenote because I didn't anticipate it reading as such a scathing rebuke as when it was conceived but, your behavior might be earned, you might be the Linus of motor-bins, but like the way you're acting here in front of your target audience is pretty much like every other BDFL who turned on their community. You are blessed that anybody shows any interest in submitting any code to your project, and I'm not saying that means you have to go merging every CoC that lands in your PR's, but I am saying that even though someone may be misguided, or may not share your vision, it doesn't mean they lack the potential to be swayed. obviously you know your stuff on motor-bins, and obviously you're passionate about that. Rather than ignoring and then shunning those who are incongruent in their vision, perhaps you could mentor them on the things you've learned over this time about what makes their idea suck. last but not least, when someone's giving you unsolicited advice that sounds like complete and utter shite, you respond with "thanks, I'll take that into consideration and keep it in mind". The dev equivalent of that is merge it to a branch, let them polish that turd until they succeed or fail, and then you can be validated in both cases and you've not alienated anybody. The way you act today, since I've been here about ohhh 2006ish maybe, is in line with every other BDFL who watched their project flourish as a fork instead. You might be cool with that, idk, we only just met, but if that is something you're cool with, you should be up front about that.
      - hypfer 4y ago

fxtentacle 4y ago

Sorry, that was not my intention. I posted the screenshots to the Telegram group because you had written before that you are only interested in seeing forks that bring new ideas. And I thought the fact that I redesigned the map and settings screens to make them more user-friendly would make for an interesting perspective.

deleted 4y ago

[deleted]

fxtentacle 4y ago

I can't believe I got a Telegram message (by a person unknown to me) trying to confront me about this a day later... Everyone, please calm down, our disagreement was merely about communication style! The presumed "abuse" was posting these 2 screenshots https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/master/Screenshot_20221225-213228.png https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/... https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/master/Screenshot_20221225-213236.png https://github.com/DeutscheKI/dreame-w10-valetudo-fork/blob/... into this https://t.me/+uGuDHt0dNCVmODli https://t.me/+uGuDHt0dNCVmODli telegram group with a polite but lengthy text about which UI changes were made between this fork https://github.com/DeutscheKI/dreame-w10-valetudo-fork https://github.com/DeutscheKI/dreame-w10-valetudo-fork and this master branch https://github.com/Hypfer/Valetudo/ https://github.com/Hypfer/Valetudo/ and what the motivations for each UI decision were. That Telegram group has 1000+ users. But Hyper found it annoying that I @ tagged him in that message. That's it - no need for pitchforks :) Everyone, please calm down, our disagreement was merely about communication style !!!!!one1111oneone!1!!11!one1!