Tails Bulletins

• ‘New’ requests are still under consideration.
• ‘In progress’ requests have been accepted. Congrats!
• ‘On hold’ requests have been accepted in principle but have been deliberately pushed back for one reason or another.
• ‘Discarded’ requests have been declined for one reason or another (check the comments)
• ‘Completed’ tickets have been completed in our development environment. They may not be deployed as yet.

Just cleared it all out. Will be adding measures for dealing with spam (along with some other items) this week.

• Themes! You can set a theme per project, and a theme for your profile too. When you invite a new user to one of your projects, that person’s theme will be set to match your project for a totally branded experience.
• New reports system with saved searches. You’ll love this.
• Edit and preview your comments
• Preview your bulletins before you save them
• Email notifications! Hit ‘my account’ and then the appropriate tab to set your preferred alerts.
• Fancy new interface behaviours
• Improved inline editors
  Stuff you can’t:
• Massively improved DB structure and ORM layer
• Far greater use of JS, so we don’t have to serve loads of unnecessary tosh into the DOM just in case you want it
• Waaaay better tag handling
• Improved security handlers and session handling across the board
• Updated to take advantage of new framework features
  Enjoy!

Hi beta lovers,
The much-overdue release candidate of Tails will be released to you all for the holidays. You’ll all have a while to play with it and find any holes in the release before… christ… we launch. Lots of great new features coming!

I just wanted to let you all know what’s up with Tails!
As some of you may know, Tails has been under active (albeit part-time) development for somewhere around a year. In this time a lot of really neat stuff has happened to the Rails framework which we’re simply not using – because it didn’t exist when we built some of our features.
I’m currently in the process of bringing Tails’ code bang up-to-date. We’ll be using RJS, reponds_to for javascript failover, DOM-based inline editing, and more – expect these things to be deployed over the next few weeks and for them to also be completely invisible, since it’s behind-the-scenes stuff.
But you can take solace in the fact that it’s there, right?