I read through the first claim, here's a summary I built as I went along (IANAL so I'm probably wrong). Their first claim is the following: A way to communica

I read through the first claim, here's a summary I built as I went along (IANAL so I'm probably wrong). Their first claim is the following: A way to communicate between computers (1:many) where users can designate by computer to follow someone else. Where users are identified by accounts where following is an account config. Where users can be notified of messages that they are not explicitly told about (but follow). Where another user is marked as the sender (we have their followers, so that is implicitly marked too). Where the first user is one of the followers. Where the first user has devices ("endpoints") that they'd like to recieve messages from (phone/etc), this patent applies to sending each message to each of the endpoints in their appropriate format. Points 2-8 are about: - Different ways to send the message. - per-following subscription preferences. - Message preferences set up in weird ways. (3. I'm not too sure on this) - Broadcasting through an aggregator that sends data through batched messages. - Translating messages from/to UTF-8/etc. - Delivering messages at specific times. - Sending URLs to messages At a glance, claim 9 is about storing the data for a message. Claims 10-15 are about: - Different ways to trigger the message that this data can represent. - Per-following subscription preferences (I'm starting to think this is Twitter group subscriptions) - Per-following subscription preferences including time periods. - Messages that have no explicit recipient. - Aggregated message delivery. - Sending URLs to messages as the message At a glance, claim 16 is about building the system that does this. Claims 17-22 are pretty much the same as 10-15 EDIT: Wow, I didn't realize HN uses a variant of Markdown. (Good, good)