Hey Matt,

Thanks for the valuable feedback. Comments below:

You do bring up an interesting point. You may be right that some users don't mind the security risks, but part of our job is to pro- actively protect our users from potential attacks. It wasn't an easy decision to make, but the fact is that inlined gadgets has always compromised security in various ways. The truth is that many users do get scared away from the opt-in message that gets displayed when adding a third-party inlined gadget. So I do think we need to keep this in mind.

In addition to security, there are other complications and limitations surrounding inlined gadgets such as the inability to add them to other pages, etc. However, this is probably irrelevant to someone who really wants to use inlined gadgets for their own personal use.

Yes. After the switch is flipped, you can continue to update inlined gadget as you normally would.

Possibly, which is part of the reason why I posted the announcement in advance. However, I can't guarantee that they'll make it in since they'll probably have very low traffic. I'd go ahead and create them anyway as you might as well try.

Inlined gadgets do not have to exist in the directory to be qualified although you should make sure they are getting some volume of traffic.

Yes, technically this would be possible and may help with the transition. However I don't have any updates on whether this will be available in the near future. These are container-specific features that only apply to iGoogle. So there's naturally going to be some debate over how useful this would be to the general public.

Hope this helps,