WinterMute and censoring of people trying to help other people

Eggman making a call-out post on his twitter.com (2018, colorized)

I seriously can't wrap my head around why he deleted your posts. You were just trying to help.

He's an asshole, that's why.

WinterMute is an SJW.
He gets offended when he sees people using or preserving older versions of devkitARM and other devkitPro stuff, and he apparently hates facts and truth as well.
Think of a particular version of DKA as someone's opinion or preference. You respect that person for his/her opinion, not attack him/her for it, just because it doesn't match up yours.

I get trying to push people to use the newest builds of things because they typically have more of the bugs squashed but it ultimately should be encouraging people to do it wherever possible, not censoring people. Even companies like Microsoft know this and however much they try to push people to new versions, they know full well that jumping to a new version isn't always possible. If he can't make the software 100 percent backwards compatible (I realize that's a gigantic ask) he shouldn't push people to the extreme he does. If it was, we might be having a different conversation.

He banned me from his org's github repos for fixing SSL, after he refused to do so for almost a year Thin skinned and petty indeed.

I got blocked from his twitter cause I told him to take backups of the website.
aka something a basic server manager needs to do

Came once for help to him for info working on a reboot and code-redirect feature for NDS. He was an ass about it. He even used "we don't really care" to make it like he spoke in the name of the whole community. Never liked him.

I respect his work and often there is a better solution to problems other than what people suggest but he is an ass and goes way out of his way to censor everything that could even remotely lead to support requests. If he doesn't want support requests he should not be maintaining a toolchain. devkitPro is literally the only existing provider actively deleting and censoring links to old toolchain versions. Other providerss don't give a fuck.

I hate to say it but keep archiving old versions and spread them.

The thing is, the dKP team doesn't officially support old versions, nor do they allow them to be distributed (while everything is FOSS, most rehosts include the dKP name and logo, which is a registered trademark and needs to be stripped out).

If your bug can be fixed by using a newer version, then that is what you should use.

Removing old builds and stopping people from advising to use old versions is an entirely sensible choice in this light.

Would you like to waste hours on old toolchains with breaking changes, or would you like to ask your questions about the latest, supported toolchains on the official channels?

Feel free to keep your old toolchains if you don't want to fix your "works for me" setup; just don't ask for help or plaster the devkitPro name or logo on them. If something broke between the old version and the next version, ask your question on the official channels. Isn't it annoying when you fixed something, but you get a ton of support requests that something is still broken?

It's fine if you like to keep the older toolchain version; just strip out the devkitPro name and don't nag WinterMute about it. I don't think you want to talk to him anyway if you are using an older toolchain version due to his behavior.

Ev1l0rd said:

most rehosts include the dKP name and logo, which is a registered trademark and needs to be stripped out

Click to expand...

Did they actually register it? Last time I checked US, UK and EU trademark databases and got back nothing. You have to actively register and maintain such things (there is minimal automatic protection like there is for copyright or inherent protection like aspects of trade secrets), and minimal recourse available in most places (especially if rehosting unchanged releases is the only thing done) if you have not registered it.
Can't link to searches on most of them but feel free to replicate it by tapping in devkitpro, dkp, devkitarm, devkitppc and so forth into them.

https://trademark-search.marcaria.com/en/Result?trademark=devkitpro&country=EM&status=1&mode=1
https://trademarks.ipo.gov.uk/ipo-tmtext
http://tmsearch.uspto.gov/bin/gate.exe?f=searchss&state=4806:v8q43a.3.1

Do I need to also check Canada, Australia and other such places?

@FAST6191 - To be exact, I did some research. WM is British (according to his Twitter), which has a law that forbids an act called "passing off". I assume that this is the law that WM is referring to when talking about the devKitPro trademark, as it is not needed to register the trademark to file a "passing off" suit.

https://en.wikipedia.org/wiki/Passing_off

Relevant cut-out:

Wikipedia said:

The law of passing off prevents one trader from misrepresenting goods or services as being the goods and services of another, and also prevents a trader from holding out his or her goods or services as having some association or connection with another when this is not true.

Click to expand...

of course, IANAL

> Removing old builds and stopping people from advising to use old versions is an entirely sensible choice in this light.
Not if you just want to do a simple change to a string of text (for example, translation)

Please read the thread I linked above @Ev1l0rd (also, do pings work in blogs? Last time I checked, they didn't)

I mean if you wanna change a string your hex editor of choice will often do (which will not work if the new string is bigger than the old one). I remember commenting a thread where this argument was brought up.

@maorninja - It does still make sense.

These old versions were distributed with the trademark of dKP (as described before, they do have something enforceable and since trademarks get lost, registered or not, if you don't protect them they kinda have to plus from what I have seen of these threads it seemed like they were distributing the windows installer exes which have the name and logo of dKP). If it was distributed without any usage of the names and logos of dKP, then you'd be in the right.

And yes, if they have the control over a support venue that is officially linked to them, stopping people from giving support they don't support is a sensible action, because otherwise you're not properly following the rules and guidelines you have set.

It'd be like someone asking for piracy here and then getting angry because their post is removed by the mods because its against the rules and putting out the argument that "the rules are only for the mods". I hope you recognize how insane that sounds.

Secondly, homebrew devs should just flat out update their tools to work with the latest devKitPro.

They could just say "No support for you because you are using an outdated version. Please update." but they don't. Instead they resort to removing/censoring where they can. Look i think updating old code is the right thing but at the same time i can't stand their behavior.

> Secondly, homebrew devs should just flat out update their tools to work with the latest devKitPro.
And yet, 99% of the time they left the scene, letting their homebrew to rot. If someone wanted to do a simple change that has more characters than the old one (for example, apparently (I don't speak dutch so I have no idea if this is true. I'm basing myself off Google Translate), Dutch words are, like, 2x the amount of characters than english words), they have to redo everything?

and yeah, as ghjfdtg said, they could tell old users to update rather than removing their history