| # Use this to block Spotify ad servers | |
| # sources: | |
| # https://www.reddit.com/r/Piracy/comments/4kn6rq/comprehensive_guide_to_blocking_ads_on_spotify/ | |
| # https://gist.github.com/teomaragakis/cb187d880c9a3ca2c8a2 | |
| # https://gist.github.com/Shujito/b7a8f8f971b22f49b4313d7d3e8e6931 | |
| # https://gist.github.com/rifkyekayama/f7c43e470f23878b20416e68f73829dc | |
| # https://gist.github.com/shokoylele/8f4160a102480471cb946fbd800bc86a | |
| ############## Begin manual list | |
| # 127.0.0.1 spclient.wg.spotify.com # might block the entire Spotify app from working too |
One of the most common projects I've seen for ComputerCraft is to write an operating system. People look at the limited command-line interface that CraftOS provides, and think, "I want this to work like my normal computer does!" Time and time again, a new post pops up on the ComputerCraft forums or Discord either announcing an OS, or asking for help with an OS, or releasing an OS. Usually, there are some very obvious flaws in these "OS"es, ranging from poor design choices, to overstating what they are and underdelivering. There are many common misunderstandings and undersights that newbie developers run into when writing an operating system, and these end up creating mediocre products at best.
The term "OS" is thrown around a lot, and in my opinion it's very overused. According to [Wikipedia]: "An operating system (OS) is system software that manages computer hardware, software resources, and provides common services for computer programs." However, m
Made possible with this reddit post.
wine regedit wine-breeze-dark.reg
wine regedit wine-reset-theme.reg
| <?php | |
| if ( ! function_exists('config_path')) | |
| { | |
| /** | |
| * Get the configuration path. | |
| * | |
| * @param string $path | |
| * @return string | |
| */ |
| /* This is an Example for a gallery-item in Elementor Custom CSS with Media Queries for different Elements */ | |
| /* Small devices (mobile/tablets, 767px and below) */ | |
| @media only screen and (max-width: 766px) { | |
| selector .gallery-item img { | |
| object-fit: cover; | |
| height: 18.5em | |
| } | |
| } |
| // Quite minimal example showing how to configure MPSSE for SPI using libftdi | |
| // compile like this: g++ minimal_spi.cpp -o minimal_spi -lftdipp -lftdi | |
| #include <ftdi.hpp> | |
| #include <usb.h> | |
| #include <stdio.h> | |
| #include <iostream> | |
| #include <string.h> | |
| // UM232H development module | |
| #define VENDOR 0x0403 |
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.
