Conversation
Notices
-
At last night's @KWVoIP meeting I was told my #Twitter feed is a disjoint series of half-conversations. Tried to explain that's because #Twitter doesn't federate with the !Fediverse, offered him a spot on sn.jonkman.ca. Got told that it wasn't *his* problem, so he shouldn't have to do extra work to see my feed. Didn't help when I pointed out that he was the one complaining, I'm perfectly satisfied being a disjoint half-wit on #Twitter.
-
@bobjonkman Also, I believe your tweets contain links to original conversations. Since it is often difficult enough to piece together complete conversations between #Twitter's own users (esp if more than two parties and you only follow one), with one or two clicks, he can see more than T allows.
-
I was blocked by a couple of Twitter users, and one user made her account private, thanks to usename collision. I thought it was useful to push all the notices to Twitter but it didn't convince any user to join the fediverse. Instead, my Twitter stream became a pain to follow and keep track of (if I looked at it from a regular Twitter user's view point.) So I decided not to push notices from here to there.
-
@lohang @bobjonkman Username collision seems to be a problem with that plugin we should probably look at addressing. I'm going to be looking at implementing it here soon so I'll see what I can manage when I do.
-
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 without catching up. @jbfavre@status.jbfavre.org did a lot of maintenance, but it seems he's not even running a GNUsocial instance any longer
-
@bobjonkman and then some day they'll shut it down due to API rule breaking.
-
-
-
-
