<?xml version="1.0" encoding="UTF-8"?>



<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <atom:link href="http://harmful.cat-v.org:80/Blog/index.rss" rel="self" type="application/rss+xml" />
        <title><![CDATA[cat -v]]></title>
        <link>http://harmful.cat-v.org:80/Blog/index.rss</link>
        <description><![CDATA[]]></description>
        <language>en-us</language>
        <generator><![CDATA[Tom Duff's rc, and Kris Maglione's clever hackery]]></generator>
<lastBuildDate>Mon, 13 Jan 2020 22:30:24 -0500</lastBuildDate>

        <item>
            <title><![CDATA[For tech-weary Midwest farmers, 40-year-old tractors now a hot commodity]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2020/01/13/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2020/01/13/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:18 -0400</pubDate>
            <description> &lt;blockquote&gt;&lt;p&gt;The other big draw of the older tractors is their lack of complex
technology.  Farmers prefer to fix what they can on the spot, or take
it to their mechanic and not have to spend tens of thousands of
dollars.&lt;/p&gt;

&lt;p&gt;“The newer machines, any time something breaks, you’ve got to have a
computer to fix it,” Stock said.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="http://m.startribune.com/for-tech-weary-midwest-farmers-40-year-old-tractors-now-a-hot-commodity/566737082/"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[bloomberg.com]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2019/05/07/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2019/05/07/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:17 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://plan9.stanleylieber.com/mothra/img/bloomberg.com.png" width="500"&gt;&lt;/p&gt;


&lt;p&gt;Read more &lt;a href="https://www.bloomberg.com/tosv2.htm"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Couldn't sign you in]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/11/13/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/11/13/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:17 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com:80/src/21128/img/small.1541081265.png" alt="Couldn't sign you in" /&gt;&lt;/p&gt;

&lt;p&gt;Read more &lt;a href="https://security.googleblog.com/2018/10/announcing-some-security-treats-to.html"&gt;here&lt;/a&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Microsoft acquires go get]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/06/04/1/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/06/04/1/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:16 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/20874/img/1528134162.jpg" alt="GitHub 365" /&gt;&lt;/p&gt;

&lt;p&gt;Read more &lt;a href="https://blogs.microsoft.com/blog/2018/06/04/microsoft-github-empowering-developers/"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Young Woman or Old Woman]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/06/04/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/06/04/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:16 -0400</pubDate>
            <description> &lt;p&gt;How Instagram&amp;rsquo;s algorithm works:&lt;/p&gt;

&lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/20873/img/small.1528118923.png" alt="Instagram algorithm" /&gt;&lt;/p&gt;

&lt;p&gt;Read more &lt;a href="https://techcrunch.com/2018/06/01/how-instagram-feed-works/"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[The UNIX Philosophy]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/05/31/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/05/31/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:16 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/20872/img/small.1527773532.png" alt="React" /&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[short story in one image]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/05/16/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/05/16/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:16 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/20816/img/small.1526478390.png" alt="hn" /&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Total Meltdown?]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/03/27/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/03/27/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:15 -0400</pubDate>
            <description> &lt;blockquote&gt;&lt;p&gt;Meet the Windows 7 Meltdown patch from January.  It stopped Meltdown
but opened up a vulnerability way worse &amp;hellip;  It allowed any process to
read the complete memory contents at gigabytes per second, oh - it was
possible to write to arbitrary memory as well.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="http://blog.frizk.net/2018/03/total-meltdown.html"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Don't get ripped off on an SXGA+ screen for your X61/X62]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2018/02/15/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2018/02/15/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:15 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/19251/img/small.1510191851.png" alt="THERE ARE MANY PANELS, BUT THIS ONE IS MINE" /&gt;&lt;/p&gt;

&lt;p&gt;ATTENTION THINKPAD MODDERS&lt;/p&gt;

&lt;p&gt;xiphmont reports:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Most &amp;lsquo;new&amp;rsquo; HV121P01-100 SXGA+ screens for sale on ebay, AliExpress,
etc, are neither genuine nor new.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="https://xiphmont.dreamwidth.org/90510.html"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[YOU WILL NOT UNDERSTAND THIS]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2017/11/16/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2017/11/16/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:14 -0400</pubDate>
            <description> &lt;p&gt;Your esteemed editor jettisons dead weight:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;This is my exit interview from social media.  Some of these “services”
I abandoned years ago.  Others I am still struggling to avoid.  From
experience, I assume that you, reader, will make it impossible for me
to remain ignorant of developments WRT: all of this garbage.  What all
of this garbage has in common is that it has all lately proven to be
surplus to requirements, and soon I will never voluntarily use any of
it ever again.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read the entire article &lt;a href="http://stanleylieber.com/2017/11/07/0/"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Update:&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;HN &lt;a href="https://news.ycombinator.com/item?id=15649499"&gt;disagrees&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[webshit weekly]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/12/08/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/12/08/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:14 -0400</pubDate>
            <description> &lt;p&gt;An annotated digest of the top &amp;ldquo;Hacker&amp;rdquo; &amp;ldquo;News&amp;rdquo; posts:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://n-gate.com"&gt;http://n-gate.com&lt;/a&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[8cc.vin: Pure Vim script C Compiler]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/10/20/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/10/20/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:13 -0400</pubDate>
            <description> &lt;blockquote&gt;&lt;p&gt;This is a Vim script port of 8cc built on ELVM.  In other words, this
is a complete C compiler written in Vim script.&lt;/p&gt;

&lt;p&gt;8cc is a nicely-written small C compiler for x86_64 Linux.  It&amp;rsquo;s
C11-aware and self-hosted.  ELVM is a Eso Lang Virtual Machine.  ELVM
customizes 8cc to emit its own intermediate representation, EIR as
frontend.  ELVM compiles C code into EIR via the frontend.  And then
translates EIR into various targets (Python, Ruby, C, BrainFxxk, Piet,
Befunge, Emacs Lisp, &amp;hellip;) in backend.  The architecture resembles
LLVM.  This presentation is a good stuff to know ELVM architecture
further (though in Japanese).&lt;/p&gt;

&lt;p&gt;ELVM can compile itself into various targets.  So I added a new &amp;lsquo;Vim
script&amp;rsquo; backend and use it to translate C code of 8cc into Vim script.&lt;/p&gt;

&lt;p&gt;Now 8cc.vim is written in pure Vim script.  8cc.vim consists of
frontend (customized 8cc) and backend (ELC).  It can compile C code
into Vim script.  And of course Vim can evaluate the generated Vim
script code.&lt;/p&gt;

&lt;p&gt;Note that this is a toy project. 8cc.vim is much much slower. It takes 824 (frontend: 430 +
backend: 396) seconds to compile the simplest putchar() program on MacBook Pro Early 2015 (2.7
GHz Intel Core i5). But actually it works!&lt;/p&gt;

&lt;p&gt;As VM runs on Vim script, 8cc.vim works on Linux, OS X and (hopefully) Windows.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="https://github.com/rhysd/8cc.vim"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Related]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/10/18/1/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/10/18/1/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:13 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/18521/img/1476834464.jpg" alt="JavaScript 2016" /&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[How it feels to learn JavaScript in 2016]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/10/18/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/10/18/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:13 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/18519/img/small.1476834219.png" alt="JavaScript" /&gt;&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;You know what.  I think we are done here.  Actually, I think I’m done.
I’m done with the web, I’m done with JavaScript altogether.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read the full article &lt;a href="https://hackernoon.com/how-it-feels-to-learn-javascript-in-2016-d3a717dd577f#.t3fn4vrpb"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[hello, world]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/09/12/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/09/12/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:11 -0400</pubDate>
            <description> &lt;p&gt;&lt;a href="http://img.stanleylieber.com/src/18329/img/1471204306.jpg" target="_b"&gt;&lt;img src="http://img.stanleylieber.com/src/18329/img/1471204306.jpg" width="600" border="0"&gt;&lt;/a&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[if you are confident no hackers are within 100 feet]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/07/02/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/07/02/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:12 -0400</pubDate>
            <description> &lt;p&gt;&lt;a href="http://img.stanleylieber.com/src/18230/img/1467485797.jpg" target="_b"&gt;&lt;img src="http://img.stanleylieber.com/src/18230/img/1467485797.jpg" border="0"&gt;&lt;/a&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Douglas Crockford]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/06/25/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/06/25/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:12 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/18213/img/1466912963.jpg"&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Five states of software development]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2016/06/22/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2016/06/22/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:12 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://img.stanleylieber.com/src/17523/img/1434993767.jpg"&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[emailreg.com]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/10/29/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/10/29/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:11 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://plan9.stanleylieber.com/mothra/img/emailreg.com.png"&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[OpenBSD]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/10/20/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/10/20/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:10 -0400</pubDate>
            <description> &lt;pre&gt;&lt;code&gt;CVSROOT:  /cvs
Module name:     src
Changes by:      deraadt@cvs.openbsd.org     2015/10/17 18:04:43

Modified files:
   sys/kern       : syscalls.master kern_pledge.c uipc_syscalls.c 
   sys/sys        : pledge.h proc.h socketvar.h 
   sys/netinet    : in_pcb.c 
   sys/netinet6   : in6_pcb.c 

Log message:
Add two new system calls: fbsocket() and fbconnect().  This creates a
SS_FACEBOOK tagged socket which has limited functionality (for example,
you cannot accept on them...)  The libc farmville will switch to using
these, therefore pledge can identify a facebook transaction better.
ok tedu guenther kettenis beck and others
&lt;/code&gt;&lt;/pre&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Google]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/10/19/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/10/19/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:09 -0400</pubDate>
            <description> &lt;p&gt;What&amp;rsquo;s harmful about Google?&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Anonymous 10/19/15 (Mon) 18:01:02 No. 416982&lt;/p&gt;

&lt;blockquote&gt;&lt;blockquote&gt;&lt;p&gt;416422&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;liking any corporation ever&lt;/p&gt;

&lt;p&gt;thinking a structure where key people are constantly replaced and
everyone has to fake doing good work to not get fired / replaced has
any stable identity&lt;/p&gt;

&lt;p&gt;but other than that Google has been pretty reliable and fair to their
users.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;okay, now fuck off.&lt;/p&gt;

&lt;p&gt;Google is just another corporation. The problem is lots of le geeks
fap about Google because it&amp;rsquo;s Super Innovative etc. The only useful
thing Google ever did was make a search engine that wasn&amp;rsquo;t buggy and
filled with annoying ads as the other ones. That was the in the early
2000s.&lt;/p&gt;

&lt;p&gt;But now all the search engines are pretty much the same. Also Bing*
actually has a feature to turn off safe search. Google slowly fazed
out that option and replaced it with some bullshit that turns off safe
search for your search if you add"porn" or some trigger word to your
search. Also Google used to like actually show pages that contain the
words you search. Now it just"knows what you mean" and pulls up some
completely irrelevant garbage almost every fucking time.&lt;/p&gt;

&lt;p&gt;Another innovation brought to you by Google is the prevelance of this
Recaptcha trash on every fucking page of the internet. Pretty much
half the time the captcha will be 3 numbers. The rest of the time it&amp;rsquo;s
either one of:&lt;/p&gt;

&lt;p&gt;o Picture captcha - select all 4 of the images with street signs, but
there are only actually 3 images with street signs here. Please repeat
the same scenario 3-15 more times so we can see that you aren&amp;rsquo;t a
robot. Similar scenarios with burgers and ice cream. Also note that
this captcha only appears when the I&amp;rsquo;m not a robot button failed (I&amp;rsquo;ve
never seen it &lt;em&gt;not&lt;/em&gt; fail&amp;hellip; even without tor and on Windows). The"I&amp;rsquo;m
not a robot" button is essentially DRM. You must have a conforming
browser so they can see that the series of input/output events looks
statistically like a human. The problem here is conforming browser
simply means Firefox, Chrome, or IE or one of the other big ones. You
cannot possibly make a browser from scratch and have it pass this
button test. If you can, it means the button test is trivial to
defeat. But I assume that&amp;rsquo;s not the case, and it relies on the
behavior of millions of lines of code in Firefox/Chrome/etc.&lt;/p&gt;

&lt;p&gt;o Nazi word captcha - Usually full of rnmrnrnmrnmrnmrnmr
uvuvuvuvuvuwuwvuwwvu etc. They succeed 99% of the time at building a
completely ambiguous string which your answer depends on which order
you read the characters in, whether you look ahead, the amount of time
you spend re-reading the captcha, the mood you&amp;rsquo;re in, etc. You are
almost guaranteed to fail this captcha unless you retry it like 15
times or it&amp;rsquo;s on fuzzy mode and it just accepts a string that&amp;rsquo;s
similar to the captcha shown (for example ul.to is on fuzzy mode for
some reason, I have no idea how this is activated or if google just
decides ul.to will have this mode activated for some reason).&lt;/p&gt;

&lt;p&gt;o They just block you depending on which tor exit node you use.
There&amp;rsquo;s nothing more ironic than blocking people from using your
captcha.&lt;/p&gt;

&lt;p&gt;Worse yet, Google seems to be the ones who started the fad of
requiring a cell phone to sign up to a fucking &lt;em&gt;website&lt;/em&gt;. And they
brought that cancer to youtube. Fuck that shit right off. I still have
a gmail account I registered before they switched to requiring cell
phone to sign up. It&amp;rsquo;s still annoying as fuck to use because they are
constantly threatening that they&amp;rsquo;re going to give someone my account
because they added secret question/cellphone/etc backdoor #35782357823
to my account or the XSS of the day (yes, Google routinely has XSS
vulns too, even trivial ones, despite that they are super leet haxors.
WTF do you expect? It&amp;rsquo;s a corporation and software companies are not
responsible for security errors - they can just appeal to"Security is
Hard" every time).&lt;/p&gt;

&lt;blockquote&gt;&lt;blockquote&gt;&lt;p&gt;416570&lt;/p&gt;&lt;/blockquote&gt;&lt;/blockquote&gt;

&lt;p&gt;The open source community is utter shit regardless.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;I&amp;rsquo;m not shilling Bing. Bing has a shitty UI for image search where
you have to wait for it to make remote requests before showing the
window that has the image and link to the page. This combiend with all
the animation bullshit inthe UI is incredibly annoying on my under
$1000 computer over tor. Also they used to use JS/popup to implement
the"view page containing this image" button, which was guaranteed to
be blocked as a popup, but they finally replaced that with a normal
link after years.&lt;/li&gt;
&lt;/ul&gt;
&lt;/blockquote&gt;

&lt;p&gt;Read more in the mostly lame &lt;a href="https://8ch.net/tech/res/416422.html#q416982"&gt;8ch thread&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[instagram]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/07/21/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/07/21/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:09 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://plan9.stanleylieber.com/mothra/img/instagram.png"&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Crashing iPad App Grounds Dozens of American Airline Flights]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/05/01/1/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/05/01/1/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:09 -0400</pubDate>
            <description> &lt;p&gt;Insanely great:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;American Airlines was forced to delay multiple flights on Tuesday
night after the iPad app used by pilots crashed.  Introduced in 2013,
the cockpit iPads are used as an &amp;ldquo;electronic flight bag,&amp;rdquo; replacing
16kg (35lb) of paper manuals which pilots are typically required to
carry on flights.  In some cases, the flights had to return to the
gate to access Wi-Fi to fix the issue.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="http://slashdot.feedsportal.com/c/35028/f/648022/s/45da07d8/sc/28/l/0Ltech0Bslashdot0Borg0Cstory0C150C0A40C290C12452230Ccrashing0Eipad0Eapp0Egrounds0Edozens0Eof0Eamerican0Eairline0Eflights0Dutm0Isource0Frss10B0Amainlinkanon0Gutm0Imedium0Ffeed/story01.htm"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Boeing advises periodically rebooting 787]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/05/01/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/05/01/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:08 -0400</pubDate>
            <description> &lt;blockquote&gt;&lt;p&gt;The US Federal Aviation Administration (FAA) has issued a new
airworthiness directive &lt;a href="https://s3.amazonaws.com/public-inspection.federalregister.gov/2015-10066.pdf"&gt;PDF&lt;/a&gt; for Boeing&amp;rsquo;s 787 because a software bug
shuts down the plane&amp;rsquo;s electricity generators every 248 days.&lt;/p&gt;

&lt;p&gt;“We have been advised by Boeing of an issue identified during
laboratory testing,” the directive says.  That issue sees “The
software counter internal to the generator control units (GCUs) will
overflow after 248 days of continuous power, causing that GCU to go
into failsafe mode.”&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="http://www.theregister.co.uk/2015/05/01/787_software_bug_can_shut_down_planes_generators/"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Everyone has JavaScript, right?]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/04/24/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/04/24/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:08 -0400</pubDate>
            <description> &lt;p&gt;From &lt;a href="http://kryogenix.org/code/browser/everyonehasjs.html"&gt;kryogenix.org&lt;/a&gt;:&lt;/p&gt;

&lt;dl&gt;
&lt;dt&gt;Your user requests your web app&lt;/dt&gt;

&lt;dt&gt;Has the page loaded yet?&lt;/dt&gt;
&lt;dd&gt;“All your users are non-JS while they're downloading your JS” — &lt;a href="https://t.co/uTM3255RuW"&gt;Jake Archibald&lt;/a&gt;&lt;/dd&gt;

&lt;dt&gt;Did the HTTP request for the JavaScript succeed?&lt;/dt&gt;
&lt;dd&gt;If they're on a train and their net connection goes away before your JavaScript loads, then there's no JavaScript.&lt;/dd&gt;

&lt;dt&gt;Did the HTTP request for the JavaScript complete?&lt;/dt&gt;
&lt;dd&gt;How many times have you had a mobile browser hang forever loading a page and then load it instantly when you refresh?&lt;/dd&gt;

&lt;dt&gt;Does the corporate firewall block JavaScript?&lt;/dt&gt;
&lt;dd&gt;Because loads of them still do.&lt;/dd&gt;

&lt;dt&gt;Does their ISP or mobile operator interfere with downloaded JavaScript?&lt;/dt&gt;
&lt;dd&gt;&lt;a href="http://www.theguardian.com/technology/2014/jan/28/sky-broadband-blocks-jquery-web-critical-plugin"&gt;Sky accidentally block jQuery&lt;/a&gt;, &lt;a href="http://aaron-gustafson.com/notebook/2014/the-network-effect/"&gt;Comcast insert ads into your script&lt;/a&gt;, and if you've never experienced this before, drive to an airport and use their wifi.&lt;/dd&gt;

&lt;dt&gt;Have they switched off JavaScript?&lt;/dt&gt;
&lt;dd&gt;People &lt;a href="https://gds.blog.gov.uk/2013/10/21/how-many-people-are-missing-out-on-javascript-enhancement/"&gt;still do&lt;/a&gt;.&lt;/dd&gt;

&lt;dt&gt;Do they have addons or plugins installed which inject script or alter the DOM in ways you didn't anticipate?&lt;/dt&gt;
&lt;dd&gt;There are thousands of browser extensions. Are you sure none interfere with your JS?&lt;/dd&gt;

&lt;dt&gt;Is the CDN up?&lt;/dt&gt;
&lt;dd&gt;CDNs are good at staying up (that’s what being a CDN &lt;em&gt;is&lt;/em&gt;) but &lt;a href="http://www.cdnperf.com/"&gt;a minute downtime a month&lt;/a&gt; will still hit users who browse in that minute.&lt;/dd&gt;

&lt;dt&gt;Does their browser support the JavaScript you’ve written?&lt;/dt&gt;
&lt;dd&gt;Check &lt;a href="http://caniuse.com/"&gt;Can I Use&lt;/a&gt; for browser usage figures.&lt;/dd&gt;

&lt;dt&gt;&lt;p&gt;Is all the above true?&lt;/p&gt;&lt;p&gt;Then yes, your JavaScript works.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Probably.&lt;/strong&gt;&lt;/p&gt;&lt;/dt&gt;
&lt;dd&gt;&lt;p&gt;&lt;a href="http://jakearchibald.com/2013/progressive-enhancement-still-important/"&gt;Progressive enhancement&lt;/a&gt;. Because sometimes your JavaScript just won’t work.&lt;/p&gt;
&lt;p&gt;Be prepared.&lt;/p&gt;&lt;/dd&gt;
&lt;/dl&gt;

 </description>
        </item>

        <item>
            <title><![CDATA[fizzbuzz]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/04/09/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/04/09/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:08 -0400</pubDate>
            <description> &lt;p&gt;Old, but it&amp;rsquo;s still what it is.&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Google won&amp;rsquo;t allow the co-inventor of Unix and the C language to
check-in code, because he won&amp;rsquo;t take the mandatory language test.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more &lt;a href="http://www.theregister.co.uk/2010/04/21/ken_thompson_take_our_test/"&gt;here&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Barely Metal]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/03/31/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/03/31/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:07 -0400</pubDate>
            <description> &lt;blockquote&gt;&lt;p&gt;Running on bare metal is being made possible in large part by
virtualisation technologies such as Xen which provide standard virtual
networking and file system interfaces.  These virtualised interfaces
mean that bare metal solutions don&amp;rsquo;t need hardware device driver
support, making the core concept much easier to implement.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more at &lt;a href="http://fourlightyears.blogspot.com.au/2015/03/bare-metal-application-builders-are.html"&gt;Not Constructive blog&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[Google Summer of Code 2015]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/03/02/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/03/02/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:07 -0400</pubDate>
            <description> &lt;p&gt;&lt;img src="http://plan9.stanleylieber.com/mothra/img/gsoc2015.png"&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[content, pt. 3]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/02/24/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/02/24/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:07 -0400</pubDate>
            <description> &lt;pre&gt;
; hget http://www.xojane.com/ | htmlfmt
; hget http://www.xojane.com/ | wc
    170     470    6699
;
&lt;/pre&gt;

 </description>
        </item>

        <item>
            <title><![CDATA[HTTP/2.0 — The IETF is Phoning It In]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2015/01/07/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2015/01/07/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:06 -0400</pubDate>
            <description> &lt;blockquote&gt;&lt;p&gt;Some will expect a major update to the world&amp;rsquo;s most popular protocol
to be a technical masterpiece and textbook example for future students
of protocol design.  Some will expect that a protocol designed during
the Snowden revelations will improve their privacy.  Others will more
cynically suspect the opposite.  There may be a general assumption of
&amp;ldquo;faster.&amp;rdquo; Many will probably also assume it is &amp;ldquo;greener.&amp;rdquo; And some of
us are jaded enough to see the &amp;ldquo;2.0&amp;rdquo; and mutter &amp;ldquo;Uh-oh, Second Systems
Syndrome.&amp;rdquo;&lt;/p&gt;

&lt;p&gt;The cheat sheet answers are: no, no, probably not, maybe, no and yes.&lt;/p&gt;

&lt;p&gt;If that sounds underwhelming, it&amp;rsquo;s because it is.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Read more at &lt;a href="http://queue.acm.org/detail.cfm?id=2716278"&gt;acmqueue&lt;/a&gt;.&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[To Wash It All Away]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2014/11/16/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2014/11/16/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:06 -0400</pubDate>
            <description> &lt;p&gt;James Mickens' classic rant (Usenix ;login, March 2014, p.2-8):&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;Describing why the Web is horrible is like describing why it&amp;rsquo;s horrible to drown in an ocean composed of pufferfish that are pregnant with Tiny Freddy Kruegers&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;Download the &lt;a href="https://www.usenix.org/system/files/1403_02-08_mickens.pdf"&gt;pdf&lt;/a&gt;&lt;/p&gt;
 </description>
        </item>

        <item>
            <title><![CDATA[this is why software sucks]]></title>
            <author><![CDATA[sl@noreply.cat-v.org (sl)]]></author>
            <link>http://harmful.cat-v.org:80/Blog/2014/07/23/0/</link>
            <guid isPermaLink="true">http://harmful.cat-v.org:80/Blog/2014/07/23/0/</guid>
            <pubDate>Wed, 06 Apr 2022 22:22:05 -0400</pubDate>
            <description> &lt;p&gt;&lt;a href="http://www.tedunangst.com/flak/post/this-is-why-software-sucks"&gt;Ted Unangst&amp;rsquo;s thoughts&lt;/a&gt; on recent develepmonts in the &lt;a href="http://www.libressl.org/"&gt;LibreSSL&lt;/a&gt; world:&lt;/p&gt;

&lt;blockquote&gt;&lt;p&gt;It&amp;rsquo;s been a week and change since the first LibreSSL portable
release was announced to much sturm und drang. I&amp;rsquo;m not directly
involved, but a few thoughts and reflections on the release and its
reception. (Deliberately missing some links; do your own digging if
you care.)&lt;/p&gt;

&lt;p&gt;Most people seemed pretty happy with the release. That was good. There
were a few portability wrinkles. They got fixed. That was good.&lt;/p&gt;

&lt;p&gt;Then there were the LibreSSL is an unsafe catastrophe fun times. My
earlier thoughts.&lt;/p&gt;

&lt;p&gt;Now what was missing was any mention of prior art. Like CVE-2013-1900.
Is PostgreSQL unsafe? Or CVE-2014-0017. Is stunnel unsafe? These are
real programs, presumably trying to be secure, with real exploits. Not
carefully crafted samples that aided in their own exploitation.
Perhaps it&amp;rsquo;s OpenSSL that&amp;rsquo;s unsafe? It&amp;rsquo;s not like OpenSSL
hasn&amp;rsquo;t had its own fixes for trouble with pid reuse.&lt;/p&gt;

&lt;p&gt;I don&amp;rsquo;t have much involvement in portable, but I definitely had a
hand in neutering the RAND and egd interfaces. Contrary to some
commentary, we didn&amp;rsquo;t neuter these interfaces because we didn&amp;rsquo;t
know what they were. We neutered them because we know precisely what
they are. They&amp;rsquo;re fucking stupid.&lt;/p&gt;

&lt;p&gt;The next turn of events was the notion that the getpid/atfork fixes
were then rushed out the door. It&amp;rsquo;s sad when &amp;ldquo;Bug fixed in timely
manner&amp;rdquo; is headline worthy news. It&amp;rsquo;s twisted when it&amp;rsquo;s spun as
something bad. What else should one do after receiving a bug report
via blog post via front page news? Sit on it? What purpose would that
serve? Or, phrased differently, what narrative does a delayed fix
facilitate?&lt;/p&gt;

&lt;p&gt;Finally came the report that the atfork fix was all wrong, which was
then edited to be rather less wrong. Hey, that&amp;rsquo;s ok, we all make
mistakes. I&amp;rsquo;m more disappointed with the chorus of tweeters and
sharers and likers who rushed to spread the bad news without
apparently reading or understanding it, simply because it slotted
nicely into the &amp;ldquo;wrong wrong wrong&amp;rdquo; story they had going.&lt;/p&gt;

&lt;p&gt;Not to say all criticism is unwarranted or unwelcome. Indeed, with
every release, Bob specifically asks for criticism, though I think he
calls it feedback.&lt;/p&gt;

&lt;p&gt;Whether for serious or for fun, phk and djb have each conjectured a
massive all encompassing conspiracy dedicated to maintaining the
status quo and preventing the development of secure software. I&amp;rsquo;m
not sure I believe in such a conspiracy, but I am certain that should
it exist, it could not possibly hope to be more disruptive. On the one
hand we have people claiming the OpenSSL API is too broken to work
with (they may have a point); on the other hand we have people
demanding that we maintain every last misfeature piece of shit
function in that API.&lt;/p&gt;

&lt;p&gt;Do you want software to stop being shit? Then stop expecting&amp;hellip; nay,
stop demanding that software be shit.&lt;/p&gt;&lt;/blockquote&gt;
 </description>
        </item>
    </channel>
</rss>

