Moderation Log

Date/Time Moderator Story/Comment/User, Action, Reason
2018-05-06 11:18 -0500 pushcx Story: Crisis at Void Linux as Lead Developer Goes Missing in Action
Action: merged into tvilj4 (Serious Issues in Void Linux project)
Reason: Merging into the primary source.
2018-05-05 00:23 -0500 pushcx Story: Chris Lattner on "I am leaving LLVM"
Action: merged into nf3xgg (I am leaving LLVM)
Reason: Merging into same story posted yesterday.
2018-05-04 19:52 -0500 (Users) Story: Questionnaire which every programmer should fill in
Action: changed title from "Questionair which every programmer should fill in" to "Questionnaire which every programmer should fill in"
Reason: Automatically changed from user suggestions
2018-05-04 17:59 -0500 pushcx Story: What are the top takeaways of graph theory?
Action: changed title from "Ask: What are the top takeaways of graph theory?" to "What are the top takeaways of graph theory?"
Reason: The `ask` tag is colored to stand out, you don't need to include "Ask" in the title.
2018-05-04 17:50 -0500 pushcx Story: Favorite code editor with strong security practices?
Action: changed title from "Ask L: Favorite code editor with strong security practices?" to "Favorite code editor with strong security practices?"
Reason: The `ask` tag is colored to stand out, you don't need to include "Ask" in the title.
2018-05-04 08:51 -0500 pushcx Story: When mutability bites
Action: changed title from "When mutability bites – Chris Davies" to "When mutability bites"
Reason: Please don't include authors in story titles.
2018-05-03 12:40 -0500 pushcx Story: on false equivalences
Action: deleted story
Reason: This is about politics and rhetoric rather than computing. If you're responding to something about the llvm/CoC thread, please write a comment there with a link.
2018-05-03 11:47 -0500 pushcx Comment by pushcx on I am leaving LLVM
Action: used Sysop hat
2018-05-03 08:15 -0500 pushcx Comment by isra17 on I am leaving LLVM
Action: deleted comment
Reason: This is the kind of uncharitable post that leads to flamewars. You can make this points without reading the worst into his comment and character, because even if your worst assumptions are right your comment would be better in every way without the word "you".
2018-05-03 07:58 -0500 pushcx Comment by pushcx on I am leaving LLVM
Action: used Sysop hat
2018-05-03 00:12 -0500 (Users) Story: What conferences are you attending this year?
Action: changed tags from "event" to "event ask"
Reason: Automatically changed from user suggestions
2018-05-02 23:16 -0500 (Users) Story: GCC 8.1 Released
Action: changed tags from "c c++" to "c c++ release"
Reason: Automatically changed from user suggestions
2018-05-02 10:36 -0500 (Users) Story: 🏎Create fake REST API in one sec.
Action: changed tags from "go api" to "go api show"
Reason: Automatically changed from user suggestions
2018-05-01 19:21 -0500 (Users) Story: Native Code Performance and Memory: The Elephant in the CPU
Action: changed tags from "performance" to "performance video"
Reason: Automatically changed from user suggestions
2018-05-01 18:35 -0500 (Users) Story: Painting made out of CSS rules
Action: changed tags from "web css" to "web css art"
Reason: Automatically changed from user suggestions
2018-05-01 10:32 -0500 pushcx Story: “Fake news”: reaction to the end of the monopoly on the narrative
Action: deleted story
Reason: This article is about politics and media, not tech.
2018-05-01 09:30 -0500 (Users) Story: How the C Programming Language Was Created And What Was Forgotten As a Result
Action: changed tags from "event video c" to "video c historical"
Reason: Automatically changed from user suggestions
2018-04-30 15:34 -0500 pushcx Story: ‘Who the hell is this person?’ Trump’s Mar-a-Lago pal stymies VA project
Action: deleted story
Reason: The technical aspects of this system would be on topic, but the political manuevering is not.
2018-04-28 11:26 -0500 (Users) Story: The NetHack DevTeam is happy to announce the release of NetHack 3.6.1
Action: changed tags from "c games historical" to "c games"
Reason: Automatically changed from user suggestions
2018-04-27 08:32 -0500 (Users) Story: Go's New Brand
Action: changed tags from "go" to "go design"
Reason: Automatically changed from user suggestions
2018-04-26 17:29 -0500 pushcx Story: Ubuntu 18.04 LTS is finally released and is available for download now
Action: merged into zq6tb6 (In Beaver We Trust: A Lengthy, Pedantic Review of Ubuntu 18.04 LTS)
Reason: Merging into earlier submission of same event.
2018-04-26 14:46 -0500 pushcx Story: Fuzzy finding everything with fzf
Action: changed title from "Weekly Command: Fuzzy finding everything with fzf" to "Fuzzy finding everything with fzf"
Reason: Please don't include site/blog titles in story titles.
2018-04-26 09:36 -0500 pushcx Story: What happened to distributed programming languages?
Action: changed title from "What happened to distributed programming languages? by Heather Miller" to "What happened to distributed programming languages?"
Reason: Please remove speaker names from talk titles.
2018-04-25 08:18 -0500 pushcx Story: Program Reduction: A Win for Recursion Schemes
Action: changed url from "https://newartisans.com/2018/04/win-for-recursion-schemes/" to "http://newartisans.com/2018/04/win-for-recursion-schemes/"
Reason: Fixing link.
2018-04-25 08:11 -0500 pushcx Story: Program Reduction: A Win for Recursion Schemes
Action: changed url from "http://newartisans.com/" to "https://newartisans.com/2018/04/win-for-recursion-schemes/"
Reason: Fixing ilnk.
2018-04-25 07:07 -0500 pushcx Story: Transcript of Russ Cox Interview on GoTime
Action: changed tags from "go" to "go transcript"
2018-04-24 15:49 -0500 pushcx Story: Hackers emptied Ethereum wallets by breaking the basic infrastructure of the internet
Action: merged into lbr7j4 (Hijack of Amazon’s internet domain service used to reroute web traffic for two hours unnoticed)
Reason: Merging into same story.
2018-04-24 05:56 -0500 pushcx Comment by michaelochurch on Up or out: tech company leveling and mandatory promotions
Action: deleted comment
Reason: Please don't use bizarre pornographic obscenities to describe business practices.
2018-04-23 17:35 -0500 pushcx Story: Facebook, Politics and Orwell's 24/7 Hate
Action: deleted story
Reason: This post is about American politics and media, not technology.
2018-04-23 11:30 -0500 pushcx Story: Running my own git server
Action: changed description from "How I started my move away from hosted services to my own OpenBSD server, starting with git. Hopefully more stories to come as I move more things onto my server" to "", changed markeddown_description from "<p>How I started my move away from hosted services to my own OpenBSD server, starting with git. Hopefully more stories to come as I move more things onto my server</p>\n" to ""
Reason: Removing redundant description.
2018-04-22 20:53 -0500 (Users) Story: Beginner Friendly Gentoo Based Sabayon Linux Has a New Release
Action: changed tags from "linux" to "linux release"
Reason: Automatically changed from user suggestions
2018-04-21 11:38 -0500 (Users) Story: A peek inside Docker for Mac (Hyperkit, wait xhyve, no bhyve …)
Action: changed title from "A peek inside Docker for Mac (Hyperkit, wait xhyve, no bhyve …) – the BSD box" to "A peek inside Docker for Mac (Hyperkit, wait xhyve, no bhyve …)", changed tags from "virtualization" to "virtualization freebsd mac"
Reason: Automatically changed from user suggestions
2018-04-20 17:40 -0500 (Users) Story: Why I'm declining funding from Ruby Together
Action: changed tags from "ruby" to "ruby culture"
Reason: Automatically changed from user suggestions
2018-04-19 15:46 -0500 pushcx Story: Unblocking Telegram - Russia, shame on you! Censorship is lame.
Action: changed title from "Unblocking Telegram - Russia, shame on you! Censorship is lame. - 0xCC.re Blogs" to "Unblocking Telegram - Russia, shame on you! Censorship is lame."
Reason: Please remove blog names from titles.
2018-04-19 15:20 -0500 pushcx Story: BAN.AI's Public Access Multics System
Action: changed description from "My effort to provide and maintain a large public access system capable of supporting a community, in the spirit of the LCM TD-2 / SDF Twenex TOPS-20, ELVIRA RSTS/E at Stacken, Jim Wilcoxson's PRIRUN PRIMOS, the Cyber1 CDC system, the old Deathrow VMScluster, etc. \r\n\r\nI'll be making a more serious web page with some additional technical details soon. For those here who are interested, the system is based on the Honeywell DPS-8/M virtual machine emulator which is running on OpenBSD. Performance is somewhat faster than a similarly configured hardware site, and should comfortably support *many* users, with *many* *thousands* of users in the future once multiprocessing support has stabilized. \r\n\r\nSpecial thanks to all the Multicians, including but not limited to Tom Van Vleck, Harry Reed, Olin Sibert, Daiyu Hurst, Gary Dixon, Michael Mondy, and especially Charles Anthony and Eric Swenson for many late nights [pouring](http://www.ultimate.com/phil/pdp10/wizard.gif) over code and documentation, diagnosing problems, and basically rediscovering (and properly documenting) the tricks, processes, and methods for tuning Multics performance and stability for a particular site - many bugs were fixed along the way. It took a lot of effort to get from a clean slate to something I'd be comfortable making publicly available, and I'd never have been able to do it on my own.\r\n\r\nMuch of necessary lore was simply never passed down from Honeywell installers to the users or managers of these systems because of just how much there is to know, and the historical separation of duties between sales, installation, field engineering, site administration, system operators, and end users. \r\n\r\nAl Kossow of the Computer History Museum and Tom Van Vleck of the Multicians Archive deserve major and extra thanks for their tireless work in cataloging and preserving so much history that would otherwise be lost. This sort of publicly accessible site simply wouldn't be a possibility if the necessary manuals were not preserved. It's likely even the emulation would never have been completed without the preservation efforts preceding it.\r\n\r\n**NOTE**: If you experience any issue after being connected to a line, such as the system not echoing characters, not being responsive to input, etc, just disconnect and reconnect to the system and you should get the next available HSLA line. I'm still working out a few issues with the virtualized front-end terminal servers and the emulated mainframe FNP. \r\n\r\nFeel free to register for an account - in addition to a user directory and being able to participate in mail and forums, you'll be able to set a plan file for the finger daemon now and serve your own gopherspace soon. Also," to "My effort to provide and maintain a large public access system capable of supporting a community, in the spirit of the LCM TD-2 / SDF Twenex TOPS-20, ELVIRA RSTS/E at Stacken, Jim Wilcoxson's PRIRUN PRIMOS, the Cyber1 CDC system, the old Deathrow VMScluster, etc. \r\n\r\nI'll be making a more serious web page with some additional technical details soon. For those here who are interested, the system is based on the Honeywell DPS-8/M virtual machine emulator which is running on OpenBSD. Performance is somewhat faster than a similarly configured hardware site, and should comfortably support *many* users, with *many* *thousands* of users in the future once multiprocessing support has stabilized. \r\n\r\nSpecial thanks to all the Multicians, including but not limited to Tom Van Vleck, Harry Reed, Olin Sibert, Daiyu Hurst, Gary Dixon, Michael Mondy, and especially Charles Anthony and Eric Swenson for many late nights [pouring](http://www.ultimate.com/phil/pdp10/wizard.gif) over code and documentation, diagnosing problems, and basically rediscovering (and properly documenting) the tricks, processes, and methods for tuning Multics performance and stability for a particular site - many bugs were fixed along the way. It took a lot of effort to get from a clean slate to something I'd be comfortable making publicly available, and I'd never have been able to do it on my own.\r\n\r\nMuch of necessary lore was simply never passed down from Honeywell installers to the users or managers of these systems because of just how much there is to know, and the historical separation of duties between sales, installation, field engineering, site administration, system operators, and end users. \r\n\r\nAl Kossow of the Computer History Museum and Tom Van Vleck of the Multicians Archive deserve major and extra thanks for their tireless work in cataloging and preserving so much history that would otherwise be lost. This sort of publicly accessible site simply wouldn't be a possibility if the necessary manuals were not preserved. It's likely even the emulation would never have been completed without the preservation efforts preceding it.\r\n\r\n**NOTE**: If you experience any issue after being connected to a line, such as the system not echoing characters, not being responsive to input, etc, just disconnect and reconnect to the system and you should get the next available HSLA line. I'm still working out a few issues with the virtualized front-end terminal servers and the emulated mainframe FNP. \r\n\r\nFeel free to register for an account - in addition to a user directory and being able to participate in mail and forums, you'll be able to set a plan file for the finger daemon now and serve your own gopherspace soon.", changed markeddown_description from "<p>My effort to provide and maintain a large public access system capable of supporting a community, in the spirit of the LCM TD-2 / SDF Twenex TOPS-20, ELVIRA RSTS/E at Stacken, Jim Wilcoxson’s PRIRUN PRIMOS, the Cyber1 CDC system, the old Deathrow VMScluster, etc.</p>\n<p>I’ll be making a more serious web page with some additional technical details soon. For those here who are interested, the system is based on the Honeywell DPS-8/M virtual machine emulator which is running on OpenBSD. Performance is somewhat faster than a similarly configured hardware site, and should comfortably support <em>many</em> users, with <em>many</em> <em>thousands</em> of users in the future once multiprocessing support has stabilized.</p>\n<p>Special thanks to all the Multicians, including but not limited to Tom Van Vleck, Harry Reed, Olin Sibert, Daiyu Hurst, Gary Dixon, Michael Mondy, and especially Charles Anthony and Eric Swenson for many late nights <a href=\"http://www.ultimate.com/phil/pdp10/wizard.gif\" rel=\"nofollow\">pouring</a> over code and documentation, diagnosing problems, and basically rediscovering (and properly documenting) the tricks, processes, and methods for tuning Multics performance and stability for a particular site - many bugs were fixed along the way. It took a lot of effort to get from a clean slate to something I’d be comfortable making publicly available, and I’d never have been able to do it on my own.</p>\n<p>Much of necessary lore was simply never passed down from Honeywell installers to the users or managers of these systems because of just how much there is to know, and the historical separation of duties between sales, installation, field engineering, site administration, system operators, and end users.</p>\n<p>Al Kossow of the Computer History Museum and Tom Van Vleck of the Multicians Archive deserve major and extra thanks for their tireless work in cataloging and preserving so much history that would otherwise be lost. This sort of publicly accessible site simply wouldn’t be a possibility if the necessary manuals were not preserved. It’s likely even the emulation would never have been completed without the preservation efforts preceding it.</p>\n<p><strong>NOTE</strong>: If you experience any issue after being connected to a line, such as the system not echoing characters, not being responsive to input, etc, just disconnect and reconnect to the system and you should get the next available HSLA line. I’m still working out a few issues with the virtualized front-end terminal servers and the emulated mainframe FNP.</p>\n<p>Feel free to register for an account - in addition to a user directory and being able to participate in mail and forums, you’ll be able to set a plan file for the finger daemon now and serve your own gopherspace soon. Also,</p>\n" to "<p>My effort to provide and maintain a large public access system capable of supporting a community, in the spirit of the LCM TD-2 / SDF Twenex TOPS-20, ELVIRA RSTS/E at Stacken, Jim Wilcoxson’s PRIRUN PRIMOS, the Cyber1 CDC system, the old Deathrow VMScluster, etc.</p>\n<p>I’ll be making a more serious web page with some additional technical details soon. For those here who are interested, the system is based on the Honeywell DPS-8/M virtual machine emulator which is running on OpenBSD. Performance is somewhat faster than a similarly configured hardware site, and should comfortably support <em>many</em> users, with <em>many</em> <em>thousands</em> of users in the future once multiprocessing support has stabilized.</p>\n<p>Special thanks to all the Multicians, including but not limited to Tom Van Vleck, Harry Reed, Olin Sibert, Daiyu Hurst, Gary Dixon, Michael Mondy, and especially Charles Anthony and Eric Swenson for many late nights <a href=\"http://www.ultimate.com/phil/pdp10/wizard.gif\" rel=\"nofollow\">pouring</a> over code and documentation, diagnosing problems, and basically rediscovering (and properly documenting) the tricks, processes, and methods for tuning Multics performance and stability for a particular site - many bugs were fixed along the way. It took a lot of effort to get from a clean slate to something I’d be comfortable making publicly available, and I’d never have been able to do it on my own.</p>\n<p>Much of necessary lore was simply never passed down from Honeywell installers to the users or managers of these systems because of just how much there is to know, and the historical separation of duties between sales, installation, field engineering, site administration, system operators, and end users.</p>\n<p>Al Kossow of the Computer History Museum and Tom Van Vleck of the Multicians Archive deserve major and extra thanks for their tireless work in cataloging and preserving so much history that would otherwise be lost. This sort of publicly accessible site simply wouldn’t be a possibility if the necessary manuals were not preserved. It’s likely even the emulation would never have been completed without the preservation efforts preceding it.</p>\n<p><strong>NOTE</strong>: If you experience any issue after being connected to a line, such as the system not echoing characters, not being responsive to input, etc, just disconnect and reconnect to the system and you should get the next available HSLA line. I’m still working out a few issues with the virtualized front-end terminal servers and the emulated mainframe FNP.</p>\n<p>Feel free to register for an account - in addition to a user directory and being able to participate in mail and forums, you’ll be able to set a plan file for the finger daemon now and serve your own gopherspace soon.</p>\n"
Reason: Typo fix.
2018-04-19 12:55 -0500 pushcx Story: 'Big bitcoin heist' suspect escapes prison and flees Iceland 'on PM's plane'
Action: changed tags from "cryptocurrencies" to "cryptocurrencies law person"
Reason: Adding appropriate tags.
2018-04-18 18:23 -0500 pushcx Story: SCUMM internals and syntax for the sake of nostalgia
Action: changed tags from "programming games" to "games compilers"
Reason: Adding a more-specific tag.
2018-04-18 15:34 -0500 pushcx Story: Seeker, the easiest way to create your own paid job board
Action: deleted story
Reason: A thing your friend made is not on-topic, but if your friend would like to submit it to barnacl.es with the `show` tag (or, better, a blog post about its creation) it'd be on-topic there.
2018-04-18 15:24 -0500 (Users) Story: Hello wasm-pack!
Action: changed title from "Hello wasm-pack! – Mozilla Hacks" to "Hello wasm-pack!"
Reason: Automatically changed from user suggestions
2018-04-18 07:06 -0500 pushcx Story: Introduction to HardenedBSD World
Action: changed description from "HardenedBSD is a security enhanced fork of FreeBSD which happened in 2014. HardenedBSD is implementing many exploit mitigation and security technologies on top of FreeBSD which all started with implementation of Address Space Layout Randomization (ASLR). The fork has been created for ease of development." to "", changed markeddown_description from "<p>HardenedBSD is a security enhanced fork of FreeBSD which happened in 2014. HardenedBSD is implementing many exploit mitigation and security technologies on top of FreeBSD which all started with implementation of Address Space Layout Randomization (ASLR). The fork has been created for ease of development.</p>\n" to ""
Reason: Removing redundant description.
2018-04-18 07:04 -0500 pushcx Story: FreeBSD Desktop – Part 1 – Simplified Boot
Action: changed description from "According to the project website – https://freebsd.org/ – “FreeBSD is an operating system used to power modern servers, **desktops**, and embedded platforms” so why not tune the boot process to be more appealing on laptops/desktops?" to "", changed markeddown_description from "<p>According to the project website – <a href=\"https://freebsd.org/\" rel=\"nofollow\">https://freebsd.org/</a> – “FreeBSD is an operating system used to power modern servers, <strong>desktops</strong>, and embedded platforms” so why not tune the boot process to be more appealing on laptops/desktops?</p>\n" to ""
Reason: Removing redundant description.
2018-04-18 07:03 -0500 pushcx Story: FreeBSD Desktop – Part 2 – Install
Action: changed description from "How about actually installing FreeBSD? On a real hardware? You may first want to mess with the FreeBSD installer in a virtualized hardware (Bhyve/KVM/XEN/Virtualbox/…) so You will gain some confidence. In these posts series we will create a complete step by step FreeBSD desktop installation on USB 2.0 pendrive. 8 GB size or more is required. This way You will not have to ‘touch’ you installed system and as You gain confidence in FreeBSD You may want to switch to it if it suits your needs better then the currently installed system on your hardware. This way You can also try it on various computers without the need of (re)install or You may use it as You ‘go/mobile’ system on a stick." to "", changed markeddown_description from "<p>How about actually installing FreeBSD? On a real hardware? You may first want to mess with the FreeBSD installer in a virtualized hardware (Bhyve/KVM/XEN/Virtualbox/…) so You will gain some confidence. In these posts series we will create a complete step by step FreeBSD desktop installation on USB 2.0 pendrive. 8 GB size or more is required. This way You will not have to ‘touch’ you installed system and as You gain confidence in FreeBSD You may want to switch to it if it suits your needs better then the currently installed system on your hardware. This way You can also try it on various computers without the need of (re)install or You may use it as You ‘go/mobile’ system on a stick.</p>\n" to "", merged into dtfyln (FreeBSD Desktop – Part 1 – Simplified Boot)
Reason: We don't need this discussion spread across two stories. In the future, just use the story description to add the second link, and don't use the story description for links unless you're adding some important information or context.
2018-04-18 07:02 -0500 pushcx Story: So, why Plan 9?
Action: changed title from "[9fans] So, why Plan 9?" to "So, why Plan 9?"
Reason: Please remove site names from titles.
2018-04-17 19:59 -0500 (Users) Story: What programming languages have been designed to reduce naming things?
Action: changed tags from "plt" to "plt ask"
Reason: Automatically changed from user suggestions
2018-04-17 07:05 -0500 pushcx User redbus
Action: Banned
Reason: Banning attempt by yesterday's voting ring to re-establish.
2018-04-17 06:36 -0500 pushcx Story: How is data stored during C programming?
Action: deleted story
Reason: Banning attempt by yesterday's voting ring to re-establish.
2018-04-17 06:36 -0500 pushcx User bluerain
Action: Banned
Reason: Banning attempt by yesterday's voting ring to re-establish.
2018-04-17 06:36 -0500 pushcx User littlechicken
Action: Banned
Reason: Banning attempt by yesterday's voting ring to re-establish.
2018-04-17 06:36 -0500 pushcx User palsya
Action: Banned
Reason: Banning attempt by yesterday's voting ring to re-establish.
2018-04-16 23:16 -0500 (Users) Story: Teen charged in Nova Scotia government breach
Action: changed tags from "security" to "security law"
Reason: Automatically changed from user suggestions