Menu ⇓
  3. ↪ Charles Stanhope: @BarnabyWalters Is Facebook's behavior different from Twitter's t.co in this regard? (I don't use Facebook, so genuinely curious.)

    @cstanhope Twitter do indeed shorten all links, they’re just a little bit more honest about it. But I’m certainly going to make the extension unshorten them all too (there’s enough info in the HTML do to that without extra HTTP requests).

  10. Turns out the 2 JSON structures enable safe entity expansion just like twitter entities.

    In my reply contexts I am not wanting to embed 3rd party HTML in my site, so I take the p-summary and strip tags. But, I want embedded h-cards to be expanded just like at-mentions on twitter. Pseudocode:

    
let h-card = canonical JSON structure for a note, with .summary as a plaintext representation of the content;

for item in h-card.children:
 if not in_array('h-card', item.type) continue;
 let html = HTML representation of the child from properties.url, name, etc;
 replace item.value in h-card.summary with html

    Example here.

  11. Twitter’s “you only see replies from people you follow if you also follow the target of the reply” model is quite fascinating because it means that, within a particular community, the number of tweets you see is not directly proportional to the number of people you follow. It’s probably square or cubic, perhaps I’ll model it and see.

  13. ↪ Ben Ward: @BarnabyWalters The one strange thing I see in your replies to @drewm is the lack of threading in client UI. Missing the in_reply_to header?

    benward heh, or not :/ Hopefully this time though. If not I won’t bother you with any more of these tweets :)

  14. ↪ Ben Ward: @BarnabyWalters The one strange thing I see in your replies to @drewm is the lack of threading in client UI. Missing the in_reply_to header?

    @BenWard fixed, thanks! I blame twitter for using /status/ and /statuses/ interchangeably in tweet URLs and confusing me :) This tweet should have in_reply_to set correctly.

  17. I am hugely annoyed at @twitter’s API stupidity, but almost as annoyed by their failure to provide a consistent tweet authoring experience across their platform.

    If I see “remaining chars = 0”, I expect the tweet to post, not give me some near-meaningless error message. I also expect URLs to be automatically detected and compensated for consistently across the platform. This is just crap .

  18. ↪ Kyle Weems: If you have thoughts about the @twitterapi changes (cut off RSS, public timeline, etc), you should tell me today. #squoose topic tonight.

    @cssquirrel “if” we have thoughts? You mean there’s a possibility we won’t?! My “thoughts” would fill a podcast on their own, but no–one wants to listen to me ranting to myself ;)