Current issues list / re-share problem
Kevin C.
Is there a current issues list?
I noticed that a re-share of the "Pencil vs Camera" post came across
very confusingly in Facebook, but I can't remember if re-share
problems was a known issue or just Google Reader shares.
I like the new interface with the buttons for turning on and off
sharing. The only disadvantage is that the debug option seems to have
disappeared, as far as I can see, so I can't tell if the problem with
the re-share is happening on your end, or if the underlying Buzz API
doesn't provide you what you need. (Of course, how many of your 53
users would actually try to read a Buzz dump in the first place...)
Thanks,
Kevin
Emlyn
> Hi,
>
> Is there a current issues list?
There isn't, and that's something I need to fix.
In fact, it's my intention to properly open source the whole thing.
The source is already all available here:
http://code.google.com/p/emlynoreganappengine/
If you feel masochistic enough to browse through the source code,
you'll notice that's it full of unrelated stuff. It's basically the
original project I used to built my somewhat skeletal website, added
to over time to do all my other appengine projects. So a definite
piece of work I have in the future is to remove syyncc from this
bucket 'o' code and give it it's own dedicated repo.
As to raising issues, using the issue list there is probably a great
start. I've never used that issue list before, so I'm not sure if
anyone other than me can add things; if you can't, let me know and
I'll give you the ability to do that if you like.
>
> I noticed that a re-share of the "Pencil vs Camera" post came across
> very confusingly in Facebook, but I can't remember if re-share
> problems was a known issue or just Google Reader shares.
Google Reader reshares are totally crap at the moment, due to API
issues. I see that Pencil vs Camera wasn't through Reader, but does
come from something external; some of the same problems apply. It's
definitely something I'll have to look into further, an ongoing point
of pain I'm afraid.
> I like the new interface with the buttons for turning on and off
> sharing. The only disadvantage is that the debug option seems to have
> disappeared, as far as I can see, so I can't tell if the problem with
> the re-share is happening on your end, or if the underlying Buzz API
> doesn't provide you what you need. (Of course, how many of your 53
> users would actually try to read a Buzz dump in the first place...)
>
Yes, I did leave out the dumps. And you saw the user count, nice :-)
I'll put the dumps back in (another issue for the list!), I'll throw
in an "advanced" link, something like that.
Also, the new interface is probably just transitional. I've been
thinking very hard about how to add Twitter. Currently the
architecture is very point-to-point; I have things called Monitors
which monitor a network for changes, and Actions which do something
with a detected changed (usually writing it to a network). A Monitor
has many Actions. There is a Facebook Monitor connected to a Buzz
Action, and a Buzz Monitor connected to a Facebook Action.
I was thinking of adding in Twitter by adding probably another
point-to-point link between Buzz and Twitter, but it's just
unsatisfactory for a lot of reasons (eg: what if you want posts to go
into Twitter and Facebook, but not Buzz?). What I really need to do is
to adopt a spoked wheel model, with a hub at the center, and all the
networks at the end of spokes. Detected changes go into the hub, then
the hub disperses them out to the other networks. I can implement this
in a fairly straightforward way as:
- Every network has a Monitor, which is linked to a Hub Action.
- There is one Hub Monitor which is linked to an Action for every network.
- The hub itself has a store of posts/comments, which functions as a buffer.
- The hub will also contain rules about which networks to move posts
between, so you could specify "Buzz posts go to Twitter, Facebook
posts go to Buzz and Twitter, Twitter posts go to Facebook". Those
rules will be straightforwardly exposed in the UI.
- This will supercede the current setup where you say eg: Buzz should
not accept posts, and so that will no longer apply.
> Thanks,
> Kevin
--
Emlyn
http://my.syyn.cc - A service for syncing buzz and facebook, posts,
comments and all.
http://www.blahblahbleh.com - A simple youtube radio that I built
http://point7.wordpress.com - My blog
Find me on Facebook and Buzz
Kevin C.
On 17 November 2010 07:53, Kevin C. <lab...@gmail.com> wrote:There isn't, and that's something I need to fix.
> Hi,
>
> Is there a current issues list?
<snipped>
As to raising issues, using the issue list there is probably a great
start. I've never used that issue list before, so I'm not sure if
anyone other than me can add things; if you can't, let me know and
I'll give you the ability to do that if you like.
Yes, I was able to submit an issue successfully. I was logged in to my Google account at the time.
--Kevin
--
If you're reading this, you're part of the mass hallucination that is Kevin the Blue.
Copyright 2010 Kevin C. <co...@kevin.lebleu.info>
"Wonderful is your gift of knowledge
the more we share, the more it grows
the more we hoard it, the more it diminishes"
- Traditional Indian hymn to Saraswati, the Goddess of Knowledge
Emlyn
> On Tue, Nov 16, 2010 at 6:28 PM, Emlyn <emlyn...@gmail.com> wrote:
>>
>> On 17 November 2010 07:53, Kevin C. <lab...@gmail.com> wrote:
>> > Hi,
>> >
>> > Is there a current issues list?
>>
>> There isn't, and that's something I need to fix.
>> <snipped>
>> As to raising issues, using the issue list there is probably a great
>> start. I've never used that issue list before, so I'm not sure if
>> anyone other than me can add things; if you can't, let me know and
>> I'll give you the ability to do that if you like.
>
> Yes, I was able to submit an issue successfully. I was logged in to my
> Google account at the time.
>
> --Kevin
Thanks Kevin, nice and clear. I'll start using that list.