Moderation Log

Date/Time Moderator Story/Comment/User, Action, Reason
2018-12-08 12:33 -0600 (Users) User Student
Action: changed own username from "marcintustin" to "Student"
2018-12-08 08:30 -0600 (Users) User spacejam
Action: changed own username from "icefall" to "spacejam"
2018-12-07 21:33 -0600 pushcx Story: Why Systolic Architectures? (1982)
Action: changed title from "Why Systolic Architectures?" to "Why Systolic Architectures? (1982)"
Reason: Adding year
2018-12-07 20:06 -0600 pushcx Story: EdgeHTML: a bad demise nobody much noticed
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Merging hot take into article.
2018-12-07 19:49 -0600 pushcx Story: The Death of Edge
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Merging hot take into article.
2018-12-07 17:22 -0600 pushcx Story: Don't use the greater than sign in programming
Action: changed description from "I came across this article just now, but I independently discovered the joys of only using `<=` and `<` a few years ago, after cleaning up a bit too much code that looked something like this:\r\n\r\n if days_so_far > max_days:\r\n ...\r\n if days_so_far < max_days and days_so_far > (max_days - 7):\r\n ...\r\n\r\nMerely rewriting that to use `<`, so that the variables appeared in order of size, was a huge relief:\r\n\r\n if (max_days - 7) < days_so_far and days_so_far < max_days and:\r\n ...\r\n if max_days < days_so_far:\r\n ...\r\n\r\nLlewelyn's article is the first time I've seen someone else give this advice -- so hooray, I'm not alone! \r\n\r\nWhy I like it only using `<` and `<=`: when the `<` marks all point the same way, the numbers and variables always go from small to large, and it makes it easier to mentally move the `(a < b)` expressions around and place them next to each other and see which conditions cover which bits of the number line. Especially when there are multiple comparisons involved.\r\n\r\nThe only case where I'm still tempted to use the greater-than sign is when it really is just a single comparison. \r\n`if 2 <= sys.argv` still feels like a weird way to say \"`sys.argv is at least 2`\"... not that `>=` or 'greater or equal than' is a great way to say 'at least'.\r\n\r\n([Previous submission & discussion](https://lobste.rs/s/m0mwqr/don_t_use_greater_than_sign_programming))" to "", changed markeddown_description from "<p>I came across this article just now, but I independently discovered the joys of only using <code>&lt;=</code> and <code>&lt;</code> a few years ago, after cleaning up a bit too much code that looked something like this:</p>\n<pre><code>if days_so_far &gt; max_days:\n ...\nif days_so_far &lt; max_days and days_so_far &gt; (max_days - 7):\n ...\n</code></pre>\n<p>Merely rewriting that to use <code>&lt;</code>, so that the variables appeared in order of size, was a huge relief:</p>\n<pre><code>if (max_days - 7) &lt; days_so_far and days_so_far &lt; max_days and:\n ...\nif max_days &lt; days_so_far:\n ...\n</code></pre>\n<p>Llewelyn’s article is the first time I’ve seen someone else give this advice – so hooray, I’m not alone!</p>\n<p>Why I like it only using <code>&lt;</code> and <code>&lt;=</code>: when the <code>&lt;</code> marks all point the same way, the numbers and variables always go from small to large, and it makes it easier to mentally move the <code>(a &lt; b)</code> expressions around and place them next to each other and see which conditions cover which bits of the number line. Especially when there are multiple comparisons involved.</p>\n<p>The only case where I’m still tempted to use the greater-than sign is when it really is just a single comparison.<br>\n<code>if 2 &lt;= sys.argv</code> still feels like a weird way to say “<code>sys.argv is at least 2</code>”… not that <code>&gt;=</code> or ‘greater or equal than’ is a great way to say ‘at least’.</p>\n<p>(<a href=\"https://lobste.rs/s/m0mwqr/don_t_use_greater_than_sign_programming\" rel=\"nofollow\">Previous submission &amp; discussion</a>)</p>\n" to ""
Reason: Please don't use the story text for personal comments. Mailed you a copy to post as a comment.
2018-12-07 13:50 -0600 (Users) User felselva
Action: changed own username from "ferreiradaselva" to "felselva"
2018-12-07 09:37 -0600 pushcx Story: Microsoft Edge: Making the web better through more open source collaboration
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Already posted.
2018-12-07 09:37 -0600 pushcx Story: Goodbye, EdgeHTML
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Already posted.
2018-12-06 23:14 -0600 pushcx Story: Mozilla CEO: Goodbye, EdgeHTML
Action: deleted story
Reason: Already posted in the comments of the thread your other story was merged into. Please stop submitting dupes.
2018-12-06 11:40 -0600 pushcx Story: While we Blink, we lose the Web
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Hot take/dupe roundup. Please check and post comments when you see existing stories, folks.
2018-12-06 11:40 -0600 pushcx Story: The State of Web Browsers
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Hot take/dupe roundup. Please check and post comments when you see existing stories, folks.
2018-12-06 11:40 -0600 pushcx Story: Microsoft Edge: Making the web better through more open source collaboration
Action: merged into zwrts3 (Microsoft is building a Chromium-powered web browser for Windows 10)
Reason: Hot take/dupe roundup. Please check and post comments when you see existing stories, folks.
2018-12-04 12:27 -0600 pushcx Story: Announcing .NET Core 3 Preview 1 and Open Sourcing Windows Desktop Frameworks
Action: merged into oclua5 (Announcing Open Source of WPF, Windows Forms, and WinUI at Microsoft Connect(); 2018)
Reason: Merging into earlier submission.
2018-12-04 06:56 -0600 pushcx Story: The True Cost of Commuting (2011)
Action: deleted story
Reason: Article is not about computing.
2018-12-04 06:14 -0600 (Users) Story: POLA Would Have Prevented the Event-Stream Incident
Action: changed tags from "security cryptocurrencies nodejs" to "security nodejs"
Reason: Automatically changed from user suggestions
2018-12-03 21:11 -0600 pushcx Story: Quora Security Update
Action: changed title from "Quora Security Update - The Quora Blog - Quora" to "Quora Security Update"
Reason: Please remove extraneous components from titles such as the name of the site and the name of the site.
2018-12-03 19:12 -0600 alynpost User teknoraver
Action: Granted hat "Red Hat employee" (https://developers.redhat.com/blog/author/mcroce/)
2018-12-03 10:44 -0600 (Users) Story: Two Books
Action: changed tags from "book objectivec" to "book"
Reason: Automatically changed from user suggestions
2018-12-02 13:25 -0600 pushcx Story: Here are the most interesting developer podcasts — 2019 edition
Action: deleted story
Reason: Please don't link newsletters and other aggregations; Lobsters is already a link aggregator. Submit the individual links to avoid overflowing the stack.
2018-12-02 13:20 -0600 pushcx Comment by pushcx on Blockchain for International Development: Using a Learning Agenda to Address Knowledge Gaps
Action: used Sysop hat
2018-12-02 13:18 -0600 pushcx Story: Blockchain for International Development: Using a Learning Agenda to Address Knowledge Gaps
Action: changed url from "https://www.theregister.co.uk/2018/11/30/blockchain_study_finds_0_per_cent_success_rate/" to "http://merltech.org/blockchain-for-international-development-using-a-learning-agenda-to-address-knowledge-gaps/", changed title from "Blockchain study finds 0.00% success rate and vendors don't call back when asked for evidence" to "Blockchain for International Development: Using a Learning Agenda to Address Knowledge Gaps", changed description from "" to "Mod replaced original link [Blockchain study finds 0.00% success rate and vendors don't call back when asked for evidence](https://www.theregister.co.uk/2018/11/30/blockchain_study_finds_0_per_cent_success_rate/) with primary source.", changed markeddown_description from "" to "<p>Mod replaced original link <a href=\"https://www.theregister.co.uk/2018/11/30/blockchain_study_finds_0_per_cent_success_rate/\" rel=\"nofollow\">Blockchain study finds 0.00% success rate and vendors don’t call back when asked for evidence</a> with primary source.</p>\n"
Reason: Replacing clickbait writeup with primary source.
2018-12-01 11:43 -0600 pushcx Story: The Hard Parts of Open Source
Action: changed title from "\"The Hard Parts of Open Source\" (Evan Czaplicki)" to "The Hard Parts of Open Source"
Reason: Please don't include speaker names in story titles.
2018-11-30 16:28 -0600 kyle Story: The Road to RSS 3.0 (2002)
Action: changed title from "The Road to RSS 3.0" to "The Road to RSS 3.0 (2002)"
Reason: Changed from user suggestions.
2018-11-29 22:23 -0600 (Users) Story: Bullshit Jobs excerpt about Open Source projects
Action: changed title from "Bulshit Jobs excerpt about Open Source projects" to "Bullshit Jobs excerpt about Open Source projects"
Reason: Automatically changed from user suggestions
2018-11-29 16:33 -0600 alynpost Comment by Sirikon on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:33 -0600 alynpost Comment by pgeorgi on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:32 -0600 alynpost Comment by nebkor on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:32 -0600 alynpost Comment by markos on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:31 -0600 alynpost Comment by gerikson on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:31 -0600 alynpost Comment by femiagbabiaka on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:31 -0600 alynpost Comment by Yetanfou on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:30 -0600 alynpost Comment by gerikson on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:29 -0600 alynpost Comment by zge on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:29 -0600 alynpost Comment by Yetanfou on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:29 -0600 alynpost Comment by rs86 on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 16:29 -0600 alynpost Comment by Hail_Spacecake on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread. This should have been done earlier. I misjudged the thread level.
2018-11-29 13:28 -0600 pushcx Story: From Datacenter Applications to Planetary Scale Applications
Action: changed title from "Keynote: Distributed Erlang: From Datacenter Applications to Planetary Scale Applications" to "From Datacenter Applications to Planetary Scale Applications"
Reason: Editing to match talk title + tag `erlang`.
2018-11-29 11:17 -0600 (Users) Story: The "high-level CPU" challenge (2008)
Action: changed title from "The \"high-level CPU\" challenge" to "The \"high-level CPU\" challenge (2008)"
Reason: Automatically changed from user suggestions
2018-11-28 20:47 -0600 (Users) Story: Perchance to Scheme (2016)
Action: changed title from "Perchance to Scheme (2006)" to "Perchance to Scheme (2016)"
Reason: Automatically changed from user suggestions
2018-11-28 19:09 -0600 (Users) Story: Perchance to Scheme (2016)
Action: changed title from "Perchance to Scheme" to "Perchance to Scheme (2006)"
Reason: Automatically changed from user suggestions
2018-11-28 09:06 -0600 pushcx Story: Bulshit Jobs - excerpt about Open Source projects
Action: deleted story
Reason: Please leave a comment to respond to the npm story rather than post a story. I'm PMing you your transcription in case you don't have a copy.
2018-11-28 04:56 -0600 alynpost Story: How to Deal with Difficult People on Software Projects
Action: merged into 9jnqcx (How to Deal with Difficult People on Software Projects)
2018-11-27 19:51 -0600 pushcx Comment by Sirikon on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Pruning inappropriate thread.
2018-11-27 19:50 -0600 pushcx Comment by nebkor on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: Stop calling for violence. Last warning.
2018-11-27 19:26 -0600 alynpost Comment by zacstewart on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: pruning off-topic thread.
2018-11-27 19:26 -0600 alynpost Comment by nebkor on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: pruning off-topic thread.
2018-11-27 19:26 -0600 alynpost Comment by notriddle on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: pruning off-topic thread.
2018-11-27 19:25 -0600 alynpost Comment by nebkor on We are Google employees. Google must drop Dragonfly
Action: deleted comment
Reason: your preference on the matter is off-topic here.
2018-11-27 13:15 -0600 pushcx Story: Robust Website Fingerprinting Through the Cache Occupancy Channel
Action: merged into 1lul8h (Robust Website Fingerprinting Through the Cache Occupancy Channel)
Reason: Merging dupe.