As to wikis being hard to maintain, if a spammer gets the login, just change it; or grant individual accounts, and watch. Why many independent wikis don't work, is because access is not
, or it is not checked for spam. With individual accts., you could just delete the acct. of a spammer, since you can see who did what in the history. I doubt more than a half a dozen ppl will ask to update the extension compatibility wiki - especially ones who have posted here a handful of times and sound like they have a clue of what they are asking for. Thus, I consider easier than represented.
Moonbat presumably has a point, however. If PM goes back to a PM GUID, and that fixes a lot of CAA extensions, then I'll have no issues except hiding the title bar like in Basilisk with the various bars configured as I like; but this is only an annoyance, not a stopper. I'll hold my horses for now. If enough extensions work in 3.0, then an extension compatibility wiki would be moot point.
Alternately, I would have no grudge against an automatic extension converter such as the one for SeaMonkey, which I remember using from before. Here's the link:
The source is on GitHub. Perhaps it changes GUIDs; which would be another option to support older extensions.
That being said, I'm still using Basilisk, and loving it. There are a few websites that break; but I can get stuff like YT, Bitchute and Yahoo Mail (I know, I'm looking at getting something better) to work. Bitchute breaks the player, so I must use a GreaseMonkey script to fix it (which breaks the comments and the search, but I can get by by toggling it on and off), and GreaseMonkey does a lot to improve my YT experience. I have to use a recent browser User ID string to use Yahoo Mail right. I look forward hopefully to see what will be done about extension compatibility in 3.0; but expect to keep using Basilisk until it drops.
Basilisk really had come a long way in recent releases. Both PM and Basilisk had a tendency to chew up a lot of CPU cycles when a lot of tabs were open, and Basilisk I remember until recent versions would refuse to shut down pretty often with many tabs open, and had to be terminated, because evidently some tabs or extensions were still running, and wouldn't shut down. In the final Basilisk, it rarely starts wasting CPU like that, and almost always shuts down promptly when I hit File | Exit. The problem is well over 95% better. Thus, it seems ironic that it was cancelled just as soon as most of its issues got fixed. I am not really surprised, however, that you do not intend to support two browsers indefinitely, if one will do.
Don't get me wrong. I would love to transition to PM and be able to use CAA extensions (with or without auto conversion step) and the PM extensions together. I especially like the new CPU usage and memory usage extensions it has. So, it seems like I've switched browsers a lot to get some of those awesome old extensions working: FF to SM to Basilisk to PM to Basilisk, and presumably back to PM; but I am optimistic about PM 3.0.
I'm trying to break myself of the habit of calling them plugins instead of extensions; but old habits die hard. I am trying.