Research and Innovations Digital applications are allowing seeing a health care provider from the comfort of your home possible while avoiding wait times and staying secure.
The house call is experiencing a revival, courtesy of digital apps offering patients health care services in the comfort of their home.
Presented as a solution to overcrowded clinics and hospital emergency rooms, the vision is to create a seamless experience where patients can efficiently access quality health care services — right at home.
"Canadians are disappointed with wait times. Patients can now receive health care comfortably at home, select who treats them and when, and providers can choose whom they see, when, and where. It's a win-win for them and the system," says Daniel Warner, founder and CEO of MediSeen, a secure, digital house call platform, based in Ontario.
"Health care providers, like physicians, can build their own house call practice, by defining their coverage area, and patients can browse and select a provider, with visibility of the services, schedule, languages spoken and more," Warner explains. Each provider is carefully vetted before joining the network, providing a layer of comfort and security for patients.
Digitizing the process allows patients to view and download their medical documentation. "This new type of multi-service, secure platform that enables patient access and self-determination doesn't currently exist in the health care space," says Elise Devlin, Vice President of Clinical Strategy at MediSeen.


When you think about it, you will realise you spend a fair bit of your time in your car – whether driving or as a passenger. While you are in your car, even though you are enclosed, you are still exposed to heat and UV rays. Often in the summer, your air-conditioner is pumped at all times, even if it's just for a short trip to the supermarket.
Window tinting can be used as protection against the sun and other types of harsh weather environments in your car, home or office. It's important to keep your body safe – and why not save on using that harsh air-conditioner while you're at it?
How Does Window Tinting Protect You in Your Car?
In your car: Avoid that awful and unsafe "driver's arm" where your arm is repetitively burnt due to the heat radiating from your windows. Tinting in your car will also reduce eye strain from the harsh sunlight, potentially protecting you from driver fatigue.
How Does Reducing Heat and UV Protect You in Your Home or Office?
A more natural heating or cooling system: Not only is it cheaper but keeping the sun and UV out means you don't need to have artificial heating and cooling systems on all the time. Air-con can be bad for your breathing and bad for your skin and artificial heating can also be very expensive.
A barrier for your interiors: Window tinting will stop the harsh sun and UV from fading your home or office interiors.
Which Window Tints are best to Reduce Heat and UV?
The darker the tint, the better it will be in protecting you from heat and UV. In Australia, though, automotive window tints must maintain 35% visible light transmittance into the vehicle, so you can't make your window tint incredibly dark.
Find the Best Window Tint to Reduce Heat and UV?
If you've decided to tint your windows, then you really need to consider going somewhere that will not only consult with you on the best shade for your home or office but will also provide you with a great product you can trust. All Aspects Window Tinting is proud to offer Centennium Automotive and 3M Window Film that comes with a lifetime guarantee. We also provide a range of products and types of tinting for your home or office. Contact us at our office in Rouse Hill today for your obligation-free quote – we service the entire Hills district.


Comments: My mother Maria Madrid (Anaya) was born @ Chaparito, I'm trying to collect info on my grandparents; Gregorio Madrid & Juanita (Anita) Sanchez; and anyone beyond these people??
Comments: Joe, I have compiled the census for Chaperito (1860-1930). When was your mother born or grandparents, maybe I can help?? There are Madrid's listed.
Comments: Severa Chavez Estrada..do you have any information on the following surnames, Pacheco, Urioste or Garduno?


text:
The Quiet Man 70th Anniversary presented by TCM (G)
Directed By: John Ford
Genre: Program
Run Time: 2 hr. 20 min.
Fathom Events, Turner Classic Movies and Paramount Pictures are bringing The Quiet Man to select cinemas on March 13 and 17, including exclusive insights from TCM. Celebrating 70 years, John Ford's THE QUIET MAN is simply one of the greatest love stories ever told. John Wayne is retired boxer Sean Thornton who makes a pilgrimage to his home village in Ireland in order to claim his family's estate. He meets his match in the spirited young Mary Kate Danaher (Maureen O'Hara) only to find himself confronted by her belligerent brother and the town's strict customs. An Oscar winner for Best Director and Cinematography, this Republic Pictures classic lives on in the hearts of moviegoers and moviemakers alike.

redpajama_set_name: RedPajamaCommonCrawl


text:
cartels, collusion, dominance, draft, East Africa, Kenya, legislation, leniency / amnesty, Media, Telecoms, Uncategorized
Kenya competition landscape active
September 15, 2014 Editordraft, leniency, MultiChoice, pay TV Leave a comment
Zuku pay-TV launched complaint against DStv in Kenya
As we reported in "Your Choice", MultiChoice has been an active (if unwilling) player in African antitrust news. Zuku pay-TV has recently requested the Competition Authority of Kenya (CAK) to impose a financial penalty on DStv for refusing to re-sell some of its exclusive content like the English Premier League to its rivals.
In its letter to the CAK, Zuku pay-TV accuses MultiChoice, the owners of DStv, of abusing its dominance and curbing the growth of other, competing pay-TV operators. Furthermore, Zuku pay-TV requested the CAK to compel DStv to re-sell some of its exclusive content and impose a financial penalty, which can be up to 10 per cent of a firm's annual sales, on the South Africa firm. According to Zuku pay-TV, DStv has a market share of 95% in Kenya.
The CAK has not indicated whether it is investigating the complaint yet.
Mr Wang'ombe Kariuki, director of the CAK
Kenya to get leniency policy
In addition to the ongoing pay-TV antitrust dispute, the CAK has drafted a law (the Finance Bill of 2014) which will create a Kenyan cartel leniency programme in order for whistleblower companies and their directors to get off with lighter punishment, for volunteering information that helps to break up cartels, as AAT reported here.
To recap the leniency programme will either grant full immunity for applicants or reduce the applicant's fines, depending on the circumstances. The Finance Act 2014 is awaiting its third reading in Parliament.
The introduction of a leniency programme in Kenya is a pleasing sight due to leniency programmes' proving to be an integral and vital tool for uncovering cartels in every jurisdiction in which it has been deployed.
→ Antitrust enforcer subjects mobile payment operator to central bank oversight
← Unfair competitors or clever innovators? Lessons from the sharing economy.


Pope Francis could make a flying visit to Scotland in September, according to reports.
The Pope has "pencilled in" a short visit to St Andrews to sign a charter calling on all faiths to unite against extremism, the Sunday Times reports.
Mario Aguilar, professor of religion and politics at St Andrews University, received a letter from Rome, via the Vatican embassy in London, saying that the invitation to the Pope was being considered.
"My understanding is that Pope Francis is interested and has put [the event] on his agenda of activities and that further arrangements will be discussed," Aguilar, who has met Francis on several occasions and wrote a biography of the Pontiff in 2014, told the Sunday Times.
Pope Francis's trip to Scotland, which would probably take place over the course of one day, would follow Benedict XVI's visit to the country in 2010.
St Andrews has designated 2016 as a "year of inter-faith dialogue", with a programme of lectures and events scheduled.


Posted on July 22, 2015 by Filipe M.
Shooting to a specific format other than your camera's native aspect ratio isn't always an easy task. Here's how to fix that with a piece of card, a printer, a cutting tool, and a few minutes.
Often when shooting for clients you'll be required to "shoot to a specific format": it might be an 8.5×11″ for a full page in a magazine, a 11×14″ wall portrait, a facebook banner at 851×315 px, or just a 16:9 wide image, with no final dimensions provided, to insert stills into video. These seemingly random numbers define either the output size of the image (in y x z units), or an aspect ratio – the ratio between your image width w and height h, expressed in w:h.
In reality, the output size can also be considered an aspect ratio: just strip away the units. In some cases, you might have to divide both numbers by a common factor to get to the lowest possible integers, e.g., an 8×10″ uses the 4:5 aspect ratio (both values divided by 2). And obviously, the difference between a 4:5 and a 5:4 is the camera orientation!
Since these are all completely different to the traditional 3:2 aspect ratio of most DSLRs or 4:3 of m4/3's cameras, knowing how much to crop, or how to create your composition to fit the final crop can be quite challenging. Shooting tethered is probably the best away around this problem, but it isn't always practical to do so.
Some cameras attempt to make this task easier by providing a few built-in crop modes, such as 4:3 or 5:4, complete with viewfinder masks to help with composition. Some others, such as the Leica D-Lux Typ 109 / Panasonic LX100, use different sensor areas to provide a few native aspect ratios, giving you as many pixels as possible in the final file while still keeping the overall camera size "pocketable".
But what happens if you're stuck with a camera that doesn't have these features, or you need something different than the built-in formats and aspect ratios?
Step 3 – Draw or print a rectangle with those dimensions on a piece of thick stock and cut it out.
To make sure you're using as much screen real estate as possible, and consequently the biggest output file size with no unnecesssary cropping, it is advisable to use matte frames that are matched to your LCD's image size.
Measuring it is really easy: take a photo of something bright (don't worry about focus or correct exposure – just make it really bright), then scroll through the view modes to find the one that gives you the biggest possible image – that's the mode you will want to use your matte frame with; grab your ruler and measure both width and height of the image (be careful not to scratch the LCD!).
Use the edges of the frame as guide to avoid measuring in diagonals and be as precise as you can, but there's no need to overdo it. Write down these numbers, as you'll need them in step 2.
The maths involved are quite simple, and to make them even simpler we've created a Google spreadsheet for you: just plug in your image measurements from Step 1 and desired aspect ratio and it'll calculate your matte frame dimensions automatically.
We'll start by finding out the aspect ratio of your camera. Take the numbers you've measured in Step 1 and divide the width by the height. If you're shooting with a DSLR, it should be 1.5 or *very* close to it (3:2). If it's a m4/3 camera, it should be 1.33 or again, really close to it (4:3). If not, make sure your measurement procedure was correct.
and obviously, if you want a square 1:1 ratio, the width of the cutout is going to be the same as your image's measured height.
Note: If you use the imperial system rather than metric, the principle still applies: since the aspect ratio doesn't need units, the output units are going to be the same you used as the input.
This step is fairly obvious: take the numbers you got in Step 2, draw or use your favourite design software to print a rectangle with these dimensions on a piece of card that's at least 1/2″ larger in all directions, and cut the rectangle out – and there's your brand new matte frame.
Print on A4 or Letter sized thick stock, cut along the dotted lines, and you're good to go! If your camera isn't on the list, just leave us a comment with your camera make, model, and image dimensions (measured according to step 1 above) and we'll create a template for you.
UPDATE: the original templates for the Nikon D7000 and D7100 had errors on the 4:3, 11:8.5 and 5:4 ratios. They were fixed on v.1.1 | 2015.07.23, so please download them again and use the new ones. Sorry for the inconvenience!
Great idea! Do you have a template for a Canon 7D made? Thank you!
Wow! So informative – thank you. I've been wondering about aspect ratios, always hoping my crop in post-production will work out. I plan to tackle "the math" myself, with your thorough guidance. I love your videos!
could you make a set of templates for this camera please?
And done, original Canon 5D added to the list!
i have a panasonic GH4.
Do you have a template for the 2.35: 1 – Cinemascope ?


I live near pacifica on the San Mateo county coast, I have a 10'-6" 3/4-4oz ODM Frontier X, im looking for suggestions on what reel you guys would recommend I pair it with for this upcoming surf striper season. I've been doing some homework and looking at all the forums, and with the new year comes new gear so the one thing besides waders and lures im going to buy is a new reel, not looking to spend a fortune but also nothing cheap, maybe $150-$500 range (i know its a little much for our weat coast stripeds but I will be going to mexico for surf fishing as well).........at least this justifies my spending to myself thanks for the help.
Thanks, Ill have to check that reel out. I just bought a Penn Slammer 3 4500 on sale on Amazon for $125 so I couldn't pass it up but I'm wishing I would've bought the 5500 instead as the 4500 doesn't seem to balance out the rod too great. The striper season out on the SM county coast is May-ish through August, and they are all up and down the coast, I usually fish Pacifica or San Francisco, right now is the time to hit the stockton area, there stripers are biting out there right now!
Lots of options, models, service your own reels etc.
Though dunking is unlikely in NorCal coast, accidents can happen, so something to consider.
Personal biased recommendation; Stradic 5000, Saragosa 6000SW, Biomaster 6000SW.
How was the slammer 4500 out of the box, I also picked one up for $125 but it was really stiff and didn't have that new silky feel compared to my BG and Stradic reels. Would it being sealed account for that stiffness, there was also a slight rubbing sound from inside and I ended up sending it back and getting a replacement which I haven't received yet. I expected it to feel a lot better than it was and was kinda disappointed.
My slammer seems fine and smooth, maybe its just the feeling of the seals. My BG is smoother but the slammer is sealed. All in all i am happy with my purchase, but I believe the 4500 is a little small for my 10'-6" Frontier. I will look to either trade it for a 5500 or sel it so I can buy the 5500. I am also happy that the reel i recieves came with tve upgraded line roller baring. Good luck with your slammer, we got a hell of a deal!
A VR175/200 should balance that rod well, and is lightweight while sealed enough to withstand most of our West Coast fishing.
I use different reels in Mexico because you want your retrieve to be minimum 49"/crank. That doesn't mean the VR's won't work in Mexico, I think the 200 is something like 40" per crank but you'll just have to work a little harder.
The slammers have a sealed drag, I don't think the rest of the reel is sealed, so you'll still need to be careful in sand and water. The Penn Torque II's are better suited if you plan on dunking your reel (and want to go with Penn).
Thanks, after reading a lot more on the forums, I'm now saving up for a VSX Van Staal reel. I have about $600 saved up right now, hopefully in the next 2 weeks I'll have the rest. Everyone on the other forums (mostly east coast guys) seem to recommend the VSX200 which weights around 21oz, plus my rod at 12oz would be around 33oz setup......seems somewhat heavy for continuous surf casting, but also versatile, what would you guys think about a VSX150 at only 12oz? seems kinda small for my rod. any west coast opinions on this?
Agree with Moocks here, although the Gosa is a fairly different route with reel choice, sacrificing the sealed factor of a reel in favor of weight and smoothness. Can't go wrong though! At the $600+ range you could likely find a used Stella or Saltiga.
A 150vsx bailed would be fine on the 9'6 Frontier. The bail less version may seem light. (The bailed version has an extended reel foot and weighs considerably more than the bail less).
Remember the East coast guys fish different water and techniques than we do and often harsher conditions. Rarely are we swimming with our reels or fishing them underwater. If you plan on doing so then go with a VSX, otherwise any of the other reel suggestions here should suffice.
One last option is the ZX22, which is still on the heavy side but is sort of in between the size of a 150 and 200 VS.
Find a reel that balances. A tip heavy setup may feel heavier to fish despite lesser aggregate weight.
Hey i just wanted tk come back to this thread since i finally bought a new reel. Thank you all for you recommendations , i ended up going with a black van staal vsx200, i know, a little overkill for my area but love how well it balances the rod and i wont have to buy a reel that size for a long long time. Anyone else using a van staal out here?!
Very sweet set up btw!


Our Dover call center offers 302 area code numbers and serves the 19901, 19902, 19903, 19904, 19905 & 19906 zip code.
Because we partner with businesses and healthcare communities throughout Delaware, we understand local news, local weather and local pain points for your customers or patients. We keep our finger on the pulse of Dover business trends, medical practice mergers and breaking news. This allows us to make on-the-fly changes based on situations in your community. Professional industries hire us because we offer the most secure, highly trained, top quality call center available.


text:
That Woman Is Poison! is an album by the American R&B musician Rufus Thomas. Originally recorded for King Snake Records, it was released in 1988 via Alligator Records. Thomas was in his seventies when he made That Woman Is Poison!

Production
The backing band was put together by Bob Greenlee, the owner of King Snake. The musicians included the saxophonist Noble "Thin Man" Watts and the harmonica player Lazy Lester. That Woman Is Poison! was recorded in Sanford, Florida.

"The Walk" jokingly alludes to both Thomas's age and his previous dance hits "The Funky Chicken" and "Walking the Dog".

Critical reception

The Chicago Reader thought that Thomas "grinds out his blues with a sweaty crunch that puts to shame men 30 years his junior, and his sense of humor is as wicked as ever." The Crisis wrote that "Thomas uses a traditional blues sound, but struts his way through the vocals with a characteristic smirk." The Edmonton Journal determined that Thomas's "voice still contains the same rich textures as in the past, yet it lacks a sense of urgency."

The Globe and Mail called Thomas "still a great singer, with a full, throaty voice and a great sense of comic timing." The Sun Sentinel praised the "blistering" original songs, and wrote that the "horn work and arrangements are first rate." The Chicago Tribune concluded that "despite his years, Thomas is in top voice and spirit as he blusters, struts, hams it up, deftly draws from both Memphis blues and soul."

AllMusic deemed it "a masterful comeback album from a blues and soul veteran who was assumed to be ready for the retirement home."

Track listing

Personnel
Rufus Thomas - vocals
Bryan Bassett, Ernie Lancaster - guitar
Louis Villery - bass guitar
Bob Greenlee - bass guitar, baritone saxophone
Lucky Peterson - keyboards
Danny Best - drums
Kenny Neal - harmonica
Noble "Thin Man" Watts - tenor saxophone solos
Lawson "Buzz" Montsinger - tenor saxophone
Sylvester Polk - trumpet

References

Rufus Thomas albums
1988 albums
Alligator Records albums

redpajama_set_name: RedPajamaWikipedia


Six Nation State are set to release special 'video album'.
The band, who are playing this year's Camden Crawl festival, have announced that they will release films made by the group.
The Southampton band made short films for all the tracks on their self-titled debut album, and will be allowing fans to watch selected videos online throughout April before releasing the DVD in May.
Six Nation State have put the first preview from the release on Myspace.com/sixnationstatetheband .
The film for album track 'Taking Me Over' includes 50 fans who played zombies in the thriller, and is online now.
The group, who have just finished a tour of Europe, are set to play Camden Crawl 2008 alongside Does It Offend You, Yeah?, Operator Please and Crystal Castles on April 18.


Discontinued Tempest with 0.99 carat Princess Center and One Matching Band - 14k White Gold - Ring Size 5.0-7.0 was added to your cart.
The Tempest classic solitaire engagement ring features a stunning Princess cut Nexus Diamond™ alternative in an attractive basket setting. Its low profile is designed to dramatically reduce snagging.


Tim brings a lifetime of experience to the corps. His marching experience includes performing with the Rochester Crusaders, Syracuse Brigadiers, Connecticut Hurricanes, Magic of Orlando and Pioneer.
He has designed and taught for The Ghost Riders, as well as a being a Staff Member for The White Sabers from 2012-2017, serving as Ensemble Coordinator and Visual Caption Head in 2017.
He is currently the Visual Caption Head and Winds and Front Ensemble co-arranger for the 2017 NYS Field Band Champion Corning-Painted Post High School Marching Band, as well as the Assistant Director and Front Ensemble Arranger for their indoor Percussion Ensemble.
Keep up-to-date with us via our website, Skyliners Drum & Bugle Corps Website or contact Joshua Delanuez via email info [at] skylinersdbc [dot] org. The Skyliners Drum & Bugle Corps is a 501(c)3 non-profit, performance-based organization that provides quality educational opportunities for its members.
Posted by News Editor on Wednesday, October 10th, 2018. Filed under Current News, DCA News, FrontPage Feature.


text:
Summer Hockey
ClubHub
Dating back to 1939, Western Hockey is incredibly proud of its roots.
The Club history can be traced back to Owai Rovers Hockey Club, which was affiliated with the Auckland Hockey Association on March 27, 1939 with three teams, won it's first Championship in 1940 and reached Senior Status in 1942. A Ladies team was entered in 1940, but only lasted for three seasons.
In 1954 a few players from the Club decided to form a Club of young players who had attended Avondale College. This club was affiliated on April 21, 1954 as Avondale College Past Pupils Association, and had one team in the third grade. This team won the championship in it's first year, and again the year after! In 1956, the Club's name was changed to Avondale College Ex Students, which quickly became ACES. This Club won every grade that it entered for the next four years. However it did not manage to achieve promotion to Senior Status.
Meanwhile, Owai Rovers had continued, but was finding difficulties in fielding teams of strength in some grades. The club could also see the problems of ACES, and an approach was made about the two clubs amalgamating. Both clubs also knew that another group in Henderson was proposing to form a new Club, so this group was approached, in the hope of forming one strong Club.
As a result, Western Districts Hockey Club was formed at a meeting held March 1, 1958 by an amalgamation of the three groups. Affiliation with the Auckland Hockey Association was granted on March 13, 1958, and affiliation with the Ladies Association was granted on March 15, 1958.
The new Club immediately proved successful, and in the decade of the sixties became one of the strongest clubs in Auckland, winning many Championships in both Mens and Ladies Hockey. In 1983 the Club opened the Rob Henry Pavilion, which is the only all weather, fully enclosed Hockey Training Facility in New Zealand. This Pavilion is a great asset, allowing training to be carried out indoors, on turf, at any time of the day or night, no matter what the weather is like.
In 1999, the new Avondale College water based turf was opened on Rosebank Road, Avondale. The Club moved their home premises to the Avondale College Pavillion to take advantage of this fantastic facility and we have been there since.
Along with a brand new clubrooms facility, the water-based turf changed the game of hockey to a fast paced, skill based game which has attracted a host of new players to the game across Auckland. The Club has gone from strength to strength, with Western teams representing most grades in the Juniors, Youth and Senior divisions. Throughout the nineties and noughties the club has had an enthusiastic membership. We celebrated our Club's 50th Jubilee in 2008 and had a weekend of festivities to mark the occasion.
We have had many players travel to New Zealand to play hockey for our Club teams, including international representatives. We have also played host to several Black Sticks representatives who often transfer to our Club for an Auckland base during the NZ selection process, including Kyle Pontifex the former Black Sticks goalkeeper.
The Club highlights of the past decade include the Auckland Hockey Association Championship win by our Premier Ladies team in 2016 and Danielle Jones representing New Zealand in the Black Sticks team.
We look forward to continuing to grow our membership in the years to come and fostering a love of hockey amongst the local community.
Here are some words from international players who've played for Western in the past
Julian Dapena - Argentina
Hola, bueno les cuento que mi experiencia en Western hockey club fue muy buena y la gente es muy calida y social a la vez, desde que arrive a este pais siempre tube mucho apoyo de todas las personas tanto en lo afectivo como en lo laboral, es como una gran familia. Tambien encontre que es un pais que le encanta tomar cervezas despues de los partidos y asi seguir con la parte social entre los equipos y a la ves seguir disfrutando de otros partidos.
James Grant - England
I first played for Western in 1995 whilst enjoying my University summer holidays. I found the club to be extremely social and very similar to the hockey clubs in England. I enjoyed the hockey and the Western "family" so much that I decided to return in 1996 for a second season. In 2002 I moved permanently to NZ and found that the Western tradition of work hard, play hard had not changed and would thoroughly recommend the club to any hockey player of any ability.
Victor Straatman -
Western is een erg gezellige club, waar goed hockey wordt gespeeld. Wat ik vooral leuk vind aan Western is het internatiale karakter; zoals je hierboven ziet komen onze spelers overal vandaan. Western is verder een club waar ze wel een pintje lusten, dus dat is natuurlijk ook altijd mooi. Als je meer wil weten over hockeyen in Nieuw Zeeland, stuur ons dan gerust een email en we helpen je verder!
Western Districts Hockey Club - Gate3, Avondale College, Rosebank Road, Avondale, Auckland, New Zealand.


Tonight, when you turn around during Lecho Dodi and greet the Shabbos Malka, close your eyes and really focus on accepting the neshama yeseirah. If you do it right, you will feel it!
This entry was posted in Shabbos, Spirituality. Bookmark the permalink.


Q. I have 9 years and 10 months of active-duty military time, and 10 years of federal government time. I left the federal government 15 years ago. I was buying back my military time, but I didn't finish paying it off before I left the federal government. Can I get the money back that I paid into buying my time since I didn't finish, or shall I look into trying to finish paying it off? I took my annuity and rolled it over. Am I ineligible for any FERS benefits when I retire from this nonfederal job?
I did buy back my time !! now opm is saying thier have not got my payed in full letter !! where can i get the payed in full letter ! I have talked to DFAS-CLEVEIAND !! HOW CAN I GET THIS LETTER !!!


text:
The Daily Television
The lighter side of Batman
The original television series is 50 years old, and back then its hero didn't need to be dark to be super
by Peter Hoskin
Fifty years ago today, on January 12th 1966, Americans gathered around their television sets. It was Lyndon B. Johnson's third State of the Union address, and the first ever to be broadcast in colour. Could the message possibly match the cathode-ray cheerfulness of the medium? Sadly not, as it turned out. The president explained his policy on Vietnam in a sad staccato: "We will stay until aggression has stopped." The speech was one of war and regret.
Still, the television schedules weren't a total loss. There was another first that day: the premiere of a series on the ABC network that, like LBJ's broadcast, was shot in colour. Except this wasn't the colour of Washington, DC, but of comic books and crime capers and the groovy 1960s. This was the start of "Batman", starring the strong-jawed Adam West. His war was on the miscreants of Gotham City. He had no regrets.
That first episode began as the series meant to go on. The prime minister of the fictional republic of Moldavia is attending a "friendship luncheon" in sunny Gotham when a great cake is brought in on a tray. As he goes to cut it, the cake explodes – the only injuries are to the PM's suit and his national pride – which sends a note flying into the air. "Why is an orange like a bell?" it reads. This is clearly the doing of the Riddler.
Naturally, the cops need the help of Batman and Robin (Burt Ward) to crack this one, so they dial them up on the police department's very own Batphone. What follows is a madcap mystery. The pair face legal action; Batman dances his dance, the Batusi, at the What a Way to Go-Go Club after his drink gets spiked by one of the Riddler's clan; and Robin ends up having a scalpel waved in his face by the Riddler himself. A voiceover intones: "Is this the ghastly end of our dynamic duo?" Find out tomorrow.
And millions did. Despite the fact that most households would have watched it on undersized black-and-white television sets, "Batman" was an immediate and immense success. Kids thrilled at the simple, cliff-hanging plots. Their parents had the delights of some wry comedy and attractive actors in tight costumes. And ABC could count its cash: $75m of merchandise was produced during that first year alone.
Now that the Batman movies give us a darker, more complicated version of the character, it is easy to scoff at this Sixties Batmania. But it is wrong to. Batman was popular because it was good. That's why so many of its components have stuck in our collective memory. Neal Hefti's der-der-duh-duh-duh-duh-der-der theme tune is a pop masterpiece. The Batmobile, converted by George Barris from a 1950s Lincoln Futura concept car, with the profile of a descending bat and a cockpit for each of our dynamic duo, has left its tyre tracks across millions of teenage dreams. The fluorescent pows! and bams! that fill the screen every time Batman socks another goon, recalling the written sound effects of comic books, are as much a signifier of their time as the Beatles and Warhol.
What "Batman" demonstrated is that Batman himself can do almost anything. In this respect, it wasn't a betrayal of the comic books, as those who take their cue from the 1980s work of Frank Miller, preferring their Dark Knight to be moody, sometimes insist. Even that first episode was adapted from a story called "The Remarkable Ruse of the Riddler" in issue 171 of the comic. This Batman was an all-dancing, all-prancing punchline, but his key characteristics remained. He was still dedicated, as he should be, to ending crime. And he was counteracted by one of the finest rogues' galleries ever created. Frank Gorshin set an early and unsurpassable watermark as a particularly demented Riddler, but there was also Julie Newmar's sinuous Catwoman, Burgess Meredith's cantankerous Penguin, and even Cesar Romero's Joker, with his moustache still visible beneath his white face paint.
Thankfully, even as Batman dours up for the forthcoming film "Batman v Superman: Dawn of Justice", released worldwide in March, there seem to be some executives who remember all of this. The show was remastered and given a splendid Blu-ray release in 2014, whilst DC Comics has just capped off "Batman '66", a comics series telling new stories from that Sixties universe. There is even talk of West and Ward reprising their roles to voice an animated movie this year.
The show itself ended after three series in 1968, a victim of over-familiarity. There were only so many cliff hangers that could be hung on viewers, only so many times the Batphone could ring. But this Batman wouldn't have minded at all. As he put it in one episode, "I'd rather die than beg for such a small favour as my life."


text:
Drew From The Chainsmokers Says "It's My Fault" T.I. Punched Him In The Face
August 18, 2022 7:46AM EDT
LOS ANGELES, CA - DECEMBER 31: Andrew Taggart of The Chainsmokers performs onstage during Dick Clark's New Year's Rockin' Eve With Ryan Seacrest 2019 on December 31, 2018 in Los Angeles, California. (Photo by Kevin Winter/Getty Images for dcp)
Drew Taggart from The Chainsmokers talked about an incident that happened with rapper T.I. in a TikTok posted this week that: "T.I. just literally punched me in the face." "We were on a vibe, and I gave him a kiss on the cheek, and he totally punched me in the face. It was my fault." "He punched me in the face, and I was like, 'Ok, I'm sorry,' and he was like, 'Alright, cool, we're good' It was the weirdest interaction ever." T.I. then apparently told Alex Pall "'You need to get get your boy.'"
@thechainsmokersMy bad T.I. won't happen again… unless?♬ original sound – The Chainsmokers
T.I. gave his side of it in a 17-minute video on Instagram, and the first 30-seconds-plus were just him laughing. "Ok, first of all, I love The Chainsmokers," "We just had to work through some stuff."
A post shared by TIP (@troubleman31)
He didn't get into the actual details of what happened, but just said "Afterwards, we had a drink, we took a shot. You know what I'm saying, we moved on." He also invited Taggart and Pall to work it out furter on his podcast ExpediTIously saying "Let's sit down & chop it up."
Alex Pall
Drew Taggart
punched


text:
CHILD'S ERCALL, SHROPSHIRE
Grid Ref: SJ 665 251
St. Michael's The tower
The Porch Sun dial
Child's Ercall is about 6 miles south of Market Drayton in the Bradford Hundred. It is mentioned in the Domesday Survey as belonging to Rainald, the Sheriff of Shropshire. At that time it had a priest indicating a church or chapel, probably of Saxon origin. The churchyard is roughly circular, which often indicates an ancient even pagan origin for a site. The current church of St. Michael has clearly been through many phases of building. As seen in the photograph at the top left, the early 16th century tower stands at the west end of what is now the south chapel. The chancel and north aisle date from 1879. A 12th century doorway was reset in the chancel as shown in the picture bottom right. The south aisle was widened in early 14th century. The church was not open when we visited.
A wall constructed of stout ashlar blocks near the church shows that a fine house once stood nearby. The wall has been much patched with stone and brick. However, Child's Ercall Hall was a farmhouse even in 1868.
The Old Parish Churches of Shropshire, by Mike Salter, Folly Publications, 2001, ISBN 1-871731-47-X
A description of Child's Ercall in 1868 is given on the Genuki Page.
The Victoria County History has a page on the Bradford Hundred, which includes Child's Ercall.


text:
A külképviselet vezetőinek listája

Magyarország varsói nagykövetségén 1919 előtt az Osztrák–Magyar Monarchia diplomatái képviselték a magyar érdekeket. Az 1919-től 1939-ig terjedő időszakban különböző szintű diplomaták képviselték Magyarországot, a mai diplomáciatörténeti művek azonban csak 1946-ra datálják a követség, és 1954-re a nagykövetség megnyitását.

A lista azokat a személyeket mutatja, akik 1919 óta  - nem feltétlenül nagyköveti rangban - vezetői voltak a magyar (nagy)követségnek Lengyelországban. A nagyköveteket az államfő nevezi ki, ennek dátuma az első oszlopban olvasható. A megbízólevél átadásának időpontja a diplomáciai szolgálat tényleges megkezdésének dátuma. A megbízás visszavonása szintén a mindenkori magyar államfő joga.

Jegyzetek

Követek és nagykövetek listái


The mightiest team of superheroes are back! A throw-down with a prehistoric terror in the heart of Washington D.C. sets the stage for the dramatic return of a wayward hero! Meanwhile, half a world away, a sinister plan begins to awaken an ancient evil!PLUS - Riverdale High's new substitute teacher is very odd. Snubbed by the scientific community, he plans his revenge - on the students of Riverdale High! It's going to take a team of people with some mighty powers to stop him. Archie Comics' two most renowned superhero teams are going to meet up for the first time ever!
Archie Action scribe IAN FLYNN has been the chief writer for Archie's popular and record-setting SONIC THE HEDGEHOG comic for more than a decade. He was the main writer of its sister titles SONIC UNIVERSE and SONIC BOOM and their accompanying graphic novels, and was also the writer of Archie's MEGA MAN series, another critical and popular hit. Flynn also helmed the historic meeting of Sonic and Mega Man in the popular SONIC/MEGA MAN- WORLDS COLLIDE and WORLDS UNITE storylines, and wrote main titles ARCHIE and JUGHEAD.


Received changes through RFC Editor sync (changed abstract to 'The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine- to-machine (M2M) applications such as smart energy and building automation.
-18 addresses all of my concerns and thank you for addressing them!
4.2/4.3: "Reject" in the sense it is talked about in these sections is an internal state change. That's confusing to me, as the normal sense of the English word implies a party that "hears about" the rejection. (It's hard to me to think of a circumstance where someone or something was "rejected" and only the rejector ever knew about it.) In your use, "silently ignore" is one possible form of rejection. That's just weird.
If you're going to do this, I'd define the term up front. Maybe even capitalize "Reject" wherever you use it.
Either way, in both 4.2 and 4.3, "MUST reject" is probably wrong (since that's an internal state and nothing a protocol requirement is useful for) and "MAY involve sending" is a strange construction.
SHOULD process any request or response in the message only once.
I suggest: "The recipient SHOULD silently ignore any duplicated Non-confirmable message, and SHOULD process any request or response in the message only once, though the specific semantics of the message might dictate an exception."
4.6: I feel like this section is really one big implementation note: Because it is a layer violation, it's not clear to me that any implementer has the ability to figure out much of this. (For example, the idea that an implementer would be willing to -- or even know how to -- set the Do Not Fragment bit or figure out the Path MTU is a bit hopeful.) I have no objection to this section, but it might be better as an implementation note rather than a set of protocol instructions.
5.3.2: Change "the client will likely send a Reset message so it does not receive any more retransmissions" to "the client will send". A client that has lost state that receives what it will see as a random CON message will always send back a Reset.
5.4.6: If it were me, I would have put the NoCacheKey bits in the high four bits of the most significant byte so that you could simply do a <224 test for cache-matching options. I suppose this ship has sailed.
5.5.1: The implementation note notwithstanding, I don't understand why Content-Format is not a SHOULD.
A server SHOULD be aware that a request arrived via multicast, e.g.
That SHOULD is not meaningful. It is useful, not required with exceptions (as SHOULD indicates), for the server to know that it is using multicast.
This also gives a reason not to allow RST on *any* NON messages.
12.1: I think it would be much easier to figure these out if you separated out the bit fields of code type and code, and then had sub-registries for request codes, success codes, client error codes, and server error codes.
Updated based on - 17.
A well-written document and I have a few points to discuss.
The protocol does not have any real means for the receiver to control the amount of data that is being sent to it. I can understand the attempt to provide a simple protocol, but adding a very basic flow control mechanism will not prohibitively increase the complexity of the protocol, while improving robustness.
The 4.13 "Request Entity Too Large" with a protocol field that indicates the maximum data size would be fixing this.
The congestion avoidance mechanisms look ok, but I assume we will get feedback from implementers and deployments on the parameters and mechanisms. It would be good to get this feedback documented at some point.
1) IPv6 UDP checksum calculation -- fixed.
2) Handling of UDP-lite -- fixed.
3) Fragmentation of messages -- done.
4) Ensuring no fragmentation with IPv4 -- done.
I wonder why the draft is not discussing any reaction to network failures signalled through ICMP messages. This relates also to my DISCUSS issue no 4.
Regarding reserved or prohibited values in the IANA section, it would be useful to be clear about what happens when those values are seen. I.e., should they be ignored, generate an error, etc.
"The same Message ID MUST NOT be re-used (in communicating with the same endpoint) within the EXCHANGE_LIFETIME (Section 4.8.2)" with EXCHANGE_LIFETIME of 247s.
By now it is unrealistic that the message ID of 16 bits will wrap around in that time frame, but protocols live long and at some later time it can be possible.
However, the protocol doesn't have any means to detect wrapped message IDs.
The recommendation in Section 4.6 about the path MTU is generally valid only for IPv6. For IPv4, 567 bytes is the safe area to work without fragmentation, though in today WANs 1280 work perfectly, but I am not so sure about the networks envisioned for CoAP. This 576 bytes for IPv4 are mentioned in the implementation note, but deserves text on the same level as for IPv6.
4) Ensuring no fragmentation with IPv4 -- fixed.
According to Section 2.1, a node can always return a RST if the message cannot be process for whatever reason.
I propose to add an option to the RST message that allows the message receiver to state how much data it is willing to accept from a particular sender or in general (up to the implementation).
SHOULD be sent as a response.
The possibility that a server could potentially not send back a 4.06 seems really problematic from a client perspective. I have no way as a client to say, "I really can only accept format X, and if you can't make format X, I don't want something else", and I have no way to distinguish that from "I would prefer format X, but am willing to take whatever you can give me." For the former, I have to be prepared to throw things away. For the latter, I have to be willing to send two requests, the first with Accept (potentially getting back 4.06), and then a re-request without Accept. Which one of the above are current clients doing? If it's the former, then I suggest making this into an implementation note, and I would even consider getting rid of the 4.06 response code for this use case, since it is nearly useless, and probably harmful. If it's the latter, then these SHOULDs ought to be MUSTs and the option should be critical so that clients can stop doing that.
I suggest changing the last two sentences above to: "The class can indicate a request (0), a success response (2), a client error response (4), or a server error response (5). (All other class values are reserved.)"
4.1: Personally, I find the word "empty" confusing here. "Null" or "Noop" probably would have been better. If this use is already well understood, it's probably best to define it clearly. Capitalizing "Empty" might help.
s/SHOULD/should. There's nothing to implement here.
5.10.5 s/MUST/is. The MUST is not meaningful.
12.1: As mentioned regarding section 3 and 5.2 above, I think it would be much easier to figure these out if you separated out the bit fields of code type and code, and then had sub-registries for request codes, success codes, client error codes, and server error codes.
in below from last time, but didn't check 'em against -17.
specification work to get CoAP interop.
detect and react to that.
"interesting" application layer behaviour. Why is that ok?
worse because the message ID comparison can be skipped.
client "may want to use a non-trivial, randomized token"
the start (of what?) then its marginal.
that'd be way less than otherwise possible with e.g. HTTP.
CoAP doesn't work for their use-case.
> thank you for this attentive review.
Thank you for the quick and careful response.
We've discussed my DISCUSS, so I'm changing my ballot position to YES (but please make Martin happy on his transport-ish DISCUSS :-).
I have a couple of places where I've suggested text that seems clearer to me, but I moved these to COMMENTs on my ballot.
> Note that I plan to ballot Yes, after we resolve these questions.
> I have three points - the first one is the one I'm most curious about.
> application environment use consistent values for these parameters.
> changing the parameters until there is a good way to do so.
> answers in this document.
application environment use consistent values for these parameters.
continued to say "Operation with inconsistent values in an application environment is outside the scope of this specification", or something like that.
> The value is intended to be current at the time of transmission.
> Max-Age SHOULD update the value before each retransmission.
> should be a MUST.
Your explanation was very helpful to me. I'm fine with SHOULD as 2119 language here - that matches what I'm hearing you say.
> resources as described in [RFC6690].
> extremely important but implementations might not do it".
This is very helpful. What I wasn't getting was whether there was any way other than CoRE Link Format to discover resources when there are no humans in the loop.
Again, as a COMMENT, I'm reading this response as "SHOULD support the CoRE Link Format of discoverable resources as described in [RFC6690] if there are no humans in the loop, to maximize interoperability". Am I getting that right?
And if this is a statement of expectation, I'm OK with SHOULD, if the working group thinks that's appropriate.
> people will need to read it - that's why I'm being picky on comments.
> (support for UDP-lite, etc.). I'm sympathetic, but didn't restate them.
> If Martin is happy, I'll be happy.
So I should be reading this as something like "Constrained networks like 6LoWPAN support the fragmentation of IPv6 packets into small link-layer frames, but this mechanism is expensive in that it reduces performance"?
> Is "compressing ... interfaces" the right way to say this?
> same paragraph) without qualification.
> specific codes added, as defined in Section 5.9.
> In 6.4. Decomposing URIs into Options, is "fail this algorithm" clear?
> It might be a term of art for HTTP folk, but I'm not familiar with it.
> 4. If |url| has a <fragment> component, then fail this algorithm.
No, I think you're doing this right (thanks for the clue!).
> a RST in reply to NON as usual.
> environments. But if you have to (.NET?)..."
> Thing X from happening, ..." that would be helpful.
> payload or an error response).
> avoid the 2119 question?).
> I think 2119 language is appropriate here.
I understand why you're using 2119 language now. I'm not sure I understand how the requirement for the peer is different from either the request or response getting lost.
I'm reading the spec as saying that multicast requests are sent as non-confirmable at the messaging layer, so if there's no confirmation at the messaging layer and no response from the server at the request/response layer, does the peer see any difference between hearing nothing back because something was lost, and hearing nothing back because the server had nothing to say?
> be done in the response if the request is not authenticated.
> to combine these points in a single paragraph.
My apologies for not being clearer in my comment.
be done in the response if the request is not authenticated.
- the subsequent suggestion to use slicing/blocking, which is not conditional on authentication, seamlessly hooked together.
Is the intention that the recommendation to use slicing/blocking be conditional on authentication, or should the server always use slicing/blocking whether the request is authenticated or not?
I lacked some time to review the draft details. However, after a discussion with Joel Jaeggli, and with the OPS DIR review from Mehmet, I trust that the OPS aspects have been taken care of.
Thank you for this important work and well written specification. While there are aspects that I would personally have done differently and some fine-tuning of the spec could continue, I believe the document is ready to move to an RFC. I also believe it that is a much-awaited spec and very useful to the Internet community in its current state.
I do agree with some of the points raised in other reviews, and those need to be addressed.
I did have one specific additional suggestion worth bringing up here. Dan Romascanu did a Gen-ART review and raised the issue that the parameter changes discussed in S4.8.1 are security sensitive, i.e., changes in the parameters may cause security/denial-of-service issues. This should be noted somewhere in the S11. I'd make a brief observation that it is security sensitive and should be addressed in any system that allows configuration of these parameters.
3. Section 4.8 defines a number of CoAP protocol parameters and derived parameters that according to 4.8.1 may be changed. Some of these parameters have limitations and their changes may affect the basic functionality of the nodes, the interaction between nodes or between nodes and servers, as well as the functioning in constrained environments. However there is no risk analysis in Section 11 (Security Considerations) about the threats related to mis-configuration of the modes and un-appropriate or malevolent changes in these parameters, and recommendations of security counter-measures on this respect.
Thank you for this important work and well written specification. While there are aspects that I would personally have done differently, I believe the document is ready to move to an RFC. I also believe it that is a much-awaited spec and very useful to the Internet community.
Thanks for a clear draft. Makes things so much easier to review. Just want to discuss a couple of things before moving to yes (hopefully).
0) s9.1.3.2: Before I get in to the nitty-gritty of the specific concerns I have with DTLS use of Raw Public Keys, I have to ask whether use of the DTLS client_certificate_url extension was considered? If raw public keys is just about size then that'd work wouldn't it. If you're about dumping processing of paths, then that's another thing.
i) s9.1.3.2.1: For machines it's perfect appropriate to generate the key and install it because we doubt it'll be able to do that well enough right (i.e., crummy entropy sources)? I want to make it clear that that's been done by the manufacturer.
X.509 certificate (called a raw public key).
paid is generated by the manufacturer and installed on the device.
from the public key as described in Section 2 of [RFC6920].
b) draft-ietf-tls-oob-pubkey is likely to take a pass on specifying a mechanism for revoking the public key and identity binding. Note that ocsp-/multi-ocsp staplingwon't work because there's no way to request information about a certificate that you don't have information about. I'm not trying to gold plate the security mechanism here but I think we need some words on how revocation for this mode will be handled. However, I suspect you'll want to use the ACLs....there's a mechanism for including ACLs during provisioning but is there a way to update them later? What happens if a new node gets installed or removed? Is there a requirement for ACLs to be supported; the text has a SHOULD but that seems to be about ACL provisioning support not ACL support.
When referring to TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 please include the MTI curve(s). Ever so glad that conservative curves are being used. In the following, I assumed you'd want the one must and the two mays but I can understand if you don't. I'd argue you do have algorithm agility with DTLS so you could get away with just the MUST ad not the MAYs.
Unrelated to you, but I thought I'd let you know about: the curve requirements will almost certainly be removed from the mcgrew draft at my direction because no other D/TLS EC cipher suite specifies an MTI curve. There's support for conservative curves, but not enough interest in starting to add MTI curves instead of the application picking them. Note the Zigbee folks also point to the mcgrew draft but it seems their drafts already include the curves so we ought to be good to go on both fronts.
server SHOULD expect to receive it.
server need not expect to receive it.
o [RFC6090] MAY be used as an implementation method.
And then, I think we need to specify how the MTI would look: namely by adding the following on to the end of the paragraph.
those object identifiers [RFC5480] are included instead.
That way everybody knows what values go in the SPKI of the oob-pubkey draft. Note they tried to change that field recently and I had to remind them not to.
needed when setting up the security association.
Made me wonder whether you considered which other DTLS extensions might be useful in addition to the EC ones and SNI as well as what extensions should be profiled out? For example, max_fragment_length looks pretty useful in this context as well as certificate_url. But does heartbeat make any sense?
4) s8: I think you need to make it pretty darn clear in s8 that multi-cast is an unsecured "mode" as specified in this document. It's kind of buried in s9.
5) s9.1.2: (worried about a DoS attack) Do you mean that responses to secured-CoAP messages returned unsecured are silently discarded/ignored or rejected and then that kicks off an error code response?
6) s9.1.3.1: Did you consider whether there should be an application profile for the psk_identity_hint (see Section 5 [RFC4279]) - i.e., is there a standard format for CoAP that should be defined?
7) s9.1.3.3: When you say "the Certificate must be validated" I'm just checking that you're think there's going to be a certificate chain? If there's no chain the validation rules in 5280 don't apply.
8) s9: If you're going to allow more than two entities to share the preshared keys I think it's worth pointing out you really can't get peer authentication with either CoAP or DTLS. The description in s9 and elsewhere seems to imply that more than one peer might share the same key.
9) Either in s9 or s11 we need to say something about devices with bad entropy sources not bothering to make keys because they won't be of any use. If they've got bad entropy sources the manufacturer or whoever should be making the keys.
0) s1.2: Is the "CoAP-to-CoAP proxy" definition missing? s5.7 refers to s1.2 for the definition but that term is not in s1.2.
2) s9: In the NoSec option is worth also pointing to the link layer security (IEEE 802.15.4)?
3) s9.1: Because there's no s9.2 (I assume that might have been an IPsec-secured CoAP section at one point) you can drop the header.
the key usage extension indicates digitalSignature.
On the fist bit: You could lock it down to just one curve if that's what you decide to do based on comment #5.
7) s9.1.3.3: r/further work./further study.
It is not clear if zero UDP checksums are permitted or not permitted with COAP.?
Can UDP-lite (RFC 3828) be used or cannot be used in conjunction with CoAP?
The implementation note in Section 4.6 states that for IPv4 it is 'harder to ensure that there is no IP fragmentation'. This neglects the possibility of using the Don't Fragment (DF) flag in the IPv4 header and also that there is possibly feedback from a node enroute that the MTU is too big if the DF flag is set, i.e., by means of an ICMP error message.
Should there be any recommendation or protocol machinery to deal with path probing? E.g., referencing RFC 4821 (PMTUD).
I think this specification is well-written, it's important, and a lot of people will need to read it - that's why I'm being picky on comments.
Martin already has a DISCUSS about some of the more transport-ish topics (support for UDP-lite, etc.). I'm sympathetic, but didn't restate them. If Martin is happy, I'll be happy.
Is "support" the right word here? I'm not understanding "support the expensive fragmentation".
Is "compressing ... interfaces" the right way to say this?
I've seen other reviewers mention "short messages" in "CoAP is based on the exchange of short messages", but it may also be worth clearly distinguishing "short message" from "SMS" ("short message service") - as I understand it, the two phrases have nothing in common, but they are both used in the document (at the beginning of Section 3, and even in the same paragraph) without qualification.
specific codes added, as defined in Section 5.9.
I get this, but I'm wondering if it's worth thinking about whether these similar but unrelated namespaces can semi-collide (if HTTP is extended to include a 328 response code, is it OK for CoAP to define a 3.28 response code that means nothing like what HTTP 328 means?) Given that 404 and 4.04 are similar, for example, I'd expect some implementers to guess what less common CoAP response codes are, based on HTTP response codes, rather than check carefully. That's an obscure comment, but I thought I should ask.
In 6.4. Decomposing URIs into Options, is "fail this algorithm" clear? It might be a term of art for HTTP folk, but I'm not familiar with it.
4. If |url| has a <fragment> component, then fail this algorithm.
a RST in reply to NON as usual.
Doesn't this tell me that the MUST NOT is not required for interoperability? I'm only quibbling about the use of 2119 language. On a related point, if there was a sentence that started out "to keep Bad Thing X from happening, ..." that would be helpful.
payload or an error response).
but MAY is pretty weak anyway (maybe "can always ignore the request", to avoid the 2119 question?).
I don't understand what the SHOULD NOT means in practice. Is this saying the server shouldn't return large resources for NoSec requests (whatever "large" means), or ? If this is saying the same thing as the text on using "slicing/blocking mode" two paragraphs, down, it would be clearer to combine these points in a single paragraph.
Note that I plan to ballot Yes, after we resolve these questions.
I have three points - the first one is the one I'm most curious about.
I'm thinking about this in an IOT/M2M context where it's somewhere between inconvenient and impossible to change parameters on all the deployed devices at once. I understand that configuring these parameters is out of scope for the doc, so assume changing the parameters is out of scope as well.
The value is intended to be current at the time of transmission.
Max-Age SHOULD update the value before each retransmission.
Will servers know that resources they serve have strict tolerances? The answer may be "yes", I'm just asking. If not, I'm wondering if this should be a MUST.
resources as described in [RFC6690].
Is it obvious that this is a SHOULD? Is CoRE Link Format necessary for resource discovery, or can you also accomplish this with humans if they're in the loop? I'm just trying to wrap my head around "it's extremely important but implementations might not do it".
I don't understand what the SHOULD NOT means in practice. Is this saying the server shouldn't return large resources for NoSec requests (whatever "large" means), or ? If this is saying the same thing as the text on using "slicing/blocking mode" two paragraphs, down, it would be clearer to combine these points in a single paragraph, or otherwise describe "large amplification factors SHOULD NOT be done".
Overall, this is a very nicely written specification. Thanks!
In Section 2.2., are requests and responses in 1-1 correspondence? Or can a single request receive more than one response?
In Section 3, why is version number 1 and not 0? What's the plan here, do we get 3 or 4 versions out of this?
Request X X ? !
Response X X X !
Might be helpful to include something like that as a summary. This might be a bad idea, but: Did the WG consider allowing an ACK to contain a request? In the case where a CON contains a response and the client wants to send another request, it would save a message to put the request in the ACK to the response.
I will (still:-) end up balloting yes for his.
Just one DISCUSS point remaining.
(3) Cleader, but see comment below.
(4) Cleared, but see comment below.
We have a question about the IANA Considerations section of this document.
We understand that, upon approval of this document, there are several actions which we must complete.
This will be called the "CoAP Codes" registry and will contain a number of subregistries.
Values in the registry and its subregistries are eight-bit values notated as three decimal digits c.dd separated by a period between the first and the second digit; the first digit c is between 0 and 7 and denotes the code class; the second and third digit dd denote a decimal number between 00 and 31 for the detail.
0.00 Indicates an empty message (see Section 4.1 of [ RFC-to-be ]).
0.01-0.31 Indicates a request. Values in this range are assigned by the "CoAP Method Codes" sub-registry (see Section 12.1.1 of [ RFC-to-be ]).
2.00-5.31 Indicates a response. Values in this range are assigned by the "CoAP Response Codes" sub-registry (see Section 12.1.2 of [ RFC-to-be ]).
All other Method Codes are to be marked "Unassigned."
The Response Codes 3.00-3.31 are Reserved for future use. All other Response Codes are Unassigned.
The range of 0 - 255 is reserved for options maintained by IETF Review or IESG approval as defined in RFC 5226. The range of 256 - 2047 is maintained via Specification Required as defined by RFC 5226. The range of 2048 - 64999 is maintained via Expert Review as defined in RFC 5226. The option numbers between 65000 and 65535 inclusive are reserved for experimental use.
For values in the range 0 - 255 maintenance of the registry will be done through Expert Review as defined in RFC 5226. Values in the range 256 - 9999 are maintained through IETF Review or IESG approval as defined in RFC 5226. Values in the range 10000 - 64999 are registered through "First Come, FIrst Served" as defined in RFC 5226. Values between 65000 and 65535 are reserved for experimental use.
Eighth, IANA has done an early allocation of port number 5683. Approval of this document will make that assignment permanent and the reference for port 5683 will be changed to [ RFC-to-be ].
CoAP resource discovery may also be provided using the DTLS-secured CoAP "coaps" scheme. Thus the CoAP port for secure resource discovery needs to be standardized.
Besides unicast, DTLS-secured CoAP can be used with anycast.
Tenth, a multicast address from the IPv4 Multicast Address Space registry is to be assigned. Called the "All CoAP Nodes" address, the authors request it should come from the Internetwork Control Block (224.0.1.x, RFC 5771).
Eleventh, a multicast address from the IPv6 Multicast Address Space registry, in the Variable Scope Multicast Addresses space (RFC3307) is requested.. The authors request that the address should be of the form FF0x::nn, where nn is a single byte, to ensure good compression of the local-scope address with [RFC6282].
We understand that these eleven actions are the only ones required upon approval of this document.
> The IESG contact persons are Barry Leiba and Pete Resnick.
> energy and building automation.
> implementers. There are no particular controversies to note.
> input, that resulted in significant changes to the specification.
> All review feedback is now incorporated in the final document.
> been reported from those events.
> expert for the IANA registries defined in Sections 12.2 and 12.3.
requirement that you change the text, and I am ballotting Yes.
scoping your environment to today.
simply run an early, low-function version of HTTP.
the full family of rich features that may chew memory and bandwidth.
What about the use of CoAP on the wider Internet?
application requirements, such as repeated readings from a sensor.
the ability to do something: this message can be confirmed.
"Can be confirmed" != "A confirmation must be sent"
"Cannot be confirmed" != "A conformation does not need to be sent"
Section 1.2. Also a very minor point.
failure of any encapsulated request.
Message may also carry a Piggy-backed response (q.v.).
as 0x7d34 while NON is encoded as 0x01a0.
I don't think it is based on UDP. I think it runs over UDP.
Maybe insert another pointer to [REST].
unless it is used only to elicit a Reset message.
to elicit a Reset message in which case it is empty.
This paragraph is giving me some worries.
think a CoAP implementaiton must not give up unless it is told to.
relaxation, and how does it square with the MUST NOT?
larger than an IP fragment result in undesired packet fragmentation.
one UDP payload) obviously MUST fit within a single IP datagram.
policy for the registry. But "Reserved or future use" means what?
I support some of the points raised by mehmet against draft 13 (addressed by carsten) which ultimately are not likely to be resolved by the this draft alone.
> - It would be useful to state clearly, in which cases it is dangerous to change any of the recommended default values or parameters in future versions of CoAP and would potentially impact the co-existence of two CoAP versions. Thus such a statement would support an incremental deployment to be successful.
Again, I believe this is future work, which also applies for the configuration and management data model.
Protocol debugging is aided by the self-describing nature of the protocol messages.
This has worked pretty well in the (informal and formal) interops so far.
Future work will have to address management interfaces for CoAP nodes, including management of security related events.
I think some of this will have to integrate with resource discovery, an active subject in the working group.
this is not a dicuss because frankly I think at some point you have to draw a line under work that has been done so far and progress work from there.
P. 15: why start at version 1 when you can only have a total of 4 versions? Wouldn't version 0 be a better choice?
SHOULD be normalized where possible.
strings representing the same text.
other proxies could as well, but that's a much bigger change.
an ACK with a request.
Acknowledgement or Reset message from their recipient.
be better stated this way?
MUST NOT respond with either Acknowledgement or Reset messages.
really benefiting from that anyway.
used for this is outside this document's scope; see also Section 9.
decomposed as an IP address literal?
carelessly assuming that it means (1) or (1 or 2).
were for emphasis, and weren't path separators.
user part to the authority section of the URI.
Overall, this is a very nicely written specification. Thanks! There's just one point I think needs action on before I switch to a "YES" position.
In Section 5.3.1, "A client sending a request...". This needs to be stronger. The requirement for a randomized token needs to be a MUST, and the stack SHOULD limit the number of rejected responses (before closing the request) based on the length of the token (e.g., 2**(TKL/2)).
perhaps this statment is scheme specific to some extent?
schemes can be used with CoAP and which cannot.
think 9.1 might cover all the above, but want to just check.
then we need to DISCUSS that.
5280 section 6? If so, say so. If not, say what you do mean.
(9) 9.1.3.3 - you don't mention certificate status checking.
is better. Too late now though.
say "CoAP is designed to easily..."
message" doesn't make that (ctystal) clear. "Unsafe Option"
to distinguish that explicitly from Message ID.
2.3: For what "security reason" are proxies useful?
might set both bits to 1, so saying '01'B might be better.
missing != 0? Might be worth saying.
schemes might invalidate this MUST?
4.6, 1st sentence: don't get that, maybe better deleted.
5.2.2, "The server maybe initiates..." seems too casual.
become an issue there? How's that handled?
but I think that'd be bettern being more obvious.
to pick if more than one matches. Why's that?
does "support" mean for port 5683 then?
the text was trying to hide something from me fwiw.
the interop gains that will accrue from that.
terms of message size) for security. Am I wrong?
not done so already, I do see a shepherd response).
15 Dan Romascanu Request for Telechat review by GENART Completed: Almost Ready. Reviewer: Dan Romascanu.
I am entering no-objection on the basis that this has no impact on the routing layer and I am confident that the applications layer ADs will ensure the quality of the design.
The discussion of idempotency is useful, but overlooks message order. I.e., the discussion appears to assume that a sequence of the same actions has the same effect as a single action, but this is true only if different sets of actions (from different sources, or copies of different actions from a single source) aren't interleaved. This should be addressed.
This document uses the term "endpoint" to refer to the combination of address and port, and possibly also security association, that is local to one end of an association. I would have expected the more common term "socket", as originated in TCP parlance, to be used instead (even though here the term is used in a connectionless context).
Link layers can give some hints if the link is up, down, etc. Traditionally, this has not been taken into account too much when design transport protocols, but wouldn't it make sense to take it into account for CoAP, as it is much more working in constrained environments?
What are short messages in terms of bytes? Is this a hidden protocol requirement?
> not overlap). The initial variable value should be randomized.
> larger than an IP fragment result in undesired packet fragmentation.
should read larger than an 'IP packet' instead of 'IP fragment'.
as it provides important information that shouldn't be missed.
> a promise that the request will be acted upon.
Assuming that the server did sent an ACK for a request but is never ever fulfilling its promise to send any real 'response'. The request/response initiated from the client is done on the CoAP level, but not for the application on top.
Is there any recommendation for the application on top of CoAP how to handle such cases?
A well-written document and I have a few points to discuss, but I still need to write them in a comprehensive way.
Thank you for a well-written document. I do support Pete's DISCUSS points.
The items here are very borderline in my book for DISCUSS items; I'm happy to be talked out of them. But I would like to hear from the authors and/or chairs before I give my "YES" (which is my plan once these are resolved).
If you insist on the MUSTs, make the second one "bytes of data MUST NOT be present". The current construction is ambiguous. That said, I find the combination of MUSTs to be a bit problematic. MUST NOT send data, but MUST receive as a format error will lead to some sender saying, "A conformant receiver MUST reject with an error, so no need for me to validate on the way out" and for a receiver to say, "A conformant sender MUST NOT send data, so no need for me to validate on the way in." That's a recipe for non-interoperability. If it were me, I'd drop the last sentence.
See comment on 2.1. But if you're going to allow this, I don't understand the MAY: Doesn't rejecting the message require sending a Reset? Otherwise, the message has not been rejected; it's simply been ignored. The second part is either redundant or confusing: What else might I do with a rejected message other than send the Reset and ignore it? I think this needs rewriting.
5.2.2: It is probably worth saying somewhere in here: "Once the server sends back an empty Acknowledgement, it MUST NOT send back the response in another Acknowledgement, even if the client retransmits another identical request. If a retransmitted request is received (perhaps because the original Acknowledgement was delayed), another empty Acknowledgement is sent and any response MUST be sent as a separate response."
5.4.2: Cache-Key is undefined, here or in any other document I can find. It probably needs an explanation somewhere in this document.
5.5: Again, I don't like the combination of MUST NOT include/MUST ignore. I would drop the MUST ignore part.
1. The reference to [I-D.ietf-lwig-terminology] worries me, given that it is not even in LC yet.
reply with a Reset message (RST).
Why is this? If a NON message can't be ACKed, why can it be RST? This seems like additional machinery for the client.
response, detailed in Section 5.2.1.
It took me a bit to figure out why things worked this way, and I think a sentence or two of explanation would be useful. A piggy-backed response to a Confirmable request doesn't itself need to be confirmable because if the ACK gets lost, the client will re-transmit the request until it gets the answer. When the response to a Confirmable request is not piggy-backed, the response should itself be Confirmable, since a Confirmable request will normally want a guaranteed response.
although the server may send a Confirmable message.
"Likewise" seems wrong here. A Non-confirmable request can *not* get an Acknowledgement message, and therefore can *not* get a piggy-backed response. Additionally, the response MAY be Confirmable or MAY be Non-confirmable, though certainly Non-Confirmable is the more likely case. This should probably be reworded.
Why not make TKL a 3-bit unsigned integer and have a reserved padding bit before it? Is this protocol likely to be extended to 9-15 byte Tokens?
request (1-31) or a response (64-191), or is empty (0).
As above, why not make a 3-bit field for Code Type (000=request, 001=reserved, 010=success response, 100=client error response, 101 =server error response, 110/111=reserved), and then a 6-bit Code? It would also make the registry much easier to read.
I don't understand the requirement not to be empty, especially when there is an exception at the end of the sentence. Shouldn't this be "and contains data bytes unless it is used only to elicit a Reset message."?
I don't understand the second MUST: What other choice is there besides carrying a response or being empty? Aren't those the only two options?
Confirmable message, and MUST be empty.
Why MUST a Reset be empty? What harm is there if there is data in there?
or Reset message is effected by silently ignoring it.
I don't understand the above. As far as I can tell, an Acknowledgement nor a Reset can be rejected; the side that sent them will never know it is rejected.
4.5: All of the MUSTs and MAYs in the section are used rather terribly. I'm glad to suggest text if you need.
4.6: The phrase "and (by fitting into one UDP payload) obviously MUST fit within a single IP datagram" is unnecessary, but even if you do use it, s/MUST/needs to. The MUST is not a requirement on an implementation of CoAP. That said, I fear this section is really nothing more than an implementation note: Because it is a layer violation, it's not clear to me that any implementer has the ability to figure out much of this. (For example, the idea that an implementer would be willing to -- or even know how to -- set the Do Not Fragment bit or figure out the Path MTU is a bit hopeful.) I have no objection to this section, but it might be better as an implementation note rather than a set of requirements.
5.2: I found "indicating a value of 4*32+3, hexadecimal 0x83 or decimal 131" just adds confusion rather than clarify. Perhaps instead: "even though if taken as an 8-bit unsigned, the entire Response Code field would have a value of hexadecimal 0x83 or decimal 131 (4*32+3)". But personally, I would simply drop it; it doesn't add anything. See also comments above on section 3 and below on 12.1.
First, I suggest changing the first sentence after the colon: "Response Code details that are unrecognized by an endpoint when the class is Client Error or Server Error are treated as equivalent to the...". Much clearer, and the MUST is wrong. Second, I don't see why you don't simply define a 2.00 so that this can be a bunch simpler.
5.4.1: I don't understand the need for the third bullet. Isn't this already said in the second bullet? The fourth bullet has the same issue as 2.1 and 4.3.
like an unrecognized option (see Section 5.4.1).
That is to say, you can't choose to keep later ones and discard earlier ones.
5.4.6: If it were me, I would have put the NoCacheKey bits in the high four bits so that you could simply do a <224 test for cache-matching options. I suppose this ship has sailed.
Also: "a proxy SHOULD be conservative" s/SHOULD/should. There's nothing to implement here.
8.2: "the server MAY always pretend"? We are getting sillier with our 2119 usage later in the document. Did you really mean, "the server MAY ignore the request"? Isn't that true of any NON request, not just multicast ones?
14 Tero Kivinen Request for Last Call review by SECDIR Completed: Has Nits. Reviewer: Alexey Melnikov.
14 Dan Romascanu Request for Last Call review by GENART Completed: Almost Ready. Reviewer: Dan Romascanu.
IANA has reviewed draft-ietf-core-coap-14. Authors should review the comments and/or questions below. Please report any inaccuracies and respond to any questions as soon as possible.
We have questions about the IANA Considerations section of this document.
We understand that, upon approval of this document, there are several actions which IANA must complete.
This will be called the "CoAP Parameters and Codes" registry and will contain a number of subregistries.
QUESTION -> What is the URL address for this new top-level registry?
0 Indicates an empty message (see Section 4.1).
the "CoAP Method Codes" sub-registry (see below).
The remainder of the entries in this registry, 5-31, are unassigned.
The Response Codes 96-127 are Reserved for future use. All other Response Codes are Unassigned.
IANA Question -> What reference should be substituted for the reference in these initial registrations marked "EXIMIME?"
of the URI Scheme registry for review and approval.
discovery needs to be standardized.
"IANA MAY accept early assignment [RFC4020 <http://tools.ietf.org/html/rfc4020>] requests (known as "early allocation" therein) from IETF working groups that reference a sufficiently stable Internet-Draft instead of a published Standards-Track RFC. "
IANA understands that these eleven actions are the only ones required upon approval of this document.
13 Barry Leiba Doing AD review in parallel with working group last call (which ends 21 Dec).


text:
Utena, Revolutionary Girl Fan Fiction ❯ Arisugawa's Locket ❯ Mother, may I? ( Chapter 35 )
Mother, may I?
"So how's your friend?" Setsuna asked Juri quietly. They were sitting in the kitchen of the Outers' house, enjoying their cups of coffee. Juri had come over to see her late last night, and instead of her going home they had spent the night together.
"Sober," Juri smiled back wryly, "a definite improvement." She drank from her cup, savoring the taste of good coffee.
Haruka and Michiru stumbled in, Haruka doing a slight double-take at seeing Juri sitting at the table. She opened her mouth to say something about Juri's rumpled clothes, only to be cut off by a swift elbow in the ribs from Michiru.
"Good morning Juri," Michiru said demurely.
"Morning," Juri raised her cup in a toast to the two of them.
Hotaru stumbled in, giving them all an absent minded wave as she retrieved her carton of orange juice from the fridge. A glass full of juice in hand, she wandered out into the living room to watch her cartoons.
"She's taking my being here well," Juri noted, sounding just a bit nervous.
"Hotaru usually does," Haruka agreed, "I can only think of one or two times I've seen her even mildly thrown off by something."
"She'll probably have a few questions for me later, though," Setsuna noted.
Michiru groaned softly, remembering something.
When no explanation was forthcoming Juri asked, "What?"
Haruka smiled, sipping her coffee. "Hotaru got let out of school early," she explained, "and walked in on us while we were..." she trailed off.
Juri blinked, then, "Oh ho!"
"Exactly," Michiru was blushing faintly. "Hotaru left as calm as you please, and we figured we were fine. A few days later she asked poor Setsuna what we were doing, and she described in detail what she saw."
"Personally, there were some details that I just really didn't need to know," a blushing Setsuna said mildly.
Juri was still chuckling to herself occasionally when she headed back to the city. 'Wish Setsuna could be here beside me,' she thought, steering her sports car expertly, 'but her nursing job keeps her pretty busy.'
Juri returned to her apartment first, showering and putting on a fresh set of clothes. She looked much more businesslike as she strode out into the Shinjuku district, taking a short walk to a busy restaurant nearby. She picked out an early lunch, and polished it off in record time.
The calendar hanging on the wall caught her eye, and with a slight twinge Juri noticed it was nearly Mother's day. She remembered the tall, aristocratic woman everyone said she resembled. It had been a long time since she had actually seen her mom, a few months after she had been throw out of the house.
She knew it had been a difficult moment for them both, her mother's stumbling attempt at an apology, and Juri's own anger and resentment flaring up in return. She had said some harsh things that day, things that she regretted saying now.
The gift shop was on her way home, and Juri stepped inside to look around. The card was easy, a simply designed Mother's Day card, then she looked at the gifts. There were so many it was confusing, but then the chocolates caught her eye.
'She's always liked chocolate,' Juri remembered with a smile.
Chocolates, card, a nice box and wrapping paper, and Juri put it all together in the store. Deciding what to write on the card was the hardest part. After a few moments of thought she settled on a simple, 'Thank you, love, Juri.'
Not giving herself too much time to think about it, Juri put the stamps on the package, wrote the memorized address, and had it in the mail in a few minutes.
It was too early to open the Locket, but Juri swung by the building to make sure it was still locked up tight. She stood in front of the building thoughtfully, considering what to do for the hours before the Locket was going to open.
"Juri-sama!" a happy voice squealed, and a young woman all but throttled her from behind.
"Wakaba?" Juri blinked, recognizing the curly haired friend of Utena.
"I knew this place had to be yours as soon as I heard the name," Wakaba beamed. The girl had gotten a bit older, but other than that the perky young woman remained the same.
"What are you doing here?" Juri asked curiously.
"I was in town visiting Utena," and Wakaba's eyes darkened a bit, "had some time on my hands." She perked back up, "I was looking around, and heard about this place."
'Wonder from whom?' Juri thought ruefully. "We're not open yet," Juri said, "but why don't you come in, look around?"
"Really? Could I?" Wakaba was practically bouncing up and down.
Juri chuckled softly, opening up the front door. They walked down the hallway into the main room, the empty dance floor, the bar, karaoke stage and dining tables nearby. Off in the corner, the library and it's couches looked comfortable and inviting.
"So what do you think?' Juri asked curiously as they walked over to lean up against the bar itself. It was odd, but she found that it actually mattered to her, what this acquaintance from the past thought of Juri's bar.
"It's incredible," Wakaba beamed. She looked over at Juri thoughtfully, "And it's just for women, isn't it?"
"Yes, it is," Juri said gently. She poured them both a ginger ale, "Are you really surprised?"
"No, not really," Wakaba smiled back.
Juri looked over at Wakaba, thinking about some of the stories that had been going around then. "You weren't always joking," Juri said softly, "when you told Utena that you loved her."
"Hmmm," Wakaba blushed faintly, looking down and having some of her drink.
Deciding it would be cruel to push Juri took a different tact, "Maybe you should stop by this evening, see what the place is like when it's open."
Wakaba smiled back cheerfully, "I'd like that."
They walked out together, Juri locking up the place before driving off. 'One more errand to do,' Juri thought with a little smile.
Later that day, a visibly tired Setsuna drove home from a hard days work. Stopping at the mailbox she pulled out a large package, recognizing Juri's writing of her name.
'What's this?" Setsuna thought, flipping up the little attached card.
'Happy (early) Mother's Day,' the card said in cheery script. Setsuna unwrapped the box carefully, and sighed softly as she saw the chocolates inside.
"Juri, you spoil me," Setsuna sighed happily, popping one into her mouth.
Characters this Episode: Arisugawa Juri, Wakaba, and Utena are from Revolutionary Girl Utena. And Haruka, Michiru, Hotaru, and Setsuna are from Sailor Moon.
Another 'Out of the Locket' episode. A few fans were concerned that Juri and Setsuna might be breaking up, so I thought I should address that. I haven't dealt with Juri's family much, and with Mother's Day here I thought I'd tackle it.


For the bedroom, my wishlist includes this soft, waffled cotton bathrobe (1). I also love Aviva Stanhoff's fresh, modern textiles - the Scribble bedspread (4) caught my eye, as did this indigo calico cushion (3), hand embroidered with a French knot design.
For the kitchen, I'm coveting the Matcha tea set (1) which includes a rustic speckled bowl and a bamboo whisk and spoon. Other kitchen essentials include a wide range of Le Creuset (4), and this Dualit Architect toaster (5). For coffee afficionados there's also a large selection of Nespresso machines.
Head over to the Harrods website and explore the Harrods I'm Home range for a chance to win a luxury home collection worth nearly £3,500.


Under the impulse of its designer Nancy Minner, year after year, Bouton Jaune's brand evolved while remaining faithful to the spirit of the workshop-boutique where it was created. High quality local crafting, top of the line imported fabrics, chic and refined design, no frills; these are the essential characteristics that have made its popularity.
Burley is the worldwide leader in bicycle trailer design and has been for more than 35 years. We put our heart and soul into every trailer we make so you can be sure you are getting the absolute best in quality, durability and safety.
Dutailier is specializing in the manufacturing of high-end wood bedroom furniture for babies, children and teens and rocking chairs.
Dedicated to build a global community of confident parents with smart, ergonomic solutions that enable and encourage bonding between parents and babies.
We make on-the-go easier for today's parent. Bundleme, Diaper Bags, Carriers, Strollers and more gear for your active lifestyle.
Lulujo is a proud Canadian company that launched in 2009 by founder and CEO, Dawn Marie Pottier. The brand, inspired and named after her two children, is an ever growing global business based out of the east coast in Canada.
At Maxi-Cosi we understand the thrill of having a new baby in the family and the excitement of spending time together, discovering the world as you both grow - as a parent and as a curious, wide-eyed baby.
Perlimpinpin is a Canadian manufacturer of cloths and bedding for kids and baby.
Petunia Pickle Bottom fearlessly brings style and sophistication to the world of modern motherhood with bold pattern and smart design.
SouthShore manufacture affordable furniture for the North American market and share their passion and tips with the consumers so they can create the décor that suits their way of life.
Innovation, integrated ergonomics and human centered design result in products that strengthen the bond between parent and child.
Tiny Love® is a multiple award-winning global toy and baby products' company that was founded in 1991 by Shoshi and Isaac Oren.
Valco Baby is a family owned and operated company from Australia. We have been manufacturing and distributing baby products for more than 30 years. Within those 30 years there have been a lot of babies that have born, many of them into the Valco Baby family.


text:
module ElectricSheep
  module Commands
    module Database
      class MySQLDump
        include Command
        include Helpers::ShellSafe

        register as: 'mysql_dump'

        option :user
        option :password, secret: true

        def perform!
          logger.info "Creating a dump of the \"#{input.basename}\" " \
                      'MySQL database'
          file_resource(host, extension: '.sql').tap do |dump|
            shell.exec cmd(dump)
          end
        end

        def stat_database(input)
          shell.exec(database_size_cmd(input))[:out].chomp.to_i
        end

        private

        def cmd(dump)
          'mysqldump' \
           " #{credentials}" \
           " #{shell_safe(input.name)} > #{shell.expand_path(dump.path)}"
        end

        def database_size_cmd(input)
          "echo \"#{database_size_query(input.name)}\" | " \
            "mysql --skip-column-names #{credentials}"
        end

        def database_size_query(db)
          'SELECT sum(data_length+index_length)' \
            ' FROM information_schema.tables' \
            " WHERE table_schema='#{shell_safe(db)}'" \
            ' GROUP BY table_schema'
        end

        def credentials
          option(:user).nil? && '' ||
            "--user=#{shell_safe(option(:user))} " \
            "--password=#{shell_safe(option(:password))}"
        end
      end
    end
  end
end

redpajama_set_name: RedPajamaGithub


STATUS: 20181130:I have tested and "blinks" in two colours. Have to test "camera operation" but I am quite sure it will work. LED footprint is wrong and I have fixed it for the next batch. Still I can solder with difficulty and make it work. Already fixed it for the next batch 6.2.4 Alpha. The "gold" ENIG finish is nice and easy to solder. Not sure it is worth the 5X price increase.
COMMENTS: Looks nice, LED footprint perhaps is too small or hard to hand solder. Outline fits perfectly. I wonder how hard is going to be soldering on ENIG (gold). Photodiode footprint looks spot-on. 20181130: I have to test with a camera in the VF to see if the magic happens. Hope it does or it can be easily fix in the next batch.
STATUS: 20181130:I have tested and "blinks" in two colours. Have to test "camera operation" but I am quite sure it will work. LED footprint is wrong and I have fixed it for the next batch. Still I can solder with difficulty and make it work. Already fixed it for the next batch 6.2.4 Alpha. The HASL finish is OK, but doesn't look as nice.
COMMENTS: Looks nice, LED footprint perhaps is too small or hard to hand solder. Outline fits perfectly. HASL looks definitely easier to solder. And way cheaper.
STATUS: 20181130 Build one and sent it to Clément. Seems to work but I don't like it: footprint of switches (was a catch all) is not good. Holes are too small. Have to rethink it.
COMMENTS: ENIG and black but I'm not so sure about this one! 20181130: Maybe it could be smaller? Not sure.
COMMENTS: Same as before but in HASL. I'm not so sure about this one!
COMMENTS: This a jig to test all kind of pcbs. I need a 3D printed bench.
COMMENTS: Long shot done in a hurry for a unified USB-dongle connected via FPC. Credit to Marco.
COMMENTS: Just a remake to have uDongles in case the new ones are a flop!


there's a war against the world going on.
are walking into my heart.
because the half matters when you're little.
if I just give it a chance.
but too young to be heard.
yet i'm still too little for them to listen.
but now, I'm not just two.
the unwanted byproduct of being too alive.
weed: noun, a plant in an undesirable situation.
i lie in a bed of weeds.
left me where i belong.


text:
Q: Swift Vapor: How to read a JSON file? I'm using Vapor, the server-side Swift 4 framework for creating web servers. I have a migration that I'd like to apply that reads in from a JSON file; however, most if not all Swift tutorials I see on this indicate using Bundle, which to my knowledge, isn't available when developing server-side swift applications, which means attempts like this don't work:
if let path = Bundle.main.url(forResource: "myFile", withExtension: "json") {
...

This begs the question, given a relative file path, how can I read in a file using server-side Swift?

A: Silly me. Vapor exposes a DirectoryConfig object from which you can retrieve the working directory of the application. To parse a file, it thus becomes:
let directory = DirectoryConfig.detect()
let configDir = "Sources/App/Configuration"

do {
    let data = try Data(contentsOf: URL(fileURLWithPath: directory.workDir)
        .appendingPathComponent(configDir, isDirectory: true)
        .appendingPathComponent("myFile.json", isDirectory: false))

    // continue processing

} catch {
    print(error)
}

redpajama_set_name: RedPajamaStackExchange