Jump to content

Search the Community

Showing results for tags 'open source'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station


  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions


  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

  1. A simple GUI wrapper for youtube-dl and yt-dlp. Features: Follow system color mode, or choose between dark mode and light mode. Update youtube-dl/yt-dlp on startup. List all available formats. Override video, audio formats and output container. Embed metadata into downloaded file. Download and embed thumbnails. Download playlists. Select types of subtitles (default, all languages, auto-generated) to download and embed. Specify custom download filename template. Specify custom download path. Specify custom ffmpeg path. Specify custom proxy. Specify custom command-line arguments. Homepage: https://github.com/database64128/youtube-dl-wpf Download: https://github.com/database64128/youtube-dl-wpf/releases/tag/v1.11.0
  2. Just wanted to open a discussion in regards to building a somewhat secure PC or laptop in respect to privacy of the business/user. With everything slowly becoming closed source and with end users having no access to control the security of their systems (E:G - Spretre, Meltdown, Thunderbolt exploits, Intel Management Engine etc). I am very interested in building a computer that runs on open-source system software such as Linux, and has full access to CPU firmware code with features such as Libreboot or Coreboot. This has been something I have been researching for a while. Would be very interested in hearing from others with such a setup or also any ideas on the above topic. Any ideas in regards to implementing such system or just brainstorming on how to build a secure setup would be great. Im talking about open-source software, hardware switches, manually removing components such as microphones / cameras to prevent three letter agencies stockpiling data and hoarding it in fusion centers. For a bit of context, please watch this Documentary. Any feedback on systems by companies such as System76 and Purism and the like would be phenomenal! Thanks in advance!
  3. A Desktop App for YouTube Music ====================================================================== Changelog: Add Unlisted languages (Deutsch, Bahasa Indonesia, Türkçe, Italiano, Japanese) Option to remove the download bar on taskbar #158 Miniplayer sizes (4, 5 and 6) Select audio output mpris integration #144 Single instance settings & lyrics windows #154 Option to minimize app on startup #148 BUG report button on context menu (right click mouse) Fix Dark grey bar at bottom of the app #109 A JavaScript error occured in the main process #126, #112 Last.fm won't authenticate. #124 Mini player and lyrics windows become unresponsive and lock up desktop when moved #151 Lyrics at times do not advance to the next/previous songs #156 Share should open in the default browser #141 Improve Single instance mode #107 Improve some languages Check if video is advertisement and prevent scrobble Electron v7.2.4 Lyrics Companion Server Listen on http://localhost:9863/query to get info about player and track. (WS or HTTP Request) Listen on http://localhost:9863/info to get info about app and server. (HTTP Only) You can enable or disable protection token (prevent unauthorized commands) ====================================================================== Home: https://ytmdesktop.app/ https://github.com/ytmdesktop/ytmdesktop ------------------------------ Download for Windows: https://github.com/ytmdesktop/ytmdesktop/releases/download/v1.10.0/YouTube.Music.Desktop.App.Setup.1.10.0.exe Download for Mac or Linux: https://github.com/ytmdesktop/ytmdesktop#available-for
  4. HandyPAF

    Tricycle 2.4.3 (x64)

    Video transcoding... easier than riding a bike. ------------------------------ Tricycle is an open-source video transcoder. It takes the guesswork out of converting videos by using layman's terms and providing a reasonable default configuration. Tricycle is powered by other open-source projects such as FFmpeg, x264, and x265. Features: Reads/decodes most video and audio formats Writes/encodes to the following formats Container formats: MP4 MKV Video formats: AVC (H.264) HEVC (H.265) Audio formats: AAC Dolby Digital (AC-3) Dolby TrueHD (copy/passthru to MKV only) DTS (copy/passthru only) DTS Master Audio (copy/passthru to MKV only) Supports 4K resolution and HDR (HDR10) Tonemaps HDR to SDR Scales video to standard resolutions Detects and crops black bars Crops to a selected aspect ratio Reduces noise in video Overlays subtitles (all or forced only) Supports mutliple audio tracks in mono, stereo, 5.1 surround, or 7.1 surround (copy/passthru to MKV only) ====================================================================== Changelog: All Platforms Fixed a bug that prevented transcodes from starting with some culture settings Fixed a bug that prevented the video configuration from displaying properly with some culture settings ------------------------------ Requirements: macOS High Sierra (10.13) or later Windows 7 or later (64-bit) .NET Framework 4.6.1 or later ====================================================================== Home: https://github.com/kmcclive/tricycle ------------------------------ Download: Windows | MacOS
  5. One of the biggest problems of owning an older boat (besides being a money pit – that is common to all boats regardless of age) is the lack of parts and equipment, and the lack of support for those parts if you can find them at all. Like most things, this is an area that can benefit greatly from some open source solutions, which the Open Boat Projects in Germany has been able to show. (Google Translate from German) This group has solutions for equipment problems of all kinds for essentially any sized boat. At their most recent expo, many people were interested in open source solutions for situations where there is currently only an expensive proprietary option, such as support for various plotting devices. This isn’t the only part of this project, though. It includes many separate projects, like their solutions for autopilot and navigation. There are even complete hardware packages available, all fully documented. Open source solutions for large, expensive things like this are often few and far between for a number of reasons. There are limited options for other modes of open source transportation too, as it seems like most large companies are not willing to give up their secrets easily. Communities like this, however, give us hope that people will have other options for repairing their vehicles without having to shell out too much money. Source
  6. muCommander is a cross-platform, open source file manager Total Commander has been the favorite file manager of many users for decades. It's no surprise that it has been the inspiration for many clones. muCommander is one of these, and happens to be an open source alternative. The program is available for macOS, Windows, and Linux. Here's a comparison of the interfaces of Total Commander and muCommander. The latter's GUI is perhaps a bit easier on the eyes, that's probably due to the theme and the icons on the toolbar. But it's the features that are important. muCommander has a two-pane interface, obviously. You can switch to a horizontal view from the Window menu. Not a fan of the dual-pane view? Switch to the single pane mode. There is an optional tree view that can be enabled as well. An address bar is available at the top of each pane, to the left of which is a drive switcher menu button. There are five columns displayed in the interface: Extensions (which is the icon column on the left edge), file name, size, Date, Permissions. These can be toggled from the View menu's Show/Hide Columns. Drag and drop a column to rearrange the order. Right-clicking inside the interface brings up a context menu that's used for opening files in their default handler, or load the location in Explorer. You can also use the menu to copy files, or just the file names, base names or the path of the files. Working with a bunch of files or folders? Use the mark and unmark options, there are mark all and unmark all menu items too. One useful feature here is the "Change Permissions" options that lets you set the Read, Write and Executable permission for each file and folder on a per-user or group basis. The program has an archiver tool built-in that you can use to pack ZIP, TAR, GZip, BZip2 formats. Unpacking support includes 7z, RAR among other popular formats. The File Menu has a checksum value checker tool, a file splitter and joiner, and a batch rename utility. The application remembers the previous session and opens the last accessed folders when you start it again. This behavior can be changed from the Preferences. muCommander can be used to setup and connect to your FTP, SMB, SFTP, S3, HTTP, HDFS, NFS, VSPHERE servers. You may also email files directly from the application. Bookmarks can be added to quickly jump to your favorite folders. The command bar at the bottom displays some functions that you can access, these can also be used by using the hotkeys F3-F10. muCommander features a built-in text and image viewer that can be accessed from the command bar or the F3 key. There is an internal editor too, but this only works with text files. The Refresh button in the Command Bar is an extra option that most File Managers don't have. Speaking of which, you can customize the bottom bar from the View menu and there are a whole host of shortcuts to choose from. The program has a handful of themes to choose from including a retro theme that's similar to Norton Commander, a dark theme and some sub-theme styles as well. muCommander is keyboard friendly and there are many shortcuts that you can use and customize. The program requires Java to run. The Linux version is quite identical to the Windows version. Though the current build was updated a year ago, the developer has been working on it, and has recently hinted that a new version will be released soon. Of the many Total Commander clones out there, muCommander is one of the better ones. Landing Page: http://www.mucommander.com/ Source: muCommander is a cross-platform, open source file manager (gHacks)
  7. Open source licenses: What, which, and why Learn what open source licenses are, which one to choose, and why it matters. Enlarge / Most open source projects are vastly more restrictive with their trademarks than their code. OpenBSD's Puffy, Linux's Tux, and the FSF's Meditating Gnu are among the few FOSS logos that can easily and legally be remixed and reused for simple illustrative purposes. OpenBSD, Free Software Foundation, Larry Ewing, Seattle Municipal Archives Most people have at least heard of open source software by now—and even have a fairly good idea of what it is. Its own luminaries argue incessantly about what to call it—with camps arguing for everything from Free to Libre to Open Source and every possible combination of the above—but the one thing every expert agrees on is that it's not open source (or whatever) if it doesn't have a clearly attributed license. You can't just publicly dump a bunch of source code without a license and say "whatever—it's there, anybody can get it." Due to the way copyright law works in most of the world, freely available code without an explicitly declared license is copyright by the author, all rights reserved. This means it's just plain unsafe to use unlicensed code, published or not—there's nothing stopping the author from coming after you and suing for royalties if you start using it. The only way to actually make your code open source and freely available is to attach a license to it. Preferably, you want a comment with the name and version of a well-known license in the header of every file and a full copy of the license available in the root folder of your project, named LICENSE or LICENSE.TXT. This, of course, raises the question of which license to use—and why? There are a few general types of licenses available, and we'll cover each in its own section, along with one or more prominent examples of this license type. Default licensing—proprietary, all rights reserved In most jurisdictions, any code or content is automatically copyrighted by the author, with all rights reserved, unless otherwise stated. While it's good form to declare the author and the copyright date in the header of any code or document, failing to do so doesn't mean the author's rights are void. An author who makes content or code available on their own website, a Github repository, etc—either without a stated license or with an express declaration of copyright—maintains both usage and distribution rights for that code, even though it's trivially simple to view or download. If you execute that code on your own computer or computers, you're transgressing on the author's usage rights, and they may bring civil suit against you for violating their copyright, since they never granted you that right. Similarly, if you copy that code and give it to a friend, post it on another website, sell it, or otherwise make it available anywhere beyond where the author originally posted it, you've transgressed upon the author's distribution rights, and they have standing to bring a civil suit against you. Note that an author who maintains proprietary rights to a codebase may individually grant license to persons or organizations to use that code. Technically, you don't ever "buy" software, even when it's boxed up in a physical store. What you're actually purchasing is a license to use the software—which may or may not include physical media containing a copy of the code. Home-grown licenses The short version of our comment on home-grown licensing is simple: just don't do it. There are enough well-understood, OSI-approved open source licenses in the world already that nearly any person or project should be able to find an appropriate one. Writing your own license instead means that potential users of your project, content, or code will have to do the same thing the author didn't want to—read and understand a new license from scratch. The new license will not have been previously tested in court, which many (though not all) of the OSI-approved open source licenses have been. Even more importantly, your new license will not be widely understood. When a person or company wants to use a project licensed under—for example—GPL v3, Apache 2.0, or CC0 (more on these licenses later), it's relatively easy to figure out whether the license in question grants enough rights, in the right ways, to be suited for that purpose. Asking a competent intellectual property lawyer for advice is cheap and easy, because that competent IP lawyer should already be familiar with these licenses, case-law involving them, and so forth. By contrast, if your project is licensed "Joe's Open Source License v1.01" nobody knows what that means. Legal consultation for a project under that license will be much more expensive—and dicey—because an IP lawyer would need to evaluate the text of the license as an entirely new work, unproven and untested. The new license might have unclear text, unintentional conflicts between clauses, or be otherwise unenforceable due to legal issues its author did not understand. Failure to choose an OSI-approved license can also invalidate a project from certain rights or grants. For example, both Google and IBM offer royalty-free usage of portions of their patent portfolio to open source projects—and your project, no matter how "free" you consider it, may not qualify with a home-grown license. (IBM specifically names OSI license approval as a grant condition.) OSI-approved licenses The Open Source Initiative maintains a list of approved open source licenses, which comply with the OSI's definition of "open source." In the OSI's own words, these licenses "allow software to be freely used, modified, and shared." There is a lot of overlap among these licenses, many of which probably never should have existed—see "home grown licenses," above—but at some point, each of them gained enough traction to go through the OSI license approval process. We're going to break this list of licenses down into three categories and list some of the more notable examples of each. Most authors don't need to read and understand the OSI's entire list—there usually aren't enough differences between common and uncommon variants of a general license type to make it worth straying from the most commonly used and well-understood versions. Strong copyleft licenses A copyleft license is a license that grants the permission to freely use, modify, and redistribute the covered intellectual property—but only if the original license remains intact, both for the original project and for any modifications to the original project anyone might make. This type of license—sometimes dismissively or fearfully referred to as "viral"—is the one attached to such famous projects as the Linux kernel, the GNU C Compiler, and the WordPress content management system. A copyleft license may be "strong" or "weak"—a strong copyleft license covers both the project itself and any code that links to any code within the covered project. A weak copyleft license only covers the original project itself and allows non-copyleft-licensed code—even proprietary code—to link to functions within the weak-copyleft-licensed project without violating its license. Some of the more popular strong copyleft licenses include: GPLv2—the GNU General Public License allows for free usage, modification, and distribution of covered code, but the original license must remain intact and covers both the original project and any modifications. No attribution or patent grants are required in the GPLv2, but the seventh section does prohibit redistribution of GPLv2 licensed code if patents or any other reason would render the redistributed code unusable to a recipient. The GPL also requires that anyone distributing compiled versions of a project make original source code available as well, either by providing the source along with the distributed object code, or by offering it upon request. GPLv3—Version three of the GNU General Public License is for most intents and purposes similar to GPLv2. It handles patents differently, however—the GPLv2 forbade redistribution under the GPLv2 if doing so would potentially require royalty payments for patents covering the work. The GPLv3 goes a step further and explicitly grants free usage rights to any patents owned, then or in the future, by any contributor to the project. The GPLv3 also expressly grants recipients the right to break any DRM (Digital Rights Management) code contained within the covered project, preventing them from being charged with violations of the Digital Millennium Copyright Act or similar "tamper-proofing" laws. AGPL—the Affero GNU General Public License is, effectively, the GPLv3 with one significant additional clause—in addition to offering GPL freedoms to those who receive copies of AGPL-licensed software, it offers those same freedoms to users who interact with the AGPL-licensed software over a network. This prevents an individual or company from making significant valuable modifications to a project intended for widespread network use and refusing to make those modifications freely available. We're going to give a little more ink to the AGPL outside of our bulleted list above, because it's a little harder to explain its impact to someone who isn't already very familiar with copyleft. In order to better understand its impact, we'll look at one real AGPL licensed project and a fictitious scenario involving a large company that might wish to adopt it. The Nextcloud Web-based file-sharing suite is an AGPL-licensed project. Because it's licensed under a GPL variant, any person or company can freely download, install, and use it, either for themselves or to offer services—including paid services—to others. Let's imagine a hypothetical company—we'll call the company PB LLC, and their product Plopbox—that decides to spin up a large commercial site offering paid access to managed, hosted Nextcloud instances. In the course of making Plopbox scale to millions of users, PB LLC makes substantial modifications to the code. The modified code consumes far fewer server resources and also adds several features that Plopbox's users find valuable enough to distinguish Plopbox substantially from vanilla installations of Nextcloud. If Nextcloud—the open source project PB LLC consumed in order to create the Plopbox service—had been licensed under the standard GPL, those modifications could remain proprietary, and PB LLC would not be required to provide them to anyone. This is because the standard GPL's restrictions only kick in on redistribution, and PB LLC did not redistribute its modified version of Nextcloud. Since PB LLC only installed Nextcloud on its own servers, it's not obligated to provide copies of Nextcloud—either the original or the modified versions—to anyone, either automatically or upon request. However, Nextcloud is not licensed under either standard version of the GPL—it's licensed under the Affero GPL, and the Affero GPL grants all of the rights associated with the GPL to networked users of a covered project, not merely to recipients of distributed code. So PB LLC actually would be required to make their scalability and new-feature modifications available, in source code form (and object code form, if applicable) to anyone who had both used the project (eg, by opening a Plopbox account) and requested a copy. Weak copyleft licenses A weak copyleft license is essentially similar to a strong copyleft license, but it does not extend its "viral" protection across linkage boundaries. Modifications to the weak-copyleft library (or other project) itself must retain the original license, but any code outside that project—even fully proprietary code—may link directly to functions inside the weak copyleft-licensed project. There are relatively few weak copyleft licenses. The most commonly encountered are: LGPL—the Lesser GNU General Public License. Sometimes still referred to by its original name, GNU "Library" General Public License, since it's most commonly used in shared libraries. Compatible for use with GPL-licensed projects. MPL 2.0—the Mozilla Public License. MPL 2.0 is compatible for use with GPL-licensed projects; prior versions were not. CDDL v1.0—The Common Development and Distribution License, originally authored by Sun Microsystems. CDDL is famously considered incompatible with the GPL, although this incompatibility has not been tested in court. The major difference between the LGPL and the MPL is attribution—in order to link to an LGPL project from a non-GPL-compliant project, you must "give prominent notice... that the Library is used in it (and) covered by this license." The MPL does not have any attribution requirements; you may redistribute MPL projects, and link to functions within an MPL project, without any need to announce that you're doing so. The Mozilla Public License is also notable for offering "forward migration." The Mozilla Foundation, as license steward, may create updated versions of the MPL in the future, with unique version numbers. Should it do so, any user of a project licensed MPL 2.0 may choose to use it under the original MPL 2.0 or any later version of the license. The CDDL similarly allows forward migration but defines the license steward as Sun Microsystems rather than the Mozilla Foundation. Unlike the LGPL and MPL 2.0, CDDL is generally considered incompatible—possibly deliberately—with the GPL. Some organizations have chosen to dynamically link CDDL and GPL licensed code anyway—most notably Canonical, makers of the Ubuntu Linux distribution, who announced their decision to do so by distributing a Linux port of the ZFS filesystem in early 2016. We at Canonical have conducted a legal review, including discussion with the industry’s leading software freedom legal counsel, of the licenses that apply to the Linux kernel and to ZFS. And in doing so, we have concluded that we are acting within the rights granted and in compliance with their terms of both of those licenses. Others have independently achieved the same conclusion. Differing opinions exist, but please bear in mind that these are opinions. One significant dissent to Canonical's position comes from the Software Freedom Conservancy, which states that linking CDDL and GPL code is necessarily a GPL violation. Although the SFC states this in no uncertain terms, it expresses "sympathy" to Canonical's goals, and its conclusion focuses on asking Oracle (the CDDL's license steward, as the current owners of Sun Microsystems) to resolve the issue. Should Oracle make the original ZFS codebase available under a GPLv2 compatible license—including any of the compatible permissive licenses—this availability would, in turn, grandfather in the later OpenZFS project without need for laborious consultation of every individual contributor. We do not recommend modern use of the CDDL license—it is neither generally useful as a permissive license due to its GPL incompatibility, nor is it likely to be useful as a "GPL poison pill" given the strong stance Canonical and others have taken in belief that legal challenges to the linkage of CDDL and GPLv2 code would fail in court. Permissive licenses Permissive licenses make very few restrictions in the usage, distribution, or modification of covered projects. As a result, one permissive license tends to be very similar to another. The most common restriction in permissive licenses is attribution—in other words, these licenses generally require statements giving credit to the original project in any projects derived from them. (We cover permissive licenses that do not require attribution in the next section on public domain equivalent licenses.) Notable permissive licenses include: BSD four-clause license—the original 1990 Berkeley Software Distribution license allowed for free usage, modification, redistribution, and even relicensing of covered software. Four clauses provided the only limiting factors: any redistribution must include the copyright notice of the original project (clauses one and two), any advertising materials for the project or any derivative project must acknowledge the use of the source project (clause three), and no rights to use the name of the authors and/or owners of the original project are granted to endorse any derivative projects (clause four). BSD three-clause license—The BSD three-clause license, first published in 1999, omits the advertising clause from the original four-clause BSD license. It is otherwise identical. BSD two-clause license—Also known as the "Simplified BSD license" or "FreeBSD license," the two-clause BSD license omits the endorsement clause as well as the advertising clause of the original BSD license. Apache license 2.0—the Apache license is a permissive license similar to the BSD two-clause license, except that it additionally grants patent rights similarly to the GPLv3. The Apache 2.0 license also requires redistribution of the original contents of a NOTICE file, should one be present in the source project. The NOTICE file may be appended to if desired but must not omit the original contents and must not alter—or seem to alter—the license terms. "MIT license"—we placed this one in scare quotes because it's ambiguous and could refer to any of several license variants. When someone says "MIT license" they most commonly mean the variant known as the Expat license—which, similarly to the BSD two-clause license, grants usage, modification, redistribution, and relicensing rights to the covered project, requiring only that the original copyright notice be retained and included. In an attempt to de-obfuscate usage of the term "MIT License," the OSI has published a word-for-word copy of the Expat license. GNU All-permissive License—this is another extremely simple permissive license, allowing usage, redistribution, and modification of covered projects, requiring only inclusion of the original copyright and the single paragraph of the GNU all-permissive license itself. Although it's possible to license entire projects under the GNU APL, this is both uncommon and discouraged—it's really intended for use in README, INSTALL, and similar, simple single files. Although software surveys performed by Github and Black Duck Software both list the MIT License as the most commonly encountered open source license, we strongly recommend against its usage due to the ambiguity involved. The MIT license does not grant (or restrict) usage significantly differently from the BSD two-clause license. Since the BSD two-clause license is considerably more clear, both in its own text and in what "BSD two-clause license" refers to in normal use, we strongly recommend its use instead. We recommend the Apache 2.0 license to those who wish to explicitly grant patent rights—with the caveat that this makes Apache 2.0 compatible with the GPLv3 but not with the more widely used GPLv2. Public domain equivalent licenses Many of the people who publish their work without any license notice at all just don't want to bother reading or understanding any of the licenses or their implications and mistakenly believe that providing the work without providing a license makes it "free." We understand the desire not to have to think about licensing, but implore those people to use a public domain equivalent license instead. There is only one OSI-approved public domain equivalent license, and here it is, in its own single-bullet list: BSD 0-clause license—this is the warranty disclaimer from the original BSD license, with none of the restrictive clauses, and with the leading statement "Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted." The BSD 0-clause license does not specifically grant royalty-free usage of software patents to anyone receiving or using BSD 0-clause licensed projects. This is the only OSI-approved public domain equivalent license. Non-OSI-approved licenses For the most part, if a license is not OSI approved, you shouldn't consider using it—and you should be wary of using it, as well. Whether you're looking for strong copyleft, weak copyleft, or permissive licensing, there are plenty of examples in the OSI-approved list and, therefore, no reason to stray. On the other hand, there's only one OSI-approved public domain equivalent license—and the kind of folks who don't find permissive licenses permissive enough tend to be pretty stubborn and may balk even at that. With that in mind, we'll cover a few of the most notable non-OSI-approved public domain equivalents here. Unlicense—the Unlicense states that covered works are released into the public domain and goes on to specify exactly what that means. This is not an OSI-approved license, due in part to its use of the term "public domain" itself, which could complicate any legal situations involving works placed under the Unlicense. CC0—The Creative Commons Zero license is the most permissive form of the Creative Commons family of licenses, which are more commonly used to cover text and media creations than code. The Creative Commons Foundation submitted CC0 to the OSI for ratification as an open source license; although the OSI never formally rejected it, they were unable to reach a conclusion to ratify it—due mostly to its explicit disclaimer of conveyance of patent rights, which the OSI refers to as both "exceedingly rare" and "potentially dangerous" in an open source license. WTFPL—short for, well, WTF Public License, the WTFPL is a very short and exceedingly informal affirmation that you can do whatever you'd like to do with any code made available under the WTFPL. The Free Software Foundation recognizes the WTFPL as a GPL-compatible Free Software License but does not recommend its use; the OSI rejected the WTFPL entirely on the dubious grounds that it is "no different to a public domain dedication," despite its lack of use of the term "public domain" and the different rights associated with public domain in different jurisdictions. We want to note—again—that we do not recommend the use of any non-OSI-approved license. Using any of these unapproved public domain-equivalent licenses—no matter how apparently free—is a risky proposition. It's better to use a non-OSI-approved license than no license at all, but doing so runs the risk of disqualifying yourself or your users from patent or even monetary grants. Source: Open source licenses: What, which, and why (Ars Technica)
  8. Why the entire open source movement is under threat right now FOSS projects are scrambling to raise funds during the pandemic (Image credit: Shutterstock / fatmawati achmad zaenuri) To date, the Covid-19 pandemic has affected over 170 technology events worldwide. Some of them have been postponed and others have moved online, but the majority have been cancelled outright. This has had a significant impact on the open source community, placing high-profile organizations and projects under mounting financial pressure. The Open Source Initiative (OSI), the organisation responsible for assessing open source licenses and preventing, “the abuse of the ideals and ethos inherent to the open source movement”, has indicated it needs to raise $600,000 to meet its funding goals for 2020. The Drupal Association, which oversees the development of the popular Drupal CMS, has already had to lay off staff and as a direct result of event cancellations - and it too needs to raise $500,000. At a surface level, the role of a technology event in helping foster free and open source software (FOSS) communities isn’t immediately apparent. But the reality is that running and attending events has helped raise money for FOSS projects and their governing bodies for decades, sustaining their existence. Further, these events offer various opportunities for the FOSS projects to educate new users and onboard fresh contributors, coordinate their core development activities, perform project housekeeping and brainstorm ideas for future development. Open source community Event cancellations can also negatively impact the already limited funds of participating open source projects and individual contributors. In a bid to minimise the monetary impact of a cancelled event on the FOSS ecosystem, a group of stalwarts from the community, along with their corporate backers, have banded together to form the FOSS Responders working group. In addition to creating a corpus fund, the group is identifying open source events and communities that are most in need of support and also wants to support individuals who are unable to absorb conference-related cancellation fees. The fund, much like the community it is designed to sustain, is hosted on open crowdfunding platform Open Collective. Not only is the platform's code released under the MIT License, but it also publishes financial information relating to campaigns. The Sloan Foundation has contributed $50,000 to the FOSS Responders fund, while Google, Indeed.com, and Sentry.io have pitched in $10,000 each, bringing the total close to $100,000. FOSS Responders is also holding a virtual funding event on Friday May 22, and Indeed.com has promised to match all donations upto $5,000. Besides monetary assistance, FOSS Responders is also working to create a resource center to equip projects with technical resources to help them engage with their community and even organise events virtually. If you are looking for financial help, you can apply to the fund for an emergency grant either as an individual or as a project. And if you want to support the open sources community, here’s a collection of crowdfunding campaigns set up by FOSS foundations to help mitigate the monetary setbacks it has suffered. Source: Why the entire open source movement is under threat right now (TechRadar)
  9. Microsoft’s romance with open source software is on display at Build 2020 But that hasn't stopped Edge from making out with Pinterest. 105 with 65 posters participating, including story author An absolute ton of new announcements has been coming out of this week's Microsoft Build 2020 virtual conference for Windows developers. While cool, most of them are a little thin for individual reports—so we'll get you up to speed on them in this roundup, with links out to each topic if you're interested in more. Windows Terminal goes 1.0 First image of article image gallery. Please visit the source link to see all 3 images. As Windows 10—and Server 2019—pack in more and better command-line functionality, one of the parts of the overall experience that began looking shabby by comparison is the terminal itself. Windows Terminal seeks to change that, and it has just gone 1.0. The terminal itself is open source and is available for perusal and/or hacking at Github under the MIT license. Microsoft's own announcement makes a point of individually crediting 14 contributors by name and acknowledging hundreds more, which is a more-than-welcome sea change for those of us old enough to have lived through the Halloween Documents era. As for the usability of the project itself—it's promising but still needs work, from the jaundiced perspective of a daily-driving Linux user. We like the JSON-formatted Settings file, which can be spawned in Notepad with a simple menu click. We like the native support for both tabs and panes even more—but rough edges include the fact that, under default configs, an Ubuntu/bash shell suddenly turns into two PowerShell panes if you split it. The problem is that the pane-split hotkeys only support creating the new panes with the default profile under Terminal, and the profile includes the interpreter loaded. In addition to changing the default profile—which is very nerdily done by copying and pasting GUIDs in the settings.json—clever users can work around this limitation to some degree by simply executing a different interpreter inside the pane, after the pane itself has been opened. Terminal 1.0 also offers somewhat PuTTY-style copy-and-paste support—selecting text in Terminal doesn't automatically put it in the copy buffer like it does on PuTTY (you need a more Linux-y ctrl-shift-C for that), but right-clicking in another Terminal pane instantly pastes. There are plenty more features in Terminal, most of which seem to amount for now to "shiny"—background images, animated GIFs, scanlines and glowing text (to emulate ancient green-screen CRTs), and so forth. Interested users are advised to check out the Build announcement here and the project docs here. Azure Arc adds Kubernetes management to its CV First image of article image gallery. Please visit the source link to see all 3 images. Azure Arc is—or at least will be—Microsoft's one-stack-fits-all-services cloud-management tool. The goal is for Arc to be as vendor- and type-neutral as possible, with support for managing Windows and Linux servers and VMs, Azure cloud services, and now Kubernetes container clusters from a single pane of glass. It has been tempting to think of Microsoft and Canonical as locked-in partners with the emphasis on Ubuntu in Windows Subsystem for Linux, but Microsoft demonstrates continued vendor neutrality in Arc with an announcement of direct support and integration of SUSE Linux Enterprise Server—which has a larger overall footprint in Europe than it does in the United States, aside from some specialty platforms (such as SAP Hana Enterprise Resource Planning). Although Azure Arc is still in preview (mostly public preview, with some features still in private preview) interested users can sign up to get started with it today. Microsoft loves open source these days—here's the Fluid framework to prove it The Fluid framework was one of the more interesting announcements made at last year's Ignite conference. Fluid enables document collaboration at massive scale and low latency—and it also blurs the lines between traditional document types, allowing simple and functional dynamic content embedding from one framework to the next. Enlarge / We were mildly impressed that this copied Word table rendered properly in an instant message at all—let alone that the recipient could update the data inside the IM itself. (Click through to view the animated demo.) Microsoft Microsoft has been teasing us with Fluid integration into Office 365 apps since the framework's initial announcement in September—this week, the company took things a step further by promising to open source the framework as well. Office 365 VP Jared Spataro announced that "Microsoft will be making the Fluid Framework open source, allowing developers and creators to use key infrastructure from Fluid Framework in their own applications." As exciting as this is, we're a little worried about the follow-on social engineering implications—being able to easily embed fully responsive Office document functionality in arbitrary webpages may make it that much easier to confuse users into putting confidential data and credentials into places they shouldn't. A live preview of some uses of the Fluid Framework is available here, for anyone with a OneDrive for Business account. Social hacking—integrated voice and text chat in Visual Studio Live Share Enlarge / Live collaboration between colleagues with very low latency is possible using VS Live Share. Microsoft Visual Studio Live Share is sort of like Google Docs for code—you and several colleagues can live-edit the same document, with cursors highlighting each of your changes live as they happen. Latency in VS Live Share is considerably lower than what most users will be accustomed to from Google Docs, however—and of course, the collaboration happens inside a full-featured development environment, not a simple word-processing document. The missing piece of this puzzle, until now, has been out-of-band communication—more simply, chat, whether text or voice. Until now, developers have needed to sideload separate tools for that—perhaps using Teams in another window for instant messaging, or Mumble / Skype / Hangouts / whatever for voice. Today's public preview brings the missing communication features directly into Visual Studio Live Share itself. Project Reunion—you got your UWP in my Win32 Project Reunion aims to allow access to both UWP and Win32 libraries from a single unifying framework. Microsoft One of the frustrations with developing for Windows is the coexistence of legacy and modern APIs. Use of the elderly Win32 API is for many developers more familiar, but shifting to UWP—the Universal Windows Platform—means getting access not only to Windows but also to Xbox One, HoloLens, and future hardware platforms. UWP also means an additional layer of security, which will frustrate as many developers as it delights—UWP apps can only be installed directly from the Microsoft Store. Project Reunion, unveiled Wednesday at Build 2020, aims to heal this divide somewhat by decoupling both APIs from the Windows OS and making functionality universally available to apps built under either API. For example, Reunion makes WinUI 3 Preview 1—the modern native UI framework for Windows—available to either UWP or Desktop (Win32) apps in the same way. Microsoft is engineering Project Reunion openly and publicly on Github, giving non-Microsoft developers a chance to directly influence the future of Windows development. Microsoft Teams adds bookings, bots, and broadcasts Microsoft Teams is the next-generation messaging and collaboration application from Redmond, replacing what your cynical author used to call "Lync, Skype for Business, or whatever they're calling it this week." Unlike Lync and Skype for Business, Teams has a functional Web interface. This makes it a much less painful experience for those who don't or can't install the native client directly onto their own PC—including, but not limited to, Linux users. The news this week is integration of appointment scheduling and shift management directly in Teams itself, along with chatbots and support for third-party streaming services. Scheduling and chatbots are exactly what they sound like—and if you're not familiar with the streaming option, think "interview on Teams, stream to the world via Open Broadcast Studio (or similar platform)." Pinterest integration added to Edge Collections Enlarge / Edge Collections are a handy way to group a bunch of websites and rich-formatted notes together. They can be saved, exported, and shared directly. Jim Salter To the dismay of die-hard Chrome fans and Microsoft haters alike, we at Ars have been getting increasingly interested in the Edge browser. By ditching its own proprietary rendering engine and collaborating with Google on the Chromium open source browser, Microsoft gained back a lot of available personnel hours and energy for innovation. Building atop Chromium pretty much instantly produced a snappy, usable browser guaranteed to work nearly anywhere that Chrome does; since then, Microsoft has split its focus on integration with its own platforms (such as Office 365 SSO authentication) and usability features. Collections is one of those features—simply put, it allows users to graphically, intuitively, and simply build rich "website playlists" that can be saved and perused later. Microsoft might have lost us a bit with its latest integration, though—the browser is integrating Pinterest into its Collections feature, showing suggestions for Pinterest boards at the bottom of users' Edge Collections, and allowing Collections themselves to export to Pinterest. Meh. Listing image by Microsoft Source: Microsoft’s romance with open source software is on display at Build 2020 (Ars Technica) (To view the article's image galleries, please visit the above link)
  10. Microsoft: we were wrong about open source Microsoft has embraced open source and even Linux in recent years Image by Alex Castro / The Verge Microsoft has admitted it was wrong about open source, after the company battled it and Linux for years at the height of its desktop domination. Former Microsoft CEO Steve Ballmer famously branded Linux “a cancer that attaches itself in an intellectual property sense to everything it touches” back in 2001. Microsoft president Brad Smith now believes the company was wrong about open source. “Microsoft was on the wrong side of history when open source exploded at the beginning of the century, and I can say that about me personally,” said Smith in a recent MIT event. Smith has been at Microsoft for more than 25 years and was one of the company’s senior lawyers during its battles with open-source software. “The good news is that, if life is long enough, you can learn … that you need to change,” added Smith. Microsoft has certainly changed since the days of branding Linux a cancer. The software giant is now the single largest contributor to open-source projects in the world, beating Facebook, Docker, Google, Apache, and many others. Microsoft has gradually been adopting open source in recent years, including open-sourcing PowerShell, Visual Studio Code, and even Microsoft Edge’s original JavaScript engine. Microsoft has also partnered with Canonical to bring Ubuntu to Windows 10, and it acquired Xamarin to aid mobile app development and GitHub to maintain the popular code repository for developers. Microsoft is even shipping a full Linux kernel in a Windows 10 update that will release later this month, and it moved to the Chromium browser engine for Edge last year. Microsoft is also collaborating with open-source communities to create PowerToys for Windows 10, and the company’s new open design philosophy may mean we’ll see a lot more open-source efforts in Windows in the years to come. Source: Microsoft: we were wrong about open source (The Verge)
  11. Majority of Mobile App Vulnerabilities From Open Source Code COVID-19 has impacted everything over the past year, and mobile app security is no exception. The Synopsys Cybersecurity Research Center (CyRC) took an in-depth look at application security, and discovered just how vulnerable apps that use open source code really are. According to the report, 98% of apps use open source code, and 63% of those apps have at least one known vulnerability. Open source code is no more or less vulnerable than any other code, Jonathan Knudsen, senior security strategist with Synopsys, was quick to point out in an email interview. The prime security task for any organization that uses open source code is how to manage the code correctly. “The report underscores, among other things, that managing security vulnerabilities in open source software components is a very real problem,” Knudsen said. The challenge lies in the self-service nature of open source use. With no commercial vendor to push out updates and patches, it then becomes the responsibility of the developers and the business to evaluate and monitor for security risks and come up with a strategy for the inevitable security problems. Adoption of Open Source Developers turn to open source because it helps them code 20 to 30 times faster than writing their own from scratch; getting a mobile application into the marketplace quickly is a top priority. This need to move fast has created a dependency on open source. It has also led to the prioritization of development over security in many IT organizations just to remain competitive in the market. “To stay competitive, software development teams must figure out how to write code quickly, while not sacrificing security to create value and preserve competitive advantage for their organizations,” said Yaniv Bar-Dayan, CEO and co-founder at Vulcan Cyber. Until that happens, open source will continue to be the go-to code. Finding the Vulnerabilities Code audits to detect vulnerabilities are easier to do on open source software, which is both a blessing and curse; threat actors and well-intentioned developers both have equal access to the code. “Ethical hackers may look at well-maintained open-source projects and quickly identify and report vulnerabilities to help them get patched,” said Hank Schless, senior manager, security solutions at Lookout. “Threat actors may observe the code, find a vulnerability, and figure out how to exploit it as quickly as possible.” On the other hand, Schless added, closed source or first-party code can encounter the same maintenance issues. “While the quality of both open and closed source code varies, switching from open to closed source code might mean swapping known vulnerabilities for unknown vulnerabilities.” A More Secure Mobile App When open source code is used, it often comes with its own list of other open source solutions that are necessary for functionality. This transitive dependency can be layers deep and create a snowball effect of adding hundreds or more. One open source project can end up including hundreds of layers and dozens of possible vulnerabilities. Because of this, you can never trust or test one layer and think everything is fine. Every layer must be tested and updates and patches regularly checked. “Software composition analysis (SCA) is a type of security testing that automates much of the work of identifying used software components, correlating known vulnerabilities and raising alerts when new vulnerabilities are identified,” said Knudsen. Managing the open source components of an application is important, Knudsen added, but it is far from the end of the story. “Applications will only get safer when they are built better with a comprehensive, proactive approach to security. This means incorporating security into every phase of software development, from design through implementation, testing and maintenance. Automated security testing is useful at multiple phases, and includes SCA, static analysis, fuzzing and other types of dynamic testing.” Source: Majority of Mobile App Vulnerabilities From Open Source Code
  12. LF Energy and Alliander Announce a program -- GXF -- to securely manage the modern electrical grid's Industrial Internet of Things. The first you may know about the next cyberwar might be when your power goes out. Just ask the citizens of Kiev, Ukraine -- whose power was cut off for an hour by an attack from Russian hackers. Indeed, you probably don't know it, but the first shots have already been fired in the US. In March 2019 a Denial of Service (DoS) attack hit power grid control systems in Utah, Wyoming, and California. Energy companies know it, which is one reason LF Energy, a Linux Foundation project, announced its latest project: Grid eXchange Fabric (GXF). Dutch distribution system operator Alliander created it as an Open Smart Grid Platform (OSGP). GXF is a scalable and technology-agnostic Industrial Internet of Things (IIoT) platform. It enables grid operators to securely collect data and monitor, control, and manage smart devices on the grid. Specifically, it can be used in the following ways: A user or operator uses one web application to monitor and/or control devices. The application connects to the GXF via web services. These are divided into functional domains, such as Public Lighting, Smart Metering, and Power Quality Third-party developers can use web services to develop or integrate new applications. The platform handles all these application requests securely and uses various functions and services to do so. For the 'translation' and communication of user/operator commands to the various smart devices, the platform uses open protocols. The platform supports various IP based data telecommunication technologies and protocols to communicate with the devices. This is important because electrical grid operators have added IIoT devices to their power grid. Each device requires vastly different tools and processes to ensure interoperability. The purpose of GXF is to decrease the overall complexity and associated maintenance costs of accessing these devices by creating a single generic method of abstracting data access. In short, this is a way of bringing system integration to the electrical grid. GXF also comes with a set of security recommendations to keep the hackers from turning off your lights. These include: Communication over TLS IPSec Virtual Private Network Firewalls between all servers and layers Certificates from a recognized Certificate Authority (CA) Audit trail on all actions throughout the platform Role-based Access Control (RBAC) "We have the tools necessary to make our power grid more efficient and better for our environment, but we're running into a system integration problem at a global scale," said LF Energy Executive Director Dr. Shuli Goodman. "Grid operators need a way to cut through the noise of different data access protocols to pull insights from smart devices directly. With the addition of GXF, we will leverage the shared expertise of our community to tackle this problem head on." GXF is a foundational move. Broadly, GXF will be used as a generic connectivity layer to collect and direct data for IIoT asset monitoring and analytics. It will also enable energy network operators to create advanced business applications across multiple use cases, but that work needs to be done. With an open-source approach, this will be much easier and more secure than doing it piecemeal with proprietary software. Some GXF functionality already exists. For instance, Alliander is already using GXF to manage public street lights in the Netherlands. Other grid operators have applied GXF as the head-end system, which allows for maximum data flexibility between smart meters and network operators, while some have used GXF to manage microgrids. Other attempts to make the electrical grid more secure, such as the recently passed Securing Energy Infrastructure Act, want to step back by adding analog backups to today's modern digital electrical systems. I don't think this will scale that well. We need modern, open-source systems like GXF to securely manage today's electrical grids. With it, we can build a clean, secure connectivity layer for modern IIoT electrical grids. Otherwise, well, with at least three hacking groups potentially disrupting US power grids, we're in trouble. Oh, and by the way, the US Cyber Command has been planting malware in the Russian electrical grid as well. Source
  13. Opinion: It was incompetence, not politics, that led to the Iowa caucus app misfiring. Above all, it was poor programming. Open-source software techniques could have prevented this blunder. When the Iowa Democratic Caucus results were delayed by an application foul-up Bernie Sanders supporters were outraged at a stolen victory. Now, as the results trickle in, and Sanders' results turned out OK, they've quieted down. But the fact remains that the application not only fouled up caucus results reporting, but it also made people even less trusting of the election process. Most of the Iowa caucus post-mortem has focused on Shadow, the company behind the app, and its parent organization, Acronym. The root problem wasn't with the groups behind the misfiring application, IowaReporterApp; it was with a fundamentally flawed software development process. What happened with the Iowa caucus app? The app was insufficiently tested, didn't install properly on many phones, and frequently failed to perform as expected. In short, the app was ripe for failure. Even before the caucus, many experts were concerned about the app's security. It wasn't the first time. In 2016, Iowa precinct chairs tried to use a Microsoft smartphone app to relay results to party headquarters. Its reporting mechanism crashed. This time around Shadow was paid about $63,000 by the Iowa Democratic Party and $58,000 by the Nevada Democratic Party to develop IowaReporterApp. That may sound like a lot of money, but for a mission-critical, mobile application it was on the cheap side. IowaReporterApp had a simple job: Count support for candidates and report back via the app. But the app didn't scale, the phone lines were understaffed, and caucus connectivity was spotty. In short, a programming failure was exacerbated by deployment and execution problems. Shadow admitted as much: "We sincerely regret the delay in the reporting of the results of last night's Iowa caucuses and the uncertainty it has caused to the candidates, their campaigns, and Democratic caucus-goers. As the Iowa Democratic Party has confirmed, the underlying data and collection process via Shadow's mobile caucus app was sound and accurate, but our process to transmit that caucus results data generated via the app to the IDP was not." Was the Iowa caucus app tested at all? Some people have called the Iowa caucus a beta test. I wish! This was an alpha test. The program was only made available to users on Jan. 18, just over two weeks before the caucus. To install the application, instead of using a mainstream app store, users had to download and install it into their phones from TestFairy, an Android app testing platform, and Apple's beta app TestFlight test site. According to Vice, Jonathan Green, chair of the Democratic presidential primary caucuses in Iowa's Fremont Township and Lone Tree precincts and an IT systems administrator, the program didn't work properly. Indeed, Green said, he didn't receive final app instructions until Feb. 3 at 1pm, the day of the caucus. The final instruction e-mail also added that precinct leaders should call the results if the app "stalls/freezes/locks up." As Herbert Lin, senior research scholar for Cyber Policy and Security, Center for International Security and Cooperation at Stanford University, observed, "The idea of releasing a poorly tested app to users without app-specific training hours before it was to be used for real is the height of hubris -- or naivete." There was reason to believe the app would blow up As Evan (Rabble) Henshaw-Plath, CEO of Planetary, a new decentralized social network, tweeted [sic]: "The caucus app is firebase / react app built by one senior engineer who's not done mobile apps and a bunch of folks who were very recent code academy graduates who as of a couple months ago worked as a prep cook for Starbucks and receptionist at Regus." In short, the app and its underlying infrastructure were badly done. Then, the fail-safe after that -- calling in the results -- failed because not enough people were available to deal with the load. So, the Iowa caucus failed because of simple incompetence. Another reason the app failed badly is due to how electoral software is funded and a misguided belief in proprietary software development. Henshaw-Plath tweeted that the "fundamental problem is we've got a very broken way we fund campaign tech." Political software is, by its very nature, focused on the short term: Gaining contributions and winning the election. Therefore, he continued, while "in normal tech circles we'd have a bunch of free software libraries and tools we build on together, but the campaign tech space doesn't have this because decision makers fear our tools will be taken and used by the other side." "The decision makers," he continued, "refuse to use free software, alienating the progcoders/ragtag communities. They also refuse to fund projects between cycles to build reusable platforms." This is fundamentally flawed thinking by leaders without a grasp of how modern software development works. As Alex Stamos, a cybersecurity expert at Stanford University, tweeted: You are building a tabulation system on the critical path of human history. Do you: a) Have your decent public university CS dept build an open-source solution and ask for public review? b) Pay the lowest bidder and keep it secret from election security experts? The result is, well, we just saw it: A proprietary program thrown together without enough time by developers who were outmatched by their job. This simply doesn't work. Open source is the way forward It took years, but everyone outside of Apple now uses open-source methods to create the software that's changing the world. Political party leaders need to wake up and realize it's the 21st century and embrace it as well. It's not as if open-source election software projects don't exist. Here are some that could help us have safe, trustworthy political campaigns and elections: The Progressive Coders Network's mission is to build open-source tools to empower the grassroots and reduce the influence of big money in politics. Some of their projects include National Voter File, a modern database of voter files; Carpool action, a program to link voters to drivers; and the Princeton Gerrymandering Project, which seeks to bring mathematical fairness to electoral district mapping. Ragtag has a similar mission to Progressive Coders. Some of their projects include Helpdesk to connect campaign workers and political activists with tech-savvy helpers and Web Squads for campaigns needing website development help. In both these groups, we're seeing basic civics, a class sorely missing for generations from schools, coming together with open-source software. It's not just small groups working on open-sourcing the election process. Microsoft is getting into the open-source election act. ElectionGuard is an open-source software development kit (SDK) for cryptographically securing voting machines. ElectionGuard should be released soon and, hopefully, will be implemented in some voting machines before the 2020 general election. The US Cybersecurity and Infrastructure Security Agency (CISA) and VotingWorks (a non-partisan, organization) recently open-sourced a tool for auditing election results: Arlo. Its code is available on GitHub. The Open Source Election Technology (OSET) Institute, as part of its Trust the Vote project, is working on ElectOS, a long-idle open-source elections technology platform. When completed, this work in progress will support elections administration and voting. That will include creating, marking, casting, and counting ballots and managing all back-office functions. ElectOS, in theory, could replace today's flawed and obsolete electronic voting systems. But real work needs to be done on it before it can be deployed in elections. The top three voting machine manufacturers -- ES&S. Hart InterCivic, and Dominion -- all use proprietary software. Indeed, most of these run on Windows 7 or even older operating systems. Oh, and in case you've been living under a rock, Windows 7 fell out of support in January 2020. Software failures like Iowa's are unacceptable It's well past time that political parties and governments move to open source. Although, as Lin pointed out, Iowa got one thing right: "It required that votes be counted on paper, and then tallied electronically. ... With that paper trail, the Democrats -- and the nation as a whole -- will be able to regard this event as a case study in how to recover from a poorly run election. … Without the paper trail, there would never be any clarity -- just a whole lot of doubt." The last thing we need is more doubt in our elections. Open source or proprietary, we need a paper ballot audit trail. Unfortunately, Lin observed, "voters in at least nine states including Texas, New Jersey, and Indiana will cast their ballots electronically on systems that do not leave a paper trail." This is a mistake that may be even worse than continuing to rely on out-of-date proprietary software for our elections. Source
  14. 'Its life doesn't have to end!' More than 10 years on from its campaign to persuade users to dump Windows 7 for a non-proprietary alternative, the Free Software Foundation (FSF) has kicked off a petition to urge Microsoft to open-source the recently snuffed software. On the face of it, the logic seems pretty simple. On 14 January Windows 7 reached its end of life as Microsoft turned off the free security update taps with a final fix (which seemed to bork desktop wallpapers for some users). "Its life doesn't have to end," cried the foundation. "We call on Microsoft to upcycle it instead." Unfortunately, the FSF couldn't resist a final dig, saying the killing of the OS had brought to an end "its updates as well as its 10 years of poisoning education, invading privacy, and threatening user security." Hey team, way to go on persuading the Redmond gang to do you a solid. Suggesting such a release would go some way to "undo past wrongs" may not be a persuasive argument for the Seattle suits, who probably saw Windows 7 as way of undoing the heinous deeds of Vista. There is a precedent. Ancient MS-DOS and Word code has been opened up, and the Calculator app found in the current Windows 10 now lurks on GitHub. But an entire, relatively recent OS? We can see some problems, not least the licensed components lurking in Windows 7 that would need to be either excised or open-sourced as well. Then there are the bits and pieces that the company would consider valuable secrets (large chunks of Windows 7 linger on in Windows 10 after all.) And then there is the fact that Windows 7 is not actually unsupported. Three more years of updates are available for those who can pay. And with Windows (as well those parts of it licensed to third parties) still accounting for a sizeable chunk of Microsoft's revenues, we can imagine a very functional and highly compatible free version is not really in the company's best fiscal interests. And let's be honest, who knows what might be lurking in that code. "Take that, Penguin fsckers!" anyone? It was a different time. The Register contacted Microsoft on the off-chance that Windows 7 might be showing up on GitHub at some point soon, but we were told that the company doesn't comment on rumours and speculation. The Win 7 request from FSF is neither rumour nor speculation. In any event, if open source is your thing, there are plenty of Linux distributions in a far better state of usefulness than what was around when Windows 7 first launched. And if there is that Windows app you just can't do without, the popular compatibility layer Wine received a bump to version 5 this week, replete with over 7,400 tweaks to allow you to inflict more Windows apps on your Penguin-tinged OS. Still, never say never. If you told us 10 years ago that Microsoft would be about to ship a version of Windows containing the Linux kernel we might have sprayed precious beer from our nostrils. So who knows what else might be coming down the line? Source
  15. shamu726

    Subtitle Edit 3.4.0

    Subtitle Edit is a free (open source) editor for video subtitles - a subtitle editor :) With SE you can easily adjust a subtitle if it is out of sync with the video in several different ways. You can also use SE for making new subtitles from scratch (do use the time-line/waveform/spectrogram) or translating subtitles. For a list of features see below or check out the Subtitle Edit Help page. On my blog you can download latest beta version and read about/discuss new features. Also, you can watch a few videos about installing and using Subtitle Edit. (Old videos.) Dny238 has written a nice tutorial about Syncing Subtitles with Subtitle Edit :) A Subtitle Edit dll (Subtitle Edit Light Library) is available for programmers (BSD New/Simplified license). Initially created and used by Sublight (a free Windows application for searching and downloading movie subtitles). Homepage Features: Create/adjust/sync/translate subtitle linesConvert between SubRib, MicroDVD, Advanced Sub Station Alpha, Sub Station Alpha, D-Cinema, SAMI, youtube sbv, and many more (170+ different formats!)Cool audio visualizer control - can display wave form and/or spectrogramVideo player uses DirectShow, VLC media player, or MPlayerVisually sync/adjust a subtitle (start/end position and speed)Auto Translation via Google translateRip subtitles from a (decrypted) dvdImport and OCR VobSub sub/idx binary subtitles (can use Tesseract)Import and OCR Blu-ray .sup files (can use Tesseract - bd sup reading is based on Java code from BDSup2Sub by 0xdeadbeef)Can open subtitles embedded inside matroska filesCan open subtitles (text, closed captions, vobsub) embedded inside mp4/mv4 filesCan open/OCR XSub subtitles embedded inside divx/avi filesCan open/OCR DVB subtitles embedded inside .ts (Transport Stream) filesCan open/OCR Blu-ray subtitles embedded inside .m2ts (Transport Stream) filesCan read and write both UTF-8 and other unicode files and ANSI (support for all languages/encodings on the pc!)Sync: Show texts earlier/later + point synchronization + synchronization via other subtitleMerge/split subtitlesAdjust display timeFix common errors wizardSpell checking via Open Office dictionaries/NHunspell (many dictionaries available)Remove text for hear impaired (HI)RenumberingSwedish to Danish translation built-in (via Multi Translator Online)Effects: Typewriter and karaokeHistory/undo manager (Undo=Ctrl+z, Redo=Ctrl+y)Compare subtitlesMultiple search and replaceChange casing using names dictionaryMerge short lines/split long linesExport to PNG images (+bdn xml), Adobe Encore FAB image script, VobSub, Blu-ray sup, EBU stl, PAC, and plain textSubtitle Edit is available in the following languages: Subtitle Edit can read, write, and convert between more than 170 subtitle formats, like: Screenshots: Subtitle Edit main window Change log: 3.4.0 (13th July 2014)New: Switched to .NET Framework 4.0 (from .NET Framework 2.0)New: Runs 64-bit on 64-bit operating systems (requires 64-bit codecs!)New: New subtitle formatsNew: New shortcutsNew: Export to image based formats can now do boxingNew: Export to image based formats, added 2k resolutions - thx JosephNew: New tool "Merge lines with same text"New: Spell check undoNew: Check for updatesImproved: Updated Spanish (Mexico) language file - thx pakitonaranjoImproved: Updated French language file - thx JM GBTImproved: Updated Portuguese language file - thx moobImproved: Updated Korean language file - thx domddolImproved: Updated German language file - thx SiegwarthImproved: Updated Polish language file - thx AdmasImproved: Updated Russian language file - thx LesergImproved: Updated Czech language file - thx TrottelImproved: Updated French language file - thx JM GBTImproved: Updated Bulgarian language file updated - thx IavorImproved: Updated Dutch language file - thx Quetsbeek + minouhseImproved: Updated Hungarian language file - thx ZityiImproved: Updated Italian language file - thx SilverDrakeImproved: Updated Finnish language file - thx TeijoImproved: Updated Romanian language file - thx MirceaImproved: Updated Swedish language file - thx TedImproved: Updated Chinese language file - thx LeonImproved: Updated Greek language file thx ΑΚΗΣImproved: Updated Brazilian Portuguese language file - thx Igor RückertImproved: Updated Basque language file - thx XabierImproved: Export to image based format now remembers most settingsImproved: Always close SAMI tags (except when end time=next start time)Improved: Merge selected lines in original - better handling of empty lineImproved: DCinema interop - better use of "Effect" - thx genaImproved: Drag & drop support for subtitle comparer - thx ivandroflyImproved: Better time division in "Split long lines" - thx JoelImproved:Better splitting of dialogues in "Split long lines" - thx JoelImproved: Word lists improved - thx ivandroflyImproved: Ctrl+I now works better in text box - thx rebawestFixed: OCR via "image compare" now works againFixed: Several bugs regarding Blu-ray sup export - thx marinerFixed: "Bridge gap in duration" when working with SSA/ASSFixed: Don't lock "settings.xml" when SE starts/exits - thx DoigtFixed: Crash when exporting to DOST - thx Nguyen HoangFixed: Crash in "Fix short display times" - thx ivandroflyFixed: Bug in batch convert regarding frame rate - thx RasmusFixed: Minor fixes for auto-wrap while typing - thx AndrewFixed: Possible crash in main window (typo in history timer)Fixed: Cut text in image export with right-alignFixed: Crash when doing OCR in batchFixed: Several fixes for "Fix common OCR errors" - thx matidio/JoelFixed: Crash related to bad font tags in SSA/ASS - thx hhgyuFixed: Error converting from DCinema interop to SMPTEFixed: Load last line if blank when loading SubRip files - thx LeonFixed: Spell check auto-fix names now actually works - thx MartinEnjoy - and thx for all the contributions on Gitbub :) Note: SE will now require 64-bit VLC/codecs on 64-bit operating systems! Download: For Windows XP users: SE requires Microsoft .NET Framework Version 2.0 - 3.5. SubtitleEdit-3.4.0-Setup.zip - Installer version, .NET 4-4.5, 64/32-bit (will run 64 bit on 64-bit OS - so do use 64-bit codecs/VLC on 64-bit OS!) - SHA1 Checksum: f9614303ebaa7e8283da95dead164fd6ba9004cf SE340.zip - Portable version, .NET 4-4.5, 64/32-bit (will run 64 bit on 64-bit OS - so do use 64-bit codecs/VLC on 64-bit OS!) - This also works on Linux (when mono/mono-form/etc is installed) - Linux users should also look here: http://www.sub-talk.net/topic/2751-subtitle-edit-for-ubuntu-troubleshoting-tips-and-tricks/ - SHA1 Checksum: e390032dd96b5fee16317339fcf86eaaa5df3ca7 For 64-bit systems, install latest version of LAV filters 64-bit or latest version of VLC 64-bit: LAV filters releases VLC 64-bit downloads (vlc-*-win64.exe is the installer)
  16. shamu726

    MKVToolNix 7.0.0

    MKVToolNix -- Cross-platform tools for Matroska MKVToolNix is a small collection of tools (mkvmerge, mkvinfo, mkvextract, mkvpropedit and mmg) that allows you to manipulate Matroska (MKV) files in several ways. You can use MKVToolNix to create, split, edit, mux, demux, merge, extract or inspect Matroska files. The program will also work with other video formats (AVI, MPEG, MP4, MPEG, Ogg/OGM, RealVideo, MPEG1/2, h264/AVC, Dirac, VC1) including some video codecs (such as VP9 video codec support - reading from IVF/Matroska/WebM files, extract to IVF files), audio (AAC, FLAC, MP2, MP3, (E)AC3, DTS/DTS-HD, Vorbis, RealAudio) and also most subtitle formats (SRT, PGS/SUP, VobSub, ASS, SSA etc.). This is a cross platform application that will work on Windows (both 32 and 64 bit versions), Mac OS X and Linux. Homepage ChangeLog Version 7.0.0 "Where We Going" mkvmerge: enhancement: In addition to the track statistics tags »BPS«, »DURATION«, »NUMBER_OF_BYTES« and »NUMBER_OF_FRAMES« mkvmerge will write two more tags identifying which application wrote the statistics (»_STATISTICS_WRITING_APP«) and when the file in question was written: »_STATISTICS_WRITING_DATE_UTC«. »_STATISTICS_WRITING_APP« will always contain the same string contained in the segment info header element »WritingApp«. »_STATISTICS_WRITING_DATE_UTC« will contain the same timestamp as in the segment info header element »Date«, though »_STATISTICS_WRITING_DATE_UTC« is actually a string representation instead of an integer value.Additionally a tag named »_STATISTICS_TAGS« is written containing the names of the tags that mkvmerge has set automatically. It equals the following currently: »BPS DURATION NUMBER_OF_BYTES NUMBER_OF_FRAMES«.build system: Boost's "date/time" library is now required.mkvmerge: bug fix: If a single subtitle track contains two or more entries at the same timecode then the cue duration and cue relative position elements written were wrong.mkvinfo: bug fix: fixed wrong progress percentage shown during saving the information to text files. Fixes #1016.mkvmerge: new feature: Added a global option for disabling writing the tags with statistics for each track: --disable-track-specific-tags.mkvmerge: new feature: When identifying a Matroska file in verbose identification mode track-specific tags will be output as well. The format is »tag_<tag name in lower case>:<tag value>», e.g. for a tag named »BPS« with the value »224000« the output would be »tag_bps:224000«. Enhancement for #1021.mkvmerge: new feature: mkvmerge will write track-specific tags with statistics (»BPS« for the average number of bits per second, »DURATION« for the duration, »NUMBER_OF_BYTES« and »NUMBER_OF_FRAMES« for the track's size in bytes and its number of frames/packets). Implements #1021.mkvmerge: bug fix: Changed the file type detection order again. The text subtitle formats are now probed after those binary formats that can be detected quickly and unambiguously. This avoids some mis-detection if e.g. Matroska files as ASS text subtitles if they do contain such a track.mmg: enhancement: The chapter editor will only use fast-mode parsing when loading chapters from Matroska files.all: bug fix: fixed invalid memory access in the cleanup procedures which only occurred if the output was redirected with the »--redirect-output« command line parameter.mkvmerge: enhancement: The last chapter entry read from MPLS files is removed if it is at most five seconds long. Patch by Andrew Dvorak (see AUTHORS).mkvmerge: enhancement: added the attachment UID to the verbose identification output of Matroska files.mmg: bug fix: Selecting a subtitle track correctly sets the »character set« drop-down box if no character set was set for this track. Fixes #1008.mmg: enhancement: the subtitle character set cannot be set anymore for subtitle tracks read from Matroska files as mkvmerge ignores that setting for said container anyway (text subs are always encoded in UTF-8 in Matroska).mmg: enhancement: mmg will look for the »mkvmerge« executable in the same directory as the »mmg« executable is located it if the location hasn't been set by the user on all operating systems (before: only on Windows). Improves detection if »mkvmerge« is not in the $PATH.Full ChangeLog Download The current version v7.0.0 is available as an installer and as a portable 7zip archive from fosshub.com. Direct links: Windows installer (32bit) - 10.36 MB | SHA1: 169ad0d5f4bc86453344b08f2d9b2ee16d94d0cc Windows installer (64bit) - 11.48 MB | SHA1: d98281cbcde8924566798c6b26df4ef0732b01c8 Windows portable (32bit) - 9.63 MB | SHA1: a133c1c8fe8f1ec9780313540ecfeb393c280560 Windows portable (64bit) - 10.36 MB | SHA1: 1ffa6f91c8ce0235867f3811ba5799ad9648c4cb * Supported Windows versions are XP and newer from the client OS line and Windows Server 2008 and later from the server line. * For Mac OS X and Linux versions, visit the MKVToolNix homepage.
  17. from the way-of-the-penguin dept Working from home is beginning to move from being a necessary but temporary way of achieving social distancing in offices, to a radical shift in how many companies will operate. Until now, most of the evidence of that change has been anecdotal. But a Twitter thread by Chris Herd, who is CEO of FirstbaseHQ, which "lets you supply, finance and manage all the physical equipment your remote teams need to do great work at home", provides some fascinating statistics on the scale of the shift to working from home. Herd says he has talked to around 1000 companies over the last six months about their plans for remote work. One trend is that corporate headquarters are "finished", he says: companies will cut their commercial office space by 40 to 60%, with people working from home for two to four days each week. Some 30% of the companies Herd talked to say that they intend to get rid of offices completely, and move fully to remote working. Some of the reasons for this shift are obvious. Things like increasing worker satisfaction by avoiding stressful daily commuting, and enabling them to participate in family life during the entire day through flexible working patterns. Slashing office costs is a major factor for the companies, but also cited is the reduction in the pollution generated by traditional office working. However, the main driver for a shift to remote working may be surprising: The first reason they are going remote-first is simple -- it lets them hire more talented people Rather than hiring the best person in a 30-mile radius of the office, they can hire the best person in the world for every role Traditional ways of running a company have made it hard to bring about this change. But there is one sphere whose stunning success is built on this very shift. The world of free software and open source has embraced distributed teams working at home for nearly 30 years. This has allowed projects to select people on the basis of their skills, rather on their availability for a local office. It also means that people can work on what they are best at, and most interested in, rather than on what their local team needs them to do. As a result, open source software has gone from a bit of coding fun in the bedroom of a Finnish student, Linus Torvalds, to the dominant form of software in every field, with the lone exception of the desktop. Its success has also inspired a range of related movements, such as open access, open data, open science and many more. What's remarkable is that Linus did not set out to create this new kind of global, distributed software development methodology. It simply evolved from the time he placed his first, rough version of the Linux kernel on an FTP server in Finland, and invited people to download it freely. The crucial step was his willingness to accept suggestions to improve the code from anyone, provided they were good ones. That encouraged people to join the project, because they knew that there was no traditional business hierarchy based on seniority, just a meritocracy, where their suggestions would be accepted if their work was demonstrably better than the existing code. The companies that will thrive most from today's epochal shift to working from home will be those that are willing to implement similar ideas to those of Linus from 30 years ago, transposed to a general business context. Source
  18. App Manager v2.5.15 (Pre-release) (Open Source) jpg Yet another Android package manager and viewer but... 1. Copylefted libre software (GPLv3+) 2. Material design (and a nice UI) 3. No useless permissions 4. Does not connect to the Internet (the permission is required for ADB mode) 5. Displays as much info as possible in the main window 6. Lists activities, broadcast receivers, services, providers, permissions, signatures, shared libraries, etc. of any app 7. Launch (exportable) activities, create (customizable) shortcuts 8. Block any activities, broadcast receivers, services or providers you like with native import/export as well as Watt and Blocker import support (requires root) 9. Revoke permissions considered dangerous (requires root/ADB) 10. Disable app ops considered dangerous (requires root/ADB) 11. Scan for trackers in apps and list (all or only) tracking classes (and their code dump) 12. Generate dynamic manifest for any app 13. View/edit/delete shared preferences of any app (requires root) 14. Display running processes/apps (requires root/ADB) 15. Display your app usage, data usage and app storage info (requires “Usage Access” permission) 16. APK files can be shared (hence the use of a provider) 17. Clear app data or app cache (requires root/ADB) 18. Batch operations: clear app data, disable run in background, disable/kill/uninstall apps 19. One-click operations: block ads/tracker components, block components by signature, block multiple app ops …and other minor features such as installing/uninstalling/updating/enabling/disabling apps, displaying app installation info, opening on F-Droid, Aurora Droid or Aurora Store combining the features of 5 or 6 apps any tech-savvy person needs. Homepage Changelog Changelog: Download: AppManager_v2.5.15-arm64-v8a.apk AppManager_v2.5.15-armeabi-v7a.apk AppManager_v2.5.15-x86.apk AppManager_v2.5.15-x86_64.apk AppManager_v2.5.15.apk
  19. LibreAV v1.0.2 (10002) (Open Source Real Time Scanning Antivirus) LibreAV is an attempt to detect malware on Android devices using a machine learning approach that is powered by TensorFlow. We use a two-layer neural network trained with a carefully selected set of features. The neural network is tuned in such a way that it performs efficiently on mobile devices where computational resources are limited. Tests show that LibreAV performs efficiently and effectively even on low-end mobile devices. With LibreAV, you can scan all the installed apps in your device in a matter of seconds. It also has a realtime scan feature which alerts you whenever an app is installed or updated. Features • Real time scanning • On device inference • Lightweight • 100% free and no ads How it works? LibreAV uses permissions and intent-filters to detect malicious apps. While scanning, it loads the machine learning model and extracts permissions and intents from the installed applications on the user's device. These extracted features are then fed to the machine learning model in the form of a vector. The machine learning model returns a prediction score between 0 and 1 that denote the degree of maliciousness of the scanned application. We use this score to classify the scanned app into one of the following categories: 1. Goodware: The prediction score is less than 0.5 2. Risky: Prediction score between 0.5 and 0.75 3. Malware: Prediction score is greater than 0.75 4. Unknown: If LibreAV is unable to extract permissions and intents from an app, then that app is labelled as 'Unknown' You can check the code for building machine learning model here Homepage F-Droid Changelog Changelog: This is the first release of LibreAV on F-Droid. • Rebuilt the open-source library info screen with About Libraries • Updated the targetSdkVersion to 29 • Updated gradle version to 6.1.1 Download
  20. Google Launches Database for Open Source Vulnerabilities Google last week announced the launch of OSV (Open Source Vulnerabilities), which the internet giant has described as a vulnerability database and triage infrastructure for open source projects. OSV should make it easier for the users of open source software to find out which vulnerabilities impact them. It can also help maintainers of open source software accurately identify all versions and commits impacted by a flaw across all their branches. For consumers, Google says OSV provides a database that can be easily queried, with its goal being to complement existing vulnerability databases. “OSV automates the triage workflow for an open source package consumer by providing an API to query for vulnerabilities,” Google’s security team said in a blog post. In the case of maintainers, they can obtain information on the impact of vulnerabilities by providing the commit that introduced a bug and the commit that patched it. “Unfortunately, many open source projects, including ones that are critical to modern infrastructure, are under resourced and overworked. Maintainers don't always have the bandwidth to create and publish thorough, accurate information about their vulnerabilities even if they want to,” Google’s security experts said. OSV currently stores information on thousands of vulnerabilities from more than 380 critical open source projects integrated with Google’s OSS-Fuzz fuzzing service. However, the company wants to extend it with data from repositories such as npm Registry and PyPI. It also wants to make it very easy for developers to submit information on vulnerabilities. “Our goal with OSV is to rethink and promote better, scalable vulnerability tracking for open source. In an ideal world, vulnerability management should be done closer to the actual open source development process, aided by automated infrastructure. Projects that depend on open source should be promptly notified and fixes uptaken quickly when a vulnerability is reported,” Google said. Source: Google Launches Database for Open Source Vulnerabilities
  21. Open source Chromium browser shows up on the Microsoft Store If you've ever looked for web browsers in the Microsoft Store, you've probably come up short on finding anything at all. That's because according to Microsoft Store policy, any third-party browser needs to have the same rendering engine as its own Edge. But now, Edge runs on Chromium, which opens up the Store to a wide array of browsers. One of those is Chromium itself, which has now appeared on the Store, as spotted by Aggiornamenti Lumia. Chromium is an open source project that's managed by Google, but to be clear, this isn't being published by any big brand. It's published by a developer called Store Ports, who seemingly ran the browser through the Desktop App Converter and threw it up on the Store. The developer does have 10 other apps on the Store, some of which are also ports, and some aren't. One app is labeled as 'Universal (UWP) File Explorer', but the app description says that it's just a shortcut to the app that's hidden in Windows 10. If you want to check out Chromium on the Microsoft Store, you can find it here. It's unclear how often the browser will be updated. Open source Chromium browser shows up on the Microsoft Store
  22. Hemperor

    AM Downloader 1.1

    AM Downloader is a free, modern download manager for Windows. Support for parallel downloading of many items Pause and resume downloads Add download items using URL patterns Throttle speed to reduce network pressure Easy-to-use and modern interface 100% free and open-sourced Homepage: https://mozibsoft.com/amdownloader https://github.com/PocketAppZ/AM-Downloader Download: https://mozibsoft.com/downloads/amdownloader/AMDownloader1.1_Setup.msi
  23. Sos Gomes

    Freeplane 1.2.23

    Freeplane is a free and open source application for organising, visualising and sharing information. The program is a redesigned version of FreeMind, and can similarly be used to create mindmaps, although with more features and functionality. You can use Freeplane to build regular, static mindmaps, simple charts and diagrams which structure information. At its simplest you just press Ins to add a node; customise it, with an image, text, or icon; repeat the process to add other nodes, then link and organise them as you like. Freeplane goes further, though. This starts with smart tools to help you build better maps. So for instance conditional styling allows the program to automatically give nodes your preferred look and feel according to their hierarchical level in the map, as well as their content. That content can be very active. You can hide information within a node, present it on demand or automatically, organise it in folding branches, and use hyperlinks everywhere to help users navigate. Built-in calendar and reminder tools are useful for time and project management. There's DES encryption of individual nodes or the entire map. The program can be extended with scripts and some interesting addons. And once you've finished, the map can be shared as an image, an HTML page, via Flash and more. (In theory, anyway: from what we saw, the exported maps didn't always bear much relation to the original.) download link:http://cznic.dl.sourceforge.net/project/freeplane/freeplane%20stable/Freeplane-Setup-1.2.23_01.exe
  24. shamu726

    MKVToolNix 6.9.1

    MKVToolNix -- Cross-platform tools for Matroska MKVToolNix is a small collection of tools (mkvmerge, mkvinfo, mkvextract, mkvpropedit and mmg) that allows you to manipulate Matroska (MKV) files in several ways. You can use MKVToolNix to create, split, edit, mux, demux, merge, extract or inspect Matroska files. The program will also work with other video formats (AVI, MPEG, MP4, MPEG, Ogg/OGM, RealVideo, MPEG1/2, h264/AVC, Dirac, VC1) including some video codecs (such as VP9 video codec support - reading from IVF/Matroska/WebM files, extract to IVF files), audio (AAC, FLAC, MP2, MP3, (E)AC3, DTS/DTS-HD, Vorbis, RealAudio) and also most subtitle formats (SRT, PGS/SUP, VobSub, ASS, SSA etc.). This is a cross platform application that will work on Windows (both 32 and 64 bit versions), Mac OS X and Linux. Homepage ChangeLog Version 6.9.1 "Blue Panther" mkvmerge: bug fix: fixed huge memory usage when probing files (it was reading the whole file into memory for that).Version 6.9.0 "On Duende" all: new feature: added a Brazilian Portuguese translation of the programs by Thiago Kühn (see AUTHORS).mkvpropedit, mmg's header editor: bug fix: fixed a failed assertion in libEBML when writing the same changes twice to certain files (those for which a seek head with a single entry pointing to the elements modified by mkvpropedit/mmg's header editor; e.g. x264 creates such files). Fixes #1007.mkvmerge: bug fix: reading fonts embedded in SSA/ASS files was sometimes truncating the attachments created from them. Fixes #1003.mkvmerge: bug fix: fixed display of very large IDs during attachment extraction.mkvmerge: enhancement: improved file type detection speed for text subtitle formats.mkvextract: bug fix: during the extraction of chapters, tags or segment info XML files with the --redirect-output parameter the BOM (byte order mark) was written twice.mkvmerge: bug fix: MPEG TS: timestamp outliers are ignored if they differ at least five minutes from the last valid timestamp. Fixes #998.mkvmerge: enhancements: trailing zero bytes will be removed from AVC/h.264 NALUs. Implements #997.mkvmerge: bug fix: fixed timestamp assignment for AVC/h.264 videos in which recovery point SEIs occur in front of the second field of two interlaced fields.Full ChangeLog Download Windows installer (32bit) - 10.99 MB | SHA1: aaf7e15e75f185647b3bc3ed45b4239fe1a81671 Windows installer (64bit) - 11.50 MB | SHA1: bda4739cb057261cbe972718e98f67dde5557a66 Windows portable (32bit) - 9.65 MB | SHA1: 9c72b73a95bbb411eec670a09a188e19e95058d8 Windows portable (64bit) - 10.39 MB | SHA1: f776ef19735b41339643a6bde20478835f6d6e4b * Supported Windows versions are XP and newer from the client OS line and Windows Server 2008 and later from the server line. * For Mac OS X and Linux versions, visit the MKVToolNix homepage.
  25. shamu726

    Subtitle Edit 3.3.15

    Subtitle Edit is a free (open source) editor for video subtitles - a subtitle editor :) With SE you can easily adjust a subtitle if it is out of sync with the video in several different ways. You can also use SE for making new subtitles from scratch (do use the time-line/waveform/spectrogram) or translating subtitles. For a list of features see below or check out the Subtitle Edit Help page. On my blog you can download latest beta version and read about/discuss new features. Also, you can watch a few videos about installing and using Subtitle Edit. (Old videos.) Dny238 has written a nice tutorial about Syncing Subtitles with Subtitle Edit :) A Subtitle Edit dll (Subtitle Edit Light Library) is available for programmers (BSD New/Simplified license). Initially created and used by Sublight (a free Windows application for searching and downloading movie subtitles). Homepage Features: Create/adjust/sync/translate subtitle linesConvert between SubRib, MicroDVD, Advanced Sub Station Alpha, Sub Station Alpha, D-Cinema, SAMI, youtube sbv, and many more (170+ different formats!)Cool audio visualizer control - can display wave form and/or spectrogramVideo player uses DirectShow, VLC media player, or MPlayerVisually sync/adjust a subtitle (start/end position and speed)Auto Translation via Google translateRip subtitles from a (decrypted) dvdImport and OCR VobSub sub/idx binary subtitles (can use Tesseract)Import and OCR Blu-ray .sup files (can use Tesseract - bd sup reading is based on Java code from BDSup2Sub by 0xdeadbeef)Can open subtitles embedded inside matroska filesCan open subtitles (text, closed captions, vobsub) embedded inside mp4/mv4 filesCan open/OCR XSub subtitles embedded inside divx/avi filesCan open/OCR DVB subtitles embedded inside .ts (Transport Stream) filesCan open/OCR Blu-ray subtitles embedded inside .m2ts (Transport Stream) filesCan read and write both UTF-8 and other unicode files and ANSI (support for all languages/encodings on the pc!)Sync: Show texts earlier/later + point synchronization + synchronization via other subtitleMerge/split subtitlesAdjust display timeFix common errors wizardSpell checking via Open Office dictionaries/NHunspell (many dictionaries available)Remove text for hear impaired (HI)RenumberingSwedish to Danish translation built-in (via Multi Translator Online)Effects: Typewriter and karaokeHistory/undo manager (Undo=Ctrl+z, Redo=Ctrl+y)Compare subtitlesMultiple search and replaceChange casing using names dictionaryMerge short lines/split long linesExport to PNG images (+bdn xml), Adobe Encore FAB image script, VobSub, Blu-ray sup, EBU stl, PAC, and plain textSubtitle Edit is available in the following languages: Subtitle Edit can read, write, and convert between more than 170 subtitle formats, like: Screenshots: Subtitle Edit main window Change log: 3.3.15 (13th April 2014)New: Added new subtitle formats (200+ formats supported!)New: Export to VobSub option "Anti-alising with transparency" thx CoOoL_BoY/moobNew: Added ZPosition setting for DCinema interop - thx JosephNew: Added fade up/down to DCinema interop properties - thx RaulNew: Added shortcut for Tools -> "Split long lines" - thx JohnNew: Added shortcut for Sync -> "Change frame rate" - thx AlfonsoNew: Added setting regarding "Fix short display times" - thx S1l3nc0rNew: Added an "Update all" button for the plugin windowNew: Added UI setting for path to VLC portableNew: Added export to DCinema interop/png - thx JosephImproved: Updated French language file - thx JM GBTImproved: Updated Dutch language file - thx QuetsbeekImproved: Updated Portuguese language file - thx moobImproved: Updated Korean language file - thx domddolImproved: Updated Brazilian Portuguese language file - thx IgorImproved: Updated Polish language file - thx AdmasImproved: Updated Argentinian Spanish language file - thx walterh78Improved: Updated Spanish (Mexico) language file - thx pakitonaranjoImproved: HTML encoding of SAMI files is now again default falseImproved: Better reading of time codes of Blu-ray sup in mkv - thx Rach78Fixed: Fixed VobSub writing compatibility with gpac/mp4box + handbrake - thx RyanFixed: Minor fix for ass import from Matroska (mkv) filesFixed: Some fixes for move word up/down - thx rebawestFixed: Delete custom export format now works - thx LeonFixed: Possible crash in OCR window - thx grfilhoFixed: DCinema SMPTE sometimes generated illegal frame numbers - thx knutFixed: Fixed possible crash when converting pac to ttml - thx DanFixed: Fixed memory leak when running OCR via TesseractFixed: Fixed possible error/crash when loading bad time codes - thx JucáFrom next version SE will be compiled for .net framework 4 and use 64-bit where available, but a portable 32-bit .net framework version will still be released for a while. Download: For Windows XP users: SE requires Microsoft .NET Framework Version 2.0 - 3.5. SubtitleEdit-3.3.15-Setup.zip - Installer version, .NET 2-3.5, 32-bit (will run on win 64-bit too, but needs 32-bit codecs/VLC) - SHA1 Checksum: 74a4067493d6a560b068508c297b862821c476ff SE3315.zip - Portable version, .NET 2-3.5, 32-bit (will run on win 64-bit too, but needs 32-bit codecs/VLC) - This also works on Linux (when mono/mono-form/etc is installed) - Linux users should also look here: http://www.sub-talk.net/topic/2751-subtitle-edit-for-ubuntu-troubleshoting-tips-and-tricks/ - SHA1 Checksum: abda13df8a325adcc26588ec418948913ae18ced SE3315.Net4.zip - Portable version, .NET 4-4.5, 32/64-bit (will need 64-bit codecs/VLC on 64-bit machines) - SHA1 Checksum: ec43d2e7ae52b02cf5e9c6686214cd7880b32057
  • Create New...