Mit „twitterbridge“ getaggte Nachrichten
-
♻ Laurel L. Russwurm @laurelrusswurm: That's why I contribute so little to @Wikipedia. It's not the work, it's that I've better things to do than stave off deletionist cliques. ¶ via #Twitter, because I haven't fixed the #Twitterbridge o…
-
@andersbateva@quitter.se But to actually answer your question, no, I don't know of any #GNUsocial instance with a (working) 2-way #Twitterbridge.
-
My instance sn.jonkman.ca is supposed to have a two-way #Twitterbridge, but inbound (T->SN) mysteriously stopped working about a year after I set it up. The other instance on the same shared server, s.russwurm.org lost comms in both directions…
-
@silverwizard I don't worry about reshares to !Twitter any more than I worry about any other content that goes over the #Twitterbridge. My Twitter followers are already getting only a half side of conversations I have in the Fediverse, and nam…
-
@thomask You may be right. My #Twitter follower and I are going out for a beer, the better to understand the issue. I may just shut down my #Twitterbridge completely (until @Maiyannah fixes it, of course :)
-
I was under the impression that development on the #Twitterbridge was pretty much abandoned. First Twitter shut down their API 1.0, then there was compulsory OAuth, and it's still a continuously moving target. No-one wants to chase forever wit…
-
Yet there are plenty of !GNUsocial users who have the same userID in #Twitter. Perhaps the #Twitterbridge can keep a list of followed accounts on Twitter, and supply the @ nametag only for those.
-
That is, check with @n2admin@n2.federati.net to see if https://n2.federati.net is running the #Twitterbridge plugin. If it is, on the !GNUsocial Settings page there will be a Twitter item where you can set the connection between your !GS and your !Twitter account.
-
Sending from !GNUsocial to !Twitter requires that your !GS instance is running the #Twitterbridge plugin. Check with @neadmin. The Twitterbridge is not well supported, since Twitter keeps changing its API. Inbound Twitterbridge messages tend t…
-
@isamafifi Yes, I'm still here in the !Fediverse. My posts you see in #Twitter come from !StatusNet through the #Twitterbridge
-
!loadaverage news: #twitterbridge is now one-way https://sn.pztrn.name/url/7352
-
Okay, voting is over. !loadaverage #twitterbridge will be reconfigured for sending notices only.
-
@mararm no, this isn't a case of #twitterbridge problem :)
-
!loadaverage news: Voting about #twitterbridge https://sn.pztrn.name/url/7336
-
Okay, #twitterbridge spammed all over the queue_item table. So !loadaverage is kinda lagging in federation. Sorry, guys :( I think it will be fair if I will ask you: should we disable twitterbridge to preserve normal #loadaverage functioning, or we can deal with some lags?
-
@knuthollund No, I will stay on 24 threads for a while. If this will work - #twitterbridge will not be eliminated, but we should enforce some rate limiting on it, I think.
-
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
-
Okay, #twitterbridge again created unparsable queue item. Crap. Sorry, !loadaverage users, this wasn't made on purpose :(