GNOME Bugzilla – Bug 680182
Should support identi.ca
Last modified: 2012-09-24 20:49:38 UTC
When I click the "+" icon in the Online Accounts window, there are options for Windows Live, Facebook, Twitter, and Google. We should support free services as well; identi.ca could be a good start. What's involved in adding support for a service?
(Disclaimer: I no longer maintain g-o-a but I'm the original author) This mail https://mail.gnome.org/archives/desktop-devel-list/2011-May/msg00267.html has some thoughts that may or may not still be relevant. The important part is this Btw, already at this point, it should be clear why all this needs to happen in the well-defined sandbox that is GNOME: we can't go add support for providers or kinds of services willy-nilly - it all has to be coordinated in a way so it all works. For chat, it means coordinating GOA and Telepathy. For other kinds of services (like Mail or Calendar), it may be harder - especially if it involves coordinating the effort with multiple apps (such as both Evolution and Thunderbird) or multiple libraries. So, basically, the thinking was this: if you want to add support for a new provider (like Twitter) in g-o-a you need to make sure that the apps in GNOME actually uses it and something sensible happens.
I agree, we need to have an app first. What is the 'twitter/identi.ca' app ? We don't have one currently.
(In reply to comment #2) > I agree, we need to have an app first. What is the 'twitter/identi.ca' app ? We > don't have one currently. I don't think it's a given we even *want* one. I mean, how exactly would micro-blogging work in GNOME? Last thing I want to see is the UI being littered with a bunch of "tweet this!" buttons or, hell, someone integrating into the window manager decorations so you tweet from any window while you tweet. Needs designer input on the level of https://live.gnome.org/Design/Apps
Thanks for the big clarification, David - this certainly puts things into perspective. The way I approached this - launched the online accounts thingy, saw "Twitter" and decided to configure it because why not, then I filed this bug, and *then* I started looking for where that Twitter feature may be used. Good to know that it's not actually used; it's not that the functionality is so hidden that you can't find it :) So are you saying that openSUSE somehow did --enable-twitter on g-o-a? I can certainly file a bug there. In any case, we should clearly mention which options are for testing only and which ones are for real features. I'll close this bug.
(In reply to comment #4) > The way I approached this - launched the online accounts thingy, saw "Twitter" > and decided to configure it because why not, then I filed this bug, and *then* > I started looking for where that Twitter feature may be used. Good to know > that it's not actually used; it's not that the functionality is so hidden that > you can't find it :) Yeah, I can see that's confusing - I would probably have reacted the same way :-) > So are you saying that openSUSE somehow did --enable-twitter on g-o-a? I can > certainly file a bug there. In any case, we should clearly mention which > options are for testing only and which ones are for real features. That's a good idea - Debarshi, can we add something to the configure output about the fact that downstreams shouldn't enable providers just because they can? Thanks.
>> So are you saying that openSUSE somehow did --enable-twitter on g-o-a? I can >> certainly file a bug there. In any case, we should clearly mention which >> options are for testing only and which ones are for real features. Distributors are not expected to enable anything apart from the ones that are turned on by default. > That's a good idea - Debarshi, can we add something to the configure output > about the fact that downstreams shouldn't enable providers just because they > can? Thanks. I don't what is the best approach here. The Twitter and Yahoo providers will most likely crash because we added some virtual methods to OAuthProvider and OAuth2Provider to polish the UI. eg., we added one that checks if the user has been able to authenticate into their accounts so that we can remove the Cancel button, there is one that traverses the DOM to figure out if the user clicked the Deny Access button, and so on. Since we have this vague legal situation with how to distribute the keys and so on, I never really bothered to hook in the Twitter and Yahoo specific bits by implementing the virtual methods for them. Maybe we should just remove the Twitter and Yahoo! support? We can always add them back when the situation changes.
(In reply to comment #6) > Maybe we should just remove the Twitter and Yahoo! support? We can always add > them back when the situation changes. Yeah, that sounds like a much better idea.
*** Bug 684588 has been marked as a duplicate of this bug. ***