Taylor 1

Taylor 1  sinhala chichtra kathawa 

Sell My Annuity for Cash in the USA (Velamma EP 01)

Velamma EP 01

Velamma EP 01 chithrakatha story  Download







When her son’s friend needs her help, Velamma is ready to do anything to help him out. But where will it lead her? This is how it all started!

With the biggest payouts in North America we wanted to extend a special thank you to all of our Annuitants for making us the largest buyer. Thanks to great customer service and maximizing our payouts to annuitants just like yourself we continue to excel in the market.

Have an annuity payment that you want to trade in for cash now? Well today you can cash in your annuity with “CIYA” the leader in fast payouts for annuitants. Are program designated to purchase your annuity payments are facilitated and limited to residents of the United States so if you are in Canada, Mexico, or Central America then we are not easily able to facilitate a deal for yourself.

Our process of selling annuity payment streams are fast and simple. Our expert advisory staff work with you based on your wants and needs and can get you the funding needed in as little as 24 hours.

How to sell annuities

When you decide it’s time to raise money for a quick lump sum payment we are here to help atCIYA. Whether it’s money being used to help your family get their first home, starting a new business to become the next Donald Trump, or paying off student debt we are here to help you with the best solution and highest payout possible. You can sell part or all of your future annuity payments.

A Deferred annuity payment is not helpful to our clients who need cash now. While the asset grows and is tax deferred and distributes payments as a periodic payment, lump sum pay out, and or annuitization.

Some of the benefits of keeping your annuity is that your money can continue to grow tax deferred, is almost always AAA rated paper backed by the biggest insurance companies in the world, is guaranteed against losses and hedging your downside on your investment portfolio, income lasts and is reliable.

Why You Should Sell Your Annuity Payments

Some of the big drawbacks far outweigh the benefits and thus why we offer to purchase annuity payments from clients to help them when they need it most. The complexity of these financial instruments come with very expensive fees and are hard for most individuals to understand, you end up giving up the lump sum payment option if you purchase an immediate annuity or decide that you want to annuitize your deferred annuity contract, your cash is tied up and you can’t get to it unless we help you to facilitate a sale, Surrender charges and IRS do cause big penalties if you want to take money out before you turn 60 years of age.

No matter what you decide we are proud to help you to figure out the best route for you to take with your annuities. We can purchase payments in all 50 states as listed below.

• Alabama
• Alaska
• Arizona
• Arkansas
• California
• Colorado
• Connecticut
• Delaware
• Florida
• Georgia
• Hawaii
• Idaho
• Illinois
• Indiana
• Iowa
• Kansas
• Kentucky
• Louisiana
• Maine
• Maryland
• Massachusetts
• Michigan
• Minnesota
• Mississippi
• Missouri
• Montana
• Nebraska
• Nevada
• New Hampshire
• New Jersey
• New Mexico
• New York
• North Carolina
• North Dakota
• Ohio
• Oklahoma
• Oregon
• Pennsylvania
• Rhode Island
• South Carolina
• South Dakota
• Tennessee
• Texas
• Utah
• Vermont
• Virginia
• Washington
• West Virginia
• Wisconsin
• Wyoming

Helpful Articles

John Hancock Life (USA) Structured Settlement Information

Recoveries that are not taxable that come as periodic payments on specific due dates are known as structured settlements. For workers’ compensation claims as defined under IRC Section 104(a)(1)...

How to Avoid Taking a Settlement Loan

So, you have a settlement and you’re getting monthly payments. Although that’s a really good thing financially, there will come a time where your needs will be greater than the...

Peachtree Settlement and J.G. Wentworth: Similar, but Different

One company is known for having ads depicting Vikings sing opera in unusual places.  The other company is known for having a little animated cartoon dog.  Both are major...

Introducing the rlogging package for simple logging in R (beach adventure 2) chitrakatha

beach adventure 2

chitrakatha

Story Download 

The art of logging

In essence, logging is the act of displaying diagnostic and informative messages during the execution of a software program. Log messages can be used to debug software, to inform the user of the progress of long calculations, to document scripts, or to support the auditing of software and the results of complicated calculations.

R has a number of functions which can be used for logging purposes. Most people will be familiar with the cat() command, which concatenates its arguments and prints the result to the console or to a text file. In practice, you will want a little more control over the level of detail of logging messages. Also, you will need to put a cat() statement before each warning() and stop() command to ensure that these events will show up in the logs. Because these two commands and the message()command write to stderr, the messages may get lost when running R scripts in batch mode.

The rlogging package

To provide a slightly more advanced logging facility compared to using only the cat() command, I have created the rlogging package. The idea is to use three existing commands in R’s base package, namely message(), warning(), and stop() to provide three logging levels: ‘INFO’, ‘WARN’, and ‘STOP’ respectively. The package provides a wrapper around these commands (i.e. it ‘masks’ them) to output time-stamped log messages to the console and a text file. For example, the message()command prints a log message if the logging level is set to ‘INFO’:

> message("Hello world!")
[2013-09-20 07:56:07] [INFO] Hello world!
>

Each message starts with the timestamp and the logging level so it’s easy to find (e.g. using grep) different types of log messages in the log file.

Warnings and errors

So you can use the message() command to output informative or debugging messages. Thewarning() command also (immediately) writes a time-stamped message to the console and log file, but it also retains its original behaviour. This means that, by default, warning messages are collected and shown only after the program is finished. These can be recalled with the warnings() function and suppressed by setting options(warn=-1). Note that the latter does not suppress the log messages. See the next section on logging levels which allow you to control this behaviour. Here’s a session which demonstrates the use of warning():

> GetLogLevel()
[1] "INFO"
> warning("Be careful!")
[2013-09-20 08:56:32] [WARN] Be careful!
Warning message:
In warning("Be careful!") : Be careful!
> warnings()
Warning message:
In warning("Be careful!") : Be careful!
> options(warn=-1)
> warning("Be careful!")
[2013-09-20 08:56:56] [WARN] Be careful!
> 

As you can see, the first warning() prints the same message twice: the first one is the time-stamped log message (which is also written to the log file) and the second one is the message written tostderr by the warning() command in R’s base package. The second warning() only prints the time-stamped log message because the printing of warnings has been suppressed.

Like the warning() function, the stop() function also retains its original behaviour, i.e. it prints the error message and stops the execution of the program. The difference is that a log message is also created so there is no need to add an extra cat() statement right before the call to stop(). This is especially useful when running R scripts in batch mode and messages to stderr may be lost. Here again, the same message is printed to the console twice, but this can not be suppressed. Note that the behaviour of the stopifnot() command is not changed by the package, therefore this command does not write a log message.

Logging levels

Each of the three functions is linked to one of three logging levels: ‘INFO’, ‘WARN’, and ‘STOP’. The following table summarizes when messages are printed:

Level   message()   warning()   stop()
INFO    yes         yes         yes
WARN    no          yes         yes
STOP    no          no          yes

Error messages are always printed, but information messages and warnings can be suppressed.

Log file

By default, log messages are appended to a file rlogging.log in the current working directory. You can change the name and location of this file with the SetLogFile(file, folder) command provided by the package:

SetLogFile("mylogfile.txt") # use 'mylogfile.txt' in the current working directory
SetLogFile(folder="~") # save 'mylogfile.txt' in my home directory
SetLogFile(file="mylogfile.txt", folder="~") # same as both commands above

If you do not want to write to a file, then you set the file to NULL as in the following example:

SetLogFile(NULL)

Fork it!

Want additional features? Want to change the look of the log messages? You can find the package source code on Github at https://github.com/mjkallen/rlogging and fork it to make the required changes.

Happy logging.

Hosting static websites on Google Cloud Storage (beach adventure) chithtrakatha

beach adventure 

chithtra kathawa

Story Download

Introduction

A lot of information can be found on the internet about hosting static websites on Amazon S3. Static websites have regained popularity, because they are easy to maintain and will handle a large volume of traffic. To give an example: Obama’s election campaign in 2012 used a static website to handle the enormous number of visitors. S3 already exists for a while therefore it makes sense that quite a few has been written about it. However, Google now offers a very good alternative with Google Cloud Storage. As usual, Google’s documentation is a bit technical and there’s little to no information to be found on the internet about setting up a website on Google’s infrastructure. In this article I show you how you can have your website online with Google Cloud Storage in five steps.

What do you need?

1. a Google account (like what you log into Gmail with),
2. a credit card and
3. a website with at least one index.html file and preferably also a 404.html file.

The website can not use a database or (CGI) scripts written in something like PHP or Perl. Javascript is obviously no problem as that’s located on the client side.

Building blocks of Google Cloud Storage

Before we get started with Google’s Cloud Storage it’s good to introduce some terminology. The building blocks of Cloud Storage are projects, buckets and objects. Every project can hold one or more buckets and in turn every bucket can hold one or more objects. Summarized:

Projects > Buckets > Objects

Objects are generally just files. A collection of files is stored in a bucket and every bucket belongs to a single project. In Google Cloud Storage, projects are mostly used for bookkeeping purposes such as billing. This means that the storage costs of all buckets within a project are grouped. This is handy if you want to, for example, keep the costs of private projects and projects related to your business separated.

Google Cloud storage also offers a few tools for using the service:

• the Google API Console,
• the new Google Cloud Console which used to be the Cloud Storage Manager in the API Console, and
• the command line tool gsutil.

You use the API Console to create new projects and to enable billing. You use the Cloud Console to manage buckets and objects (upload, delete, set access rights, etcetera). These two consoles can be accessed online with a browser. The gsutil is a program which you must install on a local machine. Also, you must grant gsutil access or ‘authenticate’ it and your computer on Google Cloud Storage after installing the program.

Action plan

Do you have a Google account, a credit card and an HTML website? If yes, then follow the five steps below to get your website online.

Step 1: create a new project or select an existing one

Go to the Google API Console, create a new project and give it a name. The name of the project has no implications for the website itself and you can always change it later so don’t spend too much time thinking about a suitable name. While you create the project, activate Google Cloud Storage as a service. Do you already have a project that you want to use? Then go ahead and select it. Just make sure Google Cloud Storage is activated as a service.

Once you have created a new project, you must enable billing for it in the API Console. You can only enable billing with a credit card and billing is required to use Cloud Storage in your project.

Step 2: create a bucket

As soon as you have a project, you can create a new bucket using the Google Cloud Console. By default, buckets are created in a data center in the United states and it’s not possible to select Europe as a location using the Cloud Console. If you want this (and this is highly recommended if your target audience is primarily located in Europe), then you must use gsutil.

Be aware that every bucket must have a unique name within all of Cloud Storage. Two different users can therefore not create buckets with the same name. See Bucket Name Requirements for more requirements that the name of a bucket must adhere to. In order to host a website it is anyway required that the bucket be given the domain name of the website as it’s own name. Here we use the website ‘www.example.com’ as an example so that will also be the name of the bucket. Note that the prefix ‘www.’ is mandatory if that’s how visitors will type in your URL to get to your site!

With the next command we create a bucket with the name ‘www.example.com’ in a data center located in Europe:

gsutil mb -l "EU" gs://www.example.com

Check this with the following command:

gsutil ls -L -b gs://www.example.com

Next to LocationConstraint it should say EU. Refresh the Google Cloud Console and the new bucket should appear. For my website this looks like the following:

An empty bucket with my domain name in my ‘Personal website’ project.

If you’ve accidentally created a bucket via the console and the bucket is located in the US, you can simply delete it and create a new one using gsutil like above.

Step 3: upload your website

Go to the root of your local website (for example the _site folder if you are using Jekyll or the good old public_html folder on an Apache server) and copy all files to the bucket:

gsutil cp -R * gs://www.example.com

The -R flag ensures that all (sub)folders and the files in these folders are copied.

Step 4: configure your bucket to behave like a website

Now that all files are on Cloud Storage the bucket must be configured to act like a web server. Read the documentation on Website configuration for more information.

First we configure the bucket as a website by setting index.html as the main page and 404.html as an error page:

gsutil setwebcfg -m index.html -e 404.html gs://www.example.com

Something that’s missing in the documentation, but which is necessary, is to make all files readable for everyone:

gsutil -m setacl -R -a public-read gs://www.example.com

Go ahead and make the files public by default, otherwise you have to do the above every time you upload new files or change existing files:

gsutil setdefacl public-read gs://www.example.com

By the way, it is also possible to do this while you are copying files with the -a flag:

gsutil cp -R -a public-read * gs://www.example.com

Remember that changed files may not immediately propagate online, because Cloud Storage uses a cache with a default duration of one hour.

Step 5: configure DNS

Change the CNAME record for your domain name to point to c.storage.googleapis.com. You have to do this via the registrar for your domain. Now it should be clear why the name of the bucket must be exactly the same as your domain name: Google connects the DNS record to the correct bucket!

Superfast broadband rollout now one of the fastest in the world ( Shopping fun chithra kathawa )

 Shopping  fun chithra kathawa

Shopping  fun chithra kathawa Download 

Government’s rollout of superfast b has passed more .5 million premises and is reaching 40,000 additional homes and businesses every week.
infographic

The UK government’s ambitious rollout of superfast broadband is gathering pace and its implementation is among the fastest in the world, giving growing numbers of premises access to a fast and reliable internet connection. The rollout has been steadily accelerating since it began in 2012 and has now entered the fastest stage of deployment, with many of the 44 projects across the UK that comprise the scheme ahead of schedule.

26% of all UK connections are now superfast, up from just 6% 2 years ago. Every day more and more people are opting to make the most of all a superfast connection has to offer – be it entire households using multiple devices at the same time with no drop in quality of service, the ability to work from home, staying in touch with friends and relatives using video calls or uploading digital content to websites.

Culture Secretary Sajid Javid said:

    I’m delighted that the project has now reached more than 1.5 million homes and businesses, giving people much faster and reliable connections. We know how important superfast broadband is to everyone, which is exactly why we are investing £1.7 billion in this remarkable project. Our transformation of the UK’s digital landscape is progressing at an incredible rate and delivering a tremendous boost to the nation’s economy as part of the government’s long term economic plan.