Syyncc is fairly broken at the moment
Emlyn
A couple of things have compromised Syyncc in the last day or so:
- Buzz api seems to have been turned off.
- Google+ reading has failed
We all knew the Buzz issue was coming, ah buzz. But the Google+ one is
my fault, because Syyncc's been using the same dodgy technique since I
got it going; namely, it pulls data out of profile pages, rather than
using the API. I'm surprised it's worked as well as it has, in fact.
So I'll move over to using the API as soon as I can. Meanwhile,
there's an interruption in service, my apologies.
As to when Syyncc will be able to write back to G+ ? That still
requires a write API from Google, which doesn't look as though it's
coming any time soon. Annoying, but not much to be done there.
--
Emlyn
http://my.syyn.cc - Synchonise Google+, Facebook, WordPress and Google
Buzz posts,
comments and all.
http://point7.wordpress.com - My blog
Find me on Facebook and Buzz
Nate Taylor
Thanks for the heads up. Have you by chance looked at how, say YouTube for instance, they share/post to g+. You know. Those lil +1 bottoms that when pressed allow you to share. When I get off work ill see what reverse engineering can be done and get back to you... I know it can be done. I did a post when g+ first launched but can't remember the magic foo
Emlyn
reverse engineering that kind of thing.
Unfortunately, it posts in the security context of the current logged
in user in the browser. So there's no authentication step, I think you
just pass a magic token in your post.
That's not going to work for Syyncc, because it doesn't do its work in
the context of a logged in user. Unless there's a way to fake up a
browser user context (ie: the google end-user login process) in python
code on AppEngine, I think we're out of luck for the time being. What
I really need is an oath api.
That said, if you figure out a way that'll work in back-end code, I'm
up for it.
John Blossom - Shore Communications Inc.
Best Regards,
John Blossom
President
Shore Communications Inc.
where content, technology and people meet. (Salesmark of Shore Communications Inc.)
web: shore.com
blog: contentblogger.com
book: contentnation.com
email: jblo...@shore.com
phone: 203.293.8511
fax: 203.663.8259
facebook: John Blossom
skype: jblossom
twitter: jblossom
google+: John Blossom
Nate Taylor
I fully see the incompatability of it. Ignore the possible misspelling there : )
Im still working. Will let you know for sure if I find any thing useful.
Emlyn
<jblo...@shore.com> wrote:
> Will the change in Facebook's policy towards external postings affect the
> feed either?
I know that affects news feeds being pumped into notes, but I read it
as a very specific change. As far as I know the core functionality of
writing to fb remains unchanged.
Do you have any scarier references that I should be looking at?