Notices where this attachment appears
-
@nestort @tom79 Parsing isn't necessary, that'd be a horrible solution. It's all in the appropriate XML data structure/metadata, in the activity:verb - <activity:verb>http://activitystrea.ms/schema/1.0/post</activity:verb>
The thing is that these are not "post" verbs, they're "favorite" instead for example. Just read the data properly and you'll be fine. I think there's some hack to make JSON suck less. The real way to parse it with JSON wouldn't be the sucky Twitter-api-feed ".json" but rather ".as", but JSON will always be second to XML in awesomeness anywayz...
The hack for the .json endpoint might be something like:
is_post_verb: "false",
-
You can see that:
<activity:verb>http://activitystrea.ms/schema/1.0/share</activity:verb>
is always "[...]/share" on a repeat. On everything that you're interested to see in the comments feed, it will have:
<activity:verb>http://activitystrea.ms/schema/1.0/post</activity:verb>
instead ([...]/post).
Is it ok to filter on that?