Email options

[Jonathan A. Marshall]

> Can we create or ask users to create new Gmail accounts for LimeBits?

We could suggest that to users as an option.  We probably couldn't establish new Gmail accounts for them, though, without lots of work plus arrangements with Google.

> add your own Javascript functions to the ShareThis widget via the onclick method

Sounds interesting -- would need to hear from more people about feasibility.

> Bit is a generic umbrella term that might need some clarification

"Bit" is defined in our white paper.  It's intended as a generic umbrella term.  We don't have "site templates" per se -- just working sites and apps which are copyable and customizable.  Subcategories are possible, but I'd still want Bits to be a generic term for everything that meets the definition.

Thanks,
--J

Nischay Kumar wrote:

Jonathan A. Marshall wrote:

A "client service" like Google's is one way to wrap existing email services into a LimeBits page.  I don't think we'd need permission from the email providers -- but we would definitely check if we wanted to do this.  Instead, we'd need to persuade senders to entrust us with their email login credentials.  We'd need to deserve that trust -- proper security, etc.
There are other reasons to have CardDAV, CalDAV, etc.
ShareThis looks interesting.  How would you propose that we use it in PartySites?
Thanks,
--J

Nischay Kumar wrote:

Jonathan A. Marshall wrote:

Nischay,
I think it is worth thinking about ways to wrap existing email services into a LimeBits page -- could be easy and quick.
Thanks,
--J

Nischay Kumar wrote:

   Spent most of the day on wedding forums and websites looking up features that users really like to have and how we can market to this audience. The coolest find of the day had to be the ShareThis widget, which is seen on most sites now. It allows you to send, post or share a URL or any embeddable multimedia content via some options in the widget. It allows you to send an email too through their iFrame....  This is more about viral marketing for any of our user's sites and whether it be promoters or technology bloggers, this is a 3rd party service that could be really handy. More details on the widget and integration through their JavaScript API are up on the partysite.wiki under nkumar.limebits.com. (only read the stuff on in bold, the other stuff is more for me to keep tabs on what we can do right now to offer our clients, but you can read it if you want to.)

Yes I remember you sent out a link for the new service that Gmail provides, which would provide more powerful uses. To avoid any legal issues, we would probably have to seek approval from these companies though right?
ShareThis is probably something site developers can do on their own since it's so simple to install the widget onto a site. This probably eliminates the need for CardDAV and GroupsDAV that Tim mentioned.

Can we create or ask users to create new Gmail accounts for LimeBits? I am not sure at this point how I would feel giving my Gmail info to a third party service. Personally I feel ok with giving my Facebook and Twitter info, but my personal email has a lot of things I don't want to some company to have easy access too (besides of course Google...). Maybe we should look into OpenID or better yeat RPX--https://rpxnow.com/.

Umm so if you had a chance to look at the partysite.wiki I mentioned an idea there. You can add your own Javascript functions to the ShareThis widget via the onclick method. So lets say we have a sharethis widget just for party planners & promoters (admins of the site) who can only see that button and use the sharing tools. We would have to use some sort of authentication method via Javascript that ask the user to enter their LimeBits username and password or automat this process it if they are already logged into LimeBits (similar to OpenID scenario). Then we would have public share this buttons which anyone can sue to share a site, which is probably a feature a lot of people would want on their blogs, scrapbooks, etc. Perhaps we can make these buttons into Bits, so people can just get the source code and past it into their site.

On a similar note, I think the term Bit is a generic umbrella term that might need some clarification. Are we calling everything we and our community create "Bits". I feel like there will be both sites created, but also apps, widgets, and plug-ins.Calling all of them Bits might make it hard for users to understand exactly what is available on LimeBits. Maybe larger files like site templates should be Bytes and apps (games, blogs, galleries), widgets, plug-ins, things people incorporate into Bits. (Don't hold me on the names Bytes and Bits, I just chose them for the sake of differentiation.) Since we are trying to work on user experience now, I think organizing our Bits is crucial. We already have a large amount of Bits and they'll obviously grow, do you think just the tagging feature alone is enough to sort through all these Bits?