What is Polkacover (CVR) | What is Polkacover token | What is CVR token

Polkacover is working towards creating the world’s leading cryptocurrency-friendly insurance purchase & policy issuance marketplace with the aim to be the one stop-shop for crypto & personal insurance need…

At Polkacover, we will connect users & multi-national insurance providers with all global insurance products such as crypto related protection, health, life, education & family insurance plans to start with and would be working towards adding more products in the longer run. The platform would providing several tokenized incentives making upto 40% cheaper than any traditional insurance channel.

We are developing a frictionless insurance marketplace experience that incorporates next generation blockchain technology based on Web 3.0 framework on Polkadot using sbstrate providing tokenized incentives. By building a state-of-the-art user experience and several cryptocurrency and traditional payment options alongside benefits tied to our proprietary cryptocurrency. our users know they are purchasing through a platform of the future with transparent pricing

Why POLKACOVER?

The vision and mission of POLKACOVER.

Over the years, with giant leaps in technologies in several industries, insurance companies and brokerages seem to be stuck in a time capsule. PolkaCover was created as a solution to beat archaic manual systems and break open the industries from their shells.

Founded in late 2019 by seasoned insurtech, fintech, and blockchain experts, Polkacover believes in creating a well-developed marketplace connecting users and insurance products from around the world. This belief led to a mission to investigate the best options to create next-generation insurance management with a vision to cater to the needs of the growing crypto world.

Polkacover has four main roles it would fulfill within the insurance space.

The platform is developed in four phases:

• Phase 1: Polkacover cryptobased products
• Phase 2: Global insurance marketplace
• Phase 3: Polkacover P2P ( Insurance DAO )
• Phase 4: Autonomous third party administration/claims management for third party insurance companies

The crypto insurance platform aims to develop this dynamic insurance marketplace through the four development phases. The** vision** of the seasoned team is to bring to the crypto ecosystem as a whole, enhanced security, and unparalleled end-user ease of interaction. We want everyone to be safeguarded against the bad actors which plague crypto users.

The team is working hard behind the scene, building up ecosystem partners inside & outside the cryptosphere. Polkacover’s future is definitely a bright and interesting one that everyone is looking forward to!

Why Blockchain for the Polkacover ecosystem

Insurance is traded in traditional ways, often manually and with several layers of intermediaries. The inefficiencies have resulted in most of the major insurance institutions taking a keen interest in blockchain technology with the hope it will provide a modern, more streamlined alternative. The McKinsey Panorama FinTech database currently registers over 200 blockchain-related solutions, of which about 20 provide use cases for insurers that go beyond payment transactions — either as specific applications or as base platforms.

Finally, even traditional insurance companies, such as AXA and Generali, have started to invest in blockchain applications and Allianz has just recently announced its successful pilot of a blockchain-based smart contract solution to automate catastrophe swap transactions. Within Dubai as well, Blockchain startups are being encourage as Dubai aims to be the Blockchain capital of the World by 2020.

The blockchain provide a decentralized ledger which allows data to be permanently stored without the possibility of fraud. With the growing importance data protection, the ability to control the data in this form dramatically affects the type of communication between consumers and businesses.

For us, we found blockchain was able to provide vast improvements over centralized systems in terms of CRM Management, cross-country scaling & payment solutions, data integrity, improved user experience with the option of efficient claims management as well. It gives superpowers to the insurance industry focusing on granular level of customer-segmentation, tailored products, predicting customer behavior, targeted customer service, and an overall enhanced customer journey.

Blockchain’s enablement of increased trust and transparency speaks to the heart of the insurance business

Smart contracts have the ability to be designed to be decision makers on insurance claim settlements (based on pre-underwritten fundamentals).

Groups of participants not individually eligible for the suitable insurance coverage might use the decentralized trust and autonomous processing smart contract capability of blockchains to self-insure the group by sharing risk at a reduced cost.

The secure storage of a policy holder’s information helps in removing the manual processes which are being followed where there is duplication of information (at the broker, insurance company and customer’s end) thus reducing data redundancy and reduce the possibility of misinformation. The public registry (and decentralized nature of blockchain) removes the possibility of loss of data over years.

Reduce administrative cost Blockchain may reduce administrative/operations cost through automated verification of policyholder identity and contract validity, auditable registration of claims and data.

Customer engagement. An important lever for improving customer engagement through blockchain lies in the area of personal data. Customers’ fears about losing control of personal data as soon as it is handed over to a company and their frustration with the need to repeat data entry processes can be addressed by a customer-controlled blockchain for identity verification (see KYC use case) or medical/health data. Personal data does not need to be stored on the blockchain; it remains on the user’s personal device.

PolkaCover Updated Tokenomics

Over the last month, we have had a few changes on our Tokenomics structure. Please find below the updated Tokenomics details & Schedule for the PolkaCover project. The information below supersedes the information provided in the whitepaper as of 7th January 2021

TOKEN DETAILS

TOKEN ALLOCATION

TEAM

CVR tokens reserved for the CVR Founding team. Team tokens are locked and vested to demonstrate long-term commitment.

• Tokens locked for 24 months
• After lockup, tokens are vested over 6 months

ADVISORS

CVR tokens reserved for the PolkaCover advisory board. These tokens are vested to demonstrate long-term commitment.

MARKETING & OPERATIONAL EXPENSES

PolkaCover has the funds needed to manage its costs for running its operations for a period of 12–18months. These CVR tokens reserved for future objectives like immediate operational expansion requirement, broad marketing initiative, regulatory & compliance clearances, business expanis exchange listings etc.

• Operational Tokens — Locked for 12 months followed by 12 month vesting
• Marketing Tokens — Locked for 6 months followed by 18 month vesting

TREASURY & INCENTIVES

CVR tokens are reserved to fuel the growth of the covercompared.com platform being developed by the PolkaCover team. The tokens will be used to build token adoption within the platform once it goes live.

• Tokens are locked for 3 months
• After lockup, tokens are released equally over 36 months.

STAKING & COMMUNITY REWARDS

This is a “Go-To-Market” FUND which would be required to build the community involvement within the platform. The CVR tokens will be used to

• Provide liquidity at launch at UniSwap
• Provide Staking rewards/allocations for early adopters, governance & risk assessment members
• Bug bounty programs & early testers of the platform
• Governance & Risk Assessment rewards within the P2P platform
• Tokens are released equally over 24 months.

All the reserved allocation would be unlocked as per schedule but this does not mean it will necessary be in circulation. The PolkaCover team would be distributed at the discretion of the board. Distribution is primarily used to fuel the growth and expansion of the project over the years to come and may hold/delay the release of the tokens if the need does not arise.

CIRCULATING SUPPLY

USE OF FUNDS

Funds raised through the Private and Crowdsale round will be used to develop and to support the liquidity of the CVR token & platform. The PolkaCover is well funded to manage the growth & expenses for a period of 12–18 months

This includes:

1. Liquidity, tech and product development. CVR anticipates launching its Web 3.0 Insurance marketplace platform in 6 months after the crowdsale completed. To prepare our future ecosystem, will devote significant resources for risk liquidity and market expansion as required.

2. General marketing and development expenses such as website development, advertising materials, outreach, community, partnership and customer development.

Looking for more information…

☞ Website ☞ Explorer ☞ Explorer 2 ☞ Whitepaper ☞ Source Code ☞ Social Channel ☞ Social Channel 2 ☞ Message Board ☞ Coinmarketcap

Would you like to earn CVR right now! ☞ CLICK HERE

Top exchanges for token-coin trading. Follow instructions and make unlimited money

☞ Binance ☞ Bittrex ☞ Poloniex ☞ Bitfinex ☞ Huobi

Thank for visiting and reading this article! I’m highly appreciate your actions! Please share if you liked it!

#blockchain #bitcoin #polkacover #cvr

What is GEEK

Buddha Community

What is Polkacover (CVR) | What is Polkacover token | What is CVR token

Polkacover is working towards creating the world’s leading cryptocurrency-friendly insurance purchase & policy issuance marketplace with the aim to be the one stop-shop for crypto & personal insurance need…

At Polkacover, we will connect users & multi-national insurance providers with all global insurance products such as crypto related protection, health, life, education & family insurance plans to start with and would be working towards adding more products in the longer run. The platform would providing several tokenized incentives making upto 40% cheaper than any traditional insurance channel.

We are developing a frictionless insurance marketplace experience that incorporates next generation blockchain technology based on Web 3.0 framework on Polkadot using sbstrate providing tokenized incentives. By building a state-of-the-art user experience and several cryptocurrency and traditional payment options alongside benefits tied to our proprietary cryptocurrency. our users know they are purchasing through a platform of the future with transparent pricing

Why POLKACOVER?

The vision and mission of POLKACOVER.

Over the years, with giant leaps in technologies in several industries, insurance companies and brokerages seem to be stuck in a time capsule. PolkaCover was created as a solution to beat archaic manual systems and break open the industries from their shells.

Founded in late 2019 by seasoned insurtech, fintech, and blockchain experts, Polkacover believes in creating a well-developed marketplace connecting users and insurance products from around the world. This belief led to a mission to investigate the best options to create next-generation insurance management with a vision to cater to the needs of the growing crypto world.

Polkacover has four main roles it would fulfill within the insurance space.

The platform is developed in four phases:

• Phase 1: Polkacover cryptobased products
• Phase 2: Global insurance marketplace
• Phase 3: Polkacover P2P ( Insurance DAO )
• Phase 4: Autonomous third party administration/claims management for third party insurance companies

The crypto insurance platform aims to develop this dynamic insurance marketplace through the four development phases. The** vision** of the seasoned team is to bring to the crypto ecosystem as a whole, enhanced security, and unparalleled end-user ease of interaction. We want everyone to be safeguarded against the bad actors which plague crypto users.

The team is working hard behind the scene, building up ecosystem partners inside & outside the cryptosphere. Polkacover’s future is definitely a bright and interesting one that everyone is looking forward to!

Why Blockchain for the Polkacover ecosystem

Insurance is traded in traditional ways, often manually and with several layers of intermediaries. The inefficiencies have resulted in most of the major insurance institutions taking a keen interest in blockchain technology with the hope it will provide a modern, more streamlined alternative. The McKinsey Panorama FinTech database currently registers over 200 blockchain-related solutions, of which about 20 provide use cases for insurers that go beyond payment transactions — either as specific applications or as base platforms.

Finally, even traditional insurance companies, such as AXA and Generali, have started to invest in blockchain applications and Allianz has just recently announced its successful pilot of a blockchain-based smart contract solution to automate catastrophe swap transactions. Within Dubai as well, Blockchain startups are being encourage as Dubai aims to be the Blockchain capital of the World by 2020.

The blockchain provide a decentralized ledger which allows data to be permanently stored without the possibility of fraud. With the growing importance data protection, the ability to control the data in this form dramatically affects the type of communication between consumers and businesses.

For us, we found blockchain was able to provide vast improvements over centralized systems in terms of CRM Management, cross-country scaling & payment solutions, data integrity, improved user experience with the option of efficient claims management as well. It gives superpowers to the insurance industry focusing on granular level of customer-segmentation, tailored products, predicting customer behavior, targeted customer service, and an overall enhanced customer journey.

Blockchain’s enablement of increased trust and transparency speaks to the heart of the insurance business

Smart contracts have the ability to be designed to be decision makers on insurance claim settlements (based on pre-underwritten fundamentals).

Groups of participants not individually eligible for the suitable insurance coverage might use the decentralized trust and autonomous processing smart contract capability of blockchains to self-insure the group by sharing risk at a reduced cost.

The secure storage of a policy holder’s information helps in removing the manual processes which are being followed where there is duplication of information (at the broker, insurance company and customer’s end) thus reducing data redundancy and reduce the possibility of misinformation. The public registry (and decentralized nature of blockchain) removes the possibility of loss of data over years.

Reduce administrative cost Blockchain may reduce administrative/operations cost through automated verification of policyholder identity and contract validity, auditable registration of claims and data.

Customer engagement. An important lever for improving customer engagement through blockchain lies in the area of personal data. Customers’ fears about losing control of personal data as soon as it is handed over to a company and their frustration with the need to repeat data entry processes can be addressed by a customer-controlled blockchain for identity verification (see KYC use case) or medical/health data. Personal data does not need to be stored on the blockchain; it remains on the user’s personal device.

PolkaCover Updated Tokenomics

Over the last month, we have had a few changes on our Tokenomics structure. Please find below the updated Tokenomics details & Schedule for the PolkaCover project. The information below supersedes the information provided in the whitepaper as of 7th January 2021

TOKEN DETAILS

TOKEN ALLOCATION

TEAM

CVR tokens reserved for the CVR Founding team. Team tokens are locked and vested to demonstrate long-term commitment.

• Tokens locked for 24 months
• After lockup, tokens are vested over 6 months

ADVISORS

CVR tokens reserved for the PolkaCover advisory board. These tokens are vested to demonstrate long-term commitment.

MARKETING & OPERATIONAL EXPENSES

PolkaCover has the funds needed to manage its costs for running its operations for a period of 12–18months. These CVR tokens reserved for future objectives like immediate operational expansion requirement, broad marketing initiative, regulatory & compliance clearances, business expanis exchange listings etc.

• Operational Tokens — Locked for 12 months followed by 12 month vesting
• Marketing Tokens — Locked for 6 months followed by 18 month vesting

TREASURY & INCENTIVES

CVR tokens are reserved to fuel the growth of the covercompared.com platform being developed by the PolkaCover team. The tokens will be used to build token adoption within the platform once it goes live.

• Tokens are locked for 3 months
• After lockup, tokens are released equally over 36 months.

STAKING & COMMUNITY REWARDS

This is a “Go-To-Market” FUND which would be required to build the community involvement within the platform. The CVR tokens will be used to

• Provide liquidity at launch at UniSwap
• Provide Staking rewards/allocations for early adopters, governance & risk assessment members
• Bug bounty programs & early testers of the platform
• Governance & Risk Assessment rewards within the P2P platform
• Tokens are released equally over 24 months.

All the reserved allocation would be unlocked as per schedule but this does not mean it will necessary be in circulation. The PolkaCover team would be distributed at the discretion of the board. Distribution is primarily used to fuel the growth and expansion of the project over the years to come and may hold/delay the release of the tokens if the need does not arise.

CIRCULATING SUPPLY

USE OF FUNDS

Funds raised through the Private and Crowdsale round will be used to develop and to support the liquidity of the CVR token & platform. The PolkaCover is well funded to manage the growth & expenses for a period of 12–18 months

This includes:

1. Liquidity, tech and product development. CVR anticipates launching its Web 3.0 Insurance marketplace platform in 6 months after the crowdsale completed. To prepare our future ecosystem, will devote significant resources for risk liquidity and market expansion as required.

2. General marketing and development expenses such as website development, advertising materials, outreach, community, partnership and customer development.

Looking for more information…

☞ Website ☞ Explorer ☞ Explorer 2 ☞ Whitepaper ☞ Source Code ☞ Social Channel ☞ Social Channel 2 ☞ Message Board ☞ Coinmarketcap

Would you like to earn CVR right now! ☞ CLICK HERE

Top exchanges for token-coin trading. Follow instructions and make unlimited money

☞ Binance ☞ Bittrex ☞ Poloniex ☞ Bitfinex ☞ Huobi

Thank for visiting and reading this article! I’m highly appreciate your actions! Please share if you liked it!

#blockchain #bitcoin #polkacover #cvr

Words Counted: A Ruby Natural Language Processor.

WordsCounted

We are all in the gutter, but some of us are looking at the stars.

-- Oscar Wilde

WordsCounted is a Ruby NLP (natural language processor). WordsCounted lets you implement powerful tokensation strategies with a very flexible tokeniser class.

Are you using WordsCounted to do something interesting? Please tell me about it.

 

Demo

Visit this website for one example of what you can do with WordsCounted.

Features

• Out of the box, get the following data from any string or readable file, or URL:
  • Token count and unique token count
  • Token densities, frequencies, and lengths
  • Char count and average chars per token
  • The longest tokens and their lengths
  • The most frequent tokens and their frequencies.
• A flexible way to exclude tokens from the tokeniser. You can pass a string, regexp, symbol, lambda, or an array of any combination of those types for powerful tokenisation strategies.
• Pass your own regexp rules to the tokeniser if you prefer. The default regexp filters special characters but keeps hyphens and apostrophes. It also plays nicely with diacritics (UTF and unicode characters): Bayrūt is treated as ["Bayrūt"] and not ["Bayr", "ū", "t"], for example.
• Opens and reads files. Pass in a file path or a url instead of a string.

Installation

Add this line to your application's Gemfile:

gem 'words_counted'

And then execute:

$ bundle

Or install it yourself as:

$ gem install words_counted

Usage

Pass in a string or a file path, and an optional filter and/or regexp.

counter = WordsCounted.count(
  "We are all in the gutter, but some of us are looking at the stars."
)

# Using a file
counter = WordsCounted.from_file("path/or/url/to/my/file.txt")

.count and .from_file are convenience methods that take an input, tokenise it, and return an instance of WordsCounted::Counter initialized with the tokens. The WordsCounted::Tokeniser and WordsCounted::Counter classes can be used alone, however.

API

WordsCounted

WordsCounted.count(input, options = {})

Tokenises input and initializes a WordsCounted::Counter object with the resulting tokens.

counter = WordsCounted.count("Hello Beirut!")

Accepts two options: exclude and regexp. See Excluding tokens from the analyser and Passing in a custom regexp respectively.

WordsCounted.from_file(path, options = {})

Reads and tokenises a file, and initializes a WordsCounted::Counter object with the resulting tokens.

counter = WordsCounted.from_file("hello_beirut.txt")

Accepts the same options as .count.

Tokeniser

The tokeniser allows you to tokenise text in a variety of ways. You can pass in your own rules for tokenisation, and apply a powerful filter with any combination of rules as long as they can boil down into a lambda.

Out of the box the tokeniser includes only alpha chars. Hyphenated tokens and tokens with apostrophes are considered a single token.

#tokenise([pattern: TOKEN_REGEXP, exclude: nil])

tokeniser = WordsCounted::Tokeniser.new("Hello Beirut!").tokenise

# With `exclude`
tokeniser = WordsCounted::Tokeniser.new("Hello Beirut!").tokenise(exclude: "hello")

# With `pattern`
tokeniser = WordsCounted::Tokeniser.new("I <3 Beirut!").tokenise(pattern: /[a-z]/i)

See Excluding tokens from the analyser and Passing in a custom regexp for more information.

Counter

The WordsCounted::Counter class allows you to collect various statistics from an array of tokens.

#token_count

Returns the token count of a given string.

counter.token_count #=> 15

#token_frequency

Returns a sorted (unstable) two-dimensional array where each element is a token and its frequency. The array is sorted by frequency in descending order.

counter.token_frequency

[
  ["the", 2],
  ["are", 2],
  ["we",  1],
  # ...
  ["all", 1]
]

#most_frequent_tokens

Returns a hash where each key-value pair is a token and its frequency.

counter.most_frequent_tokens

{ "are" => 2, "the" => 2 }

#token_lengths

Returns a sorted (unstable) two-dimentional array where each element contains a token and its length. The array is sorted by length in descending order.

counter.token_lengths

[
  ["looking", 7],
  ["gutter",  6],
  ["stars",   5],
  # ...
  ["in",      2]
]

#longest_tokens

Returns a hash where each key-value pair is a token and its length.

counter.longest_tokens

{ "looking" => 7 }

#token_density([ precision: 2 ])

Returns a sorted (unstable) two-dimentional array where each element contains a token and its density as a float, rounded to a precision of two. The array is sorted by density in descending order. It accepts a precision argument, which must be a float.

counter.token_density

[
  ["are",     0.13],
  ["the",     0.13],
  ["but",     0.07 ],
  # ...
  ["we",      0.07 ]
]

#char_count

Returns the char count of tokens.

counter.char_count #=> 76

#average_chars_per_token([ precision: 2 ])

Returns the average char count per token rounded to two decimal places. Accepts a precision argument which defaults to two. Precision must be a float.

counter.average_chars_per_token #=> 4

#uniq_token_count

Returns the number of unique tokens.

counter.uniq_token_count #=> 13

Excluding tokens from the tokeniser

You can exclude anything you want from the input by passing the exclude option. The exclude option accepts a variety of filters and is extremely flexible.

1. A space-delimited string. The filter will normalise the string.
2. A regular expression.
3. A lambda.
4. A symbol that names a predicate method. For example :odd?.
5. An array of any combination of the above.

tokeniser =
  WordsCounted::Tokeniser.new(
    "Magnificent! That was magnificent, Trevor."
  )

# Using a string
tokeniser.tokenise(exclude: "was magnificent")
# => ["that", "trevor"]

# Using a regular expression
tokeniser.tokenise(exclude: /trevor/)
# => ["magnificent", "that", "was", "magnificent"]

# Using a lambda
tokeniser.tokenise(exclude: ->(t) { t.length < 4 })
# => ["magnificent", "that", "magnificent", "trevor"]

# Using symbol
tokeniser = WordsCounted::Tokeniser.new("Hello! محمد")
tokeniser.tokenise(exclude: :ascii_only?)
# => ["محمد"]

# Using an array
tokeniser = WordsCounted::Tokeniser.new(
  "Hello! اسماءنا هي محمد، كارولينا، سامي، وداني"
)
tokeniser.tokenise(
  exclude: [:ascii_only?, /محمد/, ->(t) { t.length > 6}, "و"]
)
# => ["هي", "سامي", "وداني"]

Passing in a custom regexp

The default regexp accounts for letters, hyphenated tokens, and apostrophes. This means twenty-one is treated as one token. So is Mohamad's.

/[\p{Alpha}\-']+/

You can pass your own criteria as a Ruby regular expression to split your string as desired.

For example, if you wanted to include numbers, you can override the regular expression:

counter = WordsCounted.count("Numbers 1, 2, and 3", pattern: /[\p{Alnum}\-']+/)
counter.tokens
#=> ["numbers", "1", "2", "and", "3"]

Opening and reading files

Use the from_file method to open files. from_file accepts the same options as .count. The file path can be a URL.

counter = WordsCounted.from_file("url/or/path/to/file.text")

Gotchas

A hyphen used in leu of an em or en dash will form part of the token. This affects the tokeniser algorithm.

counter = WordsCounted.count("How do you do?-you are well, I see.")
counter.token_frequency

[
  ["do",   2],
  ["how",  1],
  ["you",  1],
  ["-you", 1], # WTF, mate!
  ["are",  1],
  # ...
]

In this example -you and you are separate tokens. Also, the tokeniser does not include numbers by default. Remember that you can pass your own regular expression if the default behaviour does not fit your needs.

A note on case sensitivity

The program will normalise (downcase) all incoming strings for consistency and filters.

Roadmap

Ability to open URLs

def self.from_url
  # open url and send string here after removing html
end

Contributors

See contributors.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

---

Author: abitdodgy
Source code: https://github.com/abitdodgy/words_counted
License: MIT license

#ruby  #ruby-on-rails 

WordsCounted: A Ruby Natural Language Processor

WordsCounted

We are all in the gutter, but some of us are looking at the stars.

-- Oscar Wilde

WordsCounted is a Ruby NLP (natural language processor). WordsCounted lets you implement powerful tokensation strategies with a very flexible tokeniser class.

Features

• Out of the box, get the following data from any string or readable file, or URL:
  • Token count and unique token count
  • Token densities, frequencies, and lengths
  • Char count and average chars per token
  • The longest tokens and their lengths
  • The most frequent tokens and their frequencies.
• A flexible way to exclude tokens from the tokeniser. You can pass a string, regexp, symbol, lambda, or an array of any combination of those types for powerful tokenisation strategies.
• Pass your own regexp rules to the tokeniser if you prefer. The default regexp filters special characters but keeps hyphens and apostrophes. It also plays nicely with diacritics (UTF and unicode characters): Bayrūt is treated as ["Bayrūt"] and not ["Bayr", "ū", "t"], for example.
• Opens and reads files. Pass in a file path or a url instead of a string.

Installation

Add this line to your application's Gemfile:

gem 'words_counted'

And then execute:

$ bundle

Or install it yourself as:

$ gem install words_counted

Usage

Pass in a string or a file path, and an optional filter and/or regexp.

counter = WordsCounted.count(
  "We are all in the gutter, but some of us are looking at the stars."
)

# Using a file
counter = WordsCounted.from_file("path/or/url/to/my/file.txt")

.count and .from_file are convenience methods that take an input, tokenise it, and return an instance of WordsCounted::Counter initialized with the tokens. The WordsCounted::Tokeniser and WordsCounted::Counter classes can be used alone, however.

API

WordsCounted

WordsCounted.count(input, options = {})

Tokenises input and initializes a WordsCounted::Counter object with the resulting tokens.

counter = WordsCounted.count("Hello Beirut!")

Accepts two options: exclude and regexp. See Excluding tokens from the analyser and Passing in a custom regexp respectively.

WordsCounted.from_file(path, options = {})

Reads and tokenises a file, and initializes a WordsCounted::Counter object with the resulting tokens.

counter = WordsCounted.from_file("hello_beirut.txt")

Accepts the same options as .count.

Tokeniser

The tokeniser allows you to tokenise text in a variety of ways. You can pass in your own rules for tokenisation, and apply a powerful filter with any combination of rules as long as they can boil down into a lambda.

Out of the box the tokeniser includes only alpha chars. Hyphenated tokens and tokens with apostrophes are considered a single token.

#tokenise([pattern: TOKEN_REGEXP, exclude: nil])

tokeniser = WordsCounted::Tokeniser.new("Hello Beirut!").tokenise

# With `exclude`
tokeniser = WordsCounted::Tokeniser.new("Hello Beirut!").tokenise(exclude: "hello")

# With `pattern`
tokeniser = WordsCounted::Tokeniser.new("I <3 Beirut!").tokenise(pattern: /[a-z]/i)

See Excluding tokens from the analyser and Passing in a custom regexp for more information.

Counter

The WordsCounted::Counter class allows you to collect various statistics from an array of tokens.

#token_count

Returns the token count of a given string.

counter.token_count #=> 15

#token_frequency

Returns a sorted (unstable) two-dimensional array where each element is a token and its frequency. The array is sorted by frequency in descending order.

counter.token_frequency

[
  ["the", 2],
  ["are", 2],
  ["we",  1],
  # ...
  ["all", 1]
]

#most_frequent_tokens

Returns a hash where each key-value pair is a token and its frequency.

counter.most_frequent_tokens

{ "are" => 2, "the" => 2 }

#token_lengths

Returns a sorted (unstable) two-dimentional array where each element contains a token and its length. The array is sorted by length in descending order.

counter.token_lengths

[
  ["looking", 7],
  ["gutter",  6],
  ["stars",   5],
  # ...
  ["in",      2]
]

#longest_tokens

Returns a hash where each key-value pair is a token and its length.

counter.longest_tokens

{ "looking" => 7 }

#token_density([ precision: 2 ])

Returns a sorted (unstable) two-dimentional array where each element contains a token and its density as a float, rounded to a precision of two. The array is sorted by density in descending order. It accepts a precision argument, which must be a float.

counter.token_density

[
  ["are",     0.13],
  ["the",     0.13],
  ["but",     0.07 ],
  # ...
  ["we",      0.07 ]
]

#char_count

Returns the char count of tokens.

counter.char_count #=> 76

#average_chars_per_token([ precision: 2 ])

Returns the average char count per token rounded to two decimal places. Accepts a precision argument which defaults to two. Precision must be a float.

counter.average_chars_per_token #=> 4

#uniq_token_count

Returns the number of unique tokens.

counter.uniq_token_count #=> 13

Excluding tokens from the tokeniser

You can exclude anything you want from the input by passing the exclude option. The exclude option accepts a variety of filters and is extremely flexible.

1. A space-delimited string. The filter will normalise the string.
2. A regular expression.
3. A lambda.
4. A symbol that names a predicate method. For example :odd?.
5. An array of any combination of the above.

tokeniser =
  WordsCounted::Tokeniser.new(
    "Magnificent! That was magnificent, Trevor."
  )

# Using a string
tokeniser.tokenise(exclude: "was magnificent")
# => ["that", "trevor"]

# Using a regular expression
tokeniser.tokenise(exclude: /trevor/)
# => ["magnificent", "that", "was", "magnificent"]

# Using a lambda
tokeniser.tokenise(exclude: ->(t) { t.length < 4 })
# => ["magnificent", "that", "magnificent", "trevor"]

# Using symbol
tokeniser = WordsCounted::Tokeniser.new("Hello! محمد")
tokeniser.tokenise(exclude: :ascii_only?)
# => ["محمد"]

# Using an array
tokeniser = WordsCounted::Tokeniser.new(
  "Hello! اسماءنا هي محمد، كارولينا، سامي، وداني"
)
tokeniser.tokenise(
  exclude: [:ascii_only?, /محمد/, ->(t) { t.length > 6}, "و"]
)
# => ["هي", "سامي", "وداني"]

Passing in a custom regexp

The default regexp accounts for letters, hyphenated tokens, and apostrophes. This means twenty-one is treated as one token. So is Mohamad's.

/[\p{Alpha}\-']+/

You can pass your own criteria as a Ruby regular expression to split your string as desired.

For example, if you wanted to include numbers, you can override the regular expression:

counter = WordsCounted.count("Numbers 1, 2, and 3", pattern: /[\p{Alnum}\-']+/)
counter.tokens
#=> ["numbers", "1", "2", "and", "3"]

Opening and reading files

Use the from_file method to open files. from_file accepts the same options as .count. The file path can be a URL.

counter = WordsCounted.from_file("url/or/path/to/file.text")

Gotchas

A hyphen used in leu of an em or en dash will form part of the token. This affects the tokeniser algorithm.

counter = WordsCounted.count("How do you do?-you are well, I see.")
counter.token_frequency

[
  ["do",   2],
  ["how",  1],
  ["you",  1],
  ["-you", 1], # WTF, mate!
  ["are",  1],
  # ...
]

In this example -you and you are separate tokens. Also, the tokeniser does not include numbers by default. Remember that you can pass your own regular expression if the default behaviour does not fit your needs.

A note on case sensitivity

The program will normalise (downcase) all incoming strings for consistency and filters.

Roadmap

Ability to open URLs

def self.from_url
  # open url and send string here after removing html
end

---

Are you using WordsCounted to do something interesting? Please tell me about it.

 

RubyDoc documentation.

Demo

Visit this website for one example of what you can do with WordsCounted.

---

Contributors

See contributors.

Contributing

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request

Author: Abitdodgy
Source Code: https://github.com/abitdodgy/words_counted 
License: MIT license

#ruby #nlp 

SafeMoon Clone | Create A DeFi Token Like SafeMoon | DeFi token like SafeMoon

SafeMoon is a decentralized finance (DeFi) token. This token consists of RFI tokenomics and auto-liquidity generating protocol. A DeFi token like SafeMoon has reached the mainstream standards under the Binance Smart Chain. Its success and popularity have been immense, thus, making the majority of the business firms adopt this style of cryptocurrency as an alternative.

A DeFi token like SafeMoon is almost similar to the other crypto-token, but the only difference being that it charges a 10% transaction fee from the users who sell their tokens, in which 5% of the fee is distributed to the remaining SafeMoon owners. This feature rewards the owners for holding onto their tokens.

Read More @ https://bit.ly/3oFbJoJ

#create a defi token like safemoon #defi token like safemoon #safemoon token #safemoon token clone #defi token

SafeMoon Clone | SafeMoon Token Clone | SafeMoon Token Clone Development

The SafeMoon Token Clone Development is the new trendsetter in the digital world that brought significant changes to benefit the growth of investors’ business in a short period. The SafeMoon token clone is the most widely discussed topic among global users for its value soaring high in the marketplace. The SafeMoon token development is a combination of RFI tokenomics and the auto-liquidity generating process. The SafeMoon token is a replica of decentralized finance (DeFi) tokens that are highly scalable and implemented with tamper-proof security.

The SafeMoon tokens execute efficient functionalities like RFI Static Rewards, Automated Liquidity Provisions, and Automatic Token Burns. The SafeMoon token is considered the most advanced stable coin in the crypto market. It gained global audience attention for managing the stability of asset value without any fluctuations in the marketplace. The SafeMoon token clone is completely decentralized that eliminates the need for intermediaries and benefits the users with less transaction fee and wait time to overtake the traditional banking process.

Reasons to invest in SafeMoon Token Clone :

• The SafeMoon token clone benefits the investors with Automated Liquidity Pool as a unique feature since it adds more revenue for their business growth in less time. The traders can experience instant trade round the clock for reaping profits with less investment towards the SafeMoon token.
• It is integrated with high-end security protocols like two-factor authentication and signature process to prevent various hacks and vulnerable activities. The Smart Contract system in SafeMoon token development manages the overall operation of transactions without any delay,
• The users can obtain a reward amount based on the volume of SafeMoon tokens traded in the marketplace. The efficient trading mechanism allows the users to trade the SafeMoon tokens at the best price for farming. The user can earn higher rewards based on the staking volume of tokens by users in the trade market.
• It allows the token holders to gain complete ownership over their SafeMoon tokens after purchasing from DeFi exchanges. The SafeMoon community governs the token distribution, price fluctuations, staking, and every other token activity. The community boosts the value of SafeMoon tokens.
• The Automated Burning tokens result in the community no longer having control over the SafeMoon tokens. Instead, the community can control the burn of the tokens efficiently for promoting its value in the marketplace. The transaction of SafeMoon tokens on the blockchain platform is fast, safe, and secure.

The SafeMoon Token Clone Development is a promising future for upcoming investors and startups to increase their business revenue in less time. The SafeMoon token clone has great demand in the real world among millions of users for its value in the market. Investors can contact leading Infinite Block Tech to gain proper assistance in developing a world-class SafeMoon token clone that increases the business growth in less time.

#safemoon token #safemoon token clone #safemoon token clone development #defi token