Comments by "Anony Mousse" (@anon_y_mousse) on "Discord Tried To END This Reverse Engineered Server" video.

@SkyyySi Did they disassemble any binaries to figure out how it worked? If it was using something that was already open or if it was packet sniffing I wouldn't call that reverse engineering. But if they disassembled some official client, then yes.
7
Agreed, they should just keep using that name and give Discord the middle finger.
6
@ursa_solaris No trademark, no patent, no copyright, no legal battle. I'd get a lawyer on contingency and counter sue for court fees if it even required going to court.
4
@shock59 Is the Discord client open source? Did they fork it? Did they try to implement their own that used the same API? If it's not open source, how would they have copied it? If they reverse engineered a closed source binary, then legally there's no problem. If they merely implemented a client using the same API then there's no problem. And if they forked something that was already open source, then there's still no problem. The only way they should have a problem is if it's a "source available" program with a restrictive license.
3
@kmemz Except that doing it that way is not reversing someone else's engineering, it's doing all new engineering of your own.
3
@christopheriman4921 So you're saying nothing should be called reverse engineering? Or you're attempting to suggest an extreme position you don't even agree with just to play Devil's advocate?
3
@ursa_solaris That I agree with, open standards should be required.
2
That's a really good one.
2
I don't know if anyone here used to use it, but Yahoo Chat was fun back in the day. There were at least 100 chat clients that used Yahoo's servers and they were constantly having to update due to changes in the security functions that Yahoo used. They did not like third party clients at all. It may have been written in Python, but Zinc was definitely the best client. I don't remember if it was a fork or reimplementation of Curfloo which became Curphoo, but I loved it either way. As for GUI clients, I did kind of like YahElite, it ran decently through WINE too.
1
@dealloc Yeah, did you?
1
@generallyunimportant If you can read the disassembled code then nothing is closed off from you, but it's more about the licensing than the form it comes it. Generally that'll mean that it's easier to deal with if it's open source.
1
@trustytrojan Which tells me that you missed my point.
1
@christopheriman4921 That's like saying there's no need to differentiate between a rectangle and a square. Maybe for most instances it won't matter, but when you've got a rectangular hole and a square panel, you'll come up short.
1
@christopheriman4921 I was really just comparing the shapes, not going for some analogy over generality versus specificity. Do you know why manhole covers are round?
1
@speedytruck A CPU is basically a binary as a piece of hardware. Software doesn't need reverse engineering if it's open source, otherwise it's just a synonym for binary. And you don't reverse engineer an API, in this case it'd be the protocol. If you're figuring out the API, it's because you're reverse engineering a binary.
1
Truthfully, this sounds like a rather elitist complaint. Not everyone grew up with English as their first language, nor were they formally taught how to speak and spell it. Even amongst those that were, they might have different brains that deprioritize spoken language over better language skills with programming.
1