[Developers] Developers Digest, Vol 26, Issue 2

[Robert Cook]

James, this is a cool idea.  A couple of comments:

- If there is only one definitive account per entity (my guess is that  
for celebrities that should be true, but there might be idiosyncrasies  
to Twitter that I don't understand), then we might consider using an  
enumerated property that writes into a namespace.  This is pretty easy  
to set up.

- Is it possible that we would want to capture entities other than  
celebrities, or more generally, people?  Companies?  Organizations?

If so, then we might want to have the property off some more generic  
type like "Twitter user".

R

On Apr 3, 2009, at 3:01 PM, James Alexander Levy wrote:

> I'm building an app using some Twitter data, and I'd love to build  
> it as an Acre app considering all the new goodies that are being  
> added to the platform.
>
> For my purposes, it would be fine to add a Twitter account property  
> to the Celebrities base, but for functionality matching that of http://wefollow.com/ 
> , it would likely be better to setup a new Base with a bot to keep  
> all of the follower accounts updated.
>
> I won't be able to start hacking this until I return from a trip  
> later this month, but I'd love to hear suggestions about modeling  
> this data, and let me know if you're interested in joining the  
> Twitter->FB code sprint.
>
>
> thanks for your attention
> James Levy
> http://www.jamtoday.org
> http://www.twitter.com/jamtoday
>
> _______________________________________________
> Developers mailing list
> Developers at freebase.com
> http://lists.freebase.com/mailman/listinfo/developers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freebase.com/pipermail/developers/attachments/20090403/29af7fd0/attachment.htm