<?xml version="1.0" encoding="UTF-8" ?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:base="http://everything2.com/">
    <title>OldMiner's New Writeups</title>
    <link rel="alternate" type="text/html" href="http://everything2.com/index.pl?node=Everything%20User%20Search&amp;usersearch=OldMiner" />
    <link rel="self" type="application/atom+xml" href="?node=New%20Writeups%20Atom%20Feed&amp;type=ticker&amp;foruser=OldMiner" />
    <id>http://everything2.com/?node=New%20Writeups%20Atom%20Feed&amp;foruser=OldMiner</id>
    <updated>2011-12-05T20:11:42Z</updated>
<entry><title>December 5, 2011 (log)</title><link rel="alternate" type="text/html" href="http://everything2.com/user/OldMiner/writeups/December+5%252C+2011"/><id>http://everything2.com/user/OldMiner/writeups/December+5%252C+2011</id><author><name>OldMiner</name><uri>http://everything2.com/user/OldMiner</uri></author><published>2011-12-05T20:11:42Z</published><updated>2011-12-05T20:11:42Z</updated>
<content type="html">&lt;p&gt;For those of you unaware, Everything2 came into existence because the company &lt;a href=&quot;/title/Blockstackers+Intergalactic&quot;&gt;Blockstackers Intergalactic&lt;/a&gt; was formed by &lt;a href=&quot;/user/nate&quot;&gt;nate&lt;/a&gt; and a few others, back in the dot com days.  They secured funding and put significant money into developing the software that runs E2, getting it (and its sister sites) machines, bandwidth, and taking care of its day to day needs.  As I understand it, the business intent of the company was to ultimately sell the software that runs Everything2 to companies who wished to use it to run their own sites.  The dot com crash put an end to that dream, and with it, any reliable funding for running E2.&lt;/p&gt;

&lt;p&gt;Since then, E2 has migrated to several different hosting locations, but remained the property of the mostly-defunct Blockstackers.  However, &lt;a href=&quot;http://cmdrtaco.net/2011/12/everything2-com-seeks-new-ownership/&quot;&gt;as has been posted publicly&lt;/a&gt;, Blockstackers (largely meaning &quot;&lt;a href=&quot;/user/nate&quot;&gt;nate&lt;/a&gt;&quot;) are looking to find someone more capable of being involved in the day-to-day operations of the&amp;hellip;</content>
</entry><entry><title>Rock Man (person)</title><link rel="alternate" type="text/html" href="http://everything2.com/user/OldMiner/writeups/Rock+Man"/><id>http://everything2.com/user/OldMiner/writeups/Rock+Man</id><author><name>OldMiner</name><uri>http://everything2.com/user/OldMiner</uri></author><published>2011-12-02T18:27:56Z</published><updated>2011-12-02T18:27:56Z</updated>
<content type="html">&lt;p&gt;As an overpowering culture of the world, the U.S. is often accused of &lt;a href=&quot;/title/Californication&quot;&gt;culture creep&lt;/a&gt;.Â  Throughout the world, one can find the influence of Hollywood on local media, U.S. pop culture &lt;a href=&quot;/title/loanword&quot;&gt;loanword&lt;/a&gt;s intermixed with local language, and &lt;a href=&quot;/title/Coca-Cola&quot;&gt;U.S. brands&lt;/a&gt; on local store shelves.Â  So it is only right that kids in the United States absorb the culture of another country secondhand.Â  Of course, I'm talking about Japan.&lt;/p&gt;
&lt;p&gt;However, this culture has always seen a bit of a translation barrier as it came over.Â  Not only is there the fact that &lt;a href=&quot;/title/Zero+Wing&quot;&gt;some translations&lt;/a&gt; are &lt;a href=&quot;/title/Engrish&quot;&gt;hilariously bad&lt;/a&gt; due lack of skill of the translater, often the folks directing the translation worry that U.S. audiences will not understand or will have their sensibilities offended by a direct translation.Â  This has resulted in such oddities as the alcohol often being turned into &lt;a href=&quot;http://tvtropes.org/pmwiki/pmwiki.php/Main/FrothyMugsOfWater&quot;&gt;coffee or milk&lt;/a&gt;, editing of&amp;hellip;</content>
</entry><entry><title>root log: November 2011 (log)</title><link rel="alternate" type="text/html" href="http://everything2.com/user/OldMiner/writeups/root+log%253A+November+2011"/><id>http://everything2.com/user/OldMiner/writeups/root+log%253A+November+2011</id><author><name>OldMiner</name><uri>http://everything2.com/user/OldMiner</uri></author><published>2011-11-29T03:06:33Z</published><updated>2011-11-29T03:06:33Z</updated>
<content type="html">&lt;h2&gt;Servers Asplode&lt;a href=&quot;/title/HEAD+ASPLODE&quot;&gt;!&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;
During November we have had some severe site responsiveness issues which were capped off, most recently, by the loss of one of the three main servers that power E2.Â  Although most of the hardware from that server has been recovered, its motherboard is fried, and so we are temporarily going to have to do without it.
&lt;/p&gt;
&lt;p&gt;
I appreciate that having the site slow or outright unavailable can be very frustrating.  I empathize.  I know many of you folks feel frustrated having a site you care about unavailable and being powerless to fix it.  The words of support I've gotten from folks thanking me for trying to get the site back on its feet have been quite heartening, and I thank you all for sending them.  I'm sorry I've not been able to get the site functioning better sooner.
&lt;/p&gt;
&lt;p&gt;
This situation isn't the best for anybody involved.  Although I am the most active person with regards to working with the server configuration, I would rather be spending more&amp;hellip;</content>
</entry><entry><title>October 15, 2011 (log)</title><link rel="alternate" type="text/html" href="http://everything2.com/user/OldMiner/writeups/October+15%252C+2011"/><id>http://everything2.com/user/OldMiner/writeups/October+15%252C+2011</id><author><name>OldMiner</name><uri>http://everything2.com/user/OldMiner</uri></author><published>2011-10-15T22:17:51Z</published><updated>2011-10-15T22:17:51Z</updated>
<content type="html">&lt;p&gt;
There have been a lot of people who have tried to figure out what the magic sauce was that made Wikipedia so popular.  &lt;a href=&quot;/user/Two+Sheds&quot;&gt;Two Sheds&lt;/a&gt; recently linked to this article &lt;a href=&quot;http://www.niemanlab.org/2011/10/the-contribution-conundrum-why-did-wikipedia-succeed-while-other-encyclopedias-failed/&quot;&gt;The contribution conundrum: Why did Wikipedia succeed while other encyclopedias failed?&lt;/a&gt;.  It mentioned E2 near the start, and implies we're a failed encyclopedia, which I guess I can get behind, because E2 was never meant to be an encyclopedia.
&lt;/p&gt;

&lt;p&gt;
E2 is intended to be a web of ideas, connected both by intentional direct links and by the naturally-arising web of softlinks that evolve as people travel about, linking knowledge, stories, and emotions together in a useful and sometimes-surprising web.  The intermeshing purposes of the content, both educating, entertaining, and exploring, entangle the people creating those links, and hence you find a community intertwined within the writing, making the content&amp;hellip;</content>
</entry><entry><title>E2 Bugs (thing)</title><link rel="alternate" type="text/html" href="http://everything2.com/user/OldMiner/writeups/E2+Bugs"/><id>http://everything2.com/user/OldMiner/writeups/E2+Bugs</id><author><name>OldMiner</name><uri>http://everything2.com/user/OldMiner</uri></author><published>2011-10-12T05:34:11Z</published><updated>2011-10-12T05:34:11Z</updated>
<content type="html">&lt;p&gt;
User &lt;a href=&quot;/user/Clockmaker&quot;&gt;Clockmaker&lt;/a&gt; reports that the &lt;a href=&quot;/title/My+Achievements&quot;&gt;achievement&lt;/a&gt; &quot;Printing Press&quot;, which is supposed to be awarded for writing more writeups than any other noder in a month, does not appear to function.  The code in question is located in &lt;a href=&quot;/title/writeupsMonthMost&quot;&gt;writeupsMonthMost&lt;/a&gt; and simply returns 0.  It was likely disabled after the switch to InnoDB, as aggregate statements, like the GROUP BY that was inevitably used, are far more expensive with row level locks.
&lt;/p&gt;
&lt;p&gt;
This should be a monthly cron job (or implemented, equivalently, in a nodelet) which queries all writeups published in a month grouped by publisher_id, finds if there's a clear winner (SELECT COUNT(node_id) 'num_published' ... ORDER BY num_published LIMIT 2, if the two num_published don't match, there's a winner; or do something more complex to award to all people who tie for most that month), and awards the achievement appropriately.  This is a good candidate to use the slave MySQL DB since stale data is unlikely to have an effect.
&lt;/p&gt;
&lt;hr&gt;
&amp;hellip;</content>
</entry><entry><title>September 29, 2011 (log)</title><link rel="alternate" type="text/html" href="http://everything2.com/user/OldMiner/writeups/September+29%252C+2011"/><id>http://everything2.com/user/OldMiner/writeups/September+29%252C+2011</id><author><name>OldMiner</name><uri>http://everything2.com/user/OldMiner</uri></author><published>2011-09-30T04:16:15Z</published><updated>2011-09-30T04:16:15Z</updated>
<content type="html">&lt;h2&gt;A Consideration of Comments on Writeups

&lt;h3&gt;Preface&lt;/h3&gt;

&lt;p&gt;
We're all discussing a proposed feature which isn't coded, but is easier than you might think to implement.  As such, don't freak out because we're doing something horrible.  We're just talking.  But please feel free to add your voice if this idea horrifies you.  Because it still &lt;strong&gt;might&lt;/strong&gt; be a reality, and it'd be best if we addressed everyone's concerns to &lt;a href=&quot;/title/Candide&quot;&gt;make it the best reality it can be&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
To me, the point of adding discussions is to encourage feedback and increase interaction.  It falls somewhere between the public catbox and long form writeups; and it potentially provides a place for something that presently has no sanctioned place on the site: long-form criticism or discussion of a writeup.  Although the &quot;blab&quot; box was already created to encourage feedback, it doesn't fulfill this need as well as it could because: (1) its intent (to message the writeup's author) is not clear to many, (2)&lt;/h2&gt;&amp;hellip;</content>
</entry></feed>
