Cloudbleed

Yes Wago.io is on Cloudflare’s CDN and therefore affected by the recently announced Cloudbleed. I’ll keep this short since you’ve probably seen the announced vulnerability mentioned a bajillion times already.

Wago.io is not forcing password resets for everyone but if you use a local Wago account instead of a Battle.net or other social login it’s a good idea to do so. Keep in mind Wago does not collect e-mail addresses or other forms on identification so there’s no way to reset your password should you lose it.

For more information on Cloudbleed, this post has the best write-up I’ve found on the situation.

WeakAuras 2016 Summary

Infus, lead developer of WeakAuras has put together a nice video summarizing the last year of added features and some hints of what is to come. 2017 is going to be a good year in the World of WeakAuras!

Discuss at the Reddit thread.

Two Months Later... A Vuhdo Appears

Alright, I’m really bad with getting some regular updates. The site continues to grow and bewilder my expectations, but what has happened lately?

The big item is that Wago is now testing support for Vuhdo profiles and bouquets. This works like any other import and you can find these in the new Vuhdo menu item at the top of the screen.

Aside from that, the updates have been pretty minor. But I’ve still got some ideas and should have some time to fiddle around this month! As always, stop by the WeakAuras discord and let me know if you have any more feedback!

An Illusion! What are you hiding?

It’s been a while since the last update - Legion just has so much to do! As you can see, Wago.io has recieved a facelift! Almost everything should be working but there might be a few bits of display related wonkiness.

When I first started this project I thought it might be used by a few people that enjoy tinkering with their WeakAuras, and it would be pretty neat if it could reach maybe five thousand users per month during peak times. Wago took off significantly faster and is recieving more than double that - PER DAY.

Some requests were not optimized properly and the sheer numbers have been slowing everything down. I’ve gone through and refactored pretty much everything and it all seems to be running much quicker now. At least on my test server, we’ll have to see how things hold up.

More to come soon!