Looks like the approach I recommended doesn't work. The gallery team is building a separate UI for setting the publisher name which should be live by the time we launch extensions to Stable. Until then, thanks for your patience!
~Arne On Mon, Dec 28, 2009 at 3:16 PM, andxyz <[email protected]> wrote: > No worries about any delays. I just wanted to make my issue clear, > besides it's the holiday season (I even responded on christmas eve at > 1am, I was wrapping presents :) I know that posting the issue isn't > the same as coding the solution. > > earlier Arne had said: >> it would be neat to have verified accounts that were visually >> distinguished. > all ya need now is to choose the correct Private Key Infrastructure to > verify users... > I'm just musing here, but don't companies already pay for ssl > certificates. So I wonder if like verifying your domain for google > apps you could ask them to post a > <meta name="chrome-extension1" > content="ldkncohaggllkbadfflamlndkpfanmla (my chrome extensions public > key)" /> > <meta name="chrome-extension-verify" content="some random characters > that google asked for signed with private key" /> > in the html on their https domain. that way you could also verify what > emails they could use to support their product. I'm mostly thinking > that even if someone did use [email protected] as their support-email/ > username then that would give them enough clout to get people to click > install. cause I know that's all I looked at (unlike the average user > I know about the worries of untrusted autoupdating code accessing my > browser in cool yet powerful ways, yet I still clicked) > > happy holi/vacation days > -Andy >
-- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
