text:
---
# An instance of the Experience widget.
# Documentation: https://wowchemy.com/docs/page-builder/
widget: experience

# This file represents a page section.
headless: true

# Order that this section appears on the page.
weight: 40

title: Experience
subtitle:

# Date format for experience
#   Refer to https://wowchemy.com/docs/customization/#date-format
date_format: Jan 2006

# Experiences.
#   Add/remove as many `experience` items below as you like.
#   Required fields are `title`, `company`, and `date_start`.
#   Leave `date_end` empty if it's your current employer.
#   Begin multi-line descriptions with YAML's `|2-` multi-line prefix.
experience:
  - title: Data Science Intern
    company: Swisscom
    company_url: 'https://www.swisscom.ch/'
    location: Lausanne
    date_start: '2021-09-01'
    date_end: ''
    description: Doing an Internship at Swisscom. Mission is to build recommender systems for the Swisscom Data Catalogue. Implies a lot of Machine Learning and NLP.

  - title: Teaching Assistant for Practical Programming in Python
    company: UNIL
    company_url: ''
    location: Lausanne
    date_start: '2021-02-15'
    date_end: '2021-07-01'
    description: Help the teacher with teaching material and help students to succeed the course by leading exercise sessions. The course has over 250 students.

  - title: Communication Assistant
    company: EPFL-IC
    company_url: ''
    location: Lausanne
    date_start: '2019-09-01'
    date_end: '2020-12-01'
    description: |2-
        Have to ensure good content on different social medias: Instagram, Twitter Facebook and LinkedIn. Responsible for writing articles about events happening on        the campus, and interviewing people related to Computer Science.

  - title: Teaching Assistant for Internet & Code for girls
    company: EPFL
    company_url: ''
    location: Lausanne
    date_start: '2019-02-01'
    date_end: '2020-02-01'
    description: |2-
        Organizer of the Code & Internet for Girls course. It allows girls from 9 to 12 to build their own website and a little game using Scratch.
---

repository: valentingarnier/onlineResume

repo_name: valentingarnier/onlineResume


text:
---
title: Karen Sandler
summary: Software activist, executive director (GNOME)
date: 2013-09-19
categories:
- lawyer
- linux
---

### Who are you, and what do you do?

I'm the Executive Director of the [GNOME Foundation](http://www.gnome.org/foundation/ "The GNOME non-profit organisation."). I also do volunteer legal work for the Software Freedom Law Center, the Software Freedom Conservancy and [QuestionCopyright.org](http://questioncopyright.org/ "A website about copyright issues."). I guess it's easiest to describe me as a free software activist and advocate.

### What hardware do you use?

I now have a new laptop. It's a [Zareason Ultralap][ultralap-430]. I'm still getting used to the keyboard, but it's *pretty* and I got it shipped with the latest [Fedora][]. I haven't had time yet to get my dream setup going yet though. It's also giving my shoulder a break since it's so much lighter than anything I've owned previously.

I've got the included processor (i3-3217U 1.8ghz) 8GB memory and a 128GB mSATA SSD. The wireless card is an Intel one.

### And what software?

Right now I'm using [Fedora][], obviously (I suppose) with [GNOME 3][gnome]. I keep things pretty basic and use the default software - [evolution][] for mail and calendar (though sometimes I use web-based mail when I feel like it), Web ([Epiphany][]), [Empathy][], etc. I want to make sure that I know what the default experience is with all GNOME software.

I'd also be lost without [LibreOffice][] for presentations, word processing and spreadsheets.

When I started at GNOME, I decided that I would try not to use the command line for a while to see what a less techie user might experience and much to my surprise I haven't gone back. I use the command line a little but mostly I'm happy with the great GUI I get with GNOME and Fedora.

### What would be your dream setup?

As soon as I find a quiet weekend, my goal is to partition my drive so I can choose between [Fedora][], [Debian][] and [openSUSE][] at will! I probably should get a proper keyboard and mouse to protect my wrists. Otherwise I'm pretty happy - I'm glad to keep supporting the small independent hardware manufacturers like Zareason who will ship you the GNU/Linux distro of your choice all installed and ready to go. Plus, with 3.10 coming out next week GNOME just keeps getting better.

[debian]: https://www.debian.org/ "A Linux distribution."
[empathy]: https://wiki.gnome.org/action/show/Apps/Empathy?action=show&redirect=Empathy "An instant messenger client for GNOME."
[epiphany]: https://en.wikipedia.org/wiki/Epiphany_(web_browser) "A WebKit-base browser for GNOME."
[evolution]: https://wiki.gnome.org/Apps/Evolution "An integrated mail, calendar and contact program for GNOME."
[fedora]: https://fedoraproject.org/ "A Linux distribution."
[gnome]: https://www.gnome.org/ "A desktop system for *nix operating systems."
[libreoffice]: https://www.libreoffice.org/ "A free, open-source productivity suit."
[opensuse]: https://en.wikipedia.org/wiki/OpenSUSE "A Linux distribution."
[ultralap-430]: http://web.archive.org/web/20161013065858/https://zareason.com/shop/UltraLap-430.html "A 14.1 inch laptop."

license: MIT

repository: waferbaby/usesthis

branch_name: refs/heads/main

extension: markdown

gha_language: HTML

gha_license_id: MIT

license_type: permissive

repo_name: waferbaby/usesthis


text:
## Modified!
I've made a bunch of modifications to this theme, but below you can find the breadcrumbs back to it's original.

## Contributing

Have you found a bug or got an idea for a new feature? Feel free to use the [issue tracker](https://github.com/kishaningithub/hugo-creative-portfolio-theme/issues) to let me know. Or make directly a [pull request](https://github.com/kishaningithub/hugo-creative-portfolio-theme/pulls).

## License

This port is released under the MIT License. Check the [original theme license](https://bootstrapious.com/p/creative-portfolio) for additional licensing information.

## Thanks

Thanks to [Steve Francia](https://github.com/spf13) for creating Hugo and the awesome community around the project. And also thanks to [Bootstrapious](http://bootstrapious.com/) for creating this awesome theme.

repository: astromberg/blog

branch_name: refs/heads/master

extension: md

repo_name: astromberg/blog


text:
# Receiver Creator

<!-- status autogenerated section -->
| Status        |           |
| ------------- |-----------|
| Stability     | [alpha]: logs, traces   |
|               | [beta]: metrics   |
| Distributions | [contrib], [splunk], [sumo] |
| Issues        | [![Open issues](https://img.shields.io/github/issues-search/open-telemetry/opentelemetry-collector-contrib?query=is%3Aissue%20is%3Aopen%20label%3Areceiver%2Freceivercreator%20&label=open&color=orange&logo=opentelemetry)](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aopen+is%3Aissue+label%3Areceiver%2Freceivercreator) [![Closed issues](https://img.shields.io/github/issues-search/open-telemetry/opentelemetry-collector-contrib?query=is%3Aissue%20is%3Aclosed%20label%3Areceiver%2Freceivercreator%20&label=closed&color=blue&logo=opentelemetry)](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues?q=is%3Aclosed+is%3Aissue+label%3Areceiver%2Freceivercreator) |
| [Code Owners](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#becoming-a-code-owner)    | [@rmfitzpatrick](https://www.github.com/rmfitzpatrick) |

[alpha]: https://github.com/open-telemetry/opentelemetry-collector#alpha
[beta]: https://github.com/open-telemetry/opentelemetry-collector#beta
[contrib]: https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-contrib
[splunk]: https://github.com/signalfx/splunk-otel-collector
[sumo]: https://github.com/SumoLogic/sumologic-otel-collector
<!-- end autogenerated section -->

This receiver can instantiate other receivers at runtime based on whether
observed endpoints match a configured rule. To use the receiver creator, you
must first configure one or more
[observers](../../extension/observer/README.md) that will discover networked
endpoints that you may be interested in. The configured rules will be
evaluated for each endpoint discovered. If the rule evaluates to true then
the receiver for that rule will be started against the matched endpoint.

If you use the receiver creator in multiple pipelines of differing telemetry types,
but a given dynamically instantiated receiver doesn't support one of the pipeline's type,
it will effectively lead to a logged no-op that won't cause a collector service failure.

## Configuration

**watch_observers**

A list of observers previously defined to be run in the `extensions` section.
receiver_creator will watch for endpoints generated by these observers.

**receivers**

A map of receiver names (e.g. `redis/1`) to a template for when and how to
instantiate that receiver.

**receivers.<receiver_type/id>.rule**

Rule expression using [expvar
syntax](https://github.com/antonmedv/expr/blob/master/docs/Language-Definition.md).
Variables available are detailed below in [Rule
Expressions](#rule-expressions).

Note: The built-in `type` function introduced in v1.14.1 has been relocated to `typeOf`.

**receivers.<receiver_type/id>.config**

This is configuration that will be used when creating the receiver at
runtime.

This option can use static and dynamic configuration values. Static values
are normal YAML values. However, the value can also be dynamically constructed
from the discovered endpoint object. Dynamic values are surrounded by
backticks (\`). If a literal backtick is needed use \\` to escape it. Dynamic
values can be used with static values in which case they are concatenated.
For example:

```yaml
config:
   secure_url: https://`pod.labels["secure_host"]`
```

The value of `secure_url` will be `https://` concatenated with the value of
the `secure_host` label.

This can also be used when the discovered endpoint needs to be changed
dynamically. For instance, suppose the IP `<IP_ADDRESS>` is discovered without a
port but the port needs to be set inside endpoint.  If no `endpoint` field is available you are
required to specify any necessary fields.

**receivers.resource_attributes**

```yaml
resource_attributes:
  <endpoint type>:
    <attribute>: <attribute value>
```

This setting controls what resource attributes are set on telemetry emitted from the created receiver. These attributes can be set from [values in the endpoint](#rule-expressions) that was matched by the `rule`. These attributes vary based on the endpoint type. These defaults can be disabled by setting the attribute to be removed to an empty value. Note that the values can be dynamic and processed the same as in `config`.

Note that the backticks below are not typos--they indicate the value is set dynamically.

`type == "pod"`

| Resource Attribute | Default       |
|--------------------|---------------|
| k8s.pod.name       | \`name\`      |
| k8s.pod.uid        | \`uid\`       |
| k8s.namespace.name | \`namespace\` |

`type == "port"`

| Resource Attribute | Default           |
|--------------------|-------------------|
| k8s.pod.name       | \`pod.name\`      |
| k8s.pod.uid        | \`pod.uid\`       |
| k8s.namespace.name | \`pod.namespace\` |

`type == "container"`

| Resource Attribute   | Default           |
|----------------------|-------------------|
| container.name       | \`name\`          |
| container.image.name | \`image\`         |

`type == "hostport"`

None

`type == "k8s.node"`

| Resource Attribute | Default           |
|--------------------|-------------------|
| k8s.node.name      | \`name\`          |
| k8s.node.uid       | \`uid\`           |

See `redis/2` in [examples](#examples).

**receivers.<receiver_type/id>.resource_attributes**

```yaml
receivers:
  <receiver_type>:
    resource_attributes:
      <attribute>: <attribute string value>
```

Similar to the per-endpoint type `resource_attributes` described above but for individual receiver instances. Duplicate attribute entries (including the empty string) in this receiver-specific mapping take precedence. These attribute values also support expansion from endpoint environment content. At this time their values must be strings.

## Rule Expressions

Each rule must start with `type == ("pod"|"port"|"hostport"|"container"|"k8s.node") &&` such that the rule matches
only one endpoint type. Depending on the type of endpoint the rule is
targeting it will have different variables available.

### Pod

| Variable    | Description                       |
|-------------|-----------------------------------|
| type        | `"pod"`                           |
| id          | ID of source endpoint             |
| name        | name of the pod                   |
| namespace   | namespace of the pod              |
| uid         | unique id of the pod              |
| labels      | map of labels set on the pod      |
| annotations | map of annotations set on the pod |

### Port

| Variable        | Description                             |
|-----------------|-----------------------------------------|
| type            | `"port"`                                |
| id              | ID of source endpoint                   |
| name            | container port name                     |
| port            | port number                             |
| protocol        | The transport protocol ("TCP" or "UDP") |
| pod.name        | name of the owning pod                  |
| pod.namespace   | namespace of the pod                    |
| pod.uid         | unique id of the pod                    |
| pod.labels      | map of labels of the owning pod         |
| pod.annotations | map of annotations of the owning pod    |

### Host Port

| Variable      | Description                                      |
|---------------|--------------------------------------------------|
| type          | `"hostport"`                                     |
| id            | ID of source endpoint                            |
| process_name  | Name of the process                              |
| command       | Command line with the used to invoke the process |
| is_ipv6       | true if endpoint is IPv6, otherwise false        |
| port          | Port number                                      |
| transport     | The transport protocol ("TCP" or "UDP")          |

### Container

| Variable       | Description                                                       |
|----------------|-------------------------------------------------------------------|
| type           | `"container"`                                                     |
| id             | ID of source endpoint                                             |
| name           | Primary name of the container                                     |
| image          | Name of the container image                                       |
| port           | Exposed port of the container                                     |
| alternate_port | Exposed port accessed through redirection, such as a mapped port  |
| command        | The command used to invoke the process of the container           |
| container_id   | ID of the container                                               |
| host           | Hostname or IP of the underlying host the container is running on |
| transport      | Transport protocol used by the endpoint (TCP or UDP)              |
| labels         | User-specified metadata labels on the container                   |

### Kubernetes Node

| Variable       | Description                                                       |
|----------------|-------------------------------------------------------------------|
| type                  | `"k8s.node"`                                                                                |
| id                    | ID of source endpoint                                                                                |
| name                  | The name of the Kubernetes node                                                                                |
| uid                   | The unique ID for the node                                                                                |
| hostname              | The node's hostname as reported by its Status object                                                                   |
| external_ip           | The node's external IP address as reported by its Status object                                                        |
| internal_ip           | The node's internal IP address as reported by its Status object                                                        |
| external_dns          | The node's external DNS record as reported by its Status object                                                        |
| internal_dns          | The node's internal DNS record as reported by its Status object                                                        |
| annotations           | A key-value map of non-identifying, user-specified node metadata                                                       |
| labels                | A key-value map of user-specified node metadata                                                                        |
| kubelet_endpoint_port | The node Status object's DaemonEndpoints.KubeletEndpoint.Port value                                                    |

## Examples

```yaml
extensions:
  # Configures the Kubernetes observer to watch for pod start and stop events.
  k8s_observer:
  host_observer:

receivers:
  receiver_creator/1:
    # Name of the extensions to watch for endpoints to start and stop.
    watch_observers: [k8s_observer]
    receivers:
      prometheus_simple:
        # Configure prometheus scraping if standard prometheus annotations are set on the pod.
        rule: type == "pod" && annotations["prometheus.io/scrape"] == "true"
        config:
          metrics_path: '`"prometheus.io/path" in annotations ? annotations["prometheus.io/path"] : "/metrics"`'
          endpoint: '`endpoint`:`"prometheus.io/port" in annotations ? annotations["prometheus.io/port"] : 9090`'
        resource_attributes:
          an.attribute: a.value
          # Dynamic configuration values
          app.version: '`labels["app_version"]`'

      redis/1:
        # If this rule matches an instance of this receiver will be started.
        rule: type == "port" && port == 6379
        config:
          # Static receiver-specific config.
          password: secret
          # Dynamic configuration value.
          collection_interval: '`pod.annotations["collection_interval"]`'

      redis/2:
        # Set a resource attribute based on endpoint value.
        rule: type == "port" && port == 6379

    resource_attributes:
      # Dynamic configuration values, overwriting default attributes`
      pod:
        service.name: '`labels["service_name"]`'
        app: '`labels["app"]`'
      port:
        service.name: '`pod.labels["service_name"]`'
        app: '`pod.labels["app"]`'
  receiver_creator/2:
    # Name of the extensions to watch for endpoints to start and stop.
    watch_observers: [host_observer]
    receivers:
      redis/on_host:
        # If this rule matches an instance of this receiver will be started.
        rule: type == "port" && port == 6379 && is_ipv6 == true
        resource_attributes:
          service.name: redis_on_host
  receiver_creator/3:
    watch_observers: [k8s_observer]
    receivers:
      kubeletstats:
        rule: type == "k8s.node"
        config:
          auth_type: serviceAccount
          collection_interval: 10s
          endpoint: '`endpoint`:`kubelet_endpoint_port`'
          extra_metadata_labels:
            - container.id
          metric_groups:
            - container
            - pod
            - node

processors:
  exampleprocessor:

exporters:
  exampleexporter:

service:
  pipelines:
    metrics:
      receivers: [receiver_creator/1, receiver_creator/2, receiver_creator/3]
      processors: [exampleprocessor]
      exporters: [exampleexporter]
  extensions: [k8s_observer, host_observer]
```

The full list of settings exposed for this receiver are documented [here](./config.go)
with detailed sample configurations [here](./testdata/config.yaml).

gha_language: Go


text:
[![build](https://github.com/felangel/bloc/workflows/build/badge.svg)](https://github.com/felangel/bloc/actions)

# Github Search

Sample project which illustrates how to setup a Flutter and AngularDart project with code sharing.

## Quick Start

_Make sure you have the [Dart SDK](https://dart.dev/tools/sdk) and [Flutter SDK](https://flutter.dev/docs/get-started/install) installed before proceeding._

Open this project in your editor of choice (VSCode is recommended).

### Setup

1. Install dependencies for `common_github_search`:

   ```bash
   # change directories into common_github_search
   cd common_github_search

   # install dependencies
   pub get

   # change directories back out to the root directory
   cd ../
   ```

2. Install dependencies for `flutter_github_search`

   ```bash
   # change directories into flutter_github_search
   cd flutter_github_search

   # install dependencies
   flutter packages get

   # change directories back out to the root directory
   cd ../
   ```

3. Install dependencies for `angular_github_search`

   ```bash
   # change directories into flutter_github_search
   cd angular_github_search

   # install dependencies
   pub get

   # change directories into flutter_github_search
   cd ../
   ```

### Run Flutter

```bash
# change directories into flutter_github_search
cd flutter_github_search

# run the flutter project
flutter run
```

### Run AngularDart

```bash

# change directories into angular_github_search
cd angular_github_search

# run the angular project
webdev serve
```

repository: felangel/bloc

gha_language: Dart

repo_name: felangel/bloc


text:
# React app for voting for the good music tracks

This simple application is designed to simply to choose the best Creative Commons music tracks.

Available at [popoluska.paralelnapolis.sk](http://popoluska.paralelnapolis.sk)

Dependencies:
- nodejs
- npm
- mongodb

and run `npm i` for installing npm dependencies in parend and be directory.

## npm start

For hot reload developing

```
npm start
```

## npm build

You can simply build this app by

```
npm run build
```

## install MongoDB and Node on Debian 9
```
apt install curl
curl https://www.mongodb.org/static/pgp/server-4.0.asc |  apt-key add -
echo "deb http://repo.mongodb.org/apt/debian stretch/mongodb-org/4.0 main" >> /etc/apt/sources.list.d/mongodb-org-4.0.list

apt update
apt-get install mongodb-org nodejs libcurl3 openssl -y
systemctl enable mongod
systemctl start mongod
systemctl status mongod
```

repository: pavoltravnik/music-selection

repo_name: pavoltravnik/music-selection


text:
---
id: rocketjump
title: RocketJump
sidebar_label: RocketJump
---
## What is a RocketJump?
When you have composed all the logic you need, it is time to export generated actions, reducer, saga and selectors, and so make the real rocketjump!

In order to do this, you have to invoke the last `RocketJump Partial`.

```js
const output = myRocketJumpPartial()
```

In order to be invokable, a `RocketJump Partial` **must** contain three additional properties. These properties **must** be defined in the last configuration object supplied to the definition of the `RocketJump Partial` you are invoking.

Example
```js
const myRocketJumpPartial = rj(
    rjPlugin1,
    rjPlugin2,
    {
        /* other optional properties */

        /* ----- THIS IS THE IMPORTANT PART ----- */
        type: 'COOL_API_TYPE',
        effect: myAsyncFunction,
        state: 'soCool'
    }
)
```

## Configuration settings
### type *(string)*
This key configures the name of the asynchronous task you are going to generate. It is **mandatory** that this name is unique throughout your application, in order to avoid name clashes. The value of this key is used as a prefix to create action types that will be used in the saga to tame asynchronism:
- `${type}_LOADING` is dispatched when the asynchronous operation starts
- `${type}_SUCCESS` is dispatched when the asynchronous operation completes successfully
- `${type}_FAILURE` is dispatched when the asynchronous operation completes with some error
- `${type}_UNLOAD` is dispatched when the asynchronous operation is stopped and the state cleared

### state *(string|selector|function|false)*
This key configures the base selector used to access data managed by this rocketJump instance.
It can be a string, a selector from [reselect](https://github.com/reduxjs/reselect) or a function.

If it is a string, it is used like a path to access the state object using [lodash.get](https://lodash.com/docs/#get).
If it is a selector, it will be used as a base selector to create nested selectors.
If it is a function, it will be called with the redux store as its first argument.

If it is `false`, both selectors and reducer creation is skipped. This is useful when you need only to run action driven side effect in rocketjump environment.

### effect *(function)*

> This configuration option was called `api` in version 1.*

This is the side effect, the asynchronous task incapsulated in this rocketjump instance. The function passed to this key must conform the following signature

```js
(params: any) => Promise
```

The params argument will contain the first argument passed to the generated `load` action.

It is important that this function returns a Promise that resolves on valid data and rejects in case any error occurs. This allows the saga to launch the task and observe the outcome, reacting properly to eventual errors.

repository: inmagik/redux-rocketjump

gha_language: JavaScript

repo_name: inmagik/redux-rocketjump


text:
---
title: "Create a Docker Account"
chapter: false
weight: 20
---
{{% notice info %}}
 If you have already have an Docker ID, the you can skip this section.
{{% /notice %}}

1. Follow [these steps](https://dockr.ly/31uSAeb) to create a Docker ID for yourself. You only need to do the "Register for a Docker ID" section.
2. Have your Docker ID memorized or written down nearby as you will need to use it in future steps.


text:
# VTasks
## Chrome Extension for TO do

### How to Use it
1. Download this repository
2. Extract the zip file
3. Open any chromium based browser eg. Brave, Chrome, Edge etc
4. Go to settings
5. Go to Extensions
5. Click Manage Extensions
6. Turn on developer mode
7. Click "Load Unpacked"
8. Select the extracted repository
9. Pin this extension
10. Start Using
Done 👍🏻
***
Made By VCF Devs

repository: himanshurajora/VTasks

repo_name: himanshurajora/VTasks


text:
---
layout: post
title: PyCharm type hints
---

For class variables that get assigned:

{% highlight python %}

def foo():
    #: :type: ObservablePlanarGraph
    self._graph = graph
{% endhighlight %}

For input variables (in a docstring):

{% highlight python %}
def foo(self, feature_finder):
    """
    :type feature_finder FeatureFinder
    """
{% endhighlight %}

For return types (also note, tuples and lists):

{% highlight python %}
def foo(self):
    """
    :rtype (list[PolicyData], list[PolicyData])
    """
    return res
{% endhighlight %}

gha_language: CSS


text:
## 4. Project management

> TODO: These commands have not yet been implemented.

TODO scrum + kanban + safe references.

### 4.1. Issues

Whether you are working alone or as a team, it's best to document, coordinate and prioritize the work somehow. Taito CLI provides you commands that you can use to quickly manage issues directly from command line.

Try the following commands. Note that the given issue title don't have to be an exact match. If no exact match is found, command finds the closest matching issue title and confirms that it is the correct issue.

```shell
# Open project management on browser
taito open project

# Authenticate to the issue management system
taito issue auth

# Add a new issue with labels 'feature' and 'posts'.
# You'll be asked to enter issue description once you run the command.
taito issue add "Delete post" feature posts

# List all issues on todo lane
taito issue list todo

# Change issue state to: in progress, assigned to me.
# You'll be asked for a comment, but you can leave it empty.
taito issue state "Delete post" in-progress me

# Add comment on issue.
taito issue comment add "Delete post"

# Change issue state to: testing, assigned to John Doe
taito issue state change "Delete post" testing johndoe

# Open issue on browser
taito issue open "Delete post"
```

TODO autocomplete at least for status, labels and personnel?

### 4.2. Hour reporting

You can also do work hour reporting with Taito CLI directly from command line. This is especially handy if you need to enter the same hour entries to multiple hour reporting systems. With Taito CLI you can input your work hours to multiple systems at once with a single command. You just need to enable multiple Taito CLI hour reporting plugins in your project `taito-config.sh`.

Try the following commands:

```shell
taito hours auth                         # Authenticate
taito hours start                        # Start/continue the timer
taito hours pause                        # Pause the timer
taito hours stop                         # Stop the timer and create an hour entry
taito hours add 6.5                      # Add an hour entry for today
taito hours add 6.5 yesterday            # Add an hour entry for yesterday
taito hours add 6.5 tue Did some work    # Add an hour entry for last tuesday
taito hours list                         # Hour entries of this month
taito hours list all                     # Hour entries of this month for all projects
taito hours show                         # Hour summary for this month
taito hours show this-week               # Hour summary for this week
taito open hours                         # Open hour reporting on browser

TODO bulk adds (e.g. three weeks on vacation)
```

---

**Next:** [PART II: Environments](05-remote-environments.md)

repository: TaitoUnited/taito-cli

branch_name: refs/heads/dev

gha_language: Shell

repo_name: TaitoUnited/taito-cli


text:
+++
Categories = ["Development", "GoLang"]
Description = "One Repo, One Application"
Tags = ["Development", "golang"]
date = "2015-09-17T13:16:49+10:00"
# menu = "main"
title = "One App, One Repo"

+++

 There is a compromise on the one repo = one app, which is why we support Procfile within Cloud Foundry: that of the asynchronous worker. Logically, the worker (which consumes the queue) and the dispatch (which publishes to the queue) often *are* the same application, although they run in separate processes and perhaps separate containers. And they’re scaled differently.

license: Unlicense

repository: joshuamckenty/cloudfactor

repo_name: joshuamckenty/cloudfactor


text:
## doctest, unittest, and python 2.4's cool  doctest.DocFileSuite
Originally published: 2004-09-16 08:59:32
Last updated: 2004-09-16 08:59:32
Author: John Nielsen

Doctest and unittest are like 2 extremes of testing your python
code. One is simple and intuitive and the other is powerful and
requires more formality. In Python 2.4, doctest, builds in some of the
power of unittest, perhaps bridging the gap between the two. This
example shows you how to use doctest and the doctest.DocFileSuite
feature.

gha_language: Python


text:
[![Netlify Status](https://api.netlify.com/api/v1/badges/c06fdb32-fbe8-4df7-adcc-fae35a55ecdc/deploy-status)](https://app.netlify.com/sites/xenodochial-carson-49ee2c/deploys)
[![MIT license](https://img.shields.io/badge/License-MIT-blue.svg)](https://lbesson.mit-license.org/)

## :sun_with_face: Atlas :cloud:

> A javascript powered weather Applcation.

#### Live Version
[Go](https://xenodochial-carson-49ee2c.netlify.com/)

#### Installation
```
git clone git@github.com:mosaaleb/Atlas.git
cd Atlas
npm install

# To build the app for production, run the following command:
npm run build-prod
```

#### Description
The appliaction is built through using multiple api calls using **promises**.

#### Tech Used
- [webpack](https://webpack.js.org/)
- [tailwindcss](https://tailwindcss.com/)
- [Weather API](https://openweathermap.org/api)
- [IP Location API](https://geoipify.whoisxmlapi.com/api)

#### Author
- [Muhammad](https://github.com/mosaaleb)

repository: mosaaleb/Atlas

repo_name: mosaaleb/Atlas


text:
# mminch-64

![mminch-64](https://raw.githubusercontent.com/vasco3/mminch-64/master/mmInch64-logo.png)

[![Known Vulnerabilities](https://snyk.io/test/github/vasco3/mminch-64/badge.svg)](https://snyk.io/test/github/vasco3/mminch-64)

> Convert millimeters to inches with fractions based on 64 denominator.

## About

This library covers a specific need for practical need. People aren't used to think of inches as decimals. They understand them better in fractions. They want to see them as fractions of *64ths* like they would in an [inch ruler](https://www.piliapp.com/actual-size/inch-ruler/). There are many *inch-to-millimeters* tables like http://www.hamuniverse.com/antfrac.html that stress the importance of having inches as fractions.

### Disclaimer

You might say that `3/64 inch` is `1.1906mm`. But to keep rounding simple and to be consistent on the conversion from mm to inches and inches to mm, it rounds millimeters to the nearest half eg. `1/4 in ~ 6.5mm` or `3/64 in ~ 1mm`. This rounding can cause trouble with fractions that are close to each other like `1/4` and `17/64` or with `3/16` and `13/64`. Due to  mismatch from fractions to decimals, the results are slightly off in most cases due to rounding.

This tool is meant to be for a practical use case and not a precise millimetrical use case. This is commonly found in industries like construction and engineering when they are talking about rough estimates. That means that this library can't be replaced by the numbers `0.0393701`, or if you want **/64ths**, `2.51968504`.

By no means use this library as an exact conversion tool for projects that require ultimate precision. By doing so you run the risk of losing millions of dollars like a hand-ful of [NASA projects](http://thinkreliability.com/CM-MarsCO.aspx).

> Shout out to [ugwe43to874nf4](https://www.reddit.com/user/ugwe43to874nf4) for pointing out some of the potential flaws of this library under an incorrect use.

## Install

From npm

`npm install --save mminch-64`

From the browser

`<script<EMAIL_ADDRESS>
## Usage

### Convert mm to inches

```js
  mminch(1).toInch() // '3/64'
```

### Convert inches to mm

```js
  mminch('3/64').toMM() // '1'
```

### Convert inches to feet

```js
  mminch('12').toFeet() // '1'
```

## Supported conversions

- mm to in
- in to mm
- in to feet


text:
# uibuilder Template: Svelte Basic

This is a very simple template for using the [Svelte](https://svelte.dev/) front-end framework with uibuilder and Node-RED. It was originally created from Svelte's https://github.com/sveltejs/template template.

## Folders and Files

The root folder contains this file. It can be used for other things **but** it will not be served up in the Node-RED web server.
_Either_ the `src` or the `dist` folder are served up (along with all of their sub-folders). So the root and any other root sub-folders
can be used mostly however you like. In the case of Svelte, you need to use the `dist` folder, this is configured in the advanced settings of the uibuilder node.

One reserved item in the root folder is the `package.json` file. This is used to configure what other npm packages are needed in order to build and change Svelte-based apps.

Folder list:

* `dist/` - contains the files that will be served to your browser client.

  * `dist/build/` - contains the built JavaScript and CSS files and a map file for debugging. The bundle files are used in the

    * `dist/build/bundle.js` - The "compiled" JavaScript which is minimised for efficiency. Load this into your index.html file. This bundle contains all the required code for the UI except uibuilderfe.js and socket.io-client (they can be bundled but it is generally easier not too because if you do, you have to take on responsibility for maintaining the correct versions when uibuilder gets updated).
    * `dist/build/bundle.css` - The "compiled" CSS which is minimised for efficiency. Load this into your index.html file.
    * `dist/build/bundle.js.map` - A debugging map file that your browser dev tools can use. No need to put this into your index.html.

  * `dist/index.html` - Contains your basic HTML and will be the file loaded and displayed in the browser when going to the uibuilder defined URL.

    Note that in this example, this file simply loads the other resources and sets some metadata. It does _not_ actually contain your UI. The UI is generated by Svelte dynamically.

  * `dist/global.css` - (optional) Contains any CSS you want made available to ALL Svelte components.

* `src/` - contains the source files that Svelte will "build" into your live files in `dist`. Notice that there are a lot more files in this folder than in `dist` because the Svelte build process "bundles" a lot of them together for efficiency.

    In this case, only 2 files exist:

    * `src/main.js` - This is a very simple script that loads the main app.
    * `src/App.svelte` - This is the definition of your UI.

* `scripts` - utility scripts.

* `/` - The root folder for the uibuilder instance

   * `README.md` - This description file - it is good practice to have a README.md in the root describing everything.
   * `package.json` - The `npm` package file. It defines what dev dependencies are required along with some scripts to do builds, run the dev server, etc.
   * `rollup.config.js` - Rollup is the tool used by Svelte to build the output `dist` files. This determines the configuration including specifying the input and output folders.
   * `.eslintrc.js` - Configuration of the ESLINT tool that is strongly recommended when developing. It will find lots of silly errors and help keep code consistently written.
   * `.gitignore` - Tells the GIT code management tool to ignore certain files. Also ensures that those files don't get pushed to GitHub.

Also note that you can use **linked** folders and files in this folder structure. This can be handy if you want to maintain your code in a different folder somewhere.

## Making changes

You will normally only need to make changes to `src/App.svelte`. It is this file that defines your UI in this simple example. Of course, you could also make changes in `dist/index.html` if you want but currently, the Svelte app is being loaded to the `body` tag of the html so all of your UI is dynamic.

As your UI gets more complex, it is best to create multiple custom Svelte components. Each of these will be in its own .svelte file and will define a single custom HTML tag.

### Prerequisites

Before making any changes to this template code, you need to install the development dependencies. To do this, run the following from the instance root folder:

```bash
npm install
```

### Development

Before you start making changes to the svelte files, you should start [Rollup](https://rollupjs.org) by running the following command from the instance root folder:

```bash
npm run dev
```

This will keep running in the background and any change that you save will be immediately reflected in your front-end browser tab. Note that this works even though you are viewing the output using the Node-RED/uibuilder server and not the dev server. Using node-red/uibuilder will ensure that all of the resource URL's and communications work correctly.

So in this case, you are only using the Rollup dev server purely to do the dynamic rebuild and to tell the front-end to reload on changes.

### Production

Once you have finished your development, you should stop the dev server and run the following command from the instance root folder:

```bash
npm run build
```

This will create an optimised version of your code.

---------

If you're using [Visual Studio Code](https://code.visualstudio.com/) it is recommended to install the official extension [Svelte for VS Code](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode). If you are using other editors you may need to install a plugin in order to get syntax highlighting and intellisense.


text:
---
layout:     post
title:      "The Decomposition and Reconstruction theories in SSA"
subtitle:   ""
date:       2019-05-07 08:00:00
author:     "Chuanqi"
header-img: "img/bg/hello_world.jpg"
catalog: trues
tags:
    - Mathematics
---

# Preface
These are some of my research achievements, including the optimality of Singular Value Decomposition and Hankelization in the sense of the spectral norm and Frobenius norm respectively.

# Notes ([click](http://chuanqizhang.com/html/The-Decomposition-and-Reconstruction-theories-in-SSA.html) to view)


text:
The goal of this project is to build a common toolkit for building static sites for a variety of domains. Each program is tailored specifically to one domain, such as a blog, documentation site, or others, the programs are named to reflect this, for example `static-docs` or `static-blog`. Focusing the UX on each domain as necessary, making for a smoother experience, but still sharing a common library, making it easy to create your own.

I don't have much time for this project right now, so it only has what I need, but hopefully long-term it'll turn into something real :D.

---

[![GoDoc](https://godoc.org/github.com/apex/static?status.svg)](https://godoc.org/github.com/apex/static)
![](https://img.shields.io/badge/license-MIT-blue.svg)
![](https://img.shields.io/badge/status-stable-green.svg)

repository: iCyberon/static

repo_name: iCyberon/static


text:
# PHP project (POO MVC CRUD) Car Handle #

## The project. ##
Create a vehicle management application. This very basic application will:

 - See all vehicles
 - View a vehicle in detail
 - Add a vehicle
 - Delete a vehicle
 - Modify a vehicle:

## Needs: ##
 - An abstract class
 - Class Car, Truck, Moto that inherit the class Vehicle

## A home page: ##
- displays all the vehicles present in the car
- a button that allows the addition of vehicles
- for each vehicle, a button to view, edit and delete the vehicle

## a vehicle page: ##
- which presents the vehicle in detail
- the button to add a vehicle

repository: c-dehondt/projet-POO

repo_name: c-dehondt/projet-POO


text:
# redux-view-binder
[![Build Status](https://travis-ci.org/mycomosi/redux-view-binder.svg?branch=master)](https://travis-ci.org/mycomosi/redux-view-binder)
[![Coverage Status](https://coveralls.io/repos/github/mycomosi/redux-view-binder/badge.svg?branch=master)](https://coveralls.io/github/mycomosi/redux-view-binder?branch=master)<br>
Bind your web-component views easily with Redux (no React, no Polymer).

## Binding Views
Redux is a very nice library to centralize the management of the state of your application. The goal of redux-view-binder is to provide a small helper to 'bind' your views to your Redux state changes. Simply said, it means refreshing your views based on the changes of your Redux state automatically.

If you are using React, you might want to have a look at react-redux which provide this capability and more. Redux-view-binder is framework agnostic and can be used with any View library.

Quick example, let's imagine we have a todolist view, where we display a list of todos. Inside our Redux state we have a todos field.

```Javascript
// Import ReduxViewBinder in case of es module
import ReduxViewBinder from 'redux-view-binder';

// Create binder using store from Redux
const binder = new ReduxViewBinder(store);

//... some time later
//retrieve the web component
let todoList = document.querySelector('#todolist');

//bind the component to Redux state changes
binder.bind(
    (state) => { return state.todos; }, //only watch changes of todos field.
    (todos) => { // the watch field is passed to the onChange method.
        //if todos field has changed then we should refresh  the todoList view
        todoList.refresh(todos);
    }
);

```

## Optional parameters

Here is the bind method signature

```Javascript
bind(watch, onChange, [view], [filter])
```

In some cases you want to pass the view to the binder, the view will be provided to the onChange method as the second parameter.

In some other case you want to pass to the onChange method another field from the Redux state object than the one that is watched. In that case the filter method can be used.

Example of usage

```Javascript
// Import ReduxViewBinder in case of es module
import ReduxViewBinder from 'redux-view-binder';

// Create binder using store from Redux
const binder = new ReduxViewBinder(store);

//... some time later
//retrieve the web component
let todoList = document.querySelector('#todolist');

//... some time later
//bind the component to Redux state changes
binder.bind(
    (state) => { return state.todos; }, //only watch changes of todos field.
    (state, view) => { // the watch field is passed to the onChange method.
        //if todos field has changed then we should refresh  the todoList view
        view.refresh(state.todos);
    },
    todoList, //pass the view object, will be passed to the onChange method as second parameter
    (state) => { return state; } // passing the full state object instead of only the todos field
);

```

repository: mycomosi/redux-view-binder

repo_name: mycomosi/redux-view-binder


text:
---
layout: post
title: IAI A-to-Z Side B
nav_exclude: true
date: 2021-07-23
---
{::options parse_block_html="true" parse_span_html="true" /}

#### Print instructions:
Print this page on the back side of the Intersectional AI A-to-Z Glossary Side A and fold as [shown here()].

## Intersectional AI A-to-Z

This glossary of terms for Intersectional AI A-to-Z is a great place to get started. By all means it's only one example of definitions for these complex ideas, and it is meant as an open invitation for conversations and amendments! These concepts show the complexity of the topic seen from multiple angles; yet it is so important to try to break down these concepts into plain language in order to offer more openings for folks to join these conversations. Please chime in, ask questions, help make these definitions better!

#### artificial intelligence
Colloquially, a vague assortment of anything folks want to credit or blame computational systems for doing, or when a machine appears to take on "human" properties like "understanding" or "seeing." But these can be achieved through many different systems that vary widely from simple calculation a programmer would not call AI to complex programs that search for patterns without being given directions in advance. No matter their context or complexity, AI are always socio-technical systems, meaning they are designed, operated, and influenced by humans, rather than entirely autonomous, neutral systems.

#### bias (implicit)
"The assumptions, stereotypes, and unintentional actions (positive or negative) we make towards others based on identity labels like race, religion, age, gender, sexual orientation, or ability. [...] ]we may act on our biases without even realizing it. Often, our implicit biases contradict our values." (Love Has No Labels) They are embedded in and often amplified by digital tools, because computation replicates, speeds up, and compounds all-too-human decision-making.

#### code of conduct
Usually written together by a group, these guidelines outline expectations for behavior and procedures for when members of a community don't meet those expectations. While some argue for structureless, free-speech zones online, many counter that a lack of guidelines highlights power dynamics existing in broader culture (Dunbar-Hester 2020).

#### data colonialism
>

#### e (ethical AI, epidermalization, embodiment, emotion?)
>

#### FLOSS (free libre open source software)
>

#### g ?
>

#### heteronormativity (hackerspace?)
>

#### information &/or intelligence (situated, embodied knowledge)
>

#### justice, transformative
>

#### k (Kimberlé Crenshaw?)
>

#### l (Ada Lovelace?)
>

#### m (materiality? model something?)
>

#### nonbinary
>

#### othering
>

#### p (privacy / power?)
>

#### queering / queer theory
>

#### race, racialization, race as a technology
>

#### sustainability
>

#### trans rights, transfeminism, transhumanism
>

#### unknowability
>

#### value
>

#### white supremacy, white feminism
>

#### xenofeminism (...vs yt feminism?)
>

#### Y & ...Z
#### REFERENCES

*[Dunbar-Hester]: Dunbar-Hester, C. 2020. Hacking Diversity. Princeton UP.

repository: crosssenses/intersectionalai

repo_name: crosssenses/intersectionalai


text:
#Modules

Modules are building blocks of web-application using Catberry framework.
Usually modules are placed in `/catberry_modules` directory. Or you can override it
if set `modulesFolder` parameter in Catberry config.

##How to add modules
There are some rules how to add modules to your application:

* It always should be module `main` and its placeholder `__index.dust` with
template of whole application page (html, head, body etc)
* In fact every module is a directory, name of directory is a name of module
* Module can optionally have a logic (can just has templates), if so
it should have `index.js` that exports module constructor
* Module can optionally have placeholders, if so it should have `placeholders`
directory inside with [dustjs](https://github.com/linkedin/dustjs) templates.
Placeholders can be placed in sub-directories but with unique names

Please keep in mind that module name (directory name) should satisfy regular
expression `^[a-z]+[a-z0-9-]*$`.

##Module context
Every module instance always has `$context` property which is assigned by
Catberry when module initializes. Catberry updates `$context` every time when the
state of application is changed.

At server Catberry creates new instance of module for every incoming
request (but call constructor only once) therefore `$context` object is different
for every incoming HTTP request and represents URL parameters.

In browser Catberry creates module once and create `$context` at the same time.
Then just update state of `$context` every time user clicks link with URLs
inside the application.

##ModuleBase
Also it can be really useful to inherit your module from [catberry-module]
(https://www.npmjs.org/package/catberry-module). It is a base module
implementation with "smart method invocation" that reduce all this code that
should decide what logic to execute by placeholder, event or form name.

##Example of application structure
Typically directory structure of your application should look like this:
```
catberry_modules/
	main/
		placeholders/
			__index.dust # root placeholder (page template)
			__error.dust # error placeholder to replace errors in release mode
			placeholder1.dust
			placeholder2.dust
			...
			placeholderN.dust
		MainModule # main module implementation
		index.js # just module.exports = require('./MainModule');
	module1/
		placeholders/
			__error.dust # error placeholder to replace errors in release mode
			placeholder1.dust
			placeholder2.dust
			...
			placeholderN.dust
		ModuleConstructor # module implementation
		index.js # just module.exports = require('./ModuleConstructor');
	...
	moduleN/
lib/ # directory for your own external non-catberry components/services
public/ # this directory is default destination for browser bundle building
client.js # browser initial script
server.js # connect server start script
routes.js # definition of URL route definitions
events.js # definition of event route definitions
```

##Module code watch and reload
By default Catberry works in debug mode and it means that all changes in code
of your modules will automatically reload modules in runtime. You can switch it
to release mode passing `isRelease: true` parameter in config of Catberry
application like this:

```javascript
var catberry = require('catberry'),
cat = catberry.create({isRelease: true}),
```

If you want to see finished application as an example then please proceed to
[example directory](https://github.com/catberry/catberry-cli/tree/master/templates/example).

Read next:

* [Placeholders](placeholders.md)

Read also:

* [Render Method](render-method.md)
* [Handle Method](handle-method.md)
* [Submit Method](submit-method.md)
* [Context](context.md)

repository: rakesh-mohanta/catberry

repo_name: rakesh-mohanta/catberry


text:
# Agaricus dilatatus var. dilatatus Fr., 1815 VARIETY

#### Status
SYNONYM

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

#### Published in
Observ. mycol. (Havniae) 1: 40 (1815)

#### Original name
Agaricus dilatatus var. dilatatus Fr., 1815

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Basidiomycota/Agaricomycetes/Agaricales/Mycenaceae/Mycena/Mycena stylobates/ Syn. Agaricus dilatatus dilatatus/README.md

repo_name: mdoering/backbone


text:
# jnj-testing-device-tracker
Johnson & Johnson web application to keep track of testing devices.

### Features
- Create account
- Modify account
- Sign-in account
#### User can also
- Display a list of devices currently in storage
- Be able to add and remove devices
- Be able to check-in/out a device to/from storage
- Give good user feedback on the status of all devices
- Save updates to a database of your choosing
- Run without issues

## Technologies Used

#### Client side:
     - The client side of this application is built with REACT(Front-end Library) and Context API(state management)
#### Server side:
     - The server side is built on NODE using EXPRESS(web framework) as the server,
	  Mongoose as the ODM(Object Data Modeling) for managing relationships between data, provides schema validation, and is used to translate between objects in code and the representation of those objects in MongoDB

    - Written in ES6 and transpiled down to ES5 with BABEL

     - API's is RESTful

#### Style checking and best pratice
    - ESLINT, which is configured to Airbnb-base rule

## Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.

#### Installation and Dependencies

You can get the app running locally in the following way:
1.  Install NodeJs [`node`](https://nodejs.org/en/download/), version 5 or greater on your machine

2. Install [`mongodb`](https://docs.mongodb.com/manual/installation/) to your local machine

3. Clone the repository and cd into it

	  ```
    git clone https://github.com/akolliy1/jnj-testing-device-tracker.git
    cd jnj-testing-device-tracker
    ```

 4. Install dependenices

		npm install

		 and

		cd client

		npm install

		cd ../ go out of client folder to run app concurrently

 5. Create an .env file in the root directory of the project

		 In the application copy from .env.sample file and paste into .env file, then replace the env variables

 6.  start the application

		 - npm run dev
		 - Application would be up and running on localhost `.env port`

#### Testing
	`npm run test`


text:
---
layout: default
---

# 1996-05-29 - Re: Philosophy of information ownership

## Header Data

From<EMAIL_ADDRESS>(Timothy C. May)

To<EMAIL_ADDRESS>Message Hash: b4cd79727252513720241781e602aac5fceabc4fca718b79bcf5ee52d2dfaf89

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1996-05-29 07:47:59 UTC

Raw Date: Wed, 29 May 1996 15:47:59 +0800

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Timothy C. May)
Date: Wed, 29 May 1996 15:47:59 +0800
To<EMAIL_ADDRESS>Subject: Re: Philosophy of information ownership
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

At 2:37 AM 5/29/96, Alan Olsen wrote:
>At 12:38 PM 5/28/96 -0700, Bruce Baugh wrote:
>
>>A separate problem arises when the government compels the disclosure of
>>information for one purpose - getting a driver's license, say - and then
>>turns around and sells it to others. It's much harder to either negotiate a
>>new contract or go to a competitor when the other party is a government.
>
>This is a problem in Oregon.  The database of drivers licences and
>registered automobiles is sold openly by the state.  (You can also order a
>copy on CD-ROM from a company based in Oregon as well...)  As far as I know,
>there is no way to opt out of having your name sold to marketing firms.
>These records are routinely purchaced by mail order houses for resale to
>clients all over the country.  The cost is pretty minimal (under $200) and
>you have to provide the media (usually two 9-track tapes).  The database
>includes current address, vehicle licence number and the type of car that
>you own (among other things).

As I said, I favor "data privacy laws" when they deal with government use
of mandatory data (but not in the case of illegalizing the mere
"remembering" of data obtained non-coercively).

The problem has been made worse by "revenue enhancement" policies by
various govenmental agencies. Local and regional governments have
discovered they can make a few extra bucks by selling data bases they
acquired through government power.

Here in California there are restrictions on DL records, following the use
of DL records to allow a guy to track down an actress, Rebecca Shaefer, and
then kill her.

(But this doesn't stop such abuses. A couple of years ago I obtained the
NLETS (National Law Enforcement Telecommunications System) printout for the
extremely reclusive and unseen-since-1957 author Thomas Pynchon. He lived a
few miles from me, in Aptos, on an old logging road.)

The problem of government records being "open to the public" of course is a
two-edged sword. We want government to not operate in secret on the one
hand, but we are naturally horrified when it is possible to go to the right
office of government and look at lists of all the women who received
abortions in county hospitals.

I place no faith in government to protect my privacy.

--Tim May

Boycott "Big Brother Inside" software!
We got computers, we're tapping phone lines, we know that that ain't allowed.
---------:---------:---------:---------:---------:---------:---------:----
Timothy C. May              | Crypto Anarchy: encryption, digital money,
<EMAIL_ADDRESS>408-728-0152 | anonymous networks, digital pseudonyms, zero
W.A.S.T.E.: Corralitos, CA  | knowledge, reputations, information markets,
Licensed Ontologist         | black markets, collapse of governments.
"National borders aren't even speed bumps on the information superhighway."

{% endraw %}
```

## Thread

+ Return to [May 1996](/archive/1996/05)

+ Return to<EMAIL_ADDRESS>(Timothy C. May)](/authors/tcmay_at_got_net_timothy_c_may_)"

+ 1996-05-29 (Wed, 29 May 1996 15:47:59 +0800) - Re: Philosophy of information ownership -<EMAIL_ADDRESS>(Timothy C. May)_


text:
# Data Lock Events API

Data lock events is a feed of changes that have happened to the data lock results. A new record is added to the API every time a data lock status change occurs, and will include details of what has changed since the last event. The first event for a record will include the initial data lock status (success or failure) and all relevant information including a list of all related errors.

## Getting data lock events

Getting data lock events can be done by consuming the following URI:

    GET https://host:port/api/datalock?sinceEventId={since_event_id}&sinceTime={since_time}&employerAccountId={employer_account_id}&ukprn={ukprn}page={page_number}

Where:
* since_event_id = (Optional) The event id that you want to read from. This is non-inclusive.
* since_time = (Optional) The time that you want to read from. This is non-inclusive.
* employer_account_id = (Optional) employer account identifier to filter by, i.e. 12345. Default is null / no filter.
* ukprn = (Optional) learning provider ukprn to filter by, i.e. 12345. Default is null / no filter.
* page_number = (Optional) page number to display, i.e. 10. Default is 1.

Note: You may specify since_event_id, since_time or neither. You may not specify both.

Response:
```json
{
  "PageNumber": 1,
  "TotalNumberOfPages": 1,
  "Items": [
    {
      "Id": 1,
      "ProcessDateTime": "2017-02-09T15:45:30",
      "IlrFileName": "ILR-123456",
      "Ukprn": 123456,
      "Uln": 123,
      "LearnRefNumber": "Lrn-001",
      "AimSeqNumber": 1,
      "PriceEpisodeIdentifier": "25-27-01/05/2017",
      "ApprenticeshipId": 1,
      "EmployerAccountId": 999,
      "EventSource": "Submission",
      "HasErrors": true,
      "IlrStartDate": "2017-05-01T00:00:00",
      "IlrStandardCode": 27,
      "IlrTrainingPrice": 12000,
      "IlrEndpointAssessorPrice": 3000,
      "Errors": [
        {
          "ErrorCode": "ERR09",
          "SystemDescription": "Mismatch on price"
        }
      ],
      "Periods": [
        {
          "ApprenticeshipVersion": 99,
          "Period": {
            "Id": "1617-R10",
            "Month": 5,
            "Year": 2017
          },
          "IsPayable": false,
          "TransactionType": "Learning"
        },
        {
          "ApprenticeshipVersion": 99,
          "Period": {
            "Id": "1617-R11",
            "Month": 6,
            "Year": 2017
          },
          "IsPayable": false,
          "TransactionType": "Learning"
        },
        {
          "ApprenticeshipVersion": 99,
          "Period": {
            "Id": "1617-R12",
            "Month": 7,
            "Year": 2017
          },
          "IsPayable": false,
          "TransactionType": "Learning"
        }
      ],
      "Apprenticeships": [
        {
          "Version": 99,
          "StartDate": "2017-05-01T00:00:00",
          "StandardCode": 27,
          "NegotiatedPrice": 17500,
          "EffectiveDate": "2017-05-01T00:00:00"
        }
      ]
    },
    {
      "Id": 2,
      "ProcessDateTime": "2017-02-09T09:10:23",
      "IlrFileName": "ILR-654321",
      "Ukprn": 654321,
      "Uln": 321,
      "LearnRefNumber": "Lrn-100",
      "AimSeqNumber": 0,
      "PriceEpisodeIdentifier": "20-550-6-01/06/2017",
      "ApprenticeshipId": 9,
      "EmployerAccountId": 456,
      "EventSource": "PeriodEnd",
      "HasErrors": false,
      "IlrStartDate": "2017-06-01T00:00:00",
      "IlrProgrammeType": 20,
      "IlrFrameworkCode": 550,
      "IlrPathwayCode": 6,
      "IlrTrainingPrice": 6000,
      "IlrEndpointAssessorPrice": 1500,
      "Errors": [],
      "Periods": [
        {
          "ApprenticeshipVersion": 17,
          "Period": {
            "Id": "1617-R11",
            "Month": 6,
            "Year": 2017
          },
          "IsPayable": true,
          "TransactionType": "Learning"
        },
        {
          "ApprenticeshipVersion": 25,
          "Period": {
            "Id": "1617-R12",
            "Month": 7,
            "Year": 2017
          },
          "IsPayable": false,
          "TransactionType": "Learning"
        }
      ],
      "Apprenticeships": [
        {
          "Version": 17,
          "StartDate": "2017-06-01T00:00:00",
          "ProgrammeType": 20,
          "FrameworkCode": 550,
          "PathwayCode": 6,
          "NegotiatedPrice": 7500,
          "EffectiveDate": "2017-06-01T00:00:00"
        },
        {
          "Version": 25,
          "StartDate": "2017-06-01T00:00:00",
          "ProgrammeType": 20,
          "FrameworkCode": 550,
          "PathwayCode": 6,
          "NegotiatedPrice": 7500,
          "EffectiveDate": "2017-07-15T00:00:00"
        }
      ]
    }
  ]
}
```

Response **Items** structure:

| Attribute | Data type | Optional | Description |
| --- | --- | --- | --- |
| Id | long | no | event unique identifier |
| ProcessDateTime | DateTime | No | event creation date and time |
| IlrFileName | string | no | name of the related ilr file |
| Ukprn | long | no | learning provider's ukprn |
| Uln | long | no | learner's unique number |
| LearnRefNumber | string | no | learner unique identifier inside the ilr file |
| AimSeqNumber | long | no | learner's unique learning aim sequence number inside the ilr file |
| PriceEpisodeIdentifier | string | no | learning price episode unique identifier for the ilr file |
| ApprenticeshipId | long | no | matched apprenticeship unique identifier |
| EmployerAccountId | long | no | matched apprenticeship's employer account unique identifier |
| EventSource | EventSource | no | source of the data lock event: **Submission** (generated by an ilr submission) or **PeriodEnd** (generated by a period end run) |
| HasErrors | bool | no | flag indicating whether the data lock event represents success or failure |
| IlrStartDate | DateTime | yes | ilr price episode start date |
| IlrStandardCode | long | yes | ilr price episode standard code |
| IlrProgrammeType | int | yes | ilr price episode programme type |
| IlrFrameworkCode | int | yes | ilr price episode frameworh code |
| IlrPathwayCode | int | yes | ilr price episode pathway code |
| IlrTrainingPrice | decimal | yes | ilr price episode training price |
| IlrEndpointAssessorPrice | decimal | yes | ilr price episode endpoint assessor price |
| Errors | DataLockEventError[] | no | event's list of errors, see following table for structure |
| Periods | DataLockEventPeriod[] | no | event's list of ilr collection periods, see following table for structure |
| Apprenticeships | DataLockEventApprenticeship[] | no | event's list of matched apprenticeships, see following table for structure |

**Errors** structure:

| Attribute | Data type | Optional | Description |
| --- | --- | --- | --- |
| ErrorCode | string | no | error code |
| SystemDescription | string | no | error description |

**Periods** structure:

| Attribute | Data type | Optional | Description |
| --- | --- | --- | --- |
| ApprenticeshipVersion | long | no | apprenticeship version |
| Period | NamedCollectionPeriod | no | ilr collection period containing an id, calendar month and calcndar year |
| IsPayable | bool | no | whether any earnings against the period will be paid or not |
| TransactionType | TransactionType | no | the type of payment the period relates to; see the following tables for all possible values |

**Apprenticeships** structure:

| Attribute | Data type | Optional | Description |
| --- | --- | --- | --- |
| Version | long | no | apprenticeship version |
| StartDate | DateTime | no | apprenticeship funding start date |
| StandardCode | long | yes | apprenticeship standard code |
| ProgrammeType | int | yes | apprenticeship programme type |
| FrameworkCode | int | yes | apprenticeship framework code |
| PathwayCode | int | yes | apprenticeship pathway code |
| NegotiatedPrice | decimal | no | apprenticeship negotiated price |
| EffectiveDate | DateTime | no | apprenticeship change effective from date |

**TransactionType** values:

| Value | Description |
| --- | --- |
| Learning | on programme payment |
| Completion | completion payment |
| Balancing | balancing payment |
| First16To18EmployerIncentive | first 16-18 employer incentive payment |
| First16To18ProviderIncentive | first 16-18 provider incentive payment |
| Second16To18EmployerIncentive | second 16-18 employer incentive payment |
| Second16To18ProviderIncentive | second 16-18 provider incentive payment |
| OnProgramme16To18FrameworkUplift | 16-18 framework uplift on programme payment |
| Completion16To18FrameworkUplift | 16-18 framework uplift completion payment |
| Balancing16To18FrameworkUplift | 16-18 framework uplift balancing payment |
| FirstDisadvantagePayment | first provider disadvantage payment |
| SecondDisadvantagePayment | second provider disadvantage payment |
| OnProgrammeMathsAndEnglish | maths or english on programme payment |
| BalancingMathsAndEnglish | maths or english balancing payment |
| LearningSupport | learning support payment |

## Using the client

A .NET client also exists to easy calling the api and encapsulates the authentication and deserialization. It can be added from nuget:

```powershell
Install-Package SFA.DAS.Provider.Events.Api.Client
```

And then called by:

```csharp
var config = new PaymentsEventsApiConfiguration
{
    ClientToken = "YOUR_JWT_TOKEN",
    ApiBaseUrl = "https://some-server/"
};
var client = new PaymentsEventsApiClient(config);
var dataLockEvents = await client.GetDataLockEvents();
// The above also optionally takes sinceEventId, sinceTime, employerAccountId, ukprn and page, e.g.
// var dataLockEvents = await client.GetDataLockEvents(sinceEventId: 123, page: 2);
// var dataLockEvents = await client.GetDataLockEvents(sinceTime: lastPollTime, page: 2);
// var dataLockEvents = await client.GetDataLockEvents(employerAccountId: 123, page: 2);
// var dataLockEvents = await client.GetDataLockEvents(ukprn: 456, page: 2);
```

repository: SkillsFundingAgency/das-providerevents

gha_language: C#

repo_name: SkillsFundingAgency/das-providerevents


text:
# Cloud Security Alliance

![matrix](images/07-csa.png)

cybersecurity control framework for cloud computing\
197 control objectives that are structured in 17 domains\
[CAIQ Questionnaire](https://cloudsecurityalliance.org/artifacts/consensus-assessments-initiative-questionnaire-v3-1/):
Consensus Assessment Initiative Questionnaire\
[STAR Security Trust Assurance and Risk Registry](https://cloudsecurityalliance.org/star/)

repository: murriel/cloudnativesectools

repo_name: murriel/cloudnativesectools


text:
# affected_on_destroy

affected_on_destroy is a simple Rails plugin that recursively reflects on defined associations and lets you know which records will be deleted/nullified when using :dependent => :destroy or :dependent => :nullify.

## Installation

    config.gem 'murbanski-affected_on_destroy', :lib => 'affected_on_destroy', :source => 'http://gems.github.com'

## Usage

schema.rb:

	create_table "users", :force => true do |t|
	  t.string   "login"
	  t.string   "password"
	  t.datetime "created_at"
	  t.datetime "updated_at"
	end

	create_table "blogs", :force => true do |t|
	  t.integer  "user_id"
	  t.string   "name"
	  t.datetime "created_at"
	  t.datetime "updated_at"
	end

	create_table "posts", :force => true do |t|
	  t.integer  "blog_id"
	  t.text     "content"
	  t.datetime "created_at"
	  t.datetime "updated_at"
	end

models:

	class User < ActiveRecord::Base
	  has_many :blogs, :dependent => :destroy
	end

	class Blog < ActiveRecord::Base
	  belongs_to :user
	  has_many :posts, :dependent => :nullify
	end

	class Post < ActiveRecord::Base
	  belongs_to :blog
	end

Sample script/console session:

	>>  marcin = User.create(:login => 'marcin', :password => 'my_pass')
	=> #<User id: 1, login: "marcin", password: "my_pass", created_at: "2009-06-26 01:47:36", updated_at: "2009-06-26 01:47:36">

	>> blog = marcin.blogs.create(:name => 'My Ruby Blog')
	=> #<Blog id: 1, user_id: 1, name: "My Ruby Blog", created_at: "2009-06-26 01:47:57", updated_at: "2009-06-26 01:47:57">

	>> blog.posts.create(:content => 'Ruby tricks #1')
	=> #<Post id: 1, blog_id: 1, content: "Ruby tricks #1", created_at: "2009-06-26 01:48:40", updated_at: "2009-06-26 01:48:40">
	>> blog.posts.create(:content => 'Ruby tricks #2')
	=> #<Post id: 2, blog_id: 1, content: "Ruby tricks #2", created_at: "2009-06-26 01:48:45", updated_at: "2009-06-26 01:48:45">

What records will be affected when we destroy user 'marcin'?

	>> marcin.affected_on_destroy
	=> [#<Blog id: 1, user_id: 1, name: "My Ruby Blog", created_at: "2009-06-26 01:47:57", updated_at: "2009-06-26 01:47:57">,
	#<Post id: 1, blog_id: 1, content: "Ruby tricks #1", created_at: "2009-06-26 01:48:40", updated_at: "2009-06-26 01:48:40">,
	#<Post id: 2, blog_id: 1, content: "Ruby tricks #2", created_at: "2009-06-26 01:48:45", updated_at: "2009-06-26 01:48:45">]

Which models are affected when destroying user?

	>> User.affected_on_destroy
	=> ["Blog", "Post"]

Same for blog:

	>> Blog.affected_on_destroy
	=> ["Post"]

## Rails Version

Works on Rails 2.3 and 2.2


text:
bullseye0
=======

These images make up the bullseye0 stack for Toolforge's buildpacks, which are
in the [`cloud/toolforge/buildpacks`](https://gerrit.wikimedia.org/g/cloud/toolforge/buildpacks) repository.

These images should be compliant with the [buildpacks spec](https://github.com/buildpacks/spec/blob/main/platform.md#stacks).


text:
# $loop

This function creates a loop and executes an awaited command X amount of times

```javascript
$loop[how many;awaited command]
```

> ❗ bot.awaitedCommand is needed.

```javascript
bot.command({
        name: "Say Hello 3 times",
        code: `$loop[3;hello]`
})

bot.awaitedCommand({
       name: "hello",
       code: `hi user!`
})
//The bot would return 'hi user!' 3 times
```

repository: XzFirzal/documentation

repo_name: XzFirzal/documentation


text:
## What's new

<!-- NOTE: Pull request title should be "<package>: <summary>", if the PR affects multiple
  packages, use the main package that it affects. If the PR does not target any specific
  packages, use general tags like "ci" or "versioning". -->

<!-- uncomment the next line if this PR fixes an issue -->
<!-- fixes #<issue-id> -->

<!-- Describe your changes.

  If your changes affects the UI, show screenshots or videos.

  If your changes affects, or is affected by other RMF components outside of this repo,
  describe how the components interact.

  If your changes fixes a bug, describe the root cause of the bug and how the
  proposed solution fixes it.

  If you went through several iterations while making this PR, explain why you
  prefer the proposed solution.
-->

## Self-checks

- [ ] I have prototyped this new feature (if necessary) on Figma
- [ ] I'm familiar with and follow this [Typescript guideline](https://basarat.gitbook.io/typescript/styleguide)
- [ ] I added unit-tests for new components
- [ ] I tried testing edge cases
- [ ] I tested the behavior of the components that interact with the backend, with an e2e test

## Discussion

<!-- Questions for reviewers, if any -->

repository: apiyap/rmf-web

repo_name: apiyap/rmf-web


text:
# SimpleSecureBoot
RSA based secure boot for embedded devices

## Dependencies
### Python3
Python3 is used to signed the hex file.

### Python3 intelhex
On ubuntu:

    pip3 install --user intelhex

### Optional: Python3 pycryptodome
This is needed only if you want to generate keys using `genrsakey.py`.
On ubuntu:

    pip3 install --user pycryptodome

## Test
A self test is provided, to run it type the following:

    ./test.py

## Usage
### Create a key pair:
* Generate a key using `genrsakey.py` (or any other method).
* Place the generate output in key file.

One command does everything:

    ./genrsakey.py > mykey

### Integrate in boot code
* Include the C99 header files in the firmware which resides in internal memory.
* Call the `ssb_check_sig` function to validate an incoming image.

### Sign an image
Use `ssb.py` to sign the hex file:

    ./ssb.py <start address> <size> <hex file> <key file>

This will compile the C99 test code to make sure it verify this signature correctly.

If this check fails, `ssb.py` output the key as it should appear in `ssb_pub_key.h`. Update this file accordingly and try again, `ssb.py` output should then end by "sig match".

repository: sebastien-riou/SimpleSecureBoot

repo_name: sebastien-riou/SimpleSecureBoot


text:
---
title: OpenShift
parent: Upgrading configs
nav_order: 2
---

# Upgrading OpenShift configs

Occasionally, changes are made to OpenShift Butane configs (those that specify `variant: openshift` or, historically, `variant: rhcos`) that break backward compatibility. While this is not a concern for running machines, since Ignition only runs one time during first boot, it is a concern for those who maintain configuration files. This document serves to detail each of the breaking changes and tries to provide some reasoning for the change. This does not cover all of the changes to the spec - just those that need to be considered when migrating from one version to the next.

{: .no_toc }

1. TOC
{:toc}

## From Version 4.8.0 to Version 4.9.0

There are no functionality changes between versions 4.8.0 and 4.9.0 of the `openshift` configuration specification. Any valid 4.8.0 configuration can be updated to a 4.9.0 configuration by changing the version string in the config.

## From `rhcos` Version 0.1.0 to `openshift` Version 4.8.0

The new `openshift` config variant is intended to work both on the OpenShift Container Platform with RHEL CoreOS, and on OKD with Fedora CoreOS. The `rhcos` variant is still accepted by Butane but will not receive new features.

The `openshift` 4.8.0 specification is not backward-compatible with the `rhcos` 0.1.0 specification. It adds new mandatory metadata fields and removes certain Ignition config fields. In addition, `openshift` configs are transpiled to an OpenShift [MachineConfig] rather than an Ignition config by default. A valid `rhcos` 0.1.0 configuration can be updated to an `openshift` 4.8.0 configuration by changing the variant and version strings and then correcting any errors reported during transpilation.

The following is a list of breaking changes and notable new features.

### MachineConfig generation

By default, Butane transpiles an `openshift` Butane config into an OpenShift [MachineConfig]. Butane produces an Ignition config if the `-r` or `--raw` option is specified on the Butane command line.

### Removed config fields

The config no longer allows certain Ignition config fields that are rejected or discouraged by the OpenShift [Machine Config Operator].

In the `storage` section, `directories` and `links` are removed, along with `append` in `files`. Local file trees referenced in `trees` must not contain symlinks.

In the `passwd` section, `groups` is removed. All fields in `users` are removed except for `name` (which must be set to `core`) and `ssh_authorized_keys`.

### MachineConfig metadata fields

The config gained a new top-level `metadata` section containing metadata for the generated [MachineConfig]. The mandatory `name` field specifies a [name for the Kubernetes MachineConfig resource][k8s-names]. The `labels` field specifies a map of key-value pairs to be applied to the MachineConfig resource as [Kubernetes labels][k8s-labels]. The `machineconfiguration.openshift.io/role` label is required.

The `metadata` section is ignored when generating a raw Ignition config using the `-r` or `--raw` option.

<!-- butane-config -->
```yaml
variant: openshift
version: 4.8.0
metadata:
  name: minimal-config
  labels:
    machineconfiguration.openshift.io/role: worker
```

### MCO settings

The config gained a new top-level `openshift` section specifying [configuration][MCO settings] for the [Machine Config Operator]. The `extensions` field lists [RHCOS extension modules] to be installed on the node. The `fips` field enables [FIPS mode] when set to `true`. The `kernel_arguments` field specifies a list of [arguments][kernel arguments] to be added to the kernel command line. The `kernel_type` field can be set to `realtime` to use the [real-time kernel] on the node.

Fields in the `openshift` section are not included in a raw Ignition config generated using the `-r` or `--raw` option.

<!-- butane-config -->
```yaml
variant: openshift
version: 4.8.0
metadata:
  name: config-openshift
  labels:
    machineconfiguration.openshift.io/role: worker
openshift:
  extensions:
    - usbguard
  fips: true
  kernel_arguments:
    - console=ttyS1,115200
  kernel_type: realtime
```

### FIPS configuration for LUKS

When the `fips` field in the `openshift` section is set to `true`, LUKS volumes specified in the config (but not in any referenced configs) are configured to use a cipher compatible with [FIPS 140-2]. This cipher is applied to LUKS volumes specified in the `luks` subsections of the `storage` and `boot_device` sections.

<!-- butane-config -->
```yaml
variant: openshift
version: 4.8.0
metadata:
  name: fips-luks
  labels:
    machineconfiguration.openshift.io/role: worker
openshift:
  fips: true
boot_device:
  luks:
    tpm2: true
```

[FIPS 140-2]: https://csrc.nist.gov/publications/detail/fips/140/2/final
[FIPS mode]: https://docs.openshift.com/container-platform/4.7/installing/installing-fips.html
[k8s-names]: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
[k8s-labels]: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/
[kernel arguments]: https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#nodes-nodes-kernel-arguments_post-install-machine-configuration-tasks
[Machine Config Operator]: https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#understanding-the-machine-config-operator
[MachineConfig]: https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#machine-config-overviewpost-install-machine-configuration-tasks
[MCO settings]: https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#what-can-you-change-with-machine-configs
[real-time kernel]: https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#nodes-nodes-rtkernel-arguments_post-install-machine-configuration-tasks
[RHCOS extension modules]: https://docs.openshift.com/container-platform/4.7/post_installation_configuration/machine-configuration-tasks.html#rhcos-add-extensions_post-install-machine-configuration-tasks

repository: nikita-dubrovskii/butane

repo_name: nikita-dubrovskii/butane


text:
# sunnys:matomo
Meteor package that allows you to use Matomo Analytics with your application.

An improved fork of https://github.com/vjrj/piwik/, https://github.com/appjitsu/piwik/ and https://github.com/DavidSichau/piwik/ . Thanks for the great work.

This package uses matomo-tracker (https://www.npmjs.com/package/matomo-tracker).

NOTE: NPM package piwik-tracker is deprecated. Migraation from piwik-tracker to matomo-tracker.

#### Installation

```
meteor add ssunnys:matomo
```

#### Setup

Add the following Environmentsvariables
```
MATOMO_URL = `http://your_matomo_server_url/matomo.php"`
MATOMO_SITE_ID = `0`
MATOMO_TOKEN = `<YOUR SECRET MATOMO TOKEN>`

```

or via [settings.json](https://github.com/vjrj/matomo/blob/master/settings.json).

#### Usage

On the client serveral helpers functions are provided to track different statistics.

Before any tracking you should call the helper `setUserInfo` with the current UserId or with null.
This helper collects data like the user Agent the referral and the resolution of the users device.

```
Meteor.startup(function() {
    return Tracker.autorun(function() {
        var userId;
        userId = Meteor.userId();
        Meteor.Matomo.setUserInfo(userId);
    });
});
```

To track a specific site use the following method:
```
// to track page in your router (onRun hook)
Meteor.Matomo.trackPage(Router.current().route.path(this));
```

To track a download use:
```
Meteor.Matomo.trackDownload(downloadUrl);
```

To track a external Link use:
```
Meteor.Matomo.trackLink(linkUrl);
```

To track a search use:
```
Meteor.Matomo.trackSearch(url, {
    search: 'my cool keyword', // the search term
    search_cat: 'page search', //the category of the search
    search_count: '42' //the number of search results

});
```

To track a goal use:
```
Meteor.Matomo.trackGoal(url, goalId)
```

```
// track an event
Meteor.Matomo.trackEvent(
	Router.current().route.path(this), // the route: ie - /home, not the full url
	{
		category: "Page or Section",
		action: "Viewed|Completed|Submitted|Etc",
		name: "Name of the Event - Submitted Contact Form",
		value: "Optional Value - like how many rows saved, etc."
	},
	{// any number of extra optional values.
	 // Pass null if you do not want to pass additional values
		"1": ["Name", "Value", "page|visit"],
		"2": ["Name", "Value", "page|visit"],
		"3": ["Name", "Value", "page|visit"],
		"4": ["Name", "Value", "page|visit"],
		"5": ["Name", "Value", "page|visit"],
		"6": ["Name", "Value", "page|visit"]
	}
);
```

#### Additional Matomo Documentation:

For trackEvent and trackPageView:
http://developer.matomo.org/api-reference/tracking-javascript
http://developer.matomo.org/api-reference/tracking-api

	- trackEvent(category, action, [name], [value]) - Logs an event with an event category (Videos, Music, Games...), an event action (Play, Pause, Duration, Add Playlist, Downloaded, Clicked...), and an optional event name and optional numeric value.
	- trackPageView([customTitle]) - Logs a visit to this page

For custom event variables:
http://matomo.org/blog/2012/10/using-custom-variables-in-matomo-tutorial

repository: sunnys/matomo

repo_name: sunnys/matomo


text:
# _nichtparasoup_ ImageCrawler: Placeholders

[![shield_gh-workflow-test]][link_gh-workflow-test]
[![shield_sonar-quality]][link-sonar-dashboard]
[![shield_sonar-coverage]][link_sonar-coverage]

----

This is an example plugin for [_nichtparasoup_](https://pypi.org/project/nichtparasoup/).
Purpose of this project is, to give ImageCrawler plugin developers a kick start.

This project includes:
* simple demo implementation [`nichtparasoup_placeholders`](src)
* _nichtparasoup_ [example config](examples)
* some **minimal** [`docs`](docs)
* rules fo static code analysis and type-checks via `mypy`
* preparation for unit tests via `pytest`
* **minimal** setup config [`setup.cfg`](setup.cfg)
* some **minimal** project setup configs

For details how to write a ImageCrawler plugins,
see the [dedicated docs](../python-package/docs/dev/plugin-development/index.md).

[shield_gh-workflow-test]: https://img.shields.io/github/workflow/status/k4cg/nichtparasoup/Test%20PythonPluginExample/3.0-dev?logo=GitHub&logoColor=white "test status"
[shield_sonar-quality]: https://img.shields.io/sonar/quality_gate/nichtparasoup:PythonPluginExample?server=https%3A%2F%2Fsonarcloud.io&logo=SonarCloud&logoColor=white "quality"
[shield_sonar-coverage]: https://img.shields.io/sonar/coverage/nichtparasoup:PythonPluginExample?server=https%3A%2F%2Fsonarcloud.io&logo=SonarCloud&logoColor=white "coverage"
[link_gh-workflow-test]: https://github.com/k4cg/nichtparasoup/actions?query=workflow%3A%22Test+PythonPluginExample%22+branch%3A3.0-dev
[link-sonar-dashboard]: https://sonarcloud.io/dashboard?id=nichtparasoup%3APythonPluginExample
[link_sonar-coverage]: https://sonarcloud.io/component_measures?id=nichtparasoup%3APythonPluginExample&metric=coverage


text:
---
title: When is the font size not the font size?
date: '2016-12-07 14:06:19'
modified: '2016-12-07 14:08:45'
complete: false
inprogress: true
tags:
  - web
draft: true
---
# When is the font size not the font size?

A: When it's stuck to the chicken's foot.

Wait, no. That's not it. I've run into the same problem a few times, so I wanted to document the problem (the way I see it) and the variations on potential factors that cause a font size to adjust to a different size than expected.

<!--more-->

## initial-size


text:
# Bounceless Python API

This Python client allows you to interact with the Bounceless.io API for email verification. The client supports the following features:

1. Single email verification
2. Bulk email verification from a CSV file
3. Fetching verification results for a file

## Installation

Clone this repository to your local machine:

```bash
git clone https://github.com/bounceless/Bounceless-Python.git
```

## Usage

Import the necessary classes from the `emailverify` module:

```python
from emailverify import BouncelessOne, BouncelessBulk
```

### Single Email Verification

Use the `BouncelessOne` class to verify a single email. You will need to provide your API key and the email you wish to verify:

```python
def verify_single_email():
    # Replace 'YOUR_KEY' with your actual API key
    # Replace<EMAIL_ADDRESS>with the actual email you want to verify
    bounceless_one = BouncelessOne('YOUR_KEY'<EMAIL_ADDRESS>    response = bounceless_one.control()
    print(response)
```

### Bulk Email Verification

Use the `BouncelessBulk` class to verify a bulk of emails from a CSV file. Provide your API key and the path to the CSV file:

```python
def verify_bulk_emails():
    # Replace 'YOUR_KEY' with your actual API key
    # Replace 'path/to/file.csv' with the actual path to your CSV file
    bounceless_bulk = BouncelessBulk('YOUR_KEY', 'path/to/file.csv')
    bounceless_bulk.upload()
```

### Fetching Verification Results

After a bulk upload, fetch the verification results using the `get_info()` method from the `BouncelessBulk` class. This method can also be used independently by providing the ID of a previously uploaded file:

```python
def get_bulk_info():
    # Replace 'YOUR_KEY' with your actual API key
    # Replace 'FILE_ID' with the actual ID of your uploaded file
    bounceless_bulk = BouncelessBulk('YOUR_KEY', 'FILE_ID')
    response = bounceless_bulk.get_info()
    print(response)
```

Finally, call these functions in your main script:

```python
if __name__ == '__main__':
    verify_single_email()
    verify_bulk_emails()
    get_bulk_info()
```

## License

This project is licensed under the terms of the MIT license.

repository: bounceless/Bounceless-Python

repo_name: bounceless/Bounceless-Python


text:
```ps1

###########################################################
$SmtpServer =    "localhost"
$EmailFrom  =    "From Address<EMAIL_ADDRESS>$EmailTo    =<EMAIL_ADDRESS>
###########################################################

$Logfile = "log.txt"
$hostname = hostname
$Subject = "[ROBOCOPY] $hostname"
$Body = "Robocopy completed successfully. See attached log file for details"

# Backup
Robocopy E:\SOURCE Z:\DESTINATION /MT:32 /MIR /FFT /Z /XA:H /W:5 /LOG:$Logfile /NP

$Message = New-Object Net.Mail.MailMessage($EmailFrom, $EmailTo, $Subject, $Body)
$Attachment = New-Object Net.Mail.Attachment($Logfile, 'text/plain')
$Message.Attachments.Add($Attachment)

$SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 25)
$SMTPClient.Send($Message)
```

repository: poizon-box/til

repo_name: poizon-box/til


text:
# CHANGELOG

## 1.1.0

* Change supported mail version to 2.8.
* Drop support for ruby 2.3 and 2.4.

## 1.0.10

* Prefer header charset for encoding filename.
* Avoid encoding extra options to attachment header.
* Remove unnecessary charset from content type.

## 1.0.9

* Fix mail version to < 2.8.0.

## 1.0.8

* Don't separate escape sequence for b encoding.

## 1.0.7

* Fix deprecation warning for ruby 2.7.

## 1.0.6

* Remove rfc2231 key from options hash.

## 1.0.5

* Force us-ascii for only iso-2022-jp.

## 1.0.4

* Add rfc2231 option per mail and make false globally.
* Fix charset comparison.

## 1.0.3

* Fix for copy of headers.

## 1.0.2

* Fix unstructured field encoding.

## 1.0.1

* Fix encoding condition.

## 1.0.0

* First release.

repository: kanety/mail-jenc

gha_language: Ruby

repo_name: kanety/mail-jenc


text:
## Objectives
In this stage, you should write a program that uses the time vulnerability to find the password.

- Use the list of logins from the previous stage.
- Output the result as you did this in the previous stage.

path: /Stage 5-5/README.md


text:
# Great task for Great Fullstack Developer

This app is based on symfony skeleton app.

More information about it you can find here: https://github.com/symfony/symfony-standard

To implement login functionality with GitHub API I was trying to use this library: https://github.com/KnpLabs/php-github-api

While I was developing design of our app I realized how to build pages with ReactJS
(my repository with reactjs code you can find here: )
but it just would take more time for me to refresh my React knowledge, so I decided
to use Twig and CSS.

Dump of test database is in project directory.

# To run this project you need

Run composer install. Also you need to setup a database with provided dump of test data.

repository: PaulTroyanov/fullstack-party

repo_name: PaulTroyanov/fullstack-party


text:
#Statistical testing
2016-06-01

A statistical hypothesis is a hypothesis that is testable framework process to study and compare data assumption of observing a process that are modeled via a set of random variables. A statistical hypothesis test is a method of statistical inference (frequentist and bayesian).

Commonly, two statistical data sets are compared, or a data set obtained by sampling is compared against a synthetic data set from an idealized model. A hypothesis is proposed for the statistical relationship between the two data sets, and this is compared as an alternative to an idealized null hypothesis that proposes no relationship between two data sets. The comparison is deemed statistically significant if the relationship between the data sets would be an unlikely realization of the null hypothesis according to a threshold probability -the significance level. Hypothesis tests are used in determining what outcomes of a study would lead to a rejection of the null hypothesis for a pre-specified level of significance. The process of distinguishing between the null hypothesis and the alternative hypothesis is aided by identifying two conceptual types of errors (type 1 & type 2), and by specifying parametric limits.

### Procedure
So, put it simply:
* Proposing an alternative hypothesis over the relationship between 2 data sets.
* Proposing null hypothesis by selecting and applying a random model over the data.
* Select the test statistic T and the appropiate test to use.
* Using comparison tests to get a measure of confidence.
* Accept or reject the alternative hypothesis.

An alternative framework for statistical hypothesis testing is to specify a set of statistical models, one for each candidate hypothesis, and then use model selection techniques to choose the most appropriate model. The most common selection techniques are based on either Akaike information criterion or Bayes factor.

### Main concepts
The summary of main concepts of hypothesis testing:
* Statistical hypothesis: assumption over parameters describing the population (not the sample which are the observed parameters).
* Statistic: value computed from a sample, often to summarize the sample for comparison purposes.
* Simple hypothesis: any hypothesis which specifies the population distribution completely.
* Null hypothesis (H0): a simple hypothesis based on a random model applied over the sample. It will use to contradict the theory proposed.
* Alternative hypothesis (H1): a hypothesis (often composite) associated with a theory one would like to prove.
* Statistical test: a procedure whose inputs are samples and whose result is a hypothesis.
* Critical value: the threshold value delimiting the regions of acceptance and rejection for the test statistic.
* Power of a test (1 − $\beta$): the test's probability of correctly rejecting the null hypothesis. The complement of the false negative rate, $\beta$. Power is termed sensitivity in biostatistics. ("This is a sensitive test. Because the result is negative, we can confidently say that the patient does not have the condition.")
* Significance level of a test ($\alpha$): it is the upper bound imposed on the size of a test. Its value is chosen by the statistician prior to looking at the data or choosing any particular test to be used. It is the maximum exposure to erroneously rejecting H0 he/she is ready to accept. Testing H0 at significance level α means testing H0 with a test whose size does not exceed α. In most cases, one uses tests whose size is equal to the significance level.
p-value: the probability, assuming the null hypothesis is true, of observing a result at least as extreme as the test statistic.

### Main statistical tests
Some categories:
* One-sample tests are appropriate when a sample is being compared to the population from a hypothesis. The population characteristics are known from theory or are calculated from the population.
* Two-sample tests are appropriate for comparing two samples, typically experimental and control samples from a scientifically controlled experiment.
* Paired tests are appropriate for comparing two samples where it is impossible to control important variables. Rather than comparing two sets, members are paired between samples so the difference between the members becomes the sample. Typically the mean of the differences is then compared to zero. The common example scenario for when a paired difference test is appropriate is when a single set of test subjects has something applied to them and the test is intended to check for an effect.

Possible statistical tests to use:
* Z-tests (assumption of gaussian): comparing means with known variance.
* Welch's t test (assumption of Gaussian distribution).
* Fisher's exact test (assumption of Binomial distribution).
* E-test (assumption Poisson distribution).
* Chi-squared test (assumption of Multinomial distribution).
* Mann-Whitney U test (no assumption of distribution).
* Student's t-tests are appropriate for comparing means under relaxed conditions when less is assumed.

***Tags***: Statistics

#### See also
[Resampling methods](/resampling_methods)
## Papers
* Loftus, G R (1991). [On the Tyranny of Hypothesis Testing in the Social Sciences](https://www.ics.uci.edu/~sternh/courses/210/loftus91_tyranny.pdf). Contemporary Psychology 36 (2): 102-105.

## Books
* Huff, Darrell (1993). [How to lie with statistics](https://www.goodreads.com/book/show/51291.How_to_Lie_with_Statistics). New York: Norton.