cordless VS book

There’s a lot of instances, for example the developer of one of the alternative clients https://github.com/Bios-Marcel/cordless

The cordless project https://github.com/Bios-Marcel/cordless is now abandoned and archived, and the maintainer has been banned for a ToS violation.

People who have been caught using third-party clients have been banned before.

The developer of the cordless Discord client got banned, presumably for using a third-party client.

The only blocking issue is that their success (and subsequent spam/abuse issues) is greater than their focus on open access, to the extent that they formally disallow 3rd party client access.

So at the one end of the spectrum with have IMAP/SMTP, in the middle we have things like Telegram (everything's GPL3! The protocol is terrible and here are all the details! Go nuts!)... and at the other end we have Discord: One Protocol, One Allowed Client™®©.

Do I use Discord? No.

Would I like to use Discord? Yes.

Why can't I use Discord? The client is too much for my older laptop.

Would I like to use Discord? Yes there are a pile of people on there I'm missing out

Can I do anything about it? Yes, I have two options:

1) use https://cancel.fm/ripcord/ until it suffers the same fate as https://github.com/Bios-Marcel/cordless

2) throw the whole thing to the wind until I have better hardware

Hmm. You know come to think about it the chances are people with similar interests are probably also stuck on older hardware too and probably won't be using Discord either...

> There are alternate Discord clients, and — unlike Slack — Discord doesn't try to actively prevent people from writing alternate clients against their API.

Yes, they do.

https://github.com/Bios-Marcel/cordless:

> Hey, so I know this is somewhat of a bummer, but I got banned because of ToS violation today. This seemed to be connected to creating a new PM channel via the /users/@me endpoint. As that's basically a confirmation for what we've believed would never be enforced, I decided to not work on the cordless project anymore. I'll be taking down cordless in package managers in hope that no new users will install it anymore without knowing the risks. I believe that if you manage to build it yourself, you've probably read the README and are aware of the risks. I'll keep the repository up, but might archive it at some point. And yes, you'll still be able to use existing binaries for as long as discord doesn't introduce any more breaking changes. However, be aware that the risk of getting a ban will only get higher with time!

https://github.com/atlx/discord-term:

> Disclaimer: So-called "self-bots" are against Discord's Terms of Service and therefore discouraged. I am not responsible for any loss or restriction whatsoever caused by using self-bots or this software. That being said, there's no one stopping you from risking using an account, so go head!

Worth noting the developer of another third party client, Cordless, recently had their account disabled, which ended with the project sadly being abandoned.

To be honest, I am a fan of the excellent cordless application. Unfortunately, the creator was banned from the service for violating the terms of service. So it is not recommended anymore.

My first port of call was to google learn rust which lead me to "the book". The book is a first steps guide written by the rust community for newbies (or Rustlings as they're called) to gain a 'solid grasp of the language'.

Before Prodzilla, I’d read 'The Book' a couple of times, and had made my way through Rustlings, but hadn’t yet built a serious project in Rust.

To answer your last question;

Start with the Rust book.

https://doc.rust-lang.org/book/

Then do Rustlings until the syntax becomes muscle memory.

Then join the Discord and start doing little projects.

You won’t get up to the proficiency of other languages as quickly in Rust. It takes longer. For me it’s taking a lot longer, but I enjoy it.

Before diving into these repositories, familiarize yourself with Rust and its development ecosystem. The official Rust book is an excellent resource for developers at all levels. Each repository has documentation on how to contribute, covering code style, issue tracking, and pull requests.

This is my third Rust book after the official book and Rust in Action. The other two books are great, but they were too theoretical for me. I'm a slow learner and had much trouble grokking Rust's features and idiosyncrasies. When I was done with these books, I was lost and unsure of what I could do.

It's the same reason everything digital and downloadable isn't free: there's a cost to create it and there's a value to it.

For a language developer to charge for a book about that language, I think that's a completely valid way to make some money off of their work.

Even the Rust book, "The Rust Programming Language" is available freely online [0], but also as a print and ebook for sale via NoStarchPress [1].

[0] https://doc.rust-lang.org/book/

[1] https://nostarch.com/rust-programming-language-2nd-edition

You know you can just read it online right now in 2 different variants It does contain some systems programming.

I am looking at The Book (https://doc.rust-lang.org/book/), but hoped there was an amazing person on youtube.

Yeah, I'll build something, finally trying webassembly.

https://doc.rust-lang.org/book/ https://github.com/rust-lang/rustlings https://doc.rust-lang.org/rust-by-example/