text:
# Examining DuckDuckGo on Android
## A Mobile Forensics Perspective

### Overview
When people use the DuckDuckGo mobile app, they generally associate it with enhanced privacy while browsing the Internet.
With the easily accessible flame icon that allows users to "Clear All Tabs and Data", users may inherently believe their
browsing history is wiped the moment they see the flame animation clear their currently open tabs and history. From a
forensics perspective, we should be asking: How well does DuckDuckGo clear user data which could be useful in a mobile
forensics investigation?

By examining the DuckDuckGo application and its underlying storage on an emulated Android device, we can determine that
DuckDuckGo can still provide a variety of useful forensic artifacts to an examiner. In balancing user experience with
privacy, forensic examiners can recover artifacts such as application information, bookmarks, and residual user data even
after being "cleared" by the user.

To reach this determination, we can use the Nox Player Android emulator and a variety of tools to explore how
DuckDuckGo stores, persists, and clears user data. Special thanks to Jessica Hyde (@B1N2H3X) for her guidance and
advice over the course of this project and to Alexis Brignoni (@AlexisBrignoni) for his article on Android emulation[1]
which was the foundation used for testing DuckDuckGo on an emulated Android device.

### Tools Utilized
 - Nox Player (Version <IP_ADDRESS>5)
 - Android (Version 5.1.1 - SM-G950N)
 - DuckDuckGo (Version 5.21.2 mk - 52102)

### Analysis of DuckDuckGo's Underlying Storage
In my testing, the majority of the user data for DuckDuckGo was stored in: `/data/data/com.duckduckgo.mobile.android`

Within the above directory, DuckDuckGo data is broken up into 5 subdirectories with a specific purpose:
 - databases: DuckDuckGo application databases
 - cache: duckduckgo.com cache
 - app_webview: web browsing cache and databases
 - shared_prefs: DuckDuckGo application configuration files
 - files: DuckDuckGo application support files (trackers whitelist, helper scripts, etc.)

### Artifacts of Interest
Having examined the data pulled back from the device, I found the following artifacts to be of potential forensic interest:
1. 'databases/app.db' - SQLite3 database containing tables for artifacts such as bookmarks, tabs, sites visited, and app
usage
2. 'databases/http_auth.db' - SQLite3 database containing a table for authentication information for successful HTTP
authentication attempts
3. 'cache/*' - The primary cache for duckduckgo.com interaction
4. 'app_webview/Cache/*' - The cache for all other sites interacted with through the DuckDuckGo app
5. 'app_webview/Cookies' - SQLite3 database containing cookies from web browsing
6. 'app_webview/Web Data' - SQLite3 database containing autofill data from web browsing
7. 'shared_prefs/*.xml' - XML formatted files which contain summary data about the DuckDuckGo application to include the
installation time and the last cleared time

### Python Parser
To aid in analysis of DuckDuckGo data, I wrote a parser in Python 3 which provides summary data about DuckDuckGo and
artifacts of potential interest. All of the above artifacts are currently parsed[2]. This has been manually tested and
verified with HxD and DB Browser for SQLite.

The parser can be found on GitHub at [https://github.com/ItWasDNS/DDG-Parser] and is structured as a set of modules
which can be ran individually or as a group for bulk processing. Future work could include processing additional tables
from the databases and enhancing the cache extraction to parse more data.

To run all modules, run the below command and follow the prompt:
```
python3 process_duckduck.py
```

Note: User will be prompted for DuckDuckGo application data directory. This directory does not need to be
com.duckduckgo.mobile.android but should contain DDG application data.

### Footnotes
1. [Viewing extracted Android app data using an emulator](
https://abrignoni.blogspot.com/2017/08/viewing-extracted-android-app-data.html)
2. All 7 artifacts of interest listed are parsed but there may be additional items of interest within each artifact
which can be parsed to a greater extent

repository: ItWasDNS/DDG-Parser

repo_name: ItWasDNS/DDG-Parser


text:
# Voorhees
Express middleware to determine if JSON should assault your client.

## Huh?
Voorhees is an express middleware module that will call the [response](https://expressjs.com/en/4x/api.html#res) object's [json](https://expressjs.com/en/4x/api.html#res.json) or [render](https://expressjs.com/en/4x/api.html#res.render) functions, depending on if the [request](https://expressjs.com/en/4x/api.html#req) object's [xhr](https://expressjs.com/en/4x/api.html#req.xhr) property is either true (will call `json()`) or false (will call `render()`)

## Usage
Voorhees can be applied as middleware for your entire app
```javascript
let express = require('express')
let app = express()
let voorhees = require('voorhees')

app.use(voorhees)
```

Or can be applied to a specific route
```javascript
let express = require('express')
let router = require('express').Router
let voorhees = require('voorhees')

router.use(voorhees)
```

In either case, voorhees applies itself as a property`voorhees` on the response object. This can then be accessed by your route handling code and calling the `respond()` function:
```javascript
router.get('/', function (req, res){
  res.voorhees.respond('view/path', {'yourData': foo})
})
```

Now, your response will either be JSON (if request was called via ajax), or will render your view as HTML.

license: MIT

repository: sarcastech/voorhees

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: sarcastech/voorhees


text:
# google-releated-searches

scrap related searches on Google.

[![js-standard-style](https://cdn.rawgit.com/feross/standard/master/badge.svg)](https://github.com/feross/standard)

[![version](https://img.shields.io/npm/v/google-releated-searches.svg) ![download](https://img.shields.io/npm/dm/google-releated-searches.svg)](https://www.npmjs.com/package/google-releated-searches)

## Important

* The unofficial module to crawl the content of the site.
* Therefore, whenever it may not be a normal operation, if problems occur, please add the issue.

## Related searches
People whose searches match the restrictions most often searched for these terms too.

[Go to explore page](https://www.google.com/trends/explore#q=%EC%A7%80%EC%A7%84&date=now+7-d&geo=KR)

![Related searches](google-releated-searches.png "Related searches")

## Usage

```javascript
var related = require('./')

related.load({ term: '지진', countries: ['kr'] }, function (err, result) {
  console.log(err, JSON.stringify(result))
})

```

```javascript
// output
{
  "kr": {
    "top": [
      {
        "term": "군산지진",
        "link": "https://www.google.com/search?q=%EA%B5%B0%EC%82%B0%EC%A7%80%EC%A7%84",
        "value": null
      },
      // ...
      {
        "term": "지진운",
        "link": "https://www.google.com/search?q=%EC%A7%80%EC%A7%84%EC%9A%B4",
        "value": 450
      }
    ],
    "rising": [
      {
        "term": "익산지진",
        "link": "https://www.google.com/search?q=%EC%9D%B5%EC%82%B0%EC%A7%80%EC%A7%84",
        "value": 100
      },
      // ...
      {
        "term": "전북지진",
        "link": "https://www.google.com/search?q=%EC%A0%84%EB%B6%81%EC%A7%80%EC%A7%84",
        "value": 10
      }
    ]
  }
}
```

## List of Google domains

https://en.wikipedia.org/wiki/List_of_Google_domains

## LICENSE

google-releated-searches is licensed under the MIT license.

repository: egg-/google-releated-searches

repo_name: egg-/google-releated-searches


text:
# watch-aprs

Monitor and decode APRS packets arriving on a KISS-over-TCP device.

This is a command-line utility that decodes APRS packets and prints them
out to the console in more-or-less human-readable form.  It's useful with
ports that have been made available by the share-tnc utility, or with ports
that directly implement KISS-over-TCP, like the Direwolf sound card interface.

# Hardware/Software Environment

watch-aprs uses 'node.js'.  It has been tested most
heavily on a Raspberry Pi running Raspbian Jessie, but has been casually tested on
Windows 10, Linux Mint and MacOS Sierra, and appears to work fine.  Please file a
report if you experience difficulties.

# Installation

If you need to use 'sudo' to install globally, use
the following:

    sudo npm install -g watch-aprs

If you don't need 'sudo', then

    npm install -g watch-aprs

# Usage

## Command Line - Monitoring the On-Air APRS Traffic

    watch-aprs <host>:<port>

    e.g.

    watch-aprs raspberrypi:8001

'watch-aprs' isn't specific to the 'share-tnc' package.  It will work with any
KISS-over-TCP server (e.g. DireWolf).

# Contributing

To contribute, please fork https://github.com/trasukg/watch-aprs and then submit
pull requests, or open an issue.

See also https://github.com/trasukg/utils-for-aprs for the underlying components
used in this utility.

# License

This software is licensed under the Apache Software License 2.0

The phrase APRS is a registered trademark of Bob Bruninga WB4APR.

# Release Notes

1.0.1 - December 21, 2017 - First release.  Previously was a part of the
share-tnc package.  Releasing separately allows installation of watch-aprs
without the serialport package.
1.0.2 - December 8, 2019 - Update to latest utils-for-aprs.

repository: Trippnology/watch-aprs

repo_name: Trippnology/watch-aprs


text:
About

lit-transition is a directive for [lit-html](https://lit-html.polymer-project.org/)
that enables animated transitions between templates.
It is in parts inspired by the [transition system of vue.js](https://vuejs.org/v2/guide/transitions.html).

lit-transition is written in typescript, extremely tiny and tree-shakeable.
It mainly orchestrates state transitions when a lit-html template is updated.
By adding css classes or executing js-based animations and delaying the removal or insertion of new DOM, transitions can be played.

Currently we only support [css transitions](https://developer.mozilla.org/de/docs/Web/CSS/transition) [css animations](https://developer.mozilla.org/de/docs/Web/CSS/animation).
However, the plan is to eventually also transparently support [web animations](https://developer.mozilla.org/de/docs/Web/API/Web_Animations_API).

Check out the following example:

<script>
import {html} from 'lit-html'
import {asyncReplace} from 'lit-html/directives/async-replace.js';
import {transition, land} from 'lit-transition';

// generates a new date once a second
async function* count() {
  while (true) {
    // wrapping a template using transition directive will
    // automatically animate it on change
    yield transition(html`<div style="display: inline-block">
        ${new Date().toLocaleString()}
      </div>`, land);
    await new Promise(r => setTimeout(r,1000));
  }
}
// asyncReplace directive updates on as generator yields
export const template = html`lit! ${asyncReplace(count())}`;
</script>

Head over to the [Getting Started](getting-started) section to get set up.

repository: funkeeflow/lit-transition

gha_license_id: MIT

repo_name: funkeeflow/lit-transition


text:
### [CVE-2008-6849](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-6849)
![](https://img.shields.io/static/v1?label=Product&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

Unrestricted file upload vulnerability in index.php in phpGreetCards 3.7 allows remote attackers to execute arbitrary PHP code by uploading a file with an executable extension, then accessing it via a via a link that is listed by userfiles/number_shell.php.

### POC

#### Reference
- https://www.exploit-db.com/exploits/7561

#### Github
No PoCs found on GitHub currently.

repository: trickest/cve

branch_name: refs/heads/main

gha_language: HTML

repo_name: trickest/cve


text:
[![Gitpod](https://img.shields.io/badge/Gitpod-ready--to--code-blue?logo=gitpod)](https://gitpod.io/#https://github.com/linksplatform/Interfaces)

[![Codacy Badge](https://api.codacy.com/project/badge/Grade/93857535a2214ba9b512e1a88787d461)](https://app.codacy.com/gh/linksplatform/Interfaces?utm_source=github.com&utm_medium=referral&utm_content=linksplatform/Interfaces&utm_campaign=Badge_Grade_Settings)
[![CodeFactor](https://www.codefactor.io/repository/github/linksplatform/interfaces/badge)](https://www.codefactor.io/repository/github/linksplatform/interfaces)

| [![Actions Status](https://github.com/linksplatform/Interfaces/workflows/cpp/badge.svg)](https://github.com/linksplatform/Interfaces/actions?workflow=cpp) | [![NuGet Version and Downloads count](https://buildstats.info/nuget/Platform.Interfaces.TemplateLibrary)](https://www.nuget.org/packages/Platform.Interfaces.TemplateLibrary) [![ConanCenter package](https://repology.org/badge/version-for-repo/conancenter/platform.interfaces.svg)](https://conan.io/center/platform.interfaces) | __C++__  |
|-|-|-|
| [![Actions Status](https://github.com/linksplatform/Interfaces/workflows/csharp/badge.svg)](https://github.com/linksplatform/Interfaces/actions?workflow=csharp) | [![NuGet Version and Downloads count](https://buildstats.info/nuget/Platform.Interfaces)](https://www.nuget.org/packages/Platform.Interfaces) | C# |

# [Interfaces](https://github.com/linksplatform/Interfaces)

LinksPlatform's Platform.Interfaces Class Library

Contains common interfaces that did not fit in any major category.

Namespace: [Platform.Interfaces](https://linksplatform.github.io/Interfaces/csharp/api/Platform.Interfaces.html)

Forked from: [Konard/LinksPlatform/Platform/Platform.Helpers](https://github.com/Konard/LinksPlatform/tree/657ea248b32dc31d0793ae9a9e4989ec6ee61d5e/Platform/Platform.Helpers)

NuGet package: [Platform.Interfaces](https://www.nuget.org/packages/Platform.Interfaces)

## [Documentation](https://linksplatform.github.io/Interfaces)
*   Interface [IFactory\<TProduct\>](https://linksplatform.github.io/Interfaces/csharp/api/Platform.Interfaces.IFactory-1.html).

[PDF file](https://linksplatform.github.io/Interfaces/csharp/Platform.Interfaces.pdf) with code for e-readers.

## Dependent libraries
*   [Platform.Collections](https://github.com/linksplatform/Collections)
*   [Platform.Setters](https://github.com/linksplatform/Setters)
*   [Platform.Timestamps](https://github.com/linksplatform/Timestamps)

license: Unlicense

repository: linksplatform/Interfaces

gha_license_id: Unlicense

repo_name: linksplatform/Interfaces


text:
# Contributing Guidelines

- Try to keep eslint errors / warnings to a minimum
- Create a feature branch and PR into master
- Use [Prettier](https://prettier.io/) to format your code


text:
KEYSTONERC SELECTOR
---
This is a little utility to help openstack operators to manage their keystonerc
in a more safety way.
In particular this tool makes use of gpg to crypt/decrypt the secret credentials
containing sensitive informations.
It also allow operators to generate new keystonerc-encrypted credentials passing the
mandatory parameters needed to interact with the openstack client.

Installation
---
You can simply:

    $ git clone https://github.com/fmount/keystone-gpg-selector.git ~/clone/path

and install all the required dependencies:

    $ pip install -r requirements.txt

	{
		globals": {
			"gnupghome": "~/.gnupg",
			"gnupgbin": "/usr/bin/gpg",
			"pubring": "pubring.gpg",
			"secring": "secring.gpg",
			"keystonerchome": "~/.keystonerc_ring"
			}
	}

SOURCING A KEYSTONERC
----

	python keystonerc\_selector.py

REGISTER A NEW USER ON A SPECIFIC TENANT
----

	python keystonerc\_selector.py -u [user] -p [password] -t [aTenant] -e [API\_ENDPOINT] --persist

LICENSE
---
It is distruibuted according to the MIT LICENSE.

repository: fmount/keystone-gpg-selector

repo_name: fmount/keystone-gpg-selector


text:
# dc-vactrack

![image](https://user-images.githubusercontent.com/32506219/111910652-92d82900-8a62-11eb-983b-22cdbc581ddc.png)

dc-vactrack *will be* a **Discord** bot that tracks steam profiles for **VAC bans** and notifies a channel if a profile has been banned.

## Functions

### Notify TBD

The bot sends a message to a channel if a tracked profile has been banned

### Track

`.vac track [Steam_Account_link]` adds a steam account to the tracking list.

### List

`.vac list` gives you the names of profiles you added to the tracking list

## Installation

TBD

## Usage

TBD

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

## License
[MIT](https://choosealicense.com/licenses/mit/)

repository: domfz/dc-vactrack

repo_name: domfz/dc-vactrack


text:
### LPIS Use case: Crop-type classification (AUT)

- lpis_at_create.sql: table creation scripts
- lpis_at_sample.csv: LPIS data for sample region in Austria (year 2018), needs to be ingested into lpis_at table

Note: if you want to ingest different LPIS data for Austria (other region, other year) you can find them as Open Government Data [here](https://www.data.gv.at/katalog/dataset/e21a731f-9e08-4dd3-b9e5-cd460438a5d9)

repository: jonas-eberle/notebooks

repo_name: jonas-eberle/notebooks


text:
# E-com Backend
 ###### License: MIT
 ## Table of Contents
 - [Description](#description)
 - [Installation](#installation)
 - [Usage](#usage)
 - [Contribution](#contribution)
 - [Usage](#usage)
 - [Questions](#questions)
 - [Tests](#tests)
  ## Desctiption
  ### This is a simple backend for an e-commerce type online store. It allows the user to create new products, categories, and tags as well as update and delete any of those. It allows the user to access that data, which is stored inside a MySQL database. You can view a walkthrough video via this [link](https://youtu.be/Sj9XZki-K8A).
  ## Installation
  ### Clone the GitHub repository and run "npm i". Create the database using the Schema. Run "npm run seed" in the terminal and then start the server using "node server.js"
  ## Usage
  ### Use this starter code however you'd like to

  ## Contribution
  ### Contribute and change this code however you see fit
  ## Tests
  ### N/A
  ## Questions
  ### Please reach out to me with further quesions via my eamil<EMAIL_ADDRESS>  ### [My GitHub](https://github.com/Drake-G)

repository: Drake-G/e-com

repo_name: Drake-G/e-com


text:
authors:
- josephmedley
published_on: 2016-01-05
updated_on: 2016-01-05
order: 2
---

<p class="intro">
  Here are a few tips for making your notifications personal, timely, and relevant.
</p>

{% include shared/toc.liquid %}

## Make it personal and relevant

Look at the notifications on any of your devices. You're likely to find two types of messages: ones that tell you specific things and ones that are vague or opaque. For example, a social site might give you a notification like this:

![A notification that says nothing](images/better-notification.png){:width="380px"}

Notice that it tells you who sent it, even showing you the sender's picture, and gives you some idea what it's about.

This one on the other hand tells you nothing that would make you want to open the application.

![A notification that says nothing](images/bad-notification.png){:width="380px"}

## Make it available regardless of connectivity

Until recently only mobile apps could do this. With service workers you can store a notification until a user wants it. When the user clicks it, the status of the network is irrelevant.

## Don't advertise your native app

The point of service workers, the technology behind push notifications, is that you can avoid the time and expense of writing an application separate from your web site. A user who has both your service worker and your native app may get duplicate notifications unless write server-side code to prevent it. You can avoid the problem completely; don't encourge users to run both.

## Don't advertise

You'll have opportunities to monitize the user experience once they're in your app. Don't blow it by spamming your users when they're not. If you spam your users with notifications, they may stop allowing them altogether.

## Keep it short.

Notifications aren't emails. The intent of notifications is to tease users so they'll open your app. How do you do that? Make it personal. Make it timely. Make it relevant.

extension: markdown


text:
# Applied-AI-notes
This repository will contain notes and all the learning and daily updates for the progress of Applied Machine Learning course.

You may also fork this repository and use the resources in the repository for the learning process only.

Stay tuned and check daily for the notes and updates topic wise.

# NOTE: tensorflowdoesn’t work with python 3.7, please install python version 3.6 only.

The current anaconda installs with python 3.7 use this link if you have not already installed. The versions might differ but the product will be the same with some advanced features added to the repo. I suggest forking it as I will be updating and you'll also be constantly updated.

Windown 64 bit: https://repo.continuum.io/archive/Anaconda3-5.2.0-Windows-x86_64.exe
Windown 32 bit: https://repo.continuum.io/archive/Anaconda3-5.2.0-Windows-x86.exe
Mac : https://repo.continuum.io/archive/Anaconda3-5.2.0-MacOSX-x86_64.sh
Linux 64 bit: https://repo.continuum.io/archive/Anaconda3-5.2.0-Linux-x86_64.sh
Linux 32 bit: https://repo.continuum.io/archive/Anaconda3-5.2.0-Linux-x86.sh

repository: amitravikumar/Applied-AI-notes

repo_name: amitravikumar/Applied-AI-notes


text:
---
layout: shared/root
title: "Building for Billions"
authors:
  - samdutton
description: "Building Web Apps for the Next Billion Users"
translation_priority: 0
---

Building Web Apps for the Next Billion Users

The next billion people coming online will be diverse in every respect: their physical location, cultural experience, computer expertise, connectivity access, and the kinds of devices they use.

They will virtually all be mobile users.

This presents unique challenges for web developers who must abandon the limited mobile first approach in favor of a comprehensive mobile only strategy.

You can address these challenges by focusing on specific areas.

{% include page-structure/site-promo-banner.liquid %}

Design for seamless connectivity

Low bandwidth and intermittent connectivity are the norm for many people accessing the web. Most people online still have 2G connections or "3G" that downgrades to 2G. Even by 2020, more than 10% of users will still be on 2G. Many smartphones are used offline, and users regularly turn on airplane mode to avoid data consumption.

Test with emulated low bandwidth and high latency

Handle unreliable connectivity and "lie-fi"

Design for offline

Reduce the number of resource requests

Make installs and updates as small and fast as possible

Conserve data usage

High data cost is often a greater barrier to access than poor connectivity. Mobile users are cost-conscious; even "unlimited" plans can become expensive when roaming or if unexpected fees are applied. Many mobile users are extremely cost conscious, with good reason: for example, a 500MB data plan in India costs the same as 17 hours of minimum wage work.

Understand the cost of loading page and app components

Reduce the amount of data required for interaction

Streamline navigation: help users get to what they want

Prioritize content display

Reduce battery consumption

Many people, even in urban areas, don't have access to a reliable and affordable power supply. This makes power conservation a critical factor in all app and content design.

Avoid repaints, reflows, and required reorientations

Avoid expensive UI animations

Avoid radio usage: eliminate unnecessary downloads

Reduce user actions required to access content

Avoid expensive animations

Optimize for device capability

Low spec is the norm. Globally, most new internet users have low-cost devices with basic hardware: single-core processors, 4" screens, limited memory, and limited storage.

Cater for a range of viewports and devices

Design for limited memory and CPU: reduce and optimize

Build multi-device content

Large-layout, graphics-heavy content frustrates users and discourages them from using your app or site. Content that is too wide or too tall is overlooked by some users and deliberately avoided by others — and excess content adds page weight and data cost.

Design content to work well across different viewport sizes

Eliminate redundant content

Write for mobile

Consider AMP HTML

Transactions & monetization: think global

Payment systems are inaccessible for many people on the web. Many users globally don't have bank accounts and don't use credit cards —  including 8% of US households. Many payment systems don't work well on small viewports or with unreliable connectivity.

Streamline transactions

Streamline forms

Design orientation-friendly layouts for small screens

Plan for localization

Localization can help you access new markets. Many websites are only published in English, but English is not the first language of most people online. Only 5.52% of the world's population are native English speakers and US or European cultural conventions may not be familiar or intuitive. Instructions or prompts that are succinct and compact in English may be verbose and obtrusive in other languages.

Architect your site to enable localization


text:
# dynatrace-config
Currently it's just an idea and a place to chat it out.

## Idea

Have a small program which utilizes yaml and/or json to talk to the dynatrace api to configure the settings (environment, configuration and maybe even cluster) from a repository through CI/CD. Why would just the developers have fun and not us infra-guys too?

### Questions
Golang or Python

### What there have to be

#### Ansible Module

Possible with go and python. No shortcomings in any way.

#### k8s pod / controller

- Pod could run constantly but also short-lived
- it would fetch multiple/single file(s) from defined sources (git, https) and apply the configs to target (the gitops way)
- go would fit better as theres a smaller image

...

## Experiments

### Simple go program which reads configuration json and calls the dynatrace api

#### Usage:
1. create a dynatrace trial account if you don't have one
2. create a dynatrace API-Token with Write Configuration in the dynatrace web console "Settings -> Integration -> Dynatrace API"
3. use the experiments/config/anomaly-detection-service.json or create a new file according to the https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/configuration-api/ . the configuration file must contain the API uri and the http method like in https://github.com/rockaut/dynatrace-config/blob/f26bf58b2d61a00b08f24a29ceb255d012954575/experiments/config/anomaly-detection-service.json#L2-L3 . The json body for the dynatrace API is in the payload key, like in https://github.com/rockaut/dynatrace-config/blob/f26bf58b2d61a00b08f24a29ceb255d012954575/experiments/config/anomaly-detection-service.json#L4
4. then execute (adapt to your use case)
```
export DYNATRACE_API_URL="https://yourenvironment.live.dynatrace.com/api/config"
export DYNATRACE_API_TOKEN="xxxxxx"
```

there are different command parameters available:

get current state of the configuration object:
```
go run experiments/dynatrace-config.go get experiments/config/anomaly-detection-service.json
```

show diff between current state and desired state of the configuration object:
```
go run experiments/dynatrace-config.go diff experiments/config/anomaly-detection-service.json
```

validate desired state:
```
go run experiments/dynatrace-config.go validate experiments/config/anomaly-detection-service.json
```

apply desired state:
```
go run experiments/dynatrace-config.go apply experiments/config/anomaly-detection-service.json
```

#### Findings:
- from my opinion it doesn't make sense to build a new API or configuration layer. In the configuration json files there needs to be the same payload as the dynatrace API server expects. Otherwise we always need to adapt our tool when the dynatrace API changes or will be expanded
- setting the dynatrace configuration is not always a PUT, sometimes also a POST. so we probably need to specify the http method in the configuration json file like in https://github.com/rockaut/dynatrace-config/blob/f26bf58b2d61a00b08f24a29ceb255d012954575/experiments/config/anomaly-detection-service.json#L3
- http returncode is depending on the api, so we also need to specify the expected success return code in the configuration json file, like in https://github.com/rockaut/dynatrace-config/blob/f26bf58b2d61a00b08f24a29ceb255d012954575/experiments/config/anomaly-detection-service.json#L36
- every (?) API has a 'validator' API which can validate the desired configuration. Not sure if that is really true for every API.

repository: rockaut/dynatrace-config

gha_language: Go

repo_name: rockaut/dynatrace-config


text:
# Napal

A faster Performance Analysis of Logs

This is a tool that analyses .csv files and generates plots. The current use is for analyzing performance counter reports from Windows, but it's generic enough for other tasks.

![](powershell-usage.gif)
![](html-viewing.gif)

## Examples:

`.\napal.exe testfile.csv`

- This uses the default metrics, plot settings and plot colors, located in the config/ directory.

`.\napal.exe -v -wm specific-metrics.txt testfile.csv`

 - This will print debug information, use the metrics located in the specific-metrics.txt file and use the plot settings and plot colors located in the config/ directory.

`.\napal.exe testfile1.csv testfile2.csv`

This will use the default settings and create plots with two lines. This allows the comparison of different executions of the same thing.

## Parameters:

**[] are optional arguments
() Represents options
<> are obligatory**

**\<csv files>**
- The list of files that will be parsed and used to create plots.
- This is mandatory to be the last argument.

**[-t or -targetDir]**
- The directory where the results will be saved.
- Default is `results/{year}-{month}-{day}_{hour}-{minute}-{second}`
	- Example: results/2021-05-18_10-10-10
	- Do note that the results/dir will be placed in the working directory.

**[-wm or -wantedMetrics]**
- The path for the file that contains which metrics are desired to be analyzed.
- Default is `config/DefaultMetrics.txt`. [(link)](<config/DefaultMetrics.txt>)

**[-ps or -plotSettings]**
- The path for the file that contains the settings to be used when plotting.
- Default is `config/DefaultPlotSettings.txt`. [(link)](<config/DefaultPlotSettings.txt>)

**[-c or -colorsFile]**
- The path for the file that contains a list of the colors to be used in the graphs (by order).
- Default is `config/DefaultPlotLineColors.txt`. [(link)](<config/DefaultPlotLineColors.txt>)

**[-w or -widthPerPoint]**
- The width of each point in the plots. (x axis).
- Default is 1.

**[-s or -skipParse]**
- Whether the .csv files should be parsed or not. It is required for them to be parsed at least once, so that they generate the .altered.csv file.
- Default is false.

**[-tf or -timeFormat]**
- The format for the date column. How to write the format: https://docs.rs/chrono/0.4.7/chrono/format/strftime/index.html
- Default is `%m/%d/%Y %H:%M:%S.%f`
	- Example date: `05/02/2020 15:30:10.012`.
	- For more details on this default, look here [in the code](<src/parameters.rs>).

**[-xaxis (seconds|minutes)]**
- Whether the X axis of the plots should be in seconds or minutes.
- Default is `seconds`.
- Example:
	- `.\napal.exe -xaxis seconds testfile1.csv`
	- `.\napal.exe -xaxis minutes testfile1.csv`

**[-v or -verbose]**
- Whether to display debug information.
- Default is to not display.

**[-h or -help]**
- Displays this information.

repository: OutSystems/Napal

repo_name: OutSystems/Napal


text:
# docker compose pull

<!---MARKER_GEN_START-->
Pull service images

### Options

| Name                     | Type | Default | Description                                             |
|:-------------------------|:-----|:--------|:--------------------------------------------------------|
| `--dry-run`              |      |         | Execute command in dry run mode                         |
| `--ignore-buildable`     |      |         | Ignore images that can be built.                        |
| `--ignore-pull-failures` |      |         | Pull what it can and ignores images with pull failures. |
| `--include-deps`         |      |         | Also pull services declared as dependencies.            |
| `-q`, `--quiet`          |      |         | Pull without printing progress information.             |

<!---MARKER_GEN_END-->

## Description

Pulls an image associated with a service defined in a `compose.yaml` file, but does not start containers based on
those images.

## Examples

suppose you have this `compose.yaml`:

```yaml
services:
  db:
    image: postgres
  web:
    build: .
    command: bundle exec rails s -p 3000 -b '<IP_ADDRESS>'
    volumes:
      - .:/myapp
    ports:
      - "3000:3000"
    depends_on:
      - db
```

If you run `docker compose pull ServiceName` in the same directory as the `compose.yaml` file that defines the service,
Docker pulls the associated image.  If pull fails, it will let
user know this service image MUST be built. You can skip this by setting `--ignore-buildable` flag

repository: docker/compose

repo_name: docker/compose


text:
# gameoflife
CS6023(GPU Programming) Project to simulate and render Conway's Game of Life in Cuda C++ and OpenGL

To compile the project for the GUI visualization, run
`make display`

To begin the display after that, do
`./gui`

The display supports resizing, and has the option to toggle between CPU and GPU computation(using the key `T`). You can pause the display using the `Space` key.

The rendering is done using a 2D texture with the help of the GLUT Library. FPS is also displayed on the screen during the running of the program.


text:
#### Classifiers
##### New: Cofense Triage - Classifier
- Classifies Cofense Triage Report Incidents. (Available from Cortex XSOAR 5.5.0).

#### Incident Fields
- **Cofense Triage Report Categorization Tags**
- **Cofense Triage Report SHA256**
- **Cofense Triage Report Created At**
- **Cofense Triage Report Subject**
- **Cofense Triage Report Updated At**
- **Cofense Triage Report Reported At**
- **Cofense Triage Report Location**
- **Cofense Triage Report MD5**
- **Cofense Triage Report ID**
- **Cofense Triage Report Risk Score**
- **Cofense Triage Report From Address**
- **Cofense Triage Report Tags**
- **Cofense Triage Report Received At**
- **Cofense Triage Report Processed At**
- **Cofense Triage Report Category ID**
- **Cofense Triage Report Match Priority**
- **Cofense Triage Report Attachment Information**

#### Incident Types
- **Cofense Triage Report**

#### Integrations
##### Cofense Triage v2
- Updated docker image.
##### New: Cofense Triage v3
- The integration uses the Cofense Triage v2 API that allows users to ingest phishing reports as incident alerts and execute commands such as threat indicators, reporters, categorize reports, and more. (Available from Cortex XSOAR 6.0.0).

#### Layouts
- **Cofense Triage Report**

#### Mappers
##### New: Cofense Triage Report - Incoming Mapper
- Incoming mapper for Cofense Triage Report (Available from Cortex XSOAR 0.0.0).

#### Playbooks
##### New: Report Categorization - Cofense Triage v3
- Report Categorization playbook investigates reports that are unprocessed or uncategorized on Cofense Triage as incident alerts in XSOAR and categorizes them based on the severity of the incident. (Available from Cortex XSOAR 6.0.0).
##### New: Cluster Report Categorization - Cofense Triage v3
- Cluster Report Categorization playbook is used to retrieve the reports of specific clusters and perform the categorization of reports. (Available from Cortex XSOAR 6.0.0).
##### New: Send Indicators - Cofense Triage v3
- Send Indicators playbook is used to create or update threat indicators in Cofense Triage as a result of the analysis. (Available from Cortex XSOAR 6.0.0).

#### Scripts
##### New: CofenseTriageReportDownload
- Download all reports associated with the email address. (Available from Cortex XSOAR 6.0.0).
##### New: CofenseTriageThreatEnrichment
- Enhancement automation for type indicator, to enrich the value from Cofense Triage. (Available from Cortex XSOAR 6.0.0).

repository: demisto/content

gha_language: Python

repo_name: demisto/content


text:
CS-With-Android Project Touring Musician
============================

**This repository contains code for module Touring Musician Game of Google's Computer Science with Android.**
[*Touring Musician CSwithAndroid*](https://cswithandroid.withgoogle.com/unit?unit=14&lesson=16)

An app that will allow users to add gig locations to a map and use this to find paths through various gigs.
------------------------------------------------------------
* InsertBeginning
* InsertNearest
* InsertSmallest

repository: Shalvi-Saxena/Touring-Musician

repo_name: Shalvi-Saxena/Touring-Musician


text:
# ELK server (Elasticsearch, Logstash, & Kibana)
plus a web server for testing

[official repo](https://github.com/geerlingguy/ansible-vagrant-examples/tree/master/elk)

from Jeff Geerling's [Ansible for DevOps](http://ansiblefordevops.com/), with some additional monkeying about by myself.

repository: dheles/ansible-library

repo_name: dheles/ansible-library


text:
# Write fluent policies in Laravel

[![Latest Version on Packagist](https://img.shields.io/packagist/v/soyhuce/laravel-fluent-policy.svg?style=flat-square)](https://packagist.org/packages/soyhuce/laravel-fluent-policy)
[![GitHub Tests Action Status](https://img.shields.io/github/workflow/status/soyhuce/laravel-fluent-policy/run-tests?label=tests)](https://github.com/soyhuce/laravel-fluent-policy/actions?query=workflow%3Arun-tests+branch%3Amain)
[![GitHub Code Style Action Status](https://img.shields.io/github/workflow/status/soyhuce/laravel-fluent-policy/Check%20&%20fix%20styling?label=code%20style)](https://github.com/soyhuce/laravel-fluent-policy/actions?query=workflow%3A"Check+%26+fix+styling"+branch%3Amain)
[![GitHub PHPStan Action Status](https://img.shields.io/github/workflow/status/soyhuce/laravel-fluent-policy/PHPStan?label=phpstan)](https://github.com/soyhuce/laravel-fluent-policy/actions?query=workflow%3APHPStan+branch%3Amain)
[![Total Downloads](https://img.shields.io/packagist/dt/soyhuce/laravel-fluent-policy.svg?style=flat-square)](https://packagist.org/packages/soyhuce/laravel-fluent-policy)

Write your policies fluently in Laravel.

```php
<?php

class PostPolicy extends FluentPolicy
{
    public function delete(User $user, Post $post): Response
    {
        return $this->denyWhen($post->user_id !== $user->id)
            ->denyWhen($post->published_at !== null)
            ->allow();
    }
}
```

## Installation

You can install the package via composer:

```bash
composer require soyhuce/laravel-fluent-policy
```

## Usage

The goal of this package is to write your policies more easily in a clean syntax.

For exemple, the following policy:

```php
<?php
use Illuminate\Auth\Access\HandlesAuthorization;

class PostPolicy
{
    use HandlesAuthorization;

    public function delete(User $user, Post $post): bool
    {
        if ($post->user_id !== $user->id) {
            return false;
        }

        if ($post->published_at !== null) {
            return false;
        }

        return true;
    }
}
```

can be re-written as:

```php
<?php
use Illuminate\Auth\Access\Response;
use Soyhuce\FluentPolicy\FluentPolicy;

class PostPolicy extends FluentPolicy
{
    public function delete(User $user, Post $post): Response
    {
         return $this->denyWhen($post->user_id !== $user->id)
            ->denyWhen($post->published_at !== null)
            ->allow();
    }
}
```

You can customise the response if needed :

```php
return $this->denyWhen($post->published_at !== null, 'You cannot delete a published post')
    ->allow();
```

You can also call another policy or gate this way :

```php
return $this->authorize($user, 'update', $post)
    ->allowWhen($post->published_at === null)
    ->deny();
```

### Custom Http status

You can deny the policy returning a custom http status code :

```php
return $this->denyWithStatusWhen($post->user_id !== $user->id, 404)
        ->allow();
// or $this->>allowWhen(...)->denyWithStatus(404);
```

In the case of `404` status code, you can use the shortcut

```php
return $this->denyAsNotFoundWhen($post->user_id !== $user->id)
        ->allow();
// or $this->>allowWhen(...)->denyAsNotFound();
```

### Lazy evaluation

The different branches `allowWhen` and `denyWhen` are evaluated lazily which mean that the following code is completely
correct :

```php
<?php
use Illuminate\Auth\Access\Response;
use Soyhuce\FluentPolicy\FluentPolicy;

class PostPolicy extends FluentPolicy
{
    public function delete(User $user, Post $post): Response
    {
         // Here, $post->published_at is Carbon or null

         return $this->denyWhen($post->user_id !== $user->id)
            ->allowWhen($post->published_at === null) // 1
            ->allowWhen($post->published_at->isFuture()) // 2
            ->deny();
    }
}
```

`2` will only be called if previous branches are all false. We are sure that here `$post->published_at` is not null
thanks to `1`.

## PHPStan

When running PHPStan on

```php
public function delete(User $user, Post $post): Response
{
     return $this->denyWhen($post->user_id !== $user->id)
        ->allowWhen($post->published_at === null) // 1
        ->allowWhen($post->published_at->isFuture()) // 2
        ->deny();
}
```

an error is raised on `2` (`Cannot call method `isFuture` on Carbon|null`).

An extension is available to fix this issue and should be included in your `phpstan.neon` file.

```neon
includes:
    - vendor/bin/soyhuce/laravel-fluent-policies/extension.neon
```

Unfortunately, due to a PHPStan limitation, you still have to rewrite your policy a little bit :

```php
public function delete(User $user, Post $post): Response
{
    $this->denyWhen($post->user_id !== $user->id)
        ->allowWhen($post->published_at === null);
    // From here, PHPStan understands that $post->published_at is not null

    return $this->allowWhen($post->published_at->isFuture())
        ->deny();
}
```

## Testing

```bash
composer test
```

## Changelog

Please see [CHANGELOG](CHANGELOG.md) for more information on what has changed recently.

## Contributing

Please see [CONTRIBUTING](.github/CONTRIBUTING.md) for details.

## Security Vulnerabilities

Please review [our security policy](../../security/policy) on how to report security vulnerabilities.

## Credits

- [Bastien Philippe](https://github.com/bastien-phi)
- [All Contributors](../../contributors)

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.

repository: Soyhuce/laravel-fluent-policy

gha_language: PHP

repo_name: Soyhuce/laravel-fluent-policy


text:
# ts-avl-tree

[![Build Status](https://travis-ci.org/gwtw/ts-avl-tree.svg?branch=master)](http://travis-ci.org/gwtw/ts-avl-tree)
[![Coverage Status](https://coveralls.io/repos/github/gwtw/ts-avl-tree/badge.svg?branch=master)](https://coveralls.io/github/gwtw/ts-avl-tree?branch=master)

A TypeScript implementation of the [AVL tree](http://www.growingwiththeweb.com/data-structures/avl-tree/overview/) data structure.

Note that the primary purpose of this library is education but it should work in a production environment as well. It's certainly not as performant as it could be as it optimises for readability, abstraction and safety over raw performance.

![](http://www.growingwiththeweb.com/images/data-structures/avl-tree/avl-tree.svg)

## Features

- 100% test coverage
- Supports all common tree operations
- Store keys with optional associated values
- Optional custom compare function that can utilize both key and value to give full control over the order of the data

## Install

```bash
npm install --save @tyriar/avl-tree
```

## Usage

See the [typings file](./typings/avl-tree.d.ts) for the full API.

```typescript
// Import npm module
import { AvlTree } from '@tyriar/avl-tree';

// Construct AvlTree
const tree = new AvlTree<number, number>();

// Insert keys
tree.insert(1);
tree.insert(2);
tree.insert(3);
tree.insert(4);
tree.insert(5);
console.log('size: ' + tree.size);
console.log('contains 2: ' + tree.contains(2));
console.log('contains 7: ' + tree.contains(7));
// > size: 5
// > contains 2: true
// > contains 7: false

// Delete a key
tree.delete(2);
console.log('size: ' + tree.size);
console.log('contains 2: ' + tree.contains(2));
// > size: 4
// > contains 2: false

// Construct custom compare AvlTree
const tree2 = new AvlTree<string, string>(function (a, b) {
  return a.localeCompare(b);
});
tree2.insert('a');
tree2.insert('A');
tree2.insert('b');
tree2.insert('B');

// Delete the minimum key
const minKey = tree2.findMinimum();
tree2.delete(minKey);
console.log('minKey: ' + minKey);
console.log('new minKey: ' + tree2.findMinimum());
// > min key: 'a'
// > new min key: 'A'
```

## Operation time complexity

| Operation   | Complexity |
| ----------- | ---------- |
| contains    | O(log n)   |
| delete      | O(log n)   |
| findMaximum | O(log n)   |
| findMinimum | O(log n)   |
| get         | O(log n)   |
| insert      | O(log n)   |
| isEmpty     | Θ(1)       |
| size        | Θ(1)       |

repository: ahermida/ts-avl-tree

repo_name: ahermida/ts-avl-tree


text:
# **Counter**

### **Description**
Its a Web Application which is an Interactive Counter made with vanilla JavaScript

### **Technologies**
This Project is created with:
 - Javascript
 - HTML5
 - CSS3

### Can Find Working Project on this URL:
https://counterbydevangjoshi.netlify.app

repository: devang-joshi-dj/Counter

repo_name: devang-joshi-dj/Counter


text:
# Salmon Cookies project

## Salmon Cookies it's a website for Selling fish and displaying opening and closing dates for each of the branches around the world
## As a user,"I want a webpage that displays individual store data for my Salmon Cookie Shops, so that I can be informed about how to run my business"

 ### abdallah alabed

 ### links

 * 3wschools

###   what did you learn
  * layout
  * oop
  * event
  * injection the html with javaScrpit

repository: abdallahAlabed/cookie-stand

gha_language: JavaScript

repo_name: abdallahAlabed/cookie-stand


text:
---
layout: page
subheadline: "Where Did the Goddess Go?"
title: "Nearly Sacred Episode One: Have You Seen the Goddess?"
teaser: "The Bible is chalk full of references to the Goddess, but nobody can seem to find her..."
header:
    image_fullwidth: "oldradio.jpg"
    caption: Image by Daniel Von Appen
    caption_url: "https://unsplash.com/"
image:
    thumb:  standradio.png

categories:
    - podcasts

comments: false
show_meta: false
mediaplayer: true
---

In this, our seminal episode, we discuss the Hebrew Goddess and where she went, and why she seems to be missing. We cover the relevant news of the time period and
discuss various scriptural matters pertaining to things from self-government to the Kabbalah implications of certain letters of the Hebrew alphabet. We even delve into
some politically "sensitive" issues. You do not want to miss how this all started!

<audio src="https://ia601501.us.archive.org/16/items/NearlySacred/nearlysacredepisode1.mp3" type="audio/mp3" controls="controls"></audio>


text:
# Swiping your way through Appium
This repo will hold the example code and puzzle assignment for the "Swiping your way through Appium"-talk during
Appium Conference 2021.

## Table of contents
- [Introduction](#introduction)
- [Prerequisites](#prerequisites)
  - [Installing NodeJS](#installing-nodejs)
    - [Windows](#windows)
      - [Mac/Linux](#maclinux)
  - [Setting up an Android Emulator or an iOS Simulator](#setting-up-an-android-emulator-or-an-ios-simulator)
  - [Installing Appium](#installing-appium)
- [Test your setup](#test-your-setup)
  - [Testing your Android setup](#testing-your-android-setup)
  - [Testing your iOS setup](#testing-your-ios-setup)
- [Assignment](#assignment)

## Introduction:
We will be using:
- a local Android emulator, because this can be used on all platforms (Windows, Mac and Linux).
- a local iuOS simulator, if you have a Mac
- WebdriverIO as an automation tool

## Prerequisites
- A Windows, Mac or Linux operating system
- Administrator and/or installation rights on your machine
- Installed NodeJS, this needs to be an even version, so 12 or 14 (No odd versions like 11, 13, 15 which are not stable
  versions)
- You have downloaded and configured an Android Emulator and/or an iOS Simulator
- Have the latest version of Appium installed on your machine (1.21.0 or higher)
- Some basic JavaScript knowledge

How to set up NodeJS, configure an Android Emulator/iOS Simulator and Appium are explained below.

### Installing NodeJS
If you already have NodeJS installed on your machine then you may skip this step.

There are several ways to install NodeJS, this can be done by:
- downloading it from the [NodeJS](https://nodejs.org/en/download/) website and selecting your environment,
- or by using Node Version Manager.

My advice is to use Node Version Manager because this will give you the ability to easily switch between NodeJS versions
in the future.

> **Note:**
> Make sure that if you are downloading NodeJS that you are using even versions with a minimum of NodeJS 12. The odd
> versions (11, 13, 15) are not the stable versions to use. For more information about NodeJS checkout this
> [MeetUp recording of MoT Athens](https://youtu.be/AO49tZYoZ_8?t=4600).

#### Windows:
Follow the instructions for Windows [here](https://github.com/coreybutler/nvm-windows).

#### Mac/Linux:
Follow the instructions [here](https://github.com/nvm-sh/nvm).

### Setting up an Android Emulator or an iOS Simulator
> You can skip this if you’ve already have an emulator/simulator set up.

Android and iOS both have their own prerequisites. Please follow the installation instructions that can be found
[here](https://youtu.be/BL3ruGJmwwk) to prepare your local machine. This will help you configure your Android Emulator
or iOS simulator.

If you configure your Android emulator, then make sure that you are using Android 10.

> NOTE: Make sure that you alter the name of the Android Emulator in the WebdriverIO config files to make sure that
> everything will work, see [here](./test/configs/wdio.android.local.emu.conf.ts) and
> [here](./test/configs/wdio.android.ios.local.conf.ts)

### Installing Appium
> If you already have Appium installed on your machine then you may skip this step.

You can follow the instructions, to install Appium on your local machine, by watching
[this](https://youtu.be/AQD1bDX1K-k) video. You don’t need to watch the complete video, the installation part is
mentioned at the beginning and stops at 4:11 min.

As mentioned in the video, make sure you use [Appium Doctor](https://github.com/appium/appium-doctor) to verify if
everything works as expected.

## Test your setup
To make sure everything is working you can execute the following steps:

- Clone the project to your local machine. Open a terminal, go to a folder (or create it) to where you want to store
  this project. Then copy paste the following command in that terminal

        git clone https://github.com/wswebcreation/swiping-your-way-through-appium.git

- then go into the directory with the following command

        cd swiping-your-way-through-appium

- when you are in the `swiping-your-way-through-appium` folder you can install all dependencies with the following command

        npm install

### Testing your Android setup
Make sure you have opened the Android emulator that you configured. Verify that the name of the emulator is the same
as the name in [this](./test/configs/wdio.android.local.emu.conf.ts) or
[this](./test/configs/wdio.android.ios.local.conf.ts)-file. If not, then change the `deviceName` to the name of your
emulator.

You can now execute the following command in your terminal

    npm run npm run examples.android

This will execute a file with skipped tests on your Android emulator and should produce the following logs

```log
> npm run examples.android

><EMAIL_ADDRESS>examples.android
> npx wdio test/configs/wdio.android.local.emu.conf.ts

Execution of 1 workers started at 2021-09-15T10:46:37.918Z

[0-0] RUNNING in Android - /test/specs/gestures.spec.ts
[0-0] PASSED in Android - /test/specs/gestures.spec.ts

 "spec" Reporter:
------------------------------------------------------------------
[emulator-5554 Android 10 #0-0] Running: emulator-5554 on Android 10 executing /Users/wimselles/Sauce/Git/appium-conf-2021/swiping-your-way-through-appium/apps/Android-NativeDemoApp-0.4.1.apk
[emulator-5554 Android 10 #0-0] Session ID: 07df76ba-ac4a-471b-9e74-4767c7507181
[emulator-5554 Android 10 #0-0]
[emulator-5554 Android 10 #0-0] » /test/specs/gestures.spec.ts
[emulator-5554 Android 10 #0-0] Appium Gestures
[emulator-5554 Android 10 #0-0]    - should be able to scroll to the bottom of the page
[emulator-5554 Android 10 #0-0]    - should be able to zoom the logo
[emulator-5554 Android 10 #0-0]    - should be able to scroll the "easy" way
[emulator-5554 Android 10 #0-0]    - should be able to zoom the logo the "easy" way
[emulator-5554 Android 10 #0-0]
[emulator-5554 Android 10 #0-0] 4 skipped (357ms)

Spec Files:      1 passed, 1 total (100% completed) in 00:00:09
```

### Testing your iOS setup
> If you have a Mac you can also check this.

Make sure you have opened the iOS simulator that you configured. Verify that the name of the simulator is the same
as the name in [this](./test/configs/wdio.ios.local.sim.conf.ts) or
[this](./test/configs/wdio.android.ios.local.conf.ts)-file. If not, then change the `deviceName` to the name of your
simulator.

You can now execute the following command in your terminal

    npm run examples.ios

This will execute a file with skipped tests on your iOS simulator and should produce the following logs

```log
> npm run examples.ios

><EMAIL_ADDRESS>examples.ios
> npx wdio test/configs/wdio.ios.local.sim.conf.ts

Execution of 1 workers started at 2021-09-15T11:23:15.861Z

[0-0] RUNNING in iOS - /test/specs/gestures.spec.ts
[0-0] PASSED in iOS - /test/specs/gestures.spec.ts

 "spec" Reporter:
------------------------------------------------------------------
[iPhone 12 iOS 14.5 #0-0] Running: iPhone 12 on iOS 14.5 executing /Users/wimselles/Sauce/Git/appium-conf-2021/swiping-your-way-through-appium/apps/iOS-Simulator-NativeDemoApp-0.4.1.app.zip
[iPhone 12 iOS 14.5 #0-0] Session ID: 38e469da-01aa-4417-b3b9-e390402bf844
[iPhone 12 iOS 14.5 #0-0]
[iPhone 12 iOS 14.5 #0-0] » /test/specs/gestures.spec.ts
[iPhone 12 iOS 14.5 #0-0] Appium Gestures
[iPhone 12 iOS 14.5 #0-0]    - should be able to scroll to the bottom of the page
[iPhone 12 iOS 14.5 #0-0]    - should be able to zoom the logo
[iPhone 12 iOS 14.5 #0-0]    - should be able to scroll the "easy" way
[iPhone 12 iOS 14.5 #0-0]    - should be able to zoom the logo the "easy" way
[iPhone 12 iOS 14.5 #0-0]
[iPhone 12 iOS 14.5 #0-0] 4 skipped (1s)

Spec Files:      1 passed, 1 total (100% completed) in 00:00:08
```

## Assignment
The assignment can be found [here](./test/specs/drag.and.drop.assignment.spec.ts).

> **NOTE:** Yes you are able to cheat, but I leave it up to you on how you want to learn

Open the file in your editor and follow the instructions. If you want to run the test then open a terminal and execute
the following script(s)

    # Android:
      npm run assignment.android
    # iOS (if you have a Mac):
      npm run assignment.ios

if you want to run the answer then please check the steps in [this](./test/specs/drag.and.drop.answer.spec.ts)-file and
execute the following script(s) in the terminal

    # Android:
      npm run answer.android
    # iOS (if you have a Mac):
      npm run answer.ios

https://user-images.githubusercontent.com/11979740/133436111-5237696a-1d91-4f63-a5d4-5a15cc49f3f3.mp4


text:
# Pipeline Firebase Hosting

This action is built with a continuous deployment approach, allowing to deploy a website on firebase hosting.

## Sample implementation

To configure in your repository this action, it is necessary to have a PTA and use actions/checkout@v2 action, the following way shows an example:

```sh
- name: Checkout danielmillan/pipelines-firebase-hosting
        uses: actions/checkout@v2
        with:
          repository: danielmillan/pipelines-firebase-hosting
          ref: '1.0.7' //Latest stable version
          token: ${{ secrets.CA_GITHUB_TOKEN }}
          persist-credentials: false
          path: ./.github/actions/pipelines-firebase-hosting
```

> Note: the variable `CA_GITHUB_TOKEN`, it should contain the respective token from your repository secrets, for more information visit: https://docs.github.com/en/actions/reference/authentication-in-a-workflow

## Parameters

Please note the following parameters to configure the action:

```sh
  firebase-token:
    description: Token generated to authenticate in firebase
    required: true
  resources-name:
    description: Name of the folder containing the resources to be deployed
    required: true
  project-name:
    description: Firebase project name
    required: true
  target-name:
    description: Target name if you need to deploy to a specific instance
    required: false
```

## Job

```sh
- name: Deploy site
        uses: ./.github/actions/pipelines-firebase-hosting
        with:
          firebase-token: ${{ secrets.FIREBASE_TOKEN }}
          resources-name: dist
          project-name: my-website
          target-name: target-site // only is neccessary
```

> Note: For this configuration you will need to provide a token `FIREBASE_TOKEN` which you can obtain by executing the line firebase login:ci and add it as a secret in your repository. For more information about authentication with the firebase CLI, see: https://firebase.google.com/docs/cli

## License

MIT
**Free Software, Hell Yeah!**

repository: danielmillan/pipelines-firebase-hosting

repo_name: danielmillan/pipelines-firebase-hosting


text:
[@nori-dot-com/project](../README.md) / [v3-specification](../modules/v3_specification.md) / HistoricCRPLandManagement

# Interface: HistoricCRPLandManagement

[v3-specification](../modules/v3_specification.md).HistoricCRPLandManagement

Details surrounding how the field was managed before year 2000

Note that the state the field exists within restricts the allowed values per object property. To find applicable values per location, see [here](https://docs.google.com/spreadsheets/d/e/2PACX-1vQQnIlyxCENwJvw5Luyg2Ikbn_X0FvMTNr2J6n5Y2xwcR6oi4OA2jNW-B2DrslTKtrmQxg03byZ_aRV/pubhtml)

**`Example`**

```js
{
 // HistoricCRPLandManagement:
 "crp": "yes",
 "crpType": "100% grass",
 "crpStartYear": 1980,
 "crpEndYear": 2000,
 "preCRPManagement": "irrigated: annual crops in rotation",
 "preCRPTillage": "intensive tillage",
 "postCRPManagement": "livestock grazing",
 "postCRPTillage": "intensive tillage",
 // HistoricLandManagement:
 "preYear1980": "irrigation"
}
```

## Hierarchy

- [`HistoricLandManagement`](v3_specification.HistoricLandManagement.md)

  ↳ **`HistoricCRPLandManagement`**

## Table of contents

### Properties

- [crp](v3_specification.HistoricCRPLandManagement.md#crp)
- [crpEndYear](v3_specification.HistoricCRPLandManagement.md#crpendyear)
- [crpStartYear](v3_specification.HistoricCRPLandManagement.md#crpstartyear)
- [crpType](v3_specification.HistoricCRPLandManagement.md#crptype)
- [postCRPManagement](v3_specification.HistoricCRPLandManagement.md#postcrpmanagement)
- [postCRPTillage](v3_specification.HistoricCRPLandManagement.md#postcrptillage)
- [preCRPManagement](v3_specification.HistoricCRPLandManagement.md#precrpmanagement)
- [preCRPTillage](v3_specification.HistoricCRPLandManagement.md#precrptillage)
- [preYear1980](v3_specification.HistoricCRPLandManagement.md#preyear1980)

## Properties

### crp

• **crp**: ``"yes"``

Whether the field participated in CRP or not.

**`Default`**

"yes"

**`Example`**

When the field participated in CRP:

```js
"crp": "yes"
```

#### Defined in

[v3-specification.ts:418](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L418)

___

### crpEndYear

• **crpEndYear**: `number`

The CRP end year

**`Minimum`**

1980

**`Maximum`**

2000

**`Example`**

When CRP enrollment ended in 2000:

```js
"crpEndYear": 2000
```

#### Defined in

[v3-specification.ts:463](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L463)

___

### crpStartYear

• **crpStartYear**: `number`

The CRP start year

**`Minimum`**

1980

**`Maximum`**

2000

**`Example`**

When CRP enrollment started in 1980:

```js
"crpStartYear": 1980
```

#### Defined in

[v3-specification.ts:449](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L449)

___

### crpType

• **crpType**: ``"100% grass"`` \| ``"grass/legume mixture"``

The type of CRP the field participated in. Only applicable if [crp](#crp) is set to yes.

**`Example`**

When the field participated in 100% grass CRP:

```js
"crpType": "100% grass"
```

**`Example`**

When the field participated in grass/legume mixture CRP:

```js
"crpType": "grass/legume mixture"
```

#### Defined in

[v3-specification.ts:435](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L435)

___

### postCRPManagement

• **postCRPManagement**: ``"irrigated: annual crops in rotation"`` \| ``"irrigated: annual crops with hay/pasture in rotation"`` \| ``"irrigated: continuous hay"`` \| ``"irrigated: orchard or vineyard"`` \| ``"non-irrigated: annual crops in rotation"`` \| ``"non-irrigated: continuous hay"`` \| ``"non-irrigated: livestock grazing"`` \| ``"non-irrigated: fallow-grain"`` \| ``"non-irrigated: orchard or vineyard"``

How was the field managed after CRP

To find applicable values per field location, see [here](https://docs.google.com/spreadsheets/d/e/2PACX-1vQQnIlyxCENwJvw5Luyg2Ikbn_X0FvMTNr2J6n5Y2xwcR6oi4OA2jNW-B2DrslTKtrmQxg03byZ_aRV/pubhtml)

**`Example`**

```js
"postCRPManagement": "non-irrigated: livestock grazing"
```

#### Defined in

[v3-specification.ts:509](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L509)

___

### postCRPTillage

• **postCRPTillage**: ``"intensive tillage"`` \| ``"reduced tillage"`` \| ``"no till"``

How was the field managed after tillage

**`Example`**

```js
"postCRPTillage": "intensive tillage"
```

#### Defined in

[v3-specification.ts:529](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L529)

___

### preCRPManagement

• **preCRPManagement**: ``"irrigated: annual crops in rotation"`` \| ``"irrigated: annual crops with hay/pasture in rotation"`` \| ``"irrigated: continuous hay"`` \| ``"irrigated: orchard or vineyard"`` \| ``"non-irrigated: annual crops in rotation"`` \| ``"non-irrigated: continuous hay"`` \| ``"non-irrigated: livestock grazing"`` \| ``"non-irrigated: fallow-grain"`` \| ``"non-irrigated: orchard or vineyard"``

How was the field managed before the field entered into CRP

To find applicable values per field location, see [here](https://docs.google.com/spreadsheets/d/e/2PACX-1vQQnIlyxCENwJvw5Luyg2Ikbn_X0FvMTNr2J6n5Y2xwcR6oi4OA2jNW-B2DrslTKtrmQxg03byZ_aRV/pubhtml)

**`Example`**

```js
"preCRPManagement": "irrigated: annual crops in rotation"
```

#### Defined in

[v3-specification.ts:476](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L476)

___

### preCRPTillage

• **preCRPTillage**: ``"intensive tillage"`` \| ``"reduced tillage"`` \| ``"no till"``

How was the field tilled before the field entered into CRP

**`Example`**

```js
"preCRPTillage": "intensive tillage"
```

#### Defined in

[v3-specification.ts:496](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L496)

___

### preYear1980

• **preYear1980**: ``"upland non-irrigated"`` \| ``"irrigation"`` \| ``"lowland non-irrigated"`` \| ``"livestock grazing"``

A description of how the land was managed before 1980.

**`Example`**

When the land was not upland (referring to any land that is not low or marsh-like) irrigated before 1980:

```js
"preYear1980": "upland non-irrigated"
```

**`Example`**

When the land was irrigated before 1980:

```js
"preYear1980": "irrigation"
```

**`Example`**

When the land was not lowland (referring to land that is low and subject to flooding) irrigated before 1980:

```js
"preYear1980": "lowland non-irrigated"
```

**`Example`**

When the land employed livestock grazing before 1980:

```js
"preYear1980": "lowland non-irrigated"
```

#### Inherited from

[HistoricLandManagement](v3_specification.HistoricLandManagement.md).[preYear1980](v3_specification.HistoricLandManagement.md#preyear1980)

#### Defined in

[v3-specification.ts:296](https://github.com/nori-dot-eco/nori-dot-com/blob/475ed1b/packages/project/src/v3-specification.ts#L296)

repository: nori-dot-eco/nori-dot-com

gha_language: TypeScript

repo_name: nori-dot-eco/nori-dot-com


text:
---
layout: post
author: Thomas Cashman
title:  "mini2Dx 1.9.6 released"
date:   2019-06-25 16:00:00 +0000
---

mini2Dx 1.9.6 has been released with the following fix:

 * Fixed crash when Tiled object templates have no properties

To update your existing projects, see the [Updating mini2Dx](https://github.com/mini2Dx/mini2Dx/wiki/Updating-mini2Dx) wiki page.


text:
[![Gem Version](https://badge.fury.io/rb/one_gadget.svg)](https://badge.fury.io/rb/one_gadget)
[![Build Status](https://github.com/david942j/one_gadget/workflows/build/badge.svg)](https://github.com/david942j/one_gadget/actions)
[![Downloads](http://ruby-gem-downloads-badge.herokuapp.com/one_gadget?type=total&color=orange)](https://rubygems.org/gems/one_gadget)
[![Code Climate](https://codeclimate.com/github/david942j/one_gadget/badges/gpa.svg)](https://codeclimate.com/github/david942j/one_gadget)
[![Issue Count](https://codeclimate.com/github/david942j/one_gadget/badges/issue_count.svg)](https://codeclimate.com/github/david942j/one_gadget)
[![Test Coverage](https://codeclimate.com/github/david942j/one_gadget/badges/coverage.svg)](https://codeclimate.com/github/david942j/one_gadget/coverage)
[![Inline docs](https://inch-ci.org/github/david942j/one_gadget.svg?branch=master)](https://inch-ci.org/github/david942j/one_gadget)
[![Yard Docs](http://img.shields.io/badge/yard-docs-blue.svg)](https://www.rubydoc.info/github/david942j/one_gadget/)
[![MIT License](https://img.shields.io/badge/license-MIT-blue.svg)](http://choosealicense.com/licenses/mit/)

## OneGadget

When playing ctf pwn challenges we usually need the one-gadget RCE (remote code execution),
which leads to call `execve('/bin/sh', NULL, NULL)`.

This gem provides such gadgets finder, no need to use objdump or IDA-pro every time like a fool :wink:

To use this tool, type `one_gadget /path/to/libc` in command line and enjoy the magic :laughing:

## Installation

Available on RubyGems.org!
```bash
$ gem install one_gadget
```

Note: requires ruby version >= 2.1.0, you can use `ruby --version` to check.

## Supported Architectures

- [x] i386
- [x] amd64 (x86-64)
- [x] aarch64 (ARMv8)

## Implementation

OneGadget uses symbolic execution to find the constraints of gadgets to be successful.

The article introducing how I develop this tool can be found [on my blog](https://david942j.blogspot.com/2017/02/project-one-gadget-in-glibc.html).

## Usage

### Command Line Interface

```bash
SHELL_OUTPUT_OF(one_gadget)
```

```bash
SHELL_OUTPUT_OF(one_gadget /lib/x86_64-linux-gnu/libc.so.6)
```
![x86_64](https://github.com/david942j/one_gadget/blob/master/examples/x86_64.png?raw=true)

#### Given BuildID
```bash
SHELL_OUTPUT_OF(one_gadget -b aad7dbe330f23ea00ca63daf793b766b51aceb5d)
```
![build id](https://github.com/david942j/one_gadget/blob/master/examples/from_build_id.png?raw=true)

#### Gadgets Near Functions

##### Why

Consider this scenario when exploiting:
1. Able to write on GOT (Global Offset Table)
2. Base address of libc is *unknown*

In this scenario you can choose to write two low-byte on a GOT entry with one-gadget's two low-byte.
If the function offset on GOT is close enough with the one-gadget,
you will have at least 1/16 chance of success.

##### Usage

Reorder gadgets according to the distance of given functions.

```bash
SHELL_OUTPUT_OF(one_gadget /lib/x86_64-linux-gnu/libc.so.6 --near exit,mkdir)
```
![near](https://github.com/david942j/one_gadget/blob/master/examples/near.png?raw=true)

Regular expression is acceptable.
```bash
SHELL_OUTPUT_OF(one_gadget /lib/x86_64-linux-gnu/libc.so.6 --near 'write.*' --raw)
```

Pass an ELF file as the argument, OneGadget will take all GOT functions for processing.
```bash
SHELL_OUTPUT_OF(one_gadget /lib/x86_64-linux-gnu/libc.so.6 --near spec/data/test_near_file.elf --raw)
```

#### Show All Gadgets

Sometimes `one_gadget` finds too many gadgets to show them in one screen,
by default gadgets would be filtered automatically *according to the difficulty of constraints*.

Use option `--level 1` to show all gadgets found instead of only those with higher probabilities.

```bash
SHELL_OUTPUT_OF(one_gadget /lib/x86_64-linux-gnu/libc.so.6 --level 1)
```

#### Other Architectures

##### i386
```bash
SHELL_OUTPUT_OF(one_gadget /lib32/libc.so.6)
```
![i386](https://github.com/david942j/one_gadget/blob/master/examples/i386.png?raw=true)

##### AArch64
```bash
SHELL_OUTPUT_OF(one_gadget spec/data/aarch64-libc-2.27.so)
```
![aarch64](https://github.com/david942j/one_gadget/blob/master/examples/aarch64.png?raw=true)

#### Combine with Script
Pass your exploit script as `one_gadget`'s arguments, it can
try all gadgets one by one, so you don't need to try every possible gadgets manually.

```bash
$ one_gadget ./spec/data/libc-2.19.so -s 'echo "offset ->"'
```

![--script](https://github.com/david942j/one_gadget/blob/master/examples/script.png?raw=true)

### In Ruby Scripts
```ruby
require 'one_gadget'
RUBY_OUTPUT_OF(OneGadget.gadgets(file: '/lib/x86_64-linux-gnu/libc.so.6'))
# or in shorter way
RUBY_OUTPUT_OF(one_gadget('/lib/x86_64-linux-gnu/libc.so.6', level: 1))
# from build id
RUBY_OUTPUT_OF(one_gadget('b417c0ba7cc5cf06d1d1bed6652cedb9253c60d0'))
```

### To Python Lovers
```python
import subprocess
def one_gadget(filename):
  return [int(i) for i in subprocess.check_output(['one_gadget', '--raw', filename]).decode().split(' ')]

RUBY_OUTPUT_OF(one_gadget('/lib/x86_64-linux-gnu/libc.so.6'))
```

## Make OneGadget Better
Any suggestion or feature request is welcome! Feel free to send a pull request.

Please let me know if you find any libc that make OneGadget fail to find gadgets.
And, if you like this work, I'll be happy to be [starred](https://github.com/david942j/one_gadget/stargazers) :grimacing:

gha_language: Ruby


text:
# TangoJS Demo

Project to run demo of TangoJS.

If you want to know more follow [TangoJS project](http://tangojs.github.io/).

[mTango](https://bitbucket.org/hzgwpn/mtango/wiki/Home) is backend support for
TangoJS.

## Requirements
* Python 3.4.4+
* pip3.4+
* Mozilla Firefox 45+
  * enable [`dom.webcomponents.enabled`](about:config)
  * enable [`layout.css.grid.enabled`](about:config)
  * use
    [HTMLImports polyfill](http://webcomponents.org/polyfills/html-imports/)
  * apply [this patch](https://github.com/mliszcz/html-imports-firefox-patch)
    just before the polyfill is loaded
* Google Chrome 49+
  * enable [experimental-web-platform-features]( chrome://flags/#enable-experimental-web-platform-features )

One of the following operating system:
* Windows 10
* CentOS 7
* Ubuntu 14 or 16 (Tango 8 or Tango 9)

## Getting started

1. Make sure you have Python (minimum 3.4.4 version) installed.

2. Clone this project:
   ```bash
   $ git clone https://github.com/Unknown22/TangoJSDemo.git && cd TangoJSDemo/
   ```

3. Install requirements:
    ```bash
    $ sudo pip3.4 install -r requirements.txt
    ```

4. Run python:

    ```bash
    $ python3.4 -m tangojsdemo
    ```
or

4. Install package:
    ```bash
    $ sudo python3.4 setup.py install
    ```

5. Run command:

    ```bash
    $ runtangojsdemo
    ```

6. Follow the instructions.

> If browser will open and you see blank tab, try refresh and check requirements

### Build  and install wheel:

1. Clone this project:
   ```bash
   $ git clone https://github.com/Unknown22/TangoJSDemo.git && cd TangoJSDemo/
   ```

2. Build wheel:
    ```bash
    $ sudo python3.4 setup.py sdist bdist_wheel
    ```

3. Enter to *dist* folder:
    ```bash
    $ cd dist
    ```

4. Install wheel package:
    ```bash
    $ pip install tangojs_demo-0.X.X-py3-none-any.whl
    ```

## Demo

![TangoJS Demo](tangojsdemo/images/demo.png?raw=true)

## License
MIT license


text:
# Report

## The learning algorithm

The basics of this algorithm is described in http://ml.informatik.uni-freiburg.de/former/_media/publications/rieecml05.pdf and
http://files.davidqiu.com//research/nature14236.pdf

The start values for the hyperparameters were taken from a similar project.
---
epsilon_start = 1.0
epsilon_end = 0.01
epsilon_decay = 0.998 (start value was 0.995, vale was increased for more exploration)

replay buffer size = 10000
minibatch size = 64
Gamma = 0.99
Tau = 0.001
learning_rate = 0.0005
Update the network every 4 episodes

The neural network
---
In this project the state is represented as vector. So a simple 3 layer - DNN is used. (This environment also offers pixel output, then a CNN is needed)
- layer 1: 37  --> 128
- layer 2: 128 --> 128
- layer 3: 128 --> 4

## Result and plots

Episode 100	Average Score: 0.22
Episode 200	Average Score: 0.48
Episode 300	Average Score: 1.28
Episode 400	Average Score: 2.30
Episode 500	Average Score: 3.09
Episode 600	Average Score: 4.06
Episode 700	Average Score: 4.75
Episode 800	Average Score: 6.27
Episode 900	Average Score: 6.76
Episode 1000	Average Score: 7.28
Episode 1100	Average Score: 8.08
Episode 1200	Average Score: 8.34
Episode 1300	Average Score: 9.09
Episode 1400	Average Score: 9.12
Episode 1500	Average Score: 9.74
Episode 1600	Average Score: 10.03
Episode 1700	Average Score: 11.30
Episode 1800	Average Score: 11.50
Episode 1900	Average Score: 11.52
Episode 2000	Average Score: 10.93
Episode 2100	Average Score: 11.65
Episode 2200	Average Score: 12.44
Episode 2237	Average Score: 13.02
Environment solved in 2237 episodes.

## Untrained vs trained agent

|  |   |
|---|---|

## Ideas for the future work
- intensive hyperparameter tuning
- a deeper neural network
- other technics like double DQN, dueling DQN, prioritizied experience replay

repository: SibHusky/DQN-CollectBananas

repo_name: SibHusky/DQN-CollectBananas


text:
# Hericium diversidens (Fr.) Nikol., 1950 SPECIES

#### Status
SYNONYM

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Acta Inst. Bot. Acad. Sci. USSR Plant. Crypt. , Fasc. II 6: 222 (1950)

#### Original name
Hydnum diversidens Fr., 1821

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Russulales/Hericiaceae/Hericium/Hericium cirrhatum/ Syn. Hericium diversidens/README.md

repo_name: mdoering/backbone


text:
## Features
- Manage all PC Rayman games with a unified game launcher and configuration shortcuts.
- Configure the games with added options not normally available in the official configuration tools.
- Option to use fan-made utilities to improve the games, such as widescreen support, button remapping, higher quality cutscenes and more.
- Manage your Rayman save files by creating backups and converting to/from JSON.
- Customize how the program runs and looks, from the light/dark mode to more technical options.

### Configuration Tools
Configuration tools are available for the majority of games.

#### DosBox
For the DosBox games configuration a .ini file is created in the application's AppData directory where the chosen configuration values are saved. This file is then loaded into DosBox upon launching the game, along with the optional selected configuration file from the application settings and the mount path. The reason why all configuration commands are not passed in as parameters is due to DosBox having a parameter limit.

#### Rayman 2
The Rayman 2 configuration edits the ubi.ini file in the install directory if the GOG version is used, or else the ubi.ini file in the Windows directory. This configuration tool also has several utilities integrated into it.
The widescreen support option edits the main executable to have the game run in the same aspect ratio as the selected resolution. If widescreen support is disabled, the executable will be edited to restore the original value.
The custom button mapping edits the dinput.dll file in the game's install directory to allow for custom button mapping based on the user's selection.

#### Rayman M/Arena/3
Rayman M, Rayman Arena and Rayman 3 have their configuration saved in two ubi.ini files, one in the Windows directory and the other in the user's AppData. The configuration file the game reads usually depends on if the game is run as administrator or not. Due to this, the configuration tool for these games reads the configuration data from the primary file (in the Windows directory) and saves it to both files.

#### Rayman Raving Rabbids
Rayman Raving Rabbids stores its data in the Registry. Most of the values can be changed from within the game, thus they are not available in the configuration tool.

#### Rabbids Go Home
Rabbids Go Home sends the config as launch arguments when launching the game. As an option in the configuration this can be done in the Rayman Control Panel, allowing for a custom configuration.

#### Rayman Origins/Legends
Rayman Origins and Rayman Legends both store their data in the Registry.

#### Rayman Jungle/Fiesta Run
Rayman Jungle/Fiesta Run stores its configuration in single-byte files in the app data.

### Utilities
Utilities are available to help the games run better or add new functionality to them. Some files needed for utilities are not stored within the application due to them taking to much space. These will need to be downloaded.

#### Rayman 1 - PlayStation Soundtrack
This utility allows the game to run with the PlayStation soundtrack. For this to work, the Rayman Control Panel has to be running in the background to be able to turn off the in-game music and play the PlayStation one instead. This is done from a loop which keeps track of the game's values while running. The music itself is stores in the application's AppData and can be uninstalled from the utility dialog.

#### Rayman 1 - Complete Soundtrack
This utility replaces the Rayman Forever soundtrack with the complete one used in other editions. The utility also allows the soundtrack to be reverted back to the incomplete one.

#### Rayman Designer - Replace Infected Files
This utility will search the Rayman Designer install directory and replace any of the known infected files from the Rayman Forever release.

#### Rayman Designer - Create Missing Configuration File
This utility will recreate the Rayman Designer configuration file if it is missing, which in turn would cause the Mapper program not to launch.

#### Rayman 2 - Unofficial Translations
This utility will replace the game's textures.cnt and fix.sna files with custom ones to allow custom languages to be used in the game.

#### Rayman 2 - Patch Disc Version
This utility replaced the disc version's files with those from the GOG version to avoid the disc error.

#### Rayman 3 - DirectPlay
This utility will allow the option to enable or disable the Windows legacy feature DirectPlay which is needed to run the game.

#### Rayman Origins - Higher Quality Videos
This utility will allow the PC video files to be replaced with the ones from the PlayStation 3 version which are in higher quality.

#### Rayman Origins - Localization Converter
This utility allows the localization file to be converted to/from JSON.

#### Rayman Origins - Debug Commands
This utility will create a file called "cmdline.txt" in the game's install directory with the selected debug commands.

#### Rayman Origins - Update to 1.02
This utility will download the official Rayman Origins disc updater which allows the disc version to be updated to version 1.02.

#### Rayman Legends - UbiRay Character
This utility will edit the selected save file to have the currently selected character be UbiRay.

#### Rayman Legends - Localization Converter
This utility allows the localization file for Rayman Legends, Rayman Adventures and Rayman Mini to be converted to/from JSON.

#### Rayman Legends - Debug Commands
This utility will allow the game to be launched with the selected debug commands. This is only available for the Uplay version.

#### Rayman Fiesta Run - Localization Converter
This utility allows the localization file to be converted to/from JSON.

path: /Documentation (old)/Documentation.md


text:
---
layout: text/textblock
---
WYSIWYG stands for 'what you see is what you get'. This is the default kind of content editor for a CMS. It is sometimes also called a rich text editor. You should configure your WYSIWYG text editor to follow your own agency’s style guide.

The CMS text editor should instruct writers about style and format. Some examples include fonts, colours, sizes, heading styles and metadata.

You may also refer to the DTA [Content Guide](https://guides.service.gov.au/content-guide/) for more on this.

Editing features should support content writing. Limit the editor to basic styles and features of the style guide. Too many options makes it easy to create content that doesn’t follow the style guide.

The editor should support accessible images. You will also need to specify the image formats and file specifications that the CMS will accept.

Talk to your developer to find out how reliable and secure the text editor is, and if you need to use HTML.

Some areas to be aware:
- Potential need for customisation of content using HTML
- Type of code used (ie; open source versus proprietary systems)
- Suitability for everyone who needs to use it
- Compliance with accessibility issues
- Regularity of CMS updates and new versions
- Reliability and compatibility with current technologies and changes

repository: govau/service-manual

repo_name: govau/service-manual


text:
# `Reuty's Health Lab - Welcome!`

![](gifs/all.gif)

This project provides some code for learning and testing healing mechanics found across many types of game. The project also includes a few different types of health display, like the MMO type profile in the top right, an ARPG 'health bowl' in the bottom left, a heart type system in the center at the bottom, and a standard no-frills health bar in the center.

This project is designed to help you learn how these types of mechanisms can be implemented in games, and particularly how to do it using the Godot engine. Feel free to use this code anywhere you like, crediting [@not_reuty](https://twitter.com/not_reuty) is not required but greatly appreciated!

A huge thank you to [Kenney](https://twitter.com/KenneyNL) for making the assets public, and to the creator of [Komika Title](https://www.dafont.com/komika-title.font) (the font used throughout)!

## `Active Healing`
Active healing comes in many forms, from item pickups, to consumables, spells, and more. This project contains code for three types of active healing, i) consumable heal-over-time, ii) consumable instant heal, and iii) regular instant heal (like an instant cast spell).

Each are slightly different, see below for details;

### `Energy Drink`
An energy drink is a consumable item which gives a heal-over-time effect for a few seconds. The strength of the healing effect can be changed with the `consumable strength` buttons, which shows how many points of health are healed per second the effect is active. Drinking an energy drink extends the duration of any existing regeneration effect, like in battle royale games.

![](gifs/energy_drink.gif)

### `Painkillers`
Painkillers are similar to energy drinks but take longer to apply, and their effect lasts longer. The strength of the regeneration effect applied by painkillers is the same as energy drinks, but since they last longer their overall heal is greater.

![](gifs/painkiller.gif)

The healing effect given by both energy drinks and painkillers doesn't end if the player reaches full health. If they take damage after using either of them, any remaining effect will be applied.

### `Bandage`
A bandage is a consumable which heals a small amount of health instantly following a short delay. It cannot heal the player over maximum health, and will not affect any damage taken after the bandage has been applied (unlike the over-time regen provided by energy drinks and painkillers).

![](gifs/bandage.gif)

### `Medkit`
A medkit is a consumable which heals the player to full health instantly following a long delay. Like the bandage, it can't heal the player over maximum health.

![](gifs/medkit.gif)

### `Flash Heal`
The flash heal is like a bandage but takes no time to heal (like an instant cast spell).

![](gifs/flash_heal.gif)

### `Lay On Hands`
The lay on hands is like a medkit but takes no time to heal. It's useful for resetting the player's health to test the strength of the damage over time effect in the damage section.

![](gifs/lay_on_hands.gif)

## `Damaging the Player`
This project is all about healing, but to make that possible we need a way to damage the player. The `punch` and `whack` buttons do a small amount of damage, or bring the player to 5 health respectively. Below these two instant damage buttons, the damage over time slider lets you set a constant damage effect, which will be applied every game tick and whose value represents the damage taken by the player per second.

## `User Interface`
The UI links into the player's code through the `pressed()` and `value_changed()` events, which then set boolean values in the player directly. In an actual game this could be called from an inventory manager or similar if the player had the right healing items in their bags.

![](gifs/ui.png)

## `Project Structure`
The project structure is fairly flat, with a single player node plus a `CanvasLayer` which holds all of the UI elements. One non-intuitive part is that the consumable indicators are children of the player node, *not* the UI canvas. This is so that if the player moves, the indicators will follow if the camera stays where it is. Feel free to change/adapt this as needed in your projects!

![](gifs/structure.png)

### `Other Interesting Bits`
Although this project is all about healing mechanics, there are some other cool bits to point out;
- the consumable strength UI is custom coded because I couldn't find any +- buttons built in
- this project follows on from my previous [damage lab](https://github.com/not-reuty/damage_lab) project
- the `lay on hands` name comes from a [WoW Paladin Spell](https://classic.wowhead.com/spell=633/lay-on-hands)

## `Want to know more?`
I'd like to help - tweet me [@not_reuty](https://twitter.com/not_reuty) any questions you have about this project and I'll do my best to answer them. Good Luck!


text:
pinso
=====

A fault localization system that precisely pinpoints the root cause of concurrency bugs.
The goal of Pinso is to help programmers triage a concurrency
bug by analyzing a failed execution and automatically isolate
its root causes. It takes advantage of the fact that concurrency
bugs are non-deterministic. For a given bug triggering input,
there correspond a huge number of legal thread interleavings,
many of which tend to produce correct executions. Our observation
shows that, correct interleavings tend to manifest much
more frequently than the incorrect interleavings for a given
bug triggering input, especially in applications that adhere
to strict software quality assurance process. Pinso exploits
the above observation to isolate the root causes of a failed
execution.

1.1 OS and kernel
=================

Currently, the tool only supports Linux.

Tested Arch:
  x86_64

Tested OS:
  Redhat Enterprise Linux 5.4

  Ubuntu Desktop 10.10

1.2 Building essentials
=======================

GNU make version 3.81 or higher.

PIN binary instrumentation tool, latest version.

Google protobuf tool, version 2.4.1 or higher.

1.3 Target programs
===================

In general, our tool can test any x86 binary with the following
conditions:
  1) Should use dynamic linking
  2) Preferably use -fno-omit-frame-pointer when compile
  3) Preferably use pthread library for threading and synchronization

1.4 How to build the package
===================

1) Download and install
   a) the latest PIN binary instrumentation tool
   b) the latest Google protobuf tool

2) Set environment variable PIN_HOME and PROTOBUF_HOME accordingly

3) Make the package

   $ make compiletype=debug
   (To build the debug version)

   $ make compiletype=release
   (To build the release version. Slow assertions are removed.)

repository: poeliu/Pinso

repo_name: poeliu/Pinso


text:
# Changelog

All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.

### [1.0.0](https://github.com/eralpsahin/mysu-api/compare/v0.1.0...v1.0.0) (2019-08-05)

- Refactor getPerson endpoint to return an array of people.

### [0.0.7](https://github.com/eralpsahin/mysu-api/compare/v0.0.6...v0.0.7) (2019-07-20)

- Add travis and test CI.

### [0.0.4](https://github.com/eralpsahin/mysu-api/compare/v0.0.3...v0.0.4) (2019-07-20)

- Refactor API as a class.
- Add CORS bypassing feature to the API with `MySU({bypassCORS: true});`.

### 0.0.3 (2019-07-20)

- Remove scripts for package development from README.

### 0.0.2 (2019-07-19)

This is an alpha release for the Unofficial MySU Web API. With following features;

- Authenticate
- SuCard Data
- Course Schedule
- Directory Search

repository: eralpsahin/mysu-api

repo_name: eralpsahin/mysu-api


text:
Cordova Android Plugin for Bean SDK
===

A Cordova plugin, or JavasSript bridge and wrapper class for the native Java based PunchThrough Bean Android SDK.

[https://github.com/PunchThrough/Bean-Android-SDK](https://github.com/PunchThrough/Bean-Android-SDK)

Created to help my kids and I interact with BLE arduino devices, specifically the PunchThrough LightBlue Bean & Bean+ units. Many of us do not have iPhones, so we created this minimal plugin to enable us to build an HTML5 Android app with the Ionic Framework.

Note that there are no unit tests and we only scratch the surface of what can be done here. If you're interested in a more professional effort that can communicate with various BLE lines, check out the ```cordova-plugin-ble-central``` plugin:

[https://github.com/don/cordova-plugin-ble-central](https://github.com/don/cordova-plugin-ble-central)

For the full Ionic app that utilizes this LightBlue Bean specific plugin, visit the following repo. You should actually start there too, because the Ionic app will automatically pull this repo when building locally for the first time.

[http://github.com/djabraham/cordova-ionic-bean](http://github.com/djabraham/cordova-ionic-bean)

**NOTE:** This plugin is for Android only, version 18 or greater.

**MIT Licensed**

repository: djabraham/cordova-plugin-ngbean

repo_name: djabraham/cordova-plugin-ngbean


text:
# Development

## Week 1
- `4/19/2020`: Researched pytorch and its c++ frontend. Researched neuro networks. Watched tutorials on how to train
a neuro network on the mnist dataset.

- `4/20/2020`: Followed examples to run a minimal program that uses libtorch. Used cmake to create an executable which
could be run to display some tensors. Researched cmake, the building, and the linking process.

- `4/21/2020`: Built a simple neuro network in python. Trained it and tested it on the mnist dataset. Saved the model
as a format c++ frontend can load. Imported libtorch into the final project to successfully load the model.

## Week 2
- `4/24/2020`: Researched opencv, learned how to edit an image so that I can use my pre-traind model to make an inference.

- `4/25/2020`: Installed opnecv. Imported opencv into the project. Rewrote the python script because the format was wrong when the model was saved.

- `4/26/2020`: Used opencv to resize/edit an image from file. Converted the image to tensors which can be used with
the pre-trained libtorch model to make an inference.

- `4/27/2020`: Hand wrote digits to test the functionality of the Classity_Image method.

## Week 3
- `5/1/2020`: Read Cinder documentations on images and handling file drop events. Reviewed Snake project code
to learn how to draw texts on screen.

- `5/3/2020`: Added the background image and implemented rendering functions for the main page. Implemented functions
to handle the file drop event and use the image to call ClassifyImage method to display predicted digit.

- `5/4/2020`: Renamed some files and documented code.


text:
---
layout: post
title: 5 reasons Wales is more than cheese on toast and singing.
---

1. Mail Order Business

As well as a fantastic name, Montgomeryshire born, Sir Pryce Pryce-Jones invented the idea of a mail order business. He sold Welsh flannel to Queen Victoria, Florence Nightingale, and Australia from his warehouse in Newtown.

2. Natural Selection

Alfred Russel-Wallace pipped Darwin at the post! He published his own essay “On the Tendency of Varieties to Depart Indefinitely From the Original Type” which outlined the theory of evolution by Natural Selection which was refined by Darwin a year later in “On the Origin of Species”

3. The microphone

David Edward Hughes, from Bala, invented the microphone after showing that it was the interaction between parts in carbon telephone that resulted in the change of resistance, and was responsible	 for the ability of the device to pick up extremely weak sounds.

4. The University of the Atlantic

A century before Augustine became Archbishop of Canterbury, and probably for much longer, Llanilltud Fawr in Cardiff was spreading the Gospel, Greek, mathematics, and geometry. Supposed famous alumni include St David, St Patrick, and the bard Taliesin.

5. World’s first railways.

The world’s first steam powered locomotive was demonstrated in Merthyr Tydfil in 1804, and the first fare paying system was introduced on the Gower in 1807.

Stereotypes of Welsh cultural backwardness exist to justify modern Britain’s underinvestment in Wales. Contrary to belief, Wales has made many important cultural and scientific contributions to the world.

#AtomicEssay

url: https://raw.githubusercontent.com/TomKealy/TomKealy.github.io/b3d700802a8444e0ab6689b0b6283e8c554246b1/_posts/2021-10-06-5 reasons Wales is more than cheese on toast and singing.md

gha_language: Jupyter Notebook


text:
# FakeCovid

Link: [https://gautamshahi.github.io/FakeCovid](https://gautamshahi.github.io/FakeCovid)

Paper link: [FakeCovid- A Multilingual Cross-domain Fact Check News Dataset for COVID-19](http://workshop-proceedings.icwsm.org/abstract?id=2020_14)

Task:
* task - description of potential task
* another potential task - ...

FakeCovid is the first multilingual cross-domain dataset of 7623 fact-checked news articles for COVID-19, collected from 04/01/2020 to 01/07/2020(with a monthly update). We have collected the fact-checked articles from 92 fact-checking websites after obtaining references from Poynter and Snopes. We have manually annotated the collected articles into 11 categories of the fact-checked news according to their content. The ultimately generated dataset is in 40 languages from 105 countries. We have built a classifier to detect fake news and predict its class. Our model achieves an F1 score of 0.76 to detect the false class and other fact check articles. For more detailed information about the FakeCovid dataset, you can refer to the paper.

**Note:** Important note about data/dataset.

## Attributes

* **attribute** - description
* ...


text:
# Poisson-solver-2D

Finite difference solution of 2D Poisson equation

Current version can handle Dirichlet boundary conditions:

  (left boundary value)

  (right boundary value)

  (Top boundary value)

  (Bottom boundary value)

The boundary values themselves can be functions of (x,y).

### Package requirements
  - NumPy
  - SciPy (sparse matrices, sparse linear algebra)

### Version notes
- version 1.1
  - Fixed a bug regarding the right-hand function
  - Figure size and font size adjusted

- version 1.0 notes
  - Sparse matrix implementation. CSR format (Compressed sparse row matrix) matrix.

### Sample Output
Solution of  with boundary conditions  is shown below:

### References
  - Sparse matrices: https://docs.scipy.org/doc/scipy/reference/sparse.html
  - Sparse matrix linear algebra: https://docs.scipy.org/doc/scipy/reference/sparse.linalg.html


text:
---
hrs_structure:
  division: '1'
  volume: '5'
  title: '17'
  chapter: '286'
  section: 286-125
type: hrs_section
tags:
  - Government
menu:
  hrs:
    identifier: HRS_0286-0125
    parent: HRS0286
    name: 286-125 Discretionary revocation or suspension of license by a court
weight: 38560
title: Discretionary revocation or suspension of license by a court
full_title: 286-125 Discretionary revocation or suspension of license by a court
---
**§286-125 Discretionary revocation or suspension of license by a court.** In addition to the provisions for mandatory revocation of a license set forth in section 286-124, any court of competent jurisdiction may, in its discretion, revoke or suspend the license of any driver convicted of any felony in the commission of which a motor vehicle is used, or convicted of a violation of this part or of any traffic law or regulation of the State or any political subdivision thereof involving a vehicle in motion. [L 1937, c 234, §23; RL 1945, §7324; RL 1955, §160-56; [HRS §286-125](/title-17/chapter-286/section-286-125/); am L 1970, c 164, §3; am L 1971, c 171, §2]

Case Notes

As §291C-161(c) requires every person convicted under §291C-105 to be sentenced in accordance with §291C-105, trial court erred in sentencing defendant to a six-month driver's license suspension under this section; the plain language of §291C-105 required the sentencing court to impose the list of sanctions as specific under §291C-105(c), including a thirty-day license suspension for a first-time offender. 121 H. 117 (App.), 214 P.3d 1107 (2009).

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby