{"id":6726,"date":"2012-01-22T00:04:01","date_gmt":"2012-01-22T08:04:01","guid":{"rendered":"http:\/\/nearfuturelaboratory.com\/?p=6726"},"modified":"2017-08-18T17:58:24","modified_gmt":"2017-08-18T17:58:24","slug":"privatesquare","status":"publish","type":"post","link":"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/","title":{"rendered":"privatesquare"},"content":{"rendered":"<p>I&#8217;ve been working on, and testing out, a new thing for the last couple of weeks. It is called <strong>privatesquare<\/strong>. It is a pretty simple web application that manages a private database of foursquare check-ins. It uses foursquare itself  as a login service and also queries foursquare for nearby locations. The application uses the built-in geolocation hooks in the web browser to figure out what &#8220;nearby&#8221; means (which sometimes brings the weird but we&#8217;ll get to that later). On some levels it&#8217;s nothing more than a glorified check-in application. Except for two things:<\/p>\n<p>First, when you do check in the data is stored in a local database you control. Check-ins can be sent on to foursquare (and again re-broadcast to Twitter, etc. or to your followers or just &#8220;off the grid&#8221;) but the important part is: <em>They don&#8217;t have to be<\/em>. As much as this screenshot of my activity on foursquare cracks me up it&#8217;s not actually representative of my life and suggests a particular kind of self-censorship. I don&#8217;t tell foursquare about a lot of stuff simply because I&#8217;m not comfortable putting that data in to their sandbox. So as much as anything privatesquare is about making a place to file those things away safely for future consideration. A kind of personal <a href=\"http:\/\/www.aaronland.info\/weblog\/2011\/04\/02\/status\/#mw2011\">zone of safekeeping<\/a>.<\/p>\n<div style=\"text-align:center\"><img alt=\"\" src=\"http:\/\/farm8.staticflickr.com\/7027\/6728731529_ca57819e1c_z.jpg\" style=\"margin-bottom:30px\" \/><\/div>\n<p>Second, privatesquare has its own <a href=\"https:\/\/twitter.com\/#!\/antimega\/status\/161508845145964544\">internal taxonomy<\/a> of event-iness. It is:<\/p>\n<ul style=\"margin-left:20%\">\n<li>I am here<\/li>\n<li>I was there<\/li>\n<li>I want to go there<\/li>\n<li>again<\/li>\n<li>again again<\/li>\n<li>again maybe<\/li>\n<li>again never<\/li>\n<\/ul>\n<p>The first item maps the easiest to foursquare&#8217;s model of &#8220;checking in&#8221;. It is what it says on the tin. The second is the thing that you can&#8217;t do on foursquare but everyone does anyway: Checking in after the fact if only to have a personal record of things you&#8217;ve done. This just makes the act explicit. The third is not unlike the <a href=\"http:\/\/blog.foursquare.com\/2011\/08\/15\/foursquare_lists\/\">&#8220;lists&#8221; feature<\/a> that was introduced on foursquare, last year. <em>It is also the one flavour of check-in that is not forwarded on foursquare.<\/em> I suppose I could figure out how to add things to a list, but I haven&#8217;t yet.<\/p>\n<p>The last four are a long overdue love song to <a href=\"http:\/\/anti-mega.com\/antimega\/\">Chris Heathcote<\/a> and a plaintive desire for something like the <a href=\"https:\/\/www.dopplr.com\/socialatlas\">Dopplr Social Atlas<\/a> (not to mention <a href=\"http:\/\/revoluser.com\/talks\/122-designing-for-spacetime-building-in-no-time-cross-platform-service-design-in-a-start-up-context\">Dopplr<\/a> itself) but one that isn&#8217;t held hostage to the <a href=\"https:\/\/twitter.com\/#!\/thisisaaronland\/status\/141689911752396800\">seeming neglect<\/a> of its parent company, Nokia. Once upon a time, <a href=\"http:\/\/www.flickr.com\/photos\/straup\/sets\/72157594187100815\/detail\/\">I went to Helsinki<\/a> for Important Business Meetings \u2122  involving Flickr and Nokia while Chris still lived and worked in Finland. I asked him where I should eat during my stay and he sent back a long list of restaurants (all lunch places, I think) each flagged as &#8220;again&#8221;, &#8220;againagain&#8221; and so on.<\/p>\n<div style=\"text-align:center\"><a href=\"http:\/\/blog.dopplr.com\/2009\/07\/06\/help-illustrate-the-social-atlas-on-flickr\/\"><img alt=\"\" src=\"http:\/\/blog.dopplr.com\/wp-content\/uploads\/2009\/03\/beenhere.png\" style=\"margin-bottom:30px\" \/><\/a><\/div>\n<p>The Social Atlas was a feature added <a href=\"http:\/\/blog.dopplr.com\/2009\/03\/20\/the-dopplr-new-york-release-rolling-out-the-social-atlas\/\">somewhere around year two<\/a> at Dopplr and is a list of places to eat at, stay in or explore. Places are added by the users and organized by city. It remains a lovely example of how to do this sort of thing though there&#8217;s not much going on there these days. You can flag as place as somewhere you&#8217;ve been, somewhere you like but not someplace you dislike. Which always seemed like a shame because I would find it helpful to know that someone I know and trust dislikes a restaurant in London as much as I despise Herbivore, in San Francisco.<\/p>\n<p>Chris&#8217; is a genius classification system. It does not get lost in the weeds of weird similes and absurd metaphors (wine tasting, anyone?) and by and large captures the experience of asking someone where you should go to eat in a place you&#8217;re not all that familiar with. It is also entirely bound to the relationship of the person telling and the person asking. It is <em>not<\/em> a recommendation engine.<\/p>\n<div style=\"text-align:center\"><a href=\"http:\/\/blog.dopplr.com\/2009\/07\/06\/help-illustrate-the-social-atlas-on-flickr\/\"><img alt=\"\" src=\"http:\/\/farm3.static.flickr.com\/2467\/3643958883_bd249f44a6.jpg\" style=\"margin-bottom:30px\" \/><\/a><\/div>\n<p>It assumes that although two people would both do something again, or do it enthusiastically (&#8220;againagain&#8221;), they are just as likely not to do the <em>same<\/em> thing. Those details are left out of the equation (read: the computer) because it will never be able to account for the subtlety and history of experience between two people.<\/p>\n<p>The &#8220;again&#8221; ratings (markings, like on a tree?) are an odd lot in that they don&#8217;t go out of there way to distinguish themselves in time. Is it just an indication that you went there some time in the past and want some record of the event? Or does it mean that you wait to check-in until you&#8217;ve decided how you feel about it? Or do you check-in and then say whether it was good or not?<\/p>\n<p>I am very consciously punting on these questions for the time being in order to see how the thing actually gets used and what I find myself wishing it did. I suspect that most of the confusion that may be generated by these kinds of blurry and overlapping assignments can be overcome by displaying dates and times clearly.<\/p>\n<p>It is worth nothing that privatesquare does almost nothing that foursquare doesn&#8217;t already do, and better. privatesquare is not meant to replace foursquare but is part of an on-going exploration of the hows and whens and whys of backing up centralized services with bespoke shadow, or parallel, implementations of the service itself. It is designed to be built and run by individuals or as a managed service for small groups of people who know and trust one another.<\/p>\n<p>privatesquare remains a work in progress and I am not planning to run it as a public service any time soon but it is available as an open-source project, on Github, that you can run yourself:<\/p>\n<p style=\"font-size:2em;font-family:serif;text-align:center\"><a href=\"http:\/\/straup.github.com\/privatesquare\/\">http:\/\/straup.github.com\/privatesquare\/<\/a><\/p>\n<p>The documentation and installation process still remains out of bounds for most people who don&#8217;t self-identify with the nerd squad but that will sort itself out over time. For what it&#8217;s worth my copy is running on <em>insert a vanilla shared web-hosting provider that can run WordPress here<\/em> so that&#8217;s a promising start, I think.<\/p>\n<p>The site is built on top of <a href=\"https:\/\/github.com\/exflickr\/flamework\">Flamework<\/a>, which is a whiteroom re-implimentation of the core libraries and tools that a bunch of ex-Flickr engineers used to build Flickr, the same way that <a href=\"http:\/\/www.aaronland.info\/weblog\/2011\/10\/14\/pixelspace\/#parallel-flickr\">parallel-flickr<\/a> is. Meaning that some part of all these projects is just putting Flamework through its paces to find the stress points and to better understand the hows and whats of the process (installation, documentation, gotchas and so on) should be. And like parallel-flickr &#8220;it ain&#8217;t pretty or classy (yet) but it does work.&#8221;<\/p>\n<div style=\"text-align:center\"><img alt=\"\" src=\"http:\/\/farm8.staticflickr.com\/7169\/6669924579_3e7a6c2072_z.jpg\" style=\"margin-bottom:30px\" \/><\/div>\n<p>Here&#8217;s an unordered list of the things privatesquare still doesn&#8217;t do:<\/p>\n<ul style=\"margin-left:7%;margin-right:5%\">\n<li>\n<p>Sync with the <a href=\"https:\/\/developer.foursquare.com\/\">foursquare API<\/a>. For a whole bunch of reasons you might find yourself checking in to foursquare using another client application. privatesquare should be able to fetch and merge all those check-ins that it didn&#8217;t handle first.<\/p>\n<\/li>\n<li>\n<p>The &#8220;nearest linear&#8221; cell-tower problem. This is one of those problems that gives credence to all the hyperbolic hand-waving done by companies driving around mapping latitude and longitude coordinates for wifi networks. Without this data determining geographic location for a web application running on a phone is often handled by assuming that whatever cell tower your phone is connected to is &#8220;good enough&#8221;. Sometimes it is but just as often it&#8217;s not. You have a line-of-sight, a signal, back to a cell tower that exceeds the maximum radius in which to query for venues. Because your phone thinks you are somewhere else you always end up falling outside the hula-hoop of places that are <em>actually<\/em> near you.<\/p>\n<p>The map that&#8217;s displayed with venue listings (there&#8217;s a screenshot at the bottom of this post) is one possible alternative. As I write this the map isn&#8217;t responsive. It&#8217;s just there to try and help you understand why a particular list of places was chosen. Eventually you should be able to re-center the map to a given location and use that when looking up nearby venues, for those times when your web browser can&#8217;t figure out who is on first by itself.<\/p>\n<\/li>\n<li>\n<p>There is no ability to delete (or undo) check-ins.<\/p>\n<\/li>\n<li>\n<p>There is no ability to add new venues. Nor is there any way to record events offline or when you don&#8217;t have a network connection. I&#8217;m not sure whether either of these will ever happen. At the moment there are just too many other things going on. Beyond that I sort of like the fact that privatesquare doesn&#8217;t try to do everything.<\/p>\n<\/li>\n<li>\n<p>There is no way to distinguish duplicate venues (same name, different ID).<\/p>\n<\/li>\n<li>\n<p>Export, which is probably the single most important thing to add in the short-term. This includes a plain old web view of past check-ins.<\/p>\n<\/li>\n<li>\n<p>Pages for venues, though I&#8217;m really sure what I was thinking when I was blocking out this blog post and wrote that. It&#8217;s probably related to what I wrote about cities (below) and the idea that the really interesting aspect of a venue page is seeing a user&#8217;s arc of <em>again-iness<\/em> for that spot over time.<\/p>\n<\/li>\n<li>\n<p>Pages for cities. The other nice thing that privatesquare does when you check-in is <a href=\"https:\/\/github.com\/straup\/reverse-geoplanet\">&#8220;reverse geocode&#8221;<\/a> the location of the venue and store the Where On Earth (WOE) ID of the city the venue is in. Which will make it possible to build something that looks like the Social Atlas. For example, if you were going to <a href=\"https:\/\/www.dopplr.com\/place\/ca\/montr%C3%A9al\/\">Montr\u00e9al<\/a> I might send you a link to  all my check-ins in that city <a href=\"http:\/\/woe.spum.org\/id\/3534\">(WOE ID 3534)<\/a> tagged &#8220;again&#8221;, &#8220;againagain&#8221; and &#8220;I want to go there&#8221;.<\/p>\n<\/li>\n<\/ul>\n<p>In a way privatesquare is just the foursquare version of <a href=\"http:\/\/straup.github.com\/parallel-flickr\/\">parallel-flickr<\/a>: a tool to backup your check-ins, albeit pre-emptively. Which is sort of an interesting idea all on its own. The differences between the two applications are that parallel-flickr doesn&#8217;t let you upload photos (yet) and privatesquare doesn&#8217;t really provide any mechanism for sharing your check-ins with a restricted set of users. Currently, it&#8217;s all or nothing (read: &#8220;nothing&#8221; because the code forces you to be logged in before you can see anything).<\/p>\n<div style=\"text-align:center\"><img alt=\"\" src=\"http:\/\/farm8.staticflickr.com\/7010\/6740130203_f2d7a85ed5.jpg\" style=\"margin-bottom:30px\" \/><\/div>\n<p>I am also thinking about forking; piggybacking; hijacking (<em>piggyjacking?<\/em>) some or all of the work that Stamen has done with the <a href=\"http:\/\/dotspotting.org\/\">Dotspotting<\/a> project. For two reasons: First they are both built on Flamework so it ought to be possible to make them hold hands without too much fuss. Second, there&#8217;s a nice un-intended feature in the way the code for browser things and the code for database things handle the data that people upload to the site: HTML tables.<\/p>\n<p>In theory (and I haven&#8217;t tested this out yet) anything that can generate an HTML table, with the relevant semantic attributes, and send it to the browser along with the relevant JavaScript code will be able to take advantage of all the <a href=\"http:\/\/dotspotting.org\/embed\/photo\/?type=photo&amp;oid=12&amp;sid=1109\">lovely display and interaction work<\/a> that <a href=\"http:\/\/sean.forty-ninth.com\/\">Sean Connelley<\/a> and <a href=\"http:\/\/prag.ma\/\">Shawn Allen<\/a> did for Dotspotting. Just like that!<\/p>\n<div style=\"text-align:center\"><a href=\"http:\/\/dotspotting.org\/embed\/bucket\/map?user=594&amp;sheet=1463&amp;title=ManAboutCouch's+FourSquare+Checkins&amp;bucket=title&amp;tt=title&amp;tm=created#8\/52.718\/-7.396\"><img src=\"http:\/\/farm8.staticflickr.com\/7152\/6743855013_2c62a764d8.jpg\" style=\"margin-bottom:30px\" \/><\/a><\/div>\n<p>The reason this all works is that when we started writing Dotspotting it was during a time when Flamework was still pretty green and lacking any code for doing API delegation or authentication. <a href=\"https:\/\/github.com\/citytracking\/dotspotting\">Rather than trying to shave that particular yak<\/a> we simply opted to use the HTML sent to the browser and jQuery as a kind of internal good-enough-for-now API.<\/p>\n<p>Once it&#8217;s sorted for privatesquare it should be easy enough to swap out the table parsing code with proper API calls, now that Flamework has its own <a href=\"https:\/\/github.com\/straup\/flamework-api\">API delegation code<\/a>, and then it could be dropped in to parallel-flickr as an alternative view of your geotagged photos.<\/p>\n<div style=\"text-align:center\"><img alt=\"\" src=\"http:\/\/farm8.staticflickr.com\/7027\/6740130741_d776fb64f6.jpg\" style=\"margin-bottom:30px\" \/><\/div>\n<p>It&#8217;s all still magic-pony talk and none of it addresses mobile (tiny) web browsers or anything but a pretty conventional linear paginated view of the data (no clustering or other fancy stuff) but, still: This pleases me.<\/p>\n<p>In the short-term I&#8217;m going to continue to focus primarily on the data input side of things trying to make it as easy and fast as possible to record the data along with the simplest of CSV or GeoJSON exports, so that you could at least look at your data in tools like <a href=\"http:\/\/dotspotting.org\/faq\/\">Dotspotting<\/a> or <a href=\"http:\/\/straup.github.com\/showme-the-geojson\/\">Show Me the GeoJSON<\/a> respectively.<\/p>\n<div style=\"text-align:center\"><img alt=\"\" src=\"http:\/\/farm8.staticflickr.com\/7170\/6739846505_ba33b9dcbc_z.jpg\" style=\"margin-bottom:30px\" \/><\/div>\n<p> And if I can get that part squared then it also might be possible to re-use some of the same work to make things like <a href=\"http:\/\/nearfuturelaboratory.com\/2011\/11\/30\/airport-timer\/\">Airport Timer<\/a> easier since the two projects are each a kind of side-car to the other, when you stop and think about it.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;ve been working on, and testing out, a new thing for the last couple of weeks. It is called privatesquare. It is a pretty simple web application that manages a private database of foursquare check-ins. It uses foursquare itself as a login service and also queries foursquare for nearby locations. The application uses the built-in &hellip; <a href=\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">privatesquare<\/span><\/a><\/p>\n","protected":false},"author":4,"featured_media":6746,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[99,101,163],"tags":[353,527,530,552,687,1204,870],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v14.9 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>privatesquare - Near Future Laboratory<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"privatesquare - Near Future Laboratory\" \/>\n<meta property=\"og:description\" content=\"I&#8217;ve been working on, and testing out, a new thing for the last couple of weeks. It is called privatesquare. It is a pretty simple web application that manages a private database of foursquare check-ins. It uses foursquare itself as a login service and also queries foursquare for nearby locations. The application uses the built-in &hellip; Continue reading privatesquare\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/\" \/>\n<meta property=\"og:site_name\" content=\"Near Future Laboratory\" \/>\n<meta property=\"article:published_time\" content=\"2012-01-22T08:04:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2017-08-18T17:58:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.nearfuturelaboratory.com\/wp-content\/uploads\/2012\/01\/IBlameCheathco.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1024\" \/>\n\t<meta property=\"og:image:height\" content=\"768\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@nearfuturelab\" \/>\n<meta name=\"twitter:site\" content=\"@nearfuturelab\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Organization\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#organization\",\"name\":\"Near Future Laboratory\",\"url\":\"https:\/\/blog.nearfuturelaboratory.com\/\",\"sameAs\":[\"https:\/\/www.instagram.com\/nearfuturelaboratory\/\",\"https:\/\/www.linkedin.com\/company\/near-future-laboratory\/\",\"https:\/\/twitter.com\/nearfuturelab\"],\"logo\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#logo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/blog.nearfuturelaboratory.com\/wp-content\/uploads\/2019\/10\/NearFutureLaboratoryLogo-CS4.jpg\",\"width\":1049,\"height\":206,\"caption\":\"Near Future Laboratory\"},\"image\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#logo\"}},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#website\",\"url\":\"https:\/\/blog.nearfuturelaboratory.com\/\",\"name\":\"Near Future Laboratory\",\"description\":\"Clarify Today, Design Tomorrow\",\"publisher\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":\"https:\/\/blog.nearfuturelaboratory.com\/?s={search_term_string}\",\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#primaryimage\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/blog.nearfuturelaboratory.com\/wp-content\/uploads\/2012\/01\/IBlameCheathco.jpg\",\"width\":1024,\"height\":768,\"caption\":\"I blame Cheathco\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#webpage\",\"url\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/\",\"name\":\"privatesquare - Near Future Laboratory\",\"isPartOf\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#primaryimage\"},\"datePublished\":\"2012-01-22T08:04:01+00:00\",\"dateModified\":\"2017-08-18T17:58:24+00:00\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/\"]}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#webpage\"},\"author\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#\/schema\/person\/5afd3cc0d47493023ab09e434821969a\"},\"headline\":\"privatesquare\",\"datePublished\":\"2012-01-22T08:04:01+00:00\",\"dateModified\":\"2017-08-18T17:58:24+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#webpage\"},\"commentCount\":3,\"publisher\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/2012\/01\/22\/privatesquare\/#primaryimage\"},\"keywords\":\"Check-in,Foot,Foursquare,Geography,location,Location Based,Privacy\",\"articleSection\":\"Landscape as Interface,Location Based,Social Practice\",\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#\/schema\/person\/5afd3cc0d47493023ab09e434821969a\",\"name\":\"Aaron\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/blog.nearfuturelaboratory.com\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"http:\/\/0.gravatar.com\/avatar\/?s=96&d=mm&r=g\",\"caption\":\"Aaron\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","_links":{"self":[{"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/posts\/6726"}],"collection":[{"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/comments?post=6726"}],"version-history":[{"count":1,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/posts\/6726\/revisions"}],"predecessor-version":[{"id":10183,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/posts\/6726\/revisions\/10183"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/media\/6746"}],"wp:attachment":[{"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/media?parent=6726"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/categories?post=6726"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.nearfuturelaboratory.com\/wp-json\/wp\/v2\/tags?post=6726"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}