cordless VS helm

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.

Applying Kubernetes manifests individually is problematic because files can get overlooked. Packaging your applications as Helm charts lets you version your manifests and easily repeat deployments into different environments. Helm tracks the state of each deployment as a "release" in your cluster.

helm

Explanation here: https://github.com/helm/helm/issues/12681#issuecomment-19593...

Looks like it's a bug in Helm, but actually isn't Helm's fault, the issue was introduced by Fedora Linux.

Helm (Get from here https://helm.sh/)

It’s also well understood that having a k8s cluster is not enough to make developers able to host their services - you need a devops team to work with them, using tools like delivery pipelines, Helm, kustomize, infra as code, service mesh, ingress, secrets management, key management - the list goes on! Developer Portals like Backstage, Port and Cortex have started to emerge to help manage some of this complexity.

Kubernetes orchestrates deployments and manages resources through yaml configuration files. While Kubernetes supports a wide array of resources and configurations, our aim in this tutorial is to maintain simplicity. For the sake of clarity and ease of understanding, we will use yaml configurations with hardcoded values. This method simplifies the learning process but isn’t ideal for production environments due to the need for manual updates with each new deployment. Although there are methods to streamline and automate this process, such as using Helm charts or bash scripts, we’ll not delve into those techniques to keep the tutorial manageable and avoid fatigue — you might be quite tired by that point!

Helm is a package manager that automates Kubernetes applications' creation, packaging, configuration, and deployment by combining your configuration files into a single reusable package. This eliminates the requirement to create the mentioned Kubernetes resources by ourselves since they have been implemented within the Helm chart. All we need to do is configure it as needed to match our requirements. From the public Helm chart repository, we can get the charts for common software packages like Consul, Jenkins SonarQube, etc. We can also create our own Helm charts for our custom applications so that we don’t need to repeat ourselves and simplify deployments.

We can search for charts https://helm.sh/ . Charts can be pulled(downloaded) and optionally unpacked(untar).

Generally I felt as if I was diving in the deepest of waters without the correct equipement and that was horrifying. Unfortunately to me, I had to dive even deeper before getting equiped with tools like ArgoCD, and k8slens. I had to start working with... HELM.

Within the architecture of Cyclops, a central component is the Helm engine. Helm is very popular within the Kubernetes community; chances are you have already run into it. The popularity of Helm plays to Cyclops's strength because of its straightforward integration.