Plex is a multi-functional streaming platform that allows users to watch, organize, and curate their favorite media entertainment. Sharing Plex libraries is also an option; one that comes with piracy concerns. In an effort to "avoid the growth of piracy," Plex asked GitHub to remove a repository that allows people to reshare libraries that were not originally theirs. TorrentFreak reports: The Swiss company, which is headquartered in the U.S., asked GitHub to remove a "Plex Reshare" repository, alleging that it may contribute to its piracy problem. "Plex Reshare" doesn't host any copyright-infringing material and, as far as we've seen, it doesn't reference any either. Its main purpose is to allow Plex users to make shared Plex directories browsable on the web, which allows people to "reshare" them without being the original owner. "The reason behind this project is to make available your PLEX shares to other friends unrelated to the person who owns the original library," Plex Reshare developer Peter explains.

While the repository doesn't host or link to copyright-infringing material, Plex argues that it can be used to 'grow' piracy. "We have found infringing material in your website which indeed is OTHER 'Plex Server'. The material that is claimed to be infringing is to be removed or access to which is to be disabled immediately and avoid the growth of piracy," the takedown notice reads. The first part of the sentence is somewhat confusing. Plex-reshare is not a Plex server but the company may use "OTHER Plex Server" as an internal classification category. In any case, Plex alleges that the repository can contribute to the growth of piracy on its platform.

Citing the Online Copyright Infringement Liability Limitation Act, Plex urges GitHub to take immediate action, or else it may be held liable. It's not clear what this liability claim rests on, as there are no actual copyright infringements mentioned in the takedown notice. Despite the broad nature of this claim, GitHub has indeed taken the repository offline, replacing it with a DMCA takedown reference. This likely wasn't a straightforward decision as GitHub is known to put developers first with these types of issues. In this case, it took more than three weeks before GitHub took action, which is much longer than usual. This suggests that GitHub allowed the developer to respond and may have sought legal advice from in-house lawyers, to ensure that the rights of all parties are properly considered. The report notes that the Plex-reshare code is listed on Docker Hub as well, which means it may face a similar fate.

To celebrate the 25th anniversary of Doom, there's now mobile versions in the Google Play Store, reports Android Police, "and since this is a 25th-anniversary release, it includes the fourth expansion Thy Flesh Consumed. It's the complete package folks, and it's finally available on Android as an official release."

And in addition, three Doom re-releases are now available for the Nintendo Switch, Xbox One, and PlayStation 4, reports the Verge -- though there was one little glitch: Bethesda says it'll get rid of the strange requirement that players must log into an online account before they play the newly re-released versions of Doom, Doom II, and Doom 3, which went live yesterday. Players quickly criticized Bethesda for the seemingly ridiculous limitation -- the first of these games was released more than 25 years ago, at a time when there was obviously no internet requirement. The online login will be made optional in a coming update, Bethesda said today.
The re-releases were part of QuakeCon 2019, reports IGN, noting that Bethesda also showcased Doom Eternal's multiplayer, "revealing new details about the unique 1v2 Battle Mode."

Forbes hails the re-releases as "id Software's fast-paced, ultra-violent...classic shooters," adding that "It appears the re-releases are actually Unity remakes, though whether much has changed beyond resolution support remains to be seen." But they may also have some other minor differences, Engadget reports: There have been a few other complaints as well, such as the addition of copy protection, graphical changes (such as filtering that softens those 1993-era graphics) and apparent music tempo slowdowns on the Switch. That's not including the removal of downloads for the old PS3 and Xbox 360 versions. It's not a fiasco, but these clearly weren't the straightforward ports some were expecting.

An anonymous reader quotes a report from Android Authority: Owners of the Nest Secure alarm system have been able to use voice commands to control their home security through Google Assistant for a while now. However, to issue those commands, they needed a separate Google Assistant-powered device, like a smartphone or a Google Home smart speaker. The reason for this limitation has always seemed straightforward: according to the official tech specs, there's no onboard microphone in the Nest Secure system. However, Google just informed us that it is right now rolling out Assistant functionality to all Nest Secure devices via a software update. That's right: if you currently own a Nest Secure, you will be able to use it as a Google Home very soon. That means somewhere in the Nest Guard -- the keypad base station of the Nest Secure -- there might be a microphone we didn't know existed. Either that or your voice commands are going to be heard by another product (like your phone, maybe) but Assistant's output will now come from the Nest Guard, if you happen to be in the range of that device. UPDATE: Google has issued a statement to Android Authority confirming the built-in microphone in the Nest Guard base system that's not listed on the official spec sheet at Nest's site. The microphone has been in an inactive state since the release of the Nest Secure, Google says. This unlisted mic is how the Nest Guard will be able to operate as a pseudo-Google Home with just a software update.

A limitation of current (affordable) 3D printers is their use of open loop controllers and stepper motors which limits reliability (drove the motor too quickly and skipped a step? Your model is ruined) and precision (~300 steps per revolution). A new project, Servo Stock instead uses cheap RC Servomotors combined with Hall Effect sensors, using a closed-loop controller to precisely position the extruder. The Servo Stock is derived from the delta robot Reprap Rostock (which is pretty cool even with stepper motors). The sensors give a resolution of 4096 ticks per rotation, and the controller can currently position the motors to within +/-2 ticks. They've also simplified the printer electronics by driving as much as possible from the controlling computer using Bowler, a new communication protocol for machine control. The Servo Stock also includes sensors for the hot end, presumably to be used to control the filament feed rate and temperature. The hardware models are fully parametric, allowing reasonably straightforward scaling of the design. Source for the hardware, firmware, and software is available.

Most commenting readers scoffed at Kent State University's new policy (noted on Slashdot yesterday) forbidding athletes from using profiles on Facebook. The arguments offered (legal, moral, and practical) mostly berated the school for limiting their students to no good end, but some thought-provoking comments exposed at least some complexities which make the issue less clear-cut than a straightforward case either of censorship or contractual freedom. Read on for a sampling of the comments which typified the conversation.