|
ovs all
|
The Open vSwitch kernel module allows flexible userspace control over flow-level packet processing on selected network devices. It can be used to implement a plain Ethernet switch, network device bonding, VLAN processing, network access control, flow-based network control, and so on.
The kernel module implements multiple "datapaths" (analogous to bridges), each of which can have multiple "vports" (analogous to ports within a bridge). Each datapath also has associated with it a "flow table" that userspace populates with "flows" that map from keys based on packet headers and metadata to sets of actions. The most common action forwards the packet to another vport; other actions are also implemented.
When a packet arrives on a vport, the kernel module processes it by extracting its flow key and looking it up in the flow table. If there is a matching flow, it executes the associated actions. If there is no match, it queues the packet to userspace for processing (as part of its processing, userspace will likely set up a flow to handle further packets of the same type entirely in-kernel).
Network protocols evolve over time. New protocols become important and existing protocols lose their prominence. For the Open vSwitch kernel module to remain relevant, it must be possible for newer versions to parse additional protocols as part of the flow key. It might even be desirable, someday, to drop support for parsing protocols that have become obsolete. Therefore, the Netlink interface to Open vSwitch is designed to allow carefully written userspace applications to work with any version of the flow key, past or future.
To support this forward and backward compatibility, whenever the kernel module passes a packet to userspace, it also passes along the flow key that it parsed from the packet. Userspace then extracts its own notion of a flow key from the packet and compares it against the kernel-provided version:
How flow keys evolve over time is important to making this work, so the following sections go into detail.
A flow key is passed over a Netlink socket as a sequence of Netlink attributes. Some attributes represent packet metadata, defined as any information about a packet that cannot be extracted from the packet itself, e.g. the vport on which the packet was received. Most attributes, however, are extracted from headers within the packet, e.g. source and destination addresses from Ethernet, IP, or TCP headers.
The <linux/openvswitch.h> header file defines the exact format of the flow key attributes. For informal explanatory purposes here, we write them as comma-separated strings, with parentheses indicating arguments and nesting. For example, the following could represent a flow key corresponding to a TCP packet that arrived on vport 1:
in_port(1), eth(src=e0:91:f5:21:d0:b2, dst=00:02:e3:0f:80:a4), eth_type(0x0800), ipv4(src=<IP_ADDRESS>, dst=<IP_ADDRESS>, proto=17, tos=0, frag=no), tcp(src=49163, dst=80)
Often we ellipsize arguments not important to the discussion, e.g.:
in_port(1), eth(...), eth_type(0x0800), ipv4(...), tcp(...)
A wildcarded flow is described with two sequences of Netlink attributes passed over the Netlink socket. A flow key, exactly as described above, and an optional corresponding flow mask.
A wildcarded flow can represent a group of exact match flows. Each '1' bit in the mask specifies an exact match with the corresponding bit in the flow key. A '0' bit specifies a don't care bit, which will match either a '1' or '0' bit of an incoming packet. Using a wildcarded flow can improve the flow set up rate by reducing the number of new flows that need to be processed by the user space program.
Support for the mask Netlink attribute is optional for both the kernel and user space program. The kernel can ignore the mask attribute, installing an exact match flow, or reduce the number of don't care bits in the kernel to less than what was specified by the user space program. In this case, variations in bits that the kernel does not implement will simply result in additional flow setups. The kernel module will also work with user space programs that neither support nor supply flow mask attributes.
Since the kernel may ignore or modify wildcard bits, it can be difficult for the userspace program to know exactly what matches are installed. There are two possible approaches: reactively install flows as they miss the kernel flow table (and therefore not attempt to determine wildcard changes at all) or use the kernel's response messages to determine the installed wildcards.
When interacting with userspace, the kernel should maintain the match portion of the key exactly as originally installed. This will provides a handle to identify the flow for all future operations. However, when reporting the mask of an installed flow, the mask should include any restrictions imposed by the kernel.
The behavior when using overlapping wildcarded flows is undefined. It is the responsibility of the user space program to ensure that any incoming packet can match at most one flow, wildcarded or not. The current implementation performs best-effort detection of overlapping wildcarded flows and may reject some but not all of them. However, this behavior may change in future versions.
An alternative to using the original match portion of a key as the handle for flow identification is a unique flow identifier, or "UFID". UFIDs are optional for both the kernel and user space program.
User space programs that support UFID are expected to provide it during flow setup in addition to the flow, then refer to the flow using the UFID for all future operations. The kernel is not required to index flows by the original flow key if a UFID is specified.
Some care is needed to really maintain forward and backward compatibility for applications that follow the rules listed under "Flow key compatibility" above.
The basic rule is obvious:
New network protocol support must only supplement existing flow key attributes. It must not change the meaning of already defined
This rule does have less-obvious consequences so it is worth working through a few examples. Suppose, for example, that the kernel module did not already implement VLAN parsing. Instead, it just interpreted the 802.1Q TPID (0x8100) as the Ethertype then stopped parsing the packet. The flow key for any packet with an 802.1Q header would look essentially like this, ignoring metadata:
eth(...), eth_type(0x8100)
Naively, to add VLAN support, it makes sense to add a new "vlan" flow key attribute to contain the VLAN tag, then continue to decode the encapsulated headers beyond the VLAN tag using the existing field definitions. With this change, a TCP packet in VLAN 10 would have a flow key much like this:
eth(...), vlan(vid=10, pcp=0), eth_type(0x0800), ip(proto=6, ...), tcp(...)
But this change would negatively affect a userspace application that has not been updated to understand the new "vlan" flow key attribute. The application could, following the flow compatibility rules above, ignore the "vlan" attribute that it does not understand and therefore assume that the flow contained IP packets. This is a bad assumption (the flow only contains IP packets if one parses and skips over the 802.1Q header) and it could cause the application's behavior to change across kernel versions even though it follows the compatibility rules.
The solution is to use a set of nested attributes. This is, for example, why 802.1Q support uses nested attributes. A TCP packet in VLAN 10 is actually expressed as:
eth(...), eth_type(0x8100), vlan(vid=10, pcp=0), encap(eth_type(0x0800), ip(proto=6, ...), tcp(...)))
Notice how the "eth_type", "ip", and "tcp" flow key attributes are nested inside the "encap" attribute. Thus, an application that does not understand the "vlan" key will not see either of those attributes and therefore will not misinterpret them. (Also, the outer eth_type is still 0x8100, not changed to 0x0800.)
Don't drop packets in the kernel for malformed protocol headers, bad checksums, etc. This would prevent userspace from implementing a simple Ethernet switch that forwards every packet.
Instead, in such a case, include an attribute with "empty" content. It doesn't matter if the empty content could be valid protocol values, as long as those values are rarely seen in practice, because userspace can always forward all packets with those values to userspace and handle them individually.
For example, consider a packet that contains an IP header that indicates protocol 6 for TCP, but which is truncated just after the IP header, so that the TCP header is missing. The flow key for this packet would include a tcp attribute with all-zero src and dst, like this:
eth(...), eth_type(0x0800), ip(proto=6, ...), tcp(src=0, dst=0)
As another example, consider a packet with an Ethernet type of 0x8100, indicating that a VLAN TCI should follow, but which is truncated just after the Ethernet type. The flow key for this packet would include an all-zero-bits vlan and an empty encap attribute, like this:
eth(...), eth_type(0x8100), vlan(0), encap()
Unlike a TCP packet with source and destination ports 0, an all-zero-bits VLAN TCI is not that rare, so the CFI bit (aka VLAN_TAG_PRESENT inside the kernel) is ordinarily set in a vlan attribute expressly to allow this situation to be distinguished. Thus, the flow key in this second example unambiguously indicates a missing or malformed VLAN TCI.
The other rules for flow keys are much less subtle:
Please implement the headers and codes for compatibility with older kernel in linux/compat/ directory. All public functions should be exported using EXPORT_SYMBOL macro. Public function replacing the same-named kernel function should be prefixed with 'rpl_'. Otherwise, the function should be prefixed with 'ovs_'. For special case when it is not possible to follow this rule (e.g., the pskb_expand_head() function), the function name must be added to linux/compat/build-aux/export-check-whitelist, otherwise, the compilation check 'check-export-symbol' will fail.


Children from orphanages enjoy a day out
by Special CorrespondentMore than 600 children from 10 orphanages in the city took part in games and other entertainment activities organised as part of the annual inter-orphanage Olympics sports and cultural meet at the Canara High School, Urwa Grounds, on Sunday.
The event was organised jointly by the Rotaract Club of Mangaluru.
Among the events that the children took part in included frog jumping, jumping with gunny bags, lemon and spoon and notebook balancing. The students did a march past before taking part enthusiastically in all the events.
Inaugurating the event, Mangaluru City South MLA D. Vedavyas Kamath lauded the initiative by the Rotaract Club in providing a forum for children from orphanages to display their talent.
He called upon organisations to work towards eliminating social inequality and lend support to the needy in society. Mr. Kamath assured his support for social activities of the club.
Chairman of the organising committee of the event Devdas Rai said that the intention of holding the programme was to bring smiles on the faces of children by driving away the feeling of loneliness.


Genetic screening has been a cornerstone in efforts to dissect the program that controls how cells exert their functions or break down in disease. High-throughput chemical screens typically employ coarse assays, (e.g. cell survival) or inspect gross anatomic phenotypes, limiting what can be learned about mechanisms of action, off-target effects, and heterogeneous responses. Single-cell sequencing provides a means of interrogating the molecular consequences of genetic, chemical, or environmental perturbations, but limited sample multiplexing in commercial platforms makes screening infeasible. We have developed and continue to improve various methods for highly multiplexed single-cell sequencing experiments. We have applied these tools to study diverse biological systems including cancer cells and whole zebrafish embryos.


She was more like a beauty queen from a movie scene
I said, "Don't mind, but what do you mean I am the one
Who will dance on the floor in the round?"
She said I am the one who will dance on the floor in the round
She told me her name was Billie Jean as she caused a scene
Then every head turned with eyes that dreamed of being the one
Who will dance on the floor in the round
People always told me, "Be careful of what you do.
And don't go around breaking young girls' hearts."

Billie Jean is not my lover She's just a girl
who claims that I am the one but the kid is not my son
She says I am the one But the kid is not my son
For forty days and for forty nights Law was on her side
But who can stand When she's in demand Her schemes and plans
'Cause we danced on the floor in the round
So take my strong advice Just remember to always think twice
(Do think twice, do think twice.)
She told, "My baby, we'd danced 'til three." Then she looked at me
Then showed a photo of a baby cry His eyes looked like mine, oh, no
Do a dance on the floor in the round, baby
A-people always told me, "Be careful of what you do
And don't go around breaking young girls' hearts."


Man arrested on suspicion of OWI, fake plates made from beer case
CHIPPEWA FALLS, Wis. - The Chippewa Falls Police Department made a fourth-offense drunken driving arrest Monday and found fake plates on the suspect's vehicle.
According to a Chippewa Falls PD Facebook post, Officer Scott Schoenwetter pulled over the driver Monday and noticed the registration plates didn't match the vehicle.
"Maybe they are legal in the THE LAND OF SKY BLUE WATERS just not here in Chippewa Falls!!!" police said in the Facebook post.
Following a closer inspection, the officer realized the plates were made out of a case of Hamm's beer.
Get your weather forecast from people that actually live in your community. We update with short, easy-to-use video forecasts you can watch on your phone every day. Download the iOS or Android app here.


Ocala events
-
mangia restaurant menu easton pa
Denver, Colorado, U.S.A. extended 2 weeks weather forecast
Forecasted weather conditions the coming 2 weeks for Denver, Colorado, U.S.A..
http://www.timeanddate.com/weather/usa/denver/extBoulder CO Weather - Climate and Temperature Snow Conditions
Check weather and snow conditions in Boulder Colorado to make sure your . January is the coldest month in Boulder, with an average daytime high of 45 .
http://www.bouldercoloradousa.com/visitor/weather/Colorado Springs Weather Forecast and Conditions - weather.com
Colorado Springs weather forecast and weather conditions. Today's and tonight's Colorado Springs weather forecast plus Doppler radar from weather.com.
http://www.weather.com/weather/today/USCO0078
event edutainment in italy Upcoming events in Ocala
rear seat covers 2008 cadillac cts Hottest Tickets
-
Apr 11ft leonard wood missouri
Amway Center -
Apr 28criminal defendant punches lawyer cnn video
Amway Center -
Jun 25seboygan wi news paper
Bob Carr Performing Arts Center -
Mar 30adjusting 2005 dodge caravan headlights
Amway Center -
Aug 27imperial university glen walington
Amway Center -
Jun 21artists supplies manchester new hampshire
Amway Center -
Sep 13parachute flyer with motor
Francis Field -
Mar 17african american history syllabus
St Augustine Amphitheatre -
Oct 8gold script monogram rings
Amway Center -
May 4miniature pinschers ear problems
Bob Carr Performing Arts Center
Ocala's best venues
-
Denver Weather - AccuWeather Forecast for CO 80203
Offers current local conditions, extended forecasts weather maps, Doppler radar, and historical weather information.
http://www.accuweather.com/en/us/denver-co/80203/weather-forecast/347810 -
Weather Forecast Louisville, CO | Louisville Weather | Wunderground
Tropical Weather: Tropical Cyclone Tim (Southern Pacific). View WunderPhotos® in: Louisville, Colorado. News . Weather Station - Report - Buy a Station .
http://www.wunderground.com/weather-forecast/US/CO/Louisville.html -
Denver Weather - Climate Zone
Climate information for Denver Colorado including average .
http://www.climate-zone.com/climate/united-states/colorado/denver/23 inch kds monitor
98 people's favorite
-
Weather Forecast Falcon, CO | Falcon Weather | Wunderground
Tropical Weather: Tropical Cyclone Tim (Southern Pacific) . Meadow Lake, CO (KFLY) | 48 °F | Clear Colorado Springs, CO (KCOS) | 57 °F | Partly Cloudy Air . January, February, March, April, May, June, July, August, September, October .
http://www.wunderground.com/weather-forecast/US/CO/Falcon.html -
Weather Forecast Boulder, CO | Boulder Weather | Wunderground
Weather Underground provides local & long range Weather Forecast, weather reports, maps & tropical weather conditions for locations worldwide.
http://www.wunderground.com/weather-forecast/US/CO/Boulder.html


DAO tier is Data Access Object abstract interface. In B12phpfw code skeleton Model and DAO tiers are in :
In B12phpfw code skeleton i use M_V data flow for read, but it is easy (but in my opinion not appropriate) to use M_C_V data flow for read - in Home_ctr.php we examine user entered URL (request) and call method which can read data (or do any CRUD operation - procedure on data).
Ancient Greek maxim (aphorism) "know thyself" (Greek: γνῶθι σεαυτόν, latin "nosce te ipsum") is one of the Delphic maxims and was the first of three maxims inscribed in the pronaos (forecourt) of the Temple of Apollo at Delphi according to the Greek writer Pausanias.
The two maxims that followed are :
https://en.wikipedia.org/wiki/Know_thyself https://www.john-uebersax.com/delphi/delphi.htm https://www.wikiwand.com/en/Delphic_maxims https://www.mimamsadiary.com/the-great-wisdom-from-ancient-greece/
<a target="_blank" href="../../vendor/b12phpfw/img/meatmirror.jpg
In code above href="/vendor/b12phpfw/img/meatmirror.jpg" does work in PHP
and in HTML called with URL eg
http://dev1:8083/fwphp/glomodul/img_gallery/index.html
,
but href="/vendor/b12phpfw/img/meatmirror.jpg" does not work in double clicked HTML
meaning browser does not know where is web server document root !
href="../../vendor/b12phpfw/img/meatmirror.jpg works for both script opening methods if we do not change folder structure - which we do not - no need. href="/vendor/b12phpfw/img/meatmirror.jpg" is alike sensitive to folder structure.
This example Tryit Editor v3.6 (w3schools.com) use media queries to re-arrange the images on different screen sizes: for screens larger than 700px wide, it will show four images side by side, for screens smaller than 700px, it will show two images side by side. For screens smaller than 500px, the images will stack vertically (100%). You will learn more about media queries and responsive web design later in our CSS Tutorial. See also How To Create a Slideshow (w3schools.com) .


| oggz.h [code] | The liboggz C API |
| oggz_comments.h [code] | Reading of comments |
| oggz_constants.h [code] | General constants used by liboggz |
| oggz_deprecated.h [code] | Deprecated interfaces |
| oggz_io.h [code] | Overriding the functions used for input and output of raw data |
| oggz_off_t.h [code] | Architecture-dependent type and printf format for file position |
| oggz_read.h [code] | Interfaces for reading Ogg files and streams |
| oggz_seek.h [code] | Seeking within files |
| oggz_stream.h [code] | Interfaces for querying Ogg streams |
| oggz_table.h [code] | A lookup table |
| oggz_write.h [code] | Interfaces for writing Ogg files and streams |


--- status: publish layout: page author: display_name: Rick Kelson email<EMAIL_ADDRESS>tags: [] published: false date: 2016-11-23 09:13:55 -0700 title: 2016 NAIP 1 Meter Orthophotography Prelim categories: [] ---
AGRC has the preliminary statewide National Agricultural Imagery Program (NAIP) 3-band aerial photography for Utah in Mr. Sid county mosaics. The imagery is 1-meter resolution and was collected in the summer of 2016. The date the photography was flown can be found in the IDATE field in the associated shapefile. Be aware some of the larger counties (ex. San Juan, Millard, Tooele and Box Elder) are no longer split into multiple parts and their file size is upwards of 4 to 7 GB. The images have a UTM NAD83 meters projection.
Retrieve 2016 NAIP via Interactive MapIf you are having problems with the imagery from AGRC read this document


ANC Youth League member shot dead, another wounded at Hammanskraal rally
by Azarrah KarrimA 25-year-old African National Congress Youth League member has been shot dead and another member wounded at a rally at the Temba Stadium in Hammanskraal on Saturday.
According to South African Police Service Brigadier Mathapelo Peters, preliminary reports have suggested that an argument broke out between delegates at the rally before the shooting.
"Preliminary reports reveal that an argument broke out amongt some delegates during a political rally at the stadium, and this led to scenes of violence where the delegates allegedly started attacking each other.
"It is reported that the deceased was trying to defuse the fight when an unknown man emerged from the crowd and fired shots at the deceased, fatally wounding the 25-year old victim."
Peters added that the other victim, who is believed to be the organiser of the event, was also shot and rushed to hospital.
"The suspect is said to have driven off in a grey BMW with unknown registration," Peters said.
"Police are still on the scene to gather more information, and are appealing to anyone with information of the suspect and his whereabouts to contact police in Temba or call the Crime Stop number 08600 10111."
ANCYL Tshwane regional chairperson Lesego Makhubela confirmed to News24 that the shooting had taken place outside the venue.
"There are witnesses who witnessed the shooting," he said, adding that they would be in communication with police.
Makhuba said the shooter and his victim had been involved in an argument before the shooting, however, it is unclear what it was about.
The shooter was apparently known to witnesses and was not an ANCYL member, Makhubela said.


| DOSE: T+ 0:00 |
100 mg |
oral |
Tryptophan |
(capsule) |
| T+ 4:00 |
2 tablets |
oral |
MDMA |
|
| T+ 6:00 |
2 lines |
insufflated |
Cocaine |
(powder / crystals) |
| T+ 6:30 |
1 tablet |
oral |
MDMA |
|
[Erowid Note: While it may be that the substances described below are MDA and MDMA, Ecstasy tablets are notoriously impure or misrepresented, often containing chemicals other than those they are presumed to contain. This report indicates MDMA as the primary substance, but readers should be aware that this is more of a general Ecstasy report.]
It was a Friday night and myself, my boyfriend, C, and another one of our friends, R, had decided to attend a rave a few states away. About four hours prior to our drug ingestion, we each took 100 mg of 5-HTP. We arrived at the party and stayed sober for about 2 hours. I wanted to see a certain dj's set, so I asked R to find some pills for us. I was very tired already, because I hadn't gotten much sleep the night before, and I also didn't have enough water to drink so I was feeling really dehydrated from dancing.
In retrospect, it was a very bad idea to take drugs in this situation. As the dj's set was ending, R came up to C & I and asked us to follow him, so we went back to a more secluded area and he gave each of us two pills. I had asked him to get one for each of us, so I began giving two of them back to him and explaining his mistake, but he said that he wanted to buy us our pills for the night since we had driven six hours to the party and spent so much money on gas.
I hardly ever take more than one pill, especially in public at a rave, and I have never taken two at a time before. I guess this is unusual because I have a lot of experience with ecstasy, but I usually don't feel the need to spend so much money on one E experience. I like just taking enough to enhance my enjoyment of a rave, I really don't like to be out of control on it. I don't roll very often so I don't have much of a tolerance and am usually fine with taking one pill, but I felt like I should indulge myself.
Anyway, after taking my pills, I separated from R & C because I saw some people I wanted to talk to. About half an hour or forty-five minutes later, I was in the middle of a sentence when I suddenly felt this huge wave of fuckedupness come over me. I felt way too overwhelmed. I excused myself, and went back to the chillout area. I didn't see R or C, so I sat down with the first person I saw who was a familiar, trusted face: my friend T. He was on three hits of LSD, and a bit out of it himself. I told him that I had taken two pills and that I was not feeling well and asked him if he could sit with me for a while.
He asked what kind of pills I took, and I told him what stamp & color they were, and he got this shocked expression and told me that I shouldn't have taken two at a time because they were so powerful. As he said that, I felt myself descending into this overpowering negative experience. A few other people came over to talk, and I felt like I wasn't really able to respond to them, so I was barely saying anything (which is really unusual for me). I laid my head down on T's shoulder because I was so freaked out and didn't want to talk to anyone.
A lot of people were asking him what was wrong with me, and it was making me really paranoid and nervous. I was also having momentary blackouts which I think was from exhaustion & dehydration, I had pushed my body to the limit. I was feeling nauseous and couldn't stand up or anything. I started hallucinating; I had little weird dream sequences, and when I opened my eyes and looked around, my vision was really weird and everything was shaking and moving around. It was like I was watching everything through a video camera and it was really shaky, and there were huge tracers on everything. I was told later that my eyes were twitching and it looked like I was having a seizure.
I was freaking out really badly. T and I were trying to have a conversation, but it was really difficult because we were both in our own headspace, and I was trying not to let on to him how fucked up I was, because I felt embarrassed at getting so out of control. I was really hoping that the uncomfortable feeling would end soon and I was trying to just ride it out without calling attention to myself or making a big deal.
Suddenly, I glimpsed my boyfriend across the room, and I tried to stand up or call out to him, but I wasn't able to. I managed to say something like 'C, I need C' to T and he went and got C for me. C sat down next to me, and was having a great time apparently. He started hugging and kissing me and telling me how much he loved me. He didn't realize what a horrendous time I was having. I told him that I didn't feel very well and he went and got me a water, which I took one sip of and set down because it felt like too much effort to drink it. I just wanted C to hold me so I would feel safe but instead he wanted to talk about our relationship and how much he cared about me, which I wasn't really in the mood for. He kept asking me what was wrong and why I wasn't happy and I felt like I couldn't make him understand. He told me I should drink water and I'd feel better, but I reached for my water and it was gone, so C bought me another one.
Soon after, he ran off somewhere, and I was alone for a while.   I kept trying to get up and would be able to stand for a few minutes but the task of finding C, R, or another trusted friend seemed sooooo impossible. The venue was really not that big but I felt like I would get lost in a maze if I tried to find them, so I kept sitting back down.
Then, my friend A, who I had barely seen all night, came and sat with me. I knew that A wouldn't judge me for being in the situation I was in, so when she asked me if I was ok I told her what was going on. I told her that I felt really tired and sick, and like I couldn't stand up, and that I thought there was some kind of psychedelic in my pill. We were talking for a while but I was having a really hard time with my short term memory and remembering what we were talking about. She told me that she had a little bit of cocaine and asked me if I thought it would help to do a bump or two. I said yes, and she escorted me to the bathroom. We went in a stall and I did 2 bumps off a key, and immediately felt sooo much better. I was able to talk much more and walking took much less effort.
I started feeling MDMA-ish and gave A a big hug, and my scalp started tingling. I felt like I was rolling instead of tripping out. We went back out to the party and I found R and C again, and told them that I was feeling way better. We all danced for a while, although I didn't have quite as much dancing energy as I usually do. R asked me if I wanted another pill, and I was enjoying myself so much at that point that I said yes. (I'm not sure why I did that, I guess I just conveniently forgot what had occured earlier).
About half an hour later, the coke wore off and the pill kicked in, and I started feeling not so good again. I stopped talking quite as much and was getting tired again, although I wasn't feeling sick any more. The party was ending and people were leaving. Pretty soon, the lights came on and there were only about fifteen people still there. Since we were from out of town, we were planning to stay at A's apartment, but there were some other people who needed a place to go as well and we were trying to figure out where we were going. It was hard for me to understand the flow of conversation so I just went and sat down on the steps and waited for everyone to figure it out.
After we left, I started feeling much better and pretty much sobered up within an hour of leaving, other than feeling kind of speedy. We took a lot more drugs that weekend but that's a story for another time, I suppose.
I found out later that the pills I took had 2-CB in them, and possibly MDA. I wish I hadn't taken so many, because I probably would have been able to handle my experience otherwise. Also, I should have listened to my body and stayed sober since I didn't have proper rest, and I should have stayed hydrated. In the future I'm going to be way more careful about how much I take, and stop trying to push my body to the limit.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Amazon Kindle phone incoming?
Amazon is reportedly working on a 4.7in smartphone, according to industry supply chain sources.
This isn't the first time we've heard whisperings of a Kindle phone and the rumours suggest that Amazon will be shifting the presumably Android-based unit for as low as US$100-US$200..
The release date of the Kindle phone - and any specs beyond that 4.7in screen - are still a mystery - although the phone's reportedly facing delays due to manufacturing problems at the Foxconn factory in China. We'll be sure to keep you updated when we find out more.


{{ site.data.selected_publications_title | default: "Skills" }}
Programming languages
Machine learning research
Others


I am driven by a minimalist technological optimism: my pessimism for the future is offset by my dismay at the past.
To put it another way, I am profoundly concerned at the darker directions being taken by emerging technologies, but simultaneously excited about some of the possibilities they offer to restructure our world in ways that make it less unjust and more inclusive.
We have tools in our hands to redress the entrenched injustices of the past and to create new forms of communal existence, but most people seem to be using them exclusively to make more effective adversting. Unbelievably exciting technologies are being used to do the most boring and terrifying things imaginable.
I am particularly interested in AI (or automated decision making - ADM) as it impacts what it means to be human in today's world. By automating certain decisions, whether ethical or political, do we undermine fundamental aspects of our humanity?
I believe that philosophy, ethics, and human rights have an essential role to play in directing technological progress, so that we don't end up winning a technological arms race that equates to losing our humanity.
Check out my projects and writing to see what I'm up to on these topics.


An identity is a description of a particular entity such as a person, software agent, or organization. A credential is a qualification, achievement, quality, or information about an identity's background such as a name, government ID, home address, or university degree. This specification describes mechanisms for reading credentials from and writing credentials to an identity while ensuring that the information is only accessible to authorized applications.
This is an experimental specification that is attempting to unify the work performed in the the Web Payments Community Group, the Linked Data community, the WebID Community Group, and the Mozilla Persona team. As such, the specification borrows a number of concepts from each group and attempts to sythesize these concepts into a solution that would be easily implemented and deployed by Web developers in order to provide an elegant readable and writable identity mechanism for the Web.
An identity is a set of information that can be used to identify a particular entity such as a person, software agent, animal, or organization. We typically associate credentials with identities to access many services throughout our lives. For example, we use email addresses to identify ourselves to online services, driver's licenses to prove that we are capable of operating a motor vehicle, and government issued passports to travel between countries. It is the goal of this specification to provide an easy way of expressing all of this identity and credential information on the Web.
There are a number of design principles that have gone into the creation of this specification. The following is a brief list of these requirements:
This specification enables secure, decentralized, discoverable, controlled access to arbitrary machine-readable information associated with an identity. Since it's useful to associate varying degrees of sensitive information with a particular identity, the specification ensures that a single entity can associate themselves with multiple identities. For example, one may want to use one identity to access banking services while another identity could be used to play online games.
In order to store the breadth of information that is typically associated with an identity, a simple but extensible data model is utilized. The specification uses a data storage and expression approach called Linked Data. It is a way of expressing information on the Web that is both simple and extensible. Specifically, the Linked Data technology used by this specification is JSON-LD [[!JSON-LD]].
An entity may have one or more identities associated with it. These can be
anonymous identities, pseudo-anonymous identities, protected identities,
and public identities. The creation of these identities is out of scope
for this document, but typically result in the creation of a long-lived
identity document URL.
For example, https://example.com/identities/john
is
an example of a long-lived identity document URL.
A basic identity contains at least the type information for the identity.
@context
https://w3id.org/identity/v1
, or an equivalent
JSON-LD Context [[!JSON-LD]] expressing the terminology necessary for the
expression of the data.type
Identity
. Note that this field usually
contains more specific type information in addition to Identity
such as Person
or Organization
.A typical identity will have a mix of public and private data associated with it. For example:
{ "@context": "https://w3id.org/identity/v1", "id": "https://example.com/identities/bob", "type": ["Identity", "Person"], "name": "Bob Bobman", "governmentId": "123-45-6789", "birthdate": "1985-12-14", "email"<EMAIL_ADDRESS>"mobileNumber": "12345678910", "shippingAddress": { "street": "372 Sumter Lane", "city": "Blackrock", "region": "Nevada", "postalCode": "237842" }, "credential": [{ "id": "http://ssa.us.gov/credentials/3732", "type": "PassportCredential", "claim": { "id": "https://example.com/identities/bob", "name": "Bob Bobman", "birthdate": "1985-12-14", "governmentId": "123-45-6789" }, "expires": "2018-01-01", "signature": { "type": "GraphSignature2012", "creator": "https://ssa.us.gov/keys/27", "signature": "3780eyfh3q0fhhfiq3q9f8ahsidfhf29rhaish" } }, ... ] }
The example above contains a mix of public and private information. For example,
the identity owner may be comfortable with making their
name
publicly readable and would do so using the
identity provider's website interface.
Other information, such as governmentId
and email
would be marked as private, and would only be shared after the request for
that particular information has been approved by the
identity owner.
Information can be asserted, via a credential, by a trusted
third party and written to the identity using the mechanism described in
Section 4: Writing Data to
the Identity. Not all information needs to be placed into a
credential. For example,
shippingAddress
above is not in a credential and is
thus unverifiable. A credential consumer would have to trust that the
shippingAddress
information provided
by the identity owner is trustworthy. Other information, such as
name
, birthdate
, and governmentId
have been asserted via a credential by a third party. In this
particular case, the information has been asserted by
the Social Security Administration of the United States government.
There are two mechanisms that allow a third party to read protected information from an identity. The first is an HTTP Signature [[!HTTP-SIGNATURES]] based mechanism that allows any authorized client to access data that has been pre-approved by the entity that controls access to the identity information. The second is to use a browser-based mechanism that POSTs a request to an identity, allowing the identity owner to interactively decide what data access to allow or disallow.
The table below summarizes the HTTP Signatures-based [[!HTTP-SIGNATURES]] mechanism of accessing and modifying an identity:
| HTTP Method | Description of Action |
|---|---|
| GET | Read all of the information that is available to the credential consumer. Note: This may only be a subset of all of the information based on the level of access the credential consumer has to certain attributes in the resource. |
| POST | Used to perform operations on the identity for applications that are not capable of using HTTP Signatures [[!HTTP-SIGNATURES]] or to perform specific queries on the identity data. |
| PATCH | Modify information in the identity using the JSON Patch [[!JSON-PATCH]] protocol. |
| PUT | Replace the entire identity with the provided identity document. This operation SHOULD only be accessible to the owner of the identity. |
| DELETE | Deletes the identity. This operation SHOULD only be accessible to the owner of the identity. |
Not every Web application is capable of pre-arranging access to an identity, performing HTTP Signatures [[!HTTP-SIGNATURES]], or executing HTTP PATCH requests. In these cases, a regular HTTP POST mechanism is provided for Web applications to read, write, and query information about the identity.
| POST Parameter | Description of Action |
|---|---|
| action=query | Performs a query on the identity given a JSON-LD Frame in the POST body. |
| action=patch | Modify information in the identity using the JSON Patch [[!JSON-PATCH]] protocol. |
Reading identity information can be performed in 3 different ways depending on the sensitivity of the information being accessed. An identity provider SHOULD ensure that sensitive information is always transmitted and received over a secure channel, such as TLS [[!TLS]].
An identity can be accessed using a regular HTTP GET on the identity URL:
GET /identities/alice HTTP/1.1 Host: example.org Date: Tue, 07 Jun 2013 20:51:35 GMT
If the Content-Type
HTTP Header is not specified, a response using
the application/ld+json
content type must be provided. Other
content types MAY be negotiated for between the client and server. The
application/ld+json
content type is the only content type that
MUST be supported for all requests in this specification.
The result of the GET request SHOULD be information deemed to be public by the identity owner:
{ "@context": "https://w3id.org/identity/v1", "id": "https://example.org/identities/alice", "type": ["Identity", "Person"], "name": "Alice Smith" "publicKey": [{ "id": "https://example.org/identities/alice/keys/1" }] }
As the response above shows, the only information that the
identity owner has specified as being public is their
name
and a reference to their publicKey
.
In order to access identity information that is not public, the request SHOULD be authenticated and authorized against a known identity. The HTTP Signatures [[!HTTP-SIGNATURES]] specification is used to digitally sign the request:
GET /identities/alice HTTP/1.1 Host: example.org Date: Tue, 07 Jun 2013 20:52:12 GMT Content-Type: application/ld+json Authorization: Signature keyId="http://example.org/identities/bob/keys/4", algorithm="rsa-sha256", headers="(request-line) host date content-type", signature="Gm7W/r+e90REDpWyt.../VebAsNUtvQMe6cTjnDY="
The result of the GET request will now include information that the credential consumer has been pre-authorized to read by the identity owner:
{ "@context": "https://w3id.org/identity/v1", "id": "https://example.org/identities/alice", "type": ["Identity", "Person"], "name": "Alice Smith", "email"<EMAIL_ADDRESS>"mobileNumber": "4424672637162", "publicKey": [{ "id": "https://example.org/identities/alice/keys/1" }] }
As the response above shows, in addition to the public information, the
identity owner has authorized the credential consumer to
access their email
and mobileNumber
as well.
In the event that the credential consumer has not authorized itself prior to the request, or if it is not capable of performing an HTTP Signature [[!HTTP-SIGNATURES]], it may utilize a POST-and-callback-based approach. The following diagram provides an overview of how the POST-and-callback-based approach works:
Once the credential consumer has tried to access a protected resource, the website can request a particular set of credentials from the customer:
POST /query?credentials=true&callback=https://flights.example.org/verify?session=7f8nddn HTTP/1.1 Host: login-hub.com Date: Tue, 07 Jun 2013 20:52:12 GMT Content-Type: application/ld+json { "@context": "https://w3id.org/identity/v1", "id": "", "name": "", "governmentId": "", "birthdate": "" }
The result of the POST request will be a dialog that the identity provider displays to the identity owner asking them to verify the information that will be transmitted to the credential consumer. The mechanism used to present this dialog to the identity owner is outside of the scope of this specification. The result of a successful interaction with the verification dialog will be a POST back to the callback URL provided by the credential consumer:
POST /verify?session=7f8nddn HTTP/1.1 Host: flights.example.org Date: Tue, 07 Jun 2013 20:53:28 GMT Content-Type: application/ld+json { "@context": "https://w3id.org/identity/v1", "id": "https://example.org/identities/alice", "type": ["Identity", "Person"], "name": "Alice Smith", "birthdate": "1988-11-02", "governmentId": "321-54-9876" "credential": [{ "id": "http://ssa.us.gov/credential/8273", "type": "PassportCredential", "claim": { "id": "https://example.org/identities/alice", "name": "Alice Smith", "birthdate": "1988-11-02", "governmentId": "321-54-9876" }, "expires": "2017-02-04", "signature": { "type": "GraphSignature2012", "creator": "https://ssa.us.gov/keys/27", "signature": "fhhfiq3q9f8ahfh3q029rhaishsidfhf3780ey" } }] }
As the response above shows, the identity owner accepted the
request for information and the identity provider has performed
a POST to the callback URL provided by the credential consumer via the
identity owner's web browser. Since the request included the
credentials=true
flag, the credentials for the information
requested have been included so that the credential consumer may
validate the information against the third party credentials.
It is possible for a third party to provide digitally signed credentials to be stored with an identity. For example, if an individual would like to store digitally signed credentials verifiying their citizenship information, they would go through the following process:
There are two mechanisms that allow a third party to write information to an identity document. The first is an HTTP Signature [[!HTTP-SIGNATURES]] based mechanism that allows any authorized client to write data that has been pre-approved by the entity that controls access to the identity information. The second is to use a browser-based mechanism that POSTs a patch request to an identity document, allowing the identity owner to interactively decide what data to write to the identity document.
The example below demonstrates a digitally signed request to write information to a specific identity document using an HTTP Signature:
POST /identities/alice?action=patch HTTP/1.1 Host: example.org Date: Tue, 07 Jun 2013 20:52:12 GMT Content-Type: application/json-patch+json Authorization: Signature keyId="https://ssa.us.gov/keys/27", algorithm="rsa-sha256", headers="(request-line) host date content-type", signature="Gm7W/r+e90REDpWyt.../VebAsNUtvQMe6cTjnDY=" { "op": "add", "path": "https://w3id.org/identity#credential", "value": { "@context": "https://w3id.org/identity/v1", "id": "http://ssa.us.gov/credential/8273", "type": "PassportCredential", "claim": { "id": "https://example.org/identities/alice", "name": "Alice Smith", "birthdate": "1988-11-02", "governmentId": "321-54-9876" }, "expires": "2017-02-04", "signature": { "type": "GraphSignature2012", "creator": "https://ssa.us.gov/keys/27", "signature": "r+e90REDpW....bAsNUtvQM" } } }
The example below demonstrates an unsigned request to write information to a specific identity document. Since the request is unsigned, the identity provider would initiate an interactive authorization where the identity owner would verify that the information to be written is acceptable. The specifics of the interactive authorization flow are outside the scope of this document, but are roughly outlined in the diagram below:
The data that is sent back and forth is outlined below:
POST /create?action=patch HTTP/1.1 Host: login-hub.com Date: Tue, 07 Jun 2013 20:52:12 GMT Content-Type: application/json-patch+json { "op": "add", "path": "https://w3id.org/identity#credential", "value": { "@context": "https://w3id.org/identity/v1", "id": "http://ssa.us.gov/credential/8273", "type": "PassportCredential", "claim": { "id": "https://example.org/identities/alice", "name": "Alice Smith", "birthdate": "1988-11-02", "governmentId": "321-54-9876" }, "expires": "2017-02-04", "signature": { "type": "GraphSignature2012", "creator": "https://ssa.us.gov/keys/27", "signature": "r+e90REDpW....bAsNUtvQM" } } }
The format for the message above is JSON-PATCH where the path
value is the complete URL for JSON-LD property to add to the
identity document.
It is possible to use the mechanism described in this specification to login to a website in much the same way that Persona enables a verified email login. The process is described below:
The diagram below outlines the basic login flow described above.
In the following example, a login prompt is provided on
store.example.org
where the person that is logging in provides
the<EMAIL_ADDRESS>email address. The first step constitutes
store.example.org
fetching the identity endpoint information
from example.com
:
GET /.well-known/identity HTTP/1.1 Host: example.com Date: Wed, 08 Jun 2013 22:54:42 GMT Content-Type: application/ld+json
A successful retrieval of the identity service endpoint will result in the following document:
HTTP/1.1 200 OK Content-Type: application/ld+json Content-Length: 34 Date: Wed, 08 Jun 2013 22:54:43 GMT { "@context": "https://w3id.org/identity/v1", "identityService": "https://example.com/identities" }
The store.example.org
software may then construct the proper query
to the identity service:
POST /identities?action=query&credentials=true&callback=https://store.example.org/verify?session=8d73j320s HTTP/1.1 Host: example.com Date: Wed, 08 Jun 2013 22:54:44 GMT Content-Type: application/ld+json { "@context": "https://w3id.org/identity/v1", "email"<EMAIL_ADDRESS>}
After a UI interaction with Alice on example.com
verifies that
the email information should be sent to store.example.org
,
the following message is transmitted from Alice's user agent to
store.example.org
:
POST https://store.example.org/verify?session=8d73j320s HTTP/1.1 Host: example.org Date: Wed, 08 Jun 2013 22:55:15 GMT Content-Type: application/ld+json { "@context": "https://w3id.org/identity/v1", "id": "https://example.com/identities/asmith", "type": "Identity", "email"<EMAIL_ADDRESS>"credential": [{ "id": "http://example.com/credentials/23894", "type": "EmailCredential", "claim": { "id": "https://example.com/identities/asmith", "email"<EMAIL_ADDRESS>}, "expires": "2015-02-04", "signature": { "type": "GraphSignature2012", "creator": "https://example.com/keys/24", "signature": "jf48901fu41...23908aszfhdk23h9f" } }] }
Note that for the purposes of simplicity in the example above, there is
no tracking protection to prevent example.com
from knowing which
website Alice is logging in to. Tracking protection is easily implemented by
adding a trusted third party, such as the browser UI or a third party mixer service,
that decouples the identity provider from the relying party.
This identity mechanism is designed to be compatible with other identity mechanisms in use today such as OpenID, Facebook Connect, and Firefox ID.
The identity mechanism is such that it can be returned in a Mozilla Persona or FxID-based login. The assertion returned to the FxID-enabled website would contain an identity URL which would be compatible with this specification. This allows both the basic email address to the validated, and extension information (such as citizenship information, age assertions) to be discoverable after the login.
{ "public-key": { "algorithm": "DS", "y": "8e65e949e2e...1263ea6", "p": "ff600483dab...7fc26d0", "q": "e21e04f91d1...ecaab3b", "g": "c52a4a0ff34...233397a" }, "principal": { "@context": "https://w3id.org/identity/v1", "email"<EMAIL_ADDRESS>"identity": "https://example.org/identities/alice" <--- This bootstraps the identity assertion discovery process }, "iat":<PHONE_NUMBER>513, "exp":<PHONE_NUMBER>513, "iss": "example.org" }


Evers vetoes nursing aide training hours bill
MADISON, Wis. - Democratic Gov. Tony Evers has vetoed a Republican bill that would have made it easier to become a nurse's aide in Wisconsin.
State law currently requires nursing aide training programs to be at least 120 hours long. Federal regulations call for a minimum of 75 hours. The bill would have prohibited state health officials from requiring nurses' aides obtain more than 75 hours of training.
Evers vetoed the bill Wednesday, saying in his veto message that he objects to less training for those who care for Wisconsin's more vulnerable citizens. He says there's better ways to address the shortage of nursing aides than reducing the quality of training.
The bill's authors, Sen. Rob Cowles and Rep. Warren Petryk, called the measure a reasonable attempt to create more nursing aides. Petryk said Evers is disregarding people who need health care.
Editor's note: In a previous version of the story, The Associated Press reported that the bill would have reduced the number of training hours that nurses would have to complete. The story has been updated to reflect that it would have reduced the number of training hours that nursing aides would have to complete.


Most of the climbing done in modern times is considered free climbing—climbing using one's own physical strength, with equipment used solely as protection and not as support—as opposed to aid climbing, the gear-dependent form of climbing that was dominant in the sport's earlier days. Free climbing is typically divided into several styles that differ from one another depending on the choice of equipment used and the configurations of their belay, rope and anchor systems.
As routes get higher off the ground, the increased risk of life-threatening injuries necessitates additional safety measures. A variety of specialized climbing techniques and climbing equipment exists to provide that safety. Climbers will usually work in pairs and utilize a system of ropes and anchors designed to catch falls. Ropes and anchors can be configured in different ways to suit many styles of climbing, and roped climbing is thus divided into further sub-types that vary based on how their belay systems are set up. Generally speaking, beginners will start with top roping and/or easy bouldering and work their way up to lead climbing and beyond.
Aid climbing
Still the most popular method of climbing big walls, aid climbers make progress up a wall by repeatedly placing and weighting gear that is used directly to aid ascent and enhance safety.
Free climbing
The most commonly used method to ascend climbs refers to climbs where the climber's own physical strength and skill are relied on to accomplish the climb. Free climbing may rely on top rope belay systems, or on lead climbing to establish protection and the belay stations. Anchors, ropes and protection are used to back up the climber and are passive as opposed to active ascending aids. Subtypes of free climbing are trad climbing and sport climbing. Free climbing is generally done as "clean lead" meaning no pitons or pins are used as protection.
Bouldering
Climbing on short, low routes without the use of the safety rope that is typical of most other styles. Protection, if used at all, typically consists of a cushioned bouldering pad below the route and a spotter, a person who watches from below and directs the fall of the climber away from hazardous areas. Bouldering may be an arena for intense and relatively safe competition, resulting in exceptionally high difficulty standards.
Deep-water soloing (DWS)
Similar to free soloing in that the climber is unprotected and without a rope, but different in that if the climber falls, it is into deep water instead of on to the ground.
Free soloing
Free soloing is single-person climbing without the use of any rope or protection system whatsoever. If a fall occurs and the climber is not over water (as in the case of deep water soloing), the climber is likely to be killed or seriously injured. Though technically similar to bouldering, free solo climbing typically refers to routes that are far taller and/or far more lethal than bouldering. The term "highball" is used to refer to climbing on the boundary between free soloing and bouldering, where what is usually climbed as a boulder problem may be high enough for a fall to cause serious injury (20 ft. and higher) and hence could also be considered to be a free solo.
Roped solo climbing
Solo climbing with a rope secured at the beginning of the climb allowing a climber to self-belay as they advance. Once the pitch is completed the soloist must descend the rope to retrieve their gear, and then reclimb the pitch. This form of climbing can be conducted free or as a form of aid climbing.
Lead climbing
Leader belays the second on Illusion Dweller in Joshua Tree National Park, United States.
Lead climbing is a climbing technique. The lead climber ascends with the rope passing through intermittent anchors that are below them, rather than through a top anchor, as in a top-roped climb. A partner belays from below the lead climber, by feeding out enough rope to allow upward progression without undue slack. As the leader progresses he or she clips the rope into, using a runner and carabiners, intermediate points of protection such as active cams, or passive protection such as nuts; this limits the length of a potential fall. The leader also may clip into pre-placed bolts. Indoor gyms might have short runners pre-attached to fixed anchor points in the wall.
Unlike top-rope climbing where the climber is always supported by an anchor located above the climber, lead climbing often has scenarios where the climber will be attached to a point under him or her. In these cases, if the climber were to fall, the distance fallen would be much greater than that of top-rope and this is one of the main reasons lead climbing can be dangerous. The fall factor is the ratio of the height a climbers falls and the length of rope available to absorb the fall. The higher the fall factor, the more force placed on the climber as the ropes decelerates them. The maximum fall factor is 2. It is often advised that climbers who are interested in lead climbing should learn from experienced climbers and participate in training sessions before actually lead climbing on their own.
Multi-pitch climbing
Because the climbing rope is of a fixed length, the climber can only climb a certain distance. Thus longer routes are broken up into several pitches; this is known as multi-pitch climbing. At the top of a pitch, the leader, the first climber to ascend, sets up an anchor and then belays the second up to the anchor; as the second follows the route taken by the leader, the second removes the equipment placed along the way in order to use it again on the next pitch. Once both climbers are at the anchor, the leader begins climbing the next pitch and so on until the top is reached.
In either case, upon completion of a route, climbers can walk back down if an alternate descent path exists, or rappel (abseil) down with the rope.
Sport climbing
Unlike traditional rock climbing, sport climbing involves the use of protection (bolts) or permanent anchors which are attached to the rock walls.
Traditional climbing
Traditional or trad climbing involves rock climbing routes in which protection against falls is placed by the climber while ascending. Gear is used to protect against falls but not to aid the ascent directly.
Bottom rope climbing
Commonly known as "Top Roping": belaying a climber from the ground or the base of the route. A belay system resembling a pulley in which an anchor has been created at the top of a climb, through which the rope runs through from the belayer on the ground, to the climber on the ground (position before starting the climb). The rope is "taken-in", to clear up the slack as the climber moves upwards, so in the event of a fall the climber falls the shortest distance possible. The length of a fall is normally no more than a meter, but can vary depending on the length of the route (the longer the rope, the more stretch the rope will undergo when weighted) and the weight of the climber compared to that of the belayer, among other things.
Top rope climbing
Also known as "seconding," or belaying a climber from the top of a route, bringing them up to walk off or continue on to next pitch. A similarly safe system of climbing a route, except the belayer has set the anchors at the top of the climb (normally after leading a route) to belay the climber either indirectly (belayer is part of the system and can be vunlnerable when exposed to unexpected directions of pull and loading of the rope) or directly (belayer is not part of the system and belaying is done direct from the anchors using either an Italian / Munter Hitch or adapted use of a belay device), up the route from the top. If bolts have been clipped or traditional gear placements have been made, it is the job of the climber to collect and clean the route.


--- title: Dudley and Walsall Mental Health Partnership NHS Trust layout: gb ---
| Resource | Fetch | Format | Columns | Data | Valid | Entries | Oldest | Latest | Total (GBP) | |
|---|---|---|---|---|---|---|---|---|---|---|
| Spend over £25,000 in Dudley and Walsall Mental Health Partnership NHS Trust | ||||||||||
| 2010 October return | ✔ | ✔ | ✔ | ✔ | ✔ | 25 | 2010-10-01 | 2010-10-22 | 1763418.96 | |
| 2010 April - September return | ✔ | ✔ | ✔ | ✔ | ✔ | 217 | 2010-04-06 | 2010-09-29 | 10322980.16 |
| Resource/Stage | Error |


Once upon a time there lived in a certain village a little country girl, the prettiest creature was ever seen. Her mother was excessively fond of her; and her grandmother doted on her still more. This good woman had made for her a little red riding-hood; which became the girl so extremely well that everybody called her Little Red Riding-Hood.
One day her mother, having made some custards, said to her:
“Go, my dear, and see how thy grandmamma does, for I hear she has been very ill; carry her a custard, and this little pot of butter.”
Little Red Riding-Hood set out immediately to go to her grandmother, who lived in another village.
As she was going through the wood, she met with Gaffer Wolf, who had a very great mind to eat her up, but he dared not, because of some faggot-makers hard by in the forest. He asked her whither she was going. The poor child, who did not know that it was dangerous to stay and hear a wolf talk, said to him:
“I am going to see my grandmamma and carry her a custard and a little pot of butter from my mamma.”
“Does she live far off?” said the Wolf.
“Oh! ay,” answered Little Red Riding-Hood; “it is beyond that mill you see there, at the first house in the village.”
“Well,” said the Wolf, “and I’ll go and see her too. I’ll go this way and you go that, and we shall see who will be there soonest.”
The Wolf began to run as fast as he could, taking the nearest way, and the little girl went by that farthest about, diverting herself in gathering nuts, running after butterflies, and making nosegays of such little flowers as she met with. The Wolf was not long before he got to the old woman’s house. He knocked at the door—tap, tap.

The good grandmother, who was in bed, because she was somewhat ill, cried out:
“Pull the bobbin, and the latch will go up.”
The Wolf pulled the bobbin, and the door opened, and then presently he fell upon the good woman and ate her up in a moment, for it was above three days that he had not touched a bit. He then shut the door and went into the grandmother’s bed, expecting Little Red Riding-Hood, who came some time afterward and knocked at the door—tap, tap.
“Who’s there?”

The Wolf cried out to her, softening his voice as much as he could:
“Pull the bobbin, and the latch will go up.”
Little Red Riding-Hood pulled the bobbin, and the door opened.
The Wolf, seeing her come in, said to her, hiding himself under the bed-clothes:
“Put the custard and the little pot of butter upon the stool, and come and lie down with me.”
Little Red Riding-Hood undressed herself and went into bed, where, being greatly amazed to see how her grandmother looked in her night-clothes, she said to her:
“Grandmamma, what great arms you have got!”
“That is the better to hug thee, my dear.”
“Grandmamma, what great legs you have got!”
“That is to run the better, my child.”
“Grandmamma, what great ears you have got!”
“That is to hear the better, my child.”
“Grandmamma, what great eyes you have got!”
“It is to see the better, my child.”
“Grandmamma, what great teeth you have got!”
“That is to eat thee up.”


?TRUMAN
G.
YUNCKER
HER8ARI
OF
DEPAUW
UNIVERSITY
(DPU)
PURCHASED
BY
NY
IN
1987
NEW
YORK
BOTANICAL
GARDEN
<8>
imaged
/
Mus.
Botan.
Stockholm.
Plant¾
Indi¾
Occidentalis
N:o
(rfyw.J
^-Áloaxv-
Hispaniola.
Civ.
Santo
Domingo
:
01
529857
Fdepauw
UN
IV
^HERBARIUM.
5ZT,
19j2£
leg.
E.
L.
Ekman.
01529857
Legend -
Level of confidence that token is an accurately-transcribed word
extremely low
very low
low
undetermined
medium
high
very high


menu
Home
Rooms
Gallery
Services
Environment
Find us
Contact
Error sending your message
Sorry! An error has occurred sending your message. Try it again after few seconds.


Master’s Thesis - Offensive Language Detection
To predict whether a given tweet is offensive or not.
(Read more)
IIRIS Consulting, Gurgoan, India
- Exhaustive Research on use cases (Highway and Swimming pool security) of
Artificial Intelligence and Machine Learning in Physical Security Operations.
- Designed high quality physical security layout using AUTOCAD for
collaboration with ORACLE which is client of IIRIS.
- Worked in Command Centre Design of GENPACT Gurgaon office.
Waddaya Solutions Pvt.Ltd,New Delhi, India
- Worked with SAP GUI, Configuration and Navigation within Unix environment OS.
- Performed User Activities like Creation, Password reset, Lock / Unlock user at
the client side technical support.
- Roles Creation and Authorization as per client side to enhance customer
experience and solve technical issues.
Sidh Global Food Products ( GOLDEN LID )
- Involved in the creation of the end-to-end website of the entrepreneurial
brand for better user experience and administration.
- Branding of the products through Digital Marketing.
- Data Analysis (Excel) of customer buying patterns to induce the promotions
and to optimize manufacturing of the different products at the right time.
- Worked on creating the differentiation in the product (home-made and pure
quality) - Emerged as the costliest pickle in the Indian market due to
customer satisfaction.


This was our first robot. He was modeled after the famous movie character E.T.
This was our second robot. He makes a mean martini!
This is our newest model. This one will follow you around the house.


§1: The first rule of Fight Club is: You do not talk about Fight Club.
§2: The second rule of Fight Club is: You do not talk about Fight Club.


Welcome to the admin dashboard! Use the buttons to toggle between data about the text-messaging and the web tool.
{% include 'partials/dashboard-data.html' with type='sms' overview_title='Text Messaging' open_sessions=sms_open_sessions canceled_sessions=sms_canceled_sessions percentage_canceled=sms_percentage_canceled completed_sessions=sms_completed_sessions percentage_complete=sms_percentage_complete %}
{% include 'partials/dashboard-data.html' with type='web' overview_title='Web' open_sessions=web_open_sessions canceled_sessions=web_canceled_sessions percentage_canceled=web_percentage_canceled completed_sessions=web_completed_sessions percentage_complete=web_percentage_complete %}