Seriously, what's going on in the land of StaticCling? Who is running this thing, anyway? :)

As you've probably come to expect, no updates means everything is a-okay. However, StaticCling's backend tech is showing a bit of age. I started a re-write at least 2 years ago, and got caught up with other "real life" stuff. I'm now starting it up again -- actually posting about it might give me enough motivation via shame to get it done. :)

The rewrite will use PostgreSQL and Arrow, and will sport a modernized UI. It will also expose all of the backend goods via a REST API, so writing some "real" desktop clients should be fun and easy. I'm considering adding subdomain support as well, so you can alteratively mix subdomain pointers with wildcards, under the same top-level account. (Instead of registering multiple accounts for different locations. I'm seeing lots of "bob-home" and "bob-work" stuff -- those would become home.bob.staticling.org and work.bob.staticcling.org, respectively.)

We'll also add captcha signups and automatic "bad netblock detection" to combat the various jerks signing up for link spamming.

I'll keep the same basic principle in place -- dead simple dynamic DNS.

If you have any suggestions for feature adds (within the above principle, I'm not adding Pastie or Link shortening services) -- please don't hesitate to contact me and let me know!

We've already got a new client supporting the secure logins (and a bunch of other neat features), written by Rocon Software. (That was fast!) Find it here.

Meanwhile, I've been sitting on a 220 line patch to add StaticCling support to ez-ipupdate, a popular open source updater. Other projects use ez-ipupdate as a backend for their own dynamic dns support (such as M0n0wall) - so getting embedded StaticCling support would be great. Unfortunatley, the ez-ipupdate maintainer seems to have dropped off the planet. Anyone out there know how to get ahold of this guy? :)

Well - not a lot! As usual, no news is good news. StaticCling just keeps on truckin', doing its job as advertised. The user base keeps growing, so more and more of you are telling your friends to use us. (Thanks!)

I started on some new clients almost a year ago now (yikes!) - but real life caught up to me, and they never got off the ground. These new clients are for every platform, and are complete re-writes - supporting lots of nice bits - the most notable being challenge/response secure updates. As of now, only the perl command line client is in a usable state, so we've updated the clients page with that. The rest of the platform clients will be updated as I force myself to work on them. Thanks for hanging in there in the meantime with older junk. :)

Hello from your newest StaticCling admin! I've been working behind the scenes as StaticCling's Official Unofficial Beta Tester™ since before the site went public. I also contributed the icons to the StaticCharge Clients. As a welcoming gift from me to all of you, I've created a new theme for the site.

Mahlon and I have always appreciated the old design of Dave Winer's Scripting.com. It was clean and in our opinion beautiful. We were pretty bummed when he changed the design of the site, but an idea was born. Thus we have the theme I've named "tribute" because that is, in fact, what it is. You can give it and all the other themes a test drive by visiting the "misc" page.

I hope you all enjoy the theme and I hope to have a few more tricks up my sleeves for the next releases of StaticCharge. I'll also be helping to take some of the load off of Mahlon when it comes to support emails, so don't be surprised if you get a reply from me. Remember, we don't advertise so be sure to tell your friends about us so we can grow.

We've had 2 separate 2 hour outages, and one 4 hour outage in the past month. As best as we can tell, this is due to an intermittant disk error that hangs the main machine. It's proving to be a beast to troubleshoot, because we can't do any diagnostic work after the machine is hung, and the disks pass every test we throw at them otherwise. This is just a heads up that we're aware of the problem and are working on it!

older news