text:
# File Browser

Now, it's time to take your knowledge one step further. You're going to marry
your knowledge of layout with your knowledge of asynchronous programming and
data structures to interact with a server that shows you the contents of files
on your computer. From this point forward, most projects that you do will
combine all of the knowledge that you've used up to this point. The projects
will ask you to practice many skills in combination.

**The story**: This project mimics something you will experience while on the
job. There's some old version of some software running, and the users want
something newer and better. This project has you "replace" an existing software
application that browsers a file system with one that lets the users interact
better with the file system as well as improving information density and
throughput.

This project will have a tree, both visually and in memory, that stores the
representation of files and directories on your computer's hard drive in the
browser so that you can interact with it.

![](https://appacademy-open-assets.s3-us-west-1.amazonaws.com/Module-Responsive-Design/response-design-projects/file-browser/file-browser-final.gif)

## The starter project

Download the starter project from
https://github.com/appacademy-starters/responsive-design-file-browser-starter.
It comes with a server that you will interact with from your code via `fetch`
statements.

Run `npm install` to install the dependencies.

Go ahead and start the server by typing `npm start` in the starter project.
You'll see that the program prints out the following message.

```
Your browser.html and API served from http://localhost:3001
Browse the files statically at http://localhost:3000
```

That's right, it started _two_ Web sites. The first one is at
http://localhost:3000. Click on that link. It will open the existing version of
the file browser. It is fully functional, but basic in its presentation and
interactions.

![old version of the file browser](https://appacademy-open-assets.s3-us-west-1.amazonaws.com/Module-Responsive-Design/response-design-projects/file-browser/file-browser-old-version.png)

Continuing the story, the users have clamored for something "more modern" as
well as being able to see files and directories in a tree next to the contents
and information. That's what you're going to give them!

## The starter project contents

The directory structure of the project looks like this.

```
starter/
├── directory-browsed/
├── server/
└── your-code/
    ├── icons/
    ├── browser.html
    └── style/
```

The **directory-browsed** directory is where the server will read directory
contents from. If it's in that directory, then you should be able to see it in
the application that you write. Right now, it contains a lot of files from an
open-sourced book called JavaScript Allonge, Sixth Edition, by Reg Braithwaite.
(https://github.com/raganwald/javascript-allonge-six)

The **server** directory contains the node server that powers the application
and serves your page. It starts _two_ servers:

- http://localhost:3000 - this is a built-in and rudimentary file browser that
  your application would replace
- http://localhost:3001 - this will server your code and serve your API requests
  when you `fetch` data

The **your-code** directory contains **browser.html**, the file in which you
should put your HTML. You can create all the CSS and JavaScript files you want
in the **your-code** directory and link them the way that you would normally do
it. The server will serve them for your pleasure.

The **your-code** directory also contains icons and a CSS reset file.

## The application user interface

TODO: Explain final layout

## An API overview

Your code will make calls to an Application Programming Interface (API), which for
this case, is just a fancy way of saying "a place to get data from". The
following table shows the different ways that you can call the API. All URLs in
the first column will be for the server http://localhost:3001. All of the paths
are relative to the **directory-browsed** directory.

| URL                    | HTTP Verb | What it does                                                 |
| ---------------------- | --------- | ------------------------------------------------------------ |
| /api/path/«dir-path»   | GET       | This returns the list of files and directories in «dir-path» |
| /api/file/«file-path»  | GET       | Returns the contents of the file at «file-path»              |
| /api/entry/«file-path» | PATCH     | Moves a file from one location to another                    |

Each step of the project will go into depth about what you should do to
interact with those API endpoints. For example, **directory-browsed** has the following entries to two levels deep.
(There are a lot more files under **javascript-allonge-six/manuscript/**.)

```
directory-browsed/
├── example.txt
└── javascript-allonge-six/
    ├── LICENSE
    ├── README.md
    ├── manuscript/
    └── need-to-be-fixed
```

Here's an example of how you would call the API to retrieve the contents of a
directory.
Let's say you added the following HTML block to **your-browser.html**.

```html
<script async>
  fetch('/api/path/javascript-allonge-six/')
    .then(response => response.json())
    .then(filelist => console.log(filelist);
</script>
```

The server would get the path `/api/path/javascript-allonge-six/` as
part of your request.

The `/api/path` part is there for the server to know that you're using the API
and want it to look at the contents of a directory at the path that comes after
`/api/path/`.

The path that comes after `/api/path` is `/javascript-allonge-six/`.
The server looks in the **directory-browsed** directory for
`/javascript-allonge-six/`, finds it, and returns the list of files
to your `fetch` call. Then we use the `response.json()` to grab the list of
files in the directory, and finally, print it to the console.

Whatever path you put after `/api/path`, it's going to try to read the list
of files from that directory and return them. If the directory doesn't exist (or
something bad happens), then your code will get an appropriate HTTP status code
that indicates the error, like 404.

> Remember that you will need to check `response.ok`
> in `fetch` calls to catch things like 404 errors.)


text:
tran
====

Chrome extension for quick translating with multitran.ru (or some other translate engines)

https://chrome.google.com/webstore/detail/lhjldahfbiadelganmhjiolblffjjgok/

Build command: `grunt` creates zip ready for publish.

####Full installation:
Assume nodejs and npm are installed. Also install grunt-cli:`npm install -g grunt-cli`

1. git clone repo and `cd tran`
3. `npm install` — install all project dependencies
3. `grunt`— run build

Build also creates "build" folder that can be loaded as "unpacked extension" for local tests.

license: MIT

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
---
layout: page
title: "Featured Projects"
---

### Featured Projects on Pulse
[Mozilla Pulse](https://www.mozillapulse.org/featured) is a listing of lots of cool projects, news, events and people from around the movement for a healthy internet.

Global Sprint projects that have made an extra effort to be contributor-friendly are listed on Mozilla Pulse; these Pulse entries also show up on the main Global Sprint website. Cool! Getting your project on Pulse means more visibility for work, and potentially more contributors at the Sprint.

To be featured, you need to fill out the FEATURED PROJECT items in your project checklist issue in the [main sprint repo](https://github.com/mozilla/global-sprint/issues). Then, fill out the [Mozilla Pulse submission form](https://www.mozillapulse.org/add).

The following information must be included in any Pulse listing-- ensure that this information is complete! Otherwise your submission may be rejected, and you'll have to re-submit. This is a highly visible listing on Mozilla's website(s), so be sure your spelling and grammar are correct-- no typos please! Keep your text concise and clear.

* **Title** Use the title of the project
* **URL** If the project has a landing page, it goes here. Otherwise, link to the README in your project repo-- this will send curious potential contributors straight to the information they need about the project.
* **Description** A clear and concise description of the project
* **Creator(s)** Project lead name(s)
* **Why might this be interesting to other people in our network?** This field is important-- it will help contributors see the value of your work, why they should get involved, and where they fit in!
* **Key Internet Issues** OK to add multiple issue tags.
* **Tags** `mozsprint` and `2018` are **required!** We use these tags to pull entries into the Global Sprint main page!
* **Project Image** Images are important! Pulse is a very visual platform, so an eye-catching image will help your project stand out
* **Looking for support?...** In the text box, list specific ways people can help, like "logo design" or "javascript coding." Also select the top three asks for help from the list provided in the form.
* **Link for people to get involved.** -link to the Contributor Guidelines in the project's repository.

Submission form: [https://www.mozillapulse.org/add](https://www.mozillapulse.org/add)

Once you have submitted your Pulse listing, tag your Project Coach in the issue saying "This is ready to be featured on Mozilla Pulse" If you've followed the steps above carefully, your Coach will approve your submission. Your Project is now FEATURED on network pulse--- YAY!

repository: mozilla/global-sprint

gha_language: CSS

gha_license_id: MIT

repo_name: mozilla/global-sprint


text:
---
layout: post
status: publish
title: New Macbook and Macbook Pros

date: '2008-02-26 15:09:00 +0000'
date_gmt: '2008-02-26 15:09:00 +0000'
tags:
- apple
- mac
- hardware
---
Amid the ever entertainment Apple rumour mill so long awaiting updates have today popped out. Updates to the Macbook and Macbook Pros.
Nothing massive really, the screens on the MBP's perhaps. Specs mainly.
This taken from Apple Gazette.

The Macbook Pro now features the same multi-touch trackpad featured on the Macbook Air, but neither the Macbooks nor the Macbook Pros feature any real significant cosmetic changes. The new MacBook Pro features the latest Intel Core 2 Duo technology with up to a 2.6 GHz processor with 6MB of shared L2 cache; up to 4GB of 667 MHz DDR2 SDRAM memory and up to a 300GB hard drive, plus NVIDIA GeForce 8600M GT graphics with up to 512MB of video memory.
The MacBook lineup comes in three models and includes faster processors and larger hard drives across the line; white 2.1 GHz and 2.4 GHz models with 120GB or 160GB 5400 rpm hard drives and a black 2.4 GHz model with a 250GB 5400 rpm hard drive, previously only available as an option. The 2.4 GHz MacBook models ship with 2GB of memory standard, expandable up to 4GB across the line.


text:
# Telegram Bot - EqualHash Pool

## Get Started

This Bot is mounted on Docker, so implementing it is very easy. You just need to have a database [MongoDB](https://hub.docker.com/_/mongo) and this container.

## Environment variables
Below you can see the Environment variables necessary for the operation of this container.

 - **$TELEGRAM_TOKEN** -> Token to access the HTTP API of your bot.

 - **$URI_MONGODB**	-> Connection URI with your MongoDB database.

> For example<EMAIL_ADDRESS>
 - **$URL_POOL** -> URL of your Pool and where the bot will be able to consult the statistics.

## Start the Container

To run this bot using Docker you can use the following command:

    docker run -d \
    -e "TELEGRAM_TOKEN=YOUR-TELEGRAM-TOKEN" \
    -e "URI_MONGODB=YOUR_URI_CONNECT_MONGODB" \
    -e "URL_POOL=URL_FOR_YOUR_POOL" \
    octaviojmaia/bot-equalhash

## Donations

**ETH/ETC**: 0x07EafA605A7253af37C5bd9F5d1e62F3a073424a

repository: belmix/equalhash-telegram-bot

repo_name: belmix/equalhash-telegram-bot


text:
![Node.js CI](https://github.com/ruffythepirate/ts-s3-metrics/workflows/Node.js%20CI/badge.svg)

# S3 Metrics

AWS has very good support for metrics, and a very powerful way of implementing these metrics with other functionality. The problem is that if you work on a hobby project it's quite expensive to pay 0.3$ per metric. That is why this library instead helps you to read and write metrics to S3, so that you can track developments over time without accumulating a high running cost.

## Features

* The library contains logic to:
  - Read metrics
  - Write metrics
  - Support different merge modes when writing metrics.
  - Support writing metrics in different resolutions.

For full information, please refer to the [API documentation](https://ruffythepirate.github.io/ts-s3-metrics/globals.html) to see available classes and their functions.

## Requirements

* Node and npm
* To build or develop you will benefit from having `npx` https://github.com/npm/npx. This allows invoking of the other global npm requirements in the repository (Typescript, Jest) without having to install them.

## Usage

Not available yet.

## Contributing

Contributions, if they are in line with expanding functionality that can help with layout logic are welcome. Requirements for pull requests are:
* All code is tested
* Naming is consistent with project naming
* Commits are squashed and contain a clear commit message describing what functionality is added.

## License

[MIT](./LICENSE)

branch_name: refs/heads/main


text:
---
posttitle:  afrimapr showcase and Q&A session
categories: [presentation, open education week]
background: assets/img/blog/posts_20210506.jpg
author: [Andy South, Anelda van der Walt]
---

Back in March we hosted a showcase and Q&A during Open Education Week. The aim was to share the vision for what we are doing, gain an indication of interest from our audience and to answer questions. The video and slides can be viewed here.

![map showing where registrants are based]({{ site.baseurl }}/assets/img/blog/posts_20210506_1.jpg)

105 people registered  and 30 attended on the day. We were pleased to get such a level of interest, mostly through promotion on twitter. More than 70% of registrations were from Africa with 21 countries represented including the top two, Kenya & Nigeria.

Survey responses from those that registered will help us target our efforts.

![in which field do you work]({{ site.baseurl }}/assets/img/blog/posts_20210506_2.jpg)

It was great to see the diversity in occupations of those interested to learn mapping in R. Nearly half of those that registered worked in Health, and a quarter in Education. This partly reflects our targeting and shows good potential for health impact that is important for us and our primary funders, the Wellcome trust.

![in which sector do you work]({{ site.baseurl }}/assets/img/blog/posts_20210506_3.jpg)

51% worked in Academia, 28% for NGOs and 12% in Government. The high numbers from Academia likely reflects the popularity of R (& twitter !) there. We were also happy to see interest from the more operational sectors of NGOs and Government. This gives an indication of the potential to share R techniques across sectors to achieve maximum impact.

![level of R experience]({{ site.baseurl }}/assets/img/blog/posts_20210506_4.jpg)

We were excited to see a good range of R experience, centred on those identifying at beginner and intermediate levels. This will help us target our resources in future. We see high potential for resources targeting those that are relatively new to R. One challenge for us is also to reach out to those with more experience to see how we can help them share their work with the community.

During the session we shared information about the project, resources that have been developed, and our plans for the future. We also sought interested participants for a three-episode online training series trialing our new [tutorials](https://afrimapr.github.io/afrimapr.website/blog/2021/interactive-tutorials-for-african-maps/). We’ve just completed that and will report here soon.

The Q&A session attracted a good selection of questions, you can listen to them and our responses in the video above. We were asked about whether we could provide help to those mapping their own data, our target audience and outputs, comparisons between R & Tableau, and any plans to build capacity in Africa. If any questions do remain for you then please do [reach out to us](https://afrimapr.github.io/afrimapr.website/get-involved/).

It was good to see that there are plenty of people working in Africa who are interested in what we are doing and want to hear more from us. We will keep you updated on our progress.

![stay in touch]({{ site.baseurl }}/assets/img/blog/posts_20210506_5.jpg)

gha_language: SCSS


text:
# Portfolio Template 5

This is a portfolio site inspired by figma

![screenshot](/images/mob-screenshot.PNG)

#
Live Demo

# Description

![Live demo](/gif/temp5.gif)

>A site showing some of my best works structured beautifully. This site is fully responsive and compatible to all screen sizes and all device. A combination of flexbox and grid are used to bring this site to life. It is divided into a navigation section, an homepage section, a work section, an about section and a footer section.

# Built With

● HTML

● CSS

# Technologies used

● Git and Github

● Linters

● Normalize

# Getting Started

To get a local copy up and running follow these simple example steps.

⬜ clone the app by running this command `git clone https://github.com/fobadara/portfolio-template-5`

⬜ Run this command `cd portfolio-template-5`

⬜ Open in browser

# Prerequisites

You will be needing:

⬜ A web browser to view output

⬜ A text editor or terminal

# Run tests

You can run tests by following these steps:

⬜ commit and push your changes

⬜ navigate to pull request on github

⬜ I have created a pull request which runs linters. If you wish you could simply create a pull request of your own

# Authors

👤 Abdulfatai Badara

GitHub: [@fobadara](https://github.com/fobadara)

Linkedin: [Abdulfatai Badara](https://linkedin.com/in/abdulfatai-badara-84a5791b4)

## 🤝 Contributing

Contributions, issues, and feature requests are welcome!

Feel free to check the issues page.

# Show your support

Give a ⭐ if you like this project!

# Acknowledgments

Hat tip to anyone whose code was used

Used an  icon by Dryicons

Lots of appreciations to my wife, Habeebah who keeps supporting me

# 📝 License

This project is licensed by [MIT](LICENSE)

gha_language: HTML


text:
---
layout: default
img: image20.jpg
category: Teresa
title: House and Lot in Rizal 3 beds and 1 bath
published: true
---

### Bria Palazzo Teresa Rizal

Specification:

- Guard House
- Basketball court
- Multipurpose hall
- Play area

Location: Bagumbayan Teresa Rizal

- Lot Area: 90 sqm.
- Floor Area: 42 sqm
- No. of Bedroom: 3
- No. of Toilet & Bath: 1
- Garage: 2
- Total Contract Price: 1,465,000
- Equity: 15% 215,250
- Equity Terms: 12,828/16 months
- Max.Terms: 30 years
- Loanable Amount: 1,219,750
- Monthly Amortization: 7,710
- Financing: Bank/Pag-ibig

- Description: Single Attached
- Price per Square 11,098.48

repository: oscariotes/EQ-Lead-Gen

extension: markdown

repo_name: oscariotes/EQ-Lead-Gen


text:
# twitch-downloader

Easily download twitch VODs and Clips.

## Usage

![Uage](doc/usage.gif?raw=true)

## Download

You can download the latest release for Windows, Macos and Linux here:
https://github.com/jybp/twitch-downloader/releases

## Flags

|       Flag      | Description |
| --- | --- |
| `-url` | The URL of the twitch VOD or Clip to download. |
| `-q` | Quality of the video to download. Omit this flag to print the available qualities.<br>Use "best" to automatically select the highest quality. |
| `-o` | Path where the video will be downloaded. (optional)|
| `-start` | Specify "start" to download a subset of the VOD. Example: 1h23m45s (optional) |
| `-end` | Specify "end" to download a subset of the VOD. Example: 1h34m56s (optional) |
| `-client-id` | Use a specific twitch.tv API client ID. Using any other client id other than twitch own client id might not work. (optional) |
| `-v` | Verbose errors. (optional) |

## Build from source

1. Install the latest version of Go https://golang.org/
2. Clone the git repository
3. Set the current directory to `cmd/twitchdl` and run `go build -ldflags "-X main.defaultClientID=TwitchClientID"`

repository: jybp/twitch-downloader

gha_language: Go

repo_name: jybp/twitch-downloader


text:
# Choco

The package manager for Windows
Chocolatey - Software Management Automation

网址：[https://chocolatey.org](https://chocolatey.org)

Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.

欢迎来到Chocolatey社区包存储库！网站此部分中的软件包由社区提供，维护和审核。

## 特点

- Security, consistency, and quality checking 安全性、一致性和质量检查
- Installation testing 经过安装测试过
- Virus checking through VirusTotal 通过了VirusTotal检查病毒
- Human moderators who give final review and sign off 最终通过审核并由负责人签字

## 如何安装？

1. First, ensure that you are using an administrative shell - you can also install as a non-admin, check out Non-Administrative Installation.
1. Copy the text specific to your command shell - cmd.exe or powershell.exe.
1. Paste the copied text into your shell and press Enter.
1. Wait a few seconds for the command to complete.
1. If you don't see any errors, you are ready to use Chocolatey! Type choco or choco -? now, or see Getting Started for usage instructions.

```cmd
@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
```

## 全局设置系统环境变量

```cmd
SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"
```

> 需要通过 "系统高级设置" -> "环境变量"  -> 添加到系统环境变量中
> 然后，重新启动shell就可以使用了。

## 如何更新该工具 ?

```cmd
choco upgrade chocolatey
```

## 如何安装 "包" ?

```cmd
choco install firacode
```


text:
English | [Русский](https://github.com/MrFredber/FOS/blob/master/Readme%20files/ReadmeRus.md)

## About Main Branch

Stable version (22091700) is located in this branch. If you need a fresh version - move to [Dev](https://github.com/MrFredber/FOS/tree/Dev) branch.

## About system

FOS is a GUI system for mod OpenComputers, inspired by MineOS and Windows 11. Created by self-taught programmer. System have beautiful visual and small size.

![](https://raw.githubusercontent.com/MrFredber/FOS/master/Readme%20files/english2.png)
![](https://raw.githubusercontent.com/MrFredber/FOS/master/Readme%20files/english1.png)

## Minimal Requirements

	Graphic Card (Tier 3)
	1x Memory (Tier 2.5)

## How to Install

To install Stable version of FOS, you can use this command:

	mkdir /FOS/install/ && wget -f https://raw.githubusercontent.com/MrFredber/FOS/master/Install/Install-FOS.lua /FOS/install/Install-FOS.lua && /FOS/install/Install-FOS.lua

## Known issues

	The context menu should offer rational options (for example, do not suggest editing a folder)
	The item deletion dialog does not delete shortcuts and folders on the desktop, and shortcuts in Explorer

## Future plans

	Rewrite the loader
	Make installer for floppy disk
	Add a drop-down list to the system
	Add a time setting to OOBE
	Change the appearance of the Settings app and add more options
	Change the appearance of the login screen
	Add login by fingerprint

If you see a bug, create an Issue in this repository.

repository: MrFredber/FOS

gha_language: Lua

repo_name: MrFredber/FOS


text:
### [1664\. Ways to Make a Fair Array](https://leetcode.com/problems/ways-to-make-a-fair-array/)

Difficulty: **Medium**

Related Topics: [Dynamic Programming](https://leetcode.com/tag/dynamic-programming/), [Greedy](https://leetcode.com/tag/greedy/)

You are given an integer array `nums`. You can choose **exactly one** index (**0-indexed**) and remove the element. Notice that the index of the elements may change after the removal.

For example, if `nums = [6,1,7,4,1]`:

*   Choosing to remove index `1` results in `nums = [6,7,4,1]`.
*   Choosing to remove index `2` results in `nums = [6,1,4,1]`.
*   Choosing to remove index `4` results in `nums = [6,1,7,4]`.

An array is **fair** if the sum of the odd-indexed values equals the sum of the even-indexed values.

Return the _**number** of indices that you could choose such that after the removal,_ `nums`_is **fair**._

**Example 1:**

```
Input: nums = [2,1,6,4]
Output: 1
Explanation:
Remove index 0: [1,6,4] -> Even sum: 1 + 4 = 5\. Odd sum: 6\. Not fair.
Remove index 1: [2,6,4] -> Even sum: 2 + 4 = 6\. Odd sum: 6\. Fair.
Remove index 2: [2,1,4] -> Even sum: 2 + 4 = 6\. Odd sum: 1\. Not fair.
Remove index 3: [2,1,6] -> Even sum: 2 + 6 = 8\. Odd sum: 1\. Not fair.
There is 1 index that you can remove to make nums fair.
```

**Example 2:**

```
Input: nums = [1,1,1]
Output: 3
Explanation: You can remove any index and the remaining array is fair.
```

**Example 3:**

```
Input: nums = [1,2,3]
Output: 0
Explanation: You cannot make a fair array after removing any index.
```

**Constraints:**

*   `1 <= nums.length <= 10<sup>5</sup>`
*   `1 <= nums[i] <= 10<sup>4</sup>`

#### Solution

Language: **JavaScript**

```javascript
/**
 * @param {number[]} nums
 * @return {number}
 */
var waysToMakeFair = function(nums) {
    const n = nums.length
    const diffs = Array(n).fill(0)

    for (let i = 0; i < n; i += 1) {
        const prev = i - 1 >= 0 ? diffs[i - 1] : 0
        diffs[i] = prev + ((i & 1) ? -nums[i] : nums[i])
    }

    let ans = 0
    for (let i = 0; i < n; i += 1) {
        const prev = i === 0 ? 0 : diffs[i - 1]
        const next = diffs[n - 1] - diffs[i]
        if (prev === next) ans += 1
    }
    return ans
};
```


text:
---
author: Alex Singleton
layout: post
title: Alternate Crime Visualisations
categories:
- GIS
---

When the Police.UK website was launched at the beginning of 2011 a reasonable amount of criticism was levied at the choice of representation used for the online mapping of the crime data. I wrote about this briefly over at [Floating Sheep](http://www.floatingsheep.org/2011/02/problem-points-on-new-uk-police-maps.html), and indeed spoke about it one very early morning on [BBC Radio](http://www.alex-singleton.com/?p=402) - thus I won't repeat the issues. I recently received a knowledge exchange voucher from the [University of Liverpool Business Gateway](http://www.liv.ac.uk/businessgateway/), and in collaboration with our new Chair of Human Geography [Chris Brunsdon](http://www.liv.ac.uk/geography/staff/brunsdon.htm), we have begun to explore some of the representational issues of putting crimes on a map. This project was co-sponsored by the [National Police Improvement Agency](http://www.npia.police.uk/) and this post details results from the pilot project.

<!-- more -->

##Crimes and the Street Aggregation Process

Before demonstrating our pilot visualisations it is first worth detailing those procedures which are employed by the NPIA to aggregate the locations of individual crimes into a street level unit which is deemed to be suitably aggregated so as to prevent discloser. The points placed on the police.uk crime maps represent centroid locations of street segments. Individual crimes occurring on or near these centroids are aggregated and allocated to these points. The allocation of individual crimes to the points relies on a procedure which utilises Thiessen Polygons derived from the centroids of streets where there are greater than a threshold of addresses. The centroids for streets below this limit are removed in order to maintain confidentiality. Crimes are allocated to their nearest centroid - thus the centroids represent those crimes that were recorded on a collection of streets, hence the use of the label "On or Near Street X" when displaying the points on the current interactive map.

**Points**

The following map represents the point locations for crimes occurring in Merseyside during June 2011 - we have used these in our analysis as estimates of the full street network centroid locations. In reality the NPIA database includes further centroids where no crime had occurred during this month; thus this really was just a simple way in which we could generate some results quickly, however we acknowledge that ideally we should be deriving these nodes from the raw street network data. The [raw data](http://crimemapper2.s3.amazonaws.com/frontend/crime-data/2011-06/2011-06-merseyside-street.zip) were imported into MySQL (see [my previous post](http://www.alex-singleton.com/?p=433) on this subject) and the following SQL run within R to create aggregations of the crimes at the centroid locations.

```sql
`SELECT Crimetype, Location, Easting, Northing, count(*) as N from merseyside_2011_06 group by Crimetype, Location, Easting, Northing;`
```

Further manipulation in R created a single record for each centroid detailing the count of different crime types allocated to each location.

[![](https://lh5.googleusercontent.com/-avRP0-V2v9g/TjpYmXg9CKI/AAAAAAAABUY/0KF0Nsi_qWs/s144/Crimes.jpg)](https://picasaweb.google.com/lh/photo/bVCbx_BTQxvkDuNBccQc-w?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

**Thiessen Polygons Derived from the Points**

Using the street centroid locations [Thiessen Polygons](http://en.wikipedia.org/wiki/Voronoi_diagram) were derived.

[![](https://lh5.googleusercontent.com/-rgY0JidsAtw/TjpYn3s7YPI/AAAAAAAABUg/VUeuJnbeZ3M/s144/Crime_w_Thesian.jpg)](https://picasaweb.google.com/lh/photo/TWKw1Cxl2RHvfsKDjIqmtA?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

The crime data that was aggregated to each centroid location was attached to the corresponding Thiessen Polygon. Next, by overlaying the Thiessen Polygons on top of the street network data the intersection between the road network and and the new zonal geography could be derived. If a polygon boundary crossed a street segment these were divided, thus splitting the street segment into multiple parts.

[![](https://lh3.googleusercontent.com/-vdZPKsiIrCQ/TjpYo4x52NI/AAAAAAAABUk/w-6oBFLPb4I/s144/Crime_w_thesian_road.jpg)](https://picasaweb.google.com/lh/photo/ITXEleZjUAcPpwHgG73VPg?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

With the streets now allocated to a Thiessen Polygon, the crimes were attached to the road segments within these zones. As noted earlier, this will not be exactly the same allocation of streets that are feature in the NPIA database given the more limit set of centroids used to derive the Thiessen Polygon, however, these do provide a reasonable and useful proxy for visualisation experiments.

## Network Visualisations

With crimes now attached to the street network it was possible to use these as the unit of display to show either relative or absolute crimes committed. In this context we take relative rates to be the frequency of crimes / the total street length * 1000 (i.e. convert to per km) of those roads within each Thiessen Polygon. As part of the this process all individual streets within the Thiessen Polygons had to be dissolved into a single shape, otherwise, when calculating rates these appear higher on those streets (or parts of which) with shorter lengths - the data lack this precision, and as such should apply to the whole Thiessen Polygon zone.

**Coloured Networks**

The simplest visualisation option is to shade the network by colours representing the absolute or relative frequency of crimes. This takes a similar form to a choropleth map however with the units of display being the road network itself.

_Absolute_

[![](https://lh5.googleusercontent.com/-x070JFLZ0ag/TjuVWz8WFwI/AAAAAAAABWs/xxq5kkiyfS4/s400/Coloured_N.jpg)](https://picasaweb.google.com/lh/photo/rMZJeJSYrorEwCDCjFEQ-Q?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

_Relative_

[![](https://lh6.googleusercontent.com/-WY7RkqUbIiE/TjuVXwAnOKI/AAAAAAAABWw/o6i4mFTGI1U/s400/Coloured_L.jpg)](https://picasaweb.google.com/lh/photo/2FqCdjFM2ifwc324TktBQQ?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

To illustrate the earlier discussion on why the road network within each Thiessen Polygon is required to be a single shape, the following map presents the road network shaded by the relative crimes (i.e. over length). This visualisation shows variability in the relative crime rates within a Thiessen Polygon, which is created by the variable line segment lengths (i.e. denominator). This produces an artificial level of precision, and is a function of how the road network was divided, rather than the distribution of actual crimes.

[![](https://lh6.googleusercontent.com/-pg1AKpeqHM8/TjpYp3QonDI/AAAAAAAABUs/W5JzpxWwhIE/s400/LarkLane.jpg)](https://picasaweb.google.com/lh/photo/bvH5KUQgeuAiz8xosJXFQQ?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

**Scaled Networks**

An alternate visualisation to coloured networks can be created by scaling the width of the roads by relative or absolute crimes, the colour of which can be adapted to complement background cartography.

_Absolute_

[![](https://lh6.googleusercontent.com/-H4QkfzEHXAE/TjuYrtmsvZI/AAAAAAAABXs/qKyBu1oG9G0/s400/Scaled_N.jpg)](https://picasaweb.google.com/lh/photo/ZZ05IIoRVgmVx8qt0ajBig?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

_Relative_

[![](https://lh4.googleusercontent.com/-HzQMt1GyYPk/TjuYnrQqKSI/AAAAAAAABXg/Xio77YgGXg8/s400/Scaled_L.jpg)](https://picasaweb.google.com/lh/photo/raNW4GqQNKYA08RQXGJJlA?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

## Context Area

One alternative to bespoke cartography is to provide additional context to street centroid points when they are clicked. This could take a number of different forms such as the display of those roads which are allocated to the point, or, display the area defined by the Thiessen Polygon. In a live online mapping environment these would have some overhead on the system, although given their simplicity, they shouldn't have undue effect on the speed of operation.

_Road Overlay_

[![](https://lh4.googleusercontent.com/-ldiGrK8AY6s/TjpYsH3pRbI/AAAAAAAABU8/XPvyhlt8LyY/s400/RoadSelection.jpg)](https://picasaweb.google.com/lh/photo/NIMt40CNlYXnBqW1QzFp0A?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

_Thiessen Polygon Overlay_

[![](https://lh3.googleusercontent.com/-cwCQqdRIscg/TjpYrktKahI/AAAAAAAABU4/kSBBBwkxwZQ/s400/AreaSelection.jpg)](https://picasaweb.google.com/lh/photo/AC0-b_4O7R71bX3MQjfi-g?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

_Both_

[![](https://lh6.googleusercontent.com/-IXf6r-HCwAI/TjpYsuDRwhI/AAAAAAAABVA/xNEF79bjxhQ/s400/Both_Selection.jpg)](https://picasaweb.google.com/lh/photo/OFhbOSfaymOzS4PsP7qN_g?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

## Rural Areas

All the maps previously shown were of city centre locations - in the following maps relative crime rates are visualised for a more rural area located on the west side of the Wirral.

_Rural Scaled Network_

[![](https://lh3.googleusercontent.com/-AHeYONQlA2s/TjumjagGTrI/AAAAAAAABYw/7egcpAaBfKQ/s400/Rural1.jpg)](https://picasaweb.google.com/lh/photo/KTWLttey004jl0dRhsx10A?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)

_Rural Coloured Network_

[![](https://lh3.googleusercontent.com/-aJ7b1mVJ5c0/TjumjPi3sMI/AAAAAAAABYs/48gDpZwm3vg/s400/Rural2.jpg)](https://picasaweb.google.com/lh/photo/zkkIZO3QN8jXkmTy0w0YRA?feat=embedwebsite)

From [NPIA](https://picasaweb.google.com/alexandersingleton/NPIA?authuser=0&feat=embedwebsite)


text:
Markdown is a way to style text on the web. You can control the display of the document; formatting words as bold or italic, adding images, and creating lists are just a few of the things we can do with Markdown. Mostly, Markdown is just regular text with a few non-alphabetic characters thrown in, like # or \*.

(Click on "raw" to view the code.)

Headers

# This is an h1 tag

## This is an h2 tag

### This is an h3 tag

#### This is an h4 tag

##### This is an h5 tag

###### This is an h6 tag

Emphasis

_This text will be italics_

_This text will also be italics_

**This text will be bold**

**This text will be also be bold**

_You **can** combine them_

Lists

Unordered

-	Item 1
*	Item 2
	-   Item 2a
	*   Item 2b

Ordered

1. Item 1
2. Item 2
	- Item 2a
	* Item 2b

Images

![GitHub Logo](https://upload.wikimedia.org/wikipedia/commons/thumb/4/48/Markdown-mark.svg/64px-Markdown-mark.svg.png)

Links

https://github.com - automatic!

[GitHub](https://github.com)

Blockquotes

As GitHub says:

> GitHub is how people build software.
> We're supporting a community where more than 31 million people learn, share, and work together to build software as of November 2018.

Backslash Escapes

Markdown allows you to use backslash escapes to generate literal characters which would otherwise have special meaning in Markdown's formatting syntax.

\*literal asterisks\*

_literal asterisks_

Markdown provides backslash escapes for the following characters:

\ backslash

() parentheses

' backtick

\# hash mark

\* asterisk

\+ plus sign

\_ underscore

\- minus sign(hyphen)

{} curly braces

. dot

[] square brackets

! exclamation mark


text:
---
title: Recent RDO blogs, August 29, 2016
author: rbowen
date: 2016-08-29 17:36:28 UTC
tags: blog, openstack
comments: true
published: true
---

It's been a few weeks since I posted a blog update, and we've had some great posts in the meantime. Here's what RDO enthusiasts have been blogging about for the last few weeks.

**Native DHCP support in OVN** by Numan Siddique

> Recently native DHCP support has been added to OVN. In this post we will see how native DHCP is supported in OVN and how it is used by OpenStack Neutron OVN ML2 driver. The code which supports native DHCP can be found here.

... read more at [http://tm3.org/8d](http://tm3.org/8d)

**Manual validation of Cinder A/A patches** by Gorka Eguileor

> In the Cinder Midcycle I agreed to create some sort of document explaining the manual tests I’ve been doing to validate the work on Cinder’s Active-Active High Availability -as a starting point for other testers and for the automation of the tests- and writing a blog post was the most convenient way for me to do so, so here it is.

... read more at [http://tm3.org/8e](http://tm3.org/8e)

**Exploring YAQL Expressions** by Lars Kellogg-Stedman

> The Newton release of Heat adds support for a yaql intrinsic function, which allows you to evaluate yaql expressions in your Heat templates. Unfortunately, the existing yaql documentation is somewhat limited, and does not offer examples of many of yaql's more advanced features.

... read more at [http://tm3.org/8f](http://tm3.org/8f)

**Tripleo HA Federation Proof-of-Concept** by Adam Young

> Keystone has supported identity federation for several releases. I have been working on a proof-of-concept integration of identity federation in a TripleO deployment. I was able to successfully login to Horizon via WebSSO, and want to share my notes.

... read more at [http://tm3.org/8g](http://tm3.org/8g)

**TripleO Deploy Artifacts (and puppet development workflow)** by Steve Hardy

> For a while now, TripleO has supported a "DeployArtifacts" interface, aimed at making it easier to deploy modified/additional files on your overcloud, without the overhead of frequently rebuilding images.

... read more at [http://tm3.org/8h](http://tm3.org/8h)

**TripleO deep dive session #6 (Overcloud - Physical network)** by Carlos Camacho

> This is the sixth video from a series of “Deep Dive” sessions related to TripleO deployments.

... read more at [http://tm3.org/8i](http://tm3.org/8i)

**Improving QEMU security part 7: TLS support for migration** by  Daniel Berrange

> This blog is part 7 of a series I am writing about work I’ve completed over the past few releases to improve QEMU security related features.

... read more at [http://tm3.org/8j](http://tm3.org/8j)

**Running Unit Tests on Old Versions of Keystone** by Adam Young

> Just because Icehouse is EOL does not mean no one is running it. One part of my job is back-porting patches to older versions of Keystone that my Company supports.

... read more at [http://tm3.org/8k](http://tm3.org/8k)

**BAND-AID for OOM issues with TripleO manual deployments** by Carlos Camacho

> First in the Undercloud, when deploying stacks you might find that heat-engine (4 workers) takes lot of RAM, in this case for specific usage peaks can be useful to have a swap file. In order to have this swap file enabled and used by the OS execute the following instructions in the Undercloud:

... read more at [http://tm3.org/8l](http://tm3.org/8l)

**Debugging submissions errors in TripleO CI** by Carlos Camacho

> Landing upstream submissions might be hard if you are not passing all the CI jobs that try to check that your code actually works. Let’s assume that CI is working properly without any kind of infra issue or without any error introduced by mistake from other submissions. In which case, we might ending having something like:

... read more at [http://tm3.org/8m](http://tm3.org/8m)

**Ceph, TripleO and the Newton release** by Giulio Fidente

> Time to roll up some notes on the status of Ceph in TripleO. The majority of these functionalities were available in the Mitaka release too but the examples work with code from the Newton release so they might not apply identical to Mitaka.

... read more at [http://tm3.org/8n](http://tm3.org/8n)

repository: sulaimanothman/website

repo_name: sulaimanothman/website


text:
# v0.3.4 (latest release)
- Significant performance improvements when requesting suggestions *(up to 7,500% faster)*

# v0.3.3
- Document symbol provider - view top level symbols in the current file
- Workspace symbol provider - view top level symbols throughout the workspace
- Performance improvements

# v0.3.2
- **Added go to definition on classes, traits & interfaces**
- Fix several bugs introduced in v0.3.1
  - Namespace insert text should be prefixed with a backslash _(Thanks @TheColorRed for pointing out this mistake!)_
  - Crane no longer adds the fully qualified namespace to a class if the class is in the same namespace
  - Fixed issue where there were no suggestions for properties and methods defined in traits
- Disabled Crane suggestions when typing on a single line comment
- Bug report link now prefills basic information including vscode version, crane version and platform (win/linux/macos)

# v0.3.1
- **Improved namespace support**
  - Crane will now suggest scope-aware namespace parts in `namespace` and `use` statements
  - Crane will now suggest classes that have been aliased in `use` statements
  - When extending a class, Crane now only suggests classes
  - When implementing an interface, Crane now only suggest interfaces
  - Crane now doesn't suggest anything when declaring the name of a new class, trait or interface
  - Crane will now insert the fully qualified namespace of a class if there is no `use` statement for it
  - Crane now suggests non-namespaced classes after typing `\` (eg. `new \`) when inside a namespace
- Fix several bugs introduced in v0.3.0

# v0.3.0
- Updated the php-parser library to 2.0.0 stable, which **fixes nearly all crashes and parsing errors**
- Removed the Crane version indicator from the bottom right of the status bar
- Fixed a bug where the indexing statusbar item would be hidden if you disabled the bug report link

# v0.2.2
- Added new setting `crane.ignoredPaths` that gives users the ability to ignore files/folders for parsing _(workaround for parser crashing issue)_
- Added "what's new" section to readme to highlight new features/bug fixes

repository: glayzzle/crane

repo_name: glayzzle/crane


text:
# RunRhyme
RunRhyme is an app that generates a perfect playlist depending on the intensity of your run, simply log in with your Spotify account insert running distance and a running duration and subsequently playlist will be generated for you, choose songs that you like, click play and start running.

## Getting started

You need these to be able to work on the RunRhyme app; git, Node, npm, MongoDB.

Follow the instructions supplied below them or on their links to get them up and running before you continue with

## Installation

1. Clone this repo and enter!

   ```
   git clone https://github.com/JozefKysel/RunRhyme.git

   cd RunRhyme
   ```
2. Frontend.
   ```
   cd client
   npm install
   cd src
   npm start
   ```

3. Backend.
   ```
   cd server
   npm install
   nodemon index.js
   ```

Enjoy!

# TechStack
React, MongoDB (mongoose as ORM), Express

repository: JozefKysel/RunRhyme

gha_language: JavaScript

repo_name: JozefKysel/RunRhyme


text:
---
url: /services
classes: topic-page
title: Auth0 Professional Services
description: Professional Services offered by Auth0.
topics:
  - professional services
contentType:
  - index
useCase:
  - development
---

Auth0 Professional Services

    The Auth0 Professional Services portfolio consists of innovative, specialized service offerings designed to optimize customers' investments in Auth0. Professional Services help customers deploy, implement, and maintain solutions based on proven practices, avoiding common pitfalls and reducing risk.

Avoid costly security pitfalls and reduce risk

Accelerate your Auth0 deployments and reduce time to ROI

Optimize your investment in Auth0

## How Professional Services can help you with your project

### IAM solution design & architecture

Customers buy software to solve a business problem. The longer the implementation takes, the longer that business problem remains unsolved. If implementation stalls or fails, it’s a lost opportunity and a major additional cost both for you and for Auth0. Or in the worst case, it becomes an even bigger security issue or legal issue. This is why it is of the utmost importance to plan, design, and implement your IAM solution securely, effectively, and expediently. This is where Auth0 Professional Services (PS) come in.

The first step in a successful implementation is architecting your Identity and Access Management solution. We work together with your product and engineering teams to **architect an Identity solution** for your environment and build an **incremental Go-Live plan** that solves the most-pressing identity problems early. Auth0 Professional Services help your project reach success quickly and address your business objectives in a pragmatic, stepwise manner.

PS Solutions Architects have decades of combined industry expertise and Auth0-specific training. We have delivered **thousands of successful IAM projects and integrations**. Let us help you steer clear of costly security pitfalls and build a solid foundation for your identity needs, while reducing risk.

### Get to production faster

We can consolidate all the enablement activities leading to a successful adoption into three major milestones or phases:

1. Solution discovery and architecture
2. Initial Go-Live
3. Advanced Go-Live

In the discovery phase, our Solution Architects will work with your teams to identify the core goals, features, and functionality that constitute your successful IAM implementation. We will also uncover any legacy architectural issues or requirements that may need more careful consideration.

The initial Go-Live milestone is designed to be impactful enough to make material differences in the overall Identity project. At the same time, it is limited enough that it can be reached quickly—ideally within 30 days of the project start—to keep the positive momentum. The initial Go-Live typically includes migration off a legacy IDP, must-have features, and possibly a subset of all applications.

The last milestone, Advanced Go-Live, can be broken into multiple sub-milestones, especially if you have multiple applications or development teams. This helps manage the complexity of a large project and achieves incremental and steady progress.

The goal of a Professional Services engagement is to identify, document, and build consensus with you on these milestones as the path to successful Auth0 adoption.

If any part of your project requires more specialized attention and implementation assistance from an Auth0 Solution Architect, we may position additional Professional Services to help you reach that milestone.

### Accelerate your custom implementation

Auth0 is a unique service that offers developers unrivaled flexibility and extensibility. Our expert Professional Services team knows how to extend Auth0 in the ways that are most optimal for the platform and for your environment.

In addition to enablement activities, Professional Services provides **custom implementation services**.

Solutions that Professional Services can deliver to help you achieve the product functionality, service connectivity, operational readiness, and/or quality assurance you require to get to production include:

* **Custom rules, hooks, DB scripts, login pages, and email templates:** Solve a user experience, 3rd-party service integration, or other logical problem within a customer’s Auth0 authentication and authorization workflow. These customizations happen in-product and do not require additional infrastructure to deploy.

* **Custom endpoints and libraries:** Solve a service communication, user experience, or tenant management problem through the use of a custom web services endpoint or code library. Typically deployed on customer or third-party infrastructure.

* **Custom utilities:** Solve a quality assurance or operations problem that is out-of-band from extending core product functionality, such as performance testing or deployment scripts.

* **Custom code samples:** Demonstrate how a developer integrates with Auth0 using a specific language or technology stack. Used primarily for education.

### Maintain and improve your IAM solution

Once the implementation is complete, we will work with your teams to review your Identity environment, optimize and improve your solution, introduce new features, and answer any questions. To support this effort, we recommend scheduling an annual HealthCheck engagement.

For our larger customers, we also provide our post-implementation consulting service. Auth0’s “Premier Success” offering assigns a dedicated Solutions Architect to meet with your team on a weekly, bi-weekly, or monthly basis to help maintain and improve your Auth0 solution.

_We provide continuous education and knowledge transfer throughout the engagement._

## How to get Professional Services help

We provide packaged Professional Services offerings that are designed to optimize our customers' investments in Auth0 by helping design, deploy, implement, and maintain solutions based on proven practices, avoiding common pitfalls and reducing risk.

These packaged offerings generally fall into two categories: Design and Implement packages, and Maintain and Improve packages.

### Design and Implement packages

#### [Discovery Workshop](/media/articles/services/Auth0-Services-Discovery-Workshop.pdf)
* 2 days of services
* Remote/on-site, as mutually agreed
* Expires in 90 days
* Terms and Conditions apply

#### [Basic Package](/media/articles/services/Auth0-Services-Basic.pdf)
* 5 days of services
* Remote only
* Expires in 90 days
* Terms and Conditions apply

#### [Standard Package](/media/articles/services/Auth0-Services-Standard.pdf)
* 12 days of services
* Remote/on-site, as mutually agreed
* Expires in 180 days
* Terms and Conditions apply

#### [Advanced Package](/media/articles/services/Auth0-Services-Advanced.pdf)
* 25 days of services
* On-site
* Expires in 180 days
* Terms and Conditions apply

#### [Custom Implementation Package](/media/articles/services/Auth0-Services-Custom-Implementation.pdf)
* 15 or more days of services
* Remote only
* Expires in 180 days
* Terms and Conditions apply

### Maintain and Improve packages

#### [Implementation HealthCheck Package](/media/articles/services/Auth0-Services-HealthCheck.pdf)
 * 3 days of services
 * Remote/on-site, as mutually agreed
 * Expires in 365 days
 * Terms and Conditions apply

#### [Premier Success Package](/media/articles/services/Auth0-Services-Premier-Success.pdf)
* 24 days of services
* On-site
* Expires in 365 days
* Terms and Conditions apply

To get more information and to order these service offerings, please contact your Auth0 Account Representative.


text:
# v0.9.1
### Fixes
- Fix bugs involving routes.
- Fix `react-retina-image` version.

# v0.9.0
### Updates
- Update all dependencies, including React to 16.0.0

# v0.8.0
### Features
- Add Jest
- Add React Retina

### Updates
- Update React to v15.6.2

# v0.7.1
### Updates
- Update deprecated Redux Saga functions.

# v0.7.0
### Features
- Change env files to improve deployments.

# v0.6.0
### Features
- Add Sass Lint
- Refactor application styles
- Turn whole application responsive

# v0.5.0
### Features
- Add [Redux Persist](https://github.com/rt2zz/redux-persist)
- Add [React Intl](https://github.com/yahoo/react-intl)

### Fixes
- Fix production builds with development flag #1

# v0.4.0
### Features
- Update Webpack from v1 to v2, since v1 is now deprecated.
- Update React from v15.4.2 to v15.5.3 * This release has a critical bug.
- Add favicons.
- Add title to all pages.

repository: vitor-mariano/react-fission

repo_name: vitor-mariano/react-fission


text:
# Advanced

**Further information will come soon.**

The repository internally uses the [OpenStreetMap History Database](https://github.com/giscience/oshdb).

### REST API

When the server has started, you can examine the measure by clicking on the <i class="fas fa-cloud-download"/>-symbol.  Enjoy!

### ISEA 3H Discrete Global Grid System

the data is aggregated by a grid, advantages

**Further information will come soon.**

### Develop visualizations

[geogrid.js](https://github.com/mocnik-science/geogrid.js)

Data format is described in the readme of [Measures REST](https://github.com/giscience/measures-rest), the software that runs the REST server.

### Further information

Further information about the software used for this project can be found in the readme of the [OSM Measure Repository](https://github.com/giscience/osm-measure-repository)

repository: GIScience/measures-rest-oshdb-app

repo_name: GIScience/measures-rest-oshdb-app


text:
# XSD - Validator

## Introduction

This documentation will give you an overview of the XSD Validator component and will help you use it.

### Overview

The scope of the XSD validator is to validate a supplied XML (in Base64 format) against an XSD. XSDs with includes are supported. All XSDs are to be stored in the Azure Storage Container **xsdvalidatorstore**.

## Input

As an input, the XML in Base64 format (**content**) and the name of the XSD file (**xsdName**) need to be supplied as follows:

`{
	"content": "PD94bWwgdmVyc2lvbiA9ICIxLjAiPz4KPGNsYXNzPiAgCiAg...",
    "xsdName": "valid-sample.xsd"
}`

When setting up your Logic App, the HttpRequest is to be setup as follows:

![Http Request](../../images/xsd-validator-httprequest.png)

The request is then followed by the execution of the function **ValidateXmlAgainstXsd** as follows:

![ValidateXmlAgainstXsd Function](../../images/xsd-validator-validatexmlagainstxsdfunction.png)

## Output

After the XML is validated against the XSD, the result for a successful validation is returned with **IsValid** as true, with no **Exceptions** as follows:

`{
    "IsValid": true,
    "Exceptions": []
}`

If the validation is unsuccessful, the output is returned with **IsValid** as false, together with a list of **Exceptions** as follows:

`{
    "IsValid": false,
    "Exceptions": [
        {
            "message": "The element 'student' has invalid child element 'lastname'. List of possible elements expected: 'firstname'."
        }
    ]
}`

The response to the function **ValidateXmlAgainstXsd** is to be setup as follows:

![Http Response](../../images/xsd-validator-httpresponse.png)

repository: invictus-integration/docs-ifa

repo_name: invictus-integration/docs-ifa


text:
# oniongen
Deep Web .onion URL Generator

## About
**oniongen** is a small cli tool that generates and validates .onion urls.

## Installation
You can get the lastest version by clonning this repository:
```shell
git clone https://github.com/k11dd00/oniongen
cd oniongen && sudo pip install -r requirements.txt
```

## Usage
```shell
python oniongen.py <options> url
```
The oniongen cli takes one positional argument(url) that represents an url:
```shell
python oniongen.py --validate "http://3g2upl4pq6kufc4m.onion/"
```

See the options overview:

Short opt | Long opt | Default | Required | Description
--------- | -------- | ------- | -------- | -----------
-h        | --help        | None      | No  | shows the help usage
-c        | --count       | 100       | Yes | the number of urls to generate
-p        | --prefix      | None      | No  | the url prefix
-s        | --suffix      | None      | No  | the url suffix
-w        | --workers     | 100       | Yes | the number of url validation workers
-g        | --generate    | True      | No  | generates random .onion urls
-i        | --input       | None      | No  | the url list file
-o        | --output      | None      | No  | the output file
N/A       | --protocol    | http      | No  | the protocol(http or https)
N/A       | --tld         | .onion    | No  | the top level domain
N/A       | --validate    | False     | No  | validates the given url
N/A       | --discover    | False     | No  | enables the discover mode
N/A       | --proxy-ip    | <IP_ADDRESS> | Yes | the Tor proxy ip
N/A       | --proxy-port  | 9050      | Yes | the Tor proxy port
N/A       | --dry-run     | False     | No  | disables proxy and url validation
N/A       | --version     | None      | No  | shows the current version

## Validating .onion URLs

```shell
python oniongen.py --validate "http://3g2upl4pq6kufc4m.onion/"

             <ONIONGEN>
    Deep Web .onion URL Generator

                        [k1dd00]
                          v1.0.0

[+] Setting up proxy config
[+] Proxy IP:   <IP_ADDRESS>
[+] Proxy PORT: 9050
[+] Checking Tor Status
[+] Tor Status: READY
[+] Checking IP Address
[+] IP: <IP_ADDRESS>
[+] Running HTTP status check in 1 url(s)
[+] Be patient, this may take a looooong time...
[+] Found: DuckDuckGo Search Engine | http://3g2upl4pq6kufc4m.onion/
[+] Found 1 of 1 urls
```
### Validating .onion URLs Using Files as Input/Output
```shell
python oniongen.py --validate -i urls.txt -o active_urls.txt

             <ONIONGEN>
    Deep Web .onion URL Generator

                        [k1dd00]
                          v1.0.0

[+] Setting up proxy config
[+] Proxy IP:   <IP_ADDRESS>
[+] Proxy PORT: 9050
[+] Checking Tor Status
[+] Tor Status: READY
[+] Checking IP Address
[+] IP: <IP_ADDRESS>
[+] Running HTTP status check in 3 url(s)
[+] Be patient, this may take a looooong time...
[+] Found: TORCH: Tor Search! | http://xmh57jrzrnw6insl.onion
[+] Found: DuckDuckGo Search Engine | https://3g2upl4pq6kufc4m.onion/
[+] Found: DuckDuckGo Search Engine | http://3g2upl4pq6kufc4m.onion/
[+] Found 3 of 3 urls
```

## Generating Random .onion URLs

```shell
python oniongen.py -g
```

To change the default parameters:

```shell
python oniongen.py -g -c 10 -p parasite -s abc -w 10
```

## The "discover" mode

The discover mode keeps the script running until it finds the given number of urls.
```shell
python oniongen.py --discover -c 10
```

## Piped Input

You can pipe a list of urls to be validated:
```shell
cat urls.txt | python oniongen.py --validate
```

## Piped Output

The output can also be piped:
```shell
cat urls.txt | python oniongen.py --validate > active_urls.txt
```

## License
This is an open-source software licensed under the [MIT license](https://opensource.org/licenses/MIT).


text:
## Download YouTube Videos as MP4: Changelog

##### 1.8.8 (2016-09-02)
* removed outdated formats
* fixed manifest parsing (thanks, Elite2016)

##### 1.8.7 (2016-03-19)
* [only for the script and the Firefox extension]
* replacing a function that's supposedly deprecated in Firefox 48 (thanks, Leo)

##### 1.8.6 (2016-01-18)
* [only for the script, not the extensions]
* fixes Tampermonkey cross-origin issues (thanks, Giusy)

##### 1.8.5 (2015-12-19)
* signature bug fix
* improved format detection

##### 1.8.4 (2015-11-10)
* fixed signature detection (thanks, everyone)

##### 1.8.3 (2015-05-17)
* bug fix for experimental YouTube SPF - thanks, Alexandru

##### 1.8.2 (2015-05-14)
* bug fix for blocked or removed videos - thanks, Сергей
* DASH bug fixes

##### 1.8.1 (2015-03-19)
* [Firefox extension] Added support for electrolysis (e10s) - https://wiki.mozilla.org/Electrolysis
* [Firefox extension] Dropped support for Firefox 19 and earlier (e10s required a major code rewrite)
* Traditional Chinese translation - thanks, Tse Kit Yam
* Bug fixes

##### 1.7.31 (2015-01-30)
* fixes download issues

##### 1.7.30 (2014-11-14)
* fixes signature detection (thanks, everyone)

##### 1.7.29 (2014-11-01)
* fixes broken download URLs
* fixes video detection in Firefox 35+ (thanks, Nicolas)

##### 1.7.28 (2014-09-17)
* fixes missing like numbers

##### 1.7.27 (2014-09-15)
* brings back support for the old YouTube UI

##### 1.7.26 (2014-09-03)
* added download icon and improved button integration

##### 1.7.25 (2014-08-12)
* fix for signatures poorly detected by previous versions

##### 1.7.24
* bug fix for signature detection

##### 1.7.23
* Force refresh incorrect signatures
* Better signature detection
* Improved debugging information

##### 1.7.22
* bug fix for signature detection (thanks, jfurg26)

##### 1.7.21
* support for YouTube's latest UI experiment (thanks, David Book)

##### 1.7.19
* bug fix for signature detection

##### 1.7.18
* Korean translation (thanks, daunmore - http://userscripts.org/topics/147092)
* improved URL matching
* better file size detection
* Dash improvements:
 * setting for enabling Dash formats (if you use Scriptish in Firefox or the standalone Firefox extension, go to about:config, search for download-youtube-dash-enabled and change the value to 1. To disable Dash items, change the value to 0.)
 * 256kbps Dash audio is back (thanks, Lunboks - http://userscripts.org/topics/135892)
 * added support for 1440p Dash videos
 * replaced 4K labeling with 2160p

##### 1.7.17
* AJAX support for channels
* dropped file size styling

##### 1.7.15
* added file size next to each download option
* bug fixes

##### 1.7.14
* removed 480p FLV, 1080p MP4, 4K MP4. They're no longer available.

##### 1.7.13
* signature bug fix

##### 1.7.12
* brings back support for 480p FLV, 1080p MP4, 4K MP4.
Thanks, Xytras, Morten79, toejam119, ReadALot, Denisk, Tupring, milkywaif, funkinlesson and FlashGot devs.

##### 1.7.10
* fixes for the AJAX interface in Chrome

##### 1.7.9
* added low-quality FLV fallback - the 240p FLV option is added if no other FLV download URL is available
* the script now works when cookies are disabled (thanks, soft475u - http://userscripts.org/users/529340)

##### 1.7.8
* dropped Feather support
* fix for the "share buttons" experiment - https://plus.google.com/111166827982420581810/p...

##### 1.7.7
* using the GreaseMonkey API to store signature data (thanks, Eric - http://userscripts.org/topics/129461)
* inline signature update
* Indonesian translation (thanks, http://userscripts.org/users/bayuah)

##### 1.7.6
* updated Ajax support

##### 1.7.3, 1.7.5
* restored some features from 1.7

##### 1.7.2
* back to 1.6.3
* fixed signature obfuscation

##### 1.7
* fixed signature obfuscation (Firefox/Chrome)
* better support for the AJAX experiment

##### 1.6.3
* added support for Hindi (thanks, Arpit Kumar)
* fixed signature obfuscation

##### 1.6
* supports the new experimental Ajax interface
http://googlesystem.blogspot.com/2013/05/youtub...
* workaround for Chrome's unsafeWindow bug fix

##### 1.5.18
* fixed the same old signature obfuscation

##### 1.5.17
* removed the Chrome workaround for unsafeWindow (thanks, ngyikp - http://userscripts.org/topics/127453)

##### 1.5.16
* added Turkish translation (thanks, fader ed - http://userscripts.org/users/240701)
* cosmetic fixes for non-English interfaces
* more bug fixes

##### 1.5.10-15
* keeping up with YouTube's experiments for the signature parameter

##### 1.5.9
* Chinese and Japanese translations (thanks, SiwyPL and JayXon - http://userscripts.org/users/420869)
* bug fix for encrypted signatures

##### <IP_ADDRESS>
* fix for obtaining video information

##### <IP_ADDRESS>
* keeping up with YouTube's experiments for the signature parameter

##### 1.5.7
* Polish translation (thanks, SiwyPL)
* keeping up with YouTube's experiments for the signature parameter

##### 1.5.4-1.5.6
* more bug fixes for the blank download page (YouTube experiments with new signature formats)

##### 1.5.3
* bug fix for blank download page (thanks, Caroline)

##### 1.5.1
* Feather support - http://www.youtube.com/feather_beta (thanks, Joe)
* removed FLV 240p

##### 1.5
* faster video info detection
* Czech translation (thanks, Baegus - http://userscripts.org/users/495526)
* fixed unsafewindow hack in Chrome

##### 1.4.15
* removed black border around the download button

##### 1.4.14
* new debugging mode - http://userscripts.org/topics/120920

##### 1.4.12
* fixed download button placement for non-English interfaces
* added support for debugging - http://userscripts.org/topics/120920
* dropped support for the old YouTube interface

##### 1.4.10
* new interface tweaks (YouTube constantly tests new versions of the "watch7" UI)

##### 1.4.9
* fixed button position in the experimental YouTube interface (VISITOR_INFO1_LIVE=vSPn-CmshUU)

##### 1.4.8
* fixed button position in the experimental YouTube interface (VISITOR_INFO1_LIVE=wyVhs9Df-0E)

##### 1.4.7
* fixed code for the HTML5 player

##### 1.4.6
* fixed bug that showed a blank page when downloading videos (thanks, hnch - http://userscripts.org/topics/115665)
* language translation: Brazilian Portuguese (thanks, Paulo)

##### 1.4.5
* added Italian and Russian translation (thanks, Pietrodn and iHastr - http://userscripts.org/topics/102662)
* fixed parameter validation

##### 1.4.4
* bug fixes

##### 1.4.3
* initial support for the new YouTube interface that's currently tested. It's not clear if placing the button next to the like/unlike buttons is the right way, but it removes an extra click.

##### 1.4.2
* new video version: WebM 1080p (disabled by default, can be enabled by editing the code and replacing 'webm':'none' with 'webm':'all' ). Thanks, liadb - http://userscripts.org/topics/113027 .

##### 1.4.1
* fixed UI bug (misplaced arrow)

##### 1.4
* messages are translated in French, German, Spanish, Arabic and Romanian (thanks, Ibrahim - http://userscripts.org/topics/102662)

##### 1.3.9
* simplified code for obtaining video title (thanks, Lunboks)

##### 1.3.8
* updated CSS code (thanks, Fanel89 and TLUL http://userscripts.org/topics/97909)

##### 1.3.6
* removed Cosmic Panda support
* better validation for video URLs (thanks, Lunboks)

##### 1.3.5
* Cosmic Panda bug fix for videos with transcripts

##### 1.3.4
* bug fix for videos that can't be downloaded because YouTube uses encrypted streams (thanks, pooprscooper)

##### 1.3.3
* auto-update and update checking support for Scriptish
* update checking support for Greasemonkey 0.9.12+ (see the blog post)
* bug fix for video titles

##### 1.3.2
* more flexible code for selecting formats (now you can easily edit the code, change a setting and add WebM videos or remove FLV videos)
* bug fixes

##### 1.3.1
* visual tweaks for the download button

##### 1.3
* bug fixes, faster code

##### 1.2.5
* fixed code (thanks, TLUL - http://userscripts.org/scripts/show/109103 )

##### 1.2.3
* support for Cosmic Panda (http://www.youtube.com/cosmicpanda)

##### 1.2.2
* fixed video title

##### 1.2.1
* updated workarounds for YouTube's international versions

##### 1.2
* fixed two important bugs
* better performance for both the Flash player and the HTML5 player

##### 1.1.9
* fixed broken download URLs (YouTube changed the code and started to use Unicode values for ampersands)

##### 1.1.7
* using data URI for script icon, which is now smaller

##### 1.1.6
* simplified code (removed support for Ajax pages, missing FMT18 URLs)
* script icon (requires Greasemonkey 0.9+ or Scriptish)

##### 1.1.3
* tooltip adjustment

##### 1.1.2
* tweaks for YouTube's latest UI changes

##### 1.1.1
* support for https://www.youtube.com (partially secure YouTube pages)

##### 1.1
* HTML5 player support in Google Chrome

##### 1.0.9
* UI tweaks (YouTube changed the interface)

##### 1.0.8
* adjustments for localized interfaces

##### 1.0.6
* added support for the HTML5 player:
 * only works in Opera 10.6+, Firefox 4 beta (unfortunately, Greasemonkey doesn't support Firefox 4, but you might try this unofficial version)
 * links to WebM videos aren't included (in Firefox, you can right-click on the video and download the WebM file)

##### 1.0.5
* fixed MP4 360p links (the proper filename is displayed when you right-click and select "save link as")

##### 1.0.4
* fixed MP4 360p

##### 1.0.3
* removed MP4 360p (YouTube returns error 404)
* better support for non-English interfaces

##### 1.0.1
* support for YouTube's AJAX watch pages (only in Firefox and Opera)

##### 1.0
* important parts of the script have been rewritten for the Firefox extension: https://addons.mozilla.org/en-US/firefox/addon/...

##### 0.9973
* added support for 4K videos: http://youtube-global.blogspot.com/2010/07/what...

##### 0.9972
* menu items are now links (that means you can right-click and select "save target as" to change the filename before saving the file). This feature doesn't work in Internet Explorer/IE7Pro.

##### 0.9971
* fix for a small layout change

##### 0.9962
* fix for adding the download button even if there's no flagging button

##### 0.9961
* encode a few characters in the title

##### 0.996
* filenames can now include quotes
* detect broken standard MP4 URLs (only if you use Firefox/Greasemonkey or Chrome)

##### 0.9951
* replace the standard function for simulating a click with a script injection because it doesn't work in Chrome

##### 0.995
* obtain the final redirect URL for standard MP4s, so you'll no longer see video.mp4 in the filename (only if you use Greasemonkey)
* add a standard function for simulating clicks

##### 0.9945
* removed "YouTube -" from filenames
* add the highest-quality FLV file to the download list

##### 0.9944
* add the download button even if there's no flagging button

##### 0.9943
* faster parameter detection

##### 0.9942
* removing more characters from the filename

##### 0.9941
* workaround for FlashBlock

##### 0.994
* simplified code

##### 0.993
* add fake click for the download button to fix a bug

##### 0.992
* included HQ FLV format

##### 0.991
* fix code for adding the download button

##### 0.99
* new code for YouTube's updated interface (April 2010)

##### 0.98
* updated code for Chrome compatibility

##### 0.97
* fallback algorithm for detecting parameters

##### 0.95
* better HD detection

##### 0.9
* fix for YouTube code changes

##### 0.8
* a better way to get parameters

##### 0.7
* HD detection

##### 0.6
* message rewording

##### 0.5
* initial version

repository: joeytwiddle/downloadyoutube

repo_name: joeytwiddle/downloadyoutube


text:
# sonarwhal's recommended progressive web apps configuration (`@sonarwhal/configuration-progressive-web-apps`)

This packages is a `sonarwhal`'s configuration package to use for
checking progressive web apps (PWAs).

This package will automatically install all the missing dependencies.

To use it you will have to install it via `npm`:

```bash
npm install @sonarwhal/configuration-progressive-web-apps
```

Note: You can make `npm` install it as a `devDependency` using the
`--save-dev` parameter, or to install it globally, you can use the
`-g` parameter. For other options see [`npm`'s
documentation](https://docs.npmjs.com/cli/install).

The minimum required [`.sonarwhalrc`][sonarwhalrc] file to use it is
the following:

```json
{
    "extends": ["progressive-web-apps"]
}
```

and it will be as if you had this:

```json
{
    "connector": {
        "name": "jsdom",
        "options": {
            "waitFor": 5000
        }
    },
    "formatters": [
        "summary"
    ],
    "parsers": [
        "manifest"
    ],
    "rules": {
        "apple-touch-icons": "error",
        "manifest-app-name": "error",
        "manifest-exists": "error",
        "manifest-file-extension": "error",
        "manifest-is-valid": "error"
    },
    "rulesTimeout": 120000
}
```

If you prefer to use another formatter (or any other rule/connector,
etc.) you can do something like:

```json
{
    "extends": ["progressive-web-apps"],
    "formatters": ["codeframe"]
}
```

<!-- Link labels: -->

[sonarwhalrc]: https://sonarwhal.com/docs/user-guide/further-configuration/sonarwhalrc-formats/

repository: Munter/sonarwhal

repo_name: Munter/sonarwhal


text:
# PullPageControl

## Why use PullPageControl?

Pull to refresh and infinity scroll is a standart in development industry for ios mobile plathorm.
Apple provide default component for pull to refresh - `UIRefreshControl`. But it is boring and ugly.

## How to install

You can install via `cocoapods` with using special source:
```javascript
source 'https://github.com/DimaAvvakumov/Specs'

pod 'PullPageControl'
```

## How to use

1. Object of class `PullPageControl` response for control
 - It interact with `UIScrollView` or `UITableView`
 - Observed for contentOffset
 - It has 3 common state (normal, refresh, pageLoading)
 - Control can generate (triggered) two events: "start refreshing" and "load next page",
   ❗But, for the switch between states response UIViewController or ViewModel (based on architect)

2. Let's configure one time for the project:
```swift
extension PullPageControl {

    class func standart(scrollView:UIScrollView) -> PullPageControl {
        let control = PullPageControl(scrollView: scrollView)

        // refresh
        let refreshView = ProgressCircleView(frame: CGRect(x: 0.0, y: 0.0, width: 32.0, height: 32.0))
        control.refreshView = refreshView

        return control
    }

}
```

3. Next, simple connect to UIViewController:
```swift
class ViewController: UIViewController {

    // Outlets
    @IBOutlet var tableView: UITableView!

    // Pull Refresh
    var pullPageControl: PullPageControl!

    // MARK:- Life circle
    override func viewDidLoad() {
        super.viewDidLoad()

        pullPageControl = PullPageControl.standart(scrollView: tableView)
        pullPageControl.setup()
    }

}
```

4. Then, start to observed for events...
```swift
    pullPageControl.refreshEvent.asObservable().subscribe(onNext: { [weak self] (event) in
        // send signal to ViewModel
    }).disposed(by: bag)
```

5. ...and send switch state commands
```swift
    pullPageControl.state.accept( .refreshing )
```

repository: DimaAvvakumov/PullPageControl

repo_name: DimaAvvakumov/PullPageControl


text:
# ansible-role-bastille
Ansible role for bastille containers in Freebsd.

## Usages
```
$ cat bastille.yml
---
# This role will install bastille pkg, template,
# create some bastille containers.
# Then in those containers it will install some templates.
- hosts: localhost
  become: yes
  gather_facts: yes

  tasks:
    - import_role:
        name: ansible-role-bastille
$
```


text:
## [0.0.3](https://github.com/wzr1337/viwiServer/compare/0.0.2...v0.0.3) (2017-03-17)

### Bug Fixes

* **main:** port respect ([8bf14ce](https://github.com/wzr1337/viwiServer/commit/8bf14ce))
* **package:** add missing dependencies ([12c296b](https://github.com/wzr1337/viwiServer/commit/12c296b))
* **test:** use the new options object to spin up a server (no port collision with a running server) ([76fc722](https://github.com/wzr1337/viwiServer/commit/76fc722))
* send initial data message on new subscription to resources ([52c2c5b](https://github.com/wzr1337/viwiServer/commit/52c2c5b))

### Features

* **cli:** move cli stuff to cli ([3c60840](https://github.com/wzr1337/viwiServer/commit/3c60840))
* **docker:** add a Dockerfile and nam build task ([1324214](https://github.com/wzr1337/viwiServer/commit/1324214))
* **general:** options can be given with the run() command ([0928644](https://github.com/wzr1337/viwiServer/commit/0928644))
* **helpers:** move reusable code to helpers ([dbd9644](https://github.com/wzr1337/viwiServer/commit/dbd9644))
* **port:** port argument used ([5b418c1](https://github.com/wzr1337/viwiServer/commit/5b418c1))
* **server:** return Location header on creation of new elements ([a18800c](https://github.com/wzr1337/viwiServer/commit/a18800c))
* **types:** add xObject ([da57537](https://github.com/wzr1337/viwiServer/commit/da57537))
* **viwiWebSocket:** report event name on errors on the WebSocket channel ([6421064](https://github.com/wzr1337/viwiServer/commit/6421064))

## [0.0.2](https://github.com/wzr1337/viwiServer/compare/1ede568...0.0.2) (2017-03-04)

### Bug Fixes

* **main:** compare lowercase names for subscription ([da3e9f7](https://github.com/wzr1337/viwiServer/commit/da3e9f7))
* **main:** fix signature of serviceGET, doe snot need resource ([09d2140](https://github.com/wzr1337/viwiServer/commit/09d2140))
* **main:** fixes toString() of undefined bug for numeric check ([bb17c6c](https://github.com/wzr1337/viwiServer/commit/bb17c6c))
* **main:** unsubscribe working now ([6828af8](https://github.com/wzr1337/viwiServer/commit/6828af8))
* **subscriptions:** clients can unsubscribe separately ([8403354](https://github.com/wzr1337/viwiServer/commit/8403354))
* **websocket:** handle unssubscriptions and websocket breakdowns ([ae35000](https://github.com/wzr1337/viwiServer/commit/ae35000))

### Features

* **$fields:** add support for $fields on GET element queries ([6987ec2](https://github.com/wzr1337/viwiServer/commit/6987ec2))
* **buildchain:** add clean task ([54d6214](https://github.com/wzr1337/viwiServer/commit/54d6214))
* **compression:** add compression ([fd27962](https://github.com/wzr1337/viwiServer/commit/fd27962))
* **cors:** add cors relsoves #6 ([ea5208a](https://github.com/wzr1337/viwiServer/commit/ea5208a))
* **gulp:** add build task ([fee97d8](https://github.com/wzr1337/viwiServer/commit/fee97d8))
* **index:** add service listing, require service id ([4710047](https://github.com/wzr1337/viwiServer/commit/4710047))
* **logging:** add winston logger ([f4f9b43](https://github.com/wzr1337/viwiServer/commit/f4f9b43))
* **logginig:** unify query logging ([0ebf137](https://github.com/wzr1337/viwiServer/commit/0ebf137))
* **main:** add basic subscription capabilities ([1ede568](https://github.com/wzr1337/viwiServer/commit/1ede568))
* **main:** add unscubscribe feature on a per-event basis ([86ffc63](https://github.com/wzr1337/viwiServer/commit/86ffc63))
* **main:** respond with message on 500 error ([0042009](https://github.com/wzr1337/viwiServer/commit/0042009))
* add resource POSt for colletctions ([79e491d](https://github.com/wzr1337/viwiServer/commit/79e491d))
* prepare for easier subscription handling for updatelimit and changedetection ([96ccf9c](https://github.com/wzr1337/viwiServer/commit/96ccf9c))
* **plugin:** prepare subscriptions on resource level ([d3b51c4](https://github.com/wzr1337/viwiServer/commit/d3b51c4))
* **plugins:** add initial plugin loader mechanism ([923b554](https://github.com/wzr1337/viwiServer/commit/923b554))
* **plugins:** moved all REST calls into plugin, Subscriptions to follow ([7968d88](https://github.com/wzr1337/viwiServer/commit/7968d88))
* **resource subscriptions:** add resource subscription (no filters or paging yet) ([350cfa8](https://github.com/wzr1337/viwiServer/commit/350cfa8))
* **test:** add initial tests ([cc39fc3](https://github.com/wzr1337/viwiServer/commit/cc39fc3))

repository: Luennemann/viwiServer

repo_name: Luennemann/viwiServer


text:
# krusty-pizza-joint

pizza ordering and delivery website.

# Author

sawe-daisy
<EMAIL_ADDRESS>
## live link

## Description

Krusty-pizza-joint
pizza order and delivery place.
different pizza sizes, crust and toppings.
delivery at a small fee.

## Screenshot

## Setup instruction

- Open Terminal

- git clone ``

- cd krusty-pizza-joint

- code . or atom . based on the text editor you have.

## Technologies Used

- HTML5
- CSS
- JavaScript
  -jquery
- markdown
- Bootstrap

## BDD

## Contact Information

If you have any question or contributions, please email me at<EMAIL_ADDRESS>
## License

[MIT](https://github.com/sawe-daisy/krusty-pizza-joint/blob/master/LICENSE)

Copyright (c) 2020 **sawe-daisy**

repository: sawe-daisy/krusty-pizza-joint

repo_name: sawe-daisy/krusty-pizza-joint


text:
# Search

Search is a HTML5, CSS3  Project

Design a front-end for Google Search, Google Image Search, and Google Advanced Search.

Your task in this project is to expand on this site, creating your own front end for Google Search, as by exploring Google’s interface to identify what GET parameters it expects and adding the necessary HTML and CSS to your website

## Installation

Install the project locally
```bash
git clone https://github.com/SenayYakut/Search.git
```

## Usage
Go to this
https://senayyakut.github.io/Search/

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

Please make sure to update tests as appropriate.

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

repository: SenayYakut/Search

repo_name: SenayYakut/Search


text:
---
layout: post
title: "Patch-based 3D Human Pose Refinement"
date: 2019-05-20 17:51:41
categories: arXiv_CV
tags: arXiv_CV Segmentation Pose_Estimation Prediction
author: Qingfu Wan, Weichao Qiu, Alan L. Yuille
mathjax: true
---

* content
{:toc}

##### Abstract
State-of-the-art 3D human pose estimation approaches typically estimate pose from the entire RGB image in a single forward run. In this paper, we develop a post-processing step to refine 3D human pose estimation from body part patches. Using local patches as input has two advantages. First, the fine details around body parts are zoomed in to high resolution for preciser 3D pose prediction. Second, it enables the part appearance to be shared between poses to benefit rare poses. In order to acquire informative representation of patches, we explore different input modalities and validate the superiority of fusing predicted segmentation with RGB. We show that our method consistently boosts the accuracy of state-of-the-art 3D human pose methods.

##### Abstract (translated by Google)

##### URL
[http://arxiv.org/abs/1905.08231](http://arxiv.org/abs/1905.08231)

##### PDF
[http://arxiv.org/pdf/1905.08231](http://arxiv.org/pdf/1905.08231)


text:
Dictionary
==========

A programm to manage vocabularies for conlangs.

Installation
------------

Download the latest release [here](https://github.com/DoctorAlpaca/dictionary/releases). Make sure you have Java version 7 or later installed and open the .jar file. Alternativly compile the program for yourself.

Compiling it yourself
---------------------

This project uses Apache Maven to build. If you have Maven installed it should be as easy as using `$ mvn install` in the project directory.

repository: DoctorAlpaca/dictionary

gha_language: Java

repo_name: DoctorAlpaca/dictionary


text:
# Grand Piano

Grand Piano is a MIDI keyboard for feet, not fingers.
It is designed to be an interactive and intuitive music-making experience.

The keyboard uses force sensors and foam under each key,
allowing for a small amount of travel.
Each key lights up when pressed.
It can interface with a wide range of software, such as the included
web-based visualizer designed to be displayed on a large video wall
to provide extra feedback and interaction with users.

Compared to a typical piano, it is at roughly 157:1 scale
and only has one complete octave due to size constraints.
More octaves could theoretically be daisy chained together via MIDI
to create a full keyboard.

repository: Seledrex/Grand-Piano

repo_name: Seledrex/Grand-Piano


text:
---
parent: Administrator
version: 4.4
---

# Operator-defined Installation Namespace

Operator bundles can define what namespace they should be installed to, so that namespace is recommended as the default to the user. The user can still change the installation namespace if desired.

This design is now surfacing both the watch (availability) namespace and the install namespaces to the user. The installed namespace is initially read-only and defaults to **openshift-operators** when the availability namespace is **all namespaces**, and defaults to the **value from watch namespace dropdown** when the availability namespace is **single** & has a namespace selected. The user has the option to **Edit** the installation namespace if desired (and the operator allows.)

This design is not intended to convey every combination of controls that is possible via operator InstallModes, that information is available via [this spreadsheet](https://docs.google.com/spreadsheets/d/19J7IEjORg4-U6nQEwQkxPwe3SJazgpobN2HFKE2rFcc/edit?folder=1y5NhdQNm8b-NeX1I0uN6PHQzhp_NJPh0#gid=0). Controls in this design will be enabled/disabled/hidden as described in the spreadsheet and as conveyed in the screens below and the existing UI’s paradigms. This design is intended to show the location of controls and the interactions between them.

This design also captures the ability to enable cluster monitoring on namespaces that are installed to and the operator requests it. This setting applies to only certain whitelisted namespaces, and the user should be warned of the implications of doing so. Operators can request monitoring be enabled on their install namespace but we will also present this option.

## Installing with no operator-defined namespace (existing behavior)

![Operator namespace not defined all](img/1-1-noDefinedNS-all.png)
- Installing an operator without a operator-defined namespace now conveys that by default the operator would be installed on the **openshift-operators** namespace with the option to **Edit**.
- Namespaces available to install to would not yet have an OperatorGroup object present configured to watch all namespaces.
- The new **Operator Namespace Availability** header will include the hint text: "The namespaces that will be able to instantiate custom resources for this operator."
- The new **Operator Install Namespace** header will include the hint text: "The namespace that this operator will be installed in."

![Operator namespace not defined single](img/1-2-noDefinedNS-single.png)
-A specific namespace may be chosen for the operator to be available to (and installed to.)

![Operator namespace not defined single](img/1-3-noDefinedNS-single.png)
-The install namespace will match the specific namespace the operator is available to, until the install namespace is manually changed.

![Operator namespace not defined single](img/1-4-noDefinedNS-single.png)
- The user can **Edit** to modify the namespace the operator is installed to.

![Operator namespace not defined single](img/1-5-noDefinedNS-single.png)
- The user manually sets an alternative namespace to install to.

![Operator namespace not defined single](img/1-6-noDefinedNS-single.png)
- Changing the availability namespace no longer has any affect on the install namespace, as it has been manually changed.

## Installing with an operator-defined namespace

![Operator namespace defined all](img/2-1-definedNS-all.png)
- When an operator-defined installation namespace exists, that namespace will be the default install namespace for the operator.
- The operator-defined namespace can be used for **all namespace** availability, or **specific namespace** availability, as the operator's InstallModes allow.
- If the user **Edit** the install namespace, the namespaces available for selection besides the operator-defined namespace would be namespaces that not yet have an OperatorGroup object present configured to watch all namespaces.

![Operator namespace defined single](img/2-2-definedNS-single.png)
- The availability of this operator is changed to **specific namespace** and the operator-defined namespace is used as the default.
- Changing the availability namespace in this case would not affect the install namespace as it is the operator-defined namespace. The only way the install namespace would be changed is if the user manually changes it.

![Operator namespace defined single](img/2-3-definedNS-single.png)
- The user chooses to **Edit** and can select a different namespace other than the operator-defined.

![Operator namespace defined single](img/2-4-definedNS-single.png)
- The user selects another install namespace.

![Operator namespace defined single](img/2-5-definedNS-single.png)
- This operator will now be installed in namespace **abc** and available to namespace **desiredNamespace**.

## When an operator-defined namespace doesn’t exist

![Operator namespace defined doesn't exist all](img/3-1-definedNSCreate-all.png)
- When an operator-defined namespace doesn't exist, the user is notified via an inline alert that it will be created when the operator is installed.
- The **Edit** control would not appear in this case so that the user is always aware of the additional alert.

![Operator namespace defined doesn't exist single](img/3-2-definedNSCreate-single.png)
- **Specific namespace** option is also supported.

## Enabling cluster monitoring on a namespace

![Operator namespace defined monitor all](img/4-1-definedNSMonitor-all.png)
- Operators can also request cluster monitoring be enabled on the namespaces they are installed on.
- This operator has a defined namespace of **openshift-desiredNamespace** and is requesting cluster monitoring be enabled on it.
- The **Edit** control would not appear in this case so that the user is always aware of the additional option.

![Operator namespace defined monitor single](img/4-2-definedNSMonitor-single.png)
- **Specific namespace** option is also supported.

![Operator namespace defined monitor single](img/4-3-definedNSMonitor-single.png)
- Cluster monitoring can only be enabled on certain namespaces. If a not supported install namespace is selected, the option is disabled.
- Supported namespaces include: openshift-* (excluding operators), kube-*, default, logging

![Operator namespace defined monitor single](img/4-4-definedNSMonitor-single.png)
- The selected namespace is not supported so the monitoring checkbox is not enabled.

![Operator namespace defined monitor single](img/4-5-definedNSMonitor-single.png)
- The selected install namespace is changed to a supported namespace and the user is able to enable cluster monitoring on it.

![Operator namespace defined doesn't exist monitor single](img/5-1-definedNSCreateMonitor-single.png)
- Monitoring can be enabled on supported namespaces that are not yet created, as well.

## Warnings and Errors

![Error desired namespace not valid](img/9-1-error-desiredGroup.png)
- If an operator-defined install namespace has different availability already associated with it, the user will recieve an error and not be able to continue installation until changing the install namespace or availability.

![Error fixed namespace not valid](img/9-2-error-fixedGroup.png)
- If an operator has a fixed watch and install namespace based on install plans and the namespace has different availability already associated with it, the user will recieve an error and not be able to continue installation until changing the namespace.


text:
# port-forward
used to forward ports

## usage
The following environment variables need to be defined

1. `REMOTE_HOST` host you want to forward to
2. `REMOTE_PORT` port on remote host to forward to

port 80 inside the container will be forwarded to the remote host and port

* use `-P` to have docker pick a random port on the host to forward
* use `-p <host_port>:80` to define a custom port to forward where `host_port` is the port on the host that needs to be forwarded

## example
the following will forward local host traffic from port 8080 to remote host <IP_ADDRESS> and port 27017
```
docker run -e REMOTE_HOST=<IP_ADDRESS> -e REMOTE_PORT=27017 -p 8080:80 port-forward
```

- docker-compose

```
version: '2'
services:
  proxy:
    image: lotosbin/port-forward:alpine
    environment:
      - REMOTE_HOST=<IP_ADDRESS>
      - REMOTE_PORT=27017
    ports:
      - "8080:80"
```

repository: lotosbin/port-forward

repo_name: lotosbin/port-forward