| // This script will remove all videos from watch later list | |
| // | |
| // Usage | |
| // | |
| // #1 go to https://www.youtube.com/playlist?list=WL | |
| // #2 run following script | |
| // adjust REMOVE_BUTTON_TEXT to your language (default is english) | |
| (async function() { | |
| const REMOVE_BUTTON_TEXT = "Remove from Watch later" |
http://bookofzeus.com/harden-ubuntu/initial-setup/system-updates/
Keeping the system updated is vital before starting anything on your system. This will prevent people to use known vulnerabilities to enter in your system.
sudo apt-get update
sudo apt-get upgrade
sudo apt-get autoremove
sudo apt-get autoclean
| #!/bin/bash | |
| # Copyright © 2017 Google Inc. | |
| # Licensed under the Apache License, Version 2.0 (the "License"); | |
| # you may not use this file except in compliance with the License. | |
| # You may obtain a copy of the License at | |
| # | |
| # http://www.apache.org/licenses/LICENSE-2.0 | |
| # | |
| # Unless required by applicable law or agreed to in writing, software |
| #!/bin/bash | |
| # gnome and chrome and chrome remote desktop access | |
| # chrome itself is not required, but is included here. | |
| # other desktops can be used w/ light script changes. | |
| # tested on: | |
| # - ubuntu xenial GCE instance | |
| # - debian stretch crostini container on a Pixelbook (eve) | |
| # running ChromeOS v67.0.3383.0 (dev channel) | |
| # _without_ being in developer mode |
| #!/usr/bin/python2 | |
| # Copyright (c) 2012 The Chromium Authors. All rights reserved. | |
| # Use of this source code is governed by a BSD-style license that can be | |
| # found in the LICENSE file. | |
| # Virtual Me2Me implementation. This script runs and manages the processes | |
| # required for a Virtual Me2Me desktop, which are: X server, X desktop | |
| # session, and Host process. | |
| # This script is intended to run continuously as a background daemon | |
| # process, running under an ordinary (non-root) user account. |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
The first step to setting up an Ethereum development environment is running a node. Public nodes run by MyEtherWallet and Augur are great public services. However, you cannot always attach your private keys securely to such a node, and so you are limited to read-only interactions (reading contract variables, checking account balances). Moreover, you cannot always upload contracts reliably due to (Solidity) compiler incompatibilities.
So you want to be an Ethereum developer! Congrats, much treasure awaits you. Developing Ethereum dapps benefits from having a well-crafted development environment. This can often be daunting to beginners, so I'm giving you my favorite dev environment to help get you started.
Once your code fortress is constructed, you'll be able to
Following instructions from the excellent https://www.rinkeby.io/
A full node lets you access all state. There is a light node (state-on-demand) and wallet-only (no state) instructions as well,