Blog

By:

Seanpm2001, Et; Al.

Top

`README.md`

Read this article in a different language

Sorted by: A-Z

Translations in languages other than English are machine translated and are not yet accurate. No errors have been fixed yet as of March 21st 2021. Please report translation errors here. Make sure to backup your correction with sources and guide me, as I don’t know languages other than English well (I plan on getting a translator eventually) please cite wiktionary and other sources in your report. Failing to do so will result in a rejection of the correction being published.

Note: due to limitations with GitHub’s interpretation of markdown (and pretty much every other web-based interpretation of markdown) clicking these links will redirect you to a separate file on a separate page that isn’t the intended page. You will be redirected to the .github folder of this project, where the README translations are hosted.

Translations are currently done with Bing translate and DeepL. Support for Google Translate translations is coming to a close due to privacy concerns.

Index

00.0 – Top

00.1 – Title

00.2 – Read this article in a different language

00.3 – Index

04.1 – Pre-history

04.2 – Alpha History

04.3 – Beta History

04.4 – Modern History

05.0 – Copying

06.0 – Credits

07.0 – Installation

08.0 – Version history

09.0 – Version history

10.0 – Software status

11.0 – Sponsor info

12.0 – Contributers

13.0 – Issues

13.1 – Current issues

13.2 – Past issues

13.3 – Past pull requests

13.4 – Active pull requests

14.0 – Resources

15.0 – Contributing

16.0 – About README

17.0 – README Version history

18.0 – Footer

18.9 – End of file

<repo_description>

About

See above.

Wiki

Click/tap here to view this projects Wiki

If the project has been forked, the Wiki was likely removed. Luckily, I include an embedded version. You can view it here.

History

Write about this projects history here.

Pre-history

No pre-history to show for this project.

Alpha history

No Alpha history to show for this project.

Beta history

No Beta history to show for this project.

Modern history

No Modern history to show for this project.

Copying

View the copying license for this project here (if you haven’t built the project yet with the makefile, here is the original link: COPYINGL

Please note that you also have to follow the rules of the GNU General Public License v3 (GPL3) which you can view here

Credits

View the credits file for this project and see the people who got together to make this project by clicking/tapping here

Installation

View the installation instructions file for this project here

Requirements: Read the instructions for more info, and get the latest up-to-date instructions here

Sponsor info

You can sponsor this project if you like, but please specify what you want to donate to. See the funds you can donate to here

You can view other sponsor info here

Try it out! The sponsor button is right up next to the watch/unwatch button.

Version history

Version history currently unavailable

No other versions listed

Software status

All of my works are free some restrictions. DRM (Digital Restrictions Management) is not present in any of my works.

This sticker is supported by the Free Software Foundation. I never intend to include DRM in my works.

I am using the abbreviation “Digital Restrictions Management” instead of the more known “Digital Rights Management” as the common way of addressing it is false, there are no rights with DRM. The spelling “Digital Restrictions Management” is more accurate, and is supported by Richard M. Stallman (RMS) and the Free Software Foundation (FSF)

This section is used to raise awareness for the problems with DRM, and also to protest it. DRM is defective by design and is a major threat to all computer users and software freedom.

Image credit: defectivebydesign.org/drm-free/…

Contributers

Currently, I am the only contributer. Contributing is allowed, as long as you follow the rules of the CONTRIBUTING.md file.

seanpm2001 – x commits (As of Yr, DoW, Month, DoM, at ##:## a/pm)

No other contributers.

Issues

Current issues

None at the moment
No other current issues

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Past issues

None at the moment
No other past issues

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Past pull requests

None at the moment
No other past pull requests

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Active pull requests

None at the moment
No other active pull requests

If the repository has been forked, issues likely have been removed. Luckily I keep an archive of certain images here

Read the privacy policy on issue archival here

TL;DR

I archive my own issues. Your issue won’t be archived unless you request it to be archived.

Resources

Here are some other resources for this project:

Project language file A

Join the discussion on GitHub

No other resources at the moment.

Contributing

Contributing is allowed for this project, as long as you follow the rules of the CONTRIBUTING.md file.

Click/tap here to view the contributing rules for this project

About README

File type: Markdown Document (*.md *.mkd *.markdown)

File version: 0.1.6 (Monday, August 23rd 2021 at 6:37 pm)

Line count (including blank lines and compiler line): 0,407

README version history

Version 0.1 (Sunday, March 21st 2021 at 7:50 pm)

Changes:

Started the file

Added the title section

Added the index

Added the about section

Added the Wiki section

Added the version history section

Added the issues section.

Added the past issues section

Added the past pull requests section

Added the active pull requests section

Added the contributors section

Added the contributing section

Added the about README section

Added the README version history section

Added the resources section

Added a software status section, with a DRM free sticker and message

Added the sponsor info section

ITERATION 5

Updated the title section

Updated the index

Added the history section

Updated the file info section

Updated the file history section

ITERATION 6

Updated the title section

Fixed and update template links

Updated the index

Added the copying section

Added the credits section

Added the installation section

Updated the resources section

Updated the contributors section

Added the technical notes section

Updated the footer

Updated the file info section

Updated the file history section

No other changes in version 0.1

Version 1 (Coming soon)

Changes:

Coming soon

No other changes in version 1

Version 2 (Coming soon)

Changes:

Coming soon

No other changes in version 2

You have reached the end of the README file

( Back to top | Exit to GitHub | Exit to Bing | Exit to DuckDuckGo | Exit to Ecosia )

EOF

TermLink

Prepare an ontology and send it to the Precision Health Cloud.

Termlink is a command line client and library for uploading ontologies to LifeOmic’s Precision Health Cloud. Its goal is to make uploading standardized ontologies easier and to provide utilities for uploading custom ontologies. It provides a simple command line interface for creating standard ontologies and a Python SDK for building integrations with custom ontologies.

Quickstart

Download the following tools:

Docker

Pull the latest version of TermLink from Docker Hub:

docker pull lifeomic/termlink

Run it.

docker run lifeomic/termlink --help

Import the output ontology into the Precision Health Cloud using the LifeOmic CLI:

docker run lifeomic/termlink ... | lo ontologies import <project>

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

The following tools are required to run TermLink:

Installing

The following steps will guide you through installing the project locally.

Clone the git repository onto your local machine.

git clone git@github.com:lifeomic/termlink.git && cd ./termlink

Using Python 3, create a virtualenv and then activate it.

python3 -m venv venv && source venv/bin/activate

Note: Your Python binary may be under a different name.

Check that your local version of Python is at least version 3.7 by running python --version.

Once you have verified your version of Python is correct, run the following to download all dependencies.

pip install -r requirements.txt

pip install -r requirements-dev.txt

You now have everything you need to start developing on Termlink.

Testing

This project uses the Python nose framework.

Unit Testing

Run unit tests with yarn:

yarn test

Test coverage is enforced using the coverage.py module. Inspect the test coverage with:

yarn inspect

Deployment

TermLink is published on:

PyPI: Python package.
Docker Hub: Packaged runtime environment.
GitHub: Python package and source files.

Documentation is published on GitHub Pages.

To publish a new version run the following command:

yarn version

You will be promoted to enter a new version. Please use SemVer versioning for incrementing versions. To learn more about why SemVer is used, see the section on Versioning below.

This will trigger the deployment pipeline on Travis CI.

Built With

Docker: “Build, Ship, and Run Any App, Anywhere.”
Python 3: “Python is a programming language that lets you work quickly and integrate systems more effectively.”
Requests: “Requests is an elegant and simple HTTP library for Python, built for human beings.”

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

The following guidelines are provided on the SemVer website:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,

MINOR version when you add functionality in a backwards-compatible manner, and

PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Authors

Taylor Steinberg – Initial work – tdstein

See also the list of contributors who participated in this project.

License

This project is licensed under the MIT – see the LICENSE file for details.

Acknowledgments

[TODO]

TermLink

Prepare an ontology and send it to the Precision Health Cloud.

Termlink is a command line client and library for uploading ontologies to LifeOmic’s Precision Health Cloud. Its goal is to make uploading standardized ontologies easier and to provide utilities for uploading custom ontologies. It provides a simple command line interface for creating standard ontologies and a Python SDK for building integrations with custom ontologies.

Quickstart

Download the following tools:

Docker

Pull the latest version of TermLink from Docker Hub:

docker pull lifeomic/termlink

Run it.

docker run lifeomic/termlink --help

Import the output ontology into the Precision Health Cloud using the LifeOmic CLI:

docker run lifeomic/termlink ... | lo ontologies import <project>

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

The following tools are required to run TermLink:

Installing

The following steps will guide you through installing the project locally.

Clone the git repository onto your local machine.

git clone git@github.com:lifeomic/termlink.git && cd ./termlink

Using Python 3, create a virtualenv and then activate it.

python3 -m venv venv && source venv/bin/activate

Note: Your Python binary may be under a different name.

Check that your local version of Python is at least version 3.7 by running python --version.

Once you have verified your version of Python is correct, run the following to download all dependencies.

pip install -r requirements.txt

pip install -r requirements-dev.txt

You now have everything you need to start developing on Termlink.

Testing

This project uses the Python nose framework.

Unit Testing

Run unit tests with yarn:

yarn test

Test coverage is enforced using the coverage.py module. Inspect the test
coverage with:

yarn inspect

Deployment

TermLink is published on:

PyPI: Python package.
Docker Hub: Packaged runtime environment.
GitHub: Python package and source files.

Documentation is published on GitHub Pages.

To publish a new version run the following command:

yarn version

You will be promoted to enter a new version. Please use SemVer versioning for incrementing versions. To learn more about why SemVer is used, see the section on Versioning below.

This will trigger the deployment pipeline on Travis CI.

Built With

Docker: “Build, Ship, and Run Any App, Anywhere.”
Python 3: “Python is a programming language that lets you work quickly and integrate systems more effectively.”
Requests: “Requests is an elegant and simple HTTP library for Python, built for human beings.”

Contributing

Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.

Versioning

We use SemVer for versioning. For the versions available, see the tags on this repository.

The following guidelines are provided on the SemVer website:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,

MINOR version when you add functionality in a backwards-compatible manner, and

PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Authors

Taylor Steinberg – Initial work – tdstein

See also the list of contributors who participated in this project.

License

This project is licensed under the MIT – see the LICENSE file for details.

Acknowledgments

[TODO]

ZeroDoor

A script written lazily for generating reverse shell backdoors on the go whenever you need without any hassle for your daily penetration needs .
These backdoors are not james bond high tech stuff but rather simple ones to prevent over exploitation and limited capabilities
Once you generate the payload somehow execute on the conecrened system eithe Win or nix based systems .
Once executed you will have the capability of executing remote commands on the compromised host 🙂
Happy Hacking 😀

Usage

python zerodoor.py

Tiny Overview

Nothing special it includes three basic backdoor generation capability for :-

Nix Based
Windows ( Normal executable / PowerShell One Liner / JavaScript Backdoor )

Poweshell payload generation have been added due to its sofistication and presistence 🙂

Hot Updates ?

Added docker suppport
JS support

Author

Souhardya Sardar is a lazy guy who keeps learning and gets trolled by experts
Github :- github.com/Souhardya

Donate and contact :3

If you want to do any python based project with me please kindly mail me at Souhardya@protonmail.com
Or reach me on facebook :- facebook.com/SouhardyaSardar.py

If you like my code :3 buy me a beer

Bitcoin Address :- 1EyfivBCpdxKonG9imh8Mib3Bgeuy8cV8F

Open Source

Redistribute and Modify without any restrictions 🙂

If you encounter any problems regarding the code please open
a issue at my repository and I will try to fix it as
soon as possible . Maybe later cuz I am hell lazy

Illegal Usage is not allowed !!

Python2 Support only 🙂

You can help me implement a python3 version too

Procedural FPS Animations Plugin

Plugin for Unreal Engine 4/5 👁‍🗨 Add procedural animations to your FPS by using Curves 🔫

If you find this asset useful, please support it by giving a “★ Star” to the repository, thank you!

Description

Latest Update: September 10th, 2022

Note: A good understanding of Blueprints & Curves will be useful in order to modify content.

Official Website / GitHub Profile

📚 Overview

This tool allows you to create several animations for a First Person Shooter by editing Unreal Engine Curves. It also includes data based weapon sway. If you need more help to include this plugin to your project, you can contact me at contact@gerlogu.com.

📣 Content

This is what you can modify:

Curves
Blueprints
Components
Data Values
…and everything you need 😉

🗣 Contact

If you have any questions, contact me and I will answer you and include your question into the User’s Manual.

OFFICIAL WEBSITE: www.gerlogu.com
CONTACT EMAIL: contact@gerlogu.com

⚠ Disclaimer

No enemy nor Fire events like bullet spawning are included.

Technical Information

Features:

Custom Movement Sway by editing Component Variables.
Custom Camera Sway by editing Component Variables.
Custom Animations by editing Curves.
5 Example Animations INCLUDED.

Number of Blueprints: 1

Number of Components: 1

Number of Scripts: 5

Input:

Action Mappings

Jump: Gamepad Face Button Down | Spacebar
Fire: Left Click

Axis Mappings

HorizontalMovement: D (1.0) | A (-1.0) | Gamepad Left Thumbstick X-Axis (1.0)]
VerticalMovement: W (1.0) | S (-1.0) | Gamepad Left Thumbstick Y-Axis (1.0)]

Network Replicated: No

Supported Development Platforms:

Windows
Linux
Mac

Important/Additional Notes: Contact me and I will answer you and include your question into the User Manual.

Near Protocol | Web4 Profile Widget

A working example of deploying widget process on near.social BOS
Demo · Explore other examples · Report Bug

Developed by

Near Ukrainians Guild is a fast-growing guild based in Ukraine, aimed at providing high-quality educational content and assistance to grow a strong community of developers/entrepreneurs within the Near Protocol ecosystem

About The Project

This example covers the process of deploying your own widget on top of near.social BOS & SocialDB

If you’re not familiar with BOS & SocialDB concepts, read these resources before following further:

https://near.org/blog/near-announces-the-blockchain-operating-system

https://docs.near.org/discovery/tutorial/quickstart

https://thewiki.near.page/near.social_docs

The widget uses factory smart contract written on Near Protocol to deploy Web4 Profile on your behalf

Built With

Getting Started

💡 Before you begin, make sure you have the following installed

Prerequisites

Follow these simple instructions to setup the required dependencies before usage

Clone the repo

git clone https://github.com/nearuaguild/web4-profile-widgets.git

Install project dependencies
```
npm install
```
Install near-social binary to be able to deploy widgets to SocialDB by single command
```
cargo install --git https://github.com/FroVolod/near-social
```

Development

JSX files in this repository are NEAR Social widgets, so before you start, get familiar with these resources about platform:

Making Changes to common.jsx

common.jsx contains a set of shared utilities that is often reused within the project

When you need to change it, just edit the file in the root of the project, and update the widgets with this one command

npm run build

Code Formatter

This project is following prettier to unify code formatting

If you’re going to follow as well then use this command

npm run fmt

Deployment

Follow these simple instructions to deploy your widgets

Build project
```
npm run build
```
Apply code style
```
npm run fmt
```
Run deploy command and follow the interactive questionary
```
near-social deploy
```

After successful deployment, you will see a full command that could be used to re-deploy the widgets without interactive questionary, like this

Keys are provided here just for example

near-social deploy web4_profile.testnet sign-as web4_profile.testnet network-config testnet sign-with-plaintext-private-key --signer-public-key ed25519:6jRoreKb7RXAQZBuKZs7WDzsFHHrg62GkMmkXuiWqtKm --signer-private-key ed25519:edpktx799pgw7M4z8551URER52VcENNCSZwE9f9cst4v6h5vCrQmJE send

Usage

Once deployed, follow link, like this, to open widget

Keep in mind you need to replace YOUR_ACCOUNT_ID with actual account you’ve deployed widgets to

https://test.near.social/#/YOUR_ACCOUNT_ID.testnet/widget/pages.Home

License

Distributed under the MIT License. See LICENSE.txt for more information.

在 WindowsScriptHost 的 JScript 内使用 prompt/InputBox
Use prompt/InputBox in JScript on WindowsScriptHost

注意：JScript 不是现在浏览器或 Node.js 里的 JavaScript 语言。
Notice: JScript is not current JavaScript language in Browser or Node.js.

和 VBS 一样，你可以双击使用 WScript 运行，或使用 CScript 在命令行内运行。
As with VBS, you can double-click to run with WScript, or use CScript to run from within the command line.

背景
Background

WindowsScriptHost 执行速度比 PowerShell 快得多，并且兼容性也更广，从 Win XP 到 Win 11 都能支持。所以我写的很多脚本是用 WindowsScriptHost 运行的。
WindowsScriptHost executes much faster than PowerShell and is more compatible, from Win XP to Win 11. So many of the scripts I write run in WindowsScriptHost.

WindowsScriptHost 支持 VBScript 和 JScript 两种语言，基于 ECMAScript3 的 JScript 语法写起来肯定是比 VBScript 要简单快捷的，还可以支持一些新对象的 polyfill。
WindowsScriptHost supports VBScript and JScript, and the JScript syntax based on ECMAScript3 is certainly easier and faster to write than VBScript, and it can also support polyfills for some new objects.

但是 JScript 不支持 VBS 的 InputBox （甚至 C# 都不支持，也得调用 VB.Net），所以我收集和书写了几种实现方案来分享。这些原始代码基本都是 2015 年收集和书写的，但是我今天将他们进行了优化。
However, JScript doesn’t support VBS’s InputBox (and even C# doesn’t support it, so you have to call VB.Net), so I’ve collected and written a few implementations to share. Most of the original code was collected and written in 2015, but I’ve optimized it today.

解决方案
Solution

Type-A: MSScriptControl.ScriptControl

Code File: Type-A

原理：用 MSScriptControl.ScriptControl 对象运行 VBS 代码
Principle: Run VBS code by MSScriptControl.ScriptControl Object

Licence

原始代码来自于 Demon’s Blog ，所以此版本具有独立的许可证署名-非商业性使用-相同方式共享 2.5 中国大陆
The original code comes from Demon’s Blog, so this version has a separate license. Attribution-Noncommercial-Share Alike 2.5 China Mainland

我 2015 年发现这个代码无法在 64 位 Windows 运行，经检查发现 MSScriptControl.ScriptControl 只有 32 位的文件，因此需要用 32 位 WScript 运行才能正常使用。我在这个示例代码的开头部分加入了 64 位系统重定向到 32 位 WScript 运行的代码。
I found out in 2015 that this code does not work on 64-bit Windows, and upon inspection found that MSScriptControl.ScriptControl only has a 32-bit file, so I need to use 32-bit WScript Run to work properly. I’ve added code at the beginning of this sample code that redirects a 64-bit system to a 32-bit WScript run.

Type-B: Another VBS

Code File: Type-B

原理：在系统临时文件夹生成一个 VBS 文件用来执行 InputBox，通过标准输入流输入函数参数和标准输出流读取返回值。
Principle: Generate a VBS file in the temporary folder of the system to execute the InputBox, and read the return value through the input function parameters of the standard input stream and the standard output stream.

这个 InputBox 函数完全是我自己独立想出来的方法。因为需要启动一个另外的进程执行 VBS，缺点是InputBox 弹出框后的 MsgBox 不在前台。
This InputBox function is something I came up with on my own. Because need to start another process to execute VBS, the disadvantage is that the MsgBox after the InputBox pop-up box is not in the foreground.

Type-C: WSF file

Code File: Type-C

原理：WSF 文件支持不同代码混写，可以使用其他代码的函数。所以在 WSF 文件里运行 VBS，来调用 InputBox
Principle: WSF files can be mixed with different codes, and functions from other codes can be used. So run VBS in a WSF file to call InputBox

这是我发现 WSF 这种格式后想出来的方法，最大的缺点这种格式就是没有语法高亮支持，写东西很麻烦。
This is the method I came up with after discovering the WSF format, and the biggest drawback of this format is that it doesn’t have syntax highlighting support, and it’s cumbersome to write.

官方文档链接
Link to official documentation

Description

Semplate is a Java library to create and maintain markdown documents by:

adding semantic information
using user defined templates

It works with both Markdown and Asciidoc and may work with other markdown flavors.

More comprehensive documentation can be found in the GitHub Pages

Quick overview on how to use the Semplate library

❕ Exception handling in not shown in the following examples.

Create a class for the data object making sure it is annotated for semplate, e.g.

     import semplate.annotations.*;

       @Templatable
       public class ADR {

       @TemplateField
       private Integer id;

       @TemplateField
       private String name;

       @TemplateField
       private final String status;

       /* Setters and getters */
   }

Create a template file in markdown, e.g.:

  <!--{{template.comment}}-->

  # {{id}}. {{name}}

  ## Status

  {{status}}

  ## Context

  *Record the architectural decisions made on this project.*

  ## Decision

  **We will use Architecture Decision Records, as described by Michael Nygard in [this article: ](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions)**

Generate a markdown file using the data in an object. The markdown file will be semantically annotated.

    ADR adr = new ADR();
    adr.setId(12);
    adr.setName("Use a graph database");
    adr.setStatus("Proposed");

    SemanticWriter.with(adr)
                  .usingTemplate(path_to_template_file)
                  .write(path_to_markdown_file);

Generate a data object by reading in the generated (semantically annotated) markdown file.

    ADR adr = (ADR) SemanticReader.with(ArchitectureDecisionRecord.class)
                                  .usingFile(path_to_markdown_file)
                                  .read();   

    assertEquals(12, adr.getId());
    assertEquals("Use a graph database", adr.getName());

Update an existing (semantically annotated) markdown file

   ADR updatedADR = adr.clone();
   updatedADR.setStatus("Agreed");

   SemanticWriter.with(updatedADR)                 
                .usingFile(path_to_input_semantic_file)
                .write(path_to_updated_semantic_file);