ESN system

[bradfitz]

Update (2006-09-07): This post, while of historical interest, doesn't reflect the underlying implementation that finally happened in mid-2006. For actual data structures, see LJ/ESN.pm, LJ/Event.pm, LJ/Subscription.pm, etc...This post is a quick introduction and overview of the forthcoming Event, Subscription, and Notification system, or ESN

Comments

[halkeye]

i'll attempt it after midterms are done (tuesday afternoon)
unless someone wants todo it earlier

[evan]

Might want to consider letting people block subscriptions. (I know it's silly 'cause the blockee can reload periodically, but I think a lot of people might get mad anyway.)

[ntang]

How would the subscribee even know they were being "watched"?

I'm personally leaning towards the "if you don't want this person subscribing to this stuff, post it at a security level they can't see" idea.

[clith]

Nit pick: a "subscribee" is usually called a "publisher"

:-)

Re:

[ntang]

I have three things to say to you.

1.) Depends how you look at it. I was trying to distinguish between "publishers than know they're publishing, i.e., pushing data" and "people that are getting subscribed to, unwittingly. If someone peeks through your shades to watch you undress, it could be argued you aren't publishing that view to them. In the context of the discussion I think it made sense.

2.) It was also partially motivated by his use of "blockee".

3.) *phhhhbbbttttt*

Good day, sir!

Re: question.

[bc]

Good question. I was going to ask that.
And I also like Evan's suggestion on blocking.
The two together would make most happy, I believe. (Notification and Blocking).

Re: question.

[worldpeacedir1]

I agree notification on blocking wud work better

[ntang]

Initially only email and text message will be supported.

Gah, text messaging support. Now I really need to make sure everything's working. Speaking of which, I'm working on the next version, I'll send it to you probably this coming weekend, maybe sooner if I get the time.

[xb95]

Oooh. I like. This should be client accessible. (Or if it's not, I'll make it so.) I'd like clients to be able to actually see what updates are happening instead of just seeing "There are new friends posts!" :)

[mart]

That'll be easier if clients ever start using a persistant connection protocol. Until then, polling for a boolean value is bad enough let alone polling for a list of events...

It'd be butt-ugly.

well let us both wait

[worldpeacedir1]

let us both wait to see on the finishing touches of this point
uno it is never over untill the fat lady sings