5 ms·

Doesn't using this with Discord run a risk of your account getting banned for using a third-party client? That's why the Cordless developer shut down the projec

Doesn't using this with Discord run a risk of your account getting banned for using a third-party client? That's why the Cordless developer shut down the project: https://github.com/Bios-Marcel/cordless https://github.com/Bios-Marcel/cordless

acct776 6y ago
After a disclaimer, that sounds like a problem between the user and the Discord people.
- jakelazaroff 6y ago
  Yes — I would be the user, and I would like to avoid that problem.
kitkat_new 6y ago
t2bot.io hosts a Discord bridge and to my knowledge it is officially allowed by Discord (else they could not have more than 100+ bridge users). So I imagine there might be the possibility of it being allowed for Beeper as well.
- Half-Shot 6y ago
  t2bot.io uses webhook/bot based bridging which at least doesn't trigger the "no custom clients" clause (as you aren't using any real user account tokens) The broader question of whether bridges are allowed seems to be broadly yes as there are many other bridges out there for Discord (IRC/slack ones) and those haven't been shut down either. I think so long as you aren't abusive, Discord don't care.
stryan 6y ago
They're using HalfShot's appservice bridge I think, which works entirely through the standard Discord API with bot users. IIRC Discord is very much aware of the project. Discord's generally fine with anything using it's API/gateways as long as it's NOT logging in as a "real" user.
- timdorr 6y ago
  Well, that would be what they're doing here, no?
  - Macha 6y ago
    There's two ways to connect discord. One is a appservice. You got a bot user that relays everything and you get messages that are basically "BotUser: <Alice> Hello world" using the official API. This is currently allowed, but doesn't allow access to 1:1 chats. The other is "puppeting", the bot logs in as Alice by Alice providing her credentials and hitting endpoints the actual Web app uses. This results in a less obvious, nicer experience for people on he discord side but is the one that is banned
saagarjha 6y ago
I have yet to see any verbiage in the Discord ToS that mentions this…do they really not read their own legalese?
- brianush1 6y ago
  It's not in the Discord terms of service, it's in the Discord bot API terms of service.
doublerabbit 6y ago
If I can login to your service with the API given, there should be no reason for a ban. And this is what annoys me with today's communication protocols; your forced to enjoy their service only with their provided application. It never used to be like this. MSN messenger,AIM even YIM; they all had FOSS applications.
- aquaticsunset 6y ago
  They didn't start that way though. It wasn't until they were forced to play nice under regulatory action.

acct776 6y ago

After a disclaimer, that sounds like a problem between the user and the Discord people.

jakelazaroff 6y ago
Yes — I would be the user, and I would like to avoid that problem.

kitkat_new 6y ago

t2bot.io hosts a Discord bridge and to my knowledge it is officially allowed by Discord (else they could not have more than 100+ bridge users). So I imagine there might be the possibility of it being allowed for Beeper as well.

Half-Shot 6y ago
t2bot.io uses webhook/bot based bridging which at least doesn't trigger the "no custom clients" clause (as you aren't using any real user account tokens) The broader question of whether bridges are allowed seems to be broadly yes as there are many other bridges out there for Discord (IRC/slack ones) and those haven't been shut down either. I think so long as you aren't abusive, Discord don't care.

stryan 6y ago

They're using HalfShot's appservice bridge I think, which works entirely through the standard Discord API with bot users. IIRC Discord is very much aware of the project. Discord's generally fine with anything using it's API/gateways as long as it's NOT logging in as a "real" user.

timdorr 6y ago
Well, that would be what they're doing here, no?
- Macha 6y ago
  There's two ways to connect discord. One is a appservice. You got a bot user that relays everything and you get messages that are basically "BotUser: <Alice> Hello world" using the official API. This is currently allowed, but doesn't allow access to 1:1 chats. The other is "puppeting", the bot logs in as Alice by Alice providing her credentials and hitting endpoints the actual Web app uses. This results in a less obvious, nicer experience for people on he discord side but is the one that is banned

saagarjha 6y ago

I have yet to see any verbiage in the Discord ToS that mentions this…do they really not read their own legalese?

brianush1 6y ago
It's not in the Discord terms of service, it's in the Discord bot API terms of service.

doublerabbit 6y ago

If I can login to your service with the API given, there should be no reason for a ban. And this is what annoys me with today's communication protocols; your forced to enjoy their service only with their provided application. It never used to be like this. MSN messenger,AIM even YIM; they all had FOSS applications.

aquaticsunset 6y ago
They didn't start that way though. It wasn't until they were forced to play nice under regulatory action.