Categories
Burningbird Technology

Server is moved

Moving to a new VPN (Virtual Private Network) was as simple as signing up for a second Linode instance, and then building it to my specs. Eliminating half the cruft I had on my old system saved about 40GB of space. Now I have room for all new cruft.

I decided to stay with Drupal for this site. Frankly, I just don’t want to muck with content systems anymore. I have a couple of new sites on WordPress, this on Drupal, and that gives me a foot in two worlds. I was reading that the Drupal 8 upgrade should be button-press easy, especially if you haven’t customized your site. Sure sounds simpler than fighting to get it into WordPress.

Linode’s new billing system made the move a whole lot easier, and cheaper. I was only charged for the double VPN until I dropped the original once the move was finished. I think I’ll take this approach the next time there’s a major Ubuntu upgrade. Not only can I cleanly upgrade, this approach gives me a chance to clean my system.

Categories
Government Standards

Corporate food production interests yank the chains of Congress

Second update

House just can’t wait to pass this bill. It goes to the Floor on Thursday. Note: there is no comparable bill in the Senate.

stirring up a batter of trouble

Update

In the ultimate of ironies, the Senate passed an amendment to their appropriation bill, that would require genetically modified salmon be given a GMO label. How to explain the inconsistencies?

Sen. Lisa Murkowski (R., Alaska)…downplayed concerns that salmon labeling would set a precedent for labeling biotech crops saying, “Corn doesn’t swim from one field to another and propagate with corn in another state. Fish move. Fish escape,” she said.

No, no. No one has ever heard of pollen floating on the breeze and contaminating organic crops.

earlier
How can you tell if Vermont will prevail in the lawsuit filed against its new GMO labeling law, Act 120? Easy: Congress decides to create a national anti-GMO labeling law. More on this in a moment. First, though, a recap on the court challenge.

In April, Judge Christina Reiss issued a decision denying in part and granting in part Vermont’s motion for dismissal, and denying, outright, the *plaintiff’s motion for preliminary injunction. The latter means that when you consider how speedy civil cases of this nature proceed through the court system, Vermont’s GMO label law will be able to go into effect in 2016.

The Judge quickly dismissed the dormant Commerce Clause challenge to the GMO labeling. After all, the basis for this challenge is that a state law must discriminate against out of state interests, and Vermont’s law applies to in-state as well as out-of-state interests. The decision also reflects a growing push-back against the application of the dormant Commerce Clause, possibly reflecting the Supreme Court’s own ambivalence about its application. I particularly liked the Judge noting that Vermont’s GMO labeling law won’t lead to a “patchwork of state laws”, because no other state has implemented a GMO labeling law, and hence, no inconsistency is introduced with Vermont’s law.

The Judge did feel that the plaintiff’s claim about the law’s reference to the use of “natural” on labels was strong enough to warrant denying Vermont’s request to dismiss the Commerce Clause challenge related to it. Yeah, that was one Vermont would have been best to just leave out of the GMO law.

In my original writing on the law, and the legal pushback from Lauren Handel, we felt the strongest challenge to the Vermont law was the Supremacy Clause, and whether the law was expressly preempted by the labeling requirements in the FMIA (Federal Meat Inspections Act) and PPIA (Poultry Products Inspection Act). The FDA’s FDCA and NLEA are both quite amenable to state labeling requirements, so aren’t really a challenge. The FMIA and PPIA, however, do have strict label requirements, and do assume federal authority of said labels.

Vermont was aware of this, and built into Act 120 exemptions related to meat and meat products, which should encompass those products that would be covered under the FMIA and PPIA. Where we felt there was the possibility of conflict was a product like soup. Soup is a manufactured product and, we assume, would be covered by Vermont’s Act 120. Soup can either contain meat products, or not. If the meat content exceeds 3% raw, or 2% cooked meat, then it would be managed by the USDA; otherwise, it’s managed by the FDA. This soup conundrum reflects the truly mish-mash nature of food safety handling in the US.

Since Campbells is part of the group suing Vermont, I fully expected soup to raise it’s head at some point. If it did, though, it quickly ducked. According to Judge Reiss’ decision:

In opposing dismissal and seeking preliminary injunctive relief, Plaintiffs narrow their FMIA and PPIA preemption claims to argue that some GE food products that contain meat, poultry, and eggs which do not fall within Act 120’s exemption for products “consisting entirely of or derived entirely from an animal,” 9 V.S.A. § 3044(1), are regulated for labeling purposes by the FMIA or the PPIA. They identify canned meat and poultry products and pre-made frozen meals containing meat or poultry as examples of products that fall within both statutory frameworks. In their Amended Complaint and declarations, however, Plaintiffs fail to identify even one of their members who produces a non-exempt GE food product that is covered by the FMIA or PPIA.

In other words, something like chicken noodle soup would either be exempt under the Vermont law, or isn’t a food product covered by the FMIA or PPIA. According to the FSIS guidelines:

Although FSIS has jurisdictional authority over food labeling for products containing meat and poultry, the FMIA and the PPIA explicitly authorize USDA (through FSIS) to exempt from its regulatory coverage food products which contain meat or poultry “only in relatively small portion or historically have not been considered by consumers as products of the meat food industry …

Soup is, typically, not considered a product of the meat industry, no matter how much meat it contains. And let’s face it: most canned soups really aren’t brimming with meat.

If there are no products not exempt under Vermont Act 120, but governed by the FMIA and PPIA, the plaintiffs can’t establish standing for this particular challenge. The only reason the Judge did not dismiss the preemption challenge outright is because the plaintiffs argued there may be small food producers who are making such a product who haven’t been identified yet.

We can only imagine food producers all over the country are working late into the night, trying to create and market some product that falls between the infinitely tiny crack that may exist between the Act 120 exemptions, and FMIA and PPIA governance.

Judge Reiss than took on the First Amendment challenge to Act 120. The plaintiffs claimed Act 120 violates corporate freedom of speech because Act 120 is “a politically motivated speech regulation”—it compels political speech. Well, this is just plain rubbish. The Judge agreed, though more tactfully:

A manufacturer who is required to disclose whether its products contain certain ingredients is not compelled to make a political statement even if such a statement “links a product to a current public debate” because “many, if not most, products may be tied to public concerns with the environment, energy, economic policy, or individual health and safety.”

The more compelling challenge related to freedom of speech was whether Act 120’s disclosure requirement is nothing more than just a satisfaction of consumer curiosity. This is what torpedoed Vermont’s statute related to labeling milk that contains recombinant Bovine Somatotropin (“rBST”) or recombinant Bovine Growth Hormone (“rBGH”). However, unlike that statute, Act 120 did raise the debate about the safety of GMO products, in addition to other factors:

Act 120’s “Findings” and “Purpose” extend beyond the mere appeasement of consumer curiosity, and the State emphasizes that it is not making the concessions it made in IDFA. It cites to what it characterizes as an ample legislative record documenting the scientific debate about the safety of GE ingredients and the studies that have produced positive, negative, and neutral results. This record includes studies about the safety of consuming GE plant-based foods, as well as studies about the environmental impacts of GE and GE crops. The State also points to its interest in accommodating religious beliefs about GE, as well as its interest in providing factual information for purposes of informed consumer decision-making.

The Judge did feel the intermediate scrutiny of Act 120 as it relates to the First Amendment was a question of law, and should be debated during the court hearing related to the case. Therefore, Vermont’s motion to dismiss was denied. However, the Judge also felt that the plaintiffs were unlikely to prevail in this challenge in the court, and their request for a preliminary injunction was denied.

Judge Reiss wrote a long, thoughtful, and careful decision. Though the plaintiffs case was not dismissed outright, many of its challenges were dismissed, or had doubt cast on them as to their viability. And that leads us to HR 1559, the so-called Safe and Affordable Food Act, which just advanced from committee to the House floor. How can you tell if Vermont will prevail in the lawsuit filed against its new GMO labeling law, Act 120? Easy: Congress decides to create a national anti-GMO labeling law.

This bill seeks to preemptively undercut Vermont’s Act 120, before it has a chance to take effect. Many of its proponents are people who consider themselves tried and true “states rights” advocates…well, up and until a northern state, like Vermont, passes a bill that goes counter to select interests in their state. Can’t have them uppity Northerners telling nice southern and midwestern corporate boys what to do, no sirree.

Regardless of your stance on GMO and labeling, the bill should give you pause because it seeks to use Congress to bypass state statutes that reflect the interest of the people of the state and that have withstood a constitutional challenge.

That latter is important. Vermont’s Act 120 isn’t seeking to prevent gays from marrying or women from having access to abortion. It’s a statute impacting on commerce that ensures additional information is provided to consumers. More importantly, it’s a statute that has not failed in the courts—has not proven to be unconstitutional.

It has long been the right of states to impose stricter restrictions on commerce, particularly commerce related to food production, as long as such a restriction doesn’t unfairly impact out-of-state interests. Revoking this right because corporate agricultural interests aren’t happy about disclosing certain information is the proverbial slippery step to undermining other state laws related to food production and safety.

Want to drink raw milk? You can in states that allow it, but not in states that don’t, but this could easily change if the raw milk dairies had enough influence in Congress. Want to allow cottage industries to sell meat products or other food items long restricted? Again, no problem…if the industries have enough influence.

Of course, that’s the real key, isn’t it? These other industries don’t have the power to bring about change at the Congressional level, and that’s not a bad thing. But the GMO labeling law impacts on the very powerful, very wealthy, and very influential chemical, biotech, and food manufacturing interests, and therefore, this particular state law triggers Congressional action. And it does so not in the interests of the consumer—it is a deliberate attempt to withhold information from the consumer. Only the powerful benefit from this bill.

Regardless of your views on GMO labeling, you must deplore such an obvious act of buying Congress.

The biotech, chemical, food manufacturing et al interests have their chances in the court. Our Constitution is giving them their chance. They have the ability to bring their best arguments to the table and defeat Act 120…in the court. With this House bill, they chose not to do so. Instead, they’re putting pressure on Congress, and Congress is allowing them to. It’s a dirty move that is no less dirty because you may not agree with GMO labeling.

* The plaintiffs have filed an appeal related to the denial of a preliminary injunction, and asked for expedited handling of the appeal. This request has been granted, with back and forth filings due by September 8th.

Categories
Burningbird Technology

Mind the scaffolding

image of destroyed front porch

I have attempted to upgrade to Ubuntu 14.04 from 12.04.5 three times, failing each time. The points of failure are complex and seemingly many. I can ignore the necessary upgrade until 12.04.5 hits end of life in 2017, but whatever cruft is preventing a clean upgrade may be allowing all sorts of bad things. I also use my server as testing environment for all of my books, which means I’m constantly installing and uninstalling a host of software. When I ran

ubuntu-support-status

I was surprised at how many packages I have installed that are no longer supported.

No matter how much I want to avoid it, It’s time to clean up my system.

Not just clean up. I want to move my site to HTTPS/SSL. The new Let’s Encrypt Certificate Authority should be in business in September, simplifying the process for obtaining an SSL certificate, and removing a major obstacle for making this move.

I’m also looking at migrating my site(s) back to WordPress from Drupal. Drupal is a marvelous CMS when you like to tinker under the hood, or you have a business site that needs extensive customization and complexity. But it’s not a good CMS when you don’t have the time to tinker, and you just want a place to write. With the upcoming changes for Drupal 8, I realized that I could either migrate to the new version, or I could migrate to WordPress: the work would be the same.

The advantages to WordPress is it is geared more towards just having a place to write. There is also more updated support for social networking, commentary, mobile devices, and a larger pool of weblog themes. Drupal is powerful, but I’m finding many of the modules I’m interested in have erratic support, at best. The Drupal environment is set up in such a way as to channel all interest in a certain functionality into one module. This is fine, except when the module developer tires of it, and no one picks it up. WordPress fosters a more competitive environment for functional extensions, so you’re almost always going to be able to find a supported plugin for what you need.

Moving from WordPress to Drupal is a snap, but the reverse isn’t true. In fact, it’s been downright ugly in the past, requiring either a great deal of hacking, or an expensive migration service. Thankfully, this has changed with a new PHP script and associated tutorial, both of which help remove most of the pain. I hope.

I expect, though, that my site will end up even more fractured than it is now, with my many moves between domains, weblogs, and software—not to mention removing dated content, and merging and splitting weblogs. Such is life. One of the advantages of today’s web environment is it’s adaptable to change. A broken link is no longer the anathema it once was, and 404 errors are like gray hair and bad knees: a sign of increasing maturity.

All of this is my way of saying that things are going to be erratic around here for the next couple of months. Of course, I’ve been so quiet in my space for so long that folks might not even notice the erratic nature of my web site. I’m hoping to get better about this, too.

Categories
Social Media Technology

Facebook’s astonishing fail

update

I did find a reference to this type of behavior…from 2010.

What I suspect happened is some very old security code accidentally got compiled into the Facebook server app, in relation to the company’s new security feature, and I just happened along when it was exposed.

Either that, or I stumbled into a time vortex.

earlier

I treated myself to a new smartphone today. Among the apps I loaded was Facebook. I had copied my password from Dashlane and was ready to go, when I ran into something new:

Facebook’s new security system.

To prove I am who I am, Facebook displayed a set of images, each with a set of names, and asked me to pick the person who matched the image. OK, this ought to be good.

The first was an obviously 30+ year old photo of a chubby baby. So who is it?

I’d have a hard time recognizing one of my own baby pictures, much less the folks on Facebook. Especially considering many people, such as myself, don’t even use photos of themselves as their Facebook profile pictures. So, next image, please.

The next showed a cartoon strip, with a square around one of the panels. The security question then asked who the image was. I can tell you that it isn’t Barbara Schmitz or Nanny Baker.

The third showed an image I did recognize: Mr. Presidential Candidate Rand Paul. Which means it wasn’t Kevin Stamps or John Doppler.

The thing that saved me was when another photo of a woman looked like Sarah Barnett. Thankfully, Sarah also had a conference pass around her neck with “Sarah Barnett” printed on it. But by that time, I’d taken too long or missed too many images, or some such thing, so I had to start over.

Facebook…you’ve taken “being completely unaware of how people use your web site” to a level never before heard of, or seen. And then you exceeded it by using your complete lack of understanding to form the platform for your new security system.

Categories
Just Shelley

30 Years Ago: Mount St. Helens

Thirty years ago I was living at my Dad’s in Yakima, going to college. That Sunday was a beautiful day, and Dad was outside in the garden as I was getting ready to go to work. I worked for a photographer who had a studio in the Yakima Mall. I liked working Sundays. Sundays were always quiet, especially when the weather was nice.

I heard a loud boom but didn’t think much of it. Yakima was right next to a military training center and it wasn’t too unusual to have a hot dog pilot break the sound barrier. Some minutes later, my Dad yelled for me to come outside. I ran out and saw this ugly dark brown/black cloud rolling towards the town. We knew that Mount St. Helen’s had erupted.

We ran inside and quickly shut everything up. My boss called to jokingly tell me that I didn’t have to go into work. Unfortunately, the Mall didn’t shut down the air intake system quickly enough, and when we were able to get into the studio three days later, all of my employer’s cameras would be ruined.

The day began to turn into night. The ash started falling all around us. It was quiet except for the ash, which made a slight hissing sound when it fell—like a snake who is only going through the motions. On the TV, it interesting to see our quiet little town being the top story for most of the major networks. The President flew by. We waved.

My cat was still outside. I’ve learned since to keep cats inside. Well, I say “my” cat, but Bonzo was really Dad’s cat—a case of love at first sight between those two. I thought he would come back when he saw the cloud, but evidently the ash must have panicked him. I told my Dad I had to go find him. He was torn between wanting to keep me inside, and being worried about Bonzo. Go find him, Baby Doll, he said, but don’t stay out too long.

Yes, he called me Baby Doll. Dad’s been dead a few years now—I don’t mind telling you he used to call me Baby Doll.

I put on a plastic raincoat I bought on a lark once, and never wore. It ended up being a perfect cover for the ash. I wet a handkerchief to wrap around my nose and mouth, though it didn’t work as well as I hoped.

Walking through the streets, looking for my cat, was like walking on the moon. The ash was very fine but so persistent. It covered everything, though it slithered off the plastic of my coat. After about half an hour, I couldn’t handle the ash anymore and came home— hoping Bonzo would be smart enough to find cover.

During the day, the ash cloud would sometimes thin out, leading us to hope the worst was over. Then the ash would thicken, the day darken again. I must admit to being more than a little worried about how long the ash would fall. Would we be evacuated if it fell for days?

Were we in danger?

Towards evening, we heard a faint meow at the back door. I opened it, and there on the step was a mound of ash with two brilliantly blue and really pissed off eyes. Bonzo had made it home.

The ash fell throughout the day and into the evening. The darkness was oppressive, the acrid smell overwhelming at times. Sometime during the night, though, it finally stopped. When we woke the next day, we woke to another world. Ash covered everything.

I used to smoke in those days. I had run out of cigarettes, and we also needed milk and some other odds and ends. We couldn’t drive because of the ash, but there was a neighborhood store a couple of blocks away. I knew the store would be open—you’d have to bury that store under lava for it not to open—so I again donned my plastic coat and set off.

If the walk during the ash fall was unnerving, the walk the next day was surreal. You could see tracks of animals, including that of a bee that had become so weighted down, all it could do was squiggle along the sidewalk. Bird tracks, cat tracks, other small critters—no people tracks though.

People were out and about, primarily shoveling ash off roofs because the weight was enough to cause some real concerns. Others, seemingly indifferent to the effects of mixing ash and engine, were out driving, and their cars would send up clouds of acrid dust. Some of our more enterprising neighbors built a speed bump of ash mixed with water, which worked pretty good until the street crews knocked it down.

For the next three months, we cleaned up ash. In the beginning, we wore a lot of masks and some folks took off for ashless climes. Silly, really, because bad stuff happens everywhere. If you’re going to leave a place, you leave it before the bad stuff happens. Otherwise, you’re just moving from bad stuff to bad stuff.

My Dad used some of the ash from around our place to mix into cement for a new sidewalk. Other people created souvenir statues from the ash. I bought a t-shirt that said something about the mountain and Yakima, but I can’t remember the words now. Probably something that seemed clever then, but would be stupid, now.

A day by day account at the Yakima Herald Republic.

St. Louis Today photo gallery.