What it does
iMessageR is a small and simple package for the R statistics package that allows a user to send iMessages to any phone number or email address registered with iMessage service.
I know that there are a number of similar ways that this can be done, such as making a system call to
There are also a number of packages for sending messages from R using gmail. This is great but also requires some amount of additional configuration in R in order to function. I figured iMessages was the lowest friction option for Mac and iOS users.
I suspect this will be especially helpful for R users who run lengthy analyses and would like an alert to their phone (or any other iMessage capable device) indicating when the analysis is complete.
Since you can use this function any number of times and customize the message, you could even take things one step further and use iMessageR to help with debugging. For example, you could insert calls to this function at different locations in your script to indicate progress through your program. Alternatively you could insert it into a trycatch() or some other exception-handling system to alert you of an error.
Since iMessages is available to any user with a Mac, whether or not that user has an iPhone, iMessageR could be used by a Mac user regardless of the type of phone they use. Without an iPhone, the user would, of course, only be able to receive notifications on their Mac (or any other Mac also configured with that iMessage email address or phone number). So while an iPhone (or iPod Touch) is ideal in order to receive the most benefit, even Mac users without an iOS device will likely find some utility here.
The iMessageR package can be downloaded directly from cran or can be installed from within R:
This will give you access to the function
send.imessage(recipient: STRING, message: STRING)
- If the message string contains single or double quotes, the function will fail.
- If the email address or phone number is incorrect or unrecognized, there is no notice to the user.
I’d like to try to make this package more accessible to different platforms. I hope to add support for a wider range of platforms by adding options for different services. Presently I am thinking of Pushbullet or WhatsApp but this will depend on the level of API integration those services expose.
I should note that I am neither a computer programmer nor a habitual R user, so this is very new territory for me in a number of ways! As such I will try and address issues and add enhancements in my spare time, as my nascent skills allow.
Connect with me
Connect with me on github where you can submit an issue or fork away!
Or reach out to me on twitter: @scottisloud.
The CBC’s Marketplace is focusing on retail food waste this week. Yesterday we heard from a former Walmart contractor that a ‘heartbreaking’ amount of food is trashed every day. Today, Marketplace reveals its findings from 12 days of sifting through Walmart dumpsters.
This is a great scoop for the CBC and I think this kind of coverage is just what is needed to bring light to a shameful problem. Food retail accounts for 10% of the food wasted in Canada. This is a small slice of the pie, but in absolute terms, it’s a substantial amount of food (it is, after all, a very big pie). These CBC stories can stand on their own, but I wanted to add some additional commentary and nuance based on some of my experience and research on food waste.
Marketplace found cartons of milk days ahead of their best-before date, and Parmesan cheese with months left before it needed to be thrown away.
Assuming these products are not contaminated or otherwise unsafe, this is troubling. Best-before dates on both of these products are largely unrelated to safety. A solid piece of Parmesan cheese can be safely stored for a very long time. Barring any cross-contamination in a retailer’s or consumer’s fridge, the worst that will happen is the growth of some mould, which is a quality, not a safety, issue, and will not cause someone harm.
Mevawala, formerly with one of the company’s Edmonton stores, says if a piece of fruit or vegetable didn’t look perfect, it had to be thrown in the trash.
Moreover, cosmetic imperfections are a reflection of arbitrary quality standards that are a large reason food is disposed of at the retail level. Retailers will claim that these arbitrary quality standards are the fault of consumers, but this is untrue. This is a marketing failure. There is demand for these products, they just need to be marketed correctly. Loblaws is beginning to dip their toe into this market segment with imperfect apples marketed under their No Name brand. This is also failure of retailers to capitalize on their own value-added departments. These cosmetically imperfect produce items, if not sold to consumers directly, should become part of value-added products in-store. Fruit salads, vegetable trays, pre-chopped vegetables, etc. could all be made from imperfect products.
Over the course of more than 12 visits to the stores, Marketplace staff repeatedly found produce, baked goods, frozen foods, meat and dairy products. Most of the food was still in its packaging, rather than separated for composting.
This quote highlights a significant issue with how retail food waste is often handled. In many cases retailers want to get ‘unsaleable’ goods (however they define that) off their shelves and our of their warehouse as quickly as possible. Typically this means disposing of it directly into their dumpsters or compactors. The above quote draws attention to several problems: all that organic material ends up in landfill where it is a significant source of methane; all that packaging is, to the dismay of brand owners, in-tact and visible to anyone willing to dip their nose into a dumpster or landfill; and that packaging, the majority of which is recyclable, also ends up in landfill.
Retailers regularly fail to take advantage of the services of depackagers. Depackagers, as the name implies, remove food from its packaging. They then send the food to anaerobic digestion, rendering, or some other destination where it is at least marginally more valuable and less environmentally harmful than landfill. They also shred and recycling the packaging, which conveniently obscures the branding (not that that is needed, as most depackagers are very security conscious and discreet, unlike the dumpster!). There is unused depackaging capacity in southern Ontario, and most retailers are not taking advantage of these services because:
- It is disruptive – they are at the mercy of the depackager to pick up products which may not be as fast as the retailer would like. It’s hard to beat the convenience of tossing unsaleable goods directly and immediately into the dumpster or compactor.
- It’s another contract to juggle in addition to standard waste collection.
- It may not be available at 100% of a retail chain’s locations which makes uniform policy and best practice for store managers more difficult.
- For some retailers it just isn’t even a priority, it’s not even on the agenda.
This needs to change. While we need to reduce food waste generation upstream, there will always be some amount of downstream waste. That downstream waste could be handled better, and there’s possibility for that to happen today.
Also in the garbage: bottles of water, frozen cherries that were still cold and tubs of margarine. In a statement, Walmart said it believes the food Marketplace found was unsafe for consumption. In many cases, however, the food was well before its best-before date and appeared to be fresh. Or, if it needed refrigeration or freezing, the food found was still cold.
I have to take issue with the CBC commentary here. Coldness, best-before dates, and appearance are all terrible indicators of safety. None of the indicators listed in the quote provide any particularly useful data to make a decent risk management decision. Best-before dates are often arbitrary, typically refer to quality (at their best) and not safety, and can’t account for variability in storage temperature and handling. Further to this point, just because something that is meant to be cold is cold, doesn’t mean it is safe. There’s simply not enough information for a gleaner to know how long the product has been at a given temperature or if there’s a hazard that can’t be seen.
Our senses are pretty good judges of quality: we can taste soured milk, which is perfectly safe to eat, if perhaps a bit unpleasant. But we can’t taste Hepatitis in still-frozen berries, or an undeclared allergen in a baked good that might result in illness or death if consumed unknowingly by a gleaner or someone that gleaner feeds, or a fresh apple contaminated with Listeria.The reality is, the majority of things that are going to make us sick cannot be seen, smelled, felt, or tasted. Our eyes, fingers, noses, and tongues are bad judges of food safety.
Dumpster-divers, gleaners, freegans, are doing good work recovering perfectly edible food, but it is really risky business unless you take great care (and even then, still risky). There are ways to reduce risks, such as keeping an eye on recall notices before gleaning and becoming familiar with which products are lower risk than others when temperature history and handling are unknowns.
But the reality is, in instances like this, products that look perfectly good may be perfectly bad. Products that are perfectly good may come into contact with harmful products and show no signs of that contact, resulting in cross-contamination. Again, these are things we cannot detect with our own senses. As long as legitimately good food and food recalled for posing a health threat are intermingled in the same bins, it’s impossible to, with any degree of certainty, separate the two.
But even the people in charge don’t necessarily know the difference between quality and safety:
“On some occasions, food which has not passed its best-before date is deemed unsafe for consumption,” Walmart said in its statement. “As a rule we don’t place fresh food items on display for sale if the quality is not acceptable.”
Here, the Walmart spokesperson is dangerously conflating safety and quality. There is a grand canyon that separates what counts as “safe food” and food that possesses “acceptable quality”. A statement like this erroneously reproduces the notion that quality is a safety issue, which is is not (though they may, in some cases be related). It also further occludes the rationale that underlies Walmart’s disposal practice: Is the food in the dumpster dangerous, or does it merely fail to meet some perceived quality expectation? Dangerous food should never be made, and if it is, shouldn’t be sold to consumers. Food that deviates from quality expectations but is safe should be sold and consumed by humans.
Marketplace staff looked for food waste at all the major retailers, including Costco, Metro, Sobeys, Loblaws and Walmart. While staffers found bins full of food at some Walmart locations, other chains had compactors making it impossible to see what they throw out.
This is some seriously bad practice from Walmart. No brand owner wants their products on display to anyone who walks to the back of a store. Retailers also generally “field destroy” recalled products, that is, when there is a product recall, they dispose of it on-site rather than send it back up through the supply chain. Compactors offer security from both a brand and public health perspective inasmuch as dangerous products are destroyed and inaccessible (though, of course, the use of a depackaging service is also secure and environmentally superior, but not typically used by retailers when handling recalled products). An unfortunate side-effect of compactors is that they prohibit informal recovery by gleaners and freegans, but the tradeoff is marginally improved brand and public health security. Walmart needs to prioritize security and switch to compactors. They’re playing a dangerous game with open dumpsters (though, as the CBC story notes, they’ve now started locking those dumpsters at least).
Food waste is a pernicious problem. We waste way too much food. What we can do today is reduce the impact of that waste. However, what is really needed is upstream solutions that reduce the overall generation of food waste. This means reducing contamination and safety problems that lead to product recalls. This means reducing over-production. This means reducing knee-jerk price-hikes that result in surpluses and subsequent blow-outs or disposal. It means disrupting the reproduction of arbitrary quality standards. We have a long way to go towards reducing food waste across the value chain, but what CBC is showing us with these stories is that there are some immediate steps that can be taken to reduce food waste and the attending environmental harm.
The September 1st deadline for public comments on proposed legislation that would allow firms to irradiate beef draws near. While the previous effort to bring irradiation to the beef industry in 2002 failed, there is hope that the events of the intervening 14 years might have shifted public attitudes. However criticisms of the potential plan are already emerging and not just from consumers. While it might be intuitive to assume that the beef industry in Canada is united in their support for this move – it was industry stakeholders who pushed for the first consult in 2002, and again this year – the beef industry itself is divided.
The National Farmers Union (NFU), representing family-owned farms including cattle farms in Canada, has submitted a letter to Health Canada objecting to the potential changes. Their primary concerns are economic. The NFU are concerned that irradiation equipment would be too expensive for smaller beef packers, thus driving them out of business, while JBS and Cargill will easily distribute the capital outlays for irradiation equipment across their sprawling businesses. The ensuing consolidation of an already heavily consolidated industry would further establish Cargill and JBS, who already process 90% of the federally registered beef in Canada, as the only buyers of beef to whom farmers may sell their cattle. Such oligopolistic conditions, they argue, will ultimately produce downward price pressure. This would mean less money per head for farmers. It will limit the number packers to whom cattle ranchers could sell to and thus limit competition, and would further reduce already rather limited consumer choice.
Another concern is that the proposed change would allow for the importing of irradiated beef from the United States where beef processors have been permitted to irradiate beef for over a decade. Not only would this contribute to further downward price pressure on farmers to compete with cheap imported beef, it would displace domestically slaughtered beef and swaths slaughter and packing jobs. The NFU states that because the proposed Canadian regulation is nearly identical to that in the US that “it would effectively erase the Canadian border in regard to ground beef”.
While I am sympathetic to these concerns and I am an enthusiastic proponent of local, small-scale agriculture and family farms, there are some important considerations to make here. The first is that the proposed legislation allows beef processors to irradiate beef should they choose to, it does not require that beef producers irradiate their product. The new legislation isn’t going to suddenly put small firms out of compliance with the law. This is only a problem if irradiated beef is met with massive consumer demand and by not irradiating smaller processors would be severely disadvantaged.
With respect to imports, the majority of beef in the United States currently is not irradiated and thus would not be precluded from import anyway. Harmonizing legislation between Canada and the United States would pertain to the very small percent of US beef that is irradiated, very likely a drop in the bucket overall and not likely to pose an immediate threat to Canadian firms.
It might then be argued that while the proposed legislation doesn’t require irradiation, market demand will serve as an sort of proxy whereby if any firm that wants to compete they must irradiate. This seems to assume widespread, maybe even pent up demand for irradiated beef. The evidence from the United States, however, suggests demand is limited. Irradiated beef is available only under a hand full of brand names at a small number of retailers and restaurants. As I argue in a past post there are also unanswered question regarding what the market impacts are of irradiated beef. Will there be an “irradiated ghetto” off in the corner of the meat case touched by consumers only when the the grocer is out of the non-irradiated cut the consumer desires? Will brands begin competing on the premise of their beef being “non-irradiated” or vice-versa? Will it not matter and will consumers simply ignore the label because they don’t care, grabbing whichever tray of beef they need for tonight’s dinner regardless of the presence of a radura logo?
Given all of this, I can’t help but see the economic concerns of the NFU as a strawman. As I said before, beef producers and the government agencies that support them have an uphill battle. In over a decade in the US, irradiated beef is not a blockbuster, and I don’t think it will be in Canada either.
The NFU also raised concerns that eaters in institutional settings are not positioned to know whether the beef they are served is irradiated or not. Those who prepare the food would know – they’d see the labels on the boxes of course – but those labels won’t leave the kitchen. This is only a problem for human health or food safety if the considerable evidence indicating that irradiation of food does not pose a threat to consumers’ health is ignored. Even if there is a remote chance of human health impacts, there’s a very immediate and potentially fatal threat from fecal pathogens. This does point to a shortcoming with the labelling requirements in that in an institutional setting the labels are largely obscured from institutional eaters. This is something that should be addressed (most likely this will be in the hands of institutions themselves) in the interest of maximizing transparency for all consumers, but it is not an issue of public health or food safety. I imagine poor food handling practices at these retirement homes and schools are a far larger and far more immediate threat to the vulnerable populations that dine in those institutions than any possible threat posed by irradiation. Moreover, I suspect the majority of those institutional eaters have been consuming irradiated spices and onions for years without harm. If we are really concerned about allowing institutional eaters to make better risk management decisions, perhaps we should start posting food safety inspection scores on the doors of restaurants and institutions.
I am, however, sympathetic to the other concerns articulated by the NFU related to food safety. The NFUS are concerned that irradiation may “be used as a final control point to kill some (but not necessarily all) pathogens…that occurs when processing high volumes at high speeds without adequate inspection of lines”. I too am concerned about the possibility of irradiation becoming a food safety crutch. There are commentators who claim “we have run out of regulatory power”, and that it is a necessity to deal with ubiquitous pathogens in the context of a regulatory system that has exhausted all possible options. I couldn’t disagree more with this idea that we’ve run out of regulatory power. The XL Foods recall didn’t take place because we’re at the end of our regulatory rope; it happened because both the CFIA and XL Foods dropped the ball. There is room to improve food safety regulation, the decision is whether that is something that the government wants to do. Claims that we’ve run out of regulatory power is really a disguised claim to shunt responsibility for food safety away from government.
Further to my point, recent changes made by Walmart to reduce the presence of Salmonella and Campylobacter on their chicken have been fairly effective. There is room to improve food safety without irradiation, and Walmart has done it on its own – not in order to comply with direct government regulations. This isn’t to suggest we forbid irradiation, just that there is room to improve food safety upstream given the will to do so, and such improvements can limit how heavily we lean on irradiation as a final kill step. The NFU also point out that while irradiation is permitted in the United States, there have nevertheless been no shortage of outbreaks attributed to pathogen-contaminated beef. Were it to become a crutch it may not be the most reliable.
If Canada’s food safety system hasn’t shown itself to be so easily fallible, and if industry didn’t seem to capable of flouting their commitment to it, I might feel differently. As it stands we are clearly not at the end of the regulatory rope. When Canada’s largest beef processor fails to comply to existing food safety requirements and persistently fails to address corrective action requests from the CFIA who then does nothing to intervene, the idea of irradiation becoming a crutch doesn’t seem too far fetched.
What I do think is that irradiation should be available as a tool in a company’s food safety toolbox. If irradiation can contribute to the reduction of foodborne illness outbreaks and wasteful food recalls, then I think the benefits outweigh the costs. That said, my support is qualified. Any allowance of irradiation needs to coincide with more robust regulation, monitoring, and enforcement. It behooves regulators to demonstrate they can compel those they regulate to make improvements. Walmart has shown that companies have room to improve without relying on radiation, and regulators need to push the rest of the industry to follow suit. (For a similar sentiment, see Coral Beach’s recent article on Food Safety news)
Overall, I don’t think that irradiation poses the economic threat that the NFU assumes it will. Strawman. While I advocate for consumer transparency, I think the NFU’s concerns about the safety of institutional eaters is overblown. However, I share the NFU’s fear of a lack of effort on the part of industry and its regulators to maximize the effectiveness of existing options. Industry has demonstrated how much more can be done to improve food safety. There are a lot of unanswered questions about what irradiation might mean for the beef industry, but I don’t believe it is the threat it is being made out to be. In fact, I suspect any impact, positive or negative, will be disappointingly modest.
Stericycle this month published their Q2 report on product recalls in the United States, which they’ve called “Tainted Table”. I love these quarterly reports from Stericycle, and I think this one has some interesting bits worth highlighting.
In Q2 there were over 80 times more FDA recalls (measured in “units”) and 45 times more USDA recalls (measured in pounds) compared to Q1. The USDA recalled 1.1 million pounds in Q1, and a whopping 53.3 million pounds in Q2. (I always appreciated the USDA’s use of mass compared to the FDA’s reliance on “units”).
Of the FDA recalls, there were more pathogen-related recalls than in any of the past two years. This could likely be a result of increased testing and a large number of recalls linked to past outbreaks thanks to whole genome sequencing.
The report also highlights the role played by the “multiplier effect”, which I have written about here. Their example of the sunflower seed recalls that resulted in over 600,000 units of product being recalled highlights this multiplier effect well. Not only were many brands of plain-ol’ sunflower seeds affected, so were cereals, granola bars, and store-prepared salads. It was a mess. It shows one of the consequences of the immense consolidation and centralization of certain aspects of the food industry as well as just how serious “ingredient” recalls can be.
More recently, and not covered by the report, the recent E. coli contaminated flour recalls (see here, here, here, here, and here, and the original recall here) demonstrates this phenomenon well. The spread of this recall across so many different brands and products is quite remarkable. The original recall took place on July 1, and here we are 6 weeks later and we are still seeing recalls related to this flour.
It’s shaping up to be an interesting year for recalls in the United States. Looking forward to Q3!
A spat of spice recalls have taken place over the last few weeks in the United States.
The JM recall seems to be small, affecting only small amount of product from a Georgia farmers’ market. The Gel recall expanded considerably over time, from a single lot to several different brand labels and lots. The Oriental Packing Company has recalled a whopping 188.5 tons of the stuff. While there doesn’t appear to be any official statement to suggest a link between the two turmeric recalls, nor between the turmeric and the curry powder, it seems likely to me that there is a single common source for all of them. Turmeric frequently appears in large quantities in curry powder, in part because it’s a traditional ingredient in many Indian spice blends, but also because it is relatively cheap compared to other common Indian spices and can bulk up a curry powder nicely.
There are a couple of possible explanations for these elevated lead levels. Since most spices are sold wholesale by mass, the addition of a substance like lead oxide could be a way to add bulk and thus increase margins. This is similar to a comment made in a blog post at The Acheson Group (which has subsequently been removed) suggesting the possibility that the spat of spice recalls in 2014-2015 due to the presence of peanut powder was also economically motivated food fraud. Peanut powder and ground cumin look awfully similar after all. The addition of lead oxide is, in fact, an old habit of less-than-scrupulous spice millers for a good long time. If this turns out to be the cause of the current contamination, it’s a reminder that old food habits die hard.
Another possible explanation is that turmeric, which is a rhizome like ginger, could have taken up lead that had (naturally or unnaturally) been present in the soil. The ability for plants to take up lead has been documented by the University of Minnesota.
Either way, a couple tons of turmeric and cumin powder are headed towards destruction. I wouldn’t be surprised if we see a recall in Canada for turmeric or turmeric-based products in the coming weeks, similar to the sprawl of the nut-allergen cumin last year.
Lidl has recalled some of its yoghurt and peanuts because the packets don’t warn customers that they contain milk and nuts.
Allergen labels are immensely important in ensuring the safety of customers with allergies. No doubt there needs to be close monitoring to ensure that consumers with allergies can shop with confidence. Customers with allergies aren’t dummies. This recall is borderline insulting.
Either that or it’s a scary sign of just how far processed food has come and that consumers have now been trained to know that just because the label says the product is “nuts and yogurt” doesn’t mean it contains either of those things.
All of the recalled ground beef was produced on July 26. They all have the establishment number “EST. 337” printed inside the USDA mark or on the product packaging seam.
Note that this 30 tons of beef in a single day of production. I have always been curious about the impact of production scale on the size of food recalls. Being able to narrow down the affected product to a specific day of production – or detect an issue and resolve it within a day – is fairly remarkable. However, if a single day of production is 30 tons of product, perhaps we need to narrow this window even further. Food processors are stunningly efficient at making massive quantities of product very quickly. It seems to me that there is a need to step up detection and traceability to keep pace.
Regarding the recent signing of the DARK act:
In fact, according to Obama’s own Food and Drug Administration (FDA), if enacted, the bill would exempt most current GMO foods from being labeled at all. The FDA further commented that it “may be difficult” for any GMO food to qualify for labeling under the bill. And even for any GE foods that might be covered, the bill allows for food to be “labeled” through a digital system of QR codes that can only be accessed if the consumer has a smart phone and reliable internet connectivity.
This is a shame. Regardless of how you feel about GMOs, denying choice and transparency is a bad move. When it comes down to it, no regulation is sometimes better than bad regulation, as it stands this flaccid new regulation just consumes resources with no returns.
My regular reader will have noticed recent change to the appearance of Recall These Thoughts. For the second time in one year I’ve changed blog platforms. You, dear reader, will likely remember the move away from Squarespace over to Wordpress. This was motivated as both a cost-saving measure and a way to gain a bit of additional flexibility. I love Squarespace, but a big part of having a blog for me is having a little toy to tinker with. Wordpress offered a bit more of that type of freedom.
But Wordpress has its downsides. For one, it was very difficult to modify templates. The CSS was was already condensed and extremely complex – thus largely inscrutable. This made some template modifications difficult to make. Moreover, if you neglected to make a child template prior to making all of your changes (as I did) and an update is issued to your template, you’re in for a world of hurt.
I also found the backend to be “weighty”. There was a lot of stuff back there, a lot of things I didn’t need. The editor was a bit fussy, it didn’t always handle markdown very well, and it really just offered more than I needed.
Overall Wordpress was just too much and not really that fun to play with. It is a powerful and popular platform, but it didn’t offer me the type of tinkering I really yearned for. I wanted something a little simpler, a little faster, a little more fun to play with for this amateur coder.
I had tried to install Jekyll about a year ago. Jekyll is a Ruby and Liquid based static website generator. Having no familiarity with Ruby and only the most basic competence with the command line, I got hung up and frustrated with Jekyll.
Fast forward about a year. During an evening of being unable to sleep I poked around and worked on installing Jekyll once more. Sure enough I was able to get it installed, located a template that would make a good foundation for my site, and off I went learning and tweaking. At this point things moved quickly. While unfamiliar with SASS as a styling language, it’s a lot like CSS with which I am extremely familiar. I found my way around the single CSS file quickly and learned with little trouble the classes that were used in the various layout files.
I also got the hang of the Liquid variables that Jekyll uses, making theme modification even easier. I even went ahead and created a few conditional loops to auto-detect when I make a “linked list” style post and have it format that correctly and offer a permalink.
I used Ben Balter’s Jekyll Exporter Wordpress plugin to export my posts from Wordpress, which it did with amazing accuracy. There were a few things that needed tidying that got a bit messed up converting from HTML to markdown, but most of that could be accomplished using find and replace. Beyond that I had all my old posts locked and loaded, my theme thoroughly customized, and was ready to pull the trigger. I synced the built site from my development directory to my host, and the new site launched with only a couple hitches.
So what is the payoff? The biggest payoff is, perhaps, that the site loads about 4X faster and is about 1/8th the size. This is important for me because I have extremely cheap hosting, and I value the experience of my one regular reader.
The other payoff is portability. My posts are written in markdown and live in a directory on my computer. They are not in an SQL database with a bunch of auto-generated HTML. While there are ways to write and backup posts for Wordpress, Jekyll’s workflow has easy writing, local storage, and portability built into the process.
There is still work to be done, for sure. I have to migrate some more content over, fix a few posts that broke way back during the Squarespace migration, and I have a lot of little styling tweaks. But overall I’m very pleased with Jekyll and I look forward to making lots more content to enjoy.
In a letter sent directly to the president the renowned civil rights activist called attention to the “serious inequities [in the] GMO labeling legislation.” The bill would allow companies to use QR codes in place of on-package labeling to disclose product information. In the letter Jackson points out the discriminatory nature of such a labeling system;
“100,000,000 Americans, most of them poor, people of color and elderly either do not own a smart phone or an iPhone to scan the QR code or live in an area of poor internet connectivity….There are serious questions of discrimination presented here and unresolved matters of equal protection of the law. I am asking you to veto this bill and to send it back to Congress with instructions to correct this fatal flaw.”
There are so many issues with using QR codes to convey something a logo can do in the same space. The obvious classism, racism, and ageism are just the start. I’m a young, white, educated iPhone owner and I can’t be troubled to pull my phone out and scan every QR code on the shelf.
I think the emerging technology around QR codes on products to facilitate supply chain transparency, country of origin, and other detailed information about the product is a valuable pursuit and is very different from GMO disclosure. In most cases the information provided to the consumer by scanning these QR codes is considerably more detailed, including, as is the case of VG Meats sold at Longos in Toronto, measures of tenderness, recipes, and information about the specific cut of meat. This information is valuable to interested consumers and far exceeds what can be put on a table.
A GMO label, in contrast, is intended to allow the consumer to know whether that product contains GMO ingredients or not, just like the irradiation labelling that is mandatory on all irradiated products.
Yes, GMO and irradiation are complex, and the nuance can’t easily or accurately be conveyed by a mere indicator label. The reality is many people have already formed strong opinions about GMOs and even the well-crafted marketing that would inevitably be linked to by those QR codes is unlikely to change a consumer’s mind.
Of course, the real issue is a fear among manufacturers that explicit GMO labels will deter consumers from purchasing those products, opting instead for those without GMO labels (where an non-GMO alternative exists). This is a very real concern, but I don’t think hiding behind QR codes is the right approach No matter how you slice it this is a weasel tactic that is deceitful and ultimately undermines everything GMO labeling is supposed to facilitate. Just label it properly.
Health Canada recently announced a regulatory initiative which would allow beef processors to sell irradiated ground beef. I was invited to speak to Calgary’s Kingkade and Breakenridge on NewsTalk 770 about what this initiative might mean. The interview went well, and Rob and Roger are both thoughtful and insightful radio hosts, but there was a lot that didn’t get covered. I’ll expand on some of those thoughts here.
In 2002 Health Canada (not for the first time) put forward an initiative to allow for the sale of irradiated ground beef, but that was abandoned as a result of resounding negative feedback (from consumers, the public, or “activists” depending on your perspective). Between then and now, a considerable amount has changed. Landmark food safety events such as the deadly Maple Leaf Listeriosis outbreak in 2008 and XL Foods E. coli beef recall in 2012, which remains Canada’s largest – among numerous other high-profile recalls and outbreaks – have coincided with a growing public awareness of food safety and other issues related to food safety and provenance. More than ever, consumers want to know about where their food comes from, how it’s made, and most importantly that it is safe (e.g., Lockie 2002; Busa and Garder 2014). Indeed, the Canadian Cattlemen’s Association is confident that the public (or at least those outspoken members of the public) have changed course. Regardless of the changes in the last 15 years, there is doubt about whether or not Health Canada’s proposal will be successful. Putting aside the perceived risks, the court of public opinion is often a hard sell, and understandably so. The circumstances in which we encounter radiation are almost universally negative: cancer treatment, x-rays, air travel, nuclear disasters, and World War II to name a few.
Despite what critics say, the scientific evidence suggests that nutrient loss and toxics production is limited or non-existent, which is considerably less than what cooking itself would introduce. Moreover, consumers also seem to forget that their pre-washed salads, sprouts, and peeled carrots are treated with chlorine, while other products are treated with ammonia (let’s also not forget the many instances in which lye is used in very traditional foods like hominy, bagels, and pretzels).
Even if we accept that there is a small health risk associated with consuming irradiated beef, as many have pointed out, the risk from foodborne pathogens is far greater and far more immediate. As I said in my interview, if you want to avoid toxins and carcinogens, you’d best stop eating cooked meat altogether.
Health Canada will require beef producers to label irradiated products. I think this is a critical part of the proposal that is non-optional. Absolutely consumers should have the ability to identify irradiated food, and anything that enhances transparency in the food system more generally should be pursued. However, this will be hard for industry who have to convince consumers to buy the meat with the irradiated label, which may well be sitting next to a tray of meat that was not irradiated. It’s a difficult set of choices from a consumer’s standpoint: did something happen to the meat that required it to be irradiated? The non-irradiated stuff is fine as long as I cook it correctly (where’s my meat thermometer again?). Evidence of this consumer ambivalence is demonstrated by Costco in the US, where irradiated beef has not sold well. As Craig Wilson, Costco Food Safety Chief suggests of irradiated beef: “Mom wouldn’t buy it”, even if the risk from foodborne illness is in fact higher, and more dire.
Ultimately, while industry is one of the primary supporters of irradiation, I am not sure how quickly it will be taken up without a coordinated, industry-wide effort. Who in industry will have the guts to be the first on the shelf with the new irradiation label? How will industry and the Canadian government ensure there isn’t an “irradiated ghetto”? How do we prevent competition and marketing based on (non-)irradiation, such as the development of a premium niche of non-irradiated beef? I suspect we’ll see either an irradiated ghetto as demonstrated by Costco in the US, or a non-irradiated premium niche. Either way the beef industry has a marketing challenge on its hands here, should irradiation be permitted in Canada.
The industry challenges aside, I look critically, though not dismissively, on the prospect of irradiation. Numerous commentators, including Rick Holley, food scientist at University of Winnipeg suggests that we’ve run out of regulatory power and that because “pathogen contamination in processing plants cannot be prevented…if we really want to prevent outbreaks, we have to look at expanded use of irradiation”. However, he also suggests that irradiation will not protect against industry incompetence. I don’t entirely disagree with Holley and other commentators who seem to suggest that XL Foods is a shining example of why we need irradiation, that it might have prevented or limited the (already rather small) outbreak, but there’s a lapse in logic. A major contributing factor to the XL Foods recall was a “weak food safety culture” and that ultimately “it was all preventable”. The company failed to clean its equipment, maintain its plant, respond to CFIA corrective action requests, and actively practice its recall plan.
The conclusion of the independent reviewers of the XL Foods incident runs contrary to many commentators’ primary arguments in favour of radiation, using precisely the same case as evidence. I don’t buy the idea that we’ve run out of regulatory tricks to reduce foodborne pathogens upstream. The XL Foods recall didn’t take place because we’re at the end of our regulatory rope; it happened because both the CFIA and XL Foods dropped the ball. Based on the commentary from supporters like Holley, irradiation would have either done nothing at all (being incapable of overcoming industry incompetence, as he argues), or it would have allowed one or both to get away with a (rather protracted) moment of weakness, potentially leaving the profligate issues at the XL Foods plant to remain unresolved.
I hesitate to outright reject irradiation of ground beef and other products. Foodborne illness is a significant burden on the public health system of Canada and can profoundly impact the lives of victims. In line with my own research on food waste, it is also a non-trivial source of food waste. XL Foods alone resulted in over 5.5 million kilograms of beef being landfilled, which is equivalent to approximately 12,000 cattle. Just this week, General Mills announced that it is recalling over 10 million pounds of flour in the US due to potential E. coli contamination. There are over 300 recalls per year in Canada and over 1000 per year in the United States. If irradiation could prevent even a few of these recalls, it would be a significant improvement in terms of public health and food waste. For example, as Holley suggests (alas, we do not disagree on everything!), irradiating poultry alone would reduce foodborne illness in Canada by 25% and an inestimable quantity of recalled food from being destroyed.
Taken together, I don’t buy the popular criticisms of irradiation, but I think we need proceed with caution. I think irradiation is a reasonable compliment to a holistic farm to fork food safety system that includes regulators with teeth and clout working with competent food producers and processors who feel those teeth when they step out of line. It was the absence of this dynamic that contributed to the XL Foods recall, which has become the poster child for supporters of irradiation. As Health Canada moves forward with the public consultation over irradiating ground beef, let’s take a reasoned and critical approach without knee-jerk reactions that dismiss science, or conversely dismiss the concerns of the public (or activists therein). Most importantly, let’s take this as an opportunity to examine how irradiation can fit in to a comprehensive food safety system while we make the system as a whole stronger, because there’s plenty of room to improve.
Okay, so perhaps not precisely the month of May, but starting in late April there’s been a spat of recalls attributable to Listeria in Canada and the United States. Looking at the CFIA recall listings for the first 10 days of May:
- Food Recall Warning – Ajinomoto brand Yakitori Chicken with Japanese-Style Fried Rice recalled due to Listeria monocytogenes
- Food Recall Warning – Harmonie brand, IGA brand, Co-op brand, Western Family brand and unbranded frozen vegetable products recalled due to Listeria monocytogenes
- Food Recall Warning – Cookin’ Greens Organic brand A Blend of Kale, Sweet Corn & Peas recalled due to Listeria monocytogenes
- Food Recall Warning – Stahlbush Island Farms brand Cut Green Beans recalled due to Listeria monocytogenes
And if we look into the last week of April we also get:
- Food Recall Warning – Organic by Nature brand frozen Organic Sweet Peas recalled due to Listeria monocytogenes
Needless to say, for the last two weeks Listeria has had a field day in Canada. The United States is not exempt! In what Juska et al (2003) refer to as the “amplification” of food safety threats, or what Stericycle call the “multiplier effect”, listeria contamination from SunOpta Inc., a sunflower seed supplier has resulted in a massive cascade of recalls across the United States.
This series of recalls includes Sunflower Seed Snacks, trail mix, protein bars, Brown and Haley Chocolate snacks, and perhaps most stunningly 17 tons of Trader Joe’s salad.
Similarly, frozen vegetables from CRF Foods in Pasco Washington were recalled on April 23rd and subsequently expanded on May 2 to include over 42 brands and 358 products (notably, just in time for Listeria Month!)
It is rather stunning how far an error at a single supplier can reach in the contemporary food system. It almost seems as if we are reaching a level of consolidation and concentration in which the industry is too big to fail. The last two weeks has seen tens of tons of food pulled from the market and destroyed as a result of mistakes made by only a few companies… and this is only the beginning of Listeria Month!
As I wrap up a semester of teaching a third year university class and I prepare to present at the American Association of Geographers conference next week, I’ve been thinking about presentations, presentations, presentations. We’ve all seen it, or perhaps been there ourselves: The previously well-composed presenter now desperately trying to wake their computer up so we can move to the next slide, or scrambling to close embarrassing browser tabs and email messages only to then fish through a slew of personal files to locate the presentation file. It’s unpleasant to experience this from either side of the podium. It can disrupt the flow of our presentation, undo the polished public persona we work hard to cultivate, or reveal information we might prefer kept private. I have seen veteran academics, part of whose job is to regularly give presentations, melt into an embarrassed and frustrated mess. This has always been surprising for me. It is the things we do on a regular basis in our jobs that we should have mastered, the kinks long-ago ironed out. For some reason when it comes to technology this seems not to be the case.
The beautiful thing is you can stop embarrassing yourself when you make presentations with very little effort, and you’ll thank yourself every time you need to present. I will walk you through my setup for giving presentations without embarrassing technological gaffs. It’ll take you $0 and about 20 minutes to have yourself set up the same. The added bonus is that you’ll never have to fear for your security if you’re sharing your computer at conferences, too.
In this post I guide you through the process of setting up a computer user account dedicated to giving presentations.
Create a new user account
We want to make a little presentation “silo”, a secure enclave sterilized of your personal information. We don’t want cutesy desktop wallpapers, sensitive email notifications, and personal information in this silo; it needs to be as generic as possible. This allows us to hand off our computer to fellow presenters knowing that they won’t be rooting around our personal files. It also means we can set up the account to try and prevent technical issues. The best way to do this is to create a new user account without administrative privileges. This is fairly straightforward in Mac OS X. This is a good time to make sure you have a password enabled for your own user account, and that your computer is not set to auto log-in. Make sure the password for your personal user account is strong too, because that’s just common sense.
It is critically important that you have your personal user account well-protected. Your personal account is likely an administrative account, so you want to make sure that only you know the password to allow administration-level changes to your computer. This prevents anyone using the Presentation account from accessing your personal files and making changes to the software.
You’ll want to password protect your dedicated presentation account so I do recommend a password, but make it easy. If you are sharing your computer with other presenters you want them to be able to troubleshoot their own problems, and allowing them to restart the machine and log back into the presentation account without bother you is important. An easy to communicate and remember password is helpful here.
Configure your new user account
Now you have a generic user account that cannot access any of your personal files or make changes to your system. Now we need to configure this account. It will be tailor-made for giving presentations and to make the process as smooth as possible for you or your guest presenter.
Make all the small tweaks
Since this is a vanilla user account, we’ll need to go in and tweak all the little OS X settings to our liking. I want to see my disk drives on the desktop, I want the sidebar text to be set to “small”, I want tap-to-click on my trackpad as well as two-finger-right-clicking. Take a moment and set things up to be comfortable. Most importantly: Make sure Finder is configured to show external drives on the desktop. If your guest presenter is loading a file from a thumb drive you want that drive to be dead-easy to find.
Don’t log into anything
This is key. No iCloud, no email, no iMessages, no Google, no anything. Don’t do it. Do not sync your contacts, calendars, bookmarks, nothing. You don’t need any of that in this account and you don’t want a co-presenter to be wading through that crap either. The one exception is Dropbox, and I’ll explain why below.
Clear the dock
Regardless of how you like it with your personal account, make the dock visible, and perhaps a little larger than you’d normally like it. Now remove everything from the dock except the essential presentation-giving items. My presentation dock looks like this:
You want to have only the essential tools at hand. You aren’t going to be checking your email on this user account, so why have Mail in the dock, right?
You’ll notice that I’ve included System Preferences. I don’t normally have this in my dock on my main account, but here, it’s nice to have it immediately at hand should something go awry and you need to change a setting on the fly.
Set your defaults
I don’t have Flash installed on my computer and I use Safari as my default browser. Since Google Chrome has Flash built into the browser I keep it around just in case I encounter a site that, god help me, requires Flash. If I encounter a site in Safari, I just quickly switch to Chrome for that short while. Having Chrome as the default here means that if I click any links, I know they’ll open in a Flash-Friendly browser.
But remember, you aren’t the only one using this Presentation account, and your guest presenters may not be as tech savvy as you. You also can’t anticipate what kind of content your guest presenters might be displaying. Having Chrome as the default ensures that if you or your guest presenter needs flash, you aren’t doing the browser-juggle just to get things right.
A little amphetamine goes a long way
Avoid having your display fall asleep in the middle of a presentation by installing a small and free utility called “Amphetamine” (Mac App Store link). This menu bar utility prevents your computer’s display from falling asleep regardless of what your system preferences settings are. In my presentation account I have Amphetamine set up to launch at log-in and to be enabled by default (I also use Amphetamine on my main user account but not in this way). This means you never have to think about your display settings when giving a presentation. As soon as you or your co-presenter logs into the presentation account, Amphetamine is enabled.
You can, of course, simply adjust the “Energy Saver” settings for this user account to set the display to “never sleep”, but I appreciate that Amphetamine offers a visual indicator of it’s current status. Another advantage is that, should I need to, I can make an adjustment a bit more easily compared to the Energy Saver settings. Also, since I run Amphetamine on my main user account (though in a much different way), I have it installed anyway, so why not use it?
Share only the right files, only the right way.
You won’t be doing any actual presentation-building in the presentation account, in fact you’ll spend almost no time in this account aside from actually delivering the presentation! That means you’ll need a way of getting your presentations from your main user account to your presentation account. I have several mechanisms in place to facilitate this: Dropbox Selective Sync and /Users/Shared folder. They serve different purposes.
A dedicated sharing folder
In the /Users/Shared folder, I created a folder called “Presentations”. This /Shared folder is accessible to all user accounts on the computer, regardless of their administrative status. This means anything you put in where while logged into your main account is accessible to your Presentation account. In my presentation account I created a desktop shortcut to this folder too, again, to make things as obvious and accessible as possible for myself or anyone else who might be presenting from my computer.
This system works very well in situations where I am emailed a presentation in advance from a co-presenter, or for when I do one-off presentations such as at conferences. Once the slides are finalized or received by email, while logged into my main user account I place a copy of the presentation in /Users/Shared/Presentations and I know it will be accessible from the Presentation user account.
This folder is also only modifiable by an administrative user, which means that in order to delete or add a file when logged into the presentation account you’ll have to enter the admin user name and password. This protects against any guest presenters doing unwanted modifications to contents of this folder.
Of course, the cloud is nearly ubiquitous these days, but we are setting things up to use a minimum number of logged-in accounts, so minimizing the number of services in use is ideal. Also, as we’ve all experienced, some venues can have little or no wireless internet access. We don’t want our system to be brought to its knees because it relied on an internet connection.
Dropbox is the only exception to the “Log Into Nothing” rule. Most of my work is stored in Dropbox, but only a small amount of that work is actual presentation files, so I don’t want all of it to be accessible to the presentation account, nor do I want it all duplicated on my hard drive. Since I give presentations in my course lectures every week, I don’t want to manually move files into and out of /Users/Shared/Presentations; doing so on a regular basis is error-prone and it can be a bit frustrating if last-minute course announcements need to be added to lecture slides. It is therefore ideal to be able to have lecture material live in only one place. To do this I set up Dropbox on the Presentation account to sync only the folder that contains those presentations, and nothing else. This prevents all that other Dropbox data from being accessible from your Presentation account and occupying space on your computer.
This strategy is best for content that you will be accessing on a very regular basis and for long stretches of time. Courses are 4 months long and occur every week, so this is the ideal situation to set up selective sync for that content rather than moving one or more lecture presentations into and out of /Users/Shared/Presentation multiple times a week.
This is, of course, the easiest. On presentation day, your co-presenters can just plug a thumb drive in and be ready to rock and roll. You’ve already indicated in the Finder’s preferences that external drives should show up on the desktop so there should be no difficulty in locating the file!
Open everything for the first time
In order to ensure a nice smooth presentation, you’ll want to take a moment right now to open every application that you expect might be used: your web browsers, your presentation software, insert a thumb drive, and so on. Just take each program for a spin. If you will be on an institutional wireless network such as the one at your university, be prepared to re-login to that with this new user account (remember, no iCloud Keychain to pass along your credentials!). By going through this process now instead of on presentation day, you’ll deal with all those one-time-only first-launch dialogue boxes that all applications inevitably display. You may also find you need to re-authorize your Office 365 credentials if you are using any Microsoft software. Better to do that now, rather than scrambling moments before you or a guest presents!
Take advantage of Fast User Switching
OS X offers the ability to have multiple users logged into the computer at one time. This means you can easily switch between your main user account and your presentation account without needing to close applications or log out (Though you might want to remember to close any file you plan to open on the other account!).
A word about Windows
If you’re reading thing and work on a Windows machine, all of these principles are transferable, the steps may just be a bit different.
You’re now a presentation ninja
This seems like a rather daunting list of steps, but in reality you should be up and running in 20-30 minutes and you’ll never have to do it again. You can now enjoy your secure little presentation silo, free from embarrassing notifications and narcoleptic computer displays.
In an earlier piece I challenged the notion that the defect-to-donation model is a way of solving food waste and food security issues. Essentially I argued that stocking food bank shelves should never be considered a move towards resolving food security. It is not. The very existed of food banks, and their shelves, points to the pervasiveness and persistence of food insecurity. Moreover, the growing trend towards diverting food from landfill to food banks for quality or safety defects isn’t a solution to food waste, it’s a clear indicator of excess and the inflation of standards to match. It’s hubris. It is dehumanizing. It is opportunistic.
We do not want our food banks to exist. We look forward to a time when they disappear. We do not want to get too comfortable. We must resist the temptation to expand. I do not think having a food bank on every street corner is a way for our society to go. Foodbanks must do their best to remain ‘unusual’.
A recent article in the Guardian UK reasserts the well-known trend that indicates food bank use has become routine for a growing number of people. What’s troubling for the various people interviewed is the absence of any mechanism to lift people out of food bank-reliance. Indeed, the absence of an “exit strategy” is further evidence of the extent to which the state (of the UK, of Canada, or the US; the situation isn’t terribly different) is already failing to address the root causes of food insecurity. Initiatives such as those developed between the USDA and industry to divert food from landfill to charities, detailed in my previous post, furthers the tendency towards state-non-involvement and reaffirms the sloughing off of responsibility for social welfare to industry and civil society.
Though none of this comes as a surprise, it aligns well with the political trends of the last 30 years, it is nevertheless disappointing.
This could have disastrous consequences.
On this, the day Doc and Marty arrive in the future, the Canadian federal government has a sense of humour. Don’t worry though, Doc Brown’s got a fix.