SoylentNews is people
SoylentNews
I've been using MacOSX as my primary desktop since the days of Rhapsody. But I always had Linux virtual machines running on occasions. A dwindling number of machines at home were running Linux, most notably a couple of Raspberry Pi and a Synology Diskstation. And when I installed Linux, I usually went for Ubuntu, which did a good job polishing the user experience. The build ring for Tao3D includes a number of virtual machines running several major distros for testing purpose, but it's been quite inactive for a while, and repairing it is on my short-term to-do list.
Working for Red Hat, I thought I had to use Fedora as my primary desktop. And the experience has been a bit underwhelming so far, unfortunately. In just three days, I managed to render a Mac Book Pro unbootable in OSX, had several different issues with skippy or laggy mouse cursors and even non-responsive keyboards, had a driver crash attempting to access my home Wi-Fi, found out the hard way that NFS performance is just horrible, and had to use Google for trivial things way too often.
I complained several times on this blog about what I perceived as a degradation of OSX software quality since 10.6, but this experience with Linux puts all this in some serious perspective.
(Score: 5, Informative) by tfried on Friday December 23 2016, @09:54PM
Phoenix666 writes:
[...]
Read more here.
Is this Phoenix666 writing the cited article? I assume no, but this format makes it awfully hard to tell.
Please. I'm not going to be pedantic on citation format, but do make it something that is not downright misleading, at least. If you can't be bothered to identify the original author, at least provide clear indication that it is somebody else. E.g. "Phoenix666 found this on the intertubes", "Phoenix666 thought the following an interesting read", whatever.
Thanks.
(Score: 3, Insightful) by Nerdfest on Friday December 23 2016, @10:06PM
I thought it was Phoenix666 writing the article as well. It's not. It's an employee of RedHat trash talking Linux support (mostly from his own company). What the fuck is Redhat doing not running Linux in-house, and what are they doing rewarding Apple, whose hardware they don't even support well? Hasn't RedHat done enough damage to Linux with systemd (says he who spent hours recently fighting systemd/NetworkManager/DNS problems in VPNs).
I'd swear they're being paid to do bad things.
(Score: 1) by butthurt on Saturday December 24 2016, @12:03AM
> I thought it was Phoenix666 writing the article as well.
You must be new here. This happens all the time.
(Score: 2) by aristarchus on Friday December 23 2016, @10:08PM
Some person named "Christophe de Dinechin" actually wrote the words. I think.
(Score: 2) by wonkey_monkey on Friday December 23 2016, @11:14PM
I'm not sure that's altogether helpful in clarifying authorship, as I believe it's considered de rigueur to give oneself a pseudonym on the internet these days, and Phoenix666 might just be one...
systemd is Roko's Basilisk
(Score: 1, Redundant) by tangomargarine on Friday December 23 2016, @10:42PM
The last several times I actually checked the article, the byline would most accurately be given as,
Phoenix666 quotes verbatim the first three paragraphs from
"Is that really true?" "I just spent the last hour telling you to think for yourself! Didn't you hear anything I said?"
(Score: 3, Informative) by Phoenix666 on Saturday December 24 2016, @02:34AM
That would be most accurate. I cite verbatim because it's fast, and because it adds little value to re-summarize what most articles have already summarized. Also, it's more error-prone to do that as well, especially when the story covers something you're not expert on. Since nearly all research is highly specialized anymore, that would actually apply to most people. If in summarizing you do it too quickly or make an innocent mistake, the conversation gets sidetracked from the topic of the submission to what an idiot you are. Lastly, when you venture to write anything in a submission, there are frequent complaints about bias or that you're politicizing the story or that your composition sucks.
So my general thought on the matter is, i do what i can, how i can, for the SN community, and i look forward with anticipation to other Soylentils raising the bar and making the community even more excellent than it is.
Washington DC delenda est.
(Score: 2) by tfried on Saturday December 24 2016, @07:46AM
Don't get me wrong. There's nothing wrong with simply posting a quick quote and essentially nothing else. In fact, I like that style, and I appreciate your work. But I've stumbled over this before, I honestly got confused, again, this time. Naturally, my criticism is off-topic, but I do hope you'll be able to take it as constructive criticism.
Again: Your particular form of quoting in this and the next few submissions ismisleading. Not intentionally misleading, but misleading. This can be fixed, easily, by adding very few words. In fact, you could even save two characters and remove ambiguity at the same time, using "Phoenix666 read: [...]". Whatever, really. There are hundreds of options better than the current.
Thanks.
(Score: 0) by Anonymous Coward on Saturday December 24 2016, @12:28AM
Nitpicking. The quote block was clearly marked. Besides regs here know that Phoenix666 posts in such volume that he wouldn't have time to hand-compose each summary, unless this was his full time job (as it may be for editors on the green site).
(Score: 2) by tfried on Saturday December 24 2016, @07:53AM
I'm not asking Phoenix666 or anybody else to hand-compose the summary. I'm asking him and/or other submitters and the editors to use a less confusing template in the case that the summary consists of a quote, only (which is where the ambiguity arises). I made several suggestions in my post, but perhaps the most elegant wording is the one used in a different story, same day:
$submitter has found the following story
It even gives you a convenient place to insert a link, so it even saves you adding "Read more here."
No, this is not an end-of-the-world-severity problem, but it's rampant, and easily fixed.