Downloads of v 3.0.1-beta:


Last Update:

18 Jun 2016

Package Maintainer(s):

Software Author(s):

  • tweetenapp bc3tech


tweeten admin twitter

Tweeten (Install)

This is a prerelease version of Tweeten (Install).

3.0.1-beta | Updated: 18 Jun 2016



Downloads of v 3.0.1-beta:



Software Author(s):

  • tweetenapp bc3tech

Tweeten (Install) 3.0.1-beta

This is a prerelease version of Tweeten (Install).

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Tweeten (Install), run the following command from the command line or from PowerShell:


To upgrade Tweeten (Install), run the following command from the command line or from PowerShell:


To uninstall Tweeten (Install), 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 tweeten -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 tweeten -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 tweeten installed
    name: tweeten
    state: present
    version: 3.0.1-beta
    source: STEP 3 URL

See docs at

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

chocolatey_package 'tweeten' do
  action    :install
  version  '3.0.1-beta'
  source   'STEP 3 URL'

See docs at

    Name: tweeten,
    Version: 3.0.1-beta,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller tweeten
   Name     = 'tweeten'
   Ensure   = 'Present'
   Version  = '3.0.1-beta'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'tweeten':
  provider => 'chocolatey',
  ensure   => '3.0.1-beta',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install tweeten version="3.0.1-beta" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

Tweeten, an app for TweetDeck that makes it look and work better.

$ErrorActionPreference = 'Stop';

$packageName= 'tweeten'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''
$url64      = ''

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  url           = $url
  url64bit      = $url64

  validExitCodes= @(0)

  softwareName  = 'tweeten*'
  checksum      = ''
  checksumType  = 'md5'
  checksum64    = ''
  checksumType64= 'md5'

Install-ChocolateyPackage @packageArgs

$ErrorActionPreference = 'Stop';

$packageName = 'tweeten'
$softwareName = 'tweeten*'
$installerType = 'EXE' 

$silentArgs = '/qn /norestart'
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
if ($installerType -ne 'MSI') {
  $validExitCodes = @(0)

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

[array]$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

if ($key.Count -eq 1) {
  $key | % { 
    $file = "$($_.UninstallString)"

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File "$file"
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

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
Tweeten (Install) 3.0.1-beta 332 Saturday, June 18, 2016 Exempted
Tweeten (Install) 2.0.3-beta 248 Tuesday, May 24, 2016 Exempted
Tweeten (Install) 2.0.1-beta 294 Monday, May 23, 2016 Exempted
Tweeten (Install) 2.0-beta 219 Monday, May 9, 2016 Exempted
Tweeten (Install) 1.9.1-beta 226 Tuesday, April 26, 2016 Exempted
Tweeten (Install) 1.8-beta2 276 Thursday, April 14, 2016 Exempted
Tweeten (Install) 1.8-beta 269 Thursday, April 14, 2016 Exempted

Hi everyone,
Today, we are releasing Tweeten 3.0 for Windows and macOS with a bunch of new features which we got a lot of requests for. You can get the full details about the update on our blog (, but here's a quick roundup:

  • You can now save GIFs within Tweeten (as .gif)
  • You can now Drag and Drop static images and .gif files
  • You can now save static images
  • You can now copy URLs for tweets, user profiles, mentions, and more.
  • You can now copy image URLs
  • We've a new font on macOS which looks a lot better
  • We've added support for TweetDeck's native polls
  • The Settings window now closes by itself when you click 'Save Settings'
  • We've fixed the overlay issue for videos and GIFs
  • We've fixed a bunch of other UI issues and optimized some parts of the app
    As usual, if you have any feedback, please let us know via Twitter (@tweetenapp). Happy Tweeting!
    Latest release: Beta 3.0.1
    Released on: Friday, 17th June, 2016.

This package has no dependencies.

Discussion for the Tweeten (Install) Package

Ground Rules:

  • This discussion is only about Tweeten (Install) and the Tweeten (Install) 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 Tweeten (Install), 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