Selling Cats Without Enabled Pedigrees

[Tad Carlucci]

The issue with a global enable is that it requires a network transaction (from the Mothership to Second Life) for each cat. If your Pedigree has more than a few cats (which is virtually universal), checking or unchecking the option will run afoul of bandwidth throttles put in place on the Second Life side. This throttle should last a few minutes but, the last time I triggered it, it required a region restart to clear it.

Technically, one could work around the throttle by pacing the transactions. But, I imagine, very few users would understand, and most would complain, when it took hours (or days) for a single check, or uncheck, to take effect. This, by the way, is the reason the current implementation can take up to five minutes, per cat, to take effect. As was pointed out, above, changing the prim mode, cycling through the Cattery, or any other operation which results is a fresh copy of your cat bypasses the current traffic pacing slowdown for the option.

The only implementation of the feature which I can envision is an option which only effects new cats appearing on your Pedigree. That, of course, is no help at all to those who currently have large Pedigree rosters. For them, the only way to make use of a global option such as this would be to pass all cats and boxes to another avatar, and back, and, then, it cannot work for no-transfer (starter) cats and boxes.

All in all, the current system is the best we can have.

---

As to the request that the Pedigree link be made permanent rather than expiring after a short while: while I fully support the suggestion, the current restrictions reflect a management decision and, while I don't fully understand nor agree with the logic behind it, I also cannot envision a compelling argument for changing it. This seems to be a case where the experience and philosophy of the management trumps public opinion.

My experience, with a competing product, which allowed full, public access to their entire Pedigree-like family tree database was, while it did not appear to cause any problems for them, it did cause a significant number of problems for me as I was often accused of somehow breaking into their systems to obtain the information I was collecting when, in fact, I was simply using their public web interface (and, at that, only doing my information collection by hand rather than using computer systems to automate the process). In fact, I've occasionally been accused of similar issues with KittyCatS! when I make use of the limited information provided here. So, I view the restrictions more as limits protecting us from others in the community than as a systemic requirement; which, as I said, I don't fully agree with, but cannot see sufficient cause to argue against.

But, who knows, perhaps, with enough requests, a change would be made.