Conversation
Notices
-
cripes.. I can't type (again) tonight.
Thursday, 13-Nov-08 00:59:53 UTC from identispy-
@mcnee Yes. This is why we want people to move towards event frameworks and stop polling. :)
-
@dustin: I guess event frameworks are nice but I guess keeping connections open like with XMPP could be expensive when many clients connecte
-
@alfredwesterveld s2s helps some. Bringing up a ton of connections on every event is very expensive.
-
@alfredwesterveld *more* expensive is polling constantly just in case something shows up.
-
@marjoleink I believe so.
-
@marjoleink I've been logging the public feed since some time in August: http://www.kshep.net/daily-identica-activity
-
@kshep that is great - so my 238328 woud lbe sufficient for a long time
-
@marjoleink but why have 24hr linking followed by real confusion post 24hrs in order to stay w/in an 'arbitrary' 140c limit?
-
@dustin great - that shows a max of 14760 so far (on election day, what else!)
-
@exador23 it's not about 140char limit (though that plays a role) it's more about "easy to type for humans" - not much confusion I think...
-
@exador23 you just type the number you see in the post you reply to - how far back in time would you go in an IM client to reply?
-
@marjoleink: trying a REPLY from Gwibber client
-
@rjeffries reply to what post? AFAIK no client supports is because XMPP and API don't support it - only web supports threading
-
@marjoleink I use the web. but some conversations span days. & some favorites are faved because of what it's a reply to.
-
@marjoleink: In Gwibber, a "return" arrow is highlighted when I hover over a post. when clicked it pops up a Reply window
-
@marjoleink I thought the API supported threading and that it was just a matter of clients catching up.
-
@exador23 if you use the web there's no problem - the problem to be so;lved is how to support/maintain threading in IM
-
@rjeffries fine, but if you don't indicate for us which dent you actually reply to, hwo can we know it's linked correctly? reply and quote
-
@marjoleink so does IM use the XMPP protocol or the API or is it it's own thing? sorry, just catching up on the tech.
-
@exador23 IM uses XMPP - my idea was to add the #tinyDentID to a post (as extra text) so you can type that short code when replying
-
@marjoleink: sorry i confused you. I was merely experimenting with Gwibber RELY feature. I agree, it needs to link to the post in question.
-
@exador23 not sure if the API supports in-reply-to by now - and if it does, which clients actually support it
-
@rjeffries as long as you don't quote from a dent you reply to, we can't see if it's linked correctly; quote this: 111156666
-
@rjeffries you need to both reply *and* quote to see if it works
-
@marjoleink right. but what is generating the #tinyDentID? & why can't you just have a script such that hitting reply plugs in the full ID?
-
@marjoleink: quote this: 111156666
-
@exador23 the server would be generating the #tinyDentID and mapping it to a real dentID: all actual threading on the server
-
@exador23 you can't have a script - not all XMPP clients are scriptable, and the real dentID isn't transmitted anyway - must be server-side
-
@marjoleink sounds like a complicated solution to me. but I'm not a techie. & I think twitter changed the API to support threading mos ago.
-
@rjeffries as I suspected - that links to the latest dent - not the dent you actually reply to - so no real threading there: like @REPLY
-
@exador23 not so complicated for the server, and easy for teh user: you just type the code you see in the dent
-
@exador23 yes Twitter api supports in-reply-to but has laconica *implemented* that? I thought not (yet)
-
@exador23 and XMPP clients (IM: jabber/gtalk) don't use the API at all: all you have there is the text of the dent
-
@marjoleink I was under the impression that accurate IRT wasn't enabled til twitter API change because evan wants API compatibility for devs
-
@exador23 what's "IRT"?
-
@marjoleink IRT = In Reply To
-
@exador23 whatever, threading via API is solvable once the API and clients implement it: it's *designed* already; we're designing for XMPP
-
@kshep Do you have an idea of what the rate limits on twitter search api are? Rough estimate of # of hits per hour?
-
@marjoleink right. good luck with it. my only contribution would be remember simplicity & I worry about scalability of xtra server load.
-
@briantroy, err. you do track braintroy, right? ;)
-
@briantroy I've hit them, but they don't publish what they are.
-
@tychoish well... that is a matter of some debate :)
-
@dustin rough idea of users and number of api hits per user per hour?
-
@briantroy No, I don't remember. I just slowed it done some and they stopped rejecting me. They publish the other API limits.
-