Cordless Project Closes Down • Hacker News Board

Re: Cordless Project Closes Down

#11

Post by iAmir » Mon, Nov 23, 2020, 10:24 PM UTC

as a contributor, this is a very sad thing to happen, there should be at least a way to submit custom clients and digitally sign them so Discord can allow using those that are accepted

Re: Cordless Project Closes Down

#12

Post by polyzium » Mon, Nov 23, 2020, 10:45 PM UTC

iAmir wrote: post #11

as a contributor, this is a very sad thing to happen, there should be at least a way to submit custom clients and digitally sign them so Discord can allow using those that are accepted

I'm the contributor regarding the VTxxx stuff. I agree with your idea, considering the fact that Discord uses Electron which is just sandboxed Chromium, which uses quite a lot of RAM. For a product marketed towards gamers (or at least was), this is not good. What a shitty reality. I wish I can go back to TS3 and its Qt client... oh well, we have Mumble anyway.

Re: Cordless Project Closes Down

#13

Post by swiley » Tue, Nov 24, 2020, 2:19 AM UTC

Fucking hell, I'm using finch to handle discord notifications on my pinephone from my girlfriend. If discord starts enforcing the no 3rd party client thing I'm dumping it.

Re: Cordless Project Closes Down

#14

Post by RyJones » Tue, Nov 24, 2020, 2:38 AM UTC

james_pm wrote: post #10

vertis wrote: post #9

It really is time to start a push to move open communities to open source software. Running a whole bunch of open communities out of slack and discord has always surprised me. Slack is particularly bad with making anything longer than 10k messages inaccessible. The amount of internet history being lost in these groups is boggling.

The message history is all there, held hostage by Slack. Clearly it's not a burden for them to store it or they would simply delete everything past 10,000 messages rather than still storing it and reminding me frequently that they have it if I ever decide to pay.

If you’re an owner of a slack instance, you can export all of the history without paying.

Re: Cordless Project Closes Down

#15

Post by fuzzybear3965 » Tue, Nov 24, 2020, 3:07 AM UTC

swiley wrote: post #13

Fucking hell, I'm using finch to handle discord notifications on my pinephone from my girlfriend. If discord starts enforcing the no 3rd party client thing I'm dumping it.

finch?

Re: Cordless Project Closes Down

#16

Post by lights0123 » Tue, Nov 24, 2020, 3:16 AM UTC

raspyberr wrote: post #6

high_priest wrote: post #4

Ok, but why? Is it about the "no custom clients allowed" part of ToS?

Your question is literally the first thing answered in the README...

> I got banned because of ToS violation today

No? The part of the ToS was never mentioned.

Re: Cordless Project Closes Down

#17

Post by sseagull » Tue, Nov 24, 2020, 3:35 AM UTC

fuzzybear3965 wrote: post #15

swiley wrote: post #13

Fucking hell, I'm using finch to handle discord notifications on my pinephone from my girlfriend. If discord starts enforcing the no 3rd party client thing I'm dumping it.

finch?

I'm guessing the ncurses-based IM client based on libpurple (in other words, the text-based version of pidgin).

Which I used quite a bit when that kind of thing was more useful

Re: Cordless Project Closes Down

#18

Post by monsieurbanana » Tue, Nov 24, 2020, 4:36 AM UTC

lights0123 wrote: post #16

raspyberr wrote: post #6

Earlier quoted context omitted.

Your question is literally the first thing answered in the README...

> I got banned because of ToS violation today No? The part of the ToS was never mentioned.

But... context...

The rest of the first paragraph also make it pretty clear he was banned because of cordless.

If you're still not convinced, the author added later in the readme:

> WARNING: Third party clients are discouraged and against the Discord TOS. There have already been cordless users that got banned, including me (Bios-Marcel, the maker and maintainer)

Re: Cordless Project Closes Down

#19

Post by spockz » Tue, Nov 24, 2020, 5:58 AM UTC

xemdetia wrote: post #7

kordlessagain wrote: post #3

Earlier quoted context omitted.

What is sad is that we have another corporate entity acting aggressively to user-centric efforts.

It's frustrating too because both Slack and Discord fail to adequately provide either multi-account or at least multi-client on the same host in a nice way. Because of the Slack workspace/Discord server sprawl I always run into a situation where I want to login to the community/people/work that I am focused in but some days you just need to be in two different scopes at once.

The only solution I have is to run Rambox. Sadly that just uses whatever browser variant there is so no access to better codecs for teams/discord.

Re: Cordless Project Closes Down

#20

Post by ReactiveJelly » Tue, Nov 24, 2020, 5:59 AM UTC

RyJones wrote: post #14

james_pm wrote: post #10

Earlier quoted context omitted.

The message history is all there, held hostage by Slack. Clearly it's not a burden for them to store it or they would simply delete everything past 10,000 messages rather than still storing it and reminding me frequently that they have it if I ever decide to pay.

If you’re an owner of a slack instance, you can export all of the history without paying.

Export to what? Can I import it into Matrix?

I assumed all these SaaSS products are built like carnivorous plants - The spikes only point in.

I tried the data export from Asana once and it was useless.