Downloads of v 0.4.28:


Last Update:

26 Dec 2020

Package Maintainer(s):

Software Author(s):

  • Andrew Richards "cancel"


ripcord discord slack chat


0.4.28 | Updated: 26 Dec 2020



Downloads of v 0.4.28:



Software Author(s):

  • Andrew Richards "cancel"

Ripcord 0.4.28

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Ripcord, run the following command from the command line or from PowerShell:


To upgrade Ripcord, run the following command from the command line or from PowerShell:


To uninstall Ripcord, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade ripcord -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade ripcord -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure ripcord installed
    name: ripcord
    state: present
    version: 0.4.28
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'ripcord' do
  action    :install
  version  '0.4.28'
  source   'STEP 3 URL'

See docs at

    Name: ripcord,
    Version: 0.4.28,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller ripcord
   Name     = 'ripcord'
   Ensure   = 'Present'
   Version  = '0.4.28'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'ripcord':
  provider => 'chocolatey',
  ensure   => '0.4.28',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install ripcord version="0.4.28" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 26 Dec 2020.



Ripcord is a desktop chat client for group-centric services like Slack and Discord. It provides a traditional compact desktop interface designed for power users. It's not built on top of web browser technology: it has a small resource footprint, responds quickly to input, and gets out of your way. Shareware is coming back, baby.


  • Not made from a web browser
  • Tabs
  • Multiple windows
  • Multiple accounts
  • Voice chat (Discord OK, Slack WIP)
  • Graphical emoji and custom emoji
  • Tab completion for user names and emoji
  • Customizable fonts, colors, and sizes
  • Custom bookmark lists for easily accessing only the channels you actually use
  • Variable DPI and multi-monitor support
  • Low CPU and memory usage
  • Zero GPU usage
  • No tracking or analytics
  • No installer or forced updates

Bug reports and feature requests
Status table of feature support in Slack and Discord
Join the Ripcord Discord server or the Ripcord Slack team to get help, ask questions, or give feedback.


$ErrorActionPreference = 'Stop'
$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

# Hotfix true or false
#$hotfix = 1
# dev would ideally prefer unupdated users not get the update, and 
# users who have the update are the only ones to get the hotfix
#If ( $hotfix ) { exit }

# Place shortcuts in appropriate location
$ProgsFolder = [environment]::getfolderpath('Programs')
If ( Test-ProcessAdminRights ) {
  $ProgsFolder = Join-Path ([environment]::getfolderpath('CommonApplicationData')) "Microsoft\Windows\Start Menu\Programs"

$packageArgs = @{
	packageName      = 'ripcord'
	file64           = gi $toolsDir\*
	destination      = "$toolsDir"
	ShortcutFilePath = "$ProgsFolder\Ripcord.lnk"
	TargetPath       = "$toolsDir\Ripcord.exe"

Get-ChocolateyUnzip @packageArgs
Install-ChocolateyShortcut @packageArgs
Install-BinFile -Name "Ripcord" -Path "$destination\Ripcord.exe" -UseStart
Remove-Item $packageArgs.file64 -Force -ea 0
$ErrorActionPreference = 'Stop'
$commProgs = Join-Path ([environment]::getfolderpath('CommonApplicationData')) "Microsoft\Windows\Start Menu\Programs"
$userProgs = [environment]::getfolderpath('Programs')
Remove-Item -Path "$commProgs\Ripcord.lnk","$userProgs\Ripcord.lnk" -ea 0
Uninstall-BinFile -Name "Ripcord"

From: <>


Shareware Redistribution Rules for Ripcord
Last updated 2019-11-04 12:25 UTC

Ripcord is shareware, which means users are given permission to redistribute it to other users, with a few restrictions. This page describes what you are allowed to do and not allowed to do when redistributing Ripcord.

This page uses the term “release” as a noun to refer to the downloadable copies of Ripcord that are available on the main page of the Ripcord website. For Windows and Mac, these are .zip files which contain the software. For Linux, this is a .AppImage file, which is a type of executable self-mounting or self-extracting zip-like file which contains more software within.

This page uses the term “bundle” as a verb to refer to: wrapping Ripcord in an installer with something else, modifying the Ripcord release files to add something else, directly modifying the Ripcord program binary to add something else, and other common uses of the term “bundle” when applied to software.

You are allowed to:

    Redistribute any of the releases of Ripcord, unmodified.
        Example: you may host a copy of an official Ripcord release on your website or a package manager.
    Automate the installation, updating, and removal of Ripcord using package management software.
        Example: a command-line utility in a Linux distribution that provides a way to install and uninstall releases of Ripcord in some distribution-specific way.

You are not allowed to:

    Modify a release of Ripcord and then redistribute the modified copy.
    Claim that you created or own the rights to Ripcord.
    Misrepresent or obscure the origin or authorship of Ripcord.
    Bundle Ripcord with malware, adware, or software intended to gather and sell or profit from user data.
    Bundle Ripcord with something that bypasses or interferes with the shareware trial and licensing mechanism within Ripcord.
    Bundle Ripcord with a license key for Ripcord.
    Charge money for a redistributed copy of Ripcord, or charge money for use of Ripcord with a package manager.

On Linux, a special exception which allows you to redistribute modified copies of Ripcord is granted for the following case:

    For the Linux releases of Ripcord, when using Ripcord with a package management system, you are allowed to extract the contents of the AppImage and create a package of the software with equivalent or updated versions of shared library files (typically .so) for the purpose of improved compatibility with a Linux distribution or that package management system, to modify the Ripcord program binary to change the paths from which dynamic libraries are loaded for use in that package management system, and to redistribute that package.
        But you are not allowed to use shared library files which bypass or interfere with the shareware trial and licensing mechanism in Ripcord, or which break any of the other rules above.
        Similarly, you are not allowed to modify the Ripcord program binary to bypass the licensing mechanism, add malware, or break any of the other rules above.

If you need additional special exceptions—for example, to patch the main Ripcord binary in a way not allowed above in order to provide compatibility with a particular Linux distribution—please get in touch with me via email.

If you do not follow these rules, your permission to redistribute and/or repackage Ripcord is revoked. These rules are intended to protect Ripcord’s quality, safety, and viability as a product and source of income.

As long as you follow to these, you have permission to redistribute Ripcord, unless I (the owner of Ripcord) have revoked your permission. These rules may be changed without notice.

—Andrew Richards [email protected] Acyclic Systems LLC
md5: 444CA77FFC8772A36744F2D755823517 | sha1: D5130686FC9D35362972BED5DC8F7A9347DC074F | sha256: 8BE721D23424701E289B1145273C67E6D22517DB5C501BD0AAA3CC0390B9E41A | sha512: 3AB08D6E6DCF4205A7A2E88C8CF3CBFC88EB7CA94CF4546A33F3CBD0D362E7F63926E5933708B91221F82F641ECA054E1B9DAE7C1EDE32600F326A6915B2D813
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.
The embedded software have been downloaded from the listed download
location on <>
and can be verified by doing the following:

1. Go to


	to download the installer.

2. Get the checksum using one of the following methods:
  - Using powershell function 'Get-FileHash'
  - Use chocolatey utility 'checksum.exe'

3. The checksums should match the following:

  checksumType: sha256
  checksum64: 8BE721D23424701E289B1145273C67E6D22517DB5C501BD0AAA3CC0390B9E41A

The file 'LICENSE.txt' has been obtained from <>.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Ripcord 0.4.27 159 Saturday, November 14, 2020 Approved
Ripcord 0.4.26 274 Sunday, June 21, 2020 Approved
Ripcord 0.4.25 73 Saturday, May 23, 2020 Approved
Ripcord 0.4.24 53 Friday, April 3, 2020 Approved

This package has no dependencies.

Discussion for the Ripcord Package

Ground Rules:

  • This discussion is only about Ripcord and the Ripcord package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Ripcord, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus