This project cannot die. Not like this.

[TheOPtimal]

The whole point of free software is to resist these proprietary companies and be free. However, when a company like Discord is able to shut down a FOSS project contradicting them, it's extremely bad.

Isn't the whole point of free software to take away control from the companies and put it in the hands of people? If Discord can just shut down the project like this, then that means that they took control. And that we as a community, have failed in our efforts.

This cannot be the end of cordless. One of the best 3rd party Discord clients just getting shut down by Discord for violating ToS. The project already violated ToS, and ToS is enforced. What were people thinking? If you use a 3rd party client, you get banned.

But we as a community need to take that risk. We're fighting for freedom in software, and we can't succumb like this. At least not this simply.

This project was the first step of the death of Discord, because Discord is in itself a proprietary platform. However, we know that most of our friends and relatives will stick to Discord no matter what, because of Discord's "gamer" attitude. This project was kind of a way out of that, not quite but still close.

A project like this can't end. At least not like this.

[Hual]

reddit is that way, this platform is for software issues

[Bios-Marcel]

@TheOPtimal I partially agree with you, but Discord owns the APIs and the infrastructure. It's not like cordless was a standalone platform with both backend and frontend that was struck down by Discord. And technically I could keep cordless going, the reason I was banned was most likely an access to the DM endpoint. However, I don't neccessarily want to risk getting more people banned. Either way, I will keep the repository up and maybe archive it in the next days.

[0neGal]

Just to clarify if you were to remove all DM related parts of Cordless would it (in theory) stop the bans? Or am I missing something.

Also if you don't mind is there any way to disable the warning pop up? Whether through a config or where it is in the source code.

I'm considering just being on alts for most things and continuously using Cordless, as I like most people, can't stand the official client.

[AkiAfroo]

I never thought Discord would do something like that.damm !

[0neGal]

Tbh, I see a lot of reasons for Discord doing this but at the same time, why now? Imagine if Discord made their own official API, dahm... That'd be a dream world.

I sure as hell ain't going back to a 300-400mb app that's one thing I can guarantee you that.

[Bios-Marcel]

@0neGuyDev The warning popup is cordless. That was my way to officially discontinue package manager installations. Sorry for that.
And yes, assuming that the DM endpoint is the culprit, then it would solve the risk. But that doesn't mean, that the same issue wouldn't happen with a different endpoint tomorrow. And as discord doesn't communicate with me, I simply can't know this.

[0neGal]

It's also weird how in the past Discord used to handle these things by making issues and pr's on repos (Notably an employee who goes by Night) telling the owner's how to handle the issues, and then letting everything settle down, apparently not this time.

The warning popup is cordless.

So there's no way to remove it? That's really what I was asking about.

[Bios-Marcel]

Correct. Just use the precompiled binaries from the releases section or self-compile. Both works just fine and just like before.

[AkiAfroo]

just to be clear, we can or can not keep using cordless ? i have setup corless in raspberry pi 3b+ and was/is perfect.

[Bios-Marcel]

You can and will ever be able to do whatever you want with the source code or your already compiled binaries.

[0neGal]

Got clone the repository locally

Run go build and then mv cordless /use/bin that'll compile it.

Even tho the README said how to do this already.

Also remove the package from my package manager first.

[garrett-hopper]

@jasoncitron, @vishnevskiy, @night, what would it take for a project like this to be officially sanctioned?

[JBlocklove]

This is a real bummer, but at least what we've got so far will still work. Maybe someday they'll decide they're okay with it and it will come back, but until then thanks for the amazing program @Bios-Marcel!

[Titaniumtown]

This is so sad

[normen]

Its sad but really, if they don't say anything then everything is as before. Sure you got a ban but you probably also had to try around a lot while developing, causing some erroneous requests to their API, thus triggering some bells in their control room. Really I think all of this is still well under their radar in the sense of "we gotta stop this".

Idk if giving up so quickly is warranted - of course its a personal decision. But maybe somebody else wants to pick up the work in case @Bios-Marcel really doesn't want to continue working on this anymore?