Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror

Submission + - Slashdot Alum Samzenpus's Fractured Veil Hits Kickstarter

CmdrTaco writes: Long time Slashdot readers remember Samzenpus,who posted over 17,000 stories here, sadly crushing my record in the process! What you might NOT know is that he was frequently the Dungeon Master for D&D campaigns played by the original Slashdot crew, and for the last few years he has been applying these skills with fellow Slashdot editorial alum Chris DiBona to a Survival game called Fractured Veil. It's set in a post apocalyptic Hawaii with a huge world based on real map data to explore, as well as careful balance between PVP & PVE. I figured a lot of our old friends would love to help them meet their kickstarter goal and then help us build bases and murder monsters! The game is turning into something pretty great and I'm excited to see it in the wild!

Comment Spectacle, not transit (Score 3, Interesting) 294

The problem with the monorail is that it was designed as spectacle, not as transit, yet even as spectacle it fails because it's so out of the way that most people never even stumble across it, and if you do take it, all you see are the backs of hotels. It's even priced as spectacle. $2.75 gets you anywhere in New York City via the subway and bus, but it costs $5 to take the monorail just to go 4 miles along the backs of casinos in Las Vegas.

The monorail should have been built in the middle of the Strip. The Strip is a dystopian nightmare highway bifurcating one of the most walked streets in the United States. It's so dangerous that in many places there aren't even any at-grade pedestrian crossings; you have to go up stairs/escalators set back from the strip, go across a bridge, and then back down, often being forced to detour through one or two casinos in the process. It's the ultimate triumph of automobiles over people for no goddamn reason at all.

The mass transit should have been run right down the middle of the Strip. Instead it was forced to the margins where it remains unused, when it was really the car traffic that should have been forced to the margins. Las Vegas should do a NYC-style "Summer Streets" a few times per year and entirely close down the Strip to car traffic for half a day and let pedestrians use it as they'd like, like Mardi Gras. Then people would realize what they've been missing.

Comment Re:Maybe...? (Score 1) 220

FYI, the HSTS preload list is used by all major browsers (Chrome, Firefox, IE, Edge, Safari, Opera, etc.). This is a good thing, of course; online security shouldn't be enforced conditionally depending on which browser you're using.

The linked article got it wrong. This isn't about Chrome adding TLDs to the HSTS list, it's about the TLDs' owner (which also happens to be Google) adding them to the global HSTS list.

Comment Re:Cancer vs common cold (Score 3, Informative) 52

E47-inducible cell lines were generated by infection with
a retroviral vector expressing E47 fused to a tamoxifen-inducible
modified estrogen receptor (MER).

The way this was done was really clever: it uses a virus that causes cancer to treat cancer. Specifically, the retroviral vector is an engineered strain of Moloney Murine Leukemia Virus (MoMuLV), which can cause leukemia in mice (it is not known to cause disease in humans, though retroviral infection does carry at least a small risk of mutagenesis). The viral vector inserts a gene that expresses the protein E47, which acts in a variety of ways to make cancer cells revert to acting like healthy cells.

This is an exciting idea, though as the press release notes, "we are screening for molecules—potential drugs—that can induce overexpression of E47." That's a way of noting that retroviral vector gene therapy is in its infancy, and that it would be much better if we could find a small molecule instead.

These findings prompted us to ask whether
the growth arrest and acinar gene expression induced in vitro
might be sufficient to diminish the tumor-forming potential of
these aggressively growing cells. Indeed, temporary induction of
E47 for 2 to 8 days in vitro produced stable cell cycle arrest and
trypsinogen expression in transplanted human PDA cells. It will
now be of interest to investigate the effects of E47 on the growth
dynamics of established tumors.

And also the above- established tumors notoriously mutate and become genetically heterogeneous over time, greatly increasing the chances that at least some of the cancer cells are resistant to whatever line of attack you throw at them. Cancer cells that have mutant forms of E47's targets wouldn't be reprogrammed. Still, any advance against pancreatic cancer is highly welcome.

Comment Re:photo too blurry (Score 4, Informative) 78

If you do an image search, nearly half of the artist renderings still depict Pluto as blue-grey in color. I think the reasoning was that the planet was thought to be largely covered in methane ice, which has that color. And they were right about the ice, but UV radiation can initiate reactions in methane and diatomic nitrogen to produce a mix of simple hydrocarbons and nitriles, similar to the orange-brown haze that shrouds Titan, just on a much less dramatic scale.

Submission + - Book Review: Networking for System Administrators (amazon.com)

Saint Aardvark writes: (Disclaimer: I received a free copy of this book for writing a review.)

Michael W. Lucas has been writing technical books for a long time, drawing on his experience as both a system and a network administrator. He has mastered the art of making it both easy and enjoyable to inhale large amounts of information; that's my way of saying he writes books well and he's a funny guy. "Networking for System Administrators", available both in DRM-free ebook and dead tree formats, is his latest book, and it's no exception to this trend.

Like the title suggests, this book explains networking to sysadmins — both juniors new to this career, and those who have been around for a while but don't understand how those network folks live or what they need to do their job. If you're one of the latter, you might think "Oh I've read 'TCP/IP Illustrated' — I don't need another networking book." And it's true that there is overlap between these two books. But Lucas also explains about how to work with network folks: dealing with areas of shared responsibility, how to understand where your side ends, and how to talk to a network admin so that everyone understands each other — and more importantly, is both able and happy to help the other. This is something that is out-of-scope for a network textbook, and it's valuable.

So what's in this book? Lucas takes us through all the network layers, explaining how everything fits together. From physical ("If you can trip over it, snag it, break the stupid tab off the plastic connector at its end, or broadcast static over it, it's the physical layer.") to transport and application, he shows practical examples of how the OSI model maps (or doesn't) to the world of TCP/IP. He shows the happy path and the sad path at each layer, explaining how to understand what's going on and troubleshooting failures. This is the part with the strongest overlap with those other network textbooks. If system administration is a side gig (maybe you're a developer who has to maintain your own server), you'll have enough in this book to deal with just about anything you're likely to trip over. But if you're early in your sysadmin career, or you find yourself making the jump to Ops, you will want to follow it up with "TCP/IP Illustrated" for the additional depth.

Since you'll be troubleshooting, you'll need to know the tools that let you dump DNS, peer into packets, and list what's listening (or not) on the network. Lucas covers Linux and Unix, of course, but he also covers Windows — particularly handy if, like me, you've stuck to one side over the course of your career. Tcpdump/Windump, arp, netstat, netcat and ifconfig are all covered here, but more importantly you'll also learn how to understand what they tell you, and how to relay that information to network administrators.

That thought leads to the final chapter of this book: a plea for working as a team, even when you're not on the same team. Bad things come from network and systems folks not understanding each other. Good things — happy workplaces, successful careers, thriving companies and new friends — can come from something as simple as saying "Well, I don't know if it is the network's fault...why don't we test and find out?"

After reading this book, you'll have a strong footing in networking. Lucas explains concepts in practical ways; he makes sure to teach tools in both Unix/Linux and Windows; and he gives you the terms you'll use to explain what you're seeing to the network folks. Along the way there's a lot of hard-won knowledge sprinkled throughout (leave autonegotiation on — it's a lot better than it used to be; replace cables if there's any hint of flakiness in a server's network connection) that, for me at least (and be honest, you too) would have saved a lot of time over the years.

Who would I recommend this book to?
  • If you're a sysadmin at the beginning of your career, this book is an excellent beginning; take it, read it, and build on it — both with practical experience and further reading.
  • If you're coming into system administration the back way (as a developer who has to manage their own server, say, or who shares responsibility for a networked service with other admins), I can't think of a better single source for the practical knowledge you need. You'll gain an understanding of what's going on under the hood, how to diagnose problems you encounter, and how to talk to either system or network administrators about fixing those problems.
  • If you're a manager or senior sysadmin, buy this book and read it through before handing it to the juniors on your team, or that dev who keeps asking questions about routing and the firewall; you may learn a few things, and it's always good to read fine technical writing.

Comment Re:Not 3D chemical printing (Score 4, Informative) 132

Yes, it's a lot like existing solid-state nucleic acid or peptide synthesis setups, but with the major advantage of forming carbon-carbon bonds instead of phosphodiester or amide linkages, making the technique a lot more general. The setup involves a useful reaction called Suzuki coupling. In Suzuki coupling, a metal (usually palladium) catalyzes a reaction between a halide (that is to say, chlorine, bromine, etc.) and an organoboron compound. The mechanism is complex, but the result is a carbon-carbon single bond. This reaction and similar ones are already widely used in the pharmaceutical industry since they can reliably glue together smaller structures together to make a larger molecule. The smaller structures are not individual atoms, though- they tend to have maybe 10-20 atoms or so. Drugs with biaryl structures like the blood pressure drug valsartan are now often made this way.

In previous work, the Burke lab showed that the reaction could be made more convenient by using a specific type of boronate salt which can be easily added and removed from a molecule, and generally produces derivatives that are stable long-term. They then found that these salts can bind to silica and will only be released in the presence of the solvent tetrahydrofuran. So what they did was build a setup that can run this reaction iteratively; at each step, you add another bit of the molecule; each bit has a halide at one end and a boronate salt at the other. This is a lot like an amino acid, which has an amine at one end and a carboxylic acid at the other, which can each react with other amino acids to form chains. Since the molecule bits are shelf-stable, conceivably you could load a machine with a library of commonly used "puzzle pieces" (which you probably bought from a specialty chemicals manufacturer like Sigma-Aldrich or EMD) and assemble them, then wash off the finished product in THF. The yields demonstrated thus far are...not great, but the idea that it can run automated means that it could brute-force some syntheses and allow for the production of complex molecules from more common starting materials. It's a major advance in synthetic organic chemistry, but it's not so much a universal printer as more like an early mechanical printing press, where you still need to provide the type blocks and set the letters yourself.

Comment Re:Nice (Score 3, Informative) 169

Boxing has long been associated with a form of CTE called 'Dementia Pugilistica' (literally Boxer's Dementia), which manifests as Parkinsonism (and Dementia).

The etiology of 'Normal' Parkinsons and Dementia Pugilistica are almost certainly different, but at many stages they look similar enough that it's probably fair to say that boxing does essentially cause Parkinsons.

Comment Re:I blame the FDA (Score 3, Interesting) 365

Nicotine is only distantly related structurally to the vitamin nicotinic acid (aka vitamin B3 or niacin). While nicotinic acid is an intermediate in tobacco's biosynthesis of nicotine, the final nicotine molecule also has an N-methylpyrrolidine ring not present in the vitamin. Nicotinic acid is the active form of vitamin B3, but the amide derivative (nicotinamide, as the parent notes) is also a bioavailable form, as it is converted in the body to nicotinic acid. Nicotinic acid is not named for a direct biological relationship to nicotine, but rather a synthetic chemical relationship. Nicotinic acid was first prepared synthetically by reacting nicotine with nitric acid; it was only later that nicotinic acid was isolated from biological systems, and was eventually found to be essential in the prevention of pellagra.

The physiological effects of nicotine are for the most part not due to its similarity with the vitamin niacin, but because it can bind to and activate a certain type of acetylcholine neuronal receptor: that is to say it mimics a neurotransmitter. Notably, nicotine does not bear much structural similarity to acetylcholine, but its agonist activity at these particular receptors is an identifying property of their type, to the point where they are called nicotinic acetylcholine receptors.

Comment Re:What, no MSDS? (Score 4, Interesting) 87

I don't know- I went looking for an MSDS for a modern firefighting foam, and the composition listed is:

Polyethylene glycol: 2.5-10%
Other components below reportable levels: Greater than 90%

Now, this is for Ansul-3 Fluoroprotein foam concentrate. It definitely contains some sort of fluorinated compound (fluoroprotein foam agents are at least known to contain a fluorinated surfactant and hydrolyzed protein); the MSDS has absolutely no mention of what it is. In the Environmental Handling section, all it says is "An environmental hazard cannot be excluded in the event of unprofessional handling or disposal." Nothing about how fluorinated surfactants are persistent environmental contaminants or can cause kidney damage in high doses. It is simply written like innocuous polyethylene glycol is the only component. I've seen material safety data sheets for shampoo that have far more information.

Now, in the specific case covered by the research paper, the "unknown compounds" aren't really that mysterious. They're all either metabolites, chemical precursors, or close chemical relatives (if you're making some some sort of octane derivative, you can expect some hexane to be in there too). And they're all given as 0.1%-1% of the main PFOS surfactant; certainly chemical manufacturers need to exert better control over their processes, minimize byproducts, perform long-term safety studies, etc. And that goes double for anyone making halogenated organic compounds, which now have a substantial record of turning out to be accumulative toxins. But I think if you look at many common manufactured products at trace levels with tandem mass spec, you're going to find some compounds that aren't in the literature.

Slashdot Top Deals

Testing can show the presense of bugs, but not their absence. -- Dijkstra

Working...