ESN system

Mar 03, 2002 23:12


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 ( Read more... )

esn

Leave a comment

evan March 4 2002, 00:37:22 UTC
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.)

Reply

ntang March 4 2002, 05:11:12 UTC
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.

Reply

clith June 6 2002, 12:12:55 UTC
Nit pick: a "subscribee" is usually called a "publisher"

:-)

Reply

Re: ntang June 6 2002, 12:34:06 UTC
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!

Reply

let all of us find out worldpeacedir1 September 19 2006, 21:12:15 UTC
let us see what is in return from all of this before we judge

Reply


Leave a comment

Up