Page is a not externally linkable
grelmar - 11:31 am on May 5, 2009 (gmt 0)
Part of me gets a chuckle out of the childishness of it all. But Maone went pretty far over the line with this. He'll likely face some significant consequences from the community for this once word gets around. On the plus side, it's going to result in a lot of extensions getting better peer review. There's no real approval process for FireFox extensions, and once an extension makes it across the small enough hurdles placed in front of it, then updates tend to get a free pass from the community. It had to happen sooner or later that one of the major extensions got caught in a bit of monkey business. Now that it's happened, hopefully to extension community will start looking at each other's work more closely. With luck, some of the nagging bugs that have plagued the extension community will iron themselves out now. I'm thinking of the problems with memory leak (which is partly the core app's fault, but is worsened by poorly coded extensions), some of the cross extension conflicts, and just overall stability issues.
Hmm...