cordless VS go

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.

A Discussion about including this package in Go as encoding/json/v2 has been started on the Go Github project on 2023-10-05. Please provide your feedback there.

I like the Principles section. Very measured and practical approach to releasing new stdlib packages. https://go.dev/blog/randv2#principles

The end of the post they mention that an encoding/json/v2 package is in the works: https://github.com/golang/go/discussions/63397

There used to be the GO FIPS branch :

https://github.com/golang/go/tree/dev.boringcrypto/misc/bori...

But it looks dead.

And it looks like https://github.com/golang-fips/go as well.

I'm not sure what exactly you mean by acknowledgement, but here are some counterexamples:

- A proposal for sum types by a Go team member: https://github.com/golang/go/issues/57644

- The community proposal with some comments from the Go team: https://github.com/golang/go/issues/19412

Here are some excerpts from the latest Go survey [1]:

- "The top responses in the closed-form were learning how to write Go effectively (15%) and the verbosity of error handling (13%)."

- "The most common response mentioned Go’s type system, and often asked specifically for enums, option types, or sum types in Go."

I think the problem is not the lack of will on the part of the Go team, but rather that these issues are not easy to fix in a way that fits the language and doesn't cause too many issues with backwards compatibility.

[1]: https://go.dev/blog/survey2024-h1-results

Now, I’m not going to use C++ again; I left that chapter years ago, and it’s not going to happen. C++ isn’t memory safe and easy to use and would require extended time for developers to adapt. Rust is the new kid on the block, but I’ve heard mixed opinions about its developer experience, and there aren’t many libraries around it yet. LLRD is too new for my taste, but **Go** caught my attention.

Generative AI development has been democratised, thanks to powerful Machine Learning models (specifically Large Language Models such as Claude, Meta's LLama 2, etc.) being exposed by managed platforms/services as API calls. This frees developers from the infrastructure concerns and lets them focus on the core business problems. This also means that developers are free to use the programming language best suited for their solution. Python has typically been the go-to language when it comes to AI/ML solutions, but there is more flexibility in this area. In this post you will see how to leverage the Go programming language to use Vector Databases and techniques such as Retrieval Augmented Generation (RAG) with langchaingo. If you are a Go developer who wants to how to build learn generative AI applications, you are in the right place!

net/http: add methods and path variables to ServeMux patterns Discussion about ServeMux enhancements

Make sure you have Go installed https://go.dev/.