text:
/* Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package org.flowable.cmmn.editor.constants;

/**
 * @author Tijs Rademakers
 * @author Joram Barrez
 */
public interface CmmnStencilConstants {

    // stencil items

    String STENCIL_PLANMODEL = "CasePlanModel";
    String STENCIL_STAGE = "Stage";
    String STENCIL_TASK = "Task";
    String STENCIL_TASK_HUMAN = "HumanTask";
    String STENCIL_TASK_SERVICE = "ServiceTask";
    String STENCIL_TASK_DECISION = "DecisionTask";
    String STENCIL_TASK_HTTP = "HttpTask";
    String STENCIL_TASK_CASE = "CaseTask";
    String STENCIL_TASK_PROCESS = "ProcessTask";
    String STENCIL_TASK_SCRIPT = "ScriptTask";
    String STENCIL_MILESTONE = "Milestone";
    String STENCIL_GENERIC_EVENT_LISTENER = "EventListener";
    String STENCIL_TIMER_EVENT_LISTENER ="TimerEventListener";
    String STENCIL_USER_EVENT_LISTENER ="UserEventListener";

    String STENCIL_ENTRY_CRITERION = "EntryCriterion";
    String STENCIL_EXIT_CRITERION = "ExitCriterion";

    String STENCIL_ASSOCIATION = "Association";

    String PROPERTY_VALUE_YES = "Yes";
    String PROPERTY_VALUE_NO = "No";

    // stencil properties

    String PROPERTY_OVERRIDE_ID = "overrideid";
    String PROPERTY_NAME = "name";
    String PROPERTY_DOCUMENTATION = "documentation";

    String PROPERTY_CASE_ID = "case_id";
    String PROPERTY_CASE_INITIATOR_VARIABLE_NAME = "case_initiatorvariablename";
    String PROPERTY_CASE_VERSION = "case_version";
    String PROPERTY_CASE_AUTHOR = "case_author";
    String PROPERTY_CASE_NAMESPACE = "case_namespace";

    String PROPERTY_TIMER_DURATON = "timerdurationdefinition";
    String PROPERTY_TIMER_DATE = "timerdatedefinition";
    String PROPERTY_TIMER_CYCLE = "timercycledefinition";
    String PROPERTY_TIMER_CYCLE_END_DATE = "timerenddatedefinition";

    String PROPERTY_FORMKEY = "formkeydefinition";
    String PROPERTY_FORM_REFERENCE = "formreference";

    String PROPERTY_IS_BLOCKING = "isblocking";
    String PROPERTY_IS_BLOCKING_EXPRESSION = "isblockingexpression";

    String PROPERTY_IS_AUTOCOMPLETE = "autocompleteenabled";
    String PROPERTY_AUTOCOMPLETE_CONDITION = "autocompletecondition";

    String PROPERTY_IS_ASYNC = "isasync";
    String PROPERTY_IS_EXCLUSIVE = "isexclusive";

    String PROPERTY_REQUIRED_ENABLED = "requiredenabled";
    String PROPERTY_REQUIRED_RULE_CONDITION = "requiredrulecondition";

    String PROPERTY_REPETITION_ENABLED = "repetitionenabled";
    String PROPERTY_REPETITION_RULE_CONDITION = "repetitionrulecondition";
    String PROPERTY_REPETITION_RULE_VARIABLE_NAME = "repetitioncountervariablename";

    String PROPERTY_MANUAL_ACTIVATION_ENABLED = "manualactivationenabled";
    String PROPERTY_MANUAL_ACTIVATION_RULE_CONDITION = "manualactivationrulecondition";

    String PROPERTY_COMPLETION_NEUTRAL_ENABLED = "completionneutralenabled";
    String PROPERTY_COMPLETION_NEUTRAL_RULE_CONDITION = "completionneutralrulecondition";

    String PROPERTY_DISPLAY_ORDER = "displayorder";
    String PROPERTY_INCLUDE_IN_STAGE_OVERVIEW  = "includeinstageoverview";

    String PROPERTY_USERTASK_ASSIGNMENT = "usertaskassignment";
    String PROPERTY_USERTASK_PRIORITY = "prioritydefinition";
    String PROPERTY_USERTASK_DUEDATE = "duedatedefinition";
    String PROPERTY_USERTASK_ASSIGNEE = "assignee";
    String PROPERTY_USERTASK_OWNER = "owner";
    String PROPERTY_USERTASK_CANDIDATE_USERS = "candidateUsers";
    String PROPERTY_USERTASK_CANDIDATE_GROUPS = "candidateGroups";
    String PROPERTY_USERTASK_CATEGORY = "categorydefinition";

    String PROPERTY_USERTASK_LISTENERS = "tasklisteners";
    String PROPERTY_LISTENER_EVENT = "event";
    String PROPERTY_LISTENER_CLASS_NAME = "className";
    String PROPERTY_LISTENER_EXPRESSION = "expression";
    String PROPERTY_LISTENER_DELEGATE_EXPRESSION = "delegateExpression";
    String PROPERTY_LISTENER_FIELDS = "fields";

    String PROPERTY_LIFECYCLE_LISTENERS = "planitemlifecyclelisteners";
    String PROPERTY_LISTENER_SOURCE_STATE = "sourceState";
    String PROPERTY_LISTENER_TARGET_STATE = "targetState";

    String PROPERTY_FIELD_NAME = "name";
    String PROPERTY_FIELD_STRING_VALUE = "stringValue";
    String PROPERTY_FIELD_EXPRESSION = "expression";
    String PROPERTY_FIELD_STRING = "string";

    String PROPERTY_SERVICETASK_CLASS = "servicetaskclass";
    String PROPERTY_SERVICETASK_EXPRESSION = "servicetaskexpression";
    String PROPERTY_SERVICETASK_DELEGATE_EXPRESSION = "servicetaskdelegateexpression";
    String PROPERTY_SERVICETASK_RESULT_VARIABLE = "servicetaskresultvariable";
    String PROPERTY_SERVICETASK_FIELDS = "servicetaskfields";
    String PROPERTY_SERVICETASK_FIELD_NAME = "name";
    String PROPERTY_SERVICETASK_FIELD_STRING_VALUE = "stringValue";
    String PROPERTY_SERVICETASK_FIELD_STRING = "string";
    String PROPERTY_SERVICETASK_FIELD_EXPRESSION = "expression";

    String PROPERTY_SCRIPT_TASK_SCRIPT_FORMAT = "scriptformat";
    String PROPERTY_SCRIPT_TASK_SCRIPT_TEXT = "scripttext";

    String PROPERTY_DECISIONTABLE_REFERENCE = "decisiontaskdecisiontablereference";
    String PROPERTY_DECISIONTABLE_REFERENCE_ID = "decisiontablereferenceid";
    String PROPERTY_DECISIONTABLE_REFERENCE_NAME = "decisiontablereferencename";
    String PROPERTY_DECISIONTABLE_REFERENCE_KEY = "decisionTableReferenceKey";
    String PROPERTY_DECISIONTABLE_THROW_ERROR_NO_HITS = "decisiontaskthrowerroronnohits";
    String PROPERTY_DECISIONTABLE_THROW_ERROR_NO_HITS_KEY = "decisionTaskThrowErrorOnNoHits";
    String PROPERTY_DECISIONTABLE_FALLBACK_TO_DEFAULT_TENANT = "decisiontaskfallbacktodefaulttenant";
    String PROPERTY_DECISIONTABLE_FALLBACK_TO_DEFAULT_TENANT_KEY = "fallbackToDefaultTenant";

    String PROPERTY_CASE_REFERENCE = "casetaskcasereference";

    String PROPERTY_PROCESS_REFERENCE = "processtaskprocessreference";
    String PROPERTY_PROCESS_IN_PARAMETERS = "processtaskinparameters";
    String PROPERTY_PROCESS_OUT_PARAMETERS = "processtaskoutparameters";
    String PROPERTY_FALLBACK_TO_DEFAULT_TENANT = "fallbacktodefaulttenant";

    String PROPERTY_IN_PARAMETERS = "inParameters";
    String PROPERTY_OUT_PARAMETERS = "outParameters";

    String PROPERTY_IF_PART_CONDITION = "ifpartcondition";
    String PROPERTY_TRIGGER_MODE = "triggermode";

    String PROPERTY_TRANSITION_EVENT = "transitionevent";

    String PROPERTY_HTTPTASK_REQ_METHOD = "httptaskrequestmethod";
    String PROPERTY_HTTPTASK_REQ_URL = "httptaskrequesturl";
    String PROPERTY_HTTPTASK_REQ_HEADERS = "httptaskrequestheaders";
    String PROPERTY_HTTPTASK_REQ_BODY  = "httptaskrequestbody";
    String PROPERTY_HTTPTASK_REQ_BODY_ENCODING  = "httptaskrequestbodyencoding";
    String PROPERTY_HTTPTASK_REQ_TIMEOUT = "httptaskrequesttimeout";
    String PROPERTY_HTTPTASK_REQ_DISALLOW_REDIRECTS = "httptaskdisallowredirects";
    String PROPERTY_HTTPTASK_REQ_FAIL_STATUS_CODES = "httptaskfailstatuscodes";
    String PROPERTY_HTTPTASK_REQ_HANDLE_STATUS_CODES = "httptaskhandlestatuscodes";
    String PROPERTY_HTTPTASK_REQ_IGNORE_EXCEPTION = "httptaskignoreexception";
    String PROPERTY_HTTPTASK_RESPONSE_VARIABLE_NAME = "httptaskresponsevariablename";
    String PROPERTY_HTTPTASK_SAVE_REQUEST_VARIABLES = "httptasksaverequestvariables";
    String PROPERTY_HTTPTASK_SAVE_RESPONSE_PARAMETERS = "httptasksaveresponseparameters";
    String PROPERTY_HTTPTASK_RESULT_VARIABLE_PREFIX = "httptaskresultvariableprefix";
    String PROPERTY_HTTPTASK_SAVE_RESPONSE_TRANSIENT = "httptasksaveresponseparameterstransient";
    String PROPERTY_HTTPTASK_SAVE_RESPONSE_AS_JSON = "httptasksaveresponseasjson";

    String PROPERTY_TIMER_EXPRESSION = "timerexpression";
    String PROPERTY_TIMER_START_TRIGGER_SOURCE_REF = "timerstarttriggersourceref";
    String PROPERTY_TIMER_START_TRIGGER_STANDARD_EVENT = "transitionevent";

}

redpajama_set_name: RedPajamaGithub


Join us upstairs at the Red Star Bar to celebrate the debut of Firestone Walker's Velvet Merkin! We'll be tapping a barrel and the first 16 customers will have a chance to buy a bottle to take home! Other Firestone draft offerings will include Oaktoberfest, Velvet Merlin, and Union Jack! Wear your favorite false hair-piece (mustache, beard, wig, or other) to qualify for drink specials!


text:
<?php
# Generated by the protocol buffer compiler.  DO NOT EDIT!
# source: google/cloud/securitycenter/v1/securitycenter_service.proto

namespace Google\Cloud\SecurityCenter\V1;

use Google\Protobuf\Internal\GPBType;
use Google\Protobuf\Internal\RepeatedField;
use Google\Protobuf\Internal\GPBUtil;

/**
 * Request message for grouping by findings.
 *
 * Generated from protobuf message google.cloud.securitycenter.v1.GroupFindingsRequest
 */
class GroupFindingsRequest extends \Google\Protobuf\Internal\Message
{
    /**
     * Required. Name of the source to groupBy. Its format is
     * "organizations/[organization_id]/sources/[source_id]",
     * folders/[folder_id]/sources/[source_id], or
     * projects/[project_id]/sources/[source_id]. To groupBy across all sources
     * provide a source_id of `-`. For example:
     * organizations/{organization_id}/sources/-, folders/{folder_id}/sources/-,
     * or projects/{project_id}/sources/-
     *
     * Generated from protobuf field string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = {
     */
    private $parent = '';
    /**
     * Expression that defines the filter to apply across findings.
     * The expression is a list of one or more restrictions combined via logical
     * operators `AND` and `OR`.
     * Parentheses are supported, and `OR` has higher precedence than `AND`.
     * Restrictions have the form `<field> <operator> <value>` and may have a `-`
     * character in front of them to indicate negation. Examples include:
     *  * name
     *  * source_properties.a_property
     *  * security_marks.marks.marka
     * The supported operators are:
     * * `=` for all value types.
     * * `>`, `<`, `>=`, `<=` for integer values.
     * * `:`, meaning substring matching, for strings.
     * The supported value types are:
     * * string literals in quotes.
     * * integer literals without quotes.
     * * boolean literals `true` and `false` without quotes.
     * The following field and operator combinations are supported:
     * * name: `=`
     * * parent: `=`, `:`
     * * resource_name: `=`, `:`
     * * state: `=`, `:`
     * * category: `=`, `:`
     * * external_uri: `=`, `:`
     * * event_time: `=`, `>`, `<`, `>=`, `<=`
     *   Usage: This should be milliseconds since epoch or an RFC3339 string.
     *   Examples:
     *     `event_time = "2019-06-10T16:07:18-07:00"`
     *     `event_time = 1560208038000`
     * * severity: `=`, `:`
     * * workflow_state: `=`, `:`
     * * security_marks.marks: `=`, `:`
     * * source_properties: `=`, `:`, `>`, `<`, `>=`, `<=`
     *   For example, `source_properties.size = 100` is a valid filter string.
     *   Use a partial match on the empty string to filter based on a property
     *   existing: `source_properties.my_property : ""`
     *   Use a negated partial match on the empty string to filter based on a
     *   property not existing: `-source_properties.my_property : ""`
     * * resource:
     *   * resource.name: `=`, `:`
     *   * resource.parent_name: `=`, `:`
     *   * resource.parent_display_name: `=`, `:`
     *   * resource.project_name: `=`, `:`
     *   * resource.project_display_name: `=`, `:`
     *   * resource.type: `=`, `:`
     *
     * Generated from protobuf field string filter = 2;
     */
    private $filter = '';
    /**
     * Required. Expression that defines what assets fields to use for grouping
     * (including `state_change`). The string value should follow SQL syntax:
     * comma separated list of fields. For example: "parent,resource_name".
     * The following fields are supported:
     * * resource_name
     * * category
     * * state
     * * parent
     * * severity
     * The following fields are supported when compare_duration is set:
     * * state_change
     *
     * Generated from protobuf field string group_by = 3 [(.google.api.field_behavior) = REQUIRED];
     */
    private $group_by = '';
    /**
     * Time used as a reference point when filtering findings. The filter is
     * limited to findings existing at the supplied time and their values are
     * those at that specific time. Absence of this field will default to the
     * API's version of NOW.
     *
     * Generated from protobuf field .google.protobuf.Timestamp read_time = 4;
     */
    private $read_time = null;
    /**
     * When compare_duration is set, the GroupResult's "state_change" attribute is
     * updated to indicate whether the finding had its state changed, the
     * finding's state remained unchanged, or if the finding was added during the
     * compare_duration period of time that precedes the read_time. This is the
     * time between (read_time - compare_duration) and read_time.
     * The state_change value is derived based on the presence and state of the
     * finding at the two points in time. Intermediate state changes between the
     * two times don't affect the result. For example, the results aren't affected
     * if the finding is made inactive and then active again.
     * Possible "state_change" values when compare_duration is specified:
     * * "CHANGED":   indicates that the finding was present and matched the given
     *                  filter at the start of compare_duration, but changed its
     *                  state at read_time.
     * * "UNCHANGED": indicates that the finding was present and matched the given
     *                  filter at the start of compare_duration and did not change
     *                  state at read_time.
     * * "ADDED":     indicates that the finding did not match the given filter or
     *                  was not present at the start of compare_duration, but was
     *                  present at read_time.
     * * "REMOVED":   indicates that the finding was present and matched the
     *                  filter at the start of compare_duration, but did not match
     *                  the filter at read_time.
     * If compare_duration is not specified, then the only possible state_change
     * is "UNUSED",  which will be the state_change set for all findings present
     * at read_time.
     * If this field is set then `state_change` must be a specified field in
     * `group_by`.
     *
     * Generated from protobuf field .google.protobuf.Duration compare_duration = 5;
     */
    private $compare_duration = null;
    /**
     * The value returned by the last `GroupFindingsResponse`; indicates
     * that this is a continuation of a prior `GroupFindings` call, and
     * that the system should return the next page of data.
     *
     * Generated from protobuf field string page_token = 7;
     */
    private $page_token = '';
    /**
     * The maximum number of results to return in a single response. Default is
     * 10, minimum is 1, maximum is 1000.
     *
     * Generated from protobuf field int32 page_size = 8;
     */
    private $page_size = 0;

    /**
     * Constructor.
     *
     * @param array $data {
     *     Optional. Data for populating the Message object.
     *
     *     @type string $parent
     *           Required. Name of the source to groupBy. Its format is
     *           "organizations/[organization_id]/sources/[source_id]",
     *           folders/[folder_id]/sources/[source_id], or
     *           projects/[project_id]/sources/[source_id]. To groupBy across all sources
     *           provide a source_id of `-`. For example:
     *           organizations/{organization_id}/sources/-, folders/{folder_id}/sources/-,
     *           or projects/{project_id}/sources/-
     *     @type string $filter
     *           Expression that defines the filter to apply across findings.
     *           The expression is a list of one or more restrictions combined via logical
     *           operators `AND` and `OR`.
     *           Parentheses are supported, and `OR` has higher precedence than `AND`.
     *           Restrictions have the form `<field> <operator> <value>` and may have a `-`
     *           character in front of them to indicate negation. Examples include:
     *            * name
     *            * source_properties.a_property
     *            * security_marks.marks.marka
     *           The supported operators are:
     *           * `=` for all value types.
     *           * `>`, `<`, `>=`, `<=` for integer values.
     *           * `:`, meaning substring matching, for strings.
     *           The supported value types are:
     *           * string literals in quotes.
     *           * integer literals without quotes.
     *           * boolean literals `true` and `false` without quotes.
     *           The following field and operator combinations are supported:
     *           * name: `=`
     *           * parent: `=`, `:`
     *           * resource_name: `=`, `:`
     *           * state: `=`, `:`
     *           * category: `=`, `:`
     *           * external_uri: `=`, `:`
     *           * event_time: `=`, `>`, `<`, `>=`, `<=`
     *             Usage: This should be milliseconds since epoch or an RFC3339 string.
     *             Examples:
     *               `event_time = "2019-06-10T16:07:18-07:00"`
     *               `event_time = 1560208038000`
     *           * severity: `=`, `:`
     *           * workflow_state: `=`, `:`
     *           * security_marks.marks: `=`, `:`
     *           * source_properties: `=`, `:`, `>`, `<`, `>=`, `<=`
     *             For example, `source_properties.size = 100` is a valid filter string.
     *             Use a partial match on the empty string to filter based on a property
     *             existing: `source_properties.my_property : ""`
     *             Use a negated partial match on the empty string to filter based on a
     *             property not existing: `-source_properties.my_property : ""`
     *           * resource:
     *             * resource.name: `=`, `:`
     *             * resource.parent_name: `=`, `:`
     *             * resource.parent_display_name: `=`, `:`
     *             * resource.project_name: `=`, `:`
     *             * resource.project_display_name: `=`, `:`
     *             * resource.type: `=`, `:`
     *     @type string $group_by
     *           Required. Expression that defines what assets fields to use for grouping
     *           (including `state_change`). The string value should follow SQL syntax:
     *           comma separated list of fields. For example: "parent,resource_name".
     *           The following fields are supported:
     *           * resource_name
     *           * category
     *           * state
     *           * parent
     *           * severity
     *           The following fields are supported when compare_duration is set:
     *           * state_change
     *     @type \Google\Protobuf\Timestamp $read_time
     *           Time used as a reference point when filtering findings. The filter is
     *           limited to findings existing at the supplied time and their values are
     *           those at that specific time. Absence of this field will default to the
     *           API's version of NOW.
     *     @type \Google\Protobuf\Duration $compare_duration
     *           When compare_duration is set, the GroupResult's "state_change" attribute is
     *           updated to indicate whether the finding had its state changed, the
     *           finding's state remained unchanged, or if the finding was added during the
     *           compare_duration period of time that precedes the read_time. This is the
     *           time between (read_time - compare_duration) and read_time.
     *           The state_change value is derived based on the presence and state of the
     *           finding at the two points in time. Intermediate state changes between the
     *           two times don't affect the result. For example, the results aren't affected
     *           if the finding is made inactive and then active again.
     *           Possible "state_change" values when compare_duration is specified:
     *           * "CHANGED":   indicates that the finding was present and matched the given
     *                            filter at the start of compare_duration, but changed its
     *                            state at read_time.
     *           * "UNCHANGED": indicates that the finding was present and matched the given
     *                            filter at the start of compare_duration and did not change
     *                            state at read_time.
     *           * "ADDED":     indicates that the finding did not match the given filter or
     *                            was not present at the start of compare_duration, but was
     *                            present at read_time.
     *           * "REMOVED":   indicates that the finding was present and matched the
     *                            filter at the start of compare_duration, but did not match
     *                            the filter at read_time.
     *           If compare_duration is not specified, then the only possible state_change
     *           is "UNUSED",  which will be the state_change set for all findings present
     *           at read_time.
     *           If this field is set then `state_change` must be a specified field in
     *           `group_by`.
     *     @type string $page_token
     *           The value returned by the last `GroupFindingsResponse`; indicates
     *           that this is a continuation of a prior `GroupFindings` call, and
     *           that the system should return the next page of data.
     *     @type int $page_size
     *           The maximum number of results to return in a single response. Default is
     *           10, minimum is 1, maximum is 1000.
     * }
     */
    public function __construct($data = NULL) {
        \GPBMetadata\Google\Cloud\Securitycenter\V1\SecuritycenterService::initOnce();
        parent::__construct($data);
    }

    /**
     * Required. Name of the source to groupBy. Its format is
     * "organizations/[organization_id]/sources/[source_id]",
     * folders/[folder_id]/sources/[source_id], or
     * projects/[project_id]/sources/[source_id]. To groupBy across all sources
     * provide a source_id of `-`. For example:
     * organizations/{organization_id}/sources/-, folders/{folder_id}/sources/-,
     * or projects/{project_id}/sources/-
     *
     * Generated from protobuf field string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = {
     * @return string
     */
    public function getParent()
    {
        return $this->parent;
    }

    /**
     * Required. Name of the source to groupBy. Its format is
     * "organizations/[organization_id]/sources/[source_id]",
     * folders/[folder_id]/sources/[source_id], or
     * projects/[project_id]/sources/[source_id]. To groupBy across all sources
     * provide a source_id of `-`. For example:
     * organizations/{organization_id}/sources/-, folders/{folder_id}/sources/-,
     * or projects/{project_id}/sources/-
     *
     * Generated from protobuf field string parent = 1 [(.google.api.field_behavior) = REQUIRED, (.google.api.resource_reference) = {
     * @param string $var
     * @return $this
     */
    public function setParent($var)
    {
        GPBUtil::checkString($var, True);
        $this->parent = $var;

        return $this;
    }

    /**
     * Expression that defines the filter to apply across findings.
     * The expression is a list of one or more restrictions combined via logical
     * operators `AND` and `OR`.
     * Parentheses are supported, and `OR` has higher precedence than `AND`.
     * Restrictions have the form `<field> <operator> <value>` and may have a `-`
     * character in front of them to indicate negation. Examples include:
     *  * name
     *  * source_properties.a_property
     *  * security_marks.marks.marka
     * The supported operators are:
     * * `=` for all value types.
     * * `>`, `<`, `>=`, `<=` for integer values.
     * * `:`, meaning substring matching, for strings.
     * The supported value types are:
     * * string literals in quotes.
     * * integer literals without quotes.
     * * boolean literals `true` and `false` without quotes.
     * The following field and operator combinations are supported:
     * * name: `=`
     * * parent: `=`, `:`
     * * resource_name: `=`, `:`
     * * state: `=`, `:`
     * * category: `=`, `:`
     * * external_uri: `=`, `:`
     * * event_time: `=`, `>`, `<`, `>=`, `<=`
     *   Usage: This should be milliseconds since epoch or an RFC3339 string.
     *   Examples:
     *     `event_time = "2019-06-10T16:07:18-07:00"`
     *     `event_time = 1560208038000`
     * * severity: `=`, `:`
     * * workflow_state: `=`, `:`
     * * security_marks.marks: `=`, `:`
     * * source_properties: `=`, `:`, `>`, `<`, `>=`, `<=`
     *   For example, `source_properties.size = 100` is a valid filter string.
     *   Use a partial match on the empty string to filter based on a property
     *   existing: `source_properties.my_property : ""`
     *   Use a negated partial match on the empty string to filter based on a
     *   property not existing: `-source_properties.my_property : ""`
     * * resource:
     *   * resource.name: `=`, `:`
     *   * resource.parent_name: `=`, `:`
     *   * resource.parent_display_name: `=`, `:`
     *   * resource.project_name: `=`, `:`
     *   * resource.project_display_name: `=`, `:`
     *   * resource.type: `=`, `:`
     *
     * Generated from protobuf field string filter = 2;
     * @return string
     */
    public function getFilter()
    {
        return $this->filter;
    }

    /**
     * Expression that defines the filter to apply across findings.
     * The expression is a list of one or more restrictions combined via logical
     * operators `AND` and `OR`.
     * Parentheses are supported, and `OR` has higher precedence than `AND`.
     * Restrictions have the form `<field> <operator> <value>` and may have a `-`
     * character in front of them to indicate negation. Examples include:
     *  * name
     *  * source_properties.a_property
     *  * security_marks.marks.marka
     * The supported operators are:
     * * `=` for all value types.
     * * `>`, `<`, `>=`, `<=` for integer values.
     * * `:`, meaning substring matching, for strings.
     * The supported value types are:
     * * string literals in quotes.
     * * integer literals without quotes.
     * * boolean literals `true` and `false` without quotes.
     * The following field and operator combinations are supported:
     * * name: `=`
     * * parent: `=`, `:`
     * * resource_name: `=`, `:`
     * * state: `=`, `:`
     * * category: `=`, `:`
     * * external_uri: `=`, `:`
     * * event_time: `=`, `>`, `<`, `>=`, `<=`
     *   Usage: This should be milliseconds since epoch or an RFC3339 string.
     *   Examples:
     *     `event_time = "2019-06-10T16:07:18-07:00"`
     *     `event_time = 1560208038000`
     * * severity: `=`, `:`
     * * workflow_state: `=`, `:`
     * * security_marks.marks: `=`, `:`
     * * source_properties: `=`, `:`, `>`, `<`, `>=`, `<=`
     *   For example, `source_properties.size = 100` is a valid filter string.
     *   Use a partial match on the empty string to filter based on a property
     *   existing: `source_properties.my_property : ""`
     *   Use a negated partial match on the empty string to filter based on a
     *   property not existing: `-source_properties.my_property : ""`
     * * resource:
     *   * resource.name: `=`, `:`
     *   * resource.parent_name: `=`, `:`
     *   * resource.parent_display_name: `=`, `:`
     *   * resource.project_name: `=`, `:`
     *   * resource.project_display_name: `=`, `:`
     *   * resource.type: `=`, `:`
     *
     * Generated from protobuf field string filter = 2;
     * @param string $var
     * @return $this
     */
    public function setFilter($var)
    {
        GPBUtil::checkString($var, True);
        $this->filter = $var;

        return $this;
    }

    /**
     * Required. Expression that defines what assets fields to use for grouping
     * (including `state_change`). The string value should follow SQL syntax:
     * comma separated list of fields. For example: "parent,resource_name".
     * The following fields are supported:
     * * resource_name
     * * category
     * * state
     * * parent
     * * severity
     * The following fields are supported when compare_duration is set:
     * * state_change
     *
     * Generated from protobuf field string group_by = 3 [(.google.api.field_behavior) = REQUIRED];
     * @return string
     */
    public function getGroupBy()
    {
        return $this->group_by;
    }

    /**
     * Required. Expression that defines what assets fields to use for grouping
     * (including `state_change`). The string value should follow SQL syntax:
     * comma separated list of fields. For example: "parent,resource_name".
     * The following fields are supported:
     * * resource_name
     * * category
     * * state
     * * parent
     * * severity
     * The following fields are supported when compare_duration is set:
     * * state_change
     *
     * Generated from protobuf field string group_by = 3 [(.google.api.field_behavior) = REQUIRED];
     * @param string $var
     * @return $this
     */
    public function setGroupBy($var)
    {
        GPBUtil::checkString($var, True);
        $this->group_by = $var;

        return $this;
    }

    /**
     * Time used as a reference point when filtering findings. The filter is
     * limited to findings existing at the supplied time and their values are
     * those at that specific time. Absence of this field will default to the
     * API's version of NOW.
     *
     * Generated from protobuf field .google.protobuf.Timestamp read_time = 4;
     * @return \Google\Protobuf\Timestamp|null
     */
    public function getReadTime()
    {
        return $this->read_time;
    }

    public function hasReadTime()
    {
        return isset($this->read_time);
    }

    public function clearReadTime()
    {
        unset($this->read_time);
    }

    /**
     * Time used as a reference point when filtering findings. The filter is
     * limited to findings existing at the supplied time and their values are
     * those at that specific time. Absence of this field will default to the
     * API's version of NOW.
     *
     * Generated from protobuf field .google.protobuf.Timestamp read_time = 4;
     * @param \Google\Protobuf\Timestamp $var
     * @return $this
     */
    public function setReadTime($var)
    {
        GPBUtil::checkMessage($var, \Google\Protobuf\Timestamp::class);
        $this->read_time = $var;

        return $this;
    }

    /**
     * When compare_duration is set, the GroupResult's "state_change" attribute is
     * updated to indicate whether the finding had its state changed, the
     * finding's state remained unchanged, or if the finding was added during the
     * compare_duration period of time that precedes the read_time. This is the
     * time between (read_time - compare_duration) and read_time.
     * The state_change value is derived based on the presence and state of the
     * finding at the two points in time. Intermediate state changes between the
     * two times don't affect the result. For example, the results aren't affected
     * if the finding is made inactive and then active again.
     * Possible "state_change" values when compare_duration is specified:
     * * "CHANGED":   indicates that the finding was present and matched the given
     *                  filter at the start of compare_duration, but changed its
     *                  state at read_time.
     * * "UNCHANGED": indicates that the finding was present and matched the given
     *                  filter at the start of compare_duration and did not change
     *                  state at read_time.
     * * "ADDED":     indicates that the finding did not match the given filter or
     *                  was not present at the start of compare_duration, but was
     *                  present at read_time.
     * * "REMOVED":   indicates that the finding was present and matched the
     *                  filter at the start of compare_duration, but did not match
     *                  the filter at read_time.
     * If compare_duration is not specified, then the only possible state_change
     * is "UNUSED",  which will be the state_change set for all findings present
     * at read_time.
     * If this field is set then `state_change` must be a specified field in
     * `group_by`.
     *
     * Generated from protobuf field .google.protobuf.Duration compare_duration = 5;
     * @return \Google\Protobuf\Duration|null
     */
    public function getCompareDuration()
    {
        return $this->compare_duration;
    }

    public function hasCompareDuration()
    {
        return isset($this->compare_duration);
    }

    public function clearCompareDuration()
    {
        unset($this->compare_duration);
    }

    /**
     * When compare_duration is set, the GroupResult's "state_change" attribute is
     * updated to indicate whether the finding had its state changed, the
     * finding's state remained unchanged, or if the finding was added during the
     * compare_duration period of time that precedes the read_time. This is the
     * time between (read_time - compare_duration) and read_time.
     * The state_change value is derived based on the presence and state of the
     * finding at the two points in time. Intermediate state changes between the
     * two times don't affect the result. For example, the results aren't affected
     * if the finding is made inactive and then active again.
     * Possible "state_change" values when compare_duration is specified:
     * * "CHANGED":   indicates that the finding was present and matched the given
     *                  filter at the start of compare_duration, but changed its
     *                  state at read_time.
     * * "UNCHANGED": indicates that the finding was present and matched the given
     *                  filter at the start of compare_duration and did not change
     *                  state at read_time.
     * * "ADDED":     indicates that the finding did not match the given filter or
     *                  was not present at the start of compare_duration, but was
     *                  present at read_time.
     * * "REMOVED":   indicates that the finding was present and matched the
     *                  filter at the start of compare_duration, but did not match
     *                  the filter at read_time.
     * If compare_duration is not specified, then the only possible state_change
     * is "UNUSED",  which will be the state_change set for all findings present
     * at read_time.
     * If this field is set then `state_change` must be a specified field in
     * `group_by`.
     *
     * Generated from protobuf field .google.protobuf.Duration compare_duration = 5;
     * @param \Google\Protobuf\Duration $var
     * @return $this
     */
    public function setCompareDuration($var)
    {
        GPBUtil::checkMessage($var, \Google\Protobuf\Duration::class);
        $this->compare_duration = $var;

        return $this;
    }

    /**
     * The value returned by the last `GroupFindingsResponse`; indicates
     * that this is a continuation of a prior `GroupFindings` call, and
     * that the system should return the next page of data.
     *
     * Generated from protobuf field string page_token = 7;
     * @return string
     */
    public function getPageToken()
    {
        return $this->page_token;
    }

    /**
     * The value returned by the last `GroupFindingsResponse`; indicates
     * that this is a continuation of a prior `GroupFindings` call, and
     * that the system should return the next page of data.
     *
     * Generated from protobuf field string page_token = 7;
     * @param string $var
     * @return $this
     */
    public function setPageToken($var)
    {
        GPBUtil::checkString($var, True);
        $this->page_token = $var;

        return $this;
    }

    /**
     * The maximum number of results to return in a single response. Default is
     * 10, minimum is 1, maximum is 1000.
     *
     * Generated from protobuf field int32 page_size = 8;
     * @return int
     */
    public function getPageSize()
    {
        return $this->page_size;
    }

    /**
     * The maximum number of results to return in a single response. Default is
     * 10, minimum is 1, maximum is 1000.
     *
     * Generated from protobuf field int32 page_size = 8;
     * @param int $var
     * @return $this
     */
    public function setPageSize($var)
    {
        GPBUtil::checkInt32($var);
        $this->page_size = $var;

        return $this;
    }

}


When temperatures fall and you fire up the heater for winter, it seems each time a corner of the house—or maybe an entire room—that never gets quite warm enough.
Rather than overheat the rest of the house, you might plug in a portable electric heater to cozy up the space. The multipurpose units can be effective, energy-efficient tools to help keep things relaxed until spring. But, they're also a recognized as a fire risk.
According to the National Fire Prevention Association, in a recent five-year period, transportable heaters accounted for one-third of home heating fires, with half of all such fires happening during the months of December, January and February.
Select a heater that's been tested and certified for safety by an organization such as Underwriters Laboratories. Some shut off automatically if the unit overheats or tips over, but don't substitute such features for careful use. To check for safety recalls, visit the SaferProducts website.
Plug your portable heater into a wall outlet that can handle the wattage, and guarantee the plug fits tightly. Never plug it into an extension cord or power strip or into the same wall outlet as other heavy-duty appliances.
Place the heater in an open area, not under desks or in other encircled areas, and keep it at least 3 feet away from everything flammable. Safeguard children and pets don't get too close, either.
Don't cover up the cord.
During use, check habitually to regulate if the heater plug or cord, wall outlet or faceplate is hot. If so, discontinue use and seek repairs.
By using a heater with thermostat controls, you can help avoid overheating the room, which wastes energy, as well as the unit.
Leaving the room or sleeping? Hit the "off" button, and unplug the heater.
Recall, electrical fires can start inside your walls, too, not just in the immediate area. If you blow a fuse or trip a circuit breaker while using your space heater, it's a good indication that it's more than your system can handle. Try a different outlet or a different portable heater to better reduce your risk.


Welcome to beautiful San Antonio, home of the Spurs, Rodeos and the beautiful Texas Hill Country. San Antonio offers an abundance of choices in lifestyles and a vast selection of affordable family homes as well as secluded luxury estates. Whether you prefer urban living in beautiful downtown, enjoying the nightlife of the Riverwalk or perhaps the private, quiet ambiance of the Texas Hill Country life, look no further for homes for sale in San Antonio, we have them! Best of all, real estate in the surrounding communities; Helotes, Leon Valley, Shavano Park, Boerne, Live Oak, Alamo Heights, Bulverde, Garden Ridge, New Braunfels, Gruene, Schertz, Cibolo and the Canyon Lake all offer their own unique lifestyles. Please bookmark our website and come back to visit often. We are your go-to San Antonio realtor. Get to know more about life in and around San Antonio by visiting our blog.
We consider it a privilege to take extra time and special dedication to those who serve our community. We recognize the home selling and buying process can be overwhelming. We also understand that not all those in our community, especially those who work as first responders, work 8-5. Let us be the one you can count on to take the late night, early morning or yes even middle of the night calls to get you on your way to buying or selling your home! We want to ensure you receive the highest quality service that everyone deserves, even when your schedule might be a bit tricky. We are here for you! We also offer special incentives as a thank you for what you do.
Did you know there are special programs to assist with your down payment and closing costs? Call Us to get more information.
Programs for First Responders and Veterans along with experience in the VA buying process.
Experience with first time home buyers and down payment assistance programs for those who qualify.
Non - Traditional hours, designed for those in our community who work as first responders. We are here to work for you when you need us.
Extensive resources to help those relocating to the area.
One on one service with a both a dedicated Listing and Buyers Specialist.
We love our clients, so feel free to give us a call and set up a time to meet with us!


Search for your match in the Hoosier State and find online personals in Indiana. Find your match in Indiana today! Whether you're looking for Christian singles, Black singles, Asian singles, Jewish singles or local singles, go to the dating site that is responsible for hundreds of thousands of happy couples. Match.com makes dating easy in Mooresville, with dating options available through thousands of Mooresville personals.


Gardners Candies was founded in 1897 by a sixteen-year-old boy named James ''Pike'' Gardner in Tyrone, Pennsylvania. The young entrepreneur operated out of a small store in downtown Tyrone. Pike later added a horse-drawn wagon so that he could transport and sell candy, popcorn and peanuts at local fairs and carnivals. Today, Gardners Candies has 15 retail stores in Pennsylvania. Gardners Candies Stores are beautifully decorated with taste-tempting candies that some have described as ''simply out of this world.'' Stop by the factory store to see how Gardner's candies are made, right before your eyes!


text:
Q: Extending Banach-Tarski paradox? I've learned the Banach-Tarski paradox as following:

*

*The points on the sphere (but not the fixed points) are drawn as a square grid, form each point there are three new directions plus the direction back to the point it came form.

*The grid is cut in four pieces:

*

*(A) The x-axis, plus the points where you can come when turning right

*(B) The points  where you can come when turning left, excluding x-axis

*The points where you can come by going up

*The points where you can come by going down

Then there is a new sphere created by moving all points on A one place to the left. This creates together with B the new sphere.
Now my question is: Can we create a complete sphere by moving all points on A countably infinitely many points to the left?

A: The question is a bit light on details, but if I understand it correctly the answer is no.
First let me fill in some of the details of the usual argument.  We take a copy of $F_2$, the free group on two generators, contained in $\text{SO}(3)$, the group of isometries of the sphere $S^2$.  Excluding the set $D$ of fixed points (meaning points that are fixed by some nonidentity element of $F_2$) the action of $F_2$ on the remaining points is free.  There are only countably many fixed points, so there is a trick for dealing with these later; let's ignore them.
In $S^2 \setminus D$, we use $\mathsf{AC}$ to choose, for each orbit, a point in that orbit.  This allows us to consider each orbit of $S^2 \setminus D$ as a copy of $F_2$ and to transfer a paradoxical decomposition of $F_2$ to each copy simultaneously, giving a paradoxical decomposition of $S^2 \setminus D$.
The question seems to be considering a single orbit (copy of $F_2$) on its own, so it essentially asking about paradoxical decompositions of $F_2$.  (By the way, I think it is a bit misleading to say "square grid": in a square grid if I go right, up, left, and then down, then I am back where I started, whereas in $F_2$ if I multiply $a$, $b$, $a^{-1}$, and $b^{-1}$ in that order, then I do not get the identity element.)
Now for your question:

Can we create a complete sphere by moving all points on A countably infinitely many points to the left?

I don't think it makes sense to move "infinitely many points to the left".  In $F_2$ there is no element $b^{-1}b^{-1}b^{-1}\cdots.$  You might think that because we are consider a copy of $F_2$ that is contained in the sphere, there is a metric and so we could try to take a limit:
let $x \in S^2 \setminus D$ be the point we have chosen from this orbit and consider the sequence of points $x, b^{-1}x, b^{-1}b^{-1}x,\ldots.$  However, this sequence is not convergent (in fact its set of limit points forms a circle.)
You may be confused by diagrams that show $F_2$ contained in the plane, and in which points approach a limit as they move to the left:

However, the metric that $F_2$ inherits from the plane $\mathbb{R}^2$ in this picture is not the same one that it inherits from $S^2$.  In fact, this picture does not represent an isometric action of $F_2$ at all (note that the edges do not all have the same length.)  So the usefulness of this picture for understanding the paradoxical decomposition of the sphere is limited.

redpajama_set_name: RedPajamaStackExchange


text:
Сопвит -{F.1}- камел () је британски ловачки авион. Авион је први пут полетео 1916. године.

Ово је један од најзначајнијих ловачких авиона Првог светског рата.

Највећа брзина авиона при хоризонталном лету је износила 182 -{km/h}-.
Распон крила авиона је био 8,53 метара, а дужина трупа 5,72 метара. Празан авион је имао масу од 421 килограма. Нормална полетна маса износила је око 658 килограма. Био је наоружан са два митраљеза 7,7 мм Викерс или једним Викерс и једним Луис или два Луис. Могао је да носи до четири бомбе (свака 11,3 кг) на подкрилним носачима.

Наоружање

Референце

Литература
 Детаљнији подаци о авиону

Спољашње везе

 Истребители Сопвич в России

Ловачки авиони
Сопвит авиони
Војни авиони 1910—1919.
Авиони Првог светског рата
Британски ловачки авиони Првог светског рата
Британски ловачки авиони 1910—1919.

redpajama_set_name: RedPajamaWikipedia


The snippets below have been gleaned from various files left by Gervas. He thought them worth recording, so they are placed here for the same reason, and so that Search Engines such as Google can find the texts, and produce the references when asked. They are in no particular order.
Extracts from "Economy of the Central Barotse Plain" by Max Gluckman.
Page 4. This King, is, by patrilineal descent, a member of the Lozi tribe which conquered outwards from its homeland to establish a great kingdom during the years from about 1600 to 1888.
P.6. Lozi say it (the Little River) has grown out of a canal dug by King Mulambwa (circa 1790-1825).
P. 12. (chart), Melland groups the Kaonde as a branch of the Luba though they have not the circumcision ceremonies which are characteristic of the Luba group.
P. 27. Great care was taken in selecting the men who would control it (land) and under Lozi law of inheritance there was no fixed rule of succession so that heirs could be selected solely on the basis of their characters. A man might select his heir before death or the heir .was chosen for his character by the members of the family in consultation with the political authorities. Though there was a patrilineal bias, brothers, cross-cousins; and "uterine nephews and grandchildren were quite frequently selected; even when the patrilineal line was followed, not only might the sons of the great wife; (musali yo muhulu, the first wife married) be passed over, but also among the sons of one wife the eldest might not be chosen. This heir in turn would be succeeded by an elected heir who took the same name and this might go back several generations; therefore Lozi said of a family heir, as they did of a new incumbent of an old office, u yolile libizo (he inherited the name). The Lozi said the heir must be a kind, generous, just and peaceable man, to hold the family together; if he were not he could be dismissed on application to the court: The immediate task of the heir on election was to distribute the inherited land; he had to divide fairly fishing-sites and garden-land. If his predecessor had owned many mounds, he had to allot these, but he kept ownership of the main family mound for himself. This should not be divided.
P. 36. I suspect an increasing tendency for men of other tribes to be Lozi-ised and settle in the Plain.
P. 37. While all the tribes of this region have small chiefs, with matrilineal descent, the Lozi have powerful chiefs and a bias for patrilineal descent. I shall argue that this is because Lozi chiefs acquired big lots of mound land and corresponding power, and mounds placed a premium on inheritance within the resident group.
P. 43. Wiko, with their original matrilineal bias, are more numerous in the Bush than at the Plain.
P. 84. The Lozi kinship system correspondingly worked in all lines of descent. This appears in the Lozi institution of mishiku (sing. mushiku) which were names of lines of descent. Everyone is commonly said to have four descent-names, one from each grandparent; others give eight, one from each great-grandparent; and it is admitted 'that the number of these names is in theory limited only by the number of descent-names which exist in Loziland.
I found that some people knew less than four of these names, perhaps only one, according to the relatives with whom they had contact. A man was called by the chief patrilineal descent-name of the relatives with whom he was living or visiting, and if asked would first give as his descent-name either that of the descent-name of relatives with whom he grew up, or from whom he was getting help, etc, irrespective of the line of descent, whether through father's father or mother, or mother's father or mother. There was however a tendency when people had grown up in the homestead of matrilineal kin for them to be assimilated into the patrilineal line by, e.g. after some time treating their mother's brother as their father in their genealogy, or their mother as a man. This was easy since the same names were given to men and women.
Correlated with these decent-names was a widely extended system of kinship nomenclature, associated with reciprocal duties and rights. In it all cousins were classed with brothers and sisters and marriage was not only not allowed between cross-cousins, as in the neighbouring tribes, but with no-one to whom the _Lozi could trace genealogical relationship, which they could do as far as three or four generations only, owing to the _small size of homestead groups, Beyond that marriage could take place between people with the same descent-names but between whom genealogical relationship could not be traced. Hospitality and help were expected from a person with any of the same descent-names. Under the system of land-exploitation described above it was important for a man to have many "homes", and this is associated with a ban on marriage into any of them.
Moreover, among the Lozi we do not find the common Bantu institutions of levirate and sorrorate. It was a good thing if a widow with children arranged to marry into her dead husband's family where her children were, if she found a willing relative of his, but there was no compulsion on her to do so, and bride-wealth had to be given again for her. Thus too the sister of a dead wife might marry the widower, bride-wealth passing.
However, and here again the Lozi were unusual among Bantu, it was rare for a man to marry the sister of his still-living wife: it was said that they would quarrel far more than unrelated women, and to marry them both would be to spoil their family-group (ku sinya mukowa wa bona). It is true that easy divorce laws might have made difficulties where a man married two sisters. But these Lozi marriage rules, different from those of most Bantu, in my opinion were associated with the idea that it was redundant to be related by two relation ships to one person or group of people and that it were better to create ties with other people through a fresh person. The Lozi saying "mwaboyu ta mwaboyu" (true Lozi: in Kalolo, "wa habo mutu kaewa habo") was often quoted to me: it states that "the relatives of a man's relatives are his relatives." They usually gave as an example: A's father, X, had two wives, a (A's mother) and b (B's mother). X divorced b and she married Y by whom she had C; C was brother to B through b and also to A with whom he had no blood-connection whatever because A was B's half-brother through a common father, X. So too a man was related to the husband of his wife's sister; the two men called each other mufubalume (the same term as used between X and Y above) and a child could find a home with his father's mufubalume.
The unusual marriage bans, and the absence of the levirate and sororate, together with the rule mwaboyu ta mwaboyu (the relatives of a man's relatives are his relatives), increased greatly the number of people with whom a man could trace present genealogical relationship and therefore the number of people with whom he co-operated, exchanged gifts and help, and could settle. Associated with the economic need for a wide system of personal reciprocities And yet the impossibility of there developing a large kinship grouping based on one line of descent, is a kinship system in which all lines of descent were pushed as far as possible and extended by the rules described above, Mounds were the basis of relationship, as of the rest of the social structure, and present relationship with mound-owners of any line, rather than any single line of descent, was one of the main principles of social integration.
Nevertheless the Lozi bias was in favour of the patrilineal line of descent, and I have explained in the introduction that this possibly developed in the Plain. Here too, I suggest that the determining factor was the mounds. Even if the Lozi came to the Plain as a matrilineal people, the importance of mound-ownership necessitated inheritance within the resident group in any line, and gave the sons of dead headmen a chance to succeed them. A mound-owner could favour his sons and keep them with him especially if his wife's parents had no mound, whereas in the Bush matrilineal tribes, ownership of land conferred little authority.
In fact, mound-ownership enabled a man to attract to himself both his sons and uterine relatives. Richards has shown that the Bemba matrilineal system is associated with a matrilineal clan and the gardening services rendered by sons-in-law; no unilateral group was possible among -the Lozi, nor could a man work for one group of relatives only. He had to co-operate with all, and mound-ownership gave headmen a dominant position which they could use to claim their sons.
P. 88. There are to-day also homesteads of Wiko who have emigrated in groups of matrilineally-related men and women with their spouses and children; in them patriliny is becoming more important because the Lozi courts follow patrilineal laws.
P. 89. Lozi mythology says that at first the Lozi had a woman chief, Mbuyamwambwa, whose rule was not strong. She was a daughter and wife of High-God Nyambe. One day her sons went hunting with dogs, and stopped to rest at a pan where Lozi and Imilangu (i.e. Ndundulu, not a Luyana tribe, see Chart 1) were having a stabbing fish-battle. One of the men who was maternal uncle to the princes (bana ba mulena) thought they should be given some fish for themselves and their dogs, and with an Ndundulu he took fish from each fisherman (ku binguta, the word used today when owners of pans claim their share of fish).
The princes had no men to carry the fish and men were chosen to do this. When the princes got home the people admired this and the big man of their mother's homestead - not the Ngambela (chief councillor) for there was then no Ngambela - called the people to confer and they decided to have a man as chief instead of a woman. Mbuyamwambwa heard of this by chance and was delighted; her son Mboo became the first chief and she became MaKoshi, mother of the chief, still a powerful position. The man who had proposed the male chieftainship became the first Ngambela (chief councillor). Mboo built a new capital; his mother's homestead, Makono, is where the king must spend a night before he can be crowned. Mboo was succeeded by his brother Inyambo, and since then the Lozi kings have been chosen from their patrilineal male descendants. Under Mboo the Lozi began to conquer outwards.
This tradition suggests several things. First, especially since Mboo was a son of God and not related to Kamumu, the first man, whose cleverness drove God from earth to the heavens, it suggests that the powerful Lozi chieftainship originated in the Plain and subsequently gave them the cohesion to become a conquering people. Second, it describes a change in the Plain from matriliny to patriliny. Third, the origin of male chieftainship is related to a particular form of economic activity in which property rights give rights to claim a share of other people's catch. Fourth, since Lozi chiefs were related to God by both lines of descent (and they still marry their classificatory sisters), while Kamunu the first man was not descended from God, the chieftainship is given a strong religious basis. Fifth, at the time the chieftainship developed, the Lozi were already co-operating with at least one another tribe, the Ndundulu.
It is chiefly relevant to this paper on Lozi economy that the myth reflects the position of the king in the economic organisation - his ownership of many rich land-sites and his tribute and labour rights, all of which arise from the oecological and economic pattern described above. The tradition that royal children are born with cattle horns may indicate that the chief owned most cattle. The problem: why was it the Lozi who became dominant in this region? is worth considering sociologically, though ultimately, for lack of data, it may prove to be non-empirical and incapable of scientific investigation as an historical process. However, in postulating the following argument, I analyse the structural functioning of the kingship, once established.
The economic factors making for the political dominance of the Lozi were of two types: first the internal cohesion they derived from residence in the Plain, and second, the relation of Loziland to the neighbouring regions.
Within the Plain, mounds varied in size and the resources exploited from different mounds varied in richness therefore individual ownership of mounds gave not only power over other people, but also varying degrees of this power to the owners of different mounds. The king and his family owned the most and the biggest mounds, and the richest of other resources, so that they had many immediate dependents. From these resources they got surpluses, which, traded for foreign goods, enabled them to distribute these to other Lozi. These Lozi themselves, in the conditions of varying production by individuals which characterised Plain economy, would get goods from the king and in return give him present i.e. tribute. Thus though the Lozi reached the Plain probably under a small female chief, with weak authority, the chiefly family's power could grow if it obtained possession of many and the largest mounds, since it could strengthen itself by the accretion of kinsmen and strangers who wanted land and goods.
P. 103. However, though more research into the Ila system is required, it Is clear that basically they were divided into hostile villages of up to 3,000 inhabitants, and that there were marked segmentary tendencies in villages, which were constituted by family units linked on a matrilineal clan system.
British South Africa Company Executive Committee meeting.
Minutes of 29th January, 1914.
Civil Service Mr. B. Ryan.
Mr. Ryan was injured whilst evicting a reedbuok which had taken refuge in his office for the night.
Federal Archives H.C. 1/2/1. File 3552/02.
Extract from report by Mr. Codrington.
Enclosure to letter to Foreign Office dated 15th May, 1902.
Concerning Civil police of North Eastern Rhodesia, Totals are given by District Stations. Grand total 210.
2. LEFT LUWINGU . . . . . . . . MARCH 11TH 1931.
RETURNED LUWINGU . . . MARCH 25TH 1931.
CHIEF MATIPA AND 57 OF HIS VILLAGES.
These were good on the whole. Several of the older villages were given permission to move to new sites.
One village – Malizawa – has recently come from the Fort Rosebery district, owing to the fact that a lion killed a child there. As these natives are away gathering their crops near their old village, it was not possible to census them. This, however, could be done at a later date, when the government camp at Muchinshi is next visited.
CHIEF MATIPA, on his own initiative, has had what might perhaps be termed a by-pass road made in order to connect villages on different sides of the island. These paths are at least 12 feet wide, and avoid the village gardens as far as is practicable. Though very rough at present, they could become excellent at a later date.
There are now over 200 native-owned bicycles on the island, so that the natives themselves are realising the value of good roads.
The great majority of the island is now under cassava cultivation. The crops appeared to be entirely satisfactory.
This appeared to be uniformly good.
Enough care is not taken by natives to avoid coming into contact with those suffering from leprosy. In one case a woman and two small children, none of whom were affected, were found living in a hut with a leper at some distance from the village. In a second case, two lepers were discovered sitting among the natives in the village while the census was being taken, the excuse given was that they had come in to see the official. The chief was told to deal severely with any natives found in leper's huts, and to hold the headman responsible in cases where a leper had entered a village. As the island is a small one, it might perhaps be practicable to form a village out of the 27 lepers thereon, and to impose a heavy penalty on anyone found entering or leaving it.
Many natives were given passes to Ndola to seek work.
These statistics show a further reduction of over 200 in the number of sheep on the island since last year, said to be due to disease and the depredations of hyenas. There are no lion or leopards on the islands, so that there should be no difficulty in exterminating hyenas also, but the natives do not appear to possess enough initiative and organisation to EFFECT this. As there is a ready sale for sheep, it seems a pity that a really effective round-up is not held.
£33 – 3 – 6d was collected. There are still some 200 1930 taxes outstanding, but the natives in arrears are all said to be at work at the mines.
The following chiefs and divisional headmen visited me: – Chief Kalimankando, sub- chiefs Mulengro and Mwoshi, acting-sub- chiefs Baamba, Mushili, Chula , Mwanokasawe, and Kambule.
The centre Maria Mission was visited, and the Father Superior held a cinema show for the edification of the above chiefs.
I was informed that there are some 200 Christians on the island out of a total population of 8723 souls.


The tyre pyrolysis oil distillation plant can help you refine the all kinds pyrolysis oil and waste oil. The pyrolysis oil is a kind of fuel oil that you get from waste tyres, plastic with the pyrolysis plant. But we all know that the diesel oil has a higher market price and wider application. So if you refine the tyre oil to diesel, you will make higher profits from the waste.
Our tyre oil distillation plants are BZJ-06 and BZJ-10 batch operating plant.
Heating Materials Oil, LPG, natural gas, wood, coal, etc.
Use oil pump to feed raw material into reactor.
Heat reactor by using fuel oil, LPG, natural gas, wood as well as pyrolysis oil. Oil vapour appears when the temperature is rising to the working point. Then it will be stored in oil tank after being cooled by cooling system. After sedimentation filtration, it will be mixed with decolorizing agent. At last, it will become the qualified fuel oil at last.
Gasoline will be released when temperature is rising to 180℃, and diesel oil will be released when the temperature is between 180-360 ℃.
Incondensable combustible gas shall be sent into the gas tank. Then it can be the fuel to heat reactor after being sealed by the water seal system.
The flue gas generated by heating reactor will not cause air pollution after de-dusting system.
Our waste tyre pyrolysis oil to diesel plants for sale have been sold to Dominica, Ukraine and other countries because of their gorgeous design and performance. It can create high value-added products for investors. So if you want to know more about the plant, you can come to visit us or contact us directly.


text:
Will Young speaks of receiving death threats in the street
The singer who owns a home in Cornwall has spoken openly about the struggles he's faced during his career
The 40-year-old is preparing to release new music (Image: Steve Schofield)
In the 17 years since Will Young won Pop Idol - he has notched up four chart-topping albums, four number one UK singles and won two Brit Awards.
But his forthcoming seventh album, titled Lexicon, is a new direction for the 40-year-old singer, who has opened up about some of the challenges he has faced during his long career.
The singer, who purchased his £615k Bodmin Moor bolthole just under 15 years ago to escape the limelight of London, has also spoken about homophobia in the music industry.
He said: "What I find really interesting is the narrative has changed so much. So, as an artist who is gay, now there's stuff that I was talking about 15 years ago where there was no place for it, and now there is a place for it.
Fans concerned for Love Island's Camilla Thurlow as star opens up about anxiety
"Like, on radio, a DJ could be blatantly homophobic about me on live radio but now that would never happen. So it's kind of shocking in a way, but it's also wonderful because it allowed me a whole new life, and it certainly doesn't feel like almost two decades. I mean, I feel like I've just got going."
Will Young (Image: Steve Schofield)
He definitely hasn't rested on his music laurels. He has campaigned passionately for the LGBTQ movement and his podcast is already enjoying a second series. In October, he'll embark on a UK tour and his summer diary is already fully booked with live performances.
Given that he's been in the industry for a while, does he wish the openness and conversations being had now around so many different topics had been present back in the day?
Comic Relief to cut back on celebrity appeals after 'white saviour' row
"I wouldn't have wanted to have had some of the things - people threatening to kill me in the street and record companies saying, 'He sounds gay' - no, of course I wouldn't want that, but I'm very proud of how I got through that and I'm very proud of all the people, all the liberal people for pushing all of those agendas, because it really unites you, to be in a minority, it really unites you as a person and that's really special," he says candidly.
Following a wave of change in various spheres of the entertainment industry, post-movements like Me Too, surely there must have been some type of shift in the music industry at large?
The singer purchased his house in Cornwall just under 15 years ago (Image: Steve Schofield)
For Young, the things he'd like to see in five years include "more transgender artists, more gay women", and he adds: "I'd love to see, I think, still even more black artists. But I do think it's got a lot better now and I do think the industry has caught up."
One area that still niggles, though, is streaming.
Why Love Island bosses can suddenly axe contestants from the show
"There's still a lack of transparency in terms of what deals record companies are doing with streaming platforms and that really now is outrageous ... that's really where I'd like to see artists getting more of what they are due and I don't quite understand why that isn't happening," he says.
"I think streaming is, I have a mixed opinion of it - I love the support that people like Amazon, Spotify give new artists, but I don't know if that support translates to full financial remuneration."
Lexicon, his first release on the independent label Cooking Vinyl, has reunited him with the team he worked with on his 2011 album, Echoes.
"When I'm creating something, be it the podcast I do (called Homo Sapiens) or music, I always kind of go very much on instinct and there's a great thing about being creative - I sort of have to remove myself out of the equation, which can sound very pretentious but it's kind of necessary," he says matter-of-factly.
"I wanted to do a sort of part two of an album that I'd done called Echoes, which I did with Richard X, the producer, and with two writers called Jim Eliot and Mima Stilwell, and we always said we wanted to do a sort of part two. I knew I wanted to do that so that meant it was going to fit within a genre of almost luxury electro pop, which is a word I've just made up!"
Love Island host Caroline Flack and Molly-Mae revealed to have dated the same man
Given that it's been nearly two decades since his music career took off, how much has he changed as an artist?
He explains: "I feel like it couldn't have gone any better, for me as an artist to find the evolution and to continue it and to come across the right people, be that Simon Fuller, who was my manager for years, to Steve Lipson, who produced so many amazing records from Annie Lennox to Whitney Houston, to working with people like Michael Gracey, who directed the Greatest Showman, you know, finding Richard X and writers like Jim and Mima.
The singer has celebrated a long career since winning Pop Idol (Image: Steve Schofield)
"They all allowed me to find my way through it."
For Lexicon he wanted to incorporate a host of new writers and voices.
"I didn't want to write as much as I have done in the past. I wanted to very much make it as easy and as joyous as possible, and sometimes I find writing extremely stressful," he says.
"I think it's getting to a stage when I feel like I proved myself as a songwriter, to myself really, apart from anyone else.
Elma Pazar and Maura Higgins are Love Island's newest contestants
"I'm confident enough to still have it as my work but I don't feel insecure - and I'm not saying other people feel this - but I don't feel insecure that people aren't going to take it seriously or see me as an artist or think that it's more throwaway.
"And actually it was about the benefit of a record because there's so many amazing writers and it's like, well why not... It's a bit like if I'm going to go on a dating app I might as well go on all of them because I'll spread the net, you know what I mean?"
He admits he had nearly reached a point where he didn't think he'd make music again. But it was the prospect of touring and performing live - as well as playing at Tom Kerridge's Pub in the Park (which he'll be doing again) that reignited his music flame.
He explains: "I didn't really want to do it anymore (music), I thought, 'Well, I've done my time and I'll go and train to be a psychotherapist', but it was the prospect of touring.
"I'd done a Pub in the Park gig (Kerridge's event) and I did this gig and I just suddenly thought and I said to the band, 'I think I'll go touring again' and that really brought me back into music, so the tour has been at the forefront of my mind."
There would have undoubtedly been a legion of his fans who'd have been devastated if he had thrown the towel in for good. But for Young, it's also been about finding a balance.
He says: "I just kind of recalibrated my work life, so I work four days a week and I work really hard in those four days, so that allows me then three days to do my other interests.
Jamie Oliver loves Cornwall
French and Saunders reunited in new film
The Voice winner performs at Truro shop
Doc Martin viewers fear series is over
"I'm not with a management company and that really works for me, because I'm not very good with authority and I've worked that out.
"So I don't have to have these clashes with people and I've worked out how I want to do a record and who I want to work with, then I get to work with these amazing people, like photographer and director Rankin and, you know, brilliant artists and it's just great fun."
Lexicon is out on June 21.
See the star "with friends" in concert at the Princess Theatre, Torquay on October 1 or Plymouth Pavilion on October 2. Get tickets here

redpajama_set_name: RedPajamaCommonCrawl


text:
Chef Anne Burrell Net Worth & Salary. Her Girlfriend Koren Grieveson & age.
WikiCelebInfo February 21, 2018
Ann Burrell is a renowned TV personality host, who started as a sous chef and went on to become a host of her own TV show, thanks to her natural talent for cooking. She has appeared in a number of cooking shows that have made a name for her. In 2015, she won the Chopper All-Star Tournament for her exquisite cooking, this made her even more popular and boosted her career. Let's find out about Chef Anne Burrell Net Worth. Also, meet her lesbian partner and girlfriend Koren Grieveson.
Chef Anne Burrell Net Worth: Her Salary.
Her career
Yes, Chef Anne Burrell is Lesbian. Meet her partner, Koren Grieveson.
Her Age and Birthday.
According to reliable sources, it is said the Food Network pays Burrell Salary about 50,000 dollars for her work in the kitchen program known as Secret of A Restaurant Chef for the network. Many people around the world lover her show so much. Given that huge salary she receives, we can assume Chef Anne Burrell Net Worth is pretty fat.
In the recent past, Anne has been working for the Food Network and is currently residing in the busy New York in a classy house. But she does not own an apartment, although she can afford it. It appears as if she is looking for a home near her workplace.
According to her, the best way to get to a person's heart is through food. The best invention that human beings have ever made is food.
In today's world, you can make a lot of money by being a Chef. Anne is one of the few celebrity Chefs in the world that make seven figures.
At the moment, Anne Burrell net worth stands at $5 million, which she has earned from her cooking skills, and being on various TV shows.
She became famous when she became a part of the Institute of Culinary Education and was the main character of the show Chef Wanted with Anne Brunell.
She has also been on the show known as Secrets of a Restaurant Chef. She has also appeared in other amazing cooking shows such as the Worst Cooks in America, in 2010.
Her next season was aired in 2017. Another notable show was known as The Iron Chef America which was aired in 2011.
Anne has appeared in over forty reality shows in her television career. However, some of her notable mentions include The Next Iron Chef, Food Network Star; Chef Wanted With Anne Burrell, The Best Thing I Ever Made, Guilty Pleasures, Rachel Ray, Beat Bobby Flay.
All these have made her a respectable person continue to sum up her overall net worth, getting endorsements and sponsors on her shows.
As far as this Chef's private life is concerned, Anne is a lesbian. She released a statement at the New York Post to confirm that she is actually lesbian and she has a girlfriend whom she has been dating for two years now.
It was alleged to have been exposed by author Ted Allen, but she denied that people presented her as lesbian, but her sexuality is out in public, and she has never kept her sexuality a secret.
Anne Burrell with girlfriend/ partner Koren Grieveson
In 31st December 2012, she tweeted publicly that she is engaged to her lesbian partner by the name Chef Koren Grieveson. The two have been dating for two months. However, she says she has no plans to get married sooner, and she seems to put her focus and time on her career now. Further, there are no records about her marriage or divorce in any of her previous relationships.
She was born on 21st Sept 1969 in New York. She is 47 years old as of writing this article. She was not a culinary student during her college years. As a matter of fact, she majored in English literature then. However, she forwent literature and dived into kitchen business. Her career kicked off from 1996 and ever since then she has never looked back.
Now you know Anne Burrell Net Worth and Salary. Leave us a comment.
David Grainger: Wiki-Bio: Net Worth, Age, Married, Wife
Egypt Sherrod Husband DJ Mike Jackson. Her Net Worth, Weight Loss, Sister, Ethnicity
Catfish star Nev Schulman Net worth 2018. His wife Laura Perlongo, age, height.


Home » Balance Transfer » Can I Balance Transfer a Personal Loan?
Can I Balance Transfer a Personal Loan?
2 Why do you need a personal loan balance transfer?
3 What are the steps to follow ?
Your details are secure and will not be shared without your consent.
Balance transfer became a big-name in the banking sector due to the increasing demand of customers just like you who began transferring their balances from one personal loan to another. As the personal loan transfer from one bank to another bank that gives better rates eases their financial concerns. So, if you are like – Can I balance transfer a personal loan? Well, the answer is a clear cut 'yes' you can. You can get your personal loan transferred from bank to another and not only save on interest but get higher loan amount as well. Who would not be tempted to go for such an offer? However, you must know the fact that there are many banks and lenders to choose from and all of them will offer you better rates.
Why do you need a personal loan balance transfer?
The main reason behind the balance transfer is that you get the opportunity to get a higher (Top-up loan) amount on your existing loan. Other than the higher loan amount, you get lower interest rates. So, if you want to transfer the balance and opt for top-up, you can get more money at lower interest rates and hence a handsome amount of savings in future, isn't it amazing?
What are the steps to follow ?
So, how are you going to pick one? Here is the guideline that you must look at before applying for a balance transfer.
The first step toward transferring the personal loan is to check the best offers in the market. Some of the best personal loan balance transfer schemes in the present market are given by SBI, ICICI Bank, HDFC Bank, Axis Bank and Citibank. So, you can choose the bank that gives you the most attractive offer as per your suitability.
Even if some banks try to attract you with reduced EMIs and increased tenure, you must know that your total outgo increases this way. So, compare the total outgo for both banks and then decide If there is no urgent need of money, prefer your current bank and try to pay off the loan if possible.
The processing fee is a percentage of the total loan amount that benefits banks. Act smartly and calculate the charges in rupees as your bank might increase the foreclosure charges of your personal loan since it is about balance transferring. However, the processing fee is a matter of change depending on the profile of the customer.
If you have cleared the major part of your loan and need a lesser amount, do not let the new lender have your complete collateral. If you have a secured personal loan, offer your new bank a lesser amount of collateral and choose the amount lesser than your collateral.
Do not get into any kind of frills that banks will generally show you, analyze whether you actually need them or not. The most common of all the gifts is a free credit card or a personal accident insurance or anything similar but make sure you accept them only if you need.
We are all educated enough to know that there are many terms and conditions in almost each and everything when it comes to buying or purchasing. However, when we ourselves are applying, we forget to read them and later feel cheated. So, read the terms and conditions thoroughly and then seal the deal.
Think about the pros and cons of the offer you are getting like why the lender is offering your lower rates and what this offer has for your benefits? Once you will be free from doubts, you will take the right decision for sure.
A personal loan transfer calculator is the calculator that takes in account the remaining loan amount of your existing personal loan, its rate of interest, loan tenure, the EMIs that you have paid and the new tenure you wish to choose.
Rate of interest: 12% p.a.
New Interest Rate: 13.75% p.a.
The interest rates offered on the balance transfer facility are generally lower than the original rate of interest on a personal loan. Whenever you are applying for a personal loan balance transfer, choose the lender that gives lower rates as compared to your existing personal loan otherwise transferring the personal loan would not make much sense.
So I hope now all the cobwebs related to your burning question, Can I balance transfer a Personal Loan, is cleared.


text:
Q: ManyToMany Hibernate in Kotlin I am trying to build Many To Many relationship in Kotlin as the following:
@Entity
data class Gender(@field:Id var abbr: Char? = null,
                  var description: String = "") : PanacheEntityBase

@Entity
data class Interest(
    var description: String = ""): PanacheEntity()

@Entity
data class User(@field:Id var id: UUID? = null,
                @ManyToOne(fetch = FetchType.LAZY) var gender: Gender? = null,
                var birthday: Long = 0,
                @ManyToMany(fetch = FetchType.LAZY, cascade = [CascadeType.PERSIST])
                @JoinTable(
                    name = "user_interests",
                    joinColumns = [JoinColumn(name = "user_id", referencedColumnName = "id")],
                    inverseJoinColumns = [JoinColumn(name = "interest_id", referencedColumnName = "id")]
                )
                var interests: List<Interest> = listOf()) : PanacheEntityBase

and I receive error messages:
GenerationTarget encountered exception accepting command : Error executing DDL "drop table if exists User cascade" via JDBC Statement: org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "drop table if exists User cascade" via JDBC Statement

Error executing DDL "create table User (id uuid not null, birthday int8 not null, gender_abbr char(1), primary key (id))" via JDBC Statement: org.hibernate.tool.schema.spi.CommandAcceptanceException: Error executing DDL "create table User (id uuid not null, birthday int8 not null, gender_abbr char(1), primary key (id))" via JDBC Statement

Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or near "User"
  Position: 22

What am I doing wrong?


text:
The Retirees in the South East USA – Onboard the PSS American Queen
When fronting at the Pursers desk to book our spot on the Hop on Hop off bus, all spots were gone. We were not beaten yet. So we left the boat after it had landed found a cab and for USD $8 we got a trip into up town Natchez with a guided tour by our cab driver.
Once we arrived up town we were dropped off at one of the hop on hop off bus stops and joined the tour. We decided not to await the bus but start our own tour by visiting the major church in town (catholic so nicely dressed up) then we walked to Magnolia Hall – see the feature photo above. Magnolia Hall was built by Thomas Henderson, a wealthy merchant, planter and cotton broker. The home is one of the finest examples in Natchez of the Greek Revival style. It is an antebellum home and during a bombardment of Natchez by the Union gunboat Essex, a shell hit the soup tureen in Magnolia Hall's kitchen.
The Natchez Garden Club has restored Magnolia Hall. Rooms on the main floor are filled with mid-nineteenth century antiques, while rooms on the upper floors contain a costume collection.
Note the picture of the plate warmer.
After the Hall we move onto the home of William Johnson. William T. Johnson (1809 – June 17, 1851) was a free African American barber of biracial parentage, who lived in Natchez, Mississippi. He was born into slavery but his owner, also named William Johnson and thought to be his father, emancipated him in 1820. His mother, Amy, had been freed in 1814 and his sister Adelia in 1818. Johnson trained with his brother-in-law James Miller as a barber, and began working in Port Gibson, Mississippi. He returned to Natchez, becoming a successful entrepreneur with a barbershop, bath house, bookstore, and land holdings. Though a former slave, William Johnson went on to own sixteen slaves himself. He began a diary in 1835, which he continued through the remainder of his life. In 1835, he married Ann Battle, a free woman of colour with a similar background to his, and they had eleven children. Johnson loaned money to many people, including the governor of Mississippi who had signed his emancipation papers.
Johnson was murdered in 1851 after an adjudicated boundary dispute, by a mixed-race neighbour named Baylor Winn, in front of his son, a free black apprentice, and a slave. Winn was held in prison for two years and brought to trial twice; Johnson was such a well-respected businessman that the outrage over his murder caused the trial to be held in a neighbouring town. In that town no one knew Winn, so they didn't know that he was half-black. Since Mississippi law forbade blacks from testifying against whites in criminal cases, Winn's defence was that he was half-white and half-Native American, making him white by law. The defence worked, none of the (black) witnesses could testify, and Winn escaped conviction. Johnson's diary was rediscovered in 1938 and published in 1951. It reveals much of the daily life of a 19th-century Mississippi businessman, including the fact that he was himself later a slaveholder. His papers are archived at Louisiana State University.
Through an act of Congress, the home of William Johnson became a part of the Natchez National Historical Park in 1990.
Here is a photo of the Johnson house and next door the Adams County Jail (Goal to us).
Natchez grew up in two parts Natchez below the Hill which provided for the boatmen and the handling of cargo and Natchez above the Hill which was built by the Spanish on the high ground for a fort and township not affected by the river. Our next stop was to visit the few remaining buildings forming Lower Natchez then return to the boat for lunch. Parked nearby was the American Duchess a sister boat of the American Queen.
In the afternoon we had booked to see a historic plantation with original slave quarters church cookhouse gin etc. Frogmore Plantation and Gin contrasts a working cotton plantation of the early 1800's with a modern cotton plantation and gin of today. Our tour started with a drive through the present-day gin -1800 acre cotton plantation with a computerized 900 bales-per-day cotton gin, then through the fields to the church where we heard songs from the fields from locals who had experienced this life. We listened to the slave customs, secret music, and their surprising relationships with the master, mistress, and overseer. We then walked through authentically furnished slave quarters, a relic of a rare steam gin, and other plantation dependencies.
Our day ended with a bus ride back to the American Queen a grand dinner in the dining room then the show. Tough life.
Posted on September 22, 2018 Categories USA - Florida MississippiTags Adams county, Frogmore Plantation, Magnolia Hall Natchez, Natchez, Natchez below the hill, Union gunboat Essex, William T Johnson


San Luis, Arizona — The City of San Luis offices will be closed on Monday, January 21st, 2019 in observance of Martin Luther King Jr. Day. Offices will resume regular business hours on Tuesday, January 22nd, 2019. Emergency and law enforcement services will remain available.
For Public Works emergency situations (i.e., water and sewer service emergencies) please call the Police Department Communications Division at (928) 341-2420.
Residential trash collection will change that week due to the holiday. Residents who normally have their trash collected on Monday and Thursday will have their trash collected on Tuesday and Thursday. Residents who normally have their trash collected on Tuesday and Friday will have their trash collected on Wednesday and Friday.


The article analyzes corelation of chosen indicators of economical development SR and points at direct infl uence in development of volume medial expenses in non specialized retail segment in conditions of SR. The article is also about development of particular economical indicators, medial expenses of chosen investors group in 2006 to 2011 and their inner structure. The aim of article is to point at how volume of top-heaviness fi nance resources in media relies on actual cyclical progress of economical indicators from the view of the four biggest investors in non specialized retail segment in Slovakia. The result of this article explicitly confi rms the presumption of corelation between chosen macroeconomic indicators and volume media expenses of select group of advertisers in non specialized retail segment and also the rule that the effi ciency of the national economy infl uences the effi ciency of individual businesses and their own communication activities with the target market.


text:
04/14/18 04/19/18 with 0 Comments
Samsung Galaxy S9 Features You Can't Live Without
Samsung Galaxy S9 and its larger counterpart S9+ came out one month ago and featured a great variety of features, some of them that we haven't yet seen. If you're still undecided whether you should invest in here are some Galaxy S9 features that may change your mind.
Samsung's new flagship phone came out in March 2018 and features an improved design over Galaxy S8 measuring 5.81 x 2.70 x 0.33 in and weighing 5.75 oz (163g.) It sports enhanced camera system, with 12 MP on the rear cameras and 8 MP on front-facing one. Its performance is also quite impressive with both Samsung Exynos 9810 chipset and Qualcomm Snapdragon 845 (USA and China.) The phone comes in three storage options (64,128 and 256GB) and 4GB of RAM. Here are some of its most notable features.
Super-Slow-Motion Recording Videos
Slow motion video is no stranger on other smartphones. On the other hand, Samsung's implementation of this feature shows quite a difference. The camera of Galaxy S9 and Galaxy S9+ is capable of slowing a video down to 960 frames per second at 720p resolution for 0.2 seconds in order to convert it into a 6-seconds long video clips you can after share on social media networks you use.
This is one of users' favorite Galaxy S9 features, because the camera lens intelligently detects action being performed in the frame, and then it slows it down, without additional editing required. There is also a manual mode that allows user to control what's happening in the slow-motion video, actions such as looping the clip, swinging it back and forth or reverse it.
Support for low light conditions
Have you ever wanted to take pictures of your friends in dark surroundings like bar, concert or a night walk? However, you couldn't do so because you were confronted by dreadful, dark conditions. HDR mode in most of phones partially fixed it problem. However, Samsung's camera takes a step forward.
One of the really useful Galaxy S9 features includes Samsung's dual aperture camera which approaches its photos in order for them to look sharper and clearer. According to Samsung, its new flagship smartphones are capable of perceiving 28% more light as opposed to the camera of Samsung Galaxy S8. All of that, thanks to the apertures either at f/1.5 or f/2.4.
Animated Emoji with AR
Animated emoji or Animoji were introduced with iPhone X and were totally worth the hype. However, animated emoji on Galaxy S9 won our hearts. The camera will smartly use your facial expressions to make an animated character that will still sort of remind others of you. While iPhoneX's animoji are designed to be witty and funny, the AR emoji work in a way to make your face look more realistic by utilizing the technology. It's worth pointing that Samsung doesn't use an depth sensor, so you will find resemblance with the extremely popular Bitmoji that are moving around.
In order to enhance security of its users, Samsung took several measures to make phones safe and private with the user. While Galaxy S8 offers three modes of authentication, Galaxy S9 features also come with the fourth authentication mode, known as Intelligent Scan. The method combines facial and iris scanning. Samsung played smart, so in case one of the methods failed to recognize you, you can use the other that won't fail. Reason for this is because facial recognition can fail when it's night. Nevertheless, Intelligent Scan security and accuracy can't be compared to the one of a fingerprint sensor, which Galaxy S9 is also equipped with. Still, it doesn't hurt to explore new authentication modes and see how they work.
New Location For Fingerprint Scanner
Dual lens camera is not the only new thing on the rear of Galaxy S9. It's no secret that one of the only reasons that made Galaxy S8 a lackluster phone was the irritating location of the fingerprint scanner. This time, the company decided to please the community and ended up placing the sensor beneath the camera, instead of next to it. That way users don't have to worry about messing up the lens while trying to unlock their phone but can precisely aim the fingerprint scanner beneath.
Those were some of the most notable Galaxy S9 features. If you already own Galaxy S9 check out most common issues that Samsung Galaxy S9 and S9+ are facing. Also, if your charging plug became dusty and is slowing down the charging process, take a look at dust plugs from our Amazon shop.
What is your favorite Galaxy S9 feature? Let us know in the comments.