| #!/bin/sh | |
| print_usage() { | |
| echo "usage: compress_video <input_file>" | |
| echo "supported formats: mp4, webm, mkv, mov, avi, flv" | |
| } | |
| get_extension() { | |
| f="${1##*/}" | |
| case "$f" in |
Caution
As of April 7th 2026, Discord has expressed their intent to crack down on automating quest completion.
Some users have received the following system message:
There isn't much I can do to make the script undetected, so use it at your own risk, as you most likely WILL get flagged by doing so.
Wait, what?
Inspired by this awesome article.
According to wikipedia, OOP is a programming paradigm or technique based on the concept of "objects". The object structure contain data and behaviour.
Data is the object's state, which should be isolated and must be private.
| #!/usr/bin/env python3 | |
| """ | |
| Copyright 2019 StollD, 2019 vurpo | |
| Original: https://github.com/StollD/linux-surface-fix-eraser | |
| Licensed under GNU GPL version 3 | |
| """ | |
| import os | |
| import os.path |
| // Ark Labs presents - Slack dARK mode | |
| $slackBaseDir = "$env:LocalAppData\Slack" | |
| $installations = Get-ChildItem $slackBaseDir -Directory | Where-Object { $_.Name.StartsWith("app-") } | |
| $version = $installations | Sort-Object { [version]$_.Name.Substring(4) } | Select-Object -Last 1 | |
| Write-Output "Select highest intalled Slack version: $version"; | |
| $modAdded = $false; | |
| $customContent = @' |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>esptool.js</title> | |
| <script src="https://cdnjs.cloudflare.com/ajax/libs/xterm/2.9.2/xterm.min.js" integrity="sha256-8rsVcpCnO6HdeJL84i0VdubjM42fjSmO8aONghdq3gc=" crossorigin="anonymous"></script> | |
| <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/xterm/2.9.2/xterm.min.css" integrity="sha256-w69o8Y6P5VZjfYFmn2KlqMU7TUi2I+oWObi8FLlVZZg=" crossorigin="anonymous" /> | |
| </head> |
| [Unit] | |
| Description=RClone Mount (crypt) | |
| AssertPathIsDirectory=/mnt/decrypt | |
| After=plexdrive.service | |
| Requires=plexdrive.service | |
| PartOf=plexdrive.service | |
| [Service] | |
| Type=simple | |
| User=username |
| /* This has been added to CSS Protips https://github.com/AllThingsSmitty/css-protips */ | |
| /* The type font size in a responsive layout should be able to adjust with each viewport. | |
| You can calculate the font size based on the viewport height and width using :root */ | |
| :root { | |
| font-size: calc(1vw + 1vh + .5vmin); | |
| } | |
| /* Now you can utilize the root em unit based on the value calculated by :root */ | |
| body { |
Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.
In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.
Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j
http://www.thoughtworks.com/radar/#/languages-and-frameworks/683 - ThoughtWorks Technology Radar - January 2014
We continue to see teams run into trouble using JSF -- JavaServer Faces -- and are recommending you avoid this technology. Teams seem to choose JSF because it is a J2EE standard without really evaluating whether the programming model suits them. We think JSF is flawed because it tries to abstract away HTML, CSS and HTTP, exactly the reverse of what modern web frameworks do. JSF, like ASP.NET webforms, attempts to create statefulness on top of the stateless protocol HTTP and ends up causing a whole host of problems involving shared server-side state. We are aware of the improvements in JSF 2.0, but think the model is fundamentally broken. We recommend teams use simple frameworks and embrace and understand web technologies including HTTP, HTML and CSS.
