Opened at 2010-10-23T22:16:04Z
Closed at 2014-07-07T13:21:15Z
#704 closed enhancement (wontfix)
Support for Facebook news feed (like twitter)
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | pony | Milestone: | |
Component: | BitlBee | Version: | 3.0 |
Keywords: | facebook status news feed | Cc: | |
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: | Fedora 13 |
Description
Facebook has a status or news feed that works like twitter or identi.ca. Would be great to be able to use that with BitlBee in the same way as twitter and identi.ca.
Attachments (0)
Change History (4)
comment:1 Changed at 2010-11-26T23:53:45Z by
comment:2 Changed at 2011-07-05T21:49:37Z by
I second this--I was just about to add another ticket about this, and thought I should check for an existing one first. I have no problem with going through ping.fm, provided that I can post to different accounts individually (facebook allows longer posts than twitter does). It would be nice to be able to do it without logging into a 3rd party service to do it, but if that's what it takes, its fine with me.
comment:3 Changed at 2014-02-04T10:07:57Z by
Priority: | wishlist → pony |
---|---|
Summary: | Support for Facebook status → Support for Facebook news feed (like twitter) |
comment:4 Changed at 2014-07-07T13:21:15Z by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Closing all protocol request tickets.
For most of the requested protocols, it's likely we won't have time and/or interest to implement them, and some tickets have stayed open here for years when they have libpurple implementations, or even as third party plugins. Implementing protocols in the core is far from a priority nowadays, although I hope we can make it easier to write third party plugins. As always, anyone who is interested in implementing bitlbee plugins for these can do so, and we're willing to help (join irc!)
I don't see what an IM client has to do with microblogging. If you ask me, bitlbee shouldn't support twitter either.
Of course there's always twitter<->facebook sync. Maybe bitlbee -> twitter -> facebook ? OR what I do: bitlbee -> tweet.im(via gtalk) -> twitter -> facebook ?
"IF" bitlbee devs want to support microblogging, I recommend they simply support ping.fm and that will cover just about everything else.