Friday, August 29, 2008

Barcode Waffle Weave Off The Loom

By Leigh

My waffle weave fabric is finally off the loom, washed, dried, and ready to be cut and sewn into towels.

Leigh's barcode WW fabric off the loom.
I used 10/2 unmercerized cotton, sett is 30 epi. That weaves up into a nice thirsty feeling fabric. You may recall that this is for a towel exchange withing the Western North Carolina Fiber/Handweavers Guild. You may also recall that I got the stripe pattern .....

Leigh's interpretation of the barcode below.
Barcode for the Western NC Fibers/Handweavers Guild
.... from a barcode of the Guild's initials. I think it translated quite well.

The finished towel size for the exchange is to be 18 by 24 inches. I figured the width in the loom based on my sample, which had a draw-in and shrinkage of about 30%. After weaving a bit on the towels, I recalculated, and was worried that the finished fabric would be too narrow. That's when I came up with a way to widen the warp on the loom (that post here.) OK. That slowed me down a bit until the added warp sticks were firmly wound onto the cloth beam.

Ironically, the wet finished cloth now off the loom measures 19 inches in width. The original 10 inches that I wove on this warp (the one I thought would be too narrow), is 18 inches! So I had it right the first time.

So. I'm just going to chalk this one up to "lessons learned." :)


Related Posts:
Waffle Weave
Light Bulb Moments with Waffle Weave
Barcode Waffle Weave Update
List of all my Waffle Weave posts

Tuesday, August 26, 2008

Cotton Spinning Update

By Leigh

This is how I kept my hands busy while watching the Olympics -

Cotton lint red #1
Cotton lint red #2
Cotton lint orange #1
Cotton lint orange #2
Cotton lint yellow
Spinning cotton lint . These are from my experiments for the Online Guild's recent "Dyeing Vegetable Fibers Challenge" last June.

I'm spinning the approximately 100 gram amounts long draw. So far I've completed two reds and one orange. I'm ready to ply the second orange and then start on the yellow. That leaves me several greens, blues, and purples left to go. Progress is slow and won't be very steady, but I'm enjoying it just the same.


Related Posts:
Summary of Procion MX Dye Experiments
Spinning Cotton Lint
More On Spinning Cotton

Saturday, August 23, 2008

Update on Stolen Content (& a little more info)

By Leigh

Yesterday I checked on the status of my stolen blog posts. This is what I saw:

Yipeeeeee!
What a relief. Since mailing a formal complaint to the site host, I have been checking the site every day.

Prior to filing that complaint, I had contacted the site's owner. Even though they never replied, after several days I found that "View text" links had been added at the bottom of all the stolen posts:

A sneaky way to link back to the original author.What this did, was to link back to my original post, though you wouldn't know that from the name of the link. The "Add Favorite" linked back to the offender's home page, while "Close" did nothing.

This type of link back is a popular scraping technique, in hopes that the author of the original content will think, "Oh well. At least they linked back to me. Maybe I'll get some traffic out of it." However, it doesn't give proper credit in regards to authorship. Sometimes they will use the author's name as the link back. Whether or not this is acceptable is up to the original author.

If you own the content you have the right to choose if and how it is used. Creative Commons has several licensing options, whereby you can choose how you want to allow your work to be shared. I've looked these over, but still, I would like to be asked first, especially considering I don't know where my content might end up. For example, I don't want my posts or photos being used on a site which sells viagra or promotes adult only content. Actually, my preference is that they just say that the content exists and give a link to it.

Even though the site which used my posts has been suspended, I was advised by the host that
If a Counter DMCA (Digital Millennium Copyright Act) is submitted, the site will be reactivated & it will be up to the two parties to figure this out.
In other words, if the thief can provide "documentation" that the content was originally theirs, then I have to find another course of action.

When I first discovered the splog, I spent a lot of time tracking down and contacting some of the others whose content had been stolen. Some of these were interested in doing something about it, others didn't care. I figured that if several people complained rather than just me, we could permanently shut down the site. Hopefully that is the case.

However, because a thief can file a counter-DMCA, I'm not sure that copyright notices are enough. After all, blog post dates can be changed or the stolen content can be edited. That's why I finally decided to register with MyFreeCopyright. This free online service offers 3rd party proof that you hold the original copyright to your online work.

I registered my blog via my blog's site feed url. With each new post I publish, I am emailed dated documentation verifying my ownership of the material including publishing date, title, description, and a digital fingerprint which I can present as proof that I am indeed the original author. MyFreeCopyright keeps this information along with a copy of the original, so that I have 3rd party copyright proof. Hopefully I will never need to use it.

So that's what happened. In some ways I hate the bother of having to add copyright precautions to my blog, but on the other hand, I'm not willing to make crime easy for someone else.

Now, I don't know about you, but I'm ready to get back to fiber and textile content! I've still got waffle weave on the loom, and I'm still spinning that cotton lint. More updates on those soon.

Posted 23 Aug 2008 at http://leighsfiberjournal.blogspot.com

Related Post:
Stolen Content
A Note About Watermarks

Wednesday, August 20, 2008

Barcode Waffle Weave Update

By Leigh

Let's see. In the last episode of my waffle weave adventure (before my little detour after finding some of my blog posts stolen), I had figured out a way to both correct my waffle weave threading as well as widen it. The warp I added for width has been pretty successful, though not without some problems.

What I have had trouble with has been a curving fell. "Fell", for you non-weavers, is the leading edge of the cloth on the loom; the line of fabric made by the last weft thread. It needs to be perfectly straight, or the weft won't beat in properly. Sometimes it curves upward at the selvedges, so that your weaving looks like it's smiling at you. This is the case if the warp at the edges is too loose, or if the weft is pulled too hard through the shed so as to cause unnecessary draw-in.

Initially, I assumed it had to do with the amount of water in my milk jug weights. However, even after adjusting the amount of water and taking care with the weft didn't completely correct this problem.

In analyzing the problem, I realized that the sticks I added to tie the extra warp to (photo here), are not supported by the front apron strings. I suspect that that may be the problem, because those sticks still flex somewhat under the weight of the warp tension.

My solution was to add a second set of sticks in the tabby sheds......

Sticks added to help correct my fell problem.
Close-up of problem & solutionHere's a close-up, in which you can really see the problem with the fell. See the upward curve of the bottom cloth? As a beginning weaver I had this problem a lot. Oftentimes it was simply uneven tension in the warp, especially if I didn't wind it under an even tension for its entire length.

The other problem I've had to learn to correct is excessive draw-in. This appears to be related to either the shuttle itself or how I throw it. For finer warp threads like the 10/2 I'm using, I use boat shuttles. My favorite (because it holds the most yarn) is my 13.5 inch Gilmore shuttle. It holds six inch bobbins, which are almost too snug a fit in the shuttle, though they still rotate freely. With all my boat shuttles, I find that I must take care with the amount of weft pulled from the bobbin before I throw the shuttle. If enough isn't pulled out, there is a tendency for the selvedges to pull in too much.

All this means that I need to pay attention to what I'm doing, which is probably a good thing anyway. However, even taking care to correct these two things, I was still having the problem. So far, my added sticks seem to be working, and I don't have anymore curves to deal with. Hopefully that will remain to be the case! I'll let you know how well it actually works.


Related Posts:
Waffle Weave
Light Bulb Moments with Waffle Weave
Barcode Waffle Weave Off the Loom
List of all my Waffle Weave posts

Sunday, August 17, 2008

Stolen Content

By Leigh

This post has absolutely nothing to do with weaving, spinning, dyeing, or knitting. But it is the reason why I haven't gotten much accomplished in the past several days.

The other day I checked my free StatCounter account, and was browsing visitor paths. This is often interesting as well as useful information. Imagine my surprise when I clicked on one referring link, only to see this (click on the picture for a closer look) -

Yup. It's my entire Computer Hex Code Dyeing 2: Wrestling With Recipes on another website, stolen along with about 4 or 5 other of my posts.

I took a look around this site, and quickly figured out that almost all of its content was stolen from other blogs. In other words it is a "splog" (spam blog). A number of the stolen posts showed copyright information and symbols, but this were stolen along with the text and content.

The question is, what to do? Evidently this is a fast growing problem, much to the frustration of folks like us, who respect one another's intellectual property and just want to have ours respected in return. Is it possible to try and fight back? Well, here's what I've been doing about it:

First I did a whois search at Network Solutions, to try to find someone to complain to....

This gave me the administrative and technical contact whom I emailed, asking them to remove my content. I received no response and neither was my content removed.

My next step was to contact the blog host to report the theft. Toward the bottom of the whois information is an IP address link -

From there, I found this -
This tells me who is hosting the offending website, and how to contact them with abuse problems. After emailing their abuse department, I received a quick response with instructions of what to document and where to send it. By law, they will have to remove it, unless the offender offers a counter claim. Then it's left up to the two parties to duke it out.

In the meantime, I have discovered Who Is Hosting This? You can type any URL into the search box and are immediately taken to that website's host. If the offender doesn't remove the stolen content upon your request, the host is the next one to contact.

Another possibility is to contact Google's AdSense, if that's what the splog was set up to take advantage of. Complete instructions of how to do that can be found at What to do if you're getting as sick as I am of having your blog copied by Ian in Hamburg.

In researching all this, I learned quite a bit. Some folks honestly don't understand about copyright. Others, like sploggers, do it intentionally, without regard to copyright. Sploggers often use hacking tools such as 1-More Scanner or Site Import for Dreamweaver, which find and copy content from all over the Internet. It appears that in my case, the scraping (content stealing) software searched the internet for text with certain keywords. The keyword in my posts was "recipe" (as in dye recipes), which is the category the filed my posts were under on that website.

The only reason I found out about it, is because someone clicked on one of the links in that post which brought them back to me. I have been purposely doing this with every post I publish, and for that very reason. Thieves and their hacking software usually just copy and paste, which leaves links intact (though I have learned that some hacking software can ignore the links).

While links back to yourself might alert a reader that the content has been stolen, they don't necessarily let you know about it. Another helpful online tool is Copyscape, which searches for duplicate pages on the Internet. They allow a couple of free searches a day, or unlimited searches with a subscription.

What else am I doing? Since most theft takes place from feed readers, there are two options.
  1. Change the settings so that only a summary of the post is seen in the reader. This may be a minor nuisance for folks who like to read entire posts in their reader of choice, but it allows only the first paragraph or so of a post to be scarped. For Blogger, click on "Settings" then "Site Feed." Look for "Allow Blog Feeds" and choose "short". Then save settings.
  2. Leave the blog feed setting to "full" but put a copyright notice in the post feed footer at the bottom of the site feed settings page. This notice will show up at the end of each post in the feed reader, which means it will be scraped too.
For the moment, I've chosen to do #2, being sure to include my blog url, http://leighsfiberjournal.blogspot.com/ (in addition to my blog name, Leigh's Fiber Journal) in the feed footer. This is in case the scraper copies the text without their links.

You also probably noticed that I added "By Leigh" at the top of the post, and a posted date and "by" at the bottom. Both link back to my blog.

While there is no way to stop content theft, we can all take measures to protect our digital property. Here are some articles that have been helpful to me, so I'm passing them on to you:

5 Content Theft Myths & Why They Are False
by Jonathan Bailey
The 6 Steps to Stop Content Theft by Jonathan Bailey
Fighting Scrapers With Your Left Jab by Darren Rowse
People Stealing My Content - Blah Blah Blah by TheLostGirl
How to deter thieves from stealing your images and server bandwidth by David Airey

If you do find that some of your content has been stolen:
What Do You Do When Someone Steals Your Content by Lorelle

Since most scraping takes place pretty quickly (sometimes almost instantaneously) after publication, adding all this to back posts may or may not help. I'm still trying to decide whether or not to add a copyright or watermark to all my photos. More bother.

Anyway, that's my tale of woe. I hope all of this will be useful to you!

Posted 17 Aug 2008 by http://leighsfiberjournal.blogspot.com

Related Posts:
Update on Stolen Content (& a little more info)
A Note About Watermarks