The best way to safely and securely use local domains pointing to 127.0.0.1 is to edit your local settings (/etc/hosts) and add your own settings. Keep in mind if you want to use subdomains, you need to enter all variations.
Example:
# Adding bottom of your current file /etc/hosts
################# MY LOCAL DOMAINS
127.0.0.1 local.com admin.local.com
127.0.0.1 domain1.com
vsix-bookmarklet, create a bookmark in your browser.
*.vsix.
With the addition of ES modules, there's now no fewer than 24 ways to load your JS code: (inline|not inline) x (defer|no defer) x (async|no async) x (type=text/javascript | type=module | nomodule) -- and each of them is subtly different.
This document is a comparison of various ways the <script> tags in HTML are processed depending on the attributes set.
If you ever wondered when to use inline <script async type="module"> and when <script nomodule defer src="...">, you're in the good place!
Note that this article is about <script>s inserted in the HTML; the behavior of <script>s inserted at runtime is slightly different - see Deep dive into the murky waters of script loading by Jake Archibald (2013)
If you have more you can still use this method (3 accounts per instance)
⚠ This guide is for the app available here: https://desktop.telegram.org/ not the one in the Mac/Windows App Store. For the Mac App Store app this should work: https://gist.github.com/Nachtalb/ec590dc974f6ba4674972d4937b230be/#gistcomment-3611415 ⚠
| #!/bin/bash | |
| # Author: Matt Mastracci ([email protected]) | |
| # AppleScript from http://stackoverflow.com/questions/4309087/cancel-button-on-osascript-in-a-bash-script | |
| # licensed under cc-wiki with attribution required | |
| # Remainder of script public domain | |
| osascript -e 'tell application "iTerm2" to version' > /dev/null 2>&1 && NAME=iTerm2 || NAME=iTerm | |
| if [[ $NAME = "iTerm" ]]; then | |
| FILE=$(osascript -e 'tell application "iTerm" to activate' -e 'tell application "iTerm" to set thefile to choose folder with prompt "Choose a folder to place received files in"' -e "do shell script (\"echo \"&(quoted form of POSIX path of thefile as Unicode text)&\"\")") | |
| else |
| #!/bin/bash | |
| # Author: Matt Mastracci ([email protected]) | |
| # AppleScript from http://stackoverflow.com/questions/4309087/cancel-button-on-osascript-in-a-bash-script | |
| # licensed under cc-wiki with attribution required | |
| # Remainder of script public domain | |
| osascript -e 'tell application "iTerm2" to version' > /dev/null 2>&1 && NAME=iTerm2 || NAME=iTerm | |
| if [[ $NAME = "iTerm" ]]; then | |
| FILE=`osascript -e 'tell application "iTerm" to activate' -e 'tell application "iTerm" to set thefile to choose file with prompt "Choose a file to send"' -e "do shell script (\"echo \"&(quoted form of POSIX path of thefile as Unicode text)&\"\")"` | |
| else |
| #!/bin/bash -i | |
| #using shebang with -i to enable interactive mode (auto load .bashrc) | |
| set -e #stop immediately if any error happens | |
| # Install Open SDK | |
| apt update | |
| apt install openjdk-8-jdk -y | |
| update-java-alternatives --set java-1.8.0-openjdk-amd64 | |
| java -version |
| from mitmproxy.options import Options | |
| from mitmproxy.proxy.config import ProxyConfig | |
| from mitmproxy.proxy.server import ProxyServer | |
| from mitmproxy.tools.dump import DumpMaster | |
| import threading | |
| import asyncio | |
| import time | |
| class Addon(object): |
This isn't a guide about locking down homebrew so that it can't touch the rest of your system security-wise.
This guide doesn't fix the inherent security issues of a package management system that will literally yell at you if you try to do something about "huh, maybe it's not great my executables are writeable by my account without requiring authorization first".
But it absolutely is a guide about shoving it into its own little corner so that you can take it or leave it as you see fit, instead of just letting the project do what it likes like completely taking over permissions and ownership of a directory that might be in use by other software on your Mac and stomping all over their contents.
By following this guide you will:
sudo to forcefully change permissions of some directory to be owned by your account