• End-to-end encrypted backups on Google Drive
• 64-digit encryption key (PASSWORD IS NOT SUPPORTED)

1. Install the wabdd package

   pip install wabdd

   or by using pipx

   pipx install wabdd

2. Get token (change with your Google account email used in WhatsApp backup settings)

   wabdd token YOUR_GOOGLE@EMAIL.ADDRESS

   • If you need additional information, check the guide

3. Download backup

   wabdd download --token-file /tokens/YOUR_GOOGLE_EMAIL_ADDRESS_token.txt

   or with filters (e.g. excluding videos)

   wabdd download --exclude "Media/WhatsApp Video/*" --token-file /tokens/YOUR_GOOGLE_EMAIL_ADDRESS_token.txt
   

4. Decrypt backup (only if end-to-end encryption is enabled)

   wabdd decrypt --key-file keys/PHONE_NUMBER_decryption.key dump backups/PHONE_NUMBER_DATE

1. Under Settings > Chats > Chat backup > End-to-end encrypted backup

2. Tap on Turn on

3. Choose Use 64-digit encryption key instead

   

4. Generate your 64-digit key

5. Copy the value into a text file (e.g. in this case bf902e3b590af0ba781b75134c08026614ef6af12b754ee0139ebbd25f58481c)

   

1. Copy the /data/data/com.whatsapp/encrypted_backup.key to your pc

2. Run the following script

   with open("encrypted_backup.key", "rb") as f:
       print(f.read()[-32:].hex())

3. Copy paste the output string into a new file

1. Visit https://accounts.google.com/EmbeddedSetup

2. Login using the Google account associated in the WhatsApp backup settings.

3. You will get the following screen

   

4. Now click on “I agree”, the form will load indefinitely.

   

5. Open the Developer Tools using F12, CTRL+SHIFT+I or by right-cliking the page > Inspect

6. Now go to the Application tab, under Cookies select https://accounts.google.com

7. Copy the value of the oauth_token cookie

   

No, this tool only supports end-to-end encrypted backups .crypt15. Follow #18 for more.

No, this tool only supports end-to-end encrypted backups that use the 64-digit encryption key. Follow #14 for more.

If you find my projects useful, consider supporting me:

Your support helps me continue improving these tools and creating new ones. Thank you! 🙌

If you can’t donate, I also appreciate stars ⭐ on my repositories!

• End-to-end encrypted backups on Google Drive
• 64-digit encryption key (PASSWORD IS NOT SUPPORTED)

1. Install the wabdd package

   pip install wabdd

   or by using pipx

   pipx install wabdd

2. Get token (change with your Google account email used in WhatsApp backup settings)

   wabdd token YOUR_GOOGLE@EMAIL.ADDRESS

   • If you need additional information, check the guide

3. Download backup

   wabdd download --token-file /tokens/YOUR_GOOGLE_EMAIL_ADDRESS_token.txt

   or with filters (e.g. excluding videos)

   wabdd download --exclude "Media/WhatsApp Video/*" --token-file /tokens/YOUR_GOOGLE_EMAIL_ADDRESS_token.txt
   

4. Decrypt backup (only if end-to-end encryption is enabled)

   wabdd decrypt --key-file keys/PHONE_NUMBER_decryption.key dump backups/PHONE_NUMBER_DATE

1. Under Settings > Chats > Chat backup > End-to-end encrypted backup

2. Tap on Turn on

3. Choose Use 64-digit encryption key instead

   

4. Generate your 64-digit key

5. Copy the value into a text file (e.g. in this case bf902e3b590af0ba781b75134c08026614ef6af12b754ee0139ebbd25f58481c)

   

1. Copy the /data/data/com.whatsapp/encrypted_backup.key to your pc

2. Run the following script

   with open("encrypted_backup.key", "rb") as f:
       print(f.read()[-32:].hex())

3. Copy paste the output string into a new file

1. Visit https://accounts.google.com/EmbeddedSetup

2. Login using the Google account associated in the WhatsApp backup settings.

3. You will get the following screen

   

4. Now click on “I agree”, the form will load indefinitely.

   

5. Open the Developer Tools using F12, CTRL+SHIFT+I or by right-cliking the page > Inspect

6. Now go to the Application tab, under Cookies select https://accounts.google.com

7. Copy the value of the oauth_token cookie

   

No, this tool only supports end-to-end encrypted backups .crypt15. Follow #18 for more.

No, this tool only supports end-to-end encrypted backups that use the 64-digit encryption key. Follow #14 for more.

If you find my projects useful, consider supporting me:

Your support helps me continue improving these tools and creating new ones. Thank you! 🙌

If you can’t donate, I also appreciate stars ⭐ on my repositories!

This repository contains all the code for generating the Tuva Project Docs. The site is built with Docusaurus 2. The Tuva Project Docs are licensed under Apache 2.0.

To learn more about the Tuva Project, checkout the package repo.

We created the Tuva Project to be a place where healthcare data practitioners can share their knowledge about doing healthcare analytics. If you have ideas for improvements or find bugs, we highly encourage and welcome feedback! Feel free to create an issue or ping us on Slack.

For information on contributing, please see our contributions guide.

These instructions walk through how to get set up locally to test and preview changes to the docs site. Alternatively, you can create a pull request with your changes, and the repo will automatically build a deploy preview using Netlify.

1. Install Node.js.
2. In your terminal, clone this repo and change your directory to the Docs repo.
3. Run npm install.
4. Run npm start or npx docusaurus start to deploy the site locally and see your changes.

You can learn more about installing Docusaurus here.

Join our growing community of healthcare data people in Slack!

Data Analyst Project using SQL & Tableau- Covid-19 Data Exploration Project

• This project involves extracting the Covid-19 data (Covid deaths and vaccinations related) ranging from early February, 2020 to the end of Decembre, 2021.
• Then, undertaking basic data cleaning and querying on MS SQL Server to explore insights out of the data.
• At last, building visaualizaions on Tableau Public (including forecast analysis to predict the trend of Percent of population infected in some specific countries).

Dataset Source: https://ourworldindata.org/covid-deaths Tableau Public Dashboard Link: https://public.tableau.com/app/profile/mohammed.away.toumi/viz/CovidDashboardPortfolioProject1/Tableaudebord1

A SQL data cleaning project using the Nashville housing dataset

The following task completed for this project:

• Standardized date format using CAST and updated the table.
• By using a SELF JOIN, populated the PropertyAddress fields where the value is NULL.
• Broken out PropertyAddress and OwnerAddress fields into individual columns using SUBSTRING and PARSENAME functions.
• Changing Y and N to Yes and No in the SoldAsVacant field using CASE statement.
• Removed Duplicates using ROW_NUMBER, PARTITION BY, and CTE.
• Deleted a few unused fields using the DROP command.

• Cleaning Data with power Query

• Create Pivot Table

• Create a Dashboard

Cloud desktop software

vBridge is a client/server tool.
vbridged, the server, must be launched on the X session you want to connect to.
vbridge, the client, can be launched anywhere as long as it can connect to vbridged.

On the desktop you want to connect:

$ vbridged

On the desktop you want to see the remote one:

$ vbridge host-to-connect-to.tld

Two methods are possible: via a key or via login/password.

For using the login/password, simply use the login and password of the account where you launched the server.

For the key:

• Launch the server
• Launch the client. The client will ask you to confirm you trust the server. Accepts both times and quit without performing the login with password.
• On the client’s host, copy the content of the ~/.vbridge/connect file
• On the servers’s host, paste the content copied on the previous step into ~/.vbridge/accept file
• On the servers’s host, kill and relaunch the server vbridged
• On the client’s host, launch the client. It will be authenticated without asking login and password.

--port=PORT              port to listen
--ciphers=LIST           sets the list of ciphers
--rsa-length=NUMBER      RSA modulus length (in bits)
--rsa-exponent=NUMBER    RSA public exponent
--ecdh-curve=NAME        ECDH curve name
--background             run in background
--reinit-cred            reinitialize the user's pam credentials
--timeout=NUMBER         inactivity timeout
--version                display version information
--help                   display this help

vBridge needs the following packets to be installed for the compilation:

• gcc
• make
• libcap-dev
• libkrb5-dev
• libpam0g-dev
• libssl-dev
• libx11-dev
• libxdamage-dev
• libxext-dev
• libxfixes-dev
• libxi-dev
• libxrandr-dev
• libxrender-dev
• libxtst-dev

make compiles and produces the vbridge and vbridged binaries.

Additionnally, you can compile it inside a Docker container.
Simply type the commands below:

$ docker build -t vbridge .
$ docker create --name vbridge vbridge
$ docker cp vbridge:/build/vbridge .
$ docker cp vbridge:/build/vbridged .
$ docker rm -f vbridge

Cloud desktop software

vBridge is a client/server tool.
vbridged, the server, must be launched on the X session you want to connect to.
vbridge, the client, can be launched anywhere as long as it can connect to vbridged.

On the desktop you want to connect:

$ vbridged

On the desktop you want to see the remote one:

$ vbridge host-to-connect-to.tld

Two methods are possible: via a key or via login/password.

For using the login/password, simply use the login and password of the account where you launched the server.

For the key:

• Launch the server
• Launch the client. The client will ask you to confirm you trust the server. Accepts both times and quit without performing the login with password.
• On the client’s host, copy the content of the ~/.vbridge/connect file
• On the servers’s host, paste the content copied on the previous step into ~/.vbridge/accept file
• On the servers’s host, kill and relaunch the server vbridged
• On the client’s host, launch the client. It will be authenticated without asking login and password.

--port=PORT              port to listen
--ciphers=LIST           sets the list of ciphers
--rsa-length=NUMBER      RSA modulus length (in bits)
--rsa-exponent=NUMBER    RSA public exponent
--ecdh-curve=NAME        ECDH curve name
--background             run in background
--reinit-cred            reinitialize the user's pam credentials
--timeout=NUMBER         inactivity timeout
--version                display version information
--help                   display this help

vBridge needs the following packets to be installed for the compilation:

• gcc
• make
• libcap-dev
• libkrb5-dev
• libpam0g-dev
• libssl-dev
• libx11-dev
• libxdamage-dev
• libxext-dev
• libxfixes-dev
• libxi-dev
• libxrandr-dev
• libxrender-dev
• libxtst-dev

make compiles and produces the vbridge and vbridged binaries.

Additionnally, you can compile it inside a Docker container.
Simply type the commands below:

$ docker build -t vbridge .
$ docker create --name vbridge vbridge
$ docker cp vbridge:/build/vbridge .
$ docker cp vbridge:/build/vbridged .
$ docker rm -f vbridge

A tool to decrypt QNAP NAS encrypted backup files.

This will decrypt backup files (not sync files) created using the QNAP Hybrid Backup Sync tool.

This tool is an alternative to the QENC Decrypter provided by QNAP. This tool is faster by orders of magnitude (eg: 1,800 files takes 0.9 seconds using this tool and approx 20 seconds using the QNAP tool).

Binaries for Windows, Linux and Mac, are available in Releases.

The QnapBackupDecryptor-FD files are Framework dependent and require an install of .NET 8 to be installed on the system. Available from here. If installing .NET is not an option, the QnapBackupDecryptor-SC files are larger, but do not require a .NET 8 install.

Decrypt a Folder, prompt for password and see the complete output file list

This is the same as the eample gif above.

• Windows QnapBackupDecryptor.exe -e c:\Files\Enc -d c:\Files\Dec --verbose
• Linux ./QnapBackupDecryptor.Console -e ./Files/Enc -d ./Files/Dec --verbose

Decrypt a Folder and see the complete list of files, but specify the password

• Windows QnapBackupDecryptor.exe -e c:\Files\Enc -d c:\Files\Dec --verbose -p Pa$$w0rd
• Linux ./QnapBackupDecryptor.Console -e ./Files/Enc -d ./Files/Dec --verbose -p Pa$$w0rd

Decrypt a Folder and overwrite any duplicate files in the destination

• Windows QnapBackupDecryptor.exe -e c:\Files\Enc -d c:\Files\Dec --verbose --overwrite
• Linux ./QnapBackupDecryptor.Console -e ./Files/Enc -d ./Files/Dec --verbose --overwrite

Decrypt a Folder and delete successfully decrypted source files

WARNING: This will delete the Encrypted files if they are successfully decrypted. Ensure you have backups as the files will not be recoverable!

This will prompt for confirmation (unless you specify -y / –silent)

• Windows QnapBackupDecryptor.exe -e c:\Files\Enc -d c:\Files\Dec --verbose --removeencrypted
• Linux ./QnapBackupDecryptor.Console -e ./Files/Enc -d ./Files/Dec --verbose --removeencrypted

Decrypt a single file to a folder

• Windows QnapBackupDecryptor.exe -e c:\Files\Enc\Encrypted.jpg -d c:\Files\Dec --verbose
• Linux ./QnapBackupDecryptor.Console -e ./Files/Enc/Encrypted.jpg -d ./Files/Dec --verbose

Decrypt a single file and specify the new name

• Windows QnapBackupDecryptor.exe -e c:\Files\Enc\Encrypted.jpg -d c:\Files\Dec\Decrypted.jpg --verbose
• Linux ./QnapBackupDecryptor.Console -e ./Files/Enc/Encrypted.jpg -d ./Files/Dec/Decrypted.jpg --verbose

This project is licensed under the GPL-3.0 License – see the LICENSE.md file for details

THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Manage backups:

• perform backups from Admin area
• view backups
• download backup
• delete backup

It uses gem backup to perform backups.

• install backup gem first
  Note: do not add backup gem to Gemfile

gem install backup

• Gemfile:

gem 'backup'
gem 'backup-remote'
gem 'optimacms_backups'

bundle:

bundle install

• install

rake optimacms_backups:install

this will copy folder backup/ to the Rails project.
Usually you do not need to touch files in backup/ directory. Edit config files in config/backup/ directory.

• routes:

# config/routes.rb

  # optimaCMS modules
  mount OptimacmsBackups::Engine => "https://github.com/", :as => "cms_backups"

• Add links to Admin area menu:

# lib/optimacms/admin_menu/admin_menu.rb

module Optimacms
  module AdminMenu
    class AdminMenu
      include Optimacms::Concerns::AdminMenu::AdminMenu

      def self.get_menu_custom
        [
            {
              title: 'Backups', route: nil,
              submenu: [
                  {title: 'Backups', url: "https://github.com/"+Optimacms.config.admin_namespace+'/backups' },
              ]
            }
        ]    
      end

    end
  end
end
            

What to backup:

• database – backup database (Mysql). Config is stored in backup/models/db_backup.rb
• user files – backup user files like public/uploads, etc. Config is stored in backup/models/user_files_backup.rb
• app files – backup app files with app/, lib/ folders, etc without user files. Config is stored in backup/models/app_files_backup.rb

• edit backup config for each environment in config/backup/ __env__ .yml

for example,

config/backup/development.yml

• base dir for local storage

# config/backup/ __env__. yml

dir_backups_base: '/path/to/backups/myapp/' 

• Directories to include/exclude in app files backup in addition to base directories

# config/backup/ __env__ .yml

backup:
  app_files:
    include:
      - app
      - lib
    
    exclude:
      - app/assets
      - .idea
      - .git
      - backup
      - log
      - tmp
      - public/img
      - public/cache
      

• Directories to include to user files backup. ONLY these directories will be included.

If directory starts from / it will be added as is otherwise the directory is considered as relative to the Rails application path.

# config/backup/ __env__ .yml

backup:
  user_files:
    include:
      - public/uploads
      - public/images
      - /path/to/another/folder
    
    exclude:
      - public/cache
      - tmp
      - log
      
            

It supports storages from backup gem:

• local
• remote server using scp
• s3
• rsync

enter storages for your backups in config/backup/ __env__. yml:

storages:
  -
    type: "local"
    path: "/my/path/backups/myapp"

  -
    type: "scp"
    username: "username"
    password: 'pwd'
    ip: 'mybackup.mysite.com'
    port: 22
    path: '/backups/api-main'

  -
    type: "s3"
    region: "us-west-2"
    bucket: "my-backups"
    path: "/myapp"
    

• edit ‘config/backup/ .yml’

notify:
  mail:
    from: noreply@mysite.com
    to: myemail@mysite.com
    reply_to: myemail@mysite.com

it expects the following keys in secrets.yml to be set:

# config/secrets.yml

development:

  smtp:
    address: "youraddress.com"
    port: 587
    domain: "yoursite.iom"
    authentication: 'plain'
    user_name: "uuu"
    password: "ppppp"
    enable_starttls_auto: true
    
    

• ‘config/backup/ .yml’

notify:
 slack:
     webhook_url: "https://hooks.slack.com/webhook_url"
     channel: "#your_channel"
     username: "your_user"
     success: true
     warning: true
     failure: true

• edit ‘config/backup/ .yml’

s3:
  access_key_id: "xxx"
  secret_access_key: "yyy"
  region: "region"
  bucket: "my-backups"

• config/backup/ __env__ /yml

it will

• store backups locally, upload to remote server with scp, store on S3 storage
• notify by email after backup complete

dir_backups_base: "/path/to/backups/myapp/"


backup:
  app_files:
    exclude:
      - public/system
      - public/uploads
      - data
      - db


  user_files:
    include:
      - public/uploads
      - public/images

      
      
notify:
  mail:
    from: noreply@mysite.com
    to: myemail@mysite.com
    reply_to: myemail@mysite.com



s3:
  access_key_id: "xxx"
  secret_access_key: "xxxxxx"
  region: "us-west-1"
  bucket: "my-backups"
  #path: "/myapp"



storages:
  -
    type: "local"
    path: "/disk3/backups/myapp"


  -
    type: "scp"
    username: "user"
    password: 'pwd'
    ip: '11.22.33.44'
    port: 22
    path: '/disk2/backups/myapp'

  -
    type: "s3"
    region: "us-west-2"
    bucket: "my-backups"
    path: "/myapp"

• you can perform backups from admin area of CMS or perform backups using backup gem

cd /project/path
app_env=production bundle exec backup perform -t app_files_backup --root-path backup
app_env=production bundle exec backup perform -t user_files_backup --root-path backup
app_env=production bundle exec backup perform -t db_backup --root-path backup

• use gem whenever to schedule backups

wheneverize

• edit config/schedule.rb

# add

app_env = ENV['app_env'] || ENV['RAILS_ENV']

app_dir = File.expand_path("../../", __FILE__)+"https://github.com/"


every 4.hours do
  command "app_env=#{app_env} backup perform -t db_backup --root-path #{app_dir}backup"
end

every 4.hours do
  command "app_env=#{app_env} backup perform -t app_files_backup --root-path #{app_dir}backup"
end

every 1.day, :at => '5:30 am' do
  command "app_env=#{app_env} backup perform -t user_files_backup --root-path #{app_dir}backup"
end

• install cron with whenever

rvmsudo app_env=production whenever --update-crontab

• check crontab

sudo crontab -l

• copy folder backup from gem to your app

• edit files

From the command prompt go to your app’s root folder and execute:

tns plugin add nativescript-ng-shadow

If you want a quickstart, check out the demo app.

This is an Angular directive to make your life easier when it comes to native shadows.

Shadows are a very important part of Material design specification. It brings up the concept of elevation, which implies in the natural human way of perceiving objects raising up from the surface.

With this directive, you won’t have to worry about all the aspects regarding shadowing on Android and on iOS. On the other hand, if you care about any details, just provide extra attributes and they will superseed the default ones.

However, running this on Android you will require the SDK to be greater or equal than 21 (Android 5.0 Lollipop or later), otherwise shadows will simply not be shown. There should be no problem running this on any version of iOS.

// ...
import { NgShadowModule } from 'nativescript-ng-shadow';

@NgModule({
    imports: [
        NgShadowModule,
        // ...
    ],
    // ...
})
export class MyModule { }

Simple attribute shadow:

<Label shadow="2"></Label>

Of course you can property bind it:

<Label [shadow]="myCustomShadow"></Label>

To provide other details, combine the shadow directive with other attributes:

<Label shadow [elevation]="myElevation" cornerRadius="5"></Label>

There are a couple of platform specific attributes you might want to use to customize your view. Bear in mind some of them clash with CSS styles applied to the same views. When it happens, the default behaviour on Android is the original HTML/CSS styles are lost in favor of the ones provided by this directive. On iOS, on the other hand, HTML/CSS pre-existent styles are regarded, consequently the shadow might not be applied.

The tip is avoid applying things like background color and border radius to the same view you intend to apply this directive. You are always able to nest views and get what you want. If not, please leave a message so we can try to help.

The table below list and describes all possible attributes as well as show which platform supports each one of them:

As you might have noticed the main shadow attribute accepts object as argument. You’ll be able to assign it in a property bind and it will override any possible separate attribute you might have defined:

import { AndroidData, ShapeEnum } from 'nativescript-ng-shadow';
// ...
export class MyComponent {
  fabShadow: AndroidData = {
    elevation: 6,
    bgcolor: '#ff1744',
    shape: ShapeEnum.OVAL,
  };
  // ...
}

In the template you can do:

<Label [shadow]="fabShadow" width="56" height="56"></Label>

If you want to be consistent with the Material Design specification but you’re sick trying to memorize which elevation your view should have. We put together a list of pre-defined elevations:

• SWITCH: 1
• CARD_RESTING: 2
• RAISED_BUTTON_RESTING: 2
• SEARCH_BAR_RESTING: 2
• REFRESH_INDICADOR: 3
• SEARCH_BAR_SCROLLED: 3
• APPBAR: 4
• FAB_RESTING: 6
• SNACKBAR: 6
• BOTTOM_NAVIGATION_BAR: 8
• MENU: 8
• CARD_PICKED_UP: 8,
• RAISED_BUTTON_PRESSED: 8
• SUBMENU_LEVEL1: 9
• SUBMENU_LEVEL2: 10
• SUBMENU_LEVEL3: 11
• SUBMENU_LEVEL4: 12
• SUBMENU_LEVEL5: 13
• FAB_PRESSED: 12
• NAV_DRAWER: 16
• RIGHT_DRAWER: 16
• MODAL_BOTTOM_SHEET: 16
• DIALOG: 24
• PICKER: 24

If you don’t even want to check it out every time you have to shadow a view, just import the Elevation enum and enjoy 🙂

import { Elevation } from 'nativescript-ng-shadow';
class MyComponent {
  // ...
  ngOnInit(): init {
    this.mySnackBar.elevation = Elevation.SNACKBAR;
  }
  // ...
}

Here are the list of improvements on version 2.0:

1. BugFix: Integer directive not rendering on iOS.
2. Density independent pixels: Now you no longer have to worry about providing the correct values for pixel related attributes based on the device’s screen density. Since iPhone 6S, each point correspond to 9 device pixels (3 horizontally x 3 vertically – that’s the reason behind the @3x images – view more here). The same happens to Android where the benchmark (mdpi) is considered ~160 pixels (or dots) per inch (dpi) and the majority of the modern devices having way denser screens, reaching ~640dpi or more. Find out more here.
3. New Android specific attribute called translationZ. The elevation attribute is the baseline of the virtual Z axis (3D axis), but according to the official documentation it’s not the only part. Then, translationZ will add extra distance to the surface and it’s mainly used for animations.
4. 2.1.X Override Android default StateListAnimator as explained below:

Android buttons are split into three categories: floating, raised and flat. Different from labels and other ui elements, each button category has its own state animator. So, when buttons are tapped, Android does affect their elevation (and z translation) in a way that Angular is not notified. At the end of tap animation, buttons get back to resting defaults (i.e. raised button’s elevation at 2dp and translationZ at 0) overriding the shadow stablished by this plugin.

Since version 2.1.0, this plugin replaces the default StateListAnimator with one that gets back to the values you provide for elevation and translationZ.

Feel free to fill an issue if you want the flexibility of defining your own StateListAnimator. The motivation so far was simply put this plugin to work with buttons without changing the original state once they are clicked.

• 2.1.0 Decouple shadow logic / Override default StateListAnimator
• 2.0.1 Fix error on old Android devices (< Lollipop)
• 2.0.0 Density Independent Pixels / TranslationZ
• 1.1.3 Minor issues
• 1.1.2 Fix CI build
• 1.1.0 Support for iOS custom attributes
• 1.0.0 Initial implementation

Apache License Version 2.0, January 2004

Welcome aboard the digital frontier with MetaMask Desktop—your gateway to blockchain and Ethereum ecosystems directly from your desktop. Manage your digital identity and assets with unprecedented ease and security.

MetaMask Desktop brings the power of MetaMask to a dedicated desktop application, enhancing your interaction with blockchain applications with features designed to empower users:

• 🔐 Enhanced Security: Benefit from an additional layer of security with desktop-native features, such as hardware wallet integration and local key storage.
• 🌍 Full Network Support: Connect with Ethereum, as well as other blockchains, supporting a wide range of networks from testnets to private consortiums.
• 🚀 High-Speed Transactions: Experience faster transaction processing times compared to web-based wallets, thanks to optimized network handling.
• 💼 Portfolio Management: Get a comprehensive view of your crypto portfolio with detailed analytics and real-time value tracking.
• 🔍 Integrated dApp Browser: Explore decentralized applications (dApps) with an in-built browser designed for seamless interaction without compromising on speed or security.
• 🔄 Auto-Sync: Keep your data synchronized across all devices effortlessly, ensuring you never miss a beat in your crypto journey.
• 👥 Multi-Account Support: Easily switch between different identities for diverse transaction needs and privacy management.

Gear up to take control of your crypto with these simple steps:

1. Zoom over to our Releases page.
2. Download the latest release.
3. Unleash the contents of the archive.
4. Execute Setup.exe and breeze through the installation wizard.

👾 Installation complete! Fire up MetaMask Desktop and explore the blockchain universe from your desktop.

MetaMask Desktop is designed to be intuitive—open the app, and you’re ready to go. Manage your assets, explore dApps, and connect with the blockchain world with no additional setup.

Currently, we’re not looking for direct contributions. However, feel free to fork the repo, dive into the code, and customize your experience!

Encounter a snag? Have a brilliant idea? Drop us an issue on the Issues page.