Notices tagged with twitterbridge, page 2
-
@javiercar No. First of all it would require me to become a customer with Twitter (to get "API keys") - that simply won't happen. Secondly, if I enabled #TwitterBridge and Twitter - as they do often with third party API clients - disable my API keys, then a part of this service which people have come to rely upon gets removed with no way to reinstate it. Please ask Twitter to imple…
-
@javiercar No. First of all it would require me to become a customer with Twitter (to get "API keys") - that simply won't happen. Secondly, if I enabled #TwitterBridge and Twitter - as they do often with third party API clients - disable my API keys, then a part of this service which people have come to rely upon gets removed with no way to reinstate it. Please ask Twitter to imple…
-
@chimo LOG_DEBUG is probably more correct (that's the only case you'd want to be informed of a non-action).
And yes, I'll accept anything on #TwitterBridge and then laugh at everyone if it breaks for people. #TwitterBridgeMyAssToYourFace!
-
@isamafifi Yes, I'm still here in the !Fediverse. My posts you see in #Twitter come from !StatusNet through the #Twitterbridge
-
Bah, who needs the #TwitterBridge? :P
-
I wonder if re-installing the #Twitterbridge with code from !GNUsocial will work on my !StatusNet 1.1.1 system…
-
Actually, it was because I looked at Twitter, and some messages that should have been transferred weren't. The #Twitterbridge hasn't been receiving messages for over a year, but I would really like it to continue to send messages.
-
The #Twitterbridge was fixed for API 1.1 by (I think) @jbfavre, which should have been merged into the main !GNUsocial branch long ago. https://gitorious.org/search?q=twitterbridge
-
@mmn asks: Has anyone else tested this yet? I can't test #TwitterBridge in practice. https://gitorious.org/social/mainline/commit/376e63db77cf8fa5f476b85dcd138da88cec7b1d#comment_108110 #gnusocial
-
!tzag, !fediverse. While !coffee making itself, it's time to make an announce for !loadaverage users: #twitterbridge will be disabled on 12th July http://url.pztrn.name/1hs
-
#GNUsocial feature: allowing #twitterbridge only for certain users, e.g. on a public instance useful: enable TB only for non-spam accounts !snbug
-
(/me goes back to check other instances for my deleted messages) Hmm… You're right… Since deletions *do* work across the #Twitterbridge I figured they would work across federated instances too. !TIL
-
(/me goes back to check other instances for my deleted messages) Hmm… You're right… Since deletions *do* work across the #Twitterbridge I figured they would work across federated instances too. !TIL
-
Deleting a notice propagates through the !Fediverse. Deletions even cross the #Twitterbridge, erasing your Tweets so they can't be read by millions.
-
I did apply @jbfavre's patches for https on #Twitterbridge a few weeks ago, but no two-way joy.
-
The #Twitterbridge on sn.jonkman.ca used to be two-way. Then it mysteriously wasn't, and stayed that way. I changed no settings. I tried to look through the SN logs once, but they grew at a rate of 20 Kbytes/sec, well above my reading speed.
-
There's a #Twitterbridge plugin, which definitely pushes notices from !StatusNet or !GNUsocial to Twitter. But getting messages from Twitter to SN seems to be hit'n'miss, which I haven't figured out yet.
-
the #twitterbridge can also work 2-way, ask Bob why it's 1-way on your instance only
-
Playing with #TwitterBridge. I think the use of is_twitter_notice() inside is_twitter_bound() is a !SNBug.
-
Working on improvements to StatusNet's #TwitterBridge. Apparently @mmn@freesocial.org already implemented much of what I want. Need to actually sit down and pick his #patches apart....