"Either way, for this to be considered for merging it needs to be consistent between all services (that apply). So, that means the required changes need to happen for identica/laconica/facebook/etc."
It will happen for identi.ca and laconi.ca, but not for facebook (as their API doesn't support it)
However, I wouldn't necessarily hold out the merge waiting for identi.ca & lacon.ica support as we're not currently targeting a particular milestone. Once we have the focus of a milestone release date then we can consider whether it would need to be held out waiting for the identi.ca/laconi.ca support. Until then, it makes sense (to me) that we merge now while the impact is lower, and I will develop the accompanying identi.ca/laconi.ca support whilst simultaneously getting decent feedback from the twitter community on whether it is a good feature / worthwhile / performant etc.
"Either way, for this to be considered for merging it needs to be consistent between all services (that apply). So, that means the required changes need to happen for identica/ laconica/ facebook/ etc."
It will happen for identi.ca and laconi.ca, but not for facebook (as their API doesn't support it)
However, I wouldn't necessarily hold out the merge waiting for identi.ca & lacon.ica support as we're not currently targeting a particular milestone. Once we have the focus of a milestone release date then we can consider whether it would need to be held out waiting for the identi.ca/laconi.ca support. Until then, it makes sense (to me) that we merge now while the impact is lower, and I will develop the accompanying identi.ca/laconi.ca support whilst simultaneously getting decent feedback from the twitter community on whether it is a good feature / worthwhile / performant etc.
I will wait to hear what Ryan thinks though :)