<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Blog on Jackenhack</title><link>https://www.jackenhack.com/tags/blog/</link><description>Recent content in Blog on Jackenhack</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 01 Sep 2014 00:00:00 +0000</lastBuildDate><atom:link href="https://www.jackenhack.com/tags/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Image Compression JPEG Tools for Web</title><link>https://www.jackenhack.com/image-compression-tools-web/</link><pubDate>Mon, 01 Sep 2014 00:00:00 +0000</pubDate><guid>https://www.jackenhack.com/image-compression-tools-web/</guid><description>&lt;p&gt;&lt;img alt="Test Image 3" decoding="async" height="99" loading="lazy" src="https://www.jackenhack.com/image-compression-tools-web/images/testimage-3-150x99_hu_3b5a62d7dfbb6359.jpg" width="150"&gt; There are several JPEG image compression tools available that takes a jpeg file and reduces the size of the photo without altering the quality. But which one works best for posting images on a website? I was curious, so I took the tools I usually use and put them through the compress photo function. All applications tested claims not to lower the quality of the image. I’m concentrating on testing jpeg files here, and do a followup article later with results for optimizing PNG files.&lt;/p&gt;</description></item><item><title>Loosing Google PageRank Because of hAtom errors</title><link>https://www.jackenhack.com/google-pagerank-hatom-errors/</link><pubDate>Tue, 10 Jun 2014 00:00:00 +0000</pubDate><guid>https://www.jackenhack.com/google-pagerank-hatom-errors/</guid><description>&lt;p&gt;&lt;img alt="Hans Gerwitz" decoding="async" height="449" loading="lazy" sizes="(min-width: 768px) 720px, 100vw" src="https://www.jackenhack.com/google-pagerank-hatom-errors/images/1402378059_hu_622244842a15fa9c.jpg" srcset="https://www.jackenhack.com/google-pagerank-hatom-errors/images/1402378059_hu_d05a7827b30337c6.jpg 360w,/google-pagerank-hatom-errors/images/1402378059_hu_84ecc8326eccc617.jpg 480w" width="600"&gt;&lt;/p&gt;
&lt;h2 id="hatom-errors-and-google-pagerank"&gt;hAtom errors and Google PageRank&lt;/h2&gt;
&lt;p&gt;When I checked my blog in Google Webmaster I noticed a lot of errors in the Structured Data section. After fixing the errors in Wordpress by adding structured data, my traffic increased without any changes. That includes posts. So obviously Google uses hAtom when setting PageRank.&lt;/p&gt;</description></item><item><title>Editorial iOS Upload Images to WordPress Workflow</title><link>https://www.jackenhack.com/editorial-app-upload-images-wordpress-workflow/</link><pubDate>Thu, 17 Apr 2014 00:00:00 +0000</pubDate><guid>https://www.jackenhack.com/editorial-app-upload-images-wordpress-workflow/</guid><description>&lt;h1 id="update-a-newer-better-version-has-been-created-you-can-download-it-here"&gt;Update: A newer, better version has been created. &lt;a href="https://www.jackenhack.com/editorial-app-workflow-upload-image-wordpress-media-library/"&gt;You can download it here&lt;/a&gt;.&lt;/h1&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;&lt;img alt="Download on the AppStore" decoding="async" height="200" loading="lazy" sizes="(min-width: 768px) 720px, 100vw" src="https://www.jackenhack.com/editorial-app-upload-images-wordpress-workflow/images/Download_on_the_App_Store_Badge_US-UK_135x40_0824_hu_e9bd881d9508069.png" srcset="https://www.jackenhack.com/editorial-app-upload-images-wordpress-workflow/images/Download_on_the_App_Store_Badge_US-UK_135x40_0824_hu_9f896ab9e7102ec7.png 360w,/editorial-app-upload-images-wordpress-workflow/images/Download_on_the_App_Store_Badge_US-UK_135x40_0824_hu_dc70ee18946631a9.png 480w" width="659"&gt;&lt;/p&gt;
&lt;p&gt;I use the excellent iPad app &lt;a href="http://omz-software.com/editorial/" title="Editorial for iPad"&gt;Editorial&lt;/a&gt; as my preferred text editor. I want to be able to upload images directly from Editorial to &lt;a href="https://wordpress.org/" title="WordPress › Blog Tool, Publishing Platform, and CMS"&gt;WordPress&lt;/a&gt;, using &lt;a href="http://python-wordpress-xmlrpc.readthedocs.org/en/latest/" title="Welcome to python-wordpress-xmlrpc’s documentation! — python-wordpress-xmlrpc 2.2 documentation"&gt;xmlrpc&lt;/a&gt;, so the images ends up in the media gallery, the files in the correct folders, thumbnails made and a &lt;a href="https://daringfireball.net/projects/markdown/" title="Daring Fireball: Markdown"&gt;Markdown&lt;/a&gt; link with the correct URL is created. So I’ve written a workflow you can download that gives you the ability to select some text (that will be the alt text for the image), and either upload the image in the original size, or resize the width to the dimension you specify. After the image is uploaded, the Markdown image code is inserted. Another good thing is that you have the ability to name the image file, which I haven’t seen in other solutions, like in Poster App, where you get the cryptical iOS internal name of the image. Not so SEO friendly. The easiest solution was to use the wordpress_xmlrpc module, so that needs to be installed before you can use the workflow! but I’ve &lt;a href="https://www.jackenhack.com/editorial-app-import-modules-with-pipista/"&gt;written a guide about how to install the module/library here&lt;/a&gt;. If you forget to install it beforehand, you will get this dialog box with instructions on how to install it if you start the workflow.&lt;/p&gt;</description></item></channel></rss>