Vitor Anjos bartier

For my reference in the future I will record here the steps that I had to follow in order to install Openwrt on the tp-link router EX220. This was done using a Windows 11 machine.

Disclaimer: Use this tutorial at your own risk. We are not responsible for any damage/harms done to your device using the information from this tutorial.

Steps to install OpenWRT on EX220 router

OEM installation using the serial + TFTP method

These are the steps provided at the official https://openwrt.org/toh/tp-link/ex220_v1 page:

Authorize gcloud to access the Cloud Platform with Google user credentials

$ gcloud auth login

Configure kubectl tool

$ gcloud container clusters get-credentials kubeernetes --zone us-central1-a --project camel-knative

Ever wanted to delete all your likes/favorites from Twitter but only found broken/expensive tools? You are in the right place.

Go to: https://twitter.com/{username}/likes
Open the console and run the following JavaScript code:

setInterval(() => {
  for (const d of document.querySelectorAll('div[data-testid="unlike"]')) {
    d.click()
 }

GENERATORS:

Text Content Generator - http://www.lipsum.com
Favicon Generator - http://tools.dynamicdrive.com/favicon
Data Generator - https://mockaroo.com/
Mobile Mockup Generator - https://mockuphone.com
Logo Generator - https://www.logaster.com
UUID Generator - https://www.uuidgenerator.net/
Hash Generator - https://passwordsgenerator.net/sha256-hash-generator/
Ultimate Code Generator - https://webcode.tools/

Usar ssh do github com wifi do netcombo

A NET parece que só libera o uso de qualquer porta, como a porta 22 de ssh, para pessoa jurídica em seus novos planos (desde 2016).

Para conseguir usar o github por ssh com plano de internet da NET para pessoa física, é necessário:

Criar o arquivo ~/.ssh/config e adicionar:

Host github.com

Project Title

One Paragraph of project description goes here

Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

Prerequisites

People

`:bowtie:`	😄 `:smile:`	😆 `:laughing:`
😊 `:blush:`	😃 `:smiley:`	☺️ `:relaxed:`
😏 `:smirk:`	😍 `:heart_eyes:`	😘 `:kissing_heart:`
😚 `:kissing_closed_eyes:`	😳 `:flushed:`	😌 `:relieved:`
😆 `:satisfied:`	😁 `:grin:`	😉 `:wink:`
😜 `:stuck_out_tongue_winking_eye:`	😝 `:stuck_out_tongue_closed_eyes:`	😀 `:grinning:`
😗 `:kissing:`	😙 `:kissing_smiling_eyes:`	😛 `:stuck_out_tongue:`

	// ==UserScript==
	// @name Slack: Always Stay Active
	// @namespace https://ericdraken.com/slack-always-stay-active
	// @version 1.0.4b
	// @description Always stay active on Slack.
	// @author Eric Draken (ericdraken.com), THOUSAND-SKY, pannal
	// @match https://app.slack.com/client/*
	// @icon https://www.google.com/s2/favicons?domain=slack.com
	// @grant unsafeWindow
	// @run-at document-start

	#!/usr/bin/env bash

	# this can be useful when developing against a custom DNS server, or
	# for example, if you made a change to the DNS settings of a domain, and you
	# know the authoritative nameserver IP address for a domain, you could use this
	# to bypass the intermediate DNS cache, and apply an HTTP request using the new
	# DNS settings supplied by your specified (authoritative) nameserver

	curl --dns-servers <DNSIP,DNSIP> url.com