I've been meaning to make a public private forum for my own purposes. Mainly to share solutions I've found for random shit. Maybe it'll help other people with the exact same problems or tangentially related problems. I don't know how often I'll actually use this if I'm honest with you. Who knows? Hopefully if you're here, it's because there's some data useful to you. Or because you're a stalker.
Whoo boy, this is probably going to get a lot of attention.
::: spoiler Background and Purpose I'm not an expert at Github or using git from the terminal. As a matter of fact, I've found it very confusing. So, I've written my own guide to sort of implant the process in my head and help out other dumb dumbs like me. Feel free to leave your commentary and suggestions in the comments. Most of the process of this guide can be found online, but Reddit sucks now and the guides on Github aren't all in one synthesized, cohesive guide for set up, at least not that I could find. Relevant links are listed in most steps.
::: spoiler Changelog Version 1.01 of this guide. V1.0: initial post V1.1: made more explicit the fact that you can change the SSH key name in step 1. Added additional commentary in step 3. Provided a general, brief overview of the process. Added additional instructions in step 3. :::
Usage guide: Each "step" is a stage in the process. Spoilers labelled "Commentary" contain additional information and author commentary. Spoilers labelled "Instructions" contain the instructions relevant to the step.
Overview: Create an SSH key on the machine you're using, then add it to your machine's agent. Following that, paste the .pub key into your github account, and then log into gh cli from the terminal to authorize git pushes to the registered account.
::: spoiler Commentary
Github's CLI software allows you to make a Github repo from the terminal. This link takes you to the installation page for Debian/Ubunutu linux distrubutions. The page has a sidebar with other OS installation instructions. There's a bunch of terminal code there to copy and paste into your own terminal, all that's needed is sudo permissions. :::
Follow this link for detailed installation instructions.
::: spoiler Commentary SSH stands for Secure Shell and, in brief, is what computers use to talk to each other. It relies on keys to work. In order to push to Github from the terminal/create repositories, you'll need an SSH key to connect your local machine to Github's servers and your github account. :::
::: spoiler Instructions
First, paste the following command into your terminal and replace the example email to whatever email you signed up with Github. ssh-keygen -t ed25519 -C "[email protected]". The second argument in the command (ed25519) is the encryption algorithm. If you have a different one you want to use, replace that with the algorithm you want (not advised). NOTE: DO NOT JUST HIT ENTER, if you wish to change the name see the next bullet point.
The followup prompt asks where you'd like to save the key. The stuff inside the parenthesis is the default location AND the default name. Hit enter to save it XOR type in a directory and file name to save the key under/in. You can use the same default directory and just change the name if you'd like.
The next followup prompt asks for a password. Give it one. On terminal, you won't see anything when you start typing the password; this is normal. If you mess up, just hold backspace for a while and then start typing again.
Next step is add the SSH key to your SSH agent. Prime the ssh agent in the background by putting eval "$(ssh-agent -s)" into the terminal. Then, just type ssh-add ~/.ssh/name-of-your-key into your terminal, replacing name-of-your-key with the name of your key established in the previous steps. At this point, your key is generated and ready for use. There is another step on the website, but I don't know if it's needed or useful; I didn't use it so whatever.
:::
::: spoiler Instructions
Open the .pub document in the folder you saved your key to, and copy the text. For CLI: type cat ~/.ssh/name-of-your-key.pub into your terminal, replacing name-of-your-key with the name of your key. This will output a bunch of text into your terminal, copy that text. If you saved the key to a different folder, replace ~/.ssh with the folder's directory.
On github, navigate to your account's settings page, and find the section titled "SSH and GPG keys." Under the section titled SSH keys, click "New SSH key," give it a title, and paste your key into the textbox.
Note: This process can be done via the terminal. The instructions will not be detailed here, but use gh auth login and follow the SSH path.
:::
::: spoiler Commentary
::: spoiler Instructions
gh auth login, and follow the command prompts. When it asks for SSH versus HTTPS, select HTTPS, use ctrl-shift-c to copy the code given, then hit enter to open a link to github's login page in your browser. Select the account you want to use, then paste the code. If you get the terminal output "Logged in as account-name" where account-name is your account name, then it worked.git config --global user.email "[email protected]" replacing [email protected] with your email, and then run 'git config --global user.name "Your Name"' replacing Your Name with whatever name you'd like.
:::::: spoiler Commentary
Now, you can make Github repositories from your terminal. Use the command gh repo create with no arguments to start the process. From here, you can manually create a new repo on Github, either from scratch or from a template repository. However, if you've started a project on your machine locally, and want to push it as a repo to Github, you'll have to turn it into a repo. This entire step follows that process. The directions though, are more or less straight from the gh repo create line following the "Push an existing local repository to github.com" path. You just need to do an extra step is all.
:::
Following is (sort of) a summary of this link: https://cli.github.com/manual/gh_repo_create, as well as the directions from gh repo create.
::: spoiler Instructions
cd. Then, type git init and press enter.gh repo create. The followup asks for the path; if you're not already in the current directory in your terminal for the repo, paste the file address for the repo. Otherwise, type a period and proceed from there. Give the repo a name, possibly a description, make it public or private, and add a remote.::: spoiler Commentary
"Pushing" means taking all the changes to a repo made on your machine (local changes) and putting them in a remote repository. Essentially, it's syncing the remote location of the repository with the local repository, with the remote repository inheriting changes from the local. The git program lets you push files and changes to files to github. Very nifty program, but very confusing, especially when merge conflicts start to crop up. This guide does not deal with merge conflicts because I do not know how to handle merge conflicts properly and they scare me. This step is more or less an overview of the flow to pushing changes to github. :::
Following is a self-written guide with no references to the internet, just what I've been taught previously. Guides for this process surely exist.
::: spoiler Instructions
First, all the changes to the local repository need to be staged, essentially gathered together. From the repo's local directory, use git add . to stage all changes made to the repository. If there's specific files you want to stage, replace the period with the name of the file.
Once added, the changes will need to be committed. This essentially is just preparing the changes made to be sent to the remote repo. Use the command git commit -m followed by a message to tag the commit with. The commit must have a message. If you don't include -m in the command, you'll be sent to the terminal file editor; I don't know how to use it because it scares me. If your message uses spaces, enclose the message in quotation marks.
Once committed, you're ready to push. Use git push to send the changes up. For the first push, you'll need to set up the upstream branch first, which can be done in the first push to the repository. What's an upstream branch you ask? I have no idea. Use the command git push --set-upstream origin master to push the changes. If you try to git push without doing this first, it'll tell you to do it first.
Now, if you make changes to the local repo, you can follow this entire step to add, commit, and then push the changes. If someone else makes changes to the remote repo, you can sync your local machine with those changes by doing git pull in the repo.
If you want to copy an entire repo from Github to your machine without already having it on there, use git clone https://github.com/repo-name-goes-here where repo-name-goes-here is the name of the repo. I don't believe you need to set up git authentication for this, but for pushing changes you likely will.
:::
My ENT a few years back gave me explicit instructions to use a nasal rinse morning and night. I've been using those little packets you can buy from various stores, but since the contents are literally baking soda and salt, I've decided to try my hand at making my own saline rinse solutions. Getting the ratios right is a touch difficult, so what follows are my notes so far.
TL;DR: Current least irritating solution is 1/2 teaspoon each of baking soda and salt with 8 ounces of water.
Kosher Salt and Baking Soda: Suggested recipe from the internet, 3 teaspoons salt to 1 teaspoon baking soda. Mix ingredients, then 1 teaspoon of the solution to 8 ounces of boiled (water that has been boiled).
Results: very irritating, uncomfortable. unsure whether kosher salt, baking soda, or solution not properly dissolved.
Sea Salt vs Kosher salt, no baking soda. 1/2 teaspoon to 8 ounces of boiling water each, waiting for each to cool. test results: sea salt produced no irritation, only a strange sensation mildly akin getting sea water up my nose. kosher salt produced a very minor irritation. Only 1 trial performed.
Sea salt vs Kosher salt, baking soda added. 1/2 teaspoon of either salt and 1/2 teaspoon of baking soda, 8 ounces of boiling water each, waited for solutions to cool. Mixing procedure notes: water fizzed up when poured over the solutions. used small white ceramic bowls, both solutions appeared milky white, sea salt solution to a greater degree. unsure if lighting issue, reflecting of the ceramic bowl on the liquid issue, or some other unknown variable. Test results: sea salt + baking soda solution produced very minor irritation, slightly greater than the irritation produced from kosher salt alone. Kosher salt + baking soda solution produced a greater amount of irritation, less than the suggested formula from the internet.
More trials on each needed. More types of salts needed. Salts used: sea salt from the sea salt grinder sold by Aldi's, kosher salt walmart brand. baking soda used: walmart brand baking soda. Salts to experiment with: canning salt, other brands of sea salt.
Wikihow suggests 1/4 teaspoon or 1/2 teaspoon of salt and equal amount baking soda. 1/2 teaspoon was tested, possibly do additional tests for 1/4 teaspoon. Internet recipe performed with Kosher salt and produced significant irritation, however, previous experiments showed Kosher salt on its own was noticeably more irritating than sea salt, possibly test internet recipe with sea salt to compare.
Prior to these tests, I created 8 cups of saline solution following 2.5 grams of sea salt to 8 ounces (1 cup) of water, as per I believe wikihow's instructions. Accidentally added more salt than called for due to scale powering off after a brief period of neglect. Stored solution in a large glass mason jar in my bathroom's... uh, pantry section I guess. My bathroom has a pantry without a door. Don't ask me, I rent this place. Anyways I used the solution to refill my nasal bottle, but after some days I noticed feeling slightly ill after using the solution. Unsure if infection caught from external circumstances or if solution became contaminated while use. Did not record time it was present in my bathroom for, or precisely when the solution began to produce strange symptoms after use. Upon preparing to use the last amount of the solution, noticed white particles floating in the liquid, unsure if undissolved salt or some other matter. Either way storage in this manner is likely not ideal but very convenient. Unsure how to proceed with storage. Store dry solution possibly, and partition out with boiled water as needed? Less convenient, especially since I go through 8 ounces of saline solution in about 2-3 days (4-7 uses). Attempt the large mason jar strategy, but store elsewhere? Humidity and heat from showers may have accelerated bacterial growth, perhaps storing in a drier, colder place may help. Storing in fridge is ideal but consumes a lot of space, maybe smaller reserves are ideal (2 cup mason jars are plentiful, replenish the nasal rinse device and store maybe 2 jar reserves in fridge for later use).
Nasal rinse device: Niel Med's squeeze bottle. Been using it for a while, directions instruct disposal of bottle after a month of use but that's dumb and wasteful, just clean the bottle with soap and water every once in a while, or bleach it if concerned about bacterial growth.
Inkarnate doesn't have an "upload image as background" feature by default. The known workaround is to upload your image as a texture, then scale and off-set the image until it's about the size of the canvas you selected, then fill the canvas using the menu. It's kind of obtuse. Linked below is a youtube video going over the process, though the UI elements are out of date, so you'll have to figure that out on your own.
So I have a VPN on my Linux (Mint) PC. Discord at one point didn't want to finish launching when I had it on; it would stall on the "Starting" popup with the actual discord window open but just a grey screen. Turning off the VPN and closing and reopening Discord allowed it to launch. Turning on the VPN at this point caused it to break somewhat, with me being unable to join voice chat or send messages, though if I was already in a voice chat, I would still be able to commune with the other voices. Launching discord from terminal while VPN is on shows the process stalling at "Splash.updateCountdownSeconds: undefined"
The issue sort of fixed itself though. After a while of having discord open with a VPN, it just kind of... stopped having the issue? I turn the VPN back on, it works as intended in all regards. I close discord and reopen, it opens with no issue. I have no idea what the original issue was at all. It's resolved but unknown what the resolution is, hence it's unsolved.
I was gifted a Tzumi brand Jobsite speaker. The peripherals card or whatever the hell that green wafer that holds all the ports for connections is called was misaligned, so I had to take it apart and fix it. Anyways here's the disassembly guide in text because I'm too lazy to make a video and also don't care enough to do so.
Step 0: Tools
You're gonna need a long Phillips screwdriver. Doesn't need to be precision, one of the heads on a six-in-one should fit fine, but the shaft needs to be at least 2 or 3 inches long, preferably longer. Idk I actually haven't measured how long the shaft is on the one I bought specifically for disassembling this speaker but you're gonna need it. Should be the only tool you need.
Step 1: Remove the metal mesh thing on the front.
Should just pop right out, may need to fiddle with it to get a good grip.
Step 2: Unscrew the screws.
There should be 7 screws holding down the front face to the back face together, they're at the bottom of these 7 really deep holes around the rim of the actual speaker pads or whatever they're called. Use a long screwdriver.
Step 3: Carefully separate the front from the back.
The cables connecting the speakers to the other stuff wasn't very long in my case, so I had to prop the front part on something to keep it from straining the cables too much because I don't actually know how much disrespect the device can take.
Step 4: Unscrew the peripheral ports chip card, realign, replace screws
Again I don't actually know what that wafer is called. Regardless, it's only held in place by two screws with washers soldered on them. Realign the chip properly by sliding the wings into the slots and rescrew the washer screws. Go back and forth doing each screw bit by bit since the shell and screw holes are rather cheap and can easily offset the chip if you're not careful about it.
Anyways once that's done just reseat everything and replace the screws. Should be fairly simple. I didn't do more than this since that was my only issue with it but once the speaker face is off the rest of the case, you should find it pretty easy to identify the rest of the parts of the speaker if you have a different issue with it.
I'm not seo'ing this post because then I'd have to do free advertising for a shitty product and I'm not doing that.
FOREWORD: I'm putting this in here because I'm not sure if it'll be accepted in the FFXIV community and I don't think it belongs in the FFXXXIV community. The guide covers nudity mod installation because I refuse to censor it. Anyways I'm simply going to paste a link to the google doc instead of copy pasting it, mainly because it's formatted for google docs and absolutely fuck everything about reformatting it.
https://docs.google.com/document/d/1IdTMAxquwBa__gdcV9KwYvjUD7kzxRuWrwO63rkBKq4/edit?usp=sharing
umm seo words
ffxiv linux ff14 final fantasy fourteen installation guide
This covers how I personally was able to make my panel background fully transparent, as well as a small amount of CSS editing for Linux Mint. My current version is 22.2.
In order to mess with the .css of your theme, you need to find where it's located, as well as which specific theme you're using. For me, my themes were located in the /usr/share/themes. There, you should see a bunch of folders named Mint followed by a letter and for most cases, a color. To find which theme you're currently using, what I did was go into my system settings, then into my themes settings. At the bottom, there are advanced settings: you should see to the right names that refer to the theme file name.
Look through the themes folder to find the specific one. In my case, I had Mint-Y-Dark-Purple. Enter the one that corresponds to your folder. Then, right click on the cinnamon folder and click open as root.
Inside, you'll find the cinnamon.css file. First, make a copy of that file and save it somewhere in case you break stuff. You'll need to find the section .panel-top, .panel-bottom, .panel-left, .panel-right. Under background color, change the value to transparent. That specific line in my file was line 420 (nice).
Edit 10/19: Removed chmod 777 advice, replaced with right click open as root advice. I did not know mint had that.