<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Founds</title>
	<atom:link href="http://blog.dataparksearch.org/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.dataparksearch.org</link>
	<description>Just DataparkSearch weblog</description>
	<lastBuildDate>Fri, 11 Dec 2020 00:54:34 +0000</lastBuildDate>
	<language>en-AU</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.0.11</generator>
	<item>
		<title>Safari; wss; OSStatus -9829</title>
		<link>http://blog.dataparksearch.org/694</link>
					<comments>http://blog.dataparksearch.org/694#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Fri, 11 Dec 2020 00:53:21 +0000</pubDate>
				<category><![CDATA[Uncategorized]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=694</guid>

					<description><![CDATA[You may google out several explanations on an error "WebSocket network error: The operation couldn't be completed (OSStatus error -9829)" when you attempt to connect to a secure websocket using Safari web-browser on Mac OS X 11.0.1 (Big Sur). One of them points out more strict requirements for trusted web-site certificates on MacOS an iOS, <a href="http://blog.dataparksearch.org/694" class="more-link">...continue reading<span class="screen-reader-text"> "Safari; wss; OSStatus -9829"</span></a>]]></description>
										<content:encoded><![CDATA[
<p>You may google out several explanations on an error "WebSocket network error: The operation couldn't be completed (OSStatus error -9829)" when you attempt to connect to a secure websocket using Safari web-browser on Mac OS X 11.0.1 (Big Sur). One of them points out <a href="https://support.apple.com/en-us/HT210176" data-type="URL" data-id="https://support.apple.com/en-us/HT210176">more strict requirements for trusted web-site certificates on MacOS an iOS</a>, which I didn't know.</p>



<p>However, in my case the error was caused by a drawback in Safari browser, - turn out it simply does not send user certificate when performing secure websocket connection (wss:// URL scheme).</p>



<p>Hopefully, Firefox browser doesn't have this drawback and all works fine when you use it. Though you would need to install all CA certificates and user certificate into Firefox's store as it turn out doesn't use the system's one.</p>
<p></p>]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/694/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Asynchronous Consensus Algorithm</title>
		<link>http://blog.dataparksearch.org/692</link>
					<comments>http://blog.dataparksearch.org/692#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Fri, 11 Dec 2020 00:25:38 +0000</pubDate>
				<category><![CDATA[Algorithms]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=692</guid>

					<description><![CDATA[It was published almost a year ago: https://arxiv.org/abs/2001.07704 Source code is available on GitHub: https://github.com/Fantom-foundation/libconsensus-dag]]></description>
										<content:encoded><![CDATA[
<p>It was published almost a year ago: <a href="https://arxiv.org/abs/2001.07704" data-type="URL" data-id="https://arxiv.org/abs/2001.07704">https://arxiv.org/abs/2001.07704</a></p>



<p>Source code is available on GitHub: <a href="https://github.com/Fantom-foundation/libconsensus-dag" data-type="URL" data-id="https://github.com/Fantom-foundation/libconsensus-dag">https://github.com/Fantom-foundation/libconsensus-dag</a></p>
<p></p>]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/692/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Tango magic exists!</title>
		<link>http://blog.dataparksearch.org/664</link>
					<comments>http://blog.dataparksearch.org/664#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Fri, 23 Dec 2016 10:23:07 +0000</pubDate>
				<category><![CDATA[Sydney/Australia]]></category>
		<category><![CDATA[Tango]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=664</guid>

					<description><![CDATA[Those were my happiest seconds of 2016. It took me almost 4 years to get from an absolute beginner never danced before to the first public performance. Just thank you so much Sophia de Lautour, Paul Wagner and Paul Warren for your lessons and passion and patience in explaining tango magic! If you are pondering <a href="http://blog.dataparksearch.org/664" class="more-link">...continue reading<span class="screen-reader-text"> "Tango magic exists!"</span></a>]]></description>
										<content:encoded><![CDATA[<p><iframe loading="lazy" width="560" height="315" src="https://www.youtube.com/embed/vKU3QF5eXgc" frameborder="0" allowfullscreen></iframe><br />
<span id="more-664"></span></p>
<p>Those were my happiest seconds of 2016. It took me almost 4 years to get from an absolute beginner never danced before to the first public performance. </p>
<p>Just thank you so much <strong>Sophia de Lautour</strong>, <strong>Paul Wagner</strong> and <strong>Paul Warren</strong> for your lessons and passion and patience in explaining tango magic!</p>
<p>If you are pondering to take tango class, think no further, the next beginners course at <a href="http://www.so-tango.com/">So-Tango</a> starts in the beginning of February. Sophia and Paul would be happy to lead and follow you from the first basic steps in the class into privy ulterior though warm and friendly life of Sydney <a href="http://www.so-tango.com/faq">milongas</a>.</p>
<p>See details on the poster below or click on it to go to the So-Tango web-site.</p>
<p><a href="http://www.so-tango.com/"><img loading="lazy" src="http://blog.dataparksearch.org/wp-content/uploads/2016/12/So-Tango-poster-500x731.png" alt="So Tango poster: beginners course starts 6 February 2017" width="500" height="731" class="aligncenter size-large wp-image-666" srcset="http://blog.dataparksearch.org/wp-content/uploads/2016/12/So-Tango-poster-500x731.png 500w, http://blog.dataparksearch.org/wp-content/uploads/2016/12/So-Tango-poster-205x300.png 205w, http://blog.dataparksearch.org/wp-content/uploads/2016/12/So-Tango-poster-768x1122.png 768w, http://blog.dataparksearch.org/wp-content/uploads/2016/12/So-Tango-poster-34x50.png 34w, http://blog.dataparksearch.org/wp-content/uploads/2016/12/So-Tango-poster.png 800w" sizes="(max-width: 500px) 100vw, 500px" /></a></p>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/664/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>PDF Forms editor for Ubuntu Linux</title>
		<link>http://blog.dataparksearch.org/661</link>
					<comments>http://blog.dataparksearch.org/661#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Mon, 05 Dec 2016 03:55:50 +0000</pubDate>
				<category><![CDATA[Linux/Ubuntu]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=661</guid>

					<description><![CDATA[I was unable to edit a PDF form using Evince on Ubuntu, some fields remained empty once I move cursor out of them after entering data on some reason, while other fields worked fine. Fortunately I have found Master PDF Editor 3 from Code Industry which done job perfectly. It has a free version for <a href="http://blog.dataparksearch.org/661" class="more-link">...continue reading<span class="screen-reader-text"> "PDF Forms editor for Ubuntu Linux"</span></a>]]></description>
										<content:encoded><![CDATA[<p>I was unable to edit a PDF form using Evince on Ubuntu, some fields remained empty once I move cursor out of them after entering data on some reason, while other fields worked fine.</p>
<p>Fortunately I have found <a href="https://code-industry.net/free-pdf-editor/">Master PDF Editor 3 from Code Industry</a> which done job perfectly. It has a free version for non-commercial use. In addition to Evince functionality it supports interactive instructions embedded into PDF document helping to fill the form.</p>
<p>I have tested it on Ubuntu 16.04 and 16.10.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/661/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>dpsearch-4.54-2016-12-03</title>
		<link>http://blog.dataparksearch.org/658</link>
					<comments>http://blog.dataparksearch.org/658#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Sat, 03 Dec 2016 02:17:03 +0000</pubDate>
				<category><![CDATA[DataparkSearch]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=658</guid>

					<description><![CDATA[A new snapshot version of DataparkSearch Engine has been released. You can get it on Google Drive or on GitHub. Changes made since previous snapshot: added setting reading timeout to socket based on document reading timemout added support for wolfssl and mbedtls libraries added timeout tracking for https removed adjustment on server weight before putting <a href="http://blog.dataparksearch.org/658" class="more-link">...continue reading<span class="screen-reader-text"> "dpsearch-4.54-2016-12-03"</span></a>]]></description>
										<content:encoded><![CDATA[<p>A new snapshot version of DataparkSearch Engine has been released. You can get it on <a href="https://drive.google.com/folderview?id=0B4LJSYsLtw_McTFUaU5mVW1ZRmc&usp=sharing#list">Google Drive</a> or on <a href="https://github.com/Maxime2/dataparksearch/releases/tag/4.54-2016-12-03">GitHub</a>.</p>
<p>Changes made since previous snapshot:</p>
<ul>
<li>added setting reading timeout to socket based on document reading timemout</li>
<li>added support for <a href="https://www.wolfssl.com/">wolfssl</a> and <a href="https://tls.mbed.org/">mbedtls</a> libraries</li>
<li>added timeout tracking for https</li>
<li>removed adjustment on server weight before putting url poprank into url data</li>
<li>fixed compilation without openssl</li>
<li>improved OpenSSL detection</li>
<li>added --enable-mcmodel option for configure</li>
<li>corrected compilation flags for threadless version of libdpsearch if no apache module selected to build</li>
<li>switched to CRYPTO_THREADID for OpenSSL 1.0.0 and above</li>
<li>minor fixes and updates</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/658/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>dpsearch-4.54-2016-10-26</title>
		<link>http://blog.dataparksearch.org/651</link>
					<comments>http://blog.dataparksearch.org/651#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Tue, 25 Oct 2016 23:43:54 +0000</pubDate>
				<category><![CDATA[DataparkSearch]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=651</guid>

					<description><![CDATA[A new snapshot version of DataparkSearch Engine has been released. You can get it on Google Drive or on GitHub. Changes made since previous one: Corrected SQL schema for MySQL5 Fixed crash on URLs with no schema specified New detection for Apache version Fixed crossword section construction p, option and input HTML tags can now <a href="http://blog.dataparksearch.org/651" class="more-link">...continue reading<span class="screen-reader-text"> "dpsearch-4.54-2016-10-26"</span></a>]]></description>
										<content:encoded><![CDATA[<p>A new snapshot version of DataparkSearch Engine has been released. You can get it on <a href="https://drive.google.com/folderview?id=0B4LJSYsLtw_McTFUaU5mVW1ZRmc&usp=sharing#list">Google Drive</a> or on <a href="https://github.com/Maxime2/dataparksearch/releases/tag/4.54-2016-10-26">GitHub</a>.</p>
<p>Changes made since previous one:</p>
<ul>
<li>Corrected SQL schema for MySQL5</li>
<li>Fixed crash on URLs with no schema specified</li>
<li>New detection for Apache version</li>
<li>Fixed crossword section construction</li>
<li>p, option and input HTML tags can now be a section</li>
<li>More fine sleeping on mutex lock failure</li>
<li>Fixed compilation on FreeBSD 10</li>
<li>Added 'Robots collect' command</li>
<li>Fixed crash if dt:minute limit specified</li>
<li>Do not process sitemaps for Server/Realm/Subnet commands with nofollow option specified</li>
<li>Some other minor fixes</li>
</ul>
<p>I am planning to retire the support for Apache 1.3 in future. Let me know if your are still using it.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/651/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>One more fix for AMP WordPress plugin</title>
		<link>http://blog.dataparksearch.org/640</link>
					<comments>http://blog.dataparksearch.org/640#comments</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Wed, 12 Oct 2016 22:51:58 +0000</pubDate>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=640</guid>

					<description><![CDATA[With the recent AMP update at Google you may notice increased number of AMP parsing errors in your search console. They look like The mandatory tag 'html ⚡ for top-level html' is missing or incorrect. Some plugins, e.g. Add Meta Tags, may alter language_attributes() using 'language_attributes' filter and adding XML-related attributes which are disallowed (see <a href="http://blog.dataparksearch.org/640" class="more-link">...continue reading<span class="screen-reader-text"> "One more fix for AMP WordPress plugin"</span></a>]]></description>
										<content:encoded><![CDATA[<p>With the recent AMP update at Google you may notice increased number of AMP parsing errors in your search console. They look like</p>
<pre><code><small>
The mandatory tag 'html &#x26a1; for top-level html' is missing or incorrect.
</small></code></pre>
<p>Some plugins, e.g. Add Meta Tags, may alter language_attributes() using 'language_attributes' filter and adding XML-related attributes which are disallowed (see <a href="https://www.ampproject.org/docs/reference/spec#required-markup">www.ampproject.org/docs/reference/spec#required-markup</a> ) and that causes the error mentioned above.</p>
<p>I have made a fix solving this problem and made pull request for WordPress AMP plugin, you may see it here:<br />
<a href="https://github.com/Automattic/amp-wp/pull/531">github.com/Automattic/amp-wp/pull/531</a></p>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/640/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Data structure for word relative cooccurence frequencies, counts and prefix tree</title>
		<link>http://blog.dataparksearch.org/632</link>
					<comments>http://blog.dataparksearch.org/632#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Sat, 08 Oct 2016 07:03:02 +0000</pubDate>
				<category><![CDATA[Algorithms]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=632</guid>

					<description><![CDATA[Trying to solve the task of calculating word cooccurrence relative frequencies fast, I have created an interesting data structure, which also allows to calculate counts for the first word in the pair to check; and it creates word prefix tree for the text processing, which can be used for further text analysis. The source code <a href="http://blog.dataparksearch.org/632" class="more-link">...continue reading<span class="screen-reader-text"> "Data structure for word relative cooccurence frequencies, counts and prefix tree"</span></a>]]></description>
										<content:encoded><![CDATA[<p>Trying to solve the task of calculating word cooccurrence relative frequencies fast, I have created an interesting data structure, which also allows to calculate counts for the first word in the pair to check; and it creates word prefix tree for the text processing, which can be used for further text analysis.</p>
<p>The source code is available on GitHub: <a href="https://github.com/Maxime2/cooccurrences">github.com/Maxime2/cooccurrences</a></p>
<p>When you execute make command you should see the following output:</p>
<pre><code>
cc -O3 -funsigned-char cooccur.c -o cooccur -lm

Example 1
./cooccur a.txt 2 &lt; a.in | tee a.out

Checking pair d e
Count:3  cocount:3
Relative frequency: 1.00

Checking pair a b
Count:3  cocount:1
Relative frequency: 0.33


Example 2
./cooccur b.txt 3 &lt; b.in | tee b.out

Checking pair a penny
Count:3  cocount:3
Relative frequency: 1.00

Checking pair penny earned
Count:4  cocount:1
Relative frequency: 0.25

</code></pre>
<p>The cooccur program takes two arguments: the filename of a text file to process and the window of words size to calculate relative frequencies within it. Then the program takes pairs of words from its standard input, one pair per line, to calculate count of appearance of the first word in the text processed and the cooccurrence count for the pair in that text. If the second word appears more than once in the window, only one appearance is counted.</p>
<p>Examples were taken here:</p>
<ul>
<li><a href="http://linguistics.stackexchange.com/a/3774">linguistics.stackexchange.com/a/3774</a></li>
<li><a href="https://iksinc.wordpress.com/tag/co-occurrence-matrix/">iksinc.wordpress.com/tag/co-occurrence-matrix/</a></li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/632/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Small fix for AMP WordPress plugin</title>
		<link>http://blog.dataparksearch.org/626</link>
					<comments>http://blog.dataparksearch.org/626#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Wed, 24 Aug 2016 01:07:30 +0000</pubDate>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[Wordpress]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=626</guid>

					<description><![CDATA[If you use AMP plugin for WordPress to make AMP (Accelerated Mobile Pages) version of your posts and have some troubles validating them on AMP validator, you may try this fix for AMP plugin to make those pages valid.]]></description>
										<content:encoded><![CDATA[<p>If you use <a href="https://wordpress.org/plugins/amp/">AMP plugin for WordPress</a> to make <a href="https://www.ampproject.org/">AMP (Accelerated Mobile Pages)</a> version of your posts and have some troubles validating them on <a href="https://validator.ampproject.org/">AMP validator</a>, you may try this <a href="https://github.com/Automattic/amp-wp/pull/449">fix for AMP plugin</a> to make those pages valid.</p>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/626/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Apache + YAJL</title>
		<link>http://blog.dataparksearch.org/620</link>
					<comments>http://blog.dataparksearch.org/620#respond</comments>
		
		<dc:creator><![CDATA[Maxime]]></dc:creator>
		<pubDate>Fri, 01 Jul 2016 02:33:29 +0000</pubDate>
				<category><![CDATA[Programming]]></category>
		<guid isPermaLink="false">http://blog.dataparksearch.org/?p=620</guid>

					<description><![CDATA[//github.com/Maxime2/stan-challenge - here on GitHub is my answer to Stan code challenge. It is an example how one can use SAX-like streaming parser inside an Apache module to process JSON with minimal delays. Custom made Apache module gives you some savings on request processing time by avoiding invocation of any interpreter to process the request <a href="http://blog.dataparksearch.org/620" class="more-link">...continue reading<span class="screen-reader-text"> "Apache + YAJL"</span></a>]]></description>
										<content:encoded><![CDATA[<p><a href="https://github.com/Maxime2/stan-challenge">//github.com/Maxime2/stan-challenge</a> - here on GitHub is my answer to Stan code challenge. It is an example how one can use SAX-like streaming parser inside an Apache module to process JSON with minimal delays.</p>
<p>Custom made Apache module gives you some savings on request processing time by avoiding invocation of any interpreter to process the request with any programming language (like PHP, Python or Go). The stream parser allows to start processing JSON as soon as the first buffer filled with data while the whole request is still in transmission. And again, as it is an Apache module, the response is starting to construct while request is processing (and still transmitting).</p>
<p><a><span style="color: red;">Red</span>&amp;<span style="color: blue;">Orange</span></a></p>
]]></content:encoded>
					
					<wfw:commentRss>http://blog.dataparksearch.org/620/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
