-
Website
http://www.emadibrahim.com -
Original page
http://www.emadibrahim.com/2008/04/11/yonkly-open-source-twitter/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
danatkinson
1 comment · 1 points
-
Korayem
3 comments · 1 points
-
dukon21
1 comment · 1 points
-
Mladen Mihajlovic
1 comment · 1 points
-
Chad Myers
3 comments · 1 points
-
-
Popular Threads
-
Select Random Records Using Nhibernate
6 days ago · 4 comments
-
Select Random Records Using Nhibernate
Assembla seems to have the best mix I've seen, so far. You might check them out too.
@haacked, @mike, @sam I will let you know when I post the source code online. I will announce on this blog
@chris, working on it :) keep throwing ideas at me
@sam: it took me about one week - but it is still missing a lot of features... so, be on the lookout for a new release next week
Thanks
I'd love to help, but me thinks I need to get comfortable with asp mvc first....
Wicked stuff.
Was unable to see the comment reply in Opera, would not open ??
Food for thought, Can this be used as a decentralized version of Twitter? This is what is being searched for and an open source solution is the only feasible option from my perspective.
Not what everyones thoughts are on how this can be done, there has been wider discussion on techcrunch regarding this:
http://www.techcrunch.com/2008/05/05/twitter-ca...
comments on the timeline can be shared on the host of the individual servers that upload the script and results of the public timeline can be displayed on your website i.e. mysite.com/yonkly/public-timeline, it would be a case of publising the public timeline link in our sites/blogs, etc. Theres no need for a central public timeline it can be viewed on any of these sites that hosts it by having the script uploaded, Like RSS feeds.
We could look at minimising the amount of space that each site takes up to host public timeline and a method to distribute the timeline equally. The more that sign up to upload the script to the server the simpler it gets to distribute.
Just thinking out load
Someone made a similar suggestion about creating a distributed twitter-like platform. But that is one tough problem... I haven't had time to really think about it but just dealing with data on multiple servers and authentication alone would cause you a headache...
So let's say we have server a and server b. Each has its own version of the database and a different set of users. How would you deal with user a on server wanting to friend user b on server b? Sure you can server a talk to server b but then what if we have 20 servers?
Or another scenario, user a leaves a message while on server a, how will this message show on the other servers? Having every server query every server on every request would just not work...
Eventually one server/provider would be the most popular and you will end up with the same problem of a centralized twitter system... It's kind of similar to OpenID, sure there are several providers, but in a few months/years, 80% of the users will be with 20% of the providers - probably one of the bigger players (yahoo or aol).
How would you handle upgrading the servers and multiple versions of the protocol floating around?
A more important question, why would anyone bother hosting one on there servers? I mean, what is the financial benefit to them?
Obviously, I haven't thought this through but it is not a simple problem...
I would love to hear what others think. Any ideas?
Simply put you can not have a version of the that collects users for an individual server and attempt any kind of resolve, it will not be practical. You could offer a version that is open source that a community driven site would want specifically for its own niche to build its own list of users, for sure. But there would have to a be custom version that maybe works using OpenID only, each user having ownership to their ID (character extension could be given to cater for the length of the OpenID, i.e. 150 characters and not 140 to make responses such as @claimID/azzam ....). The custom scripts would communicate with each server.
The question about each server talking with each other to display the messages realtime you got me there!
file, compile the project, create the database and deploy.
-Emad
haven't upgraded the code to us epreview 5 yet but the beta is coming out
soon, so I might as well wait a couple of weeks.
that would post a message to web page as an HTTP POST that I can then take
and insert into the database. The only problem is cost. These services are
not free and every message costs money. There are some out there that are
ad-supported but I don't want to go that route for now.
problems with compilation, try posting the question to the codeplex
discussion at http://www.codeplex.com/yonkly/Thread/List.aspx
Thanks.
off/on images from the admin control panel, if you are the network admin.
If you are referring to the open source version then it is not an option but
can easily be added - after all it is open source :)
No view state. Easier to unit test. better seperation between
presentation and code.
I haven't tried converting to a webform but my guess is that it won't be
easy. It will probably be easier for you to learn MVC than try to convert
it.
thanks for your input
does any know how to fix this
http://groups.google.com/group/yonkly-os
Thanks.
thanks for sharing