ping.fm trigger groups not working as twitterfeed prefix
I add ping.fm group triggers to my ping.fm posts in the prefix field, but they don't seem to be working. This is kind of awkward, shotgunning tweets all over Facebook and such.
2
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company has acknowledged this problem.
-
Inappropriate?We're aware this is an issue - it's because custom triggers only work against the "default" Ping.fm post method, and we don't support the default method.
The reason we don't support it is that the Ping.fm API doesn't provide a way to know what the default method actually is, and we treat posts to status/microblog methods differently from "blog" (in terms of the length of content). -
That's true for the method and service triggers (@s @m @ff and such) but the group triggers are attached to a specific method on creation. Choosing the proper method would be up to the user when they created the feed. -
You mean the # groups? If so, I would have thought that it should just work, as long as it just requires the #groupname in front of the tweet - perhaps ping.fm could also shed some light on this, in case there's a reason this doesn't work through the API, or we need to do something special to make it work.. -
I thought it would work too. I've asked Ping (http://gsfn.us/t/92vo) we'll see what they have to say.
Loading Profile...



EMPLOYEE
