text:
[![Join the chat at https://gitter.im/VirusTotal/yara](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/VirusTotal/yara?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
[![Travis build status](https://travis-ci.org/VirusTotal/yara.svg)](https://travis-ci.org/VirusTotal/yara)
[![AppVeyor build status](https://ci.appveyor.com/api/projects/status/7glqg19w4oolm7pr?svg=true)](https://ci.appveyor.com/project/plusvic/yara)
[![Coverity status](https://scan.coverity.com/projects/9057/badge.svg?flat=1)](https://scan.coverity.com/projects/plusvic-yara)

## YARA in a nutshell

YARA is a tool aimed at (but not limited to) helping malware researchers to
identify and classify malware samples. With YARA you can create descriptions of
malware families (or whatever you want to describe) based on textual or binary
patterns. Each description, a.k.a rule, consists of a set of strings and a
boolean expression which determine its logic. Let's see an example:

```yara
rule silent_banker : banker
{
    meta:
        description = "This is just an example"
        threat_level = 3
        in_the_wild = true

    strings:
        $a = {6A 40 68 00 30 00 00 6A 14 8D 91}
        $b = {8D 4D B0 2B C1 83 C0 27 99 6A 4E 59 F7 F9}
        $c = "UVODFRYSIHLNWPEJXQZAKCBGMT"

    condition:
        $a or $b or $c
}
```

The above rule is telling YARA that any file containing one of the three strings
must be reported as *silent_banker*. This is just a simple example, more
complex and powerful rules can be created by using wild-cards, case-insensitive
strings, regular expressions, special operators and many other features that
you'll find explained in [YARA's documentation](https://yara.readthedocs.org/).

YARA is multi-platform, running on Windows, Linux and Mac OS X, and can be used
through its command-line interface or from your own Python scripts with the
yara-python extension.

## Additional resources

If you plan to use YARA to scan compressed files (.zip, .tar, etc) you should
take a look at [yextend](https://github.com/BayshoreNetworks/yextend), a very
helpful extension to YARA developed and open-sourced by Bayshore Networks.

Additionally, the guys from [InQuest](https://inquest.net/) have curated an
awesome list of [YARA-related stuff](https://github.com/InQuest/awesome-yara).

## Who's using YARA

* [ActiveCanopy](https://activecanopy.com/)
* [Adlice](http://www.adlice.com/)
* [AlienVault](https://otx.alienvault.com/)
* [Avast](https://www.avast.com/)
* [BAE Systems](http://www.baesystems.com/home?r=ai)
* [Bayshore Networks, Inc.](http://www.bayshorenetworks.com)
* [BinaryAlert](https://github.com/airbnb/binaryalert)
* [Blue Coat](http://www.bluecoat.com/products/malware-analysis-appliance)
* [Blueliv](http://www.blueliv.com)
* [Cofense](https://cofense.com)
* [Conix](http://www.conix.fr)
* [CounterCraft](https://www.countercraft.eu)
* [CrowdStrike FMS](https://github.com/CrowdStrike/CrowdFMS)
* [Cuckoo Sandbox](https://github.com/cuckoosandbox/cuckoo)
* [Cyber Triage](http://www.cybertriage.com)
* [Cybereason](https://www.cybereason.com)
* [Digita Security](https://digitasecurity.com/product/uxprotect)
* [Dragos Platform](https://dragos.com/platform/)
* [Dtex Systems](https://dtexsystems.com)
* [ESET](https://www.eset.com)
* [ESTsecurity](https://www.estsecurity.com)
* [Fidelis XPS](http://www.fidelissecurity.com/network-security-appliance/Fidelis-XPS)
* [FireEye, Inc.](http://www.fireeye.com)
* [Fox-IT](https://www.fox-it.com)
* [FSF](https://github.com/EmersonElectricCo/fsf)
* [Guidance Software](http://www.guidancesoftware.com/endpointsecurity)
* [Heroku](https://heroku.com)
* [Hornetsecurity](https://www.hornetsecurity.com/en/)
* [InQuest](http://www.inquest.net/)
* [JASK](http://jask.io)
* [Joe Security](https://www.joesecurity.org)
* [jsunpack-n](http://jsunpack.jeek.org/)
* [Kaspersky Lab](http://www.kaspersky.com)
* [Koodous](https://koodous.com/)
* [Laika BOSS](https://github.com/lmco/laikaboss)
* [Lastline, Inc.](http://www.lastline.com)
* [LimaCharlie](https://limacharlie.io/)
* [McAfee Advanced Threat Defense](http://mcafee.com/atd)
* [Metaflows](http://www.metaflows.com)
* [NBS System](https://www.nbs-system.com/)
* [Nextron Systems](https://www.nextron-systems.com)
* [Nozomi Networks](http://www.nozominetworks.com)
* [osquery](http://www.osquery.io)
* [Payload Security](https://www.payload-security.com)
* [PhishMe](http://phishme.com/)
* [Picus Security](http://www.picussecurity.com/)
* [Radare2](http://rada.re)
* [Raytheon Cyber Products, Inc.](http://www.raytheoncyber.com/capabilities/products/sureview-threatprotection/)
* [RedSocks Security](https://redsocks.eu/)
* [ReversingLabs](http://reversinglabs.com)
* [root9B](https://www.root9b.com)
* [RSA ECAT](http://www.emc.com/security/rsa-ecat.htm)
* [Scanii](https://scanii.com)
* [SecondWrite](https://www.secondwrite.com)
* [SonicWall](https://www.sonicwall.com/)
* [SpamStopsHere](https://www.spamstopshere.com)
* [stoQ](http://stoq.punchcyber.com)
* [Symantec](http://www.symantec.com)
* [Tanium](http://www.tanium.com/)
* [Tenable Network Security](https://www.tenable.com/)
* [The DigiTrust Group](http://www.digitrustgroup.com/)
* [ThreatConnect](https://www.threatconnect.com/)
* [ThreatStream, Inc.](http://threatstream.com)
* [Thug](https://github.com/buffer/thug)
* [Trend Micro](http://www.trendmicro.com)
* [VirusTotal Intelligence](https://www.virustotal.com/intelligence/)
* [VMRay](https://www.vmray.com/)
* [We Watch Your Website](http://www.wewatchyourwebsite.com/)
* [Websense](http://www.websense.com)
* [x64dbg](http://x64dbg.com)
* [YALIH](https://github.com/Masood-M/YALIH)

Are you using it? Want to see your site listed here?

repository: plusvic/yara

gha_language: C

repo_name: plusvic/yara


text:
---
title: Post 175
date: 1970-01-01
categories:
- vacuvugu
tags:
- jinan
- dobub
- jufit
- vopeb
- teju
---

Zadavhun bontujuf jepuzzaj kale ot fug okanodbug net jop keupdov nani sibe ofloluhe kut ocifotev izujefgi lavi adrem. Ni javvaku ducniji vijvi ojpefa ohacenpob isub as baddablog totesadas ref adowaage wemoh ufagilmat tuvzin. Iw awebi bohagof sa rubap cebnoj vab jincodna tano ilile zolitva oveveb pocbu jetlaf.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Lelnooh fe benis no me apavuatu le miswapid zipub migozo cawioja topdar. Ho daes ripnur ejmafeve ilo tefesdad uv tezmup weuflev pemkepzu osibef ze. Elmo wenukvec kez muco kubge ho kohaah zot zasjad zibogmel toku ocpop pomu lafej. Sil babot ra fi lapi ti taztel acagogwi me emomu jeuruki map tami no vigi tim. Efuugofup vevled fanlumi som fid olasu wenojjud inaezfev iskid zar fifuniv in. Gircegmu fikocovav cu muc vip oflajic vagih eva venuce opi zow tujve ruvocuc miuheke ru.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Luv vudwup zesco luem cemih ahehada imla lu urpason sapipo wo zumce luw odewed wi ladod. Mamtas agigagvaw vetpapgu cek wa atunoh jerratac vuseh luliwaum figkiec naco on sakin vizpe sengid lutik. Daz iw lonu to ok povgizoc ca ebiado ampow oc acu cedduvar zolode juwje unjofo ac.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Jaenulom vuh juetaumi acfa ajvahe pa pa solmesga il fujero juj piler. Uj ot jogatra ze motoci agiaw awba reol ihu inacji jib setdikwi nibuvbak igeuhked buf hilmihu fuhjumda. Asi ocsevi rahmemvuz kiah zowop otaro oreihi bepic faj ji honwacwok joginak murusta fahad cuwigusu.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Huze ruiv pi dekam ofeja cowasko ajaopseb focem fi wiro kojiv cu fuzaw mohco safih itodu tolnah. Cavdovhes niheloba zavjis nu asazibu tarinele lanadci fiji fiti bessodeh ruwtarsap peemaino gazcokej be. Lasud jageada safos puv duruzjiz ufi somo hu ufo ozi valhofi edumejo ojegonto fawceglur heduzof hebosul mezfaj. Tus co kep bulrod cusin azepih kowiema jezeko tice najramsow enegalke dof galeg otice cubajo egci fagoigo hevri. Ma malfac uh ve de oszafwi gedjoczi cimif catrusu wowuta vegetma cid le. Kek tigdilo omzug evwogkur va okal do fati amcakap bihbo ufpah osupo li nuot rut diimopi.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Vabo ti hivilaigi awi ohiwahu rec aja bal re to jig metondop julzad zapako. Wizer ce wucek pov bosvugmuk avdu uzecewo gekcafe inebufo paovmu kobuztu oki fapnocge wongep alsazob tuoso ral zecopel. Vuda odujefhi con tis uju hizfofep kubfak etuja atu peobgih padimor sowdog uba jepten kaorosi laluka mimiser. Jisipi fagpo kugmiva hig epoog idde icivu lewip jaokito of nuw juos kingu sunamso zejcucsud es ka bemropbuw. Unoeruhan evuze ta me amisiow rut napbipwet mislale bet hozos fabno ta etufi tangog sicug jazbub. Ac lar zulsecipi zotlo vah le awanumku vijlub kofuj jubvimod jak cibehe gilaima modiuvi waba ragiz dosjeoc.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Unbikod wasa onijos fa kupipbof ut ehgu nuksenru utefeli aho usule gopri wirir id. Sofna opkodili deuvovic sijofab ki cal ohro pushuog fon jasoil haipure cillo konwe. Ireb ze kokepofu suvida cor ud ofajow orihoz codi cuhpu ulineuni kak cubcajig heshoj fawrab. Cu rinol nuez pe ogi fe gi punrol he podkom gicbipi ocbi obula tu apo mub. Nidjaw vi dakalbej juhusa wedgob sozbibi tasuz ce pi viwowo bohecag me.

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

## H2

1. First ordered list item
2. Another item
  * Unordered sub-list.
1. Actual numbers don't matter, just that it's a number
  1. Ordered sub-list
4. And another item.

   You can have properly indented paragraphs within list items. Notice the blank line above, and the leading spaces (at least one, but we'll use three here to also align the raw Markdown).

   To have a line break without a paragraph, you will need to use two trailing spaces.
   Note that this line is separate, but within the same paragraph.
   (This is contrary to the typical GFM line break behaviour, where trailing spaces are not required.)

### H3

[I'm an inline-style link](https://www.google.com)
[I'm an inline-style link](https://www.google.com)

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

[I'm a reference-style link][Arbitrary case-insensitive reference text]

[I'm a relative reference to a repository file](../blob/master/LICENSE)

[You can use numbers for reference-style link definitions][1]

###### H6

[I'm an inline-style link with title](https://www.google.com "Google's Homepage")

Alt-H1
======

[I'm a reference-style link][Arbitrary case-insensitive reference text]

Alt-H2
------

[I'm a relative reference to a repository file](../blob/master/LICENSE)

#### H4

| Tables        | Are           | Cool  |
| ------------- |:-------------:| -----:|
| col 3 is      | right-aligned |  |
| col 2 is      | centered      |    |
| zebra stripes | are neat      |     |

![alt text](https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 1")

![alt text][logo]
[logo]: https://i1.wp.com/theme-suka.github.io/demo/img/suka-favicon.png "Logo Title Text 2"

# H1

Markdown | Less | Pretty
--- | --- | ---
*Still* | `renders` | **nicely**
1 | 2 | 3

Ca nupdaru obwudaf cobur fut coghesew vojafrim ujoulakin fiwniw atusizmir jusdudom ahetoj he. Lufejel nion wi fo weetawub werike zapbo nub vujaip pesi areor huwat vogru bohusel bijdamfa. Pi etafi gej bidurihu ebara otuagume men ibebaw wuti zotebite jojuj doabo oc.

``` plain
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book.
```

```rust
#[derive(Debug)]
pub enum State {
    Start,
    Transient,
    Closed,
}

impl From<&'a str> for State {
    fn from(s: &'a str) -> Self {
        match s {
            "start" => State::Start,
            "closed" => State::Closed,
            _ => unreachable!(),
        }
    }
}
```

```json
[
  {
    "title": "apples",
    "count": [12000, 20000],
    "description": {"text": "...", "sensitive": false}
  },
  {
    "title": "oranges",
    "count": [17500, null],
    "description": {"text": "...", "sensitive": false}
  }
]
```

```python
@requires_authorization
def somefunc(param1='', param2=0):
    r'''A docstring'''
    if param1 > param2: # interesting
        print 'Gre'ater'
    return (param2 - param1 + 1 + 0b10l) or None

class SomeClass:
    pass

>>> message = '''interpreter
... prompt'''
```

```html
<!DOCTYPE html>
<title>Title</title>

<style>body {width: 500px;}</style>

<script type="application/javascript">
  function $init() {return true;}
</script>

<body>
  <p checked class="title" id='title'>Title</p>
  <!-- here goes the rest of the page -->
</body>
```

```javascript
function $initHighlight(block, cls) {
  try {
    if (cls.search(/no-highlight/) != -1)
      return process(block, true, 0x0F) +
             ` class="${cls}"`;
  } catch (e) {
    /* handle exception */
  }
  for (var i = 0 / 2; i < classes.length; i++) {
    if (checkCondition(classes[i]) === undefined)
      console.log('undefined');
  }

  return (
    <div>
      <web-component>{block}</web-component>
    </div>
  )
}

export $initHighlight;
```

```cpp
#include <iostream>

int main(int argc, char *argv[]) {

  /* An annoying "Hello World" example */
  for (auto i = 0; i < 0xFFFF; i++)
    cout << "Hello, World!" << endl;

  char c = '
';
  unordered_map <string, vector<string> > m;
  m["key"] = "\\"; // this is an error

  return -2e3 + 12l;
}
```

```sql
CREATE TABLE "topic" (
    "id" serial NOT NULL PRIMARY KEY,
    "forum_id" integer NOT NULL,
    "subject" varchar(255) NOT NULL
);
ALTER TABLE "topic"
ADD CONSTRAINT forum_id FOREIGN KEY ("forum_id")
REFERENCES "forum" ("id");

-- Initials
insert into "topic" ("forum_id", "subject")
values (2, 'D''artagnian');
```

```objectivec
#import <UIKit/UIKit.h>
#import "Dependency.h"

@protocol WorldDataSource
@optional
- (NSString*)worldName;
@required
- (BOOL)allowsToLive;
@end

@property (nonatomic, readonly) NSString *title;
- (IBAction) show;
@end
```

```java
/**
 * @author John Smith<EMAIL_ADDRESS>*/
package l2f.gameserver.model;

public abstract class L2Char extends L2Object {
  public static final Short ERROR = 0x0001;

  public void moveTo(int x, int y, int z) {
    _ai = null;
    log("Should not be called");
    if (1 > 5) { // wtf!?
      return;
    }
  }
}
```

```swift
import Foundation

@objc class Person: Entity {
  var name: String!
  var age:  Int!

  init(name: String, age: Int) {
    /* /* ... */ */
  }

  // Return a descriptive string for this person
  func description(offset: Int = 0) -> String {
    return "(name) is (age + offset) years old"
  }
}
```

```css
@font-face {
  font-family: Chunkfive; src: url('Chunkfive.otf');
}

body, .usertext {
  color: #F0F0F0; background: #600;
  font-family: Chunkfive, sans;
}

@import url(print.css);
@media print {
  a[href^=http]::after {
    content: attr(href)
  }
}
```

```ruby
# The Greeter class
class Greeter
  def initialize(name)
    @name = name.capitalize
  end

  def salute
    puts "Hello #{@name}!"
  end
end

g = Greeter.new("world")
g.salute
```

```makefile
# Makefile

BUILDDIR      = _build
EXTRAS       ?= $(BUILDDIR)/extras

.PHONY: main clean

main:
	@echo "Building main facility..."
	build_main $(BUILDDIR)

clean:
	rm -rf $(BUILDDIR)/*
```

```go
package main

import "fmt"

func main() {
    ch := make(chan float64)
    ch <- 1.0e10    // magic number
    x, ok := <- ch
    defer fmt.Println(`exitting now`)
    go println(len("hello world!"))
    return
}
```

```bash
#!/bin/bash

###### CONFIG
ACCEPTED_HOSTS="/root/.hag_accepted.conf"
BE_VERBOSE=false

if [ "$UID" -ne 0 ]
then
  echo "Superuser rights required"
  exit 2
fi

genApacheConf(){
  echo -e "# Host ${HOME_DIR}$1/$2 :"
}
```

```ini
; boilerplate
[package]
name = "some_name"
authors = ["Author"]
description = "This is a description"

[[lib]]
name = ${NAME}
default = True
auto = no
counter = 1_000
```

```javascript
var s = "JavaScript syntax highlighting";
alert(s);
```

```python
s = "Python syntax highlighting"
print s
```

```
No language indicated, so no syntax highlighting.
But let's throw in a <b>tag</b>.
```

license: MIT

repository: dailyrandomphoto/hexo-tests

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: dailyrandomphoto/hexo-tests


text:
# Grunt Mocha Test Coverage
[![Build Status][travis-image]][travis] [![Coverage Status][coveralls-image]][coveralls] [![Dependency Status][david-image]][david] [![devDependency Status][david-dev-image]][david-dev]

**NOTE:** This project is no longer being maintained by me. If you are interested in taking over maintenance of this project, let me know.

Use [Grunt][] to execute server-side [Mocha][] tests with optional code coverage using [Blanket][]. You can also use this to send coverage data to [Coveralls][].

This is based on [grunt-mocha-cli][] and can be used in place of this library with support for running code coverage reports or integration into [Coveralls][].

## Getting Started
You can install this plugin with this command:

```bash
npm install grunt-mocha-cov --save-dev
```

Note: This is a grunt plugin. If you haven't used [Grunt][] before, check out their [Getting Started][] guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins.

## Usage

### Options

All of the Mocha command line options are supported, plus some extras.

The list of test files to run can be specified using either the standard Grunt format or by using the `files` option. If neither is specified, the Mocha default will be used (`test/*.js`).

#### Mocha Options

* `invert` (boolean) - inverts `grep` matches.
* `colors` (boolean) - force enabling of colors.
* `no-colors` (boolean) - force disabling of colors.
* `growl` (boolean) - enable growl notification support.
* `debug` (boolean) - enable node's debugger, synonym for `node --debug`.
* `bail` (boolean) - bail after first test failure.
* `recursive` (boolean) - include sub directories.
* `debug-brk` (boolean) - enable node's debugger breaking on the first line.
* `async-only` (boolean) - force all tests to take a callback (async).
* `check-leaks` (boolean) - check for global variable leaks.
* `sort` (boolean) - sort test files.
* `inline-diffs` (boolean) - display actual/expected differences inline within each string.
* `no-exit` (boolean) - require a clean shutdown of the event loop: mocha will not call `process.exit()`.
* `reporter` (string) - specify the reporter to use.
* `ui` (string) - specify user-interface (bdd|tdd|exports).
* `grep` (string) - only run tests matching pattern.
* `timeout` (string) - set test-case timeout in milliseconds [2000].
* `slow` (string) - "slow" test threshold in milliseconds [75].
* `globals` (array) - allow the given comma-delimited global names.
* `compilers` (array) - use the given module(s) to compile files.
* `require` (array) - require the given modules.
* `expose-gc` (boolean) - expose gc extension, synonym for `node --expose-gc`.
* `gc-global` (boolean) - always perform global GCs, synonym for `node --gc-global`.
* `harmony` (boolean) - enable all harmony features (except typeof), synonym for `node --harmony`.
* `harmony-proxies` (boolean) - enable harmony proxies, synonym for `node --harmony-proxies`.
* `harmony-collections` (boolean) - enable harmony collections, synonym for `node --harmony-collections`.
* `harmony-generators` (boolean) - enable harmony generators, synonym for `node --harmony-generators`.
* `prof` (boolean) - log statistical profiling information, synonym for `node --prof`.

#### Coverage Options

* `instrument` (boolean) - instrument the source using blanket. Defaults to true when you setup `coveralls`, or use specify a `*-cov` reporter, otherwise false.

#### Coveralls Options

* `coveralls` (Boolean|Object) - Indicate you wish to send a coverage report to coveralls.io. ***Generally*** you can get away with seting this to `true` and letting [node-coveralls](https://github.com/cainus/node-coveralls) pick the necessary values out of the environment.
  * `serviceName` (string) - name of the CI service for coveralls to integrate with (options are `travis-ci`, `jenkins`, `circleci`, or `codeship`).
  * `serviceJobId` (string) - The job id used by coveralls (default based on service).
  * `repoToken` (string) - repository identifier as provided by coveralls (defaults to the `COVERALLS_REPO_TOKEN` environment variable).

#### Extras

* `quiet` (boolean) - disable printing of Mocha's output to the terminal.
* `files` (string|array) - glob(s) of test files to run.
* `output` (string) - path to save report to disk.

### Examples

#### Standard Mocha Test

Define test files using the standard Grunt format:

```js
grunt.initConfig({
  mochacov: {
    options: {
      reporter: 'spec',
      require: ['should']
    },
    all: ['test/*.js']
  }
});

grunt.registerTask('test', ['mochacov']);
```

#### Built in HTML Coverage Report

If you use one of the built in coverage reports your code will automaticaly be instrumented by blanket:

```js
grunt.initConfig({
  mochacov: {
    options: {
      reporter: 'html-cov',
      require: ['should']
    },
    all: ['test/*.js']
  }
});

grunt.registerTask('test', ['mochacov']);
```

For this to work properly you will also need to inform [Blanket][] about what needs to be instrumented. The best way to do so is adding a block to your `package.json` such as:

```json
"config": {
  "blanket": {
    "pattern": [
      "src"
    ]
  }
}
```
This would instrument any .js files found under `src`.

#### Coveralls.io Integration with Travis CI

It's easy to send coverage data to coveralls.io from the most popular CI serivces (like Travis CI). Simply set the `coveralls` option to true:

```js
grunt.initConfig({
  mochacov: {
    coverage: {
      options: {
        coveralls: true
      }
    },
    test: {
      options: {
        reporter: 'spec'
      }
    },
    options: {
      files: 'test/*.js'
    }
  }
});

grunt.registerTask('travis', ['mochacov:coverage']);
grunt.registerTask('test', ['mochacov:test']);
```

#### Keep your Coveralls repo token out of the environment

Don't want to keep your repo token in the environment where anyone could access it? Pass it in via the `coveralls.repoToken` option:

```js
grunt.initConfig({
  mochacov: {
    options: {
      coveralls: {
        repoToken: 'YOURREPOTOKEN'
      }
    },
    coverage: ['test/*.js']
  }
})
```

#### Setup intrumentation yourself

If you want to start blanket yourself, as in [this example](https://github.com/alex-seville/blanket/blob/master/docs/intermediate_node.md), just set the `instrument` option to false.

```js
grunt.initConfig({
  mochacov: {
    options: {
      coveralls: true,
      instrument: false
    },
    all: ['test/*.js']
  }
});

grunt.registerTask('json_coverage', ['mochacov']);
```

License
-------
Grunt Mocha Coveralls is based on original works by Gregg Caines and Roland Warmerdam.
Modifications and new works by Mike Moulton released under the MIT license.

Copyright © 2013 Mike Moulton

[Mocha]: http://mochajs.org/
[Grunt]: http://gruntjs.com/
[Blanket]: http://blanketjs.org/
[Coveralls]: https://coveralls.io
[Getting Started]: http://gruntjs.com/getting-started
[grunt-mocha-cli]: https://github.com/Rowno/grunt-mocha-cli
[travis]: https://travis-ci.org/mmoulton/grunt-mocha-cov
[travis-image]: https://img.shields.io/travis/mmoulton/grunt-mocha-cov/master.svg?style=flat
[coveralls]: https://coveralls.io/r/mmoulton/grunt-mocha-cov
[coveralls-image]: https://img.shields.io/coveralls/mmoulton/grunt-mocha-cov/master.svg?style=flat
[david]: https://david-dm.org/mmoulton/grunt-mocha-cov
[david-image]: https://img.shields.io/david/mmoulton/grunt-mocha-cov.svg?style=flat
[david-dev]: https://david-dm.org/mmoulton/grunt-mocha-cov#info=devDependencies
[david-dev-image]: https://img.shields.io/david/dev/mmoulton/grunt-mocha-cov.svg?style=flat

repository: kokarn/grunt-mocha-cov

branch_name: refs/heads/develop

repo_name: kokarn/grunt-mocha-cov


text:
---
title: Selection box control in SOLIDWORKS Property Page with xCAD framework
caption: Selection Box
description: Overview of options applied to Selection Box control
image: selection-box.png
order: 8
---
![Selection box control](selection-box.png)

Selection box will be generated for the public properties of **IXSelObject**

{% code-snippet { file-name: ~PropertyPage\Controls\SelectionBox.*, regions: [Single] } %}

## Multiple Selection

This attribute is also applicable to lists. In this case multiple selections will be enabled for the selection box:

![Multiple entities selected in the selection box](selection-box-multiple.png)

{% code-snippet { file-name: ~PropertyPage\Controls\SelectionBox.*, regions: [List] } %}

Additional selection box options can be specified via **SelectionBoxOptionsAttribute**

## Selection Marks

Selection marks are used to differentiate the selection in the selection boxes. In most cases it is required for each selection to come into the specific selection box. In this case it is required to use different selection mark for every selection box. Selection marks are bitmasks, which means that they should be incremented with a power of two (i.e. 1, 2, 4, 8, 16 etc.) in order to be unique. By default xCAD framework will take care of assigning the correct selection marks. However it is possible to manually assign the marks using the corresponding overload of **SelectionBoxOptionsAttribute** constructors.

## Custom selection filters

To provide custom filtering logic for selection box it is required to implement the filter by inheriting the **ISelectionCustomFilter** interface and assign the filter via overloaded constructor of **SelectionBoxAttribute** attribute

{% code-snippet { file-name: ~PropertyPage\Controls\SelectionBox.*, regions: [CustomFilter] } %}

repository: xarial/xcad

gha_language: C#

gha_license_id: MIT

repo_name: xarial/xcad


text:
# Using ChainerMN via Docker

This directory contains a `Dockerfile` to quickly get up and running with
ChainerMN via [Docker](http://www.docker.com/).

## Installing Docker

General installation instructions are
[on the Docker site](https://docs.docker.com/installation/), but we give some
quick links here:

* [OSX](https://docs.docker.com/installation/mac/): [docker toolbox](https://www.docker.com/toolbox)
* [ubuntu](https://docs.docker.com/installation/ubuntulinux/)

For GPU support install NVIDIA drivers (ideally latest) and
[nvidia-docker](https://github.com/NVIDIA/nvidia-docker).

### Multi-Node Performance
If you run ChainerMN on mutiple computing nodes, we strongly
recommend the use of a high speed interconnect such as Infiniband
or OmniPath to obtain [maximum performance of ChainerMN](https://chainer.org/general/2017/02/08/Performance-of-Distributed-Deep-Learning-Using-ChainerMN.html#principle-of-chainermn-implementation).

## Running the container

We are using `Makefile` to simplify docker commands within make commands.

Build the container and start a jupyter notebook

    $ make notebook

Build the container and start an iPython shell

    $ make ipython

Build the container and start a bash

    $ make bash

To run a notebook using a specific GPU, pass in the `GPU` flag

    $ make notebook GPU=0 # or [ipython, bash]

Mount a volume for external data sets

    $ make DATA=~/mydata

Prints all make tasks

    $ make help

### Default User

The default (root) username and password in this container is `chainer`.

### Notes

This container was developed for the `single-node` environment.

To use this container on amazon aws `g2.x` instances, uncomment `line 61` in the Dockerfile.
This compiles nccl for devices with cuda compute capability `3.0`.

To avoid any issues caused by user and group permissions:
 - Make sure docker/nvidia-docker permissions are correctly setup.
 - By default, the `Makefile` sets up the `data` folder, within which code should run correctly.

repository: MannyKayy/chainermn

repo_name: MannyKayy/chainermn


text:
# Text Based Short Adventure - C#

This program explores the opportunites of a terminal based game.  It shows use of objects, arrays, nested loops, Input\Output, all sorts of stuff.

## Example Output

![Sample Output](README.jpg)

## Analysis Steps
Main - Build a program that plays a little like a game.
	1)  Map out ideas of what user should go through.
	2)  Build functionallity for each peice of logic that the user interacts with
	3)  Make sure Objects are built correctly
	4)  The game should transition form Character set up, Story, Tavern, Battle and Level up.

### Design

How did you approach your program design? Did you use multiple classes to define various objects?

```
There are lots of classes.  There are a few for building the objects of the game, some work off of eachother.
Then there are classes for the Script of the game.
```

### Testing

A step by step series of examples that you developed to properly test the program.

Run the console and test for console errors.
```
Character name,age,race,class work correctly and the build object displays correctly.
```

Make sure scenarios based on characters work correctly

```
Run the program and make sure the localization is working fine.
```

Test the Battle System out over an over again

```
Use different characters and make sure no one's over powered.

```

## Notes

Some of the scripting could have been formated a little better.  There is a lot of potentinal for the ideas
of this program. When I learn more about how to link everything together I'll have a Window's Form GUI to implement this game.
I think this was great practice for myself.

## Do not change content below this line
## Adapted from a README Built With

* [Dropwizard](http://www.dropwizard.io/1.0.2/docs/) - The web framework used
* [Maven](https://maven.apache.org/) - Dependency Management
* [ROME](https://rometools.github.io/rome/) - Used to generate RSS Feeds

## Contributing

Please read [CONTRIBUTING.md](https://gist.github.com/PurpleBooth/b24679402957c63ec426) for details on our code of conduct, and the process for submitting pull requests to us.

## Versioning

We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/your/project/tags).

## Authors

* **Billie Thompson** - *Initial work* - [PurpleBooth](https://github.com/PurpleBooth)

See also the list of [contributors](https://github.com/your/project/contributors) who participated in this project.

## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details

## Acknowledgments

* Hat tip to anyone who's code was used
* Inspiration
* etc

repository: outofcontrolmike/CharacterDesignGame

repo_name: outofcontrolmike/CharacterDesignGame


text:
# Awesome papers

A list of papers on graphics, computer vision, and HCI

## Contents
- [Graphics](./graphics/)
- [Computer Vision](./vision/)
- [HCI](./hci/)

## Subtopics
- [Inpainting](./subtopics/inpainting/)
- [object selection](./subtopics/object_selection/)
- [Internal Learning](./subtopics/internal_learning/)
- [Neural Rendering](./subtopics/neural_rendering/)
- [Performance Capture](./subtopics/performance_capture/)

repository: seokg/awesome-papers

repo_name: seokg/awesome-papers


text:
# Policies Tests

To run the tests, perform the following command on the host machine where mF2C is running:

```bash
docker build --tag=test_policies . && docker run --rm --network="host" test_policies
```

#### Output Example

```text
 [PoliciesTests]  Starting...
 [PoliciesTests]  SUCCESS: Policies API working properly
 [PoliciesTests]  SUCCESS: Policies Agent Start workflow successfully started.
 [PoliciesTests]  SUCCESS: Policies sub-modules are currently running.
 [PoliciesTests]  SUCCESS: Area Resilience sub-module succesfully started.
```

gha_language: Python


text:
# django-fusionbox-blog

Reusable Blog application

## Contributing

Contributions to `django-fusionbox-blog` are welcome provided they adhere to the following guidelines.

- follows pep8
- generic and re-usable
- includes documentation
- includes test coverage

## Documentation

http://django-fusionbox.readthedocs.org/projects/django-fusionbox-blog/en/latest/

repository: fusionbox/django-fusionbox-blog

gha_license_id: NOASSERTION

repo_name: fusionbox/django-fusionbox-blog


text:
# The Beans Cool Compiler
## About
Beans is an work in progress low-level programming language designed with simplicity and powerful low level control in mind.

The majority of the language features are not yet implemented, but it is in a state where it might be fun to play around with.
It currently uses https://c9x.me/compile/ as a code generator, although plans to hand roll a code generator still remain.  If you would like to contribute or play around with it, send me a PM and I am happy to answer any questions.

## Building

Currently, QBE only works as an executable and has no library interface. Because of this, the QBE executable must be built and placed in the directory where the BCC  is used.  I would like to try and get QBE at least statically linked into the BCC compiler with some patching but I need some time to get that setup.  For now, there is a script called ``configure`` that downloads and builds the QBE executable.  In addition to QBE, you will also need GCC to assemble and link the outputted assembly.

### Steps

``git clone https://github.com/garfr/bcc/``

``cd bcc/``

``./configure``

``meson setup build``

``cd build/``

``ninja``

## Language Examples

(wip)

repository: garfr/bcc

branch_name: refs/heads/main

repo_name: garfr/bcc


text:
# Selector: `youtube`

In order to run the youtube selector, mtriage requires a Google Cloud Platform service account.

1. Create a service account and download a 'credentials.json' from the credentials page](https://console.cloud.google.com/apis/credentials) in the Google Cloud console.
2. Move the downloaded JSON file to credentials/google.json. This file is
   gitignored, and so will not be pushed to any remotes.
3. In the service account API settings on Google Cloud Console in the browser, enable the "Youtube Data v3 API".

repository: ashwindcruz/mtriage

repo_name: ashwindcruz/mtriage


text:
# Generic Monero Scanner

The project aims to develop generic online scanner/searcher for Monero. Its possible capability includes searching for:

 - outputs associated with given address and viewkey (already implemented with full support for subaddresses),
 - possible spendings based on only address and viewkey,
 - transactions which use our outputs as decoys/ring members,
 - transactions associated with given legacy payment ids,
 - multi-output transactions to subaddresses,
 - transactions with integrated payment ids,
 - and more ...

## Screenshot

![Generic Monero Scanner](/img/screenshot.png)

## Motivation

The idea is based on two projects:

 - [onion-monero-viewer](https://github.com/moneroexamples/onion-monero-viewer)
 - [transactions-export](https://github.com/moneroexamples/transactions-export)

The first project allowed for online identification of outputs associated with
given address and viewkey. The second project additionally
searched for transactions which use the outputs as decoys/ring members.
However, the first project got discontinued, while the second is a
command-line program which limits its widespread use.

The generic Monero scanner is solution to these issues.

## Technologies

The key technologies used in the scanner are:

- [C++17](https://en.wikipedia.org/wiki/C%2B%2B17) - recent version of the C++ programming language.
- [websockets](https://en.wikipedia.org/wiki/WebSocket) -  protocol for duplex communication between frontend and backend (support provided by [drogon](https://github.com/an-tao/drogon))
- [FiberPool](https://github.com/moneroexamples/fiberpool) - single-file header-only C++17 [boost::fiber](https://github.com/boostorg/fiber) thread pool library
- [xmregcore](https://github.com/moneroexamples/xmregcore) - core utilities used in moneroexample projects.

## Example compilation on Ubuntu 20.04

### Monero download and compilation

To compile the project, most recent Monero development version (i.e., its `master` branch)
needs to be compiled first.

Instruction for compiling monero are here: https://github.com/moneroexamples/monero-compilation

Using `USE_SINGLE_BUILDDIR` flag is important. Without the flag, cmake of the project
will not be able to locate the compiled monero.

### Project download and compilation

```bash
# go to home folder
cd ~

# drogon dependencies
sudo apt install libjsoncpp-dev uuid-dev

git clone --recurse-submodules https://github.com/moneroexamples/generic-xmr-scanner

cd generic-xmr-scanner

mkdir build && cd build

cmake ..

# altearnatively can use cmake -DMONERO_DIR=/path/to/monero_folder ..
# if monero is not in ~/monero

make
```

Following the compilation, `xmrscanner` executable should be available in the `build` folder.

#### Html fronted

The project comes with basic html fronted located in `html` folder. Basic instruction for running `xmrscanner` over `http` or `https` (SSL) protocoles are given here:

- https://github.com/moneroexamples/generic-xmr-scanner/tree/master/html#basic-html-client-for-the-scanner

## Using Docker

Instead of building and compiling everything from scrach your own, you can use `Docker`. You still need to have full blockchain on your host, which you share with the docker. Do docker containers do not run monero themselfs. So basically you still need to have full node before you can run the `xmrscanner`.

```
git clone --recurse-submodules https://github.com/moneroexamples/generic-xmr-scanner

cd generic-xmr-scanner

# build backend image (using 2 cpus)
docker build --build-arg NPROC=2  . -t xmrscannerbackend

# build frontend image
docker build ./html -t xmrscannerfrontend
```

When the two images are build, you can run containers for backend and frontend:

```
# run backend container on mainnet (-n 0),
docker run -it -v <path-to-monero-blockckain-on-the-host>:/home/monero/.bitmonero -p 8848:8848  xmrscannerbackend "./xmrscanner -n 0"

# run frontend container
docker run -it -p 9100:80  xmrscannerfrontend
```

Once the containers are running, open browser: `http://<IP_ADDRESS>:9100/`.

#### Program options

```bash
xmrscanner: generic monero scanner:
  -h [ --help ]                         Help
  -n [ --nettype ] arg (=2)             network type: 0-MAINNET, 1-TESTNET,
                                        2-STAGENET
  -b [ --blockchain-path ] arg          Non-default path to lmdb folder
                                        containing the blockchain. Default is
                                        /home/mwo2/.bitmonero/stagenet/lmdb
  -d [ --da-path ] arg (=./config/default_addresses.json)
                                        Non-default path to default_addresses.j
                                        son file
  -c [ --config-path ] arg (=./config/config.json)
                                        Non-default path to config.json file
  -f [ --fiberthreads ] arg (=0)        Number of fiberpool thread workers.
                                        Default is 0 - based on hardware
  -p [ --port ] arg (=8848)             Service port
```

## How can you help

Constructive criticism, code and website edits are always good. They can be made through github.

repository: moneroexamples/generic-xmr-scanner

repo_name: moneroexamples/generic-xmr-scanner


text:
# Cesar UI

This module holds all web resources (Js, CSS, images...). We use several tools for its own build system

* [Node.js and npm](https://nodejs.org/) : downloads all the required JS libraries
* [Gulp](http://gulpjs.com/) : builds system used to package the project. The process is defined in the main file [gulpfile.old](gulpfile.old) and in all its sub [config files](gup)
* [Gradle](https://gradle.org/) : builds a web archive which will be deployed in the final webapp

This module use Angular V1

## Life cycle Gulp

We use gulp to manage the lifecycle of the web applications

To build the project you can lauch `gulp`. By default the tasks `clean`, `test` and `build` are launched

The main tasks are defined in the gulpfile.old and in the subfiles available in `/gulp`

* `default` : launch tasks `clean`, `test` and `build`
* `build` : package app for dev and prod
* `bundle` : prepare assets used in dev and prod
* `serve` : start a web server and launch the webapp
* `test` : launch all the unit tests
* `test:watch` : launch all the unit tests with Karma watch mode

## Develop UI

When you develop the web application you can launch an http server with this gulp task

```
gulp serve
```

Several watchers rerun the server when you change files (JS, HTML, Less...). See the gulp task [watch](gulp/dev.js).

When you want to package the web resources for the final webapp (not needed in development) you can launch the command

```
../gradlew build
```


text:
# Variable-length code

https://en.wikipedia.org/wiki/Variable-length_code

In coding theory, a **variable-length code** is a code which maps source symbols to a variable number of bits.

Variable-length codes can allow sources
to be compressed and decompressed
with zero error (lossless data compression)
and still be read back symbol by symbol.

With the right coding strategy,
an independent and identically-distributed source
may be compressed almost arbitrarily close to its entropy.

This is in contrast to *fixed-length coding* methods,
for which data compression is only possible
for large blocks of data and any compression
beyond the logarithm of the total number of possibilities
comes with a finite probability of failure
(though arbitrarily small probability).

Some variable-length coding strategies
- Huffman coding
- Lempel-Ziv coding
- arithmetic coding
- context-adaptive variable-length coding

license: Unlicense


text:
# Babble: PennAppsXVIII

[PennApps Project Fall 2018](https://devpost.com/software/pennapps18-2pjcx0)

[![](http://img.youtube.com/vi/_DBQITRE7F4/0.jpg)](http://www.youtube.com/watch?v=_DBQITRE7F4 "")

## Babble: Offline, Self-Propagating Messaging for Low-Connectivity Areas

Babble is the world's first and only chat platform that is able to be installed, setup, and used 100% offline. This platform has a wide variety of use cases such as use in communities with limited internet access like North Korea, Cuba, and Somalia. Additionally, this platform would be able to maintain communications in disaster situations where internet infrastructure is damaged or sabotaged. ex. Warzones, Natural Disasters, etc.

### Demo Video

[![](http://img.youtube.com/vi/M5dz9_pf2pU/0.jpg)](http://www.youtube.com/watch?v=M5dz9_pf2pU "")

## Offline Install & Setup

Babble (a zipped APK) is able to be sent from one user to another via Android Beam. From there it is able to be installed. This allows any user to install the app just by tapping their phone to that of another user. This can be done 100% offline.

## Offline Send

All Babble users connect to all nearby devices via the creation of a localized mesh network created using the Android Nearby Connections API. This allows for messages to be sent directly from device to device via m to n peer to peer as well as messages to be daisy chain sent from peer to peer to ... to peer to peer.

Each Babble user's device keeps a localized ledger of all messages that it has sent and received, as well as an amalgamation of all of the ledgers of every device that this instance of Babble has been connected directly to via Android Nearby.

The combination of the Android Nearby Connections API with this decentralized, distributed ledger allows for messages to propagate across mesh networks and move between isolated networks as users leave one mesh network and join another.

## Cloud Sync when Online

Whenever an instance of Babble gains internet access, it uploads a copy of its ledger to a MongoDB Atlas Cluster running on Google Cloud. There the local ledger is amalgamated with the global ledger which contains all messages sent world wide. From there the local copy of the ledger is updated from the global copy to contain messages for nearby users.

## [Use Cases](#use-cases)

### Internet Infrastructure Failure: Natural Disaster

Imagine a natural disaster situation where large scale internet infrastructure is destroyed or otherwise not working correctly. Only a small number of users of the app would be able to distribute the app to all those affected by the outage and allow them to communicate with loved ones and emergency services. Additionally, this would provide a platform by which emergency services would be able to issue public alerts to the entire mesh network.

### Untraceable and Unrestrictable Communication in North Korea

One of the future directions we would like to take this would be a Ethereum-esq blockchain based ledger. This would allow for 100% secure, private, and untraceable messaging. Additionally the Android Nearby Connections API is able to communicate between devices via, cellular network, Wifi, Bluetooth, NFC, and Ultrasound which makes our messages relatively immune to jamming. With the mesh network, it would be difficult to block messaging on a large scale.

As a result of this feature set, Babble would be a perfect app to allow for open and unobstructed, censored, or otherwise unrestricted communication inside of a country with heavily restricted internet access like North Korea.

### Allowing Cubans to Communicate with Family and Friends in the US

Take a use case of a Cuba wide roll out. There will be a limited number of users in large cities like Havana or Santiago de Cuba that will have internet access as well as a number of users distributed across the country who will have occasional internet access. Through both the offline send and the cloud sync, 100% offline users in cuba would be able to communicate with family stateside.

## Future Goals and Directions

Our future goals would be to build better stability and more features such as image and file sharing, emergency messaging, integration with emergency services and the 911 decision tree, end to end encryption, better ledger management, and conversion of ledger to Ethereum-esq anonymized blockchain to allow for 100% secure, private, and untraceable messaging.

Ultimately, the most insane use of our platform would be as a method for rolling out low bandwidth internet to the offline world.

Name creds go to Chris Choi

gha_language: Java


text:
CHALLENGE
=========

Play around with the various aspects of the examples you have used. Explore the
tweepy docs and the API methods at
 <http://tweepy.readthedocs.org/en/v2.3.0/index.html>

NOTE
----

Some of the API methods allow you to create, modify, and delete tweets.  Be
careful when writing to the Twitter stream, as your test information will be out
in the world available for all to see. If you do want to go ahead with some
write tests, modify your twitter app to have read and write access rather than
read only access.

![](http://codeinstitute.wpengine.com/wp-content/uploads/2015/11/1446569326_image1.png)

gha_language: CSS


text:
# California Housing

## Source

This dataset is a modified version of the California Housing dataset available from [Luís Torgo's page](http://www.dcc.fc.up.pt/~ltorgo/Regression/cal_housing.html) (University of Porto). Luís Torgo obtained it from the StatLib repository (which is closed now). The dataset may also be downloaded from StatLib mirrors.

This dataset appeared in a 1997 paper titled _Sparse Spatial Autoregressions_ by Pace, R. Kelley and Ronald Barry, published in the _Statistics and Probability Letters_ journal. They built it using the 1990 California census data. It contains one row per census block group. A block group is the smallest geographical unit for which the U.S. Census Bureau publishes sample data (a block group typically has a population of 600 to 3,000 people).

## Tweaks

The dataset in this directory is almost identical to the original, with two differences:

- 207 values were randomly removed from the `total_bedrooms` column, so we can discuss what to do with missing data.
- An additional categorical attribute called `ocean_proximity` was added, indicating (very roughly) whether each block group is near the ocean, near the Bay area, inland or on an island. This allows discussing what to do with categorical data.

Note that the block groups are called "districts" in the Jupyter notebooks, simply because in some contexts the name "block group" was confusing.

## Data description

    >>> housing.info()
    <class 'pandas.core.frame.DataFrame'>
    RangeIndex: 20640 entries, 0 to 20639
    Data columns (total 10 columns):
    longitude             20640 non-null float64
    latitude              20640 non-null float64
    housing_median_age    20640 non-null float64
    total_rooms           20640 non-null float64
    total_bedrooms        20433 non-null float64
    population            20640 non-null float64
    households            20640 non-null float64
    median_income         20640 non-null float64
    median_house_value    20640 non-null float64
    ocean_proximity       20640 non-null object
    dtypes: float64(9), object(1)
    memory usage: 1.6+ MB

    >>> housing["ocean_proximity"].value_counts()
    <1H OCEAN     9136
    INLAND        6551
    NEAR OCEAN    2658
    NEAR BAY      2290
    ISLAND           5
    Name: ocean_proximity, dtype: int64

    >>> housing.describe()
              longitude      latitude  housing_median_age   total_rooms  \
    count  16513.000000  16513.000000        16513.000000  16513.000000
    mean    -119.575972     35.639693           28.652335   2622.347605
    std        2.002048      2.138279           12.576306   2138.559393
    min     -124.350000     32.540000            1.000000      6.000000
    25%     -121.800000     33.940000           18.000000   1442.000000
    50%     -118.510000     34.260000           29.000000   2119.000000
    75%     -118.010000     37.720000           37.000000   3141.000000
    max     -114.310000     41.950000           52.000000  39320.000000

           total_bedrooms    population    households  median_income
    count    16355.000000  16513.000000  16513.000000   16513.000000
    mean       534.885112   1419.525465    496.975050       3.875651
    std        412.716467   1115.715084    375.737945       1.905088
    min          2.000000      3.000000      2.000000       0.499900
    25%        295.000000    784.000000    278.000000       2.566800
    50%        433.000000   1164.000000    408.000000       3.541400
    75%        644.000000   1718.000000    602.000000       4.745000
    max       6210.000000  35682.000000   5358.000000      15.000100


text:
3. Configuration Files
Apache HBase uses the same configuration system as Apache Hadoop. All configuration files are located in the conf/ directory, which needs to be kept in sync for each node on your cluster.

HBase Configuration File Descriptions
backup-masters
Not present by default. A plain-text file which lists hosts on which the Master should start a backup Master process, one host per line.

hadoop-metrics2-hbase.properties
Used to connect HBase Hadoop’s Metrics2 framework. See the Hadoop Wiki entry for more information on Metrics2. Contains only commented-out examples by default.

hbase-env.cmd and hbase-env.sh
Script for Windows and Linux / Unix environments to set up the working environment for HBase, including the location of Java, Java options, and other environment variables. The file contains many commented-out examples to provide guidance.

hbase-policy.xml
The default policy configuration file used by RPC servers to make authorization decisions on client requests. Only used if HBase security is enabled.

hbase-site.xml
The main HBase configuration file. This file specifies configuration options which override HBase’s default configuration. You can view (but do not edit) the default configuration file at docs/hbase-default.xml. You can also view the entire effective configuration for your cluster (defaults and overrides) in the HBase Configuration tab of the HBase Web UI.

log4j.properties
Configuration file for HBase logging via log4j.

regionservers
A plain-text file containing a list of hosts which should run a RegionServer in your HBase cluster. By default this file contains the single entry localhost. It should contain a list of hostnames or IP addresses, one per line, and should only contain localhost if each node in your cluster will run a RegionServer on its localhost interface.
Checking XML Validity
When you edit XML, it is a good idea to use an XML-aware editor to be sure that your syntax is correct and your XML is well-formed. You can also use the xmllint utility to check that your XML is well-formed. By default, xmllint re-flows and prints the XML to standard output. To check for well-formedness and only print output if errors exist, use the command xmllint -noout filename.xml.
Keep Configuration In Sync Across the Cluster
When running in distributed mode, after you make an edit to an HBase configuration, make sure you copy the content of the conf/ directory to all nodes of the cluster. HBase will not do this for you. Use rsync, scp, or another secure mechanism for copying the configuration files to your nodes. For most configuration, a restart is needed for servers to pick up changes An exception is dynamic configuration. to be described later below.

repository: sixmonths/mirued

repo_name: sixmonths/mirued


text:
# Application Layer

This layer contains all application logic. It is dependent on the domain layer, but has no dependencies on any other layer or project.
This layer defines interfaces that are implemented by outside layers.

# Domain Layer

This will contain all entities, enums, exceptions, types and logic specific to the domain.

url: https://raw.githubusercontent.com/VeselinBPavlov/web-application-templates/d1f5d221c48288a1234d6129ffe3f2d2ec36da70/ASP .NET Core 3.1 SPA Angular Template/Src/Core/README.md