{"id":74,"date":"2005-06-01T23:38:23","date_gmt":"2005-06-02T04:38:23","guid":{"rendered":"http:\/\/crschmidt.net\/blog\/?p=74"},"modified":"2005-06-01T23:38:23","modified_gmt":"2005-06-02T04:38:23","slug":"in-feed-feedback","status":"publish","type":"post","link":"https:\/\/crschmidt.net\/blog\/archives\/74\/in-feed-feedback\/","title":{"rendered":"In-Feed Feedback"},"content":{"rendered":"

I’m playing second fiddle to Danny again right now, implementing his Reader Provided Blog Enhancements<\/a> as a wordpress plugin. Currently I’m posting to a local MySQL table, from which I can pull the relevant information and create different views later. <\/p>\n

This is a great example of some code that would be nice to do with XmlHttpRequest: rather than having the post go to a redirect (which is only going to work if the user has referrers on right now, otherwise it just brings to a single page that says it was completed), it could all be done in the client, and the user would never have to leave.<\/p>\n

However, there’s a couple problems with this. <\/p>\n

1. RSS Aggregators are not web browsers, and depending on the level of the implementation they are using for displaying HTML content, they may not support Javascript at all or not completely. I’m hoping that HTTP POST will actually do something useful for most of them, but even that is a guess.
\n2. Online aggregators such as LiveJournal oftentimes strip out Javascript to prevent malicious cookiestealing (and for good reason). <\/p>\n

So, unfortunately, javascript is out.<\/p>\n

Couple changes that will be happening in the meantime while I work on this: RSS feeds will be limited in size to 1 or 2 posts, so that you don’t get change-flooded every time I turn the plugin on or off to test something, and you may see the review boxes appear or disappear. <\/p>\n

Anyway, nothing much to see yet, but I will be doing RDF export of annotations provided, so the data isn’t going to be lost, and I will be working to clean up the code and make it “just work” with a WordPress plugin, hopefully. They are surprisingly easy to write. I didn’t realize how simple some of the stuff was. Keep your eyes on the prize!<\/p>\n

Oh, and Danny? Your RDF in that post is broken. Missing rdf:RDF, and one of your close tags is missing a \/. Thought I’d let you know \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"

I’m playing second fiddle to Danny again right now, implementing his Reader Provided Blog Enhancements as a wordpress plugin. Currently I’m posting to a local MySQL table, from which I can pull the relevant information and create different views later. This is a great example of some code that would be nice to do with […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,18],"tags":[],"class_list":["post-74","post","type-post","status-publish","format-standard","hentry","category-semantic-web","category-social"],"_links":{"self":[{"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/posts\/74","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/comments?post=74"}],"version-history":[{"count":0,"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/posts\/74\/revisions"}],"wp:attachment":[{"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/media?parent=74"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/categories?post=74"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/crschmidt.net\/blog\/wp-json\/wp\/v2\/tags?post=74"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}