text:
Willem Sandberg's Maverick Typography
By Steven HellerPosted January 9, 2020 ∙ 2 min. read
Willem Sandberg (1897-1984) was a typographic maverick until the day he died. Much of his most signature work were catalogues and posters, often designed in the evenings and weekends. Sandberg was the director of Amsterdam's Stedelijk Museum from 1945 to 1962, and his association with the local state printer "produced an identity that transformed the museum into one of Europe's first truly modern galleries," noted Simon Garfield in The Guardian newspaper. He rejected "the traditional dark and hushed rooms and creating something bright and accessible, a place of social interaction." And this held for the graphic design that for two decades typified the institution.
"He was a late starter and produced the majority of his work in his late forties," wrote Petr Bil'ak Starting in 1945, when he became the director of the Stedelijk museum, until 1962 Sandberg designed almost all the printed matter for the museum (over 250 catalogues and 270 posters). Additionally, he was an active member of countless institutions, committees and advisory bodies – unusual for a director with executive and administrative duties. Sandberg transformed the Stedelijk physically as well as conceptually, modernized its spaces, initiated construction of a new wing, expanded the collection and introduced many new ideas into the often stuffy world of museums.
Sandberg directed exhibitions of American and European artists, including Picasso and Pollock, and made sure that Kandinsky, Mondrian and Schwitters were included in the collection. "He spoke of how he was primarily interested in an artist's character; only through character could he determine whether they would make great things in the future or retreat into repetition." His directorial skills were recognized internationally.
Sandberg spent several years in the mid-60s establishing the Israel Museum in Jerusalem, and he was on the design committee for the Pompidou Centre in Paris when it appointed architects Richard Rodgers, Renzo Piano and Gianfranco Franchini in 1971. But it is his typography that also stands the test of time as presented here, it looks as fresh if it were done today.
His museum work would be career defining enough, but his typography and lettering, unique color combinations and expressionist design makes him one of the leading 20th century masters of art type.
Catalog cover, 1973.
Piet Zwart 80, 1965.
Cover for the Journal Musées Néerlandais, 1963.
Experimenta Typografica 11, 1956.
Cover for the catalogue de la Biblioteque due Stedelijk, 1957.
Expérimenta Typografica 11, 1956.
Texte Amendé "NU 1", 1959.
La Nouvelle Aile du Stedelijk, 1954.
Texte et illustration de "NU 2," 1968.
Symbols for le Musée d'Isreal a Jérussalem, 1964.
Posted inHistory ∙ The Daily Heller ∙ Typography
Browse all History


The Hopewell Inn is the oldest bar & grill in Dutchess County dating back to the late 1800s. Owners Dawn & Tom Weber have owned the bar for over 25 years and have continued the legacy of the business. The Hopewell Inn offers good bar food, low-priced cocktails and beer, and a complete outdoor Beach Yard complete with sand, tables, a stage, and more.
We helped bring this partner into the 21st century with a brand logo design, menu design, and complete website design. The logo hones in on the history of the business as a tenant house for railroad workers in the early 1900s. The website offers a way for the business to reach new potential customers online, while also providing a place for current customers to find information and upcoming events. Finally, the menu speaks to the business's laid-back brand experience while also using industry standards to inform and highlight popular weekly promotions.
A fun and informative menu design.
A brand logo that hones the history of the business.


The formulary comprises a list of medicines which have been approved by the SE Essex Medicines Management Committee (SEEMMC) for prescribing within the Trust.
The purpose of the formulary is to ensure evidence-based and cost-effective prescribing and provide information relating to drug use. All prescribing from within the Trust (i.e. in-patient, out-patient and FP10 prescribing) must comply with the formulary. Advice given to GPs with regard to drug treatment options must also be in line with Trust formulary recommendations. This is monitored on an ongoing basis by the Department of Pharmacy.
To ensure patient care is consistent, representatives from the local CCGs are members of SEEMMC. They ensure any drugs that are approved for the hospital formulary are managed appropriately e.g. clarifying hospital specialist & GP responsibilities.
The trust formulary can be accessed through the links at the bottom of this page.
NICE (National Institute for Health and Clinical Excellence) is the independent organisation responsible for providing national guidance on the promotion of good health and the prevention and treatment of ill health. NICE provide guidance in the form of Technology Appraisals. These are based on the best available evidence of the most effective care, looking at clinical and cost effectiveness, and aims to ensure treatment is available equally across different regions (i.e. avoids so called 'postcode prescribing').
The Foundation Trust has a responsibility to implement NICE Technology Appraisals to ensure patients receive the best and most appropriate treatment and that NHS resources are not wasted by inappropriate treatment.Under the NHS Constitution, patients have the right to drugs and treatments recommended by NICE if their doctor thinks it is clinically appropriate. The statutory obligation is for NHS organisations to fund new drugs and treatments within three months of the date of issue, unless specifically exempted. Southend has a process in place to enable access to all NICE-approved medicines.
It is essential that members of the SEEMMC discuss every medicine before it is used in the Trust in order to assess governance and safety issues. Many of the drugs are highly specialized and staff might require training and further guidance. We may also need to produce new information to explain the medicine to patients.
If a clinician wishes to use a NICE-approved medicine a request is made to the SEEMMC, and approval (within the terms of the guidance) is automatic. At this point the medicine is added to the Trust main formulary list along with any specific local commentary.
These are medicines that may be used in the Trust but have not yet been requested by a clinician and consequently have not been discussed at the Medicines Management Committee. The reason for not yet using the medicine will always be clinical.
The formulary comprises a list of medicines which have been approved by the SE Essex Medicines Management Committee for prescribing within the Trust.
Drugs listed are available for general prescribing unless specific restrictions are indicated.
Treatment with a non-formulary drug may be continued in this case. Patients' own supplies should always be used before requesting a supply from pharmacy and it should be borne in mind that there may be a delay in obtaining a non-formulary drug. An appropriate alternative should be considered in situations where treatment may otherwise be interrupted.
An admission to hospital represents an opportunity to review a patient's existing drug therapy and, if appropriate, treatment may be changed to a drug that is on the Trust formulary.
If pharmacy have not been involved in the discussion at this point, the chair will liaise with the Clinical Lead or deputy to ensure the decision is communicated, and where necessary, prompt supply of the medicine is organised.
Such an application will be considered for "one-off" occasions of drug use. A full application must be made for drugs which are required for addition to the formulary (see below).
The addition of new drugs to the formulary, and consequently to pharmacy stock, will be made only with the agreement of the Medicines Management Committee. In order to request an addition to the formulary, a New Drug Submission form must be completed in full and supporting evidence attached.
In addition, a submission form must be completed for any new indications for an existing formulary medicine.
The new drug submission form is available in the formulary section on the intranet. It is advised that clinicians inform pharmacy (e.g. relevant business unit pharmacist) before completing a submission form to ensure that the appropriate processes are followed.
Patients' own medicines should be obtained and used before any drug is requested from pharmacy.
The Trust and local CCGs have agreed that a medicines supply of 2 - 4 weeks should be prescribed on out-patient and discharge prescriptions.
It should be noted that items prescribed on FP10 (HP) forms and dispensed in a community pharmacy are charged to the Trust. Therefore the rules with regard to Trust formulary prescribing and length of treatment must be followed. Prescriptions should be issued from out-patient clinics only when drug treatment is required to start immediately. In all other circumstances treatment recommendations should be communicated to the patient's GP using the out-patient clinic communication form. Patients should be encouraged to keep up to date with their usual medication supplies and informed that these may not be supplied from out-patient clinics.
A breakdown of drug expenditure (including FP10 expenditure) is reported quarterly to each Business Unit. Non-formulary and other inappropriate prescribing will be identified and reported to the Business Unit leads.
Clinical and pharmaceutical information provided within the formulary is intended as a guide only. Always check relevant information sources before prescribing or administering any drug.
The formulary below will be updated quarterly.


text:
Q: Download and delete file from Azure file shares I have below code to download files from Azure file shares to local and it works fine.
Is there any way, I can delete the file, once download is completed?
using Azure.Storage.Files.Shares;
using Azure.Storage.Files.Shares.Models;

static void Main(string[] args)
{
    // Get a connection string to our Azure Storage account.
    string connectionString = ConfigurationManager.AppSettings.Get("StorageConnectionString");

    // Get a reference to a share named "sample-share"
    ShareClient share = new ShareClient(connectionString, ConfigurationManager.AppSettings.Get("ShareNamed"));

    // Get a reference to a directory named "sample-dir"
    ShareDirectoryClient dir = share.GetDirectoryClient(ConfigurationManager.AppSettings.Get("SourceDirectory"));

    foreach (ShareFileItem item in dir.GetFilesAndDirectories())
    {
        Console.WriteLine(item.Name);
         // Get a reference to a file named "sample-file" in directory "sample-dir"
        ShareFileClient file = dir.GetFileClient(item.Name);

        // Download the file
        ShareFileDownloadInfo download = file.Download();

        using (FileStream stream = File.Open(ConfigurationManager.AppSettings.Get("DestinationDirectory") + item.Name, FileMode.Append))
        {
            download.Content.CopyTo(stream);
            stream.FlushAsync();
            stream.Close();
        }

    }

    Console.ReadLine();
}

A: Simply add await file.DeleteAsync to delete the file after you have read the stream.
Something like:
static void Main(string[] args)
{
    // Get a connection string to our Azure Storage account.
    string connectionString = ConfigurationManager.AppSettings.Get("StorageConnectionString");

    // Get a reference to a share named "sample-share"
    ShareClient share = new ShareClient(connectionString, ConfigurationManager.AppSettings.Get("ShareNamed"));

    // Get a reference to a directory named "sample-dir"
    ShareDirectoryClient dir = share.GetDirectoryClient(ConfigurationManager.AppSettings.Get("SourceDirectory"));

    foreach (ShareFileItem item in dir.GetFilesAndDirectories())
    {
        Console.WriteLine(item.Name);
        // Get a reference to a file named "sample-file" in directory "sample-dir"
        ShareFileClient file = dir.GetFileClient(item.Name);

        // Download the file
        ShareFileDownloadInfo download = file.Download();

        using (FileStream stream = File.Open(ConfigurationManager.AppSettings.Get("DestinationDirectory") + item.Name, FileMode.Append))
        {
            download.Content.CopyTo(stream);
            stream.FlushAsync();
            stream.Close();
        }
        await file.DeleteAsync();
    }

    Console.ReadLine();
}

redpajama_set_name: RedPajamaStackExchange


Living on a community in Spain - don't do it unless you have to!
Cherries are on the markets in Spain - and they are so healthy and cheap!
I just did something amazing in the loo.
GDS has a MASSIVE, IMPORTANT breakthrough.


text:
Wisconsin Election Results
For the latest election results, click here
Below are the up to date results to the key races in Tuesday's election.
School Board Races: Len Albrecht, Steve Stupak, and Michael Meyer came away with the most votes. Election results will become official after the board of canvassers meets to certify them on April 10th.
Maple Referendum: The Maple School District asked for a referendum of $582,000 for programs through 2021. They missed the mark just barely with 52% of voters saying no to the referendum.
State Treasurer: With a vote of 61 to 38, voters have decided to keep the state's treasurer.
Superior District 6 Council: Tylor Elm (I) won his seat with 122 votes.
Superior District 3 Council: Warren Bender (I) won his seat with 276 votes.
Superior District 9 Council: Keith Kern (I) won his seat with 402 votes.
State Supreme Court: Liberal Milwaukee Judge Rebecca Dallet beat out her opponent for a seat on the Supreme Court by a double-digit margin.
Town of Superior Fire Hall: Two questions were posed in the town of Superior: 62% of voters said yes, they believe the city should spend $25,000 for land to build a new fire hall, and 68% of voters also said yes to build a new fire hall for $1.8 million.
Categories: Links, News, News – Latest News

redpajama_set_name: RedPajamaCommonCrawl


Here I am at my mum's house, unsure of where I am and what to do next. There's a lot of sorting out to do (read the last blog if you missed it). That's not for now though.
The Sisters tour finished in fantastic fashion with great gigs in Bristol (where we righted some wrongs from last time), Liverpool (amazing and beautiful old theatre but could do with some heating) and Sheffield (great punk rock type show).
On the Sunday, we went to see the Near Meth Experience destroy some old Sisters classics at a fundraiser for our fallen comrade Simon Denbigh… what an amazing and life-affirming evening, and exactly what I needed after an awful week. To cut a long story short, Si had a stroke in February this year, which left him paralysed down his left side. Six months of rehabilitation have meant he is able to get around very slowly and steadily, but his flat needs modernising so that he is able to attain a level of independence he doesn't currently have. I had an idea that we could do a fundraiser for him at the ever-excellent Brudenell Social Club, and before I knew it, I had a million people wanting to lend a hand. From the ace Membranes to the legendary Utah Saints, via a cast of seemingly thousands on merch, plus the Sisters… I mean Near Meth Experience crew, all of whom were working for free (and many of whom had never met Si before, and were doing it just because it is a good cause)… properly life-affirming stuff. The gig was fantastic, everyone pulled together, and Simon had an amazing night – and we raised enough money to not only fix up his bathroom, but also his kitchen.
Giving up a day of your life to radically affect then next 20 years or so of someone else's is a good feeling and one which I can highly recommend.
Home for a night on my own with the cat, which was… weird, to be honest. But I like my house and where I live so I'm going to try my best to keep it. I'm over in the bosom of my family now for a bit, which is exactly where you should be at times like this.
I'm not looking forward to Christmas.


InSight is scheduled to launch from the California coast to the plains of Mars on May 5, 2018. This is the first launch to another planet from the West Coast.
Mars: We Can Get There, But How do We Land?
NASA's HabEx Mission and Living Earths: The Astronomical Answer to "Are We Alone?"


text:
Idle Hands - Horror Film Review
This is quite a funny film, also a bit disgusting though, like Braindead-lite in places. It features a young cast, including the annoying Seth Green who isn't as irritating as he usually is.
There's a saying 'Idle hands are the Devils playground' which becomes true in this film as one of the laziest people in the entire world - a stoner called Anton has his hand possessed by the Devil. At first he doesn't realise, but after murdering his two best friends he does become aware. The hand is very murderous and acts independently of Anton which makes for some really really funny moments. Anton finally in desperation lops his hand off with a meat cleaver, but this turns out to be the very worst thing he could have possibly done...
The film is very funny. It is nearly a day later before lazy Anton notices his parents corpses in plain view in his house as he was too busy listening to music and watching TV. His murdered friends come back to life as Zombies due to them thinking Heaven looked kinda boring, despite being dead they are the same as they always were, and being set around Halloween everyone assumes their undead look is just a costume. Anton gets into hilarious situations as he tries to hunt down his evil severed hand, while being chased by a demon slayer, and his metal head friend who think he's possessed, and trying to woo the girl of his dreams (played by the beautiful Jessica Alba) at the most inconvenient of times.
The film has lots of punk rock music as it's soundtrack, and even has the band The Offspring with a guest appearance (the lead singer comes to a grizzly end!) Most the jokes are quite disgusting, but really funny. A cool film, and has zombies in it! I think there may be a sequel so if there is I will check that out.
Labels: Horror Films, Zombies
Brain Dead (1990) - Horror Film Review
The House of the Dead 2 - Horror Videogame Review ...
Persona 4 Review
Castlevania: Order of Ecclesia (2009) - Horror Vid...
Twin Blades (2009) - Zombie Horror Videogame Revie...
Wolf Creek - Horror Film Review
The Book of Eli - Post Apocalyptic Film Review
Dead Space (2008) - Horror Videogame Review (X-Box...
Why X-Box Live sucks
Dead of Night (1945) - Horror Film Review
Waxwork - My Review
Zombie Undead - My Review
Alien Hominid (2002-07) - Sci-fi Video Game Review...
Daybreakers (2009) - Horror Film Review
The Boy from Hell - Horror Film Review
Velvet Assassin
300 - Fantasy Film Review
Afro Samurai (2009) - Action Videogame Review
Halloween:Remake - Horror Film Review
Top 10 Horror Films of 2009


Manolo Blahnik's boundless creativity, unique sense of beauty and sharp eye are legendary. Inspired by the many element that surround him, be it a detail, an enticing shape, a color, a stylish muse, a piece of art or a striking architecture, his exuberant and colorful shoes are the ultimate objects of desire. Just ask Carrie Bradshaw and Blahnik's gaggle of glitterati fans.
For fall, the maestro's wide-spanning inspiration spans from Sicilian Baroque to Le Corbusier, from iconic model Jean Shrimpton captured during the Sixties by celebrated photographer and longtime friend David Bailey to the legendary Diana Vreeland, Blahnik's early mentor and fashion expert, renowned for her bold jewelry choices.
Blahnik also mined his own personal archives (and why wouldn't he, after all his career spans 45 years) and hints at one of his favorite films, Doctor Zhivago.
In celebration of Shrimpton, Blahnik created effortlessly chic ballerina flats, a kitten-heeled Mary Jane pump in patent leather and the black and white knee-high Wakia boots with block heel while the jewel-toned Vree T-strap with contrasting tongue homages Vreeland.
Similarly, the ornate Sicilian Baroque architecture that decorates the island's stunning churches informed the silhouettes of his court pumps and flats in plush silk satin with a flash of gold.
Whispered or dazzling, flat or sky-high, each shoe is a true labor of love, a luxurious and seductive treat that will bring out the Princess that is in you. Discover the new arrivals in our boutique.


Paper Summary Disposable Paper Bag means a bag made predominantly of paper that is provided to a customer by a Grocer, Large Retailer, Retailer and Retail Store at the point of sale for the purpose of transporting goods which is subject to the Town�s Waste Reduction Fee. 1. Disposable Paper Bag does not include the following: a. Paper Bags used by consumers inside Retail Stores to: 1. Package bulk items including: fruit, vegetables, nuts, grains, candy, or small hardware items; or 2. Provided for the sale of gift cards and post cards.


3. Mirrors It is important to think about the lighting in front of the mirrors. Use integrated light in the mirror and illuminate with spotlights obliquely from the front. This provides flat- tering facial lighting. Light temperature experiences In general it is common to use a warmer colour tempera- ture, around 3000 K, in a jewellery shop. But it also depends on the brand values. Accentuated warmer light gives a nice atmosphere in the shop. But if the brand is focused on being exclusive a colder light can trigger such an experience. When entering a jewellery shop the visitor should be welcomed with a pleasant atmosphere of visual quality and comfortable light levels. The customer should feel calm about choosing what to buy and when to do it, without feeling any stress. When illuminating jewellerys, colour, shapes and texture are important factors, just as the lighting. A more dramatic light or focused light with narrow beamed spotlights is beneficial and creates a comfortable and dynamic atmos- phere in the shop instead of a more flat general light. Integrated light Integrated LED luminaires can create a stimulating environment where the light will not glare and disturb the impression. Narrow shelves, furniture and other displays can be illuminated with smaller luminaires optimised for integrated lighting. Getting close to the products At a jewellery shop it is all about seeing the details. The lighting should enhance the items and therefore it is important that the lighting does not create glare. Jewellery shops have many displays with products arranged by campaign, season or brand. Try to distribute the lighting in these spaces so that the customer can get close to the products, seeing the details. A pleasant atmosphere On Demand Design Take the opportunity to stand out with tailor made retail solutions. We want you to find the exatly right solution for your project. With Fagerhult O.D.D, Fagerhult On Demand Design, we can custom make a lighting solutions after your project and demands. For example creating a special luminaire for the focal points or adopting a existing product suited for your needs. 4 a pleasant atmosphere a pleasant atmosphere 5 For us it is Crystal Clear Retailers are environmentally aware, focusing on creating a sustainable solutions and controls that maximise the energy savings. In our environmental initiative Crystal Clear we highlight the importance on thinking sustainable when creating future proofed lighting solutions.
8. Rathsack 14 reference reference 15 Rathsack is a new modern jewellery shop with edge and personality located in Linkping, Sweden. Jewellery in silver, titan, steal and palladium are offered from famous brands and young jewellery design- ers. The shop has several elegant design elements such as cabinets and a decorated cashier. Together with lighting designer Charlotta Mattsson at Tindra Design Fager- hult provided general lighting to the shop. The darker interior is illuminated with 3000 K and the mix of colder lighting in the cabinets contributes to an exclusive dynamic in the shop. Black Zone Evo spot- lights provide accent light and are provided with cap cones to avoid glare. Zone Evo is a spotlight with the latest LED technology. Lowered light levels with 1100 lm con- tribute to nice contrast in the shop, which further enhance the elegant atmosphere.
9. fagerhult retail ab main office Rinnavgen 12 517 33 Bollebygd, Sweden Phone: +46 33-722 15 00 www.fagerhult.com/retail At Fagerhult we feel passionate about retail lighting and can cover the entire spectrum of your lighting project with high-quality products, education, concept development, on demand design, light planning, aiming and on-going main- tenance. In this Light Guide we will give you tips on how to create a sustainable retail environment and give suggestions on what kind of products to use. Fagerhult is a part of the Fagerhult Group, one of Europes leading lighting groups, with about 2,400 employees and operations in approximately 20 countries around the world.


text:
Bedřich Pokorný (* 6. März 1904 in Brünn; † 31. März 1968 ebenda) war ein tschechoslowakischer Geheimdienstoffizier und zeitweise Leiter des tschechoslowakischen Inlandsgeheimdienstes Obranné zpravodajství (OBZ). Nach Ende des Zweiten Weltkrieges organisierte er im Brünner Todesmarsch und im Massaker von Aussig Übergriffe auf die sudetendeutsche Bevölkerung.

Leben
Pokorný besuchte eine Sekundarschule und eine Berufsakademie, bevor er im Oktober 1924 eine Militärkarriere in der Tschechoslowakischen Armee begann und als Soldat in das Infanterieregiment 31 in Jihlava eintrat. Zwei Jahre später besuchte er eine Offiziersakademie in Milovice und 1927 einen Giftgas-Kurs in Olmütz.

1934 absolvierte er eine Geheimdienstschulung im Provinzmilitärhauptquartier Košice und wurde einer Grenzeinheit als Verbindungsoffizier zugeteilt. Nach Reorganisation wurde er Agent bei der PAÚ (Predsuvná agenturní ústredna) und 1938 als Rudolf in der Slowakei gegen Ungarn eingesetzt. Nach der Besetzung und Bildung des Protektorats Böhmen und Mähren wurde er aus dem Militärdienst entlassen. 1939 bis März 1945 arbeitete er für das Finanzministerium des tschechischen Protektorats in einer Revisionskommission in Brünn und gleichzeitig als Agent des Sicherheitsdienstes des Reichsführers SS, wo er als Mitglied einer kommunistischen Zelle, die sich mit Flugblättern und Broschüren gegen die deutsche Besatzung wandte, eingesetzt war. Unklar ist, ob er dabei als Doppelagent tätig war. Am 29. April 1945 trat er in die Kommunistische Partei der Tschechoslowakei (KPTsch) ein und wurde gleichzeitig in den tschechischen Geheimdienst aufgenommen.

Nachkriegszeit
Mit der Eroberung Brünns durch die Rote Armee am 26. April 1945 formierten die Sieger den Dienst SNB, für den Pokorný von Mai bis Anfang Juli 1946 Gebietsvertreter in Mähren war, um anschließend für das Prager Innenministerium unter General Josef Bartík tätig zu sein. Hier war er verantwortlich für Berichte der Abteilungen MV (Landesverteidigung) und Z (politische Lage). Ab 18. Mai 1945 war er Befehlshaber der Nationalen Sicherheitswacht von Mähren und als solcher direkt verantwortlich für den Brünner Todesmarsch. Weiterhin war er maßgeblich an der Planung und Ausführung um die Ereignisse des Aussig-Massakers beteiligt, in deren Folge er in perfider Weise auch offiziell die Untersuchungskommission führte. Auf persönliche Weisung des damaligen Innenministers Václav Nosek wurde er am 2. Juli 1945 zum stellvertretenden Leiter der Abteilung Z ernannt. Nach einem internen Machtkampf mit seinem Vorgesetzten Josef Bartík wurde er am 15. Januar 1946 für kurze Zeit dessen Nachfolger als Chef des Inlandsgeheimdienstes OBZ.

Bereits am 3. November 1946 wurde er von diesem Posten entbunden und zum Referatsleiter des OBZ für die Slowakei degradiert. In dieser Zeit war er maßgeblich beteiligt an der Fingierung slowakischer Diversionsakte, welche zum Ziel hatten, die vollständige Machterringung der KPTsch in der gesamten Tschechoslowakei zu gewährleisten. Zugleich war er einer der Stellvertreter Jindřich Veselýs, des Chefs der Abteilung Z  (Sicherheit; des späteren tschechoslowakischen Staatssicherheitsdienstes (Státní bezpečnost, StB)). Von Februar bis April 1948 war er als getarnter Legationsrat an der Botschaft in Wien eingesetzt. Nach seiner Rückkehr nach Prag wurde er wieder stellvertretender Abteilungsleiter des OBZ.

Nach der Umbildung und Neuorganisation des Geheimdienstes wurde er am 1. Januar 1949 zum Leiter Abwehr der StB ernannt. Diese Position bekleidete er bis Oktober 1949, als er abermals von einem Posten auf dieser Führungsebene abberufen wurde. Ab 10. Oktober 1949 war er Leiter des Bereiches Gefängnisse im Innenministerium. Diese Tätigkeit übte er bis Anfang 1951 aus. Im Rahmen der Säuberungen in den Reihen der KPTsch wurde er zum Stellvertreter zurückgestuft, im Januar 1951 aus dem Dienst entlassen und am 28. Januar auf Veranlassung des Staatssicherheitsministers L. Kopřiva unter Verdacht des Landesverrats verhaftet. In einem Geheimprozess verurteilte ihn ein neunköpfiges Gericht, zusammen mit Karl Cerný nach § 85 als angeblichen Saboteur, am 23. Dezember 1953 zu 16 Jahren Haft. Er soll ab Kriegsende Verräter sowie Informanten der Gestapo eingestellt, deren Methoden eingeführt und damit Operationen des Sicherheitsapparates schwer geschädigt haben.

Pokorný gehörte zu den Parteifunktionären der zweiten Garnitur, die in dieser Zeit stalinistischen Prozessen unterzogen wurden. Zuvor waren Anfang Dezember 1952 Rudolf Slánský und andere führende Parteimitglieder im "Slánský-Prozess" hingerichtet worden.

Nach 5½ Jahren Gefängnis wurde Pokorný entlassen, wieder in die KSC (kommunistische Partei) aufgenommen und erhielt eine Schwerbeschädigtenrente sowie in späteren Jahren auch eine Entschädigung von 90.000 Kcs. Nach seiner Rückkehr in den Geheimdienst wurde er Anfang der 1960er Jahre als Oberstleutnant Chef der Geheimdienstbrigade einer Grenzbrigade an der Grenze zur Bundesrepublik Deutschland.

In der Zeit vom 8. bis 10. November 1965 wurde ein erneuter Gerichtsprozess gegen ihn durchgeführt, in welchem ihm Folterung von Gefangenen vorgeworfen wurde. Am 31. März 1968, während des Prager Frühlings, wurde er erhängt in einem Wald bei Brünn aufgefunden. Wegen der politischen Unruhen dieser Zeit kann bis heute nicht geklärt werden, ob es sich um Mord oder Selbstmord, wegen seines Wissens um die Aktionen der Staatssicherheit, handelte.

Literatur
 Helmut Roewer, Stefan Schäfer, Matthias Uhl: Lexikon der Geheimdienste im 20. Jahrhundert. Herbig, München 2003, ISBN 3-7766-2317-9.

Weblinks
 Major Bedřich Pokorný Encyklopedie dějin města Brna – Profil osobnosti , aktualisiert 6. März 2014.

Einzelnachweise

Vertreibung von Deutschen (20. Jahrhundert)
KSČ-Mitglied
Person im Zweiten Weltkrieg (Tschechoslowakei)
SD-Agent
Nachrichtendienstliche Person (Tschechoslowakei)
Person (slowakische Geschichte)
Tschechoslowake
Tscheche
Geboren 1904
Gestorben 1968
Mann

redpajama_set_name: RedPajamaWikipedia


text:
Hyundai Tate Modern sponsorship builds a bridge between art and corporate worlds - Spear's Magazine
There's nothing fishy about detoxing with superfood sushi at Sumosan Mayfair
Private university New College of the Humanities promises radical education, but are AC Grayling's ambitions realistic?
Hyundai Tate Modern sponsorship builds...
The Good Life / Art & Collecting / The Good Life
Hyundai Tate Modern sponsorship builds a bridge between art and corporate worlds
21st January 2014 by Spear's
A new bridge across the iconic Turbine Hall, linking existing galleries with a new building, is symbolic of a new sponsorship deal between Hyundai and the Tate Modern. The gallery's director Chris Dercon told Spear's: 'Building bridges is a very beautiful image for sponsorship because it enables people to connect and to use that bridge in a different way; you can go back and forth with a bridge, you can go slow and fast.'
The major new long-term partnership, set to last until 2025, was announced this morning. Speaking at the press launch Secretary of State for Culture, Media and Sport Maria Miller praised the deal, saying 'private sector support for art is vital' and identifying the 'potential mutual support it can bring' for Hyundai and Tate, the latter known as 'one of the best loved brands in the world'.
Eusiun Chung, Vice Chairman of the South Korean chaebol, echoed the sentiment saying Hyundai wanted 'to be a brand that is loved by people the world over', marking art and cars as two traditional industries and using the metaphor of a needle and thread working in partnership.
Read more on the Tate and Tate Modern from Spear's
To mark the start of the new partnership, Hyundai has joined forces with Tate's Asia Pacific Acquisitions Committee to support a major acquisition for Tate's collection, dramatically improving the museum's holdings of art from Asia. The acquisition consists of nine key works by the renowned South Korean artist Nam June Paik (1932-2006).
Tate director Nicholas Serota was keen to emphasise that 'in no sense have any of the exhibitions at the Tate been determined by sponsorship', stating 'We've shown Korean artists here long before receiving this sponsorship from Hyundai and we will look across the world and we will always look independently of sources of finance.'
Read more on art and collecting from Spear's
Nonetheless, the acquisition of Nam Junes Paik's work as a direct result of Hyundai's sponsorship and the rhetoric from the Maria Miller will raise eyebrows.
However, Dercon was unapologetic: 'You're only good at finding private money if you have sufficient public money. The enthusiasm from corporate donors is incredible.
There are many different levels -it's not true that the corporates only come for David Bowie or Damien Hirst, they really want to be part of the Tate family, not just associate with art in terms of an artist's name.'
Fittingly the press conference moved along to the new jewel in the Tate Modern's crown as the world's most visited contemporary art space; the newly built bridge across the top of the Turbine Hall. Set to open in 2016, it has been designed by Herzog & de Meuron to join the existing galleries on level 4 of Tate Modern to the new building being developed to the south.
According to Serota this project will transform Tate Modern, with the Turbine Hall now being both the' literal' as well as the 'symbolic heart of the building'. The coming decade will reveal how Tate Modern interprets such new perspectives.
The Height of the Storm – theatre review
Monica Galletti's Mere review: 'full of life and sass and verve'
Elizabeth Day on miscarriages, mixed feelings and millennials – Spear's interview


Through situations, instruction, and questioning, Playmakers: The Player's Guide to Developing Basketball Intelligence demonstrates how to teach game awareness and basketball intelligence. Playmakers: The Player's Guide to Developing Basketball Intelligence explains the basic tactical skills of every offense — from pick-and-rolls to 3v2 fast breaks — but moves beyond the skill execution to the all-important perceptual, anticipatory and decision-making skills which separate the expert performers. Playmakers: The Player's Guide to Developing Basketball Intelligence teaches tactical skills, but also develops the characteristics of a high basketball IQ player — players who: • Choose the best option in less time; • Adapt to ever-changing situations; • Possess good spatial awareness; • Know the right play at any moment relative to the time and score; And more.


text:
Q: RestKit Response map issue - " = I am using rest kit 0.20.0. I have a request in JSON format which is like
{
  "CreateSession" : yes,
  "DistributionChannel" : "string1",
  "Login" : "string2",
  "Nickname" :"string3",
  "Password" :"string4",
  "PhysicalDevice" :
   {
     "DeviceId" : "string5",
     "DeviceTypeCode" : 123,
     "PhysicalDeviceTypeCode" : 1233,
    }
}

I did this
 NSDictionary * dictionary = @{
                            @"CreateSession":@"yes",
                            @"DistributionChannel":@"string1",
                            @"Login": @"string2",
                            @"Nickname":  @"string3",
                            @"Password":  @"string4",
                            @"PhysicalDevice":  @{ @"DeviceId":  @"string5",
                                                   @"DeviceTypeCode":  @"123",
                                                   @"PhysicalDeviceTypeCode": @"1233" }
                            };

    RKObjectMapping *registerDeviceRequestMapping = [RKObjectMapping requestMapping];
        [registerDeviceRequestMapping addAttributeMappingsFromDictionary:dictionary];

created descriptors for request and response separately. Added it to the RKObjectManager shared object,also have set base url and headers.
I called this to start request
RKHTTPRequestOperation *operation = [[RKObjectManager sharedManager] appropriateObjectRequestOperationWithObject:dictionary method:RKRequestMethodPOST path:@"RegisterDevice" parameters:nil];

    [operation setCompletionBlockWithSuccess:^(AFHTTPRequestOperation *operation, id responseObject) {
         NSLog(@"response   %@",[responseObject description]);

    } failure:^(AFHTTPRequestOperation *operation, NSError *error) {
         NSLog(@"Failed with error: %@", [error localizedDescription]);
    }];

        [operation start];

I get a 200 status but could not map values from response. The mapping result that I got is
<RKMappingResult: 0x849bf60, results={
    "<null>" = "<Response: 0x849b390>";

Tried several links but seems like none provides a good solution. The actual response that i need to map is
{
    "PhysicalDevice": {
        "AddDate": "string1",
        "AuthenticationKey": "string2",
        "DeviceId": "string3",
        "DeviceTypeCode": 33,
        "DeviceTypeName": "string4",
        "Id": 10130,
        "ModDate": "2013-09-27T07:21:34.240Z",
        "PhysicalDeviceTypeCode": 1233,
        "SerialNumber": "string5",
        "Status": 1,
        "StatusName": "string6"
    },
    "RemainingDeviceAssociations": 4,
    "SessionId": "string7"
}

Note: values in request and response are dummy values, but their structure is as given

A:
<RKMappingResult: 0x849bf60, results={
      "<null>" = "<Response: 0x849b390>";

This looks like a valid response. The response mapping provides you with a dictionary where the key is the key path and the response is your designated object. So, in this case the key is nil and your object is Response. And Response doesn't implement the description method so you just get the address.
You haven't shown your mappings or descriptors so I can't say more. You may be able to look at the contents of Response in the debugger...


text:
Q: Is it possible to set a sign-up quota per minute? I'm working on a project where users can sign in anonymously. But, I don't want malicious users to spam the login button. I only see an option in the Firebase console to set an hourly sign-up quota, but I need a per minute or per second quota to solve my issue. Is there any way to do this? Thanks!

A: What you see in the console is your only option.  Otherwise, your project is limited by what you see in the documentation.  Note that it doesn't cost you anything for Firebase to process a new anonymous signin.  If you want, you can write backend code using the Firebase Admin SDK to list and delete unused or suspicious accounts.
If you have a feature request, you can send those to Firebase support.


text:
… has a mind to stop living, and go shopping instead.
<voice imitation="professor_farnsworth">Good news, everyone!</voice>: Remy tells the story of Republicans who are Caring Again. About what?
The federal budget deficit was a record $3.1 trillion in fiscal year 2020, a three-fold increase over 2019. President Trump was able to accomplish that with help from Republicans in Congress, who stopped paying even lip service to fiscal austerity after Obama left office. With a Democrat about to return to the White House, expect GOP lawmakers to remember that—as it turns out—deficits do matter.
Lyrics (with explanatory links) at the link above.
At the Washington Examiner, Timothy P. Carney solves the election mystery. Except: It's no mystery: Millions of people voted specifically against Trump.
It's apparently a mystery to the Donald:
"Democrats suffered crushing down-ballot loss across America." @nytimes. This is true. All statehouses won, and in Washington we did great. So I led this great charge, and I'm the only one that lost? No, it doesn't work that way. This was a massive fraud, a RIGGED ELECTION!
And also to left-leaning columnists:
Thomas Edsall at the New York Times puzzles over his own mystery. "Honestly, This Was a Weird Election," is his headline, with his subheading puzzling that "Biden soared among crucial suburban voters. Democrats? Not so much."
What Edsall finds "weird" is that those same congressional districts tended to vote Republican this time around.
What is weird to Edsall and impossible to Trump has the same explanation (and Edsall, unlike Trump, understands it): Millions of voters find Trump uniquely awful, and they vote explicitly against him and not for a particular party or candidate.
The corollary to this story is that in 2016, Trump drew perhaps the only politician in the world as off-putting as he himself was: Hillary Clinton.
As someone who found both major party candidates (and as a one-armed paper hanger) I find this completely credible.
OK, here's another "as a one-armed paper hanger" link. As someone who's been, um, conversing with some conspiracy theorists at an ostensibly conservative blog, I'm in sympathy with Jonah Goldberg, who asserts Conspiracy Theories Are Incompatible With Conservatism. First, he notes that he doesn't like "You're not a conservative if…" arguments.
So why are conspiracy theorists different? Well, for starters, conspiracy theories are almost always offered in bad faith because they are non-falsifiable. The moment you provide evidence disproving a conspiracy theory, the response is invariably to resort to an even deeper conspiracy theory—or to accuse the debunker of being "one of them."
For instance, Attorney General Bill Barr, who has been far too loyal to the president throughout his tenure for my taste, recently told the truth: There's no evidence for the vast conspiracy theories Donald Trump has belched out to explain his election loss. The response from many of Trump's most ardent defenders was to insist Barr was in on the "deep state" plot to get Trump.
But the incompatibility of conservatism with conspiracy theories is more fundamental. One of the central tenets of conservatism is the idea that society is too complex to be easily controlled by a despot or even cadres of well-intentioned social engineers and bureaucrats, or what Edmund Burke, the founder of modern conservatism, dubbed "sophisters, calculators and economists."
I don't have any deep insights into conspiracy theorists, other than the ones you've seen from wiser folks than I. I'll admit it's difficult to keep a civil tongue in my head, though.
Joel Kotkin is a smart guy, and he writes on a red-meat topic at the Daily Beast: The Real Fascist Threat Was Never Trump—It's Corporate Power.
For four years America has shuddered watching Donald Trump, the poor man's Benito Mussolini, doing his Il Duce imitation. Certainly, Trump's timely political demise should be celebrated, but we cannot ignore a far bigger long-term threat to democracy—one that may be further accelerated by the new regime in Washington.
Under the kindly eyes of Uncle Joe, we soon may find ourselves living under an updated version of the fascist "corporate state"— an alliance between political leaders and a handful of ultra-rich, ultra-powerful companies that increasingly dominate the economy and culture. This new American-style corporate state reflects not a conspiracy but the politics of a society with unprecedented concentrations of wealth and power.
I agree halfway: partnerships between big government and big business do not work out to my benefit, and probably not to yours either.
I will note that yesterday's "ultra-rich, ultra-powerful companies" are not today's. (See Mark J. Perry: Only 51 US companies have been on the Fortune 500 since 1955, thanks to the creative destruction that fuels economic prosperity). Kotkin writes as if things are different today.
He could be right, that this time Walmart/ExxonMobil/Apple/etc have figured out a way to live forever at the top. I have my doubts.
If you're not worried about corporate fascism, maybe James D. Miller at Quillette will get you concerned about another menace: The Apocalyptic Threat from Artificial Intelligence Isn't Science Fiction. After Miller provides a deepfake example…
While [deepfake] technology may create a bit of social havoc, the truly massive disruption will occur when AIs can match or exceed the thinking power of the human brain. This is not a remote possibility: Variants of the machine-learning AIs that today generate fake pictures have a good chance of creating computer superintelligences before this century is out.
These superior beings could be applied to wonderful purposes. Just this week, for instance, it was announced that the AI system AlphaFold has been recognized for providing a solution to the so-called "protein folding problem," which holds implications for our fundamental understanding of the basic building blocks of human biology. If, however, mankind releases smarter-than-us AI before figuring out how to align their values with our own, we could bring forth an apocalypse instead. Even the Pope fears the destructive potential of AI, and he is right to do so.
Yeah, well, maybe. Steven Pinker devoted a section of his recent book Enlightenment Now to the AI "existential threat" and was complacent about it. For now, I'm leaning that way too, but Miller's take is nonetheless interesting. See what you think
The Stranger Diaries
The second book on my Edgar Award Nominees reading project.
Clare Calloway is a divorced English (as in subject) teacher in an English (as in Great Britain) high school. The school inhabits the old mansion of Gothic horror writer R. M. Holland; in her spare time, Clare is researching Holland's strange life, working on a book project. The school is said to be haunted by the ghost of Holland's wife, who committed suicide by throwing herself down the stairs. Ouch!
But one of Clare's friends and co-workers, Ella gets murdered. And it seems the killer has aped one of the murders in Holland's most famous story.
And then Clare finds that somebody—or something?—has been writing in her diaries: "Hallo, Clare. You don't know me." Oh oh.
The book uses multiple first-person narrators, a technique cutely adapted from Wilkie Collins' The Woman in White. In addition to Clare, there's the police Detective Sergeant assigned to the case, Harbinder Kaur, a lesbian Indian lady. And Clare's precocious daughter, Georgia. It's amusing to see how their perceptions of each other clash.
There's a lot of spookiness and dread, as appropriate for a Gothic-related novel. And a very good dog.
The Power of Bad
How the Negativity Effect Rules Us and How We Can Rule It
The Dewey Decimal Code on this book's spine is "158.1", which is "Self Help". I don't usually get self-help books. Haven't read one on purpose since I was in my twenties, I think.
But this one has back-cover blurbs from P. J. O'Rourke, Steven Pinker, Greg Lukianoff and Jonathan Haidt. That shouts out "Read this!" to me. And one of the authors, John Tierney, is a constant source of good stuff at City Journal. So I checked it out. Good move.
The cover is a little gee-whiz, but the premise of the book is provided by a couple pithy sentences right there on page 11:
To survive, life has to win every day. Death has to win just once.
This is a lesson pounded into our genes by billions of years of evolution. We are hardwired to appreciate its truth. This book goes into the broad implications of that "negativity effect". There's a rough rule of thumb: Homo sap. requires the perception of four "good things" to counterbalance one perceived "bad thing". This can lead to irrational, sometimes self-destructive behavior. Writ large, it can cause organizations to stifle innovation and forego valuable opportunities. Writ very large, it can cause an entire society to become overly risk-averse.
But we can learn better, and the book explores possible pathways in numerous scenarios. Some surprising: for example, there's an entire chapter on how a New York hotel deals with negative Trip Advisor reviews. But (for me) the payoff chapter was the public policy chapter. The authors set forth some assumptions:
The world will always seem to be in crisis.
The crisis is never as bad as it sounds.
The solution could easily make things worse.
Covid, anyone? Unfortunately the book was written before that. The authors tick off the implications: The "Golden Age Fallacy" that posits some past era as ideal, our current age in irrevocable decline; terrorism; vaping; the war on drugs; technophobia. And more.
Of course, people can make money and/or gain political power off the negativity effect. Plenty of examples of that too.


I witnessed this champion of men!
My Dad and I were late arriving at the ballpark.
When we arrived, it was the bottom of the first.
field bleachers, the crowd was cheering wildly!
Jackie Robinson was stealing home!!!
This image is ingrained in my memory!
Ah, the world traveler has returned... welcome my good friend!
Oh such a wonderful poem and story Jack! Buckets of love your way <3 xomo!


She's never been afraid to play around with fashion.
And Ruth Wilson cut a striking figure on Monday as she attended the AMC Network Summit in New York City to promote her role in His Dark Materials.
Ruth Wilson talks "The Little Stranger," leaving "The Affair"
Ruth Wilson: "I Think I'm Quite Evil"
Hedda Gabler, A Passage to India, and no ice.
Stephen and Ruth strike a blow for equality but showing their \"I just found $20\" faces.


text:
Diversity Inclusion
Toggle Section Menu About Us
Diversity & Inclusion on Campus
Building a Campus Culture of Diversity and Inclusion
VWU Non-Discrimination Statement
Academic Diversity
President's Council for Inclusive Communities
Preferred Name/Pronoun
Trans* Policy
First-Generation Students
Virginia Center for Inclusive Communities
Office of Gender and Sexuality Equity
Institutional Statement
Dear Campus and Coastal Virginia Community:
Whoever you are, and wherever you come from, we welcome you warmly to our campus.
College years need to be times of growth, when we are exposed to new ideas, in conversation with different perspectives, and learning to understand, appreciate, and value others. That doesn't happen unless we celebrate diversity. We grow in important ways through the many viewpoints that come from our differences from each other, whether those differences relate to race, gender, age, and language, or to other differences that may be more subtle, like socioeconomic status, religion, sexual orientation, gender expression, gender identity, political affiliation, or geographical background.
Virginia Wesleyan does not discriminate on the basis of race, religion, color, creed, gender, national or ethnic origin, age, marital status, covered veteran status, disability, sexual orientation, gender identity and expression, or any other legally protected status in administration of its educational policies, admission policies, scholarship and loan programs, and athletic and other University-administered programs.
Critical to the identity we embrace is our going beyond mere legal expectations. VWU's Strategic Plan lays out the importance of diversity on the campus by advocating for a more diverse undergraduate population and a more diverse faculty and staff. We try to be leaders in the area of diversity and inclusion for Coastal Virginia. In 2018, for instance, Virginia Wesleyan became the first higher education institution in the region to expand our statement on non-discrimination to include gender identity and gender expression.
Finally, we believe that we must always work and strive to deepen our understanding and sensitivity regarding all perspectives surrounding diversity. As a residential campus, we provide our students the ability to practice living, learning, and collaborating with others in an environment that is both challenging and supportive in all aspects.
With you, I look forward to advancing Virginia Wesleyan University's commitment to building a more diverse and inclusive community. The differences of each community member are what make Virginia Wesleyan even stronger.
Scott D. Miller, Ph.D.
President of the University


Main Title: Lilydale Lawn Cemetery [electronic resources] : Memorials & Index of Names / Memorials transcribed and names indexed by volunteers of The Genealogical Society of Victoria Inc.
Imprint: [Melbourne], Victoria Genealogical Society of Victoria Inc., 2014.
Collation: 1 CD-ROM ; 12 cm.
Historic White Hills Cemetery, Bendigo [electronic resource] : monumental inscription photographs, compiled 2004-2005 / by Tom and Libby Luke.
A tour of the Lilydale Cemetery 1861-1994 : volume one / compiled by Sandy Ross.
No tombstones : unmarked graves at Lilydale Cemetery volume one / compiled by Sue Thompson, Lorraine Smith, Val Sheehan and Myrna McBain.
Bendigo Cemetery [electronic resource] : photographs and burial list / compiled by Pat and Ian Belmont.
The burials at Sale War Cemetery [electronic resource] : their service histories and those others who died in their RAAF service at East & West Sale 1942-1945 / Squadron Leader Stuart J Lawson RAAF (Ret'd).
Cemeteries of South West Victoria : release 9.1 [electronic resource] / Ian Marr.


text:
\section{Introduction}
OAuth 2.0~\cite{oauth} has received widespread adoption and it is considered the industry-standard protocol for authorization. OAuth~2.0 enables delegation and interoperability, it enhances end-user security, and it facilitates access control management. Due to its intriguing properties, it is being used in environments with higher security requirements than initially considered, such as IoT systems, Open Banking, eHealth, eGovernment, and Electronic Signatures~\cite{Lod2019}.

In a nutshell, OAuth 2.0 constitutes the protocol through which an
\emph{client} obtains an \emph{access token} from an \emph{authorization server}, to access a protected resource, stored in a \emph{resource server}. However, OAuth~2.0  specification does not define how an access token is generated, validated, and destroyed; instead it leaves the management of OAuth~2.0 tokens' lifecycle as an open design choice.

In this paper, we propose a new type of token, which is protected using proof-of-possession keys and at the same time it supports auditing and accountability, fast revocation, and added-value services. In order to achieve our goal, we build on the emerging distributed ledger technology (DLT). Our solution considers an append-only distributed ledger (public or private), where users, identified by a public key, can transact \emph{uniquely identified tokens}. Our implementation is based on the Ethereum blockchain and the ERC-721 token specification (but other similar technologies can be considered). Our system leverage Ethereum's support for distributed apps (referred to as \emph{smart contracts}) to build blockchain-based token management services. The proposed solution has the following advantages:
 \begin{itemize}

    \item The entity that generates access tokens (i.e., the authorization server) can easily revoke them before they expire. Furthermore, token revocation does not involve any interaction with the client or the resource server, hence it can be implemented even if these entities are offline/unreachable. Similarly, a resource server can verify the validity of a token (i.e., it has not been revoked) even if the authorization server is offline, since token revocation is recorded on the DLT through a transaction that can occur at any time prior to the token's usage.
    \item Clients do not have to store their tokens locally, neither do they have to store any secret associated with their access tokens. Instead, all tokens can be retrieved form the ledger. Hence, tokens are portable and can be easily used by multiple client devices. Furthermore, since we are using a popular token specification, a wide range of ``wallets'' and libraries can be supported by our system.
    \item Token integrity and authenticity can be verified simply by performing a lookup in the ledger, and it does not involve any signature verification or any other cryptographic operation. Therefore, our solution is less prone to implementation errors, and tokens are simpler since the do not carry any cryptographic proof. Furthermore, token ownership can be securely modified without any interaction with the authorization server.
    \item All tokens, including the revoked ones, are immutably stored in the ledger, hence auditing and accountability mechanisms are facilitated.
 \end{itemize}

The feasibility of our solution is verified through a proof-of-concept implementation, inspired by an IoT gateway access use case. The remainder of this paper is organized as follows. In Section~\ref{sec:back}, we introduce OAuth~2.0 and ERC-721 tokens. In Section~\ref{sec:sys} we present the design of our system, and in Section~\ref{sec:tok} we detail the provided token management services. Finally, we present our implementation and its evaluation in Section~\ref{sec:eval}, and we conclude in Section~\ref{sec:conc}.

 \section{Background and related work}
 \label{sec:back}
 \subsection{OAuth 2.0}
 \label{sec:oauth}
 OAuth 2.0 systems are composed of the following entities. A \emph{resource server} that hosts a protected resource owned by a \emph{resource owner}, a \emph{client} wishing to access that resource, and an \emph{authorization server} responsible for generating \emph{access tokens}. Access tokens are granted to clients authorized by the resource owner: client authorization is proven using an \emph{authorization grant}. These interactions are illustrated in Fig.~\ref{fig:oauth}. As it can be seen in this figure, a client first requests an authorization grant from the resource owner, then it uses this grant to obtain an access token from the authorization server, and finally, it uses the access token to access the protected resource stored in the resource server. The semantics, as well as the mechanisms for generating and validating access tokens and grants are transparent to the OAuth~2.0 protocol.

 \begin{figure}
    \centering
    \includegraphics[width=0.8\linewidth]{oauth-crop.pdf}
    \caption {OAuth~2.0 interactions.}
    \label{fig:oauth}
\end{figure}

 Each OAuth~2.0 deployment may choose the type of token it will use. The most commonly used type of token is the \emph{bearer} token~\cite{Jon2012}, which can be used by any user who possesses it (i.e., the ``bearer'').  For additional security, a token can be associated with a secret key, so that only users who can prove that they possess this key can use the token. Since the latter type of tokens provides more security (at the cost of the communication overhead required to verify ownership) it is considered by our solution. In particular, our constructions are based on JSON Web Tokens (JWTs)~\cite{Jon2015} enhanced with blockchain-based proof-of-possession mechanisms.

 A JWT is a compact, URL-safe means of representing ``claims.'' It consists of  zero or more name/value pairs, and it is transmitted encoded in base64url~\cite{rfc4648}. RFC 7519 defines some ``standard'' claim names and their semantics. Table~\ref{table:jwt} contains the names, and the corresponding semantics, of the JWT claims used by our solution.

 \begin{table}[h]
    \centering
    \caption{JWT claims used in our system}
    \begin{tabular}{ | l | p{3cm} |}
    \hline
    \textbf{Name} & \textbf{Semantics} \\ \hline
       \texttt{iss} &  The issuer of the token \\ \hline
       \texttt{sub} &  The subject of the token, i.e., the entity that will use the token to gain access to a resource \\ \hline
       \texttt{aud} &  The audience of the token, i.e., the the recipients that the JWT is intended for  \\ \hline
       \texttt{exp} &  The expiration time on or after which the JWT must not be accepted for processing \\ \hline
       \texttt{jti} &  A unique token identifier \\ \hline
    \end{tabular}

    \label{table:jwt}
\end{table}

\subsection{Ethereum and ERC-721}
\label{sec:eth}
Ethereum~\cite{Wood2014} is a popular blockchain system that supports distributed applications, known as ``smart contracts''. A smart contract is executed by all ``peers'' in the Ethereum network and its outcome is agreed upon consensus. Users interact with a smart contract by issuing ``transactions,'' which are signed by a user-specific key. A hash of this key is used as the user ``address'' and it is used for associating users with information stored in the blockchain. All transactions are immutably recorded in the blockchain, for this reason blockchain-based solutions are ideal for implementing auditing and accountability mechanisms. Furthermore, a smart contract can create an ``event''. Events are also recorded in the blockchain and end-user applications can be configured to ``listen'' for specific contract events.

Ethereum community is developing ``Ethereum Request for Comments'' (ERC), which the equivalent of RFC but for smart contract.
ERC-721\footnote{https://eips.ethereum.org/EIPS/eip-721}, is an open standard that describes how to build ``non-fungible or unique tokens on the Ethereum blockchain.'' This standard is very similar, in many ways, to ERC-20\footnote{https://eips.ethereum.org/EIPS/eip-20}, which probably the most popular Ethereum standard and it is used for creating custom Ethereum tokens. However, in contrast to ERC-20 tokens, ERC-721 tokens are ``unique'' and non-interchangeable with other tokens (non-fungibility). Many Ethereum wallets, such as Metamask\footnote{https://metamask.io/}, can handle these tokens. All ERC-721-based tokens are identified by a unique identifier (we will refer to this identifier as $token_{id}$), and they can be owned only by a single user.

This standard, like every other token standard in Ethereum, defines some functions that a smart contract should implement in order to be able to create and handle ERC-721 tokens.
Furthermore, the ERC-721 metadata extension, defines some additional functions that can be used for associating an ERC-721 token with metadata.
Table~\ref{table:erc} describes the functions defined in ERC-721 and in ERC-721 metadata extension, used by our system.

\begin{table}[h]
    \centering
    \caption{ERC-721 and ERC-721 metadata extension functions used in our system}
    \begin{tabular}{ | l | p{3cm} |}
    \hline
    \textbf{Name} & \textbf{Purpose} \\ \hline
      \texttt{ownerOf($token_{id}$)} &  It accepts as input a $token_{id}$ and returns the address of the token owner \\ \hline
      \texttt{transferFrom(from, to, $token_{id}$)} &  It transfers a  $token_{id}$ from one Ethereum address to another\\ \hline
      \texttt{approve(address,$token_{id}$)} &  It approves an Ethereum address to manage a $token_{id}$ on owner's behalf \\ \hline
      \texttt{getApproved($token_{id}$)} &  It retrieves the Ethereum address that is allowed to manage $token_{id}$\\ \hline
      \texttt{tokenURI($token_{id}$)} &  It accepts as input a $token_{id}$ and returns a URI that point to token's metadata \\ \hline
     \end{tabular}

    \label{table:erc}
\end{table}

Additionally,  functions \texttt{transferFrom} and \texttt{approve}, when invoked each generates an event, named \texttt{Transfer} and \texttt{Approval} respectively. Both these events have three attributes; the attributes of the \texttt{Transfer} event are the $from$ address, the $to$ address, and the $token_{id}$, while the attributes of the \texttt{Approval} event are the owner address, the approved address, and the $token_{id}$.

\subsection{Related work}
Many recent research efforts investigate Blockchain-based access control, either by defining custom blockchain systems (e.g., \cite{Dor2017}) or by using Ethereum smart contracts for recording policies and for implementing on-chain access control decisions (e.g., \cite{Ham2018, Nov2018, Zha2019,Ali2019, Mae2019}). Our solution does not rely on smart contracts for implementing access control decisions (which may cause privacy issues), instead it uses the ledger for storing auxiliary information used for validating OAuth~2.0 access tokens.

The work in this paper is related to our previous work published in~\cite{Fot2018,Lag2019,Sir2019}. However, in these papers we considered constrained devices not capable of accessing the blockchain. In this paper we relax this assumption and we consider resource servers capable of reading values from the blockchain (resource servers are not required to ``write'' in the blockchain); even with read-only access we can implement constructions that were not possible with our previous work, including revocation, and delegation.

\section{System design}
\label{sec:sys}
Our system considers a typical OAuth~2.0 architecture (such as the one described in section~\ref{sec:oauth}). Therefore, the main entities of our system are \emph{clients}, \emph{authorization servers}, \emph{resource servers}, and \emph{resource owners}.  From a high-level perspective, our system operates as follows. The client requests an access token from the authorization server, using an authorization grant received by the resource owner. The authorization server validates the authorization grant of the client, generates a JWT and an ERC-721 token, transfers the ERC-721 token to the Ethereum address of the client, and transmits the JWT to the client. Then, the client requests access from the resource server, providing the JWT. The resource server retrieves the corresponding ERC-721 token which is used for verifying the validity and the ownership of the JWT: if all verifications are successful the resource server allows the client request. This process is illustrated in Figure~\ref{fig:overview}.

\begin{figure}
    \centering
    \includegraphics[width=0.8\linewidth]{overview-crop.pdf}
    \caption {Overview of our system}
    \label{fig:overview}
\end{figure}
\subsection{Notation and security assumptions}
In our system, resources are uniquely identified by a URI, referred to as the $URI_{resource}$. We assume a security mechanism with which a resource server can prove that it hosts a specific $URI_{resource}$ (e.g., using an X.509 certificate). Henceforth, when we say that ``a client requests $URI_{resource}$ from a resource server'' it is assumed that the client has already verified $URI_{resource}$ ownership. Moreover, the communication between a client and a resource server takes place over a secure communication channel.

In our system each authorization server owns an ERC-721 contract, referred to as $Contract_{AS}$; we detail these smart contracts in the following section. Moreover, we assume a security mechanism
 with which clients and authorization servers can securely communicate; this mechanism provides confidentiality and integrity protection of the exchanged messages, as well as authorization server authentication. Furthermore, resource owners trust authorization servers to behave according to the specified procedures.

Finally, each client owns a public key $P_{Client}$, and a corresponding private key, used for transacting with the Ethereum blockchain. Again, we consider a security mechanism with which $P_{Client}$ ownership can be verified.

\subsection{The ERC-721 contract}
ERC-721 contracts in our system are implemented such that only the contract owner can create new tokens. When a token is created its $token_{id}$ and $metadata$ are specified: these two properties are read-only and they cannot be modified. Moreover, token owners in our system \emph{cannot transfer their tokens}; the only entity that can invoke the \texttt{transferFrom} method is the contract owner. Moreover, when invoking the \texttt{transferFrom} method, the contract owner is allowed to transfer any token, no matter who the token owner is.

The ERC-recommended approach for associating a token with some metadata is through the metadata extension, which provides a method that maps a $token_{id}$ to a URI where metadata are stored (i.e., \texttt{tokenURI}). Nevertheless, we postulate that this approach violates both the decentralization and immutability principles of DLTs, since with this approach the metadata file is stored in a centralized location, and it can be modified without being possible to track or even detect the changes. For this reason, in our system, metadata are encoded in a JWT and the base64url representation of the JWT is stored in the contract: this is the return value of the \texttt{tokenURI} method. Therefore, in our system, the metadata extension is used to retrieve the metadata themselves and not a URI that points to the metadata.

\subsection{Setup}
During setup, resource owners configure their resource servers with $Contract_{AS}$. Moreover, clients ``register'' with the authorization server.\footnote{This registration step is also assumed by the OAuth protocol.} During this registration process, which is out of the scope of this paper, the authorization server learns the Ethereum public key of the client (i.e., $P_{Client}$). In cases where this registration process cannot take place a priori, solutions such as the OAuth~2.0 dynamic client registration protocol~\cite{rfc7591} can be considered.

Additionally, prior to any other operation, each client obtains from the resource owner an authorization grant (the  format of this grant and the mechanisms for generating it are out of the scope of this paper). This grant represents a resource owner's authorization, and is used by a client to request an access token for a specific $URI_{resource}$.

\subsection{Access token request}
A client, that owns $P_{Client}$, requests from an authorization server an access token for a protected resource $URI_{resource}$, including in the request the authorization grant received during the \emph{setup}. The authorization server verifies $P_{Client}$ ownership and grant validity (using protocols out of the scope of this paper). Then, the authorization server creates a JWT which contains the following claims:
\begin{minipage}{\linewidth}
    \begin{lstlisting} [caption={The generated JWT},label={list:jwt}]
{
    ``iss'': ``$Contract_{AS}$'',
    ``sub'': ``$P_{Client}$'',
    ``aud'': ``$URI_{resource}$''
    ``jti'': ``$token_{id}$''
    ``exp'': ``expiration time''
}
    \end{lstlisting}
\end{minipage}

As a next step, the authorization server creates an ERC-721 token. The $token_{id}$ of this new token matches the value specified by the \texttt{jti} claim of the JWT. Moreover, the metadata of the token is set equal to the base64url encoding of the JWT. Finally, the authorization server invokes the \texttt{transferFrom} method of the ERC-721 contract to transfer the created token to $P_{Client}$, and sends the generated JWT back to the client. It should be noted that the client does not have to store the JWT: at any time it can retrieve all the tokens it owns from the ERC-721 contract, and extract the corresponding JWT from a token's metadata.

\subsection{Resource access request}
In order for a client to access a protected resource, it sends to the resource server a request that includes the received JWT. The resource server performs the following steps:
\begin{enumerate}
\item It examines: (i) if it ``knows'' the $Contract_{AS}$  included in the \texttt{iss} claim of the JWT (i.e., if it has been configured with this contract address), (ii) if the $URI_{resource}$ included in the \texttt{aud} claim of the JWT matches the URI of the requested resource, and  (iii) if the token is still valid (i.e., it has not expired).
\item It executes the \texttt{ownerOf} method of $Contract_{AS}$, providing as input the $token_{id}$ included in the \texttt{jti} claim of the JWT, and examines if the returned address corresponds to $P_{Client}$ included in the \texttt{sub} claim of the JWT.
\item It executes the \texttt{tokenURI} method of $Contract_{AS}$, and examines if the returned string is the same as the received JWT.
\end{enumerate}
At this point, the resource server is able to attest the integrity of the received JWT (since it is the same as the metadata of the token stored in the blockchain), as well as its validity. As a next step, the resource server verifies that the client is the real owner of $P_{Client}$. If all verifications succeed, the resource server accepts the client's request.

Additionally, a resource server may store a valid JWT locally, create a \emph{session identifier}, and send this identifier to the client: the client may use this identifier, as long as the JWT is still valid, accelerating this way subsequent requests for the same resource.
 \section{Token management services}
 \label{sec:tok}
 \subsection{Revocation}
 Tokens usually carry an expiration time: OAuth~2.0 and JWTs specifications do not provide any mechanism that allows an authorization server to revoke an access token prior to its expiration time. Even ``OAuth 2.0 token revocation RFC~\cite{rfc7009},'' specifies  a mechanism that allows ``\emph{clients} to notify the authorization server that a [...] access token is no longer needed,'' i.e., a mechanism that provides a ``log out'' functionality rather than revocation.

 In our system, tokens can be revoked by an authorization server by invoking the \texttt{transferFrom} method of the ERC-721 contract and transferring a token back to the authorization server.\footnote{It is reminded that authorization servers are the contract owners, and contract owners in our system are allowed to transfer any token, no matter who the token owner is.} We consider two cases: (i) the corresponding JWT has not been used by the client by the time of the revocation, and (ii) the corresponding JWT has been used, it has been stored locally by the resource server, and it has been associated with a session identifier. In the former case, when a client tries to use the JWT the verification process will fail, since the output of the \texttt{ownerOf} method will not match the $P_{Client}$ included in the \texttt{sub} claim of the JWT, hence the resource server will reject the JTW. In the latter case, the resource server must ``listen'' for the events emitted by the \texttt{transferFrom} method; if an event contains a $token_{id}$ included in an already stored JWT, the resource server must delete the JWT and the associated session identifier. It should be noted that events are immutably stored in the blockchain, hence if a resource server is offline for some time, it can easily recover all missed events.

 \subsection{Delegation}
 There can be cases where a client does not wish to authenticate to the resource server using $P_{Client}$, e.g., $P_{Client}$ may be stored in a secure, offline storage place, or a user may want to temporary use another device that does not have access to $P_{Client}$ (for example a user may want to use different devices while travelling). For these cases, our system allows a token owner to delegate an access token to another Ethereum address. The token does not change ownership, and the latter address is not allowed to further delegate the token. We implement this functionality by using the \texttt{approve} method of the ERC-721 contract and the ``proof-of-possession key Semantics for JWTs'' defined in RFC 7800~\cite{Jon2016}. RFC 7800 defines a ``confirmation'' (\texttt{cnf}) claim, which contains the key of the owner of a JWT. Delegation of a $token_{id}$ is implemented as follows: $P_{Client}$ invokes the \texttt{approve} method providing as input $token_{id}$ and the Ethereum address associated with the public key of the delegee $P_{Delegee}$. Now $P_{Delegee}$ can use this token by constructing a JWT and by adding $P_{Delegee}$ in the \texttt{cnf} claim as illustrated in listing~\ref{list:jwt}.

 \begin{minipage}{\linewidth}
    \begin{lstlisting} [caption={JWT with delegation enabled. cnf stands for ``confirmation''},label={list:jwt}]
{
    ``iss'': ``$Contract_{AS}$'',
    ``sub'': ``$P_{Client}$'',
    ``aud'': ``$URI_{resource}$''
    ``jti'': ``$token_{id}$''
    ``exp'': ``expiration time''
    ``cnf'':
    {
        ``kid'': ``$P_{Delegee}$''
    }
}
    \end{lstlisting}
\end{minipage}

The \texttt{cnf} claim is not recorded in the ERC-721 token's metadata, since metadata are read-only. For this reason, when $P_{Delegee}$ performs a resource access request, Step 3 of token integrity verification is modified as follows. It should be noted that when a token is revoked, the delegee can not use it.

\begin{enumerate}
    \setcounter{enumi}{2}
    \item The resource server executes the \texttt{tokenURI} method of $Contract_{AS}$, and examines if the returned string is the same as the received JWT \textbf{excluding the cnf claim}.
\end{enumerate}

Then, JWT ownership is verified as follows: the resource server executes the \texttt{getApproved} method of the ERC-721 contract, providing as input $token_{id}$, and examines if the return value equals to the Ethereum address associated with $P_{Delegee}$; finally, it challenges client to verify $P_{Delegee}$ ownership.

The delegation process does not involve the resource owner, neither the authorization server.
\subsection{Fair exchange}
Smart contracts are ideal for performing ``fair exchange'' of digital goods~\cite{Dzi2018}. In our previous work, published in~\cite{Sir2019}, we used smart contracts to exchange an access token for money. In a nutshell, with the solution presented in~\cite{Sir2019} the authorization server encrypts a token, the client ``deposits'' some money in the form of escrow, and the server receives the escrow only if it reveals the ``correct'' decryption key. The problem with this approach is that it does not provide any guarantee that the decrypted plaintext is a valid access token.

With the solution presented in this paper this problem is solved as follows: the authorization server creates the ERC-721 token, and stores it in the ERC-721 smart contract by ``indicating'' a $P_{Client}$; the contract transfers the token to $P_{Client}$ only when the latter performs an action (e.g., pay a pre-specified amount of money). The advantage of this approach is that the client can inspect the token before performing any action; of course the client cannot use the token, before performing the specified action, since up until this point, the client does not own the token.

\section{Implementation and Evaluation}
\label{sec:eval}
\subsection{Implementation}
We have developed a proof of concept implementation of the presented solution. We considered the case of an IoT gateway access, the owner of which wishes to grant access to guest users. As an IoT gateway we used Mozilla's WebThings Gateway\footnote{https://iot.mozilla.org/gateway/} that implements the WoT standard~\cite{wot}. For our proof of concept, we chose not to modify the gateway itself, instead, we have developed an application that acts as a proxy, between the client, the blockchain, and the gateway (that holds the role of the resource server).

As an Ethereum wallet, we used the Metamask Firefox extension, which can handle
ERC-721-based tokens. We implemented clients as JavaScript web applications using web3.js
Ethereum JavaScript API.\footnote{https://web3js.readthedocs.io/}

The main component of our proposed system is the smart contract that implements the functions of the ERC-721 interface. The smart contract was developed using Solidity\footnote{https://solidity.readthedocs.io/en/v0.5.6/},
which is a Turing-complete programming language for implementing smart contracts. In addition to the functions included in Table~\ref{table:erc} we implemented two functions that are not defined in the ERC-721
interface. The first one, named \texttt{mint}, is for creating new tokens, and the other, named \texttt{burn}, for ``burning'' tokens, i.e., for destroying them. These functions, as well as the \emph{transferFrom} and \emph{approve} functions, can only be invoked by the smart contract owner.

\subsection{Performance and Cost Evaluation}
We have tested our proposed system in the Rinkeby Ethereum test network\footnote{https://www.rinkeby.io/}. We chose a public test network rather than a private one in order to have more reliable results.

The actions of our system that involve the invocation of the smart contract functions, create some computational overhead. Gas is Ethereum's unit for measuring the computational and the storage resources required. Each operation of a smart contract costs a fix amount of gas. Gas cost is the number of units of gas required to perform an action, while gas price is the amount of ``ether'' (i.e., Ethereum's specific coin) a client is willing to pay per unit of gas. The average price of a unit of gas\footnote{As measured by https://ethgasstation.info on 30 Dec. 2019} is \$$0.011 \times 10^{-4}$. Table~\ref{table:ev} shows the cost of deploying the smart contract in the blockchain network, as well as the cost of operations performed by our system in terms of gas units.

\begin{table}[h]
    \centering
    \caption{Cost of our construction building blocks}
    \begin{tabular}{ | l | c |}
    \hline
    \textbf{Operation} & \textbf{Cost measured in gas} \\ \hline
      Contract Deployment  &     1585444                      \\
      Create a token  &         254141                    \\
      Burn a token  &           85791                 \\
      Transfer a token  &      63858                       \\
      Approve           & 45735           \\ \hline
    \end{tabular}
    \label{table:ev}
\end{table}

In addition to gas, Ethereum adds an execution time overhead related to the time the Ethereum network needs to generate a new block. On average, an operation in Ethereum is executed in $\sim$13 seconds.

Some of the aforementioned functions are declared as \emph{view functions}. That is, they only \emph{read} state of the blockchain without modifying it. Thus, they incur no cost, delay, or overhead. These functions are: \texttt{tokenURI}, \texttt{getApproved}, and \texttt{ownerOf}.

\subsection{Discussion}
\textbf{Privacy considerations.}
With our solution, an authorization server does not have to be aware of the resource server, i.e., they never have to communicate directly, not even in the case of a token revocation. The authorization server learns only the $URI_{resource}$ that a client wants to access, but this does not have to be the real URI of the resource: any pseudonym that the resource server can understand can be used instead. On the other hand, the metadata of an ERC-721 token are immutable and visible to anybody, constituting a privacy threat. In order to enhance clients' privacy metadata can be encrypted using a key known only to the resource owner, to the client, and to the resource server.

\textbf{Authorization server key breach.}
In order to enhance the security of our solution we specify that some functions of the ERC-721 contract can only be executed by the contract owner, i.e., the authorization server. Of course, if the private key the authorization server used for deploying the contract is compromised then, the security of our system is jeopardized and a new contract has to be deployed (which requires re-configuration of the resource servers). For this reason, a realization of our system may consider two different keys: one for invoking the security critical functions of the smart contract, and another for specifying which is the former key. The latter key can be the one used for deploying the contract and can be securely stored offline.

\textbf{Approving other types of identifiers.} ERC-721 specifications define that with the \texttt{approve} method a token owner can specify another Ethereum address that can manage its token. However, in our system a delegee never interacts with the blockchain, therefore the input to \texttt{approve} does not have to be an Ethereum address. Other types of delegee identifiers can be considered, such as legacy public keys, or even contemporary forms of authentication such as verifiable credentials~\cite{ver}.

\section{Conclusions}
\label{sec:conc}
In this paper we presented the design and implementation of an OAuth~2.0 authorization token, backed by blockchain-based smart contracts. Our solution uses Ethereum to store information that can be used for auditing purposes, as well as for token integrity verification. Ethereum smart contracts facilitate revocation, decouple authorization and resource servers, enable token delegation, and create opportunities for exchanging tokens with fungible assets. We believe that our work can be extended towards many directions, including the use of permissioned ledgers, token validation using conditions stored in the ledger, privacy-preserving token representations, and the application of similar mechanisms for managing authorization grants.

\bibliographystyle{IEEEtran}

redpajama_set_name: RedPajamaArXiv


Be it at office or even while at home, you always have to make sure that everything can be clean at all times, this will always get to give you a serene environment at all times, which will mean that you can always be able to know what it is that might or can get to work to your advantage, this will make sure that you can figure out what it is that can be of some assistance to you or even make sure that you can gain all that you might need.
Therefore, when looking for means of making sure that you can have a clean place, you have to make sure that you can be focused on who or even the service provider to attain, this will ensure that you have been able to find the best available, furthermore, you will have a means to making sure that you can be ale also to gain everything which you might be looking for.
Therefore, you will find that when looking for naplesfl house cleaning service provider, there can be lots of things which you can attain, which will mean that, you can know what it is that might get to work to your advantage; furthermore, you will have a means to make certain that everything which you can or might get to do can work to your advantage at all times, something which will indeed make sure that you can gain all that you might be looking for.
Furthermore, you have to know of the considerations which you have to make when looking for cleaning services, which will mean that, you can be able to find the best available and also that you can know of all that might be and can be appealing to you, thus the first consideration at all times being their location, you have to make sure that they can be within your city thus being able to conduct the services in no time. To understand more about professional cleaning services, visit http://www.ehow.com/how_8259301_write-bids-commercial-cleaning-jobs.html .
In the long run, your assessment can be made easier when using the internet, meaning that, you will be able to know what it is that might be of some assistance; likewise, you can have a clue as to what might be helpful to you, since, with the internet, it will be easier to conduct a comparison.


Notification method executed whenever the groupState of this grid changes.
Notification method executed whenever the groupState of this grid changes. Group state is accessible via getGroupState(), and contains group state information.


Diflucan is an antifungal antibiotic. The mechanism of its action lies in killing sensitive fungi by interfering with the formation of the fungal cell membrane. Diflucan also helps to prevent to prevent fungal infection in people with weak immune systems as a result of cancer treatment, bone marrow transplant or AIDS.
In some cases Diflucan pills can be used for people who received bone marrow transplants in order to prevent the appearance of candidiasis or used for treatment of meningitis. It is also can be prescribed for fungal infections in kidney and liver transplant patients and fungal infections in patients with AIDS.
Take Diflucan strictly following doctor's directions. Do not take Diflucan pills in larger dosage and longer than it is recommended by your doctor.
• Take Diflucan orally with or without food.
• You have to take Diflucan two hours before proton pump inhibitors.
• Take Diflucan during the full course of therapy in order to kill the infection completely. Do not stop taking Diflucan even if you feel improvement in few days.
• It is recommended to take Diflucan regularly at one and the same time.
• In case of skipping a dose, take it as soon as possible. If it is time for the next dose, skip the previous dose and follow regular dosing schedule. Do not take two doses at once.
If you have some another questions, please contact your healthcare provider.
Inform your doctor or healthcare provider right away if any of these apply to you. Diflucan also may interact with other medicines. Tell your doctor if you are taking aldosterone blockers, Rifabutin, macrolide immunosuppressants, Rifampin or proton pump inhibitors, anticoagulants. This is not a complete list of interactions, if you need detail information, please contact your doctor.
• with a weakened immune system, kidney or liver disease, or an irregular heartbeat, order fluconazole without prescription australia.
Any medication can cause side-effects but many people have no, or minor, side effects, diflucan medication uk.
• yellowing of the skin or eyes, cost of diflucan one canada.
This is not a full list of side effects and that may occur, cost of diflucan buy online australia. If you need detail information, ask your doctor or healthcare provider, purchase diflucan without prescription canada.
If you suspect an overdose, stop taking Diflucan and contact your local poison control center or seek an immediate emergency help, order diflucan online without prescription. Symptoms of overdose may be followed by changes in behavior; convulsions; hallucinations; seizures; slowed breathing, order diflucan online pharmacy.
Store Diflucan at temperature below 86 degrees F (30 degrees C), buy diflucan no prescription. Keep away from heat, moisture, and light, out of the reach of children and pets, can you buy diflucan over the counter. It is not recommended to store Diflucan in the bathroom, buy diflucan online without a prescription.


Locate your child's school for school closing, late start, or early release. Aftercare programs housed at Monee and Coretta Scott King Magnet School will be notified in the event of school closing, late start, or early release. We will not be closing these facilities to the aftercare programs, so please plan accordingly.
**On emergency weather closings all after-school activities are cancelled. On late start emergency weather days, after-school activities will be announced.
In the event of an emergency weather school closing our SchoolMessenger Notification System will be activated. The system has the capability of calling multiple telephone numbers as well as sending an email and text message.


text:
Home > COA > ENTOMOLOGY > ENTOMOLOGY_PUBS > 37
New microsporidia parasitizing bark lice (Insecta: Psocoptera)
Yuliya Y. Sokolova, Institute of Cytology of the Russian Academy of Sciences
Igor M. Sokolov, Institute of Cytology of the Russian Academy of Sciences
Christopher E. Carlton, Institute of Cytology of the Russian Academy of Sciences
Two species of bark lice, Xanthocaecilius sommermanae Mockford and Polypsocus corruptus Hagen, collected in a canopy Malaise trap placed in Great Smoky Mountains National Park as part of a survey of the park's fauna, were found to be infected with microsporidia. Diagnosis was originally based on light microscopy, and was confirmed by PCR amplification and electron microscopy. This is the first record of microsporidia infection in the insect order Psocoptera. Four morphological spore types corresponded to four original SSUrDNA sequences (Genbank accession no. FJ865221-24), suggesting infection with four microsporidia species. Two of those species were examined by electron microscopy. We describe here one new genus and two new species based on morphological and sequence data: Antonospora psocopterae sp. n. with elongated diplokaryotic spores, 4.4 ± 0.05 × 1.9 ± 0.03 μm and Mockfordia xanthocaeciliae gen. n. sp. n. with ovocylindrical monokaryotic spores, 2.5 ± 0.10 × 1.4 ± 0.02 μm. A. psocopterae displayed high sequence (95%) and structural similarity with Antonospora scoticae, fell within a well supported dichotomy with A. scoticae inside the Antonospora-Paranosema clade in phylogenetic analyses by NJ, PS and ML. M. xanthocaeciliae did not exhibit much sequence or structural similarity with any of known microsporidia species, except Encephalitozoon spp. M. xanthocaeciliae fell within one clade with Encephalitozoon spp. in phylogenies and shared with encephalitozoons structural resemblance and about 80% of SSUrDNA sequence identity. The other two species were not described and provisionally were placed to the collective genus Microsporidium as Microsporidium sp. 1 and Microsporidium sp. 4 from bark lice because of insufficient morphological data. The finding that samples fixed and stored for months in propylene glycol (" antifreeze" ) are good enough for DNA sequence analysis and can be used for morphological analyses (if no better fixation alternatives are available), is promising for future surveys for microsporidia. © 2010 Elsevier Inc.
Journal of Invertebrate Pathology
Sokolova, Y., Sokolov, I., & Carlton, C. (2010). New microsporidia parasitizing bark lice (Insecta: Psocoptera). Journal of Invertebrate Pathology, 104 (3), 186-194. https://doi.org/10.1016/j.jip.2010.03.008


This "plank piece" explored the filleting in three dimensions of an oak plank, which allowed for the telescoping of both ends. The ends would be tied at pre-determined intervals at the discretion of the owner/viewer of the piece depending on the length of the mounting wall. The horizontal center of the piece remains part of the original plank forming a "T" in profile. The upper and lower telescoping sections were cut as "L" forms in profile with the smallest end pieces in "square" profile. The piece could be collapsed into its original 90-inch plank for storage or transport.
H: 5 in. x W: 22 ft. 3 in. x D: 3 in.


text:
package examples;

import org.junit.*;
import org.mapdb.elsa.*;

import java.io.IOException;

import static org.junit.Assert.*;

/**
 * Shows various option to handle references, cyclic references,
 * duplicate references and deduplication.
 */
public class References {

    @Test @Ignore
    public void noReferenceHandling() throws IOException {
        String object = "object";
        //pair of two objects
        Object[] obj = new Object[]{object, object};

        ElsaSerializer serializer = new ElsaMaker()
                //disable reference tracking
                .referenceDisable()
                .make();

        Object[] cloned = serializer.clone(obj);

        // object identity is not preserved after cloning
        assertTrue(cloned[0]!=cloned[1]);

        //demonstrate cyclic reference
        obj[0] = obj;
        try {
            serializer.clone(obj);
            fail("should throw an exception");
        }catch(java.lang.OutOfMemoryError e){
            //FIXME this is just nasty, add limit on stack size?
            //expected
        }
    }

    @Test
    public void arrayReferenceHandling() throws IOException {
        String object = "object";
        //pair of two objects
        Object[] obj = new Object[]{object, object};

        ElsaSerializer serializer = new ElsaMaker()
                // Enable reference array, slower on larger graph,
                // but faster on very small graphs.
                .referenceArrayEnable()
                .make();

        Object[] cloned = serializer.clone(obj);

        // object identity is preserved after cloning
        assertTrue(cloned[0]==cloned[1]);
    }

    @Test
    public void deduplication() throws IOException {
        Integer object1 = new Integer(10000);
        Integer object2 = new Integer(10000);
        //pair of two objects
        Object[] obj = new Object[]{object1, object2};

        ElsaSerializer serializer = new ElsaMaker()
                // Use HashMap to track reference,
                // but also to deduplicate different objects which are equal
                .referenceHashMapEnable()
                .make();

        Object[] cloned = serializer.clone(obj);

        // equal but not-identical objects are identical after cloning
        assertTrue(cloned[0]==cloned[1]);
    }
}

redpajama_set_name: RedPajamaGithub


This diploma course is taught in 12 sessions over six weekends.
In this is course where you will explore how to work therapeutically, effectively and safely with young people (aged between 11 and 18). You will gain the confidence to help a young person to express themselves and tell their story whilst understanding and employing a variety of interventions. You will also reflect on your own adolescence and how this may affect your role as a young person's counsellor.
Starting with a foundation of understanding the development of the young person along with attachment patterns, you will be able to gain an understanding of the individual young person and tailor the therapy to suit their needs. You will encourage the young person to feel safe enough to have those important conversations, and empower them to explore how they can make the changes they may need to make. You will study the impact that the systems around the young person can have on them, this includes looking at the role of the family, school, their culture and the community that they live in. Exploring the practicalities of counselling young people, such as contracting, initial sessions as well as safeguarding, is balanced with developing therapeutic techniques and creative ways of working, thus offering an experience of therapy that can positively impact on the young person's life.
I facilitate this course along with my husband James Schindler-Ord. We are both psychotherapists with many years of experience working with young people. We have written and delivered training in this area for many years. We both work with young people in Private Practice and supervise counsellors and other professionals who work with young people.