We have put out a new flash display for the statistics we collect.  It's just incremental fixes and changes, mostly to help reduce the confusion and help people learn: 'How big is my audience?'.  We're not there yet, as you'll notice a large coming soon sign on a quater of the overall stats portion of the app.  However, we'll be activating those sections very soon, as well as releasing RSS stats (!!!) and tying the LES (libsyn estimated statistics) as well as new term for all you acronym lovers to chew on: LAA (libsyn active audience) into the Kiptronic podcast marketplace. 

The LES numbers most requested by potential sponsors are "Impressions" and "Audience."  We will be offering impressions (LES for all episodes) that will represent activity across your whole show: yesterday, last week, last month, and for all time.  We will also be offering active audience- our score for how many people we calculate that right now, actively listen/watch your show.  This takes into account web downloads as well as iTunes and other podcatchers.  The LAA formula we are using for that has been posted and will be discussed of the forum.

Our SSL certificate is up for renewal, and we have had some difficulties getting the new one in. There is nothing funky going on, or any of the scary messages the different browsers may give. We will have it resolved shortly.

We had a rough spell yesterday morning (Tuesday, April 13th) from around 7:30 until 9:30am.  Many files on the network were coming up as "Not Found." 

This was a regrettable side effect of a new measure we've been trying to fit into place over the past few weeks. The new measure is meant to give improperly formed links a better chance at finding their destination file.

While the implementation of this measure has been rough and presented us with a number of unexpected issues, the end result will be a more fail-safe and balanced network. 

Our apologies for the intermittent troubles.  We'll keep you posted here on the progress / any ongoing issues with the media delivery network.

If it looks like your stats are missing newer files, here's the story: I rolled out a new version of the stats engine yesterday to support some upcoming features, but I added a bug.

This bug fails to put the right date on some files.

If you appear to be missing some files, check the bottom of your stats page: probably they have been tagged with what the unix world likes to call the "Beginning of Time" (1970).

I am working to correct this bug and should have the fix in place this afternoon at some point.

If you have sent a ticket to support, thank you! You'll get a reply. I'll be using your reports to ensure that the fix actually does correct all the possible problems from this bug.

-Bluejack

PS: For the technically minded: stats keeps a local cache snapshot of the master data for all shows; in this new version, the local cache is failing to get the correct upload time from the master database. I changed some of this code in order to more gracefully handle dates for shows that are no longer in the master database, but clearly I missed something important. In order to fix the bug, I will need to find the erroneous caching code & rebuild the cache & roll a new stats app.

We experienced a couple of bugs this monday related to upgrades to the system.  Early this morning the system was timing out and delivering 404s on some requests.  A bug was discovered later in the day where some file redirects were delivering the files of other libsyn users.  We have since restored things to normal and will work to make sure these problems are prevented in the future.

We have resolved the domain mapping problem.  Any users still experiencing any domain related issues please contact us at support@libsyn.com with subject "Domain Outage 4/9/06".

We are experiencing a temporary domain name glitch this evening. Accounts that utilize domain names are resolving to the libsyn homepage. We expect to have this resolved soon.  We will follow up with an update. After which, any users experiencing any domain related issues please contact us at support@libsyn.com with subject "Domain Outage 4/9/06".

Over the course of the next 24 hours, we will be migrating the delivery nodes of the libsyn system. The upgrade will allow for better performance and ensure more accurate statistics for those folks who inadvertently link directly to the edge nodes instead of http://media.libsyn.com/media/username/file. That is still the proper way to link to your media, but sometimes the improper links get out there.. maybe someone who likes a show copies the url and posts it somewhere else. We've seen an increasing number of these types of occurrences, and this will fix that. We've been trying different options for a while now, and have finally come up with a solution that we are confident with. You wouldn't believe the weird things that happen with some file types. Did you know if you pass a query string to a .m4a file, quicktime won't play it in a web browser? Ya, we found that out the hard way. So, as always, please bring to our immediate attention any delivery issues that you see over the weekend. We want to make sure the ship is tight before the monday morning rush.

A mysql error blocked connections from our stats database from 2:05:36 am to 4:47:13 pm; we will be recovering the data and restarting the stats system within the next couple of hours.

Apologies to all, and thanks to those who brought the problem to our attention.

--Bluejack

In the middle of routine updates to the DNS server, we ran into a little glitch that has caused some widespread panic and redirection problems.

Our boys are hard at work fixing the problem and should be resolved very shortly.

---

update:  Everything is cool now. Nevermind the glitch.

For people who see the full KTML/WYSIWYG text edit box, and still wish to author HTML in an external tool (like Dreamweaver) and paste it in, you must first click the "W/H" button which flips the view into html mode. Then if you enter code, you can flip back to WYSIWYG mode and see the html rendered. It is important to not paste HTML code on the WYSIWYG side, as the tags will get displayed in your blog page, and look like crap. Example: http://libsyn.com/forum/viewtopic.php?p=7298#7298 Thanks for the heads up on this everyone who wrote in.

Finally, after a stupid year and a half, we have WYSIWYG publishing. It's still not yet ramped up to everything it will be, but we want to get something out there and people trying it out.

Problem is, it doesn't work with Safari yet :(
But for the Firefox, IE, Netscape 8 users (maybe Opera, gotta test) please let us know how the wysiwyg editor works.

Things you can do:

• bold
• italics
• font colors

1. Numbered
2. lists