{"id":9,"date":"2010-11-18T11:07:42","date_gmt":"2010-11-18T19:07:42","guid":{"rendered":"http:\/\/markwatches.net\/reviews\/?p=9"},"modified":"2010-11-18T11:47:46","modified_gmt":"2010-11-18T19:47:46","slug":"hello-watchers-lets-get-down-to-details","status":"publish","type":"post","link":"https:\/\/markwatches.net\/reviews\/2010\/11\/hello-watchers-lets-get-down-to-details\/","title":{"rendered":"Hello watchers! Let&#8217;s get down to details."},"content":{"rendered":"<p>There will be a slight lull in activity until I get things settled on the Reads site, but the very first true review will go up tomorrow: Mark Watches <em>Deathly Hallows, Part I<\/em>. Don&#8217;t you guys feel lucky? YOU GET THE FIRST REVIEW.<\/p>\n<p>Anyway, like <a href=\"http:\/\/markreads.net\/reviews\/2010\/11\/hello-readers-lets-get-down-to-details\/\" target=\"_blank\">the post I just made over on Mark Reads<\/a>, here are the details about registration, commenting, and scheduling. Discuss!<\/p>\n<h1><span style=\"text-decoration: underline;\"><strong><!--more-->Registration<\/strong><\/span><\/h1>\n<p>When I was doing research back in September for where I was going to move to (YES, I HAVE BEEN HOLDING THIS IN FOR TWO FUCKING MONTHS), I settled on WordPress because I was familiar with their posting system and I knew I&#8217;d ultimately be able to have a custom template built that best suited what I wanted to do. That being said, the way to register or subscribe to this site is a tad confusing. So here are your options:<\/p>\n<p>1)\u00c2\u00a0Register for this blog as a member\/user.\u00c2\u00a0Over on the right side, under &#8220;Meta,&#8221; click Register. This will create a UNIQUE LOGIN FOR THIS WORDPRESS BLOG ONLY. This is why you can&#8217;t use it across the board.<\/p>\n<p>2)\u00c2\u00a0Enter your general WordPress account info in the comments to &#8220;login.&#8221;\u00c2\u00a0If you already have a WordPress account, you can comment.<\/p>\n<p>3)\u00c2\u00a0Register for an IntenseDebate account. And they are pretty nifty, because you can use it all over the web and it tracks where you left all your comments so that it is easy to see if anyone replied to you.<\/p>\n<p>4)\u00c2\u00a0Enter your nickname, email, and optional site.\u00c2\u00a0This way doesn&#8217;t subscribe you in any way and also is 100% temporary.<\/p>\n<p>I&#8217;ve also removed the limit on having a moderator approve your first comment before it shows up. It&#8217;s already too much work and I can&#8217;t imagine how bad it would be during a live blog. Yikes!<\/p>\n<p>Make sense? I&#8217;m not turning on Facebook registration because Facebook already creeps me out and I&#8217;d like to avoid using them.<\/p>\n<p>Onwards we go!<\/p>\n<h1><span style=\"text-decoration: underline;\"><strong>GIFs, JPGs, PNGs, etc in comments.<\/strong><\/span><\/h1>\n<p>They are now live. You MUST use your own hosting, as you can no longer host them in the comments. I&#8217;m going to look into a CSS hack that might allow you to upload to my hosting that I bought, but for the time being, you&#8217;ll have to use the &lt; img src=&#8221;URL HERE&#8221; &gt; code. And remove the spaces around the brackets.<\/p>\n<p>I EXPECT MANY GIFS IN THE COMMENTS. Since it&#8217;s paginated better and you can actually close all the comments, the page should load better.<\/p>\n<h1><span style=\"text-decoration: underline;\"><strong>Schedule<\/strong><\/span><\/h1>\n<p>Tomorrow, I&#8217;ll post my review for <em>Deathly Hallows<\/em> and will most likely spend next week prepping\/reviewing for Mark Reads and dealing with the Thanksgiving holiday. I hope to have my first review for <em>Firefly<\/em> up on Monday, November 29th. And while I figure out how to balance multiple sets of reviews, it may be a bit choppy over here. \ud83d\ude42<\/p>\n<p>I&#8217;ll also ask if you guys want a @markreadswatches Twitter account for notifications and such! Does it sound like something you&#8217;d be interested in?<\/p>\n<h1><strong>I ALREADY DID IT. Follow me: <\/strong><a href=\"http:\/\/twitter.com\/markdoesstuff\" target=\"_blank\"><strong>@MarkDoesStuff<\/strong><\/a><\/h1>\n<p>DISCUSS SUCH THING!<\/p>\n","protected":false},"excerpt":{"rendered":"<p>There will be a slight lull in activity until I get things settled on the Reads site, but the very first true review will go up tomorrow: Mark Watches Deathly Hallows, Part I. Don&#8217;t you guys feel lucky? YOU GET &hellip; <a href=\"https:\/\/markwatches.net\/reviews\/2010\/11\/hello-watchers-lets-get-down-to-details\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[10,11,12],"class_list":["post-9","post","type-post","status-publish","format-standard","hentry","category-firefly","category-harry-potter","tag-harry-potter-2","tag-harry-potter-and-the-deathly-hallows","tag-mark-watches-firefly"],"_links":{"self":[{"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/posts\/9","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/comments?post=9"}],"version-history":[{"count":0,"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/posts\/9\/revisions"}],"wp:attachment":[{"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/media?parent=9"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/categories?post=9"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/markwatches.net\/reviews\/wp-json\/wp\/v2\/tags?post=9"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->