This Week in Techrights

• East Asia’s Patent Peril and the Curse of Patent Trolls
• USPTO Starts Discriminating Against Poor People, and Does So Even When They Rightly Point Out Errors
• Ambrose Chan Enters Document Security Systems (DSS), a Partly Patent Troll Entity
• UPC Threatens to Weaponise Software Patents in Countries That Forbade These
• The Latest Lies About the Unitary Patent (UPC) and CIPO’s Participation in Those
• The Patents Policy of Facebook is Causing an Exodus
• When Google Used Alex Converse to Raid the Public Domain With Software Patents
• Mark Kokes, the Man Behind BlackBerry’s Patent Aggression, Leaves the Company
• WordPress Demonstrates That Facebook’s Patent Strategy is Deterring/Alienating Developers
• Links 20/9/2017: Wine Staging 2.17, Randa 2017, Redox OS 0.3.3
• Links 19/9/2017: Pipewire, Mir Support for Wayland, DRM in W3C
• Links 18/9/2017: Linux 4.14 RC1, Mesa 17.2.1, and GNOME 3.26 on Ubuntu Artful

Open source licensing: What every technologist should know

If you’re a software developer today, you know how to use open source software, but do you know how and why open source licensing started? A little background will help you understand how and why the licenses work the way they do.

Kali Linux 2017.2 Release

We are happy to announce the release of Kali Linux 2017.2, available now for your downloading pleasure. This release is a roll-up of all updates and fixes since our 2017.1 release in April. In tangible terms, if you were to install Kali from your 2017.1 ISO, after logging in to the desktop and running ‘apt update && apt full-upgrade’, you would be faced with something similiar to this daunting message: Also: Kali Linux 2017.2 Released With New Hacking Tools — Download ISO And Torrent Files Here

Open source-based business lessons from a seasoned CEO

The default now is to build from open and in the open. So that's a positive. The downside is that by open source being the default, we may be getting a little lazy. If you remember back 5-10 years, open sourcing was a big deal, and it forced a level of rigor that may have led, in some cases, to founders and early investors taking better approaches to building their company—for example, shifting towards SaaS wherever possible, in part because of the ability to demonstrate clear value versus their own open source.