Disqus - Latest Comments for bear

Re: getting the exit code from a batch file that is run from a python program

bear — Wed, 11 Nov 2009 13:28:45 -0000

I suspect it's how NANT is calling the scripts from within it's code that requires the explicit use of the EXIT keyword - a batch-to-batch invocation probably is handled in a subtly different manner (which is what both of us had to find and solve ;)

Re: Google Wave FedOne component with Prosody XMPP server

bear — Mon, 02 Nov 2009 11:40:27 -0000

It is a complete Wave environment for sure, you can use the command line test client and view all of the Wave goodness flowing back and forth. The only thing you don't get is the fancy UI client.

Yep, it is completely federated - it's already making attempts to reach out and contact other servers when you add remote JID's - Google just has it turned off on the public facing servers so it fails.

Re: FriendFeed and Scoble and the crowd-as-community problem

bear — Mon, 02 Nov 2009 03:51:43 -0000

*nod* - and that was the difference I was trying to draw out of your post, so i'm glad to see you reinforce it here.

The fun part is watching the methods and styles of curation and list building work their way thru the older and newer applications and seeing how folks are responding to the limitations.

Re: FriendFeed and Scoble and the crowd-as-community problem

bear — Mon, 02 Nov 2009 03:31:24 -0000

I completely understand your point about the amount of time you would have to spend to massage the lists on both services - it's something that keeps me from truly jumping in with both feet to most of these sites.

I have been waiting to make any "public" comments on the debate going on until just now - but i'm glad at the core you do recognize that they are tools to be used properly. And thanks for the reason-dump, it helped draw me out of my micro-blogging shell and post something more substantial.

Re: Google Wave FedOne server certificate key fun (not!)

bear — Sun, 01 Nov 2009 03:52:37 -0000

I had to change/do two things: 1) export the cert as DER type instead of PEM type and also convert the key from the PEM type I had in /etc/ssl to a DER type and store both the key and the cert local to the wave component directory.

I'll edit the post to show this more clearly

Re: Random thoughts about including Google Wave in your data flow

bear — Fri, 02 Oct 2009 14:55:03 -0000

Very interactive indeed. And that's a great example of how a bot/extension can be both a sink and a source, that bot probably treats all incoming change requests as discrete/atomic updates - i'm more worried about when a bot is present in 50 wave documents and it's getting 2/3 updates per document and *some* of them need to be distributed to something other than the source doc.

Re: Loose.ly coupled 140-char message network (Scripting News)

bear — Thu, 13 Aug 2009 21:55:48 -0000

Unless they have changed in the 0.8 tree, laconi.ca distributes inbound items to different working queues in a database table and then have listening processes to consume from those queues. Because now there are different queues, the database load can be spread across servers but then you run into more of the common database replication issues.

Re: Loose.ly coupled 140-char message network (Scripting News)

bear — Thu, 13 Aug 2009 21:53:34 -0000

Twitter doesn't suffer from downtime because of the size of the data, but rather from the amount of work it has to do to distribute the item once received and get it queued for delivery. If it were a size scaling issue then increasing the number of sources of the data would work as any client would have that many more places to go.

Rather it's a distribution/routing issue and "classic" P2P would not work IMO. The rules for routing of any given item would need to be distributed to all of the P2P cloud and when anyone of them receive that item, see if they are responsible and handle it. I see problems with out the partitioning would be done to try and balance duplicating data sent over reducing decisions - a fun problem for sure :)

I'm thinking P2P could enter the scene if you applied that tech to sync up the working queue of anyone persons posts - say to distribute yours or scobles working queue across the cloud so then it's efficiently duplicated to allow for parallel work.

Re: XMPP PubSub + XSLT

bear — Sun, 02 Aug 2009 00:34:35 -0000

Both Atom and RSS 2.0 are xml, so you can use this script as a start for RSS 2.0 - but the structure and content would be different. See http://www.rssboard.org/rss-specification for what goes into RSS 2.0 content.

Re: Exploring the 2010 Web

bear — Sat, 16 May 2009 16:08:19 -0000

It sounds like you are rearchitecting your blog to be the static presentation of certain realtime events/items that you generate during the course of your day. Instead of the blog being the first place you would visit to make posts or otherwise "generate content" it can now be the place where you summarize the day using long-form content.

Re: Episode 3 - Bear

bear — Tue, 20 Jan 2009 09:57:56 -0000

Thanks for the chance to be interviewd - I had a great time!

Listening I realized I never really answered why I have the nickname "bear" ...

basically my neices and nephews all call me Uncle Bear because of the beard and the fact that I give a lot of bear-hugs

So it stuck :)

Re: Twitter in 140 characters (Scripting News)

bear — Sun, 04 Jan 2009 19:27:19 -0000

Twitter is the public space of my present and future workplace.

Re: XMPP PubSub + XSLT

bear — Sun, 04 Jan 2009 19:20:25 -0000

That is the exact type of problem we are trying to avoid by offering a "true" body option with our PubSub events - to allow people who are consuming them who are using clients which ignore non-chat messages to having something to view.

Like all things feature-rich, just have to get all our pieces in place and pointing at the same place :)

thanks!

Re: Seesmic's Video Firehose Now Available via Gnip

bear — Tue, 30 Dec 2008 01:33:46 -0000

Rob,

The "firehose" is the same information that appears in the Atom/RSS feeds, but instead of you polling it, Seesmic's PubSub server will push it to you via XMPP. The payload of the message we create uses the same Atom item as the feeds and soon we will be offering other "flavours".

So what is being done by 3rd party devs like Zac, is to wire together the receiving of the Seesmic events via XMPP and a method of inserting them into Facebook.

You can receive the events either thru a service like Gnip or directly from us.

Re: XMPP PubSub aka “death by a thousand cuts”

bear — Sun, 21 Dec 2008 14:55:51 -0000

Anyone can subscribe to it by sending me an email with the JID you want to use. We are doing the subscriptions manually just to allow me to keep track of a contact email in case something changes or I need to "break" the system.

The pushing of an item to another PubSub node is called chaining and I know they (the XMPP spec folks) are working on something to cover it - but yes, technically any valid JID can be used as the target and PubSub nodes are valid JID's

We briefly thought of using Content-Based subscriptions to allow the subscriber to control various details like format (Atom, RSS, Json) and also language (all, English, French) but quickly put that back into the "future" column when we discovered that it's not well implemented on either the Client or Server side :( and the last thing we want to do is bolt on a partially implemented feature to PubSub until we have more time to evaluate how.

Re: Seesmic and XMPP Pubsub

bear — Mon, 03 Nov 2008 21:21:21 -0000

Julien,

The biggest hurdle was finding out that different folks implement specs differently and that there wasn't a single suite of tests to compare server performance with. So we spent quite a bit of time working with the Tigase guys in getting them to probably 98% complient with the spec.

The other issue is a complete lack of docs or examples of what goes into maintaining all but the most simple of PubSub structures. Not to say the information isn't out there, it's just wasn't helpful to our needs - most folks only use the PEP part of PubSub.

Re: Is This Stupid?: Seesmic Video Gets Verklempt, RWW Has Nothing to Read or Write

bear — Fri, 25 Jul 2008 10:58:51 -0000

I am unable to see that behaviour on the current RWW site. Do you have a time when you captured the screenshot so I can see if it was something on our side and correct any issues?

thanks,
bear
seesmic dev

Re: python giveth and python taketh away

bear — Tue, 20 May 2008 19:20:42 -0000

Michael,

Glad I saved you some time :)

Re: getting the exit code from a batch file that is run from a python program

bear — Tue, 20 May 2008 05:23:03 -0000

Glad to help! With the amount of time our team took in figuring this one out there was no way I wasn't going to share it :)

Re: scaling questions and issues

bear — Sun, 06 Apr 2008 00:28:35 -0000

We are fighting mutlipe deadlines, RabbitMQ is still in use on the test box but due to reasons that are not RabbitMQ's fault at all we are still stuck with ActiveMQ :(

I'll have to take a look at the updated client list - that may give me some more info to pass to the devs to speed up the replacement.

Re: XMPP as the basis for interop in TwitterLand? (Scripting News)

bear — Mon, 21 Jan 2008 13:25:49 -0000

We are also doing XMPP notifications at Seesmic. PubSub is being worked on now.