tag:blogger.com,1999:blog-5430866.post8426510552784957732..comments2024-01-02T08:54:14.406-05:00Comments on Peter Bromberg's UnBlog: The Social API we really need.peterbromberghttp://www.blogger.com/profile/18173639411723574123noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-5430866.post-81957795315287790842009-08-05T12:33:08.325-05:002009-08-05T12:33:08.325-05:00This is definitly needed. I can see numerous ways ...This is definitly needed. I can see numerous ways this can be useful. For one, it would be great to see a complete search on specified search terms. For instance, if someone was talking about your toolset, you'd like to see all those comments in one place. It would be cool to also post to all types of accounts at once. It doesn't need to be a huge umbrella, but capturing search, posts, and maybe followers/friends would be a big help.Jason N. Gaylordhttps://www.blogger.com/profile/04153299653189636899noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-36374358220434942542008-05-27T17:46:00.000-05:002008-05-27T17:46:00.000-05:00@joshua,The GAE is fine as long as you feel compet...@joshua,<BR/>The GAE is fine as long as you feel competent in Python, are happy with their SQL-like query language called GQL, and don't expect to be too popular -- or you'll overrun their quota for number of requests.peterbromberghttps://www.blogger.com/profile/18173639411723574123noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-15145530913941660892008-05-27T14:50:00.000-05:002008-05-27T14:50:00.000-05:00Peter, my mind is in the cloud. After seeing Googl...Peter, my mind is in the cloud. After seeing Google App Engine, which handles the scalability issue for you, I think that it would be a lot less work to create a restful service on the GAE platform, then to worry about the servers and scalability yourself. You get to persist data in BigTable. Have you checked out GAE? Would the functionality of this API your are proposing not fit their offering?Josh Pearcehttps://www.blogger.com/profile/11984747479445512671noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-1708994246369439692008-05-27T14:29:00.000-05:002008-05-27T14:29:00.000-05:00@Steele,OpenSocial has four APIs for social softwa...@Steele,<BR/>OpenSocial has four APIs for social software applications to access data and core functions on participating social networks. It is an API that ties together "stuff" from existing social apps. What I want to see is an API that "IS" an app, with everything in ONE place and one codebase. You build *your* application based on this API.peterbromberghttps://www.blogger.com/profile/18173639411723574123noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-47753440819687808942008-05-27T13:35:00.000-05:002008-05-27T13:35:00.000-05:00This is indeed something needed. I was contemplat...This is indeed something needed. I was contemplating just making a "sub-blog" RSS feed which is limited to 140 chars that could be consumed nd redirected by all these social networks.<BR/><BR/>The mechanism is there (RSS), a more social aggregator is not, however Twitterfeed is working fairly well for me, it just doesn't hookup my other social sites.<BR/><BR/>What I want is control over my own prior posts and a place to hold interesting things other people say or point to. Digg and delicious don't cut it for me.<BR/><BR/>So what would your proposed API provide that OpenSocial API doesn't provide already?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5430866.post-18383292824723834012008-05-27T13:34:00.000-05:002008-05-27T13:34:00.000-05:00@Joshua,I'm not sure I follow the ".NET?" comment....@Joshua,<BR/>I'm not sure I follow the ".NET?" comment. You need server hosting for any platform. But server space is cheap - about $8.50 / mo for ASP.NET 2.0 with SQL Server 2005 at places like gate.com. The real issue is getting a group of developers together to build the API and stick with it. This is a project for a 5 person team over a good six months or so.peterbromberghttps://www.blogger.com/profile/18173639411723574123noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-78152050706548075842008-05-27T09:38:00.000-05:002008-05-27T09:38:00.000-05:00.NET? Wouldn't you have to buy a bunch of server s....NET? Wouldn't you have to buy a bunch of server space then? Why not use something like Google's App Engine? Does MS offer something like that for C# code?Josh Pearcehttps://www.blogger.com/profile/11984747479445512671noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-52715949287412058922008-05-24T14:01:00.000-05:002008-05-24T14:01:00.000-05:00Rick,Yes it's ambitious, and hence the post - I ha...Rick,<BR/>Yes it's ambitious, and hence the post - I have enough sense not to try to do something like this unless I see others are interested.<BR/><BR/>From a usefulness standpoint, an API like this with the infrastructure behind it (.NET I hope, not ROR!) gives developers the tools to build much richer social-space applications. Remember - I'm focusing on an API first. If somebody wants to build a front-end to go with it, that's fine. Thanks for the thoughtful comment.peterbromberghttps://www.blogger.com/profile/18173639411723574123noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-50310733385116335112008-05-24T11:25:00.000-05:002008-05-24T11:25:00.000-05:00That's a great idea Peter, but an ambitious one I ...That's a great idea Peter, but an ambitious one I think.<BR/><BR/>Two issues I see: Getting enough momentum on something like this is going to be hard because there are already so many alternatives - scattered as they may be - with momentum out there. Twitter is 'it' right now, it'll be something else next month. If there's no momentum or following that at least grabs everyone in your target group (let's say .NET developers or Web Developers) than the whole thing becomes moot quickly.<BR/><BR/>The other issue is if you throw all of this together you got a massive project on your hands. <BR/><BR/>If you look the past where tools or companies try to combine sort of umbrella APIs most of this stuff fails because generally the APIs are not compatible or there's not enough overlap between mechanisms. In the end you may end up wishy washy API that's not helping anybody.<BR/><BR/>You didn't mention it in the post, but: What do you want to do with this umbrella API? Just because you have access doesn't mean it's immediately useful for practical purposes.Rick Strahlhttps://www.blogger.com/profile/15191427292081443626noreply@blogger.comtag:blogger.com,1999:blog-5430866.post-22424954285507820002008-05-24T08:54:00.000-05:002008-05-24T08:54:00.000-05:00Oh man I would LOVE to do something like that... i...Oh man I would LOVE to do something like that... it's an awesome idea, I just don't have the time right now (baby due in 3 weeks!). I'll definitely be keeping an eye on anything that gets started though!Anonymousnoreply@blogger.com