Just a note: I'll deploy the new UI today on the the second stax instance.
On Mon, Mar 8, 2010 at 2:06 AM, Ethan Jewett <[email protected]> wrote: > Hi Sig, > > Yes, you've got it about right. You are using the pool message API, so > you're getting all messages in a pool. I think you're actually only > posting messages into pools, so those messages shouldn't be showing up > in the public timeline at all. > > Ethan > > On Sunday, March 7, 2010, Sig Rinde <[email protected]> wrote: >> When we filter by tag locally we request all messages with that tag >> from the public timeline with the poolid in question for that >> particular Thingamy instance. >> >> But then again I might not get quite what you mean by "public timeline"... >> >> S >> >> >> On 7 March 2010 22:30, Sig Rinde <[email protected]> wrote: >>> Being the geek-in-training I think I might have misunderstood Anne... >>> >>> Not sure where we fetch from as we're using pools - and obviously when >>> we filter locally we use all historical messages from the pool. So >>> those would be nice to have. >>> >>> Ethan, I'm sure you know after the search you enabled last for us! >>> >>> (My programmer is at the pub so I'm only the half-wit messenger :)) >>> >>> Sig >>> >>> On 7 March 2010 21:46, Anne Kathrine Petterøe <[email protected]> wrote: >>>> As I just found out, there is another very important reason to keep the >>>> public timeline and that is thingamy. >>>> They are using it. >>>> >>>> So let's keep it - I also agree with what Darren is saying. A public >>>> timeline for discovery might not be so bad. >>>> We have decided to make the public timeline a separate page on the new UI >>>> anyway, so it won't be in the way for those of us who aren't using it. >>>> >>>> - anne >>>> >>>> >>>> >>>> On 7. mars 2010, at 21.31, Darren Hague wrote: >>>> >>>>> The public timeline can be useful in the early days of a microblogging >>>>> service, as I have recently discovered with the introduction of SAPTalk >>>>> at SAP. While there are only a few users of a service and the social >>>>> graph is very sparse, the public timeline is the easiest way to find & >>>>> follow new people. >>>>> >>>>> Once the service is established, the public timeline is much less useful >>>>> - but it's still quite a good way for complete newbies to get a feel for >>>>> what's going on. Without the public timeline, new users have a chicken & >>>>> egg problem to deal with - they access the service, see very few (if >>>>> any) messages, and wonder what the big deal is with all this >>>>> microblogging nonsense and don't come back for 6 months. >>>>> >>>>> Just my 2p, >>>>> Darren >>>>> >>>>> On Sun, 2010-03-07 at 18:51 +0200, Vassil Dichev wrote: >>>>>>> IMO we don't need it. >>>>>>> We have search and streams. >>>>>>> >>>>>>> On 7. mars 2010, at 17.25, Richard Hirsch wrote: >>>>>>> >>>>>>>> Do we even need the public timeline? Or should it just be accessible >>>>>>>> via Streams Page. >>>>>> >>>>>> I've said before that I don't see much utility in the public timeline, >>>>>> and it also poses performance problems, as it's difficult to cache and >>>>>> doesn't scale well. >>>>> >>>>> >>>> >>>> >>> >> >
