text:
Q: Stop subdomain redirects to main domain in wordpress I have a website that is build in WordPress.
I want to build the sub-domains for the site according to the states same as "olx.in" do for different cities.
Everything is setup from the code, server and hosting side, but the problem I am facing is that when I type any sub-domain in the URL like "rj.mysite.com" then I there is somewhere somthing written in the wordpress php file, that is redirecting me to the main domain because I made many changes in the .htaccess file but nothing worked out.
I have tried so much but couldn't found the script that is redirecting the sub-domains to the main domain.
Can anybody please tell me that what should be there in the php code of WordPress that is redirecting my sub-domains to the main site?

A: just found the answer today, hope you've solved it, assuming you have,
what i did for mine was create another wp-config.php file, named it wp-config-sub.php, then in your sub domain, require the wp-config-sub.php file, instead of the wp-config.php file,
    require_once '../wp-config-sub.php';

then go back to your wp-config-sub.php file and comment out these lines
/* Multisite */
//define( 'WP_ALLOW_MULTISITE', true );
//define('MULTISITE', true);
//define('SUBDOMAIN_INSTALL', false);
//define('DOMAIN_CURRENT_SITE', 'yoursiteprimaryurl.com');
//define('PATH_CURRENT_SITE', '/');
//define('SITE_ID_CURRENT_SITE', 1);
//define('BLOG_ID_CURRENT_SITE', 1);

hope this will solve your problem. :)

A: if everything correct in the NS records and the domain redirects
I think you need to login to wordpress and change in the general settings
WordPress Address (URL)
and
Site Address (URL)
to your sub domain or to check your .htaccess file


Password Protect Your Personal Information | ExpressWell, Inc.
ExpressWell offers the option to protect your information with a four-digit passcode. When the passcode feature is enabled, the application information cannot be viewed without first entering the passcode.
We recommend you use this feature to keep your data safe and secure.


text:
Invite Manoj
An introduction to Raag
The Raag is a focal point of Indian classical music, be it the North Indian or the Hindustani style and the South Indian or the Carnatic style. A Raag is a combination of notes or Swaras woven in an artistic manner which transports the listener to an elevated state of music appreciation. As the Sanskrit quotation goes, "Ranjayte Iti Raagah" meaning music that provides soulful entertainment to the listener.
There are 5 basic points of introduction to a Raag. We will take a look at each of these 5 points specifically with respect to Hindustani Music.
1. Thaat
2. Types of Swaras (Shuddha, Komal or Teevra)
3. Vadi and Samvadi
4. Jaati
5. Time to perform
1. Thaat: A Thaat is a source from where a Raag is born. Thaat is a set of 7 Swaras arranged in different combinations pertaini ng to the types of Swaras, e.g. 1 Komal Swara and the resth Shuddha, 2 Komal Swaras and 1 Teevra Swara, etc. There are 10 such combinations or Thaats used in Hindustani music. Each Thaat has a defining main feature associated with it. Following are the names of the 10 Thaats and their main features:
a. Bilaval-all Shuddha Swaras
b. Kalyan-Ma Teevra and the rest Shuddha
c. Khamaj- Ni Komal and the rest Shuddha
d. Kaafi- Ga Ni Komal and the rest Shuddha
e. Asawari- Ga Dha Ni Komal and the rest Shuddha
f. Bhairavi- Re Ga Dha Ni Komal and the rest Shuddha
g. Bhairav- Re Dha Komal and the rest Shuddha
h. Marva- Re Komal Ma Teevra and the rest Shuddha
i. Purvi- Re Dha Komal and Ma Teevra
j. Todi- Re Ga Dha Komal and Ma Teevra
The Raags belonging to these 10 Thaats will have the main feature of their parent Thaat and also have their own inherent features. Thus, the relation between a Thaat and a Raag is like that between a parent and a child.
2. Types of Swaras: As mentioned above, the 10 Thaats are formed based on various combinations of types of Swaras, that is, Shuddha, Komal and Teevra. So if the Thaat or the source of a particular Raag is known, then we can generally determine the types of Swaras present in the Raag, for example, if a Raag is based on Kaafi Thaat, then we can say that it has the 2 Swaras namely, Ga and Ni Komal, as is the main feature of Kaafi Thaat.
3. Vaadi and Samvadi: The Vaadi or the Vaadi Swar is the most important swar of a Raag. This means it is the Swar which is rendered most frequently while elaborating the Raag and which has maximum halting points. Samvadi Swar is the second most important Swar in the Raag behind the Vaadi Swar.
4. Jaati: The Jaati refers to the number of Swaras present in the Raag. For a Raag to be formed, there needs to be a minimum of 5 and maximum of 7 Swaras present in it. Based on this rule, the Jaati is divided in to 3 types, Audav (5 Swaras), Shadav (6 Swaras) and Sampurna (7 Swaras). While taking in to account the Jaati of a Raag, it is necessary to note the number of Swaras present in its Aroha, the ascending scale and the Avroha, the descending scale. For example, if there are 5 Swaras in the Aroha and 7 Swaras in the Avroha of A Raag, the Jaati of the Raag will be termed as Audav Sampurna. The Aroha can have either the same number of Swaras as the Avroha or lesser.
5. Time to perform: Every raag has been assigned a specific time of the day when it can be performed. This is determined depending on the types of Swaras present in the Raag. The 24 hours of the day are divided in to 8 parts of 3 hours each called Praher. Thus, there are 3 such parts for morning, 2 for afternoon and 3 for night.
Copyright © All rights reserved | by Adhoc Infoway

redpajama_set_name: RedPajamaCommonCrawl


Available from APC Hi-Rel, API's low pass EMI filters provides more style, size IL performance and cost alternatives. The filters have a wide range of package size, mounting options and circuit configuration offering maximum design flexibility. The low pass filters has a range of models including Hermetically Sealed Threaded Case Filters, Solder-in Filters, Miniature Solder-in Filters and L Circuit Filters, Large Diameter Solder-in High Temperature Filters and more.
This series of filters features hermetic glass seals and high EMI filtering performance. They are excellent for critical applications that demand high reliability in the toughest environmental conditions and provide broadband high performance EMI filtering from 10 KHz to over 10 GHz.
Solder-in EMI filters are ideal for use in critical areas where space does not allow use of mounting tools or hardware. The solder-in feature also allows installation in unison with other board mounted components.
Miniature Solder-in EMI Filters are ideal for microwave applications that perform well in high impedance circuits where large capacitance values are not practical.
Large Diameter Solder-in High Temperature Filters can withstand 300°C installation temperatures and are ideal for low to medium impedance circuits where large amounts of capacitance to ground can be tolerated.
The Spec Mini-Press 9925 Series Lowpass Filters are knurled filters designed to be pressed into place and create a reliable mechanical bond. This feature makes it an excellent selection for applications where soldering is undesirable. Spec Mini-Press filters perform well in high impedance circuits where large capacitance values are not practical. Suitable plating is available that allows gold bonding to the terminals.
Miniature solder-in filters are hermetically sealed on one end for thru-hole sealing between compartments, allowing it to be soldered into a package, bracket, or bulkhead while maintaining hermetically. The high temperature construction meets military requirements for solderability and resistance to soldering heat and its high-purity gold plating provides excellent compatibility with gold bonding techniques.
This threaded filter is designed without a hex and does not require soldering for installation.
These features make our spanner filter an excellent selection for applications that require many lines to be filtered in close proximity. The easy swap out also allows for flexibility in filter replacement and capacitance substitution. Easy filter substitution also allows for flexibility in filter placement.
These filters are easily mounted in a tapped hole or thru-hole with supplied nut and lock-washer. The rugged case with resin seals at both ends provides excellent environmental protection. Primarily used in filtering signal/data lines and DC power lines.
High current filters are ideal for use in high current 5-volt logic buss, but also can be used for ±48 VDC telephone rack buss, high current switch mode power supplies and DC charging systems. High voltage filters find use in high voltage power supplies and applications requiring U.L. Hi-Pot.
Value-added low pass filters provide flexible solutions to meet your unique design challenges. Our manufacturing process allows you to add connectors, modify terminations or add wire harnesses without adding much cost or drastically increasing lead times.
Allow you to stream-line your bill of materials.
Offer custom application-specific low pass filter assemblies.


I was only part of second objective.
From my perspective, why we died there (Bravo), was coused by being enfilade for the enemies without any good cover. On CNTR it looks like there were 2 full squads (lets say 7/7). If any single one of them see enemy, they do report it to the SL and he gives orders (in this case it probably was GM move) to engage.
Fog or not, we were on terrible spot to be.
On The Second objective I didnt tell the Inf to do anything as by that point I was sick of wrestling with the AI and just let them get on with it. The T-72 was Ignored as you guys assumed it was unmanned since it wasnt moving. In reality it was fully manned and even shot one of your members at one point before bugging out and freezing, where upon I had to delete and replace it. Any Inf engagements were all AI managing themselves on the second Objective.


New Orleans is food. One can spend a happy lifetime exploring the city and its cuisine. These two books offer a quick but thorough introduction.
This is the 1901 edition of the Picayune newspaper's book which catalogued, preserved, and continues to popularize traditional Creole cooking. As a result of the Picayune 's visionary effort, Louisiana's cooking is today not only America's most distinctive and widely-acclaimed cuisine, but it also arguably the most important single factor in the preservation and celebration of New Orleans' culture. See further information and ordering instructions.
This recent book by Patricia Mitchell includes an information-packed summary of Louisiana food from the early settlement to today. See further information and ordering instructions.
Copyright © 2005–2014 Patricia B. Mitchell.


Pastoral Care is about caring for the person whilst they are in Hospital on a 'Human' level. Helping them through their worries and fears . This is often done by listening to what they have to say and then, when appropriate, helping them to find answers to any problems they might have.
It is not intended that Chaplaincy should (or could!) meet all the pastoral needs of those in hospital. Good pastoral care is something we all do and is part of everyone's work, whether it is answering someone's question in the corridor or delivering difficult news on the Ward.


Lyrical folk/rock song that tells a story of a couple and how they fell in love!
compass, you know they found their way!
A journey home, in a uhaul van - with a dog! Off to see her man!!
The funding for this project was made possible solely thru the generous contributions of George Guinness, Rutland, VT - He gave the song to the happy couple as a wedding present on their wedding day on July 15th 2017.


text:
package com.markwal.mcmod.letsmodreboot.item;

import com.markwal.mcmod.letsmodreboot.creativetab.CreativeTabLMRB;

/**
 * Created by mark on 7/31/14.
 */
public class ItemMapleLeaf extends ItemLMRB {

    public ItemMapleLeaf() {
        super();
        this.setUnlocalizedName("mapleLeaf");
    }
}

redpajama_set_name: RedPajamaGithub


Dawna started her real estate career with RE/MAX nova more than 10 years ago. As a member of RE/MAX International Platinum Award Club, Dawna is a committed and passionate real estate professional who prides herself on putting her clients' satisfaction above all else. Her determination and attention to detail ensure her clients receive first-class service with utmost integrity. Her 80% referral rate clearly attests to her clients' trust in her and the service she provides.
"I hold my key values in the highest regard and for me, these values—honesty, integrity, trust, knowledge and dedication—are paramount to representing my clients. I strongly believe that by maintaining these values, I will achieve the most important goal: your satisfaction, and the fulfillment of your hopes and dreams. You can be confident that I will always make the extra effort and deliver the best possible experience with buying or selling your home."
It gives me great pleasure to share my experience with Dawna Feser in the listing and sale of my home. Although I have bought and sold a number of houses, Dawna demonstrated a level of excellence superior to any of my previous experiences. From our first meeting and throughout the entire process she proved herself to be professional, friendly, knowledgeable and very resourceful. Dawna patiently guided me through each step and kept me well informed throughout. When appropriate she offered sound advice, suggesting options and the possible effects of choosing one direction or another. Dawna showed herself to be incredibly resourceful not only as a realtor but as a problem solver. When I was struggling to find competent trades people for some necessary repairs, she stepped up to the plate. Not only did she help me find good tradesmen, she facilitated getting them to do the job in a timely fashion, when otherwise my small job would have been at the bottom of the priority list. Unbidden, she even went so far as to find transportation for bulky items required for the job. I am happy to give Dawna my highest recommendation to anyone requiring the services of a realtor. Her competence, integrity, humility and grace set her apart.
Dawna has been extremely helpful in the entire house purchasing process. In the past two years she helped find my current house and a rental property. She's helped negotiate the right price based on market research and was always available to chat about any concerns I had.
I met Dawna a couple of years before we sold our home. We had a great discussion about what to look for in purchasing a rental property. Although we decided for the time being, due to unforeseen circumstances, we were not up for becoming landlords, I thought that Dawna was able to provide me with really sound advice and information. Two years later when it was time to sell our own home, I contacted Dawna right away. She was very thorough in our home assessment and made sure we were well versed on the seller's agreement. She took the time to accurately measure our home inside and out, took great photos, and highlighted the best features of our home on MLS. Our home sold very quickly and we even ended up with two offers! Dawna was easily accessible whenever we had any concerns and always showed up on time, as scheduled. I would recommend Dawna to anyone looking for a realtor. She kept us calm and well informed at all times, despite our anxiety over our military posting to Ottawa. Thanks Dawna!
Dawna is fantastic! She is knowledgeable in all areas of Real Estate and takes a personal approach to her clients. We first met Dawna in the spring of 2009 and her patience, guidance, and support helped us find that perfect house we call home! Her dedication and attentiveness to her clients' needs are exceptional and she will work with you to ensure success. She has made astounding progress in these past few years and is well versed in military relocations. Her fresh, family focused values are evident in her daily life and she finds balance without sacrificing work or family. I have no hesitation in recommending Dawna to any seller or buyer and feel 100% confident you will feel the same once you meet and work with her!
As first-time home buyers, we really had no idea what to expect from the whole process. Working with Dawna took the stress out of the equation for us. She was always available to answer our questions, was flexible to our schedule in booking viewings, and, as cliché as it might sound, she really was with us every step of the way. We are beyond happy with our first home- buying experience, and are pleased to pass Dawna's name on to friends who are looking for a dependable, smart and efficient agent.
We were referred to Dawna from a close friend who could not say enough positive things about her. Our first meeting with Dawna was very enjoyable and she left us feeling very comfortable and confident in our choice of an agent. As first time home buyers we had a lot of questions and quite a bit of uncertainty in terms of whether we wanted to buy or build. Dawna was extremely patient, always willing to take the time to explain every step of the process, what steps should be taken and why. Dawna has the ability to make you feel as though you are her only client and that she always has time to talk with you and perform research for you. We were both extremely impressed by how promptly Dawna replied to any voicemail messages we left for her and e-mails we sent to her. We ended up building a home and Dawna stood by us and assisted us in every step of the process, from making our offer to picking out our colours. We recommend Dawna very highly and will be using her as our agent for any sales or purchases we may make in the future. Dawna has all the qualities that anyone could look for in an agent. She is extremely friendly, knowledgeable, efficient and she has the ability to understand exactly what you are looking for and to find it for you. If you are looking for an enjoyable agent to work with, Dawna is a great choice. Big thanks to you Dawna for all your hard work and patience with us!
My fiancé and I first used Dawna as our agent to purchase our first home when we found out we were expecting our first baby (and have used her three times since). We were in a hurry to find a home to settle into and Dawna was there with us every step of the way. We looked at several homes and even went back to look at a few of the homes with Dawna who seemed to be just as happy as we were to be looking at our potentially new home (again). She always made us feel like we had all of the time in the world to look at the homes and ask the many questions I always had. She also was great with her communication about new listings she thought might work for us. Dawna was always very helpful in answering questions, giving direction, and being there for us beyond the closing of our home. She is very personable and I recommend her services to anyone looking for a friendly, caring, and competent agent who always goes the extra mile.


text:
Q: How to add gradient to UIView as an extension I am trying to add some gradient to a view in Xcode and for simplicity I tried to add my method as an extension to UIView:
extension UIView {
    func applyGradient() {
        let gradient = CAGradientLayer()
        gradient.colors = [UIColor(hex: "F5FF8C").cgColor,
                           UIColor(hex: "F1F99D").cgColor,
                           UIColor(hex: "FDFFE0").cgColor]
        gradient.locations = [0.0, 0.5, 1.0]

        self.layer.insertSublayer(gradient, at: 0)
    }
}

But apparently this doesn't work when I call it in my viewDidLoad:
self.myView.applyGradient()

Can someone point to me what am I doing wrong ?

A: In the question, you haven't set the frame at all. In the comment, your frame was not set correctly. This is the code that should work properly:
extension UIView {
    func applyGradient() {
        let gradient = CAGradientLayer()
        gradient.colors = [UIColor.red.cgColor,
                           UIColor.green.cgColor,
                           UIColor.black.cgColor]   // your colors go here
        gradient.locations = [0.0, 0.5, 1.0]
        gradient.frame = self.bounds
        self.layer.insertSublayer(gradient, at: 0)
    }
}

With your code:

With the modified code:

Explanation
gradient.frame.size = self.frame.size doesn't work, while gradient.frame = self.bounds does, because the frame attribute contains both the location and the size of the view, and even if you set the gradient's frame size, you do not specify the location of the gradient... So the gradient is never actually added to the view. By setting the frame attribute directly to the bounds of the view, you also add the location of the gradient in the view.

redpajama_set_name: RedPajamaStackExchange


MySQL is the world's second most used open source database. Several paid editions that use MySQL and increase functionality include Joomla and WordPress. Paid WordPress themes start at $75 per year.
LDAP is an application protocol made for organizing a set of records, such as a corporate email directory. LDAP includes closed and open source software programs for client software from cross platform to Microsoft Windows.
Python is an interactive programming language. It's open source and companies like Yahoo Maps and Google spider and search engine are written in Python.
With its automatic memory management and dynamic system, Ruby is an open source web application. Companies such as Amazon, BBC and NASA use Ruby.
Compiere is an enterprise resource planning and customer relationship management system. It is a good solution for small and medium-size businesses. Its framework is designed with the intention to follow changes as a business evolves.
Open Bravo is used for small- and medium-size companies. There are open and closed source versions. The paid-for version offers functionality including updates and upgrades and administrative tools.
BlackBerry Enterprise Service 10 takes away the concerns about security normally associated with BYOD and makes it easy to deploy, manage, secure and control devices — BlackBerry, Android, and iOS. Although not an open source solution, there is a 60-day free trial where businesses can test the mobility management for employee's devices.
Microsoft Office is the standard in most office environments, but there are other options that work just as well if not better and they are less expensive or free. Google Apps and LibreOffice are effective business productivity suites and are significantly cheaper.
LibreOffice is a free and open source office suite designed to be compatible with Microsoft Office. It has a word processor, spreadsheet program, presentation program, vector graphics editor, mathematical application and database management program.
Google Apps makes collaboration easier. Most small businesses don't benefit from bulk-purchase prices offered by Microsoft. Most people only use about 10 percent to 15 percent of the features in Microsoft Office Suite, so to use the open source software saves the cost of the proprietary solution.
GNU Image Manipulation Program is an open source software that offers many of these advantages at little to no cost. Small businesses should research whether these cost-effective options will work for its firm, suggests Business Bee.
Many small businesses are migrating to cloud services for tasks like data storage. Migrating user storage from user's pictures to a centralized location like the cloud reduces strain on client machines; there is less writing to drives and more over the network. It is also easier to backup all end-user data from a single location.
Dropbox allows users to share documents and photos across multiple devices. The free storage capacity is 2 GB, but for businesses that want as much storage as needed can pay $795 a year for five users and an additional $125 per year per user.
Microsoft SkyDrive allows people to replicate files on multiple systems and is best for small businesses. It's free up to 7 GB, while adding 200 GB is $100 more per year.
Communicating with employees, clients and vendors in other cities or countries can be expensive for small businesses. Web-based teleconferencing allows businesses to make video and voice connections without the need for special equipment or huge phone bills. Web-based teleconferencing, such as AdobeConnect, can also help companies manage their networks of mobile and social media connections.
Most businesses have migrated to web-based tools. On a Linux box, there is no need to worry about virus infections, corrupt registry entries, or installation of malware-infested applications. Linux machines can still use closed source software, such as Microsoft Office.
Still paying for Microsoft Office?


text:
import run from 'ember-metal/run_loop';
import jQuery from 'ember-views/system/jquery';
import EmberView from 'ember-views/views/view';
import { Binding } from 'ember-metal/binding';
import EmberObject from 'ember-runtime/system/object';
import { computed } from 'ember-metal/computed';
import ContainerView from 'ember-views/views/container_view';
import compile from 'ember-template-compiler/system/compile';
import { runAppend, runDestroy } from "ember-runtime/tests/utils";
import { registerHelper } from "ember-htmlbars/helpers";

import { set } from 'ember-metal/property_set';

var view, MyApp, originalLookup, lookup;

var trim = jQuery.trim;

QUnit.module('ember-htmlbars: binding integration', {
  setup() {
    originalLookup = Ember.lookup;
    Ember.lookup = lookup = {};

    MyApp = lookup.MyApp = EmberObject.create({});
  },

  teardown() {
    Ember.lookup = originalLookup;

    runDestroy(view);
    view = null;

    MyApp = null;
  }
});

QUnit.test('should call a registered helper for mustache without parameters', function() {
  registerHelper('foobar', function() {
    return 'foobar';
  });

  view = EmberView.create({
    template: compile('{{foobar}}')
  });

  runAppend(view);

  ok(view.$().text() === 'foobar', 'Regular helper was invoked correctly');
});

QUnit.test('should bind to the property if no registered helper found for a mustache without parameters', function() {
  view = EmberView.createWithMixins({
    template: compile('{{view.foobarProperty}}'),
    foobarProperty: computed(function() {
      return 'foobarProperty';
    })
  });

  runAppend(view);

  ok(view.$().text() === 'foobarProperty', 'Property was bound to correctly');
});

QUnit.test("should be able to update when bound property updates", function() {
  MyApp.set('controller', EmberObject.create({ name: 'first' }));

  var View = EmberView.extend({
    template: compile('<i>{{view.value.name}}, {{view.computed}}</i>'),
    valueBinding: 'MyApp.controller',
    computed: computed(function() {
      return this.get('value.name') + ' - computed';
    }).property('value')
  });

  run(function() {
    view = View.create();
  });

  runAppend(view);

  run(function() {
    MyApp.set('controller', EmberObject.create({
      name: 'second'
    }));
  });

  equal(view.get('computed'), "second - computed", "view computed properties correctly update");
  equal(view.$('i').text(), 'second, second - computed', "view rerenders when bound properties change");
});

QUnit.test('should cleanup bound properties on rerender', function() {
  view = EmberView.create({
    controller: EmberObject.create({ name: 'wycats' }),
    template: compile('{{name}}')
  });

  runAppend(view);

  equal(view.$().text(), 'wycats', 'rendered binding');

  run(view, 'rerender');

  equal(view.$().text(), 'wycats', 'rendered binding');
});

QUnit.test("should update bound values after view's parent is removed and then re-appended", function() {
  expectDeprecation("Setting `childViews` on a Container is deprecated.");

  var controller = EmberObject.create();

  var parentView = ContainerView.create({
    childViews: ['testView'],

    controller: controller,

    testView: EmberView.create({
      template: compile("{{#if showStuff}}{{boundValue}}{{else}}Not true.{{/if}}")
    })
  });

  controller.setProperties({
    showStuff: true,
    boundValue: "foo"
  });

  runAppend(parentView);
  view = parentView.get('testView');

  equal(trim(view.$().text()), "foo");
  run(function() {
    set(controller, 'showStuff', false);
  });
  equal(trim(view.$().text()), "Not true.");

  run(function() {
    set(controller, 'showStuff', true);
  });
  equal(trim(view.$().text()), "foo");

  run(function() {
    parentView.remove();
    set(controller, 'showStuff', false);
  });
  run(function() {
    set(controller, 'showStuff', true);
  });
  runAppend(parentView);

  run(function() {
    set(controller, 'boundValue', "bar");
  });
  equal(trim(view.$().text()), "bar");

  runDestroy(parentView);
});

QUnit.test('should accept bindings as a string or an Ember.Binding', function() {
  var ViewWithBindings = EmberView.extend({
    oneWayBindingTestBinding: Binding.oneWay('context.direction'),
    twoWayBindingTestBinding: Binding.from('context.direction'),
    stringBindingTestBinding: 'context.direction',
    template: compile(
      "one way: {{view.oneWayBindingTest}}, " +
      "two way: {{view.twoWayBindingTest}}, " +
      "string: {{view.stringBindingTest}}"
    )
  });

  view = EmberView.create({
    viewWithBindingsClass: ViewWithBindings,
    context: EmberObject.create({
      direction: "down"
    }),
    template: compile("{{view view.viewWithBindingsClass}}")
  });

  runAppend(view);

  equal(trim(view.$().text()), "one way: down, two way: down, string: down");
});


text:
KBS Reportedly Cancels Its Production For "School 2020" After The Messy Casting Controversy + KBS Issues A Response
The future of "School 2020" is uncertain!
On April 10, a Korean news outlet reported that after various discussions, KBS has decided not to continue with the next installment of the hugely popular School series.
Last month, the controversy was sparked involving Ahn Seo Hyun, the actress was initially considered for the lead female role but all of a sudden, news of her withdrawal was posted and it caused a lot of confusion among fans who had been anticipating her appearance on the drama. Instead, it was reported that Kim Sae Ron was instead being considered for the leading role.
Ahn Seo Hyun had already participated in a script read-through for the drama and also posted about the drama on social media, including a photo of herself with lead actor Kim Yo Han and director Han Sang Woo.
This was followed by statements from Ahn Seo Hyun and KBS production team, each one contradicting the other. KBS claims Ahn Seo Hyun's father made unreasonable demands that became unbearable for the production team, while Ahn Seo Hyun's father says they were stabbed in the back and that KBS had conducted under-the-table searches for another actress while his daughter had already participated in the script reading. The father also claims they didn't sign a contract because the production kept delaying it.
The issue garnered negative feedback towards KBS, Ahn Seo Hyun revealed that she had been personally preparing for the role for almost a year and has made several social media posts talking about 'being betrayed by the adults.'
A couple of days ago, it was also reported that WJSN Eunseo was offered the second leading role for the drama. While KBS didn't confirm or deny the news, the idol's agency stated that she was looking over the offer with a 'favorable outlook.' If she accepts it'll mark her TV screen debut, she's only been in MVs and web dramas thus far.
Following this report, KBS told DongA.com that they're currently discussing the matter and that nothing has been decided yet.
Source: (A)
Tags: Ahn Seo Hyun, Kim Sae Ron, School 2020
BTS Becomes The First EVER Korean Act To Sell Over 20 Million Albums On Gaon Charts
(G)I-DLE Surpasses LOONA And BLACKPINK To Break This Record On iTunes + More Impressive Album Sale Records
1 thought on "KBS Reportedly Cancels Its Production For "School 2020" After The Messy Casting Controversy + KBS Issues A Response"
Fanny Dwi Sosiawaty
Oh, Yohan-nie TT
Why 2 things are not going well for him. I really hope everything could be smoothly well


text:
All change for TfL's 384 and 112
Readers may recall my ride on route 404 earlier this month highlighting TfL's penchant for circuitous bus routes wandering around the back streets of London's suburbs making sure everyone lives within 400 metres of a bus stop.
But up in Barnet, it's all change for circuitous route 384. From today it's had the hair straighteners and extension treatment and almost all its curly bits have been removed. It now runs pretty much direct between Cockfosters and Barnet as well as gaining a significant route extension on to Edgware.
Overnight, the 384 has gone from a Barnet back street wanderer to a North London orbital titan.
Introduced in 1990, the 384 brought a bus route to many previously unserved residential roads between Cockfosters and Barnet. More twiddles were added over the years as well as an extension in Barnet to terminate at Quinta Drive in place of another similar twiddly route.
London's northernmost bus garage at Potters Bar has been home to the route since its inception (originally operated by the former London Northern company, which sold to MTL in 1994, then sold again to Metroline in 1998) and until yesterday six buses were deployed providing a twenty minute frequency.
So what's with the change from today? TfL carried out one of its regular reviews of the bus network serving Barnet back in 2017. They found "route 384 is very circuitous serving many local side roads" which shouldn't have come as too much of a surprise as that's been the route's raison d'être for the past 30 years.
The review continued "the route is not well used, especially where it is most circuitous and parked cars restrict the availability of bus stops. The frequency of the route was reduced from 4 buses per hour to 3 buses per hour in recent years but usage figures still do not justify the frequency of the service".
Another key finding of the review was "no TfL bus route runs directly between Barnet Town Centre/Barnet Hospital and Mill Hill/Edgware". Route 107 does provide a link from Barnet to Edgware (and has done since 1954) but runs via Borehamwood and Elstree taking about 40 minutes for what could be a journey of not much more than 15 minutes direct via Mill Hill.
I noted the specific words "no TfL bus route runs directly between Barnet…". There is a direct route but it's a commercial venture run by the Hatfield based unō bus company, so not regarded as a proper route by TfL.
Unō's Comet branded route 614 provides an hourly service starting at Queensbury (which by a quirk of coincidence was where the 107 also used to start before being cut back to Edgware in 1993) and runs via Burnt Oak, Edgware, Apex Corner and Stirling Corner then direct to Barnet via Arkley before continuing on to Hatfield. Other than a slightly different routing in Edgware and a twiddly bit via Barnet's Quinta Drive the newly extended 384 duplicates the 614.
In fact the 384 now follows the same roads served by route 292 from Stirling Corner to Edgware and that's why TfL has reduced the 292's frequency from 4 buses per hour to 3 buses per hour, now the 384 is also on the scene. This has reduced the frequency for passengers travelling on the 292 north of Stirling Corner to and from Borehamwood but TfL don't mind that as that section of route is 'over the border' in Hertfordshire so that's that Council's problem, not TfL's.
What should concern TfL is the coordination of timetables between the 292 and 384 now that both run at a 3 bus per hour frequency. How sensible it would be to ensure departures were as evenly spaced as possible to create a 10 minute frequency between Stirling Corner and Edgware. Sadly it was not to be as daytime journeys are timetabled within 2 minutes of each other in one direction (then an 18 minute gap) and 3 minutes apart (followed by 17 minutes) in the other. Not very integrated.
Back to the other end of route 384 and those withdrawn twiddly bits between Cockfosters and New Barnet. TfL consulted on the proposed route straightening and withdrawal from most of the side roads currently served – all except the loop around Westbrook Crescent marked in blue on the map below which continues – between September and November 2018.
Yes, I know that's two years ago, but this is TfL and timescales on route developments take time to mull over in a "world class transport system" such as London's.
Westbrook Crescent is the only twiddly bit left on the 384.
1,378 responses were received with 54% opposed or strongly opposed to the proposals and 32% supporting or strongly supporting them. In its report on the consultation, and the necessary 'Equality Impact Assessment' (EqIA) it's interesting to see how TfL justify implementing the proposals despite the majority of respondents being opposed to them.
Here's the "Rationale" summarised by TfL:
"Journey times between Cockfosters and New Barnet and between New Barnet and Chipping Barnet are longer than they need to be due to the circuitous routeing of the 384. Making the service more direct between these locations will lead to increased usage. Extending the service to Edgware will create new direct orbital bus links across North London, improving travel options. In particular it will create a new direct link between Edgware and Barnet Hospital."
It's fascinating to see TfL justifying the withdrawal of circuitous routes in favour of increased usage generated from more direct bus routes. A logic they've used completely the other way round when it also suits their purpose. The 400 metre guideline seems to have conveniently been dropped in this case and TfL admits "a number of passengers will have a longer walk to access the bus network". In fact the EqIA explains around half the route's passengers will face a longer walk – in some cases 600 metres or more – and gives details of where these people live and currently use the bus.
On the other hand "50% of people who currently travel on the 384 will still be able to board or alight at exactly the same place as they currently do. Some of their journeys will be quicker".
I took a ride out on the 384 earlier this month to see what the withdrawal will mean in practice.
Many of the buses I saw had very few passengers travelling, so I can see "usuage figures still do not justify the frequency of the service" although it didn't seem much different from many other back street routes in London's suburbs.
One capacity constrained bus (14 only allowed on board) had a fair load for these Covid times as we left New Barnet station heading towards Barnet (see above) and a few of those on board got off in the Lyonsdown Road and Gloucester Road area which from today is no longer served.
The junction of Lyonsdown Road and Gloucester Road now no longer served.
I also alighted here and walked back to New Barnet station. Being fit and active, it didn't take me long, and personally if I was catching a train I'd be happier walking anyway rather than wait for a twenty minute frequency bus. It's quite a pleasant walk too with some very mature trees to appreciate along the way.
Tree lined York Road leading to and from New Barnet Station is no longer served.
But if I was less agile or returning laden with shopping from the local shops in New Barnet, it would be a completely different matter. I'd very much welcome a bus ride home and which is no longer possible.
I then wandered over to the large section of route around Castlewood Road and Northfield Road which has also become bus-less from today and, partly because it was during the very hot spell of weather, found the walk enjoyable. But again, it would be a different matter on a wet or cold day, and Northfield Road, in particular, has a long steady incline which is quite tiring to walk up. I wouldn't like to do it if I was less agile. You're a considerable distance from where the 384 now stops.
A 384 climbs Northfield Drive now no longer served.
On the other hand, I've travelled from Cockfosters to Barnet on this route in the past and have to agree it is very circuitous and you do wonder if you're ever going to reach Barnet especially when the bus turns into Crescent Road and is almost pointing back in the direction you've just come from only to then hit East Barnet Road and head back on track again.
The Crescent Road loop is on the left hand side of the map above.
Crescent Road heading east/south (as used by the 384 heading west/north – until yesterday).
There could well be a case for a more direct orbital bus route between Cockfosters, Barnet and Edgware but I wonder if TfL embraced the 614 a bit more and promoted it as part of its network (albiet Oyster is not valid, but contactless is) then that may satisfy the demand at least between Edgware as far as Barnet.
I took a ride on the new look 384 this morning to see how it compares. Whereas the journey between Cockfosters and Barnet Church used to take 27 minutes, the new straightened out route (albeit still including that ride around Westbrook Crescent) now does it in 20 and that was generous as we had to wait time at a number of stops along the way; probably a good five minutes of idling.
After Barnet Church the 384 does a loop to serve The Spires shopping area taking 8 minutes to reach Barnet Hospital whereas routes 263 and 307 which run direct take just 3 minutes. The 384 then diverts around Quinta Drive as it used to do so the effect of all that is a journey time to Edgware from Barnet Church of 33 minutes pretty much double the time taken by unō's 614 which really is direct.
And I see that as the problem – the 384 has had a bit of straightening out and lost half its passengers but it's still not providing an attractive journey time to entice a new band of orbital travellers on board. It's now neither one thing nor the other.
Today was also a chaotic start to the new extension in that the direct route between Barnet and Stirling Corner via Arkley was still closed for the third day due to emergency road works for a burst water main.
This caused added confusion when we arrived in Barnet and dropped off the three passengers we'd gained since Cockfosters before The Spires shops and our driver had to patiently explain to passengers waiting to board there were no buses to Quinta Drive as he was heading off on a long diversion via South Mimms to Edgware where the route had never gone before.
You can forgive passengers for being frustrated and annoyed with a complete lack of information at bus stops not only about the withdrawal of the complete service to their area, but as always with TfL, nothing about the new extension to Edgware either.
There is a 'status alert' on TfL's website if you knew where to click to find it, but there again the website in another place tells you buses are still terminating at Quinta Drive with no reference to the exciting extension to Edgware.
No wonder people are confused.
In the event the diversion up the A1081 and back down the A1 via the M25 junction at South Mimms was quicker than taking the official route via Quinta Drive and Arkley – now there's a thing – so we spent another five minutes or more losing time at bus stops to be sure we didn't arrive early into Edgware bus station and Metroline didn't lose its Quality Incentive Bonus.
I'd noticed TfL's bus stop flag contractor had been out updating all the tiles by adding 384 where needed (although they missed the one in Station Road)….
…. but inevitably the timetable case department hadn't been out …
….and there was a complete dearth of bus stop information about the new 384 at newly served bus stops as well as incorrect information at bus stops previously served.
Sadly even more inevitable was no mention of the new service at all at Edgware bus station.
You had to assume it left from stand F as that's where the 292 departs.
Suffice to say my only companion on my two journeys between Barnet and Edgware was a fellow 'first day bus rider'. No 'real' passengers to be seen. Unless you're a devoted follower of the intricacies and small print of TfL's website you'd have no knowledge of this significant route development in north London.
Time will tell if the numbers generated on the new look, partly straightened out, 384 grow to offset those left stranded in the back streets. I have my doubts. Interestingly the three buses TfL have saved from the cut back on the 292 have more than paid for the extra two buses added to the 384 to achieve its extension.
With the 384's new 'direct route' status, it'll also be interesting to see if the mini style bus stops which have been a familiar feature of the 'hail and ride' section of route grow taller and sprout a flag in the Westbrook Crescent area – and show a timetable for both directions too, which is what it should have been doing when I spotted that deficiency earlier this month and was still like it this morning.
And there's a shelter going spare in now unserved Castlewood Road.
Anyone want an unused bus shelter? This one in Castlewood Road is going spare.
Meanwhile also from today, over in nearby North Finchley, another TfL route extension arrived at that suburb's infamous Tally Ho terminus – route 112 from Ealing Broadway.
For 35 years between 1935 and 1970 route 112 plied its way along the western arc of the North Circular Road linking Ealing with Palmers Green. A pioneering orbital route from west to north London.
Traffic congestion got the better of it in 1970 and the 112 was cut back from the west to turn at Manor Cottage Tavern, Finchley (with the eastern end to Palmers Green becoming a separate route 212). After junction improvements and widening to the North Circular by 1978 the 112 was re-extended back to Palmers Green again but delays hadn't gone away and in 1994 it was cut back again this time to Brent Cross shopping centre where it's terminated until today when North Finchley beckoned as a better place to head for.
As always this extension which sees buses continue along the North Circular via Henlys Corner to Finchley High Road before heading north to North Finchley was consulted on by TfL as the opportunity has also been taken to withdraw the one return journey a day on school bus route 611 which covered the same ground as the newly extended 112. Planners reckoned all the kids could travel on a newly extended scheduled bus on the 112 instead. Mind you, this was before Covid, so possibly the 611 will win a last minute reprieve as I doubt the single decks on the 112 will cope especially as TfL are designating certain journeys for school children only.
231 responses were received to the consultation in September and October last year with most concerned about the withdrawal of the bespoke 611, not surprising as over half the respondents were travelling to and from school. On route 112 respondents were concerned the extended route would make it less reliable but TfL reckon the recovery time built in at the termini will be enough to counteract that.
It's very encouraging to read that "over the last ten years there has been substantial growth on bus route 112" with a 50% increase since 2015. "Development plans at Stonebridge Park, Harrow Road and Brent Cross mean passenger numbers are expected to increase further."
It's not entirely clear why the 112 is being extended, there's no evidence of need provided in TfL's documentation, but it's a welcome addition to the bus network in north London and provides a new link from North Finchley and Finchley High Road to Brent Cross.
At the other end of route 112 another change from today sees buses take a short cut from the North Circular to its Ealing Broadway terminus by using Madeley Road instead of Uxbridge Road to improve timekeeping as well as giving residents of this road a bus for the first time with new bus stops placed right in the middle.
This proposal has been on the stocks for even longer than the 384, being consulted on back in October and November 2016 – you have to have patience when working in network route planning in TfL. It seems there was quite a bit of work needed on Madeley Road to make it suitable for buses.
The London Borough of Ealing had to resurface the road and install bus stop build outs for the new stops while TfL had to cut back the central island for a 'buses only' right hand turn from the North Circular Road into Madeley Road as the junction had previously prohibited right turns in the interests of keeping traffic flowing.
Works of this kind don't happen overnight so I guess four years is good going.
I arrived in the gloom of North Finchley's bus station around lunch time today as I made a calculated guess that's where the 112 would depart from.
Obviously there was absolutely nothing in the bus station to tell me that's where it departs….
…. not even a service update added to the white board to let us know about this fantastic new route opportunity….
….. and TfL's online information denied all knowledge of the extension still advising Brent Cross was the limit.
Incredibly two passengers boarded with me seemingly aware of this new link to Brent Cross where they were heading. That really surprised me; they must have been bus enthusiasts disguised as shoppers.
We had a free flowing journey down Finchley High Road before turning right on to the North Circular and it wasn't long before the brake lights ahead told us we were approaching slow moving traffic towards Henleys Corner which Google confirmed.
It seems timetable planners guessed there'd be delays as despite the slow progress we arrived at Henleys Corner on schedule and our driver enticed two waiting passengers for Brent Cross on board rather than wait for their more normal 232.
If they'd looked at the bus stop flag they'd have noticed 112 had been added, but obviously nothing in the timetable case would have helped.
We made a driver changeover at the bus stop just before Brent Cross bus station which is a frustrating way of adding three minutes to the journey just as you're within sight of your destination.
I left the bus at a busy Brent Cross to take a look at how TfL are promoting this new route extension; ok I'm joking; as if TfL would even consider promoting a route extension.
Instead they leave it to a bus enthusiast who manages to secrete a home made information poster into a poster frame and cover up a wildly out of date area bus map … remember those halcyon days?
Suffice to say the information booth was closed, the timetable cases and spider maps gave no indication a 112 now ventured eastwards beyond Brent Cross, but a 112 tile has appeared on the bus stop flag for stop C if your psychic to know that will be towards North Finchley as opposed to Ealing Broadway.
I caught the next 112 towards Ealing which turned out to be a late running and busy bus. We got up to 23 on board despite the Covid maximum of 14 and even then the driver left five passengers behind at one stop who were not happy at all having already had a long wait.
TfL can reassure passengers the route extension won't increase unreliability because of adequate recovery time at the termini but the problem is the running time isn't adequate for the regular delays along the North Circular.
We hit more slow moving traffic in Neasden and on the approach to Hanger Lane.
The new diversion via Madeley Road saved a valuable few minutes queuing time at the junction with Uxbridge Road but the new right turn is quite a tricky manoeuvre ….
… as buses share the slightly enlarged space for turning with northbound traffic turning right into Inglis Road opposite Madeley Road.
The left hand turn out of Madeley Road is quite tight too.
And it looked like Madeley Road is used as a cut through by locals to get to the North Circular, as it certainly looked quicker than using Uxbridge Road even with a queue at the junction with the North Circular.
The three new bus stops with their build outs….
…..and smart new poles and flags in Madeley Road looked prestine and sported a 112 tile ….
…. but obviously were devoid of timetable information….
…. as was the new departure point – stop D – at Ealing Broadway for passengers wanting to board a 112.
While I was there a mystified passenger went over to a 112 enjoying its stand time round the corner by the Green to enquire of the driver where she should wait. He was very patient in explaining the new arrangements.
I checked out the spider map on stop D where the new 112 departs …
…. and it told me to head to stop F, where it used to depart for Neasden.
But to end the day on a bright spot. I took a look at the timetable case on stop F – where the 112 used to depart up until yesterday and finally found an explanation of the changes being made today.
The only one I saw anywhere for both the new look 112 or 384.
The newly extended 112, with its ten minute frequency and additional 20 minutes running time (27 at peak times) in each direction has meant Metroline have needed to add five more buses on to the 112's vehicle requirment taking it from 11 to 16. That's quite a hefty investment for TfL to fund and will take a considerable generation of additional passengers.
All the more so as TfL acknowledge growth on the route is expected in the Brent and Stonebridge Park areas. It does seem odd therefore to add five buses for a new extension eastwards. I'd have thought using that investment to increase the frequency on the former route section would have made more sense rathe than a speculative extension.
Now it's happened though I would suggest a promotional campaign and some route branding are definitely needed to raise the 112's profile. Perhaps something along the lines uno introduced on route 383 last year and which I spotted this morning.
Moddest by provincial standards, but at least it's doing something to raise the profile of where buses go in London. Even more pertinent if they're being extended like the 112 and 384.
Brighton to Croydon and back. By bus.
Buses are back to the Hayling Ferry
13 thoughts on "All change for TfL's 384 and 112"
Alan Smith says:
TfL: Every Journey Matters (Unless you use Uno)
It's one of things that I don't understand about the London permit system. Uno pay good money to access TfL land, you'd think TfL would "promote"/push the Uno service as well. If someone operated a service from Blackburn in to Manchester, I am pretty sure TfGM would mention it. Hey ho, I suppose that's a quirk of the world class transport system…
Andrew Saffrey says:
Great post again Roger.
The 112 wasn't cut back in 1970 as I was born in 1981 and remember it still running to Palmers Green. It might have been 1991 or 1992, when the Barnet and Enfield local round of bus changes took effect respectively (I think 384 was also launched in one of these rounds too, not 1990).
I feel sorry for the roads missing out on the 384 but the new route seems like such an obvious proposition, even if a part working of the 614 might have also been a good plan. Maybe the very short 389 or 399 routes in Barnet could be extended to cover bits of the lost 384 route?
BusAndTrainUser says:
How interesting Andrew – I've just checked again and in 1978 it was re-extended back to Palmers Green replacing the 212 and continued until 1994 when it was cut back to Brent Cross and the 232 started. I'd forgotten that bit of history – will update the post. Thanks for spotting that.
grahamjohnstokesgmailcom says:
As you may know Roger whenever in doubt, or not, Ian Armstrong's site is the place to head to https://www.londonbuses.co.uk/
Ben Pattison says:
Interesting article as ever, but always so disappointing to see the lacklustre standards TfL apply to much-needed publicity. Checking Apple and Google maps, neither update their route or live departures information for either of the two routes (the only mention being of route changes on google maps, but only as a status update, the old times are still shown). It is such a shame, as TfL undoubtedly argue that using these can be an alternative to bus stop information (it seems not so). It is therefore a great surprise for TfL to state that as part of new, designated school services on existing bus routes, information "will be posted at relevant bus stops in the biggest bus stop poster campaign in TfL's history". If only this much attention were to be paid to bus stops on newly extended routes, where people (bus users even) plausibly are unaware of the much improved service (with the possible exception of some of the residential areas on the 384).
Ian McNeil says:
My memory of the 112 goes back to 1966 when it was operated by open-platform RTLs (not fitted with heaters) from Stonebridge Park (SE) and ran between Ealing Broadway and Palmers Green.
Me too; they used to pass my as I walked to school along Bowes Road having got off a 244 in Brownlow Road.
LBE97 says:
It's quite disappointing to see the 384 changes get through. The locals around Barnet were actively campaigning to keep it along the roads no longer served. The 384 is back road route as you said, not an orbital trunk route.
There's a lot of areas in TFL territory that do not have direct links to places at all. Edgware to Barnet already has the 614, and if a passenger does not like Uno, the 107 has done the link perfectly fine for years.
How very typical of the blinkered "we know best" regime of TfL to ignore the excellent UNO 614! In the coming economic climate, such a service should be embraced and integrated with the London network. I suspect we may see a few more withdrawals from outer suburbia where parked cars are many and passengers few. And why no time inter-working with the 292, particularly after a service reduction? As stated many times before, TfL clearly have people who are absolutely wizard at administrative/tender processes, particularly those taking two years to implement (!), but zilch understanding of proper bus service planning. And why oh why does London have this peculiar procedure (and this went on in London Transport days) of worrying about arrival at destination early. Provided the bus has left the last timing point as advertised (except of course times are NOT advertised these days), what the hell does it matter if passengers at least get a decent run on the last leg. We are constantly being told how buses need to be speeded up in the brave new world, yet London buses are now so absurdly slow, certainly on all the routes I have travelled on of late, that passengers are voting with their feet.
The 384 is a North London local route I cannot see much demand to go to Edgware. It might have made more sense to extend it to Wood Green
greenline727 says:
The extension of Route 384 (and the associated road withdrawals within Barnet) has been contentious for years, but as usual TfL has justified its own decisions and ignored the wishes of existing passengers. Reducing Route 292 to 3 BPH is probably the correct service level throughout the route, although Herts CC weren't happy about the reduction, but as they don't pay anything don't really have any locus to complain!!
I believe that the schedules couldn't be compiled to provide an even headway without requiring an extra bus in the cycle, which TfL wouldn't permit (in passing, service specifications and PVR's are now VERY tightly specified, with the added restriction that all buses MUST be Euro6 from October 2020, and the conversion process is quite expensive, so extra buses are simply verboten now, unless the operator pays the cost).
Concerning running times (and this applies throughout the land), operators are always expecting traffic levels to rise some time soon, thereby reducing speeds achievable. Yes, this is taking time to occur, but when the schools return, and Little Johnny is scared of travelling by bus so Mum's Taxi will be used, we could see the peak traffic back to pre-C19 levels sooner rather than later!! Schedulers have prioritised restoration of service levels and school duplications recently, but rest assured that running times will be next on the list for attention . . . . if it saves a PVR, then it'll be worth doing in our Brave New World!!
Kim Rennie says:
Presumably TfL ignore Uno routes as they do not accept TfL tickets or passes? The LT Suburban timetable booklets issued until c1970 (?) included LT bus, LCBS bus and coach, NBC and independent bus companies, Underground and even BR services; but that was in the days of cash fares and point-to-point season tickets.
Peter Luck says:
The lack of publicity for these changes is shameful, but not by any means unusual. TfL should be shamed into reintroducing bus maps, which have been systematically withdrawn. When hard copies of the maps were discontinued, these maps continued to be available on-line until comparatively recently, when even this provision ceased.
The spider maps now on offer are inadequate and difficult to use. They do not even begin to replace the former excellent and comprehensive maps which showed the entire course of every bus route and which were readily available to all who wanted them. Their reintroduction would be a win-win situation, enabling people to plan their journeys more effectively and indeed to make more journeys.
Peter Luck


From single-channel to cross-channel interactions, customers must be able to move seamlessly among them without data loss.
New technologies encourage speech designers to get creative.
The cloud services provider sought to add voice technologies to automate transactions.


Google+ Plugin Αποστολή πληροφοριών στο "Google+" plugin.
Facebook Plugin Αποστολή πληροφοριών στο "Like" plugin.
JSESSIONID Γνώση του αριθμού των χρηστών που επισκέπτονται τον ιστότοπο.
pgid sid Ταυτοποιούν τον χρήστη για να δείξουν προσωποποιημένο περιεχόμενο. Τι είδε πρόσφατα.
session Αποτρέπει την επαναλαμβανόμενη απεικόνιση μηνύματος καλωσορίσματος.
The tracking cookies, and especially third-party tracking cookies, are commonly used as ways to compile long-term records of individuals' browsing histories – a potential privacy concern that prompted European and U.S. lawmakers to take action in 2011.European law requires that all websites targeting European Union member states gain "informed consent" from users before storing non-essential cookies on their device.
The term "cookie" was coined by web browser programmer Lou Montulli. It was derived from the term "magic cookie", which is a packet of data a program receives and sends back unchanged, used by Unix programmers.
Magic cookies were already used in computing when computer programmer Lou Montullihad the idea of using them in web communications in June 1994. At the time, he was an employee of Netscape Communications, which was developing an e-commerce application for MCI. Vint Cerf and John Klensin represented MCI in technical discussions with Netscape Communications. MCI did not want its servers to have to retain partial transaction states, which led them to ask Netscape to find a way to store that state in each user's computer instead. Cookies provided a solution to the problem of reliably implementing a virtual shopping cart.
The introduction of cookies was not widely known to the public at the time. In particular, cookies were accepted by default, and users were not notified of their presence. The general public learned about cookies after the Financial Times published an article about them on February 12, 1996. In the same year, cookies received a lot of media attention, especially because of potential privacy implications. Cookies were discussed in two U.S. Federal Trade Commission hearings in 1996 and 1997.
The development of the formal cookie specifications was already ongoing. In particular, the first discussions about a formal specification started in April 1995 on the www-talk mailing list. A special working group within the Internet Engineering Task Force (IETF) was formed. Two alternative proposals for introducing state in HTTP transactions had been proposed by Brian Behlendorf and David Kristol respectively. But the group, headed by Kristol himself and Lou Montulli, soon decided to use the Netscape specification as a starting point. In February 1996, the working group identified third-party cookies as a considerable privacy threat. The specification produced by the group was eventually published as RFC 2109 in February 1997. It specifies that third-party cookies were either not allowed at all, or at least not enabled by default.
At this time, advertising companies were already using third-party cookies. The recommendation about third-party cookies of RFC 2109 was not followed by Netscape and Internet Explorer. RFC 2109 was superseded by RFC 2965 in October 2000.
RFC 2965 added a Set-Cookie2 header, which informally came to be called "RFC 2965-style cookies" as opposed to the original Set-Cookie header which was called "Netscape-style cookies". Set-Cookie2 was seldom used however, and was deprecated in RFC 6265 in April 2011 which was written as a definitive specification for cookies as used in the real world.
Instead of expiring when the web browser is closed as session cookies do, a persistent cookieexpires at a specific date or after a specific length of time. This means that, for the cookie's entire lifespan (which can be as long or as short as its creators want), its information will be transmitted to the server every time the user visits the website that it belongs to, or every time the user views a resource belonging to that website from another website (such as an advertisement).
The term "supercookie" is sometimes used for tracking technologies that do not rely on HTTP cookies. Two such "supercookie" mechanisms were found on Microsoft websites in August 2011: cookie syncing that respawned MUID (machine unique identifier) cookies, and ETag cookies. Due to media attention, Microsoft later disabled this code.
Zero or more attributes (name/value pairs). Attributes store information such as the cookie's expiration, domain, and flags (such as Secure and HttpOnly).
Corporations exploit users' web habits by tracking cookies to collect information about buying habits. The Wall Street Journal found that America's top fifty websites installed an average of sixty-four pieces of tracking technology onto computers resulting in a total of 3,180 tracking files. The data can then be collected and sold to bidding corporations.
Can support cookies as large as 4,096 bytes in size.
Can support at least 50 cookies per domain (i.e. per website).
Can support at least 3,000 cookies in total.
Cookies are set using the Set-Cookie HTTP header, sent in an HTTP response from the web server. This header instructs the web browser to store the cookie and send it back in future requests to the server (the browser will ignore this header if it does not support cookies or has disabled cookies).
The server's HTTP response contains the contents of the website's homepage. But it also instructs the browser to set two cookies. The first, "theme", is considered to be a session cookie, since it does not have an Expires or Max-Age attribute. Session cookies are intended to be deleted by the browser when the browser closes. The second, "sessionToken" is considered to be a persistent cookie, since it contains an Expiresattribute, which instructs the browser to delete the cookie at a specific date and time.
This way, the server knows that this request is related to the previous one. The server would answer by sending the requested page, possibly including more Set-Cookieheaders in the response in order to add new cookies, modify existing cookies, or delete cookies.
The value of a cookie may consist of any printable ASCII character (! through ~, Unicode\u0021 through \u007E) excluding , and ; and whitespace characters. The name of a cookie excludes the same characters, as well as =, since that is the delimiter between the name and value. The cookie standard RFC 2965 is more restrictive but not implemented by browsers.
The term "cookie crumb" is sometimes used to refer to a cookie's name–value pair.
In addition to a name and value, cookies can also have one or more attributes. Browsers do not include cookie attributes in requests to the server—they only send the cookie's name and value. Cookie attributes are used by browsers to determine when to delete a cookie, block a cookie or whether to send a cookie to the server.
The Domain and Path attributes define the scope of the cookie. They essentially tell the browser what website the cookie belongs to. For obvious security reasons, cookies can only be set on the current resource's top domain and its sub domains, and not for another domain and its sub domains. For example, the website example.org cannot set a cookie that has a domain of foo.com because this would allow the example.org website to control the cookies of foo.com.
If a cookie's Domain and Path attributes are not specified by the server, they default to the domain and path of the resource that was requested. However, in most browsers there is a difference between a cookie set from foo.com without a domain, and a cookie set with the foo.com domain. In the former case, the cookie will only be sent for requests to foo.com, also known as a host-only cookie. In the latter case, all sub domains are also included (for example, docs.foo.com). A notable exception to this general rule is Internet Explorer, which always sends cookies to sub domains regardless of whether the cookie was set with or without a domain.
The first cookie, LSID, has no Domain attribute, and has a Path attribute set to /accounts. This tells the browser to use the cookie only when requesting pages contained in docs.foo.com/accounts (the domain is derived from the request domain). The other two cookies, HSID and SSID, would be used when the browser requests any subdomain in .foo.com on any path (for example www.foo.com/bar). The prepending dot is optional in recent standards, but can be added for compatibility with RFC 2109 based implementations.
The Expires attribute defines a specific date and time for when the browser should delete the cookie. The date and time are specified in the form Wdy, DD Mon YYYY HH:MM:SS GMT, or in the form Wdy, DD Mon YY HH:MM:SS GMT for values of YY where YY is greater than or equal to 0 and less than or equal to 69.
The first cookie, lu, is set to expire sometime on 15 January 2013. It will be used by the client browser until that time. The second cookie, made_write_conn, does not have an expiration date, making it a session cookie. It will be deleted after the user closes their browser. The third cookie, reg_fb_gate, has its value changed to "deleted", with an expiration time in the past. The browser will delete this cookie right away because its expiration time is in the past. Note that cookie will only be deleted if the domain and path attributes in the Set-Cookie field match the values used when the cookie was created.
As of 2016 Internet Explorer did not support Max-Age.
The Secure and HttpOnly attributes do not have associated values. Rather, the presence of just their attribute names indicates that their behaviors should be enabled.
By default, Internet Explorer allows third-party cookies only if they are accompanied by a P3P "CP" (Compact Policy) field.
The possibility of building a profile of users is a privacy threat, especially when tracking is done across multiple domains using third-party cookies. For this reason, some countries have legislation about cookies.
The United States government has set strict rules on setting cookies in 2000 after it was disclosed that the White House drug policy office used cookies to track computer users viewing its online anti-drug advertising. In 2002, privacy activist Daniel Brandt found that the CIA had been leaving persistent cookies on computers which had visited its website. When notified it was violating policy, CIA stated that these cookies were not intentionally set and stopped setting them. On December 25, 2005, Brandt discovered that the National Security Agency (NSA) had been leaving two persistent cookies on visitors' computers due to a software upgrade. After being informed, the NSA immediately disabled the cookies.
In 2002, the European Union launched the Directive on Privacy and Electronic Communications, a policy requiring end users' consent for the placement of cookies, and similar technologies for storing and accessing information on users' equipment. In particular, Article 5 Paragraph 3 mandates that storing data in a user's computer can only be done if the user is provided information about how this data is used, and the user is given the possibility of denying this storing operation.
Directive 95/46/EC defines "the data subject's consent" as "any freely given specific and informed indication of his wishes by which the data subject signifies his agreement to personal data relating to him being processed." Consent must involve some form of communication where individuals knowingly indicate their acceptance.
Some cookies can be exempted from informed consent under certain conditions if they are not used for additional purposes. These cookies include cookies used to keep track of a user's input when filling online forms or as a shopping cart.
The industry's response has been largely negative. Robert Bond of the law firm Speechly Bircham describes the effects as "far-reaching and incredibly onerous" for "all UK companies". Simon Davis of Privacy International argues that proper enforcement would "destroy the entire industry".
Third-party cookies can be blocked by most browsers to increase privacy and reduce tracking by advertising and tracking companies without negatively affecting the user's web experience. Many advertising operators have an opt-out option to behavioural advertising, with a generic cookie in the browser stopping behavioural advertising.
Listed here are various scenarios of cookie theft and user session hijacking (even without stealing user cookies) which work with websites which rely solely on HTTP cookies for user identification.
Traffic on a network can be intercepted and read by computers on the network other than the sender and receiver (particularly over unencrypted open Wi-Fi). This traffic includes cookies sent on ordinary unencrypted HTTP sessions. Where network traffic is not encrypted, attackers can therefore read the communications of other users on the network, including HTTP cookies as well as the entire contents of the conversations, for the purpose of a man-in-the-middle attack.
An attacker could use intercepted cookies to impersonate a user and perform a malicious task, such as transferring money out of the victim's bank account.
This issue can be resolved by securing the communication between the user's computer and the server by employing Transport Layer Security (HTTPS protocol) to encrypt the connection. A server can specify the Secure flag while setting a cookie, which will cause the browser to send the cookie only over an encrypted channel, such as an SSL connection.
If an attacker is able to cause a DNS server to cache a fabricated DNS entry (called DNS cache poisoning), then this could allow the attacker to gain access to a user's cookies. For example, an attacker could use DNS cache poisoning to create a fabricated DNS entry of f12345.www.example.com that points to the IP address of the attacker's server. The attacker can then post an image URL from his own server (for example, http://f12345.www.example.com/img_4_cookie.jpg). Victims reading the attacker's message would download this image from f12345.www.example.com. Since f12345.www.example.com is a sub-domain of www.example.com, victims' browsers would submit all example.com-related cookies to the attacker's server.
If an attacker is able to accomplish this, it is usually the fault of the Internet Service Providers for not properly securing their DNS servers. However, the severity of this attack can be lessened if the target website uses secure cookies. In this case, the attacker would have the extra challenge of obtaining the target website's SSL certificate from a certificate authority, since secure cookies can only be transmitted over an encrypted connection. Without a matching SSL certificate, victims' browsers would display a warning message about the attacker's invalid certificate, which would help deter users from visiting the attacker's fraudulent website and sending the attacker their cookies.
When another user clicks on this link, the browser executes the piece of code within the onclick attribute, thus replacing the string document.cookie with the list of cookies that are accessible from the current page. As a result, this list of cookies is sent to the attacker.com server. If the attacker's malicious posting is on an HTTPS website https://www.example.com, secure cookies will also be sent to attacker.com in plain text.
It is the responsibility of the website developers to filter out such malicious code.
In older versions of many browsers, there were security holes in the implementation of the XMLHttpRequest API. This API allows pages to specify a proxy server that would get the reply, and this proxy server is not subject to the same-origin policy. For example, a victim is reading an attacker's posting on www.example.com, and the attacker's script is executed in the victim's browser. The script generates a request to www.example.com with the proxy server attacker.com. Since the request is for www.example.com, all example.com cookies will be sent along with the request, but routed through the attacker's proxy server. Hence, the attacker would be able to harvest the victim's cookies.
This attack would not work with secure cookies, since they can only be transmitted over HTTPS connections, and the HTTPS protocol dictates end-to-end encryption (i.e. the information is encrypted on the user's browser and decrypted on the destination server). In this case, the proxy server would only see the raw, encrypted bytes of the HTTP request.
If Bob's bank keeps his authentication information in a cookie, and if the cookie hasn't expired, then the attempt by Bob's browser to load the image will submit the withdrawal form with his cookie, thus authorizing a transaction without Bob's approval.
Besides privacy concerns, cookies also have some technical drawbacks. In particular, they do not always accurately identify users, they can be used for security attacks, and they are often at odds with the Representational State Transfer (REST) software architectural style.
Likewise, cookies do not differentiate between multiple users who share the same user account, computer, and browser.
Some of the operations that can be done using cookies can also be done using other mechanisms.
A JSON Web Token (JWT) is a self-contained packet of information that can be used to store user identity and authenticity information. This allows them to be used in place of session cookies. Unlike cookies, which are automatically attached to each HTTP request by the browser, JWTs must be explicitly attached to each HTTP request by the web application.
The HTTP protocol includes the basic access authentication and the digest access authentication protocols, which allow access to a web page only when the user has provided the correct username and password. If the server requires such credentials for granting access to a web page, the browser requests them from the user and, once obtained, the browser stores and sends them in every subsequent page request. This information can be used to track the user.
Some users may be tracked based on the IP address of the computer requesting the page. The server knows the IP address of the computer running the browser (or the proxy, if any is used) and could theoretically link a user's session to this IP address.
However, IP addresses are generally not a reliable way to track a session or identify a user. Many computers designed to be used by a single user, such as office PCs or home PCs, are behind a network address translator (NAT). This means that several PCs will share a public IP address. Furthermore, some systems, such as Tor, are designed to retain Internet anonymity, rendering tracking by IP address impractical, impossible, or a security risk.
A more precise technique is based on embedding information into URLs. The query stringpart of the URL is the part that is typically used for this purpose, but other parts can be used as well. The Java Servlet and PHP session mechanisms both use this method if cookies are not enabled.
This method consists of the web server appending query strings containing a unique session identifier to all the links inside of a web page. When the user follows a link, the browser sends the query string to the server, allowing the server to identify the user and maintain state.
These kinds of query strings are very similar to cookies in that both contain arbitrary pieces of information chosen by the server and both are sent back to the server on every request. However, there are some differences. Since a query string is part of a URL, if that URL is later reused, the same attached piece of information will be sent to the server, which could lead to confusion. For example, if the preferences of a user are encoded in the query string of a URL and the user sends this URL to another user by e-mail, those preferences will be used for that other user as well.
Moreover, if the same user accesses the same page multiple times from different sources, there is no guarantee that the same query string will be used each time. For example, if a user visits a page by coming from a page internal to the site the first time, and then visits the same page by coming from an external search engine the second time, the query strings would likely be different. If cookies were used in this situation, the cookies would be the same.
Other drawbacks of query strings are related to security. Storing data that identifies a session in a query string enables session fixation attacks, referer logging attacks and other security exploits. Transferring session identifiers as HTTP cookies is more secure.
Another form of session tracking is to use web forms with hidden fields. This technique is very similar to using URL query strings to hold the information and has many of the same advantages and drawbacks. In fact, if the form is handled with the HTTP GET method, then this technique is similar to using URL query strings, since the GET method adds the form fields to the URL as a query string. But most forms are handled with HTTP POST, which causes the form information, including the hidden fields, to be sent in the HTTP request body, which is neither part of the URL, nor of a cookie.
This approach presents two advantages from the point of view of the tracker. First, having the tracking information placed in the HTTP request body rather than in the URL means it will not be noticed by the average user. Second, the session information is not copied when the user copies the URL (to bookmark the page or send it via email, for example).
The downside is that every separate window or tab will initially have an empty window.name property when opened. Furthermore, the property can be used for tracking visitors across different websites, making it of concern for Internet privacy.
In some respects, this can be more secure than cookies due to the fact that its contents are not automatically sent to the server on every request like cookies are, so it is not vulnerable to network cookie sniffing attacks. However, if special measures are not taken to protect the data, it is vulnerable to other attacks because the data is available across different websites opened in the same window or tab.
Apple uses a tracking technique called "identifier for advertisers" (IDFA). This technique assigns a unique identifier to every user that buys an Apple iOS device (such as an iPhone or iPad). This identifier is then used by Apple's advertising network, iAd, to determine the ads that individuals are viewing and responding to.
Because ETags are cached by the browser, and returned with subsequent requests for the same resource, a tracking server can simply repeat any ETag received from the browser to ensure an assigned ETag persists indefinitely (in a similar way to persistent cookies). Additional caching headers can also enhance the preservation of ETag data.
ETags can be flushed in some browsers by clearing the browser cache.
Some web browsers support persistence mechanisms which allow the page to store the information locally for later use.
Internet Explorer supports persistent information  in the browser's history, in the browser's favorites, in an XML store ("user data"), or directly within a web page saved to disk.
Some web browser plugins include persistence mechanisms as well. For example, Adobe Flash has Local shared object and Microsoft Silverlight has Isolated storage.
A browser fingerprint is information collected about a browser's configuration, such as version number, screen resolution, and operating system, for the purpose of identification. Fingerprints can be used to fully or partially identify individual users or devices even when cookies are turned off.
Basic web browser configuration information has long been collected by web analyticsservices in an effort to accurately measure real human web traffic and discount various forms of click fraud. With the assistance of client-side scripting languages, collection of much more esoteric parameters is possible. Assimilation of such information into a single string comprises a device fingerprint. In 2010, EFF measured at least 18.1 bits of entropy possible from browser fingerprinting. Canvas fingerprinting, a more recent technique, claims to add another 5.7 bits.


My friendship with Ren goes beyond the stars and what our compatible zodiac signs have to say for it. I will never forget meeting them at Kellogg's Diner for waffles at 8am while I cried about whatever life crisis I was going through at the moment. They comfort me, encourage me, and give me more love than I can contain in my heart. Being around them feels safe for me. It's like being in a world where nothing bad happens and we're always smiling. In this perfect world, the sun is always glistening on my skin while we lay on fresh grass, and at night, the stars are visible and we point out all the constellations we see. I'm eternally blessed to have this secret hidden world that fulfills me when I'm around them. And I hope others get to travel to this place too in their lifetime after meeting them.
Catch Ren play at our NYC Release party on May 31st at Mehanata Bulgarian Bar. More info HERE.


text:
/*
Counting block combinations II
Problem 115

NOTE: This is a more difficult version of problem 114.
A row measuring n units in length has red blocks with a minimum length of m units placed on it, such that any two red blocks (which are allowed to be different lengths) are separated by at least one black square.
Let the fill-count function, F(m, n), represent the number of ways that a row can be filled.
For example, F(3, 29) = 673135 and F(3, 30) = 1089155.
That is, for m = 3, it can be seen that n = 30 is the smallest value for which the fill-count function first exceeds one million.
In the same way, for m = 10, it can be verified that F(10, 56) = 880711 and F(10, 57) = 1148904, so n = 57 is the least value for which the fill-count function first exceeds one million.
For m = 50, find the least value of n for which the fill-count function first exceeds one million.
*/