Skip to main content

Home/ Future of the Web/ Group items tagged Industry

Rss Feed Group items tagged

2More

Review: Puppet vs. Chef vs. Ansible vs. Salt | InfoWorld - 0 views

  •  
    "The leading configuration management and orchestration tools take different paths to server automation By Paul Venezia Follow InfoWorld | Nov 21, 2013 RELATED TOPICS Data Center Cloud Computing Server Provisioning The proliferation of virtualization coupled with the increasing power of industry-standard servers and the availability of cloud computing has led to a significant uptick in the number of servers that need to be managed within and without an organization"
  •  
    "The leading configuration management and orchestration tools take different paths to server automation By Paul Venezia Follow InfoWorld | Nov 21, 2013 RELATED TOPICS Data Center Cloud Computing Server Provisioning The proliferation of virtualization coupled with the increasing power of industry-standard servers and the availability of cloud computing has led to a significant uptick in the number of servers that need to be managed within and without an organization"
49More

XML Production Workflows? Start with the Web and XHTML - 0 views

  • Challenges: Some Ugly Truths The challenges of building—and living with—an XML workflow are clear enough. The return on investment is a long-term proposition. Regardless of the benefits XML may provide, the starting reality is that it represents a very different way of doing things than the one we are familiar with. The Word Processing and Desktop Publishing paradigm, based on the promise of onscreen, WYSIWYG layout, is so dominant as to be practically inescapable. It has proven really hard to get from here to there, no matter how attractive XML might be on paper. A considerable amount of organizational effort and labour must be expended up front in order to realize the benefits. This is why XML is often referred to as an “investment”: you sink a bunch of time and money up front, and realize the benefits—greater flexibility, multiple output options, searching and indexing, and general futureproofing—later, over the long haul. It is not a short-term return proposition. And, of course, the returns you are able to realize from your XML investment are commensurate with what you put in up front: fine-grained, semantically rich tagging is going to give you more potential for searchability and recombination than a looser, more general-purpose approach, but it sure costs more. For instance, the Text Encoding Initiative (TEI) is the grand example of pouring enormous amounts of energy into the up-front tagging, with a very open-ended set of possibilities down the line. TEI helpfully defines a level to which most of us do not have to aspire.[5] But understanding this on a theoretical level is only part of the challenge. There are many practical issues that must be addressed. Software and labour are two of the most critical. How do you get the content into XML in the first place? Unfortunately, despite two decades of people doing SGML and XML, this remains an ugly question.
  • Practical Challenges In 2009, there is still no truly likeable—let alone standard—editing and authoring software for XML. For many (myself included), the high-water mark here was Adobe’s FrameMaker, substantially developed by the late 1990s. With no substantial market for it, it is relegated today mostly to the tech writing industry, unavailable for the Mac, and just far enough afield from the kinds of tools we use today that its adoption represents a significant hurdle. And FrameMaker was the best of the breed; most of the other software in decent circulation are programmers’ tools—the sort of things that, as Michael Tamblyn pointed out, encourage editors to drink at their desks. The labour question represents a stumbling block as well. The skill-sets and mind-sets that effective XML editors need have limited overlap with those needed by literary and more traditional production editors. The need to think of documents as machine-readable databases is not something that comes naturally to folks steeped in literary culture. In combination with the sheer time and effort that rich tagging requires, many publishers simply outsource the tagging to India, drawing a division of labour that spans oceans, to put it mildly. Once you have XML content, then what do you do with it? How do you produce books from it? Presumably, you need to be able to produce print output as well as digital formats. But while the latter are new enough to be generally XML-friendly (e-book formats being largely XML based, for instance), there aren’t any straightforward, standard ways of moving XML content into the kind of print production environments we are used to seeing. This isn’t to say that there aren’t ways of getting print—even very high-quality print—output from XML, just that most of them involve replacing your prepress staff with Java programmers.
  • Why does this have to be so hard? It’s not that XML is new, or immature, or untested. Remember that the basics have been around, and in production, since the early 1980s at least. But we have to take account of a substantial and long-running cultural disconnect between traditional editorial and production processes (the ones most of us know intimately) and the ways computing people have approached things. Interestingly, this cultural divide looked rather different in the 1970s, when publishers were looking at how to move to digital typesetting. Back then, printers and software developers could speak the same language. But that was before the ascendancy of the Desktop Publishing paradigm, which computerized the publishing industry while at the same time isolating it culturally. Those of us who learned how to do things the Quark way or the Adobe way had little in common with people who programmed databases or document-management systems. Desktop publishing technology isolated us in a smooth, self-contained universe of toolbars, grid lines, and laser proofs. So, now that the reasons to get with this program, XML, loom large, how can we bridge this long-standing divide?
  • ...44 more annotations...
  • Using the Web as a Production Platform The answer, I think, is right in front of you. The bridge is the Web, a technology and platform that is fundamentally based on XML, and which many publishers are by now comfortably familiar with. Perhaps not entirely comfortably, but at least most publishers are already working with the Web; they already either know or have on staff people who understand it and can work with it. The foundation of our argument is this: rather than looking at jumping to XML in its full, industrial complexity, which seems to be what the O'Reilly-backed StartWithXML initiative[6] is suggesting, publishers instead leverage existing tools and technologies—starting with the Web—as a means of getting XML workflows in place. This means making small investments and working with known tools rather than spending tens of thousands of dollars on XML software and rarefied consultants. It means re-thinking how the existing pieces of the production toolchain fit together; re-thinking the existing roles of software components already in use. It means, fundamentally, taking the Web seriously as a content platform, rather than thinking of it as something you need to get content out to, somehow. If nothing else, the Web represents an opportunity to think about editorial and production from outside the shrink-wrapped Desktop Publishing paradigm.
  • Is the Web made of Real XML? At this point some predictable objections can be heard: wait a moment, the Web isn’t really made out of XML; the HTML that makes up most of the Web is at best the bastard child of SGML, and it is far too flaky/unstructured/underpowered to be taken seriously. We counter by arguing that although HTML on the Web exists in a staggering array of different incarnations, and that the majority of it is indeed an unstructured mess, this does not undermine the general principle that basic, ubiquitous Web technologies can make a solid platform for content management, editorial process, and production workflow.
  • With the advent of a published XML standard in the late 1990s came the W3C’s adoption of XHTML: the realization of the Web’s native content markup as a proper XML document type. Today, its acceptance is almost ubiquitous, even while the majority of actual content out there may not be strictly conforming. The more important point is that most contemporary Web software, from browsers to authoring tools to content management systems (from blogs to enterprise systems), are capable of working with clean, valid XHTML. Or, to put the argument the other way around, clean, valid XHTML content plays absolutely seamlessly with everything else on the Web.[7]
  • The objection which follows, then, will be that even if we grant that XHTML is a real XML document type, that it is underpowered for “serious” content because it is almost entirely presentation (formatting) oriented; it lacks any semantic depth. In XHTML, a paragraph is a paragraph is a paragraph, as opposed to a section or an epigraph or a summary.
  • n contrast, more “serious” XML document types like DocBook[8] or DITA-derived schemas[9] are capable of making semantic distinctions about content chunks at a fine level of granularity and with a high degree of specificity.
  • So there is an argument for recalling the 80:20 rule here. If XHTML can provide 80% of the value with just 20% of the investment, then what exactly is the business case for spending the other 80% to achieve that last 20% of value? We suspect the ratio is actually quite a bit steeper than 80:20 for most publishers.
  • Furthermore, just to get technical for a moment, XHTML is extensible in a fairly straightforward way, through the common “class” attribute on each element. Web developers have long leveraged this kind of extensibility in the elaboration of “microformats” for semantic-web applications.[10] There is no reason why publishers shouldn’t think to use XHTML’s simple extensibility in a similar way for their own ends.
  • XHTML, on the other hand, is supported by a vast array of quotidian software, starting with the ubiquitous Web browser. For this very reason, XHTML is in fact employed as a component part of several more specialized document types (ONIX and ePub among them).
  • Why re-invent a general-purpose prose representation when XHTML already does the job?
  • It is worth pausing for a moment to consider the role of XHTML in the ePub standard for ebook content. An ePub file is, anatomically, a simply disguised zip archive. Inside the zip archive are a few standard component parts: there are specialized files that declare metadata about the book, and about the format of the book. And then there is the book’s content, represented in XHTML. An ePub book is a Web page in a wrapper.
  • To sum up the general argument: the Web as it already exists presents incredible value to publishers, as a platform for doing XML content management with existing (and often free) tools, and without having to go blindly into the unknown. At this point, we can offer a few design guidelines: prefer existing and/or ubiquitous tools over specialized ones wherever possible; prefer free software over proprietary systems where possible; prefer simple tools controlled and coordinated by human beings over fully automated (and therefore complex) systems; play to our strengths: use Web software for storing and managing content, use layout software for layout, and keep editors and production people in charge of their own domains.
  • Putting the Pieces Together: A Prototype
  • At the SFU Master of Publishing Program, we have been chipping away at this general line of thinking for a few years. Over that time, Web content management systems have been getting more and more sophisticated, all the while getting more streamlined and easier to use. (NB: if you have a blog, you have a Web content management system.) The Web is beginning to be recognized as a writing and editing environment used by millions of people. And the ways in which content is represented, stored, and exchanged online have become increasingly robust and standardized.
  • The missing piece of the puzzle has been print production: how can we move content from its malleable, fluid form on line into the kind of high-quality print production environments we’ve come to expect after two decades of Desktop Publishing?
  • Anyone who has tried to print Web content knows that the existing methods leave much to be desired (hyphenation and justification, for starters). In the absence of decent tools for this, most publishers quite naturally think of producing the print content first, and then think about how to get material onto the Web for various purposes. So we tend to export from Word, or from Adobe, as something of an afterthought.
  • While this sort of works, it isn’t elegant, and it completely ignores the considerable advantages of Web-based content management.
  • Content managed online is stored in one central location, accessible simultaneously to everyone in your firm, available anywhere you have an Internet connection, and usually exists in a much more fluid format than Word files. If only we could manage the editorial flow online, and then go to print formats at the end, instead of the other way around. At SFU, we made several attempts to make this work by way of the supposed “XML import” capabilities of various Desktop Publishing tools, without much success.[12]
  • In the winter of 2009, Adobe solved this part of the problem for us with the introduction of its Creative Suite 4. What CS4 offers is the option of a complete XML representation of an InDesign document: what Adobe calls IDML (InDesign Markup Language).
  • The IDML file format is—like ePub—a simply disguised zip archive that, when unpacked, reveals a cluster of XML files that represent all the different facets of an InDesign document: layout spreads, master pages, defined styles, colours, and of course, the content.
  • IDML is a well thought-out XML standard that achieves two very different goals simultaneously: it preserves all of the information that InDesign needs to do what it does; and it is broken up in a way that makes it possible for mere mortals (or at least our Master of Publishing students) to work with it.
  • What this represented to us in concrete terms was the ability to take Web-based content and move it into InDesign in a straightforward way, thus bridging Web and print production environments using existing tools and skillsets, with a little added help from free software.
  • We would take clean XHTML content, transform it to IDML-marked content, and merge that with nicely designed templates in InDesign.
  • The result is an almost push-button publication workflow, which results in a nice, familiar InDesign document that fits straight into the way publishers actually do production.
  • Tracing the steps To begin with, we worked backwards, moving the book content back to clean XHTML.
  • The simplest method for this conversion—and if you want to create Web content, this is an excellent route—was to use Adobe’s “Export to Digital Editions” option, which creates an ePub file.
  • Recall that ePub is just XHTML in a wrapper, so within the ePub file was a relatively clean XHTML document. It was somewhat cleaner (that is, the XHTML tagging was simpler and less cluttered) than InDesign’s other Web-oriented exports, possibly because Digital Editions is a well understood target, compared with somebody’s website.
  • In order to achieve our target of clean XHTML, we needed to do some editing; the XHTML produced by InDesign’s “Digital Editions” export was presentation-oriented. For instance, bulleted list items were tagged as paragraphs, with a class attribute identifying them as list items. Using the search-and-replace function, we converted such structures to proper XHTML list and list-item elements. Our guiding principle was to make the XHTML as straightforward as possible, not dependent on any particular software to interpret it.
  • We broke the book’s content into individual chapter files; each chapter could then carry its own basic metadata, and the pages conveniently fit our Web content management system (which is actually just a wiki). We assembled a dynamically generated table of contents for the 12 chapters, and created a cover page. Essentially, the book was entirely Web-based at this point.
  • When the book chapters are viewed online, they are formatted via a CSS2 stylesheet that defines a main column for content as well as dedicating screen real estate for navigational elements. We then created a second template to render the content for exporting; this was essentially a bare-bones version of the book with no navigation and minimal styling. Pages (or even the entire book) can be exported (via the “Save As...” function in a Web browser) for use in either print production or ebook conversion. At this point, we required no skills beyond those of any decent Web designer.
  • Integrating with CS4 for Print Adobe’s IDML language defines elements specific to InDesign; there is nothing in the language that looks remotely like XHTML. So a mechanical transformation step is needed to convert the XHTML content into something InDesign can use. This is not as hard as it might seem.
  • Both XHTML and IDML are composed of straightforward, well-documented structures, and so transformation from one to the other is, as they say, “trivial.” We chose to use XSLT (Extensible Stylesheet Language Transforms) to do the work. XSLT is part of the overall XML specification, and thus is very well supported in a wide variety of tools. Our prototype used a scripting engine called xsltproc, a nearly ubiquitous piece of software that we found already installed as part of Mac OS X (contemporary Linux distributions also have this as a standard tool), though any XSLT processor would work.
  • In other words, we don’t need to buy InCopy, because we just replaced it with the Web. Our wiki is now plugged directly into our InDesign layout. It even automatically updates the InDesign document when the content changes. Credit is due at this point to Adobe: this integration is possible because of the open file format in the Creative Suite 4.
  • We wrote an XSLT transformation script[18] that converted the XHTML content from the Web into an InCopy ICML file. The script itself is less than 500 lines long, and was written and debugged over a period of about a week by amateurs (again, the people named at the start of this article). The script runs in a couple of seconds, and the resulting .icml file can then be “placed” directly into an InDesign template. The ICML file references an InDesign stylesheet, so the template file can be set up with a house-styled layout, master pages, and stylesheet definitions for paragraphs and character ranges.
  • The result is very simple and easy to use. Our demonstration requires that a production editor run the XSLT transformation script manually, but there is no reason why this couldn’t be built directly into the Web content management system so that exporting the content to print ran the transformation automatically. The resulting file would then be “placed” in InDesign and proofed.
  • It should be noted that the Book Publishing 1 proof-of-concept was artificially complex; we began with a book laid out in InDesign and ended up with a look-alike book laid out in InDesign. But next time—for instance, when we publish Book Publishing 2—we can begin the process with the content on the Web, and keep it there throughout the editorial process. The book’s content could potentially be written and edited entirely online, as Web content, and then automatically poured into an InDesign template at proof time. “Just in time,” as they say. This represents an entirely new way of thinking of book production. With a Web-first orientation, it makes little sense to think of the book as “in print” or “out of print”—the book is simply available, in the first place online; in the second place in derivative digital formats; and third, but really not much more difficult, in print-ready format, via the usual InDesign CS print production system publishers are already familiar with.
  • Creating Ebook Files Creating electronic versions from XHTML source is vastly simpler than trying to generate these out of the existing print process. The ePub version is extremely easy to generate; so is online marketing copy or excerpts for the Web, since the content begins life Web-native.
  • Since an ePub file is essentially XHTML content in a special wrapper, all that is required is that we properly “wrap” our XHTML content. Ideally, the content in an ePub file is broken into chapters (as ours was) and a table of contents file is generated in order to allow easy navigation within an ebook reader. We used Julian Smart’s free tool eCub[19] to simply and automatically generate the ePub wrapper and the table of contents. The only custom development we did was to create a CSS stylesheet for the ebook so that headings and paragraph indents looked the way we wanted. Starting with XHTML content, creating ePub is almost too easy.
  • Such a workflow—beginning with the Web and exporting to print—is surely more in line with the way we will do business in the 21st century, where the Web is the default platform for reaching audiences, developing content, and putting the pieces together. It is time, we suggest, for publishers to re-orient their operations and start with the Web.
  • Our project demonstrates that Web technologies are indeed good enough to use in an XML-oriented workflow; more specialized and expensive options are not necessarily required. For massive-scale enterprise publishing, this approach may not offer enough flexibility, and the challenge of adding and extracting extra semantic richness may prove more trouble than it's worth.
  • But for smaller firms who are looking at the straightforward benefits of XML-based processes—single source publishing, online content and workflow management, open and accessible archive formats, greater online discoverability—here is a way forward.
  • Rather than a public-facing website, our system relies on the Web as a content management platform—of course a public face could easily be added.
  • The final piece of our puzzle, the ability to integrate print production, was made possible by Adobe's release of InDesign with an open XML file format. Since the Web's XHTML is also XML, is can be easily and confidently transformed to the InDesign format.
  • today, we are able to put the process together using nothing but standard, relatively ubiquitous Web tools: the Web itself as an editing and content management environment, standard Web scripting tools for the conversion process, and the well-documented IDML file format to integrate the layout tool.
  • Using the Web as a Production Platform
  •  
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to
  •  
    I was looking for an answer to a problem Marbux had presented, and found this interesting article.  The issue was that of the upcoming conversion of the Note Case Pro (NCP) layout engine to the WebKit layout engine, and what to do about the NCP document format. My initial reaction was to encode the legacy NCP document format in XML, and run an XSLT to a universal pivot format like TEI-XML.  From there, the TEI-XML community would provide all the XSLT transformation routines for conversion to ODF, OOXML, XHTML, ePUB and HTML/CSS. Researching the problems one might encounter with this approach, I found this article.  Fascinating stuff. My take away is that TEI-XML would not be as effective a "universal pivot point" as XHTML.  Or perhaps, if NCP really wants to get aggressive; IDML - InDesign Markup Language. The important point though is that XHTML is a browser specific version of XML, and compatible with the Web Kit layout engine Miro wants to move NCP to. The concept of encoding an existing application-specific format in XML has been around since 1998, when XML was first introduced as a W3C standard, a "structured" subset of SGML. (HTML is also a subset of SGML). The multiplatform StarOffice productivity suite became "OpenOffice" when Sun purchased the company in 1998, and open sourced the code base. The OpenOffice developer team came out with a XML encoding of their existing document formats in 2000. The application specific encoding became an OASIS document format standard proposal in 2002 - also known as ODF. Microsoft followed OpenOffice with a XML encoding of their application-specific binary document formats, known as OOXML. Encoding the existing NCP format in XML, specifically targeting XHTML as a "universal pivot point", would put the NCP Outliner in the Web editor category, without breaking backwards compatibility. The trick is in the XSLT conversion process. But I think that is something much easier to handle then trying to
3More

French Magazine Fined €10,000 For Encouraging Piracy | TorrentFreak [# ! Note] - 0 views

    • Gonzalo San Gil, PhD.
       
      # ! 'Encouraging': what a shady wording... # ! Does TV News 'encourage' wars or Movies killings, scams and all the crimes they show to the people...? # ! Anyone could say so...
  •  
    [ Ernesto on June 30, 2015 C: 62 Breaking The music industry has won a landmark ruling in France where a local magazine was fined €10,000 for showing readers how and where pirated films and music can be downloaded. The ruling is the first of its kind and serves as a warning to other publications that write about online piracy. ...]
  •  
    [ Ernesto on June 30, 2015 C: 62 Breaking The music industry has won a landmark ruling in France where a local magazine was fined €10,000 for showing readers how and where pirated films and music can be downloaded. The ruling is the first of its kind and serves as a warning to other publications that write about online piracy. ...]
1More

If Streaming Is Growing So Fast, Why Isn't the Music Industry? - Digital Music NewsDigi... - 0 views

  •  
    "Monday, September 21, 2015 by Paul Resnikoff Streaming is exploding this year, across all format types: paid, ad-supported, and online radio…"
2More

Reminder 1: Copyright Monopoly Infringement Isn't Stealing (Says The US Supreme Court) ... - 0 views

  •  
    "Over the Yule holidays, I'll be running a series of reminders of some of the most useful talkbacks. We open with one of the more common ones: copyright industry lawyers tend to insist that violation of the copyright monopoly is "stealing". But in the judicial field, lawyers always go by what the courts say, and the US Supreme Court says it isn't."
  •  
    "Over the Yule holidays, I'll be running a series of reminders of some of the most useful talkbacks. We open with one of the more common ones: copyright industry lawyers tend to insist that violation of the copyright monopoly is "stealing". But in the judicial field, lawyers always go by what the courts say, and the US Supreme Court says it isn't."
2More

3 Financial Companies Innovating With Open Source | Linux.com - 0 views

  •  
    "The financial industry is on the verge of an open source breakthrough, say three companies on the cutting edge of the trend. Traditionally very secretive about their technology, banks, hedge funds and other financial services companies have begun in the past few years to talk about how they use open source software in their infrastructure and product development."
  •  
    "The financial industry is on the verge of an open source breakthrough, say three companies on the cutting edge of the trend. Traditionally very secretive about their technology, banks, hedge funds and other financial services companies have begun in the past few years to talk about how they use open source software in their infrastructure and product development."
1More

Anatomically distinct dopamine release during anticipation and experience of peak emoti... - 2 views

  •  
    [Music, an abstract stimulus, can arouse feelings of euphoria and craving, similar to tangible rewards that involve the striatal dopaminergic system. ...] *Is The Eagerness of The Industry, The Governments and the artists themselves to Control The Music Flow thru internet an Attempt to Control Human Emotions...?
2More

The Connection Between The Copyright Industry And The NSA | TorrentFreak - 1 views

  •  
    " Rick Falkvinge on May 18, 2014 C: 21 Opinion There is a direct connection between copyright monopoly enforcement and mass surveillance, and between mass surveillance and lack of free speech. If you want to keep free speech, the copyright monopoly must be reduced sharply."
  •  
    " Rick Falkvinge on May 18, 2014 C: 21 Opinion There is a direct connection between copyright monopoly enforcement and mass surveillance, and between mass surveillance and lack of free speech. If you want to keep free speech, the copyright monopoly must be reduced sharply."
2More

Illegal Copying Has Always Created Jobs, Growth, And Prosperity | TorrentFreak - 0 views

  •  
    " Rick Falkvinge on October 19, 2014 C: 33 Opinion Throughout history, those who have copied the most have also always been the most prosperous, and for that reason. Bans on copying, like the copyright and patent monopolies, are just plain industrial protectionism."
  •  
    " Rick Falkvinge on October 19, 2014 C: 33 Opinion Throughout history, those who have copied the most have also always been the most prosperous, and for that reason. Bans on copying, like the copyright and patent monopolies, are just plain industrial protectionism."
2More

Copyright Law as a Tool for State Censorship of the Internet | Electronic Frontier Foun... - 1 views

  •  
    "When state officials seek to censor online speech, they're going to use the quickest and easiest method available. For many, copyright takedown notices do the trick. After years of lobbying and increasing pressure from content industries on policymakers and tech companies, sending copyright notices to take media offline is easier than ever."
  •  
    "When state officials seek to censor online speech, they're going to use the quickest and easiest method available. For many, copyright takedown notices do the trick. After years of lobbying and increasing pressure from content industries on policymakers and tech companies, sending copyright notices to take media offline is easier than ever."
2More

Global Net Neutrality Coalition | Blog | Access - 0 views

  •  
    "Anyone who thinks that net neutrality is a boring technical issue for computer geeks needs to look outside the U.S. Netizens around the world aren't fooled by the confusing misdirection of industry lobbyists-they're championing the cause of an open internet by pushing for laws and policies that protect the features that made the internet what it is today." [ # ! #Globalization'... # ! ... for a #Good #Cause. # ! #Participate.]
  •  
    "Anyone who thinks that net neutrality is a boring technical issue for computer geeks needs to look outside the U.S. Netizens around the world aren't fooled by the confusing misdirection of industry lobbyists-they're championing the cause of an open internet by pushing for laws and policies that protect the features that made the internet what it is today."
2More

"How To Learn Absolutely Nothing In Fifteen Years," By The Copyright Industry | Torrent... - 0 views

  •  
    " By Rick Falkvinge on December 15, 2014 C: 0 Opinion The Pirate Bay was shut down this week. Whether or not it resurfaces, that event has already triggered a wave of innovation that will spawn exciting new sharing technologies over the coming years, just like when Napster was shut down fifteen years ago" [# ! The #worst… # ! … #ignorance is the #refusal to be #taught.]
  •  
    " By Rick Falkvinge on December 15, 2014 C: 0 Opinion The Pirate Bay was shut down this week. Whether or not it resurfaces, that event has already triggered a wave of innovation that will spawn exciting new sharing technologies over the coming years, just like when Napster was shut down fifteen years ago"
2More

Children Are Leading The Cord Cutting Revolution | Techdirt - 1 views

  •  
    "from the mikey-doesn't-like-it dept The cable industry has long pretended that the cord cutting phenomenon either isn't real or that the only people cutting the cord are aging losers living in their parents' basement. Of course when you actually look at the data, while cord cutting remains a slow but growing phenomenon, most of the cord cutters are young, highly educated, employed, and make a good amount of money." [# ! … #Freedom from The #Start: #Good #Move. # ! Notwithstanding '#OldSchool' #manipulators' #criticism…]
  •  
    "from the mikey-doesn't-like-it dept The cable industry has long pretended that the cord cutting phenomenon either isn't real or that the only people cutting the cord are aging losers living in their parents' basement. Of course when you actually look at the data, while cord cutting remains a slow but growing phenomenon, most of the cord cutters are young, highly educated, employed, and make a good amount of money."
2More

An Important Kindle request - 0 views

  • A Message from the Amazon Books Team Dear Readers, Just ahead of World War II, there was a radical invention that shook the foundations of book publishing. It was the paperback book. This was a time when movie tickets cost 10 or 20 cents, and books cost $2.50. The new paperback cost 25 cents — it was ten times cheaper. Readers loved the paperback and millions of copies were sold in just the first year. With it being so inexpensive and with so many more people able to afford to buy and read books, you would think the literary establishment of the day would have celebrated the invention of the paperback, yes? Nope. Instead, they dug in and circled the wagons. They believed low cost paperbacks would destroy literary culture and harm the industry (not to mention their own bank accounts). Many bookstores refused to stock them, and the early paperback publishers had to use unconventional methods of distribution — places like newsstands and drugstores. The famous author George Orwell came out publicly and said about the new paperback format, if "publishers had any sense, they would combine against them and suppress them." Yes, George Orwell was suggesting collusion. Well… history doesn't repeat itself, but it does rhyme.
  • Fast forward to today, and it's the e-book's turn to be opposed by the literary establishment. Amazon and Hachette — a big US publisher and part of a $10 billion media conglomerate — are in the middle of a business dispute about e-books. We want lower e-book prices. Hachette does not. Many e-books are being released at $14.99 and even $19.99. That is unjustifiably high for an e-book. With an e-book, there's no printing, no over-printing, no need to forecast, no returns, no lost sales due to out of stock, no warehousing costs, no transportation costs, and there is no secondary market — e-books cannot be resold as used books. E-books can and should be less expensive. Perhaps channeling Orwell's decades old suggestion, Hachette has already been caught illegally colluding with its competitors to raise e-book prices. So far those parties have paid $166 million in penalties and restitution. Colluding with its competitors to raise prices wasn't only illegal, it was also highly disrespectful to Hachette's readers. The fact is many established incumbents in the industry have taken the position that lower e-book prices will "devalue books" and hurt "Arts and Letters." They're wrong. Just as paperbacks did not destroy book culture despite being ten times cheaper, neither will e-books. On the contrary, paperbacks ended up rejuvenating the book industry and making it stronger. The same will happen with e-books.
2More

The Copyright Lobotomy: How Intellectual Property Makes Us Pretend To Be Stupid | Techdirt - 0 views

  •  
    "from the or:-how-to-build-an-intellectual-cage dept Here are two words that have no business hanging out together: "used MP3s." If you know anything about how computers work, that concept is intellectually offensive. Same goes for "ebook lending", "digital rental" and a host of other terms that have emerged from the content industries' desperate scramble to do the impossible: adapt without changing. "
  •  
    "from the or:-how-to-build-an-intellectual-cage dept Here are two words that have no business hanging out together: "used MP3s." If you know anything about how computers work, that concept is intellectually offensive. Same goes for "ebook lending", "digital rental" and a host of other terms that have emerged from the content industries' desperate scramble to do the impossible: adapt without changing. "
2More

That Study In Every Paper Claiming Title II Will Result In $15 Billion In New Taxes? Ye... - 1 views

  •  
    "As also noted, the claim was quickly picked up by media outlets and large ISP executives as the centerpiece of a campaign to convince the press, public and regulators that Title II will result in the sky falling. The cable industry was also quick to use the study as the underpinning of a series of ads pretending they care about soaring consumer bills (adorabl"
  •  
    "As also noted, the claim was quickly picked up by media outlets and large ISP executives as the centerpiece of a campaign to convince the press, public and regulators that Title II will result in the sky falling. The cable industry was also quick to use the study as the underpinning of a series of ads pretending they care about soaring consumer bills (adorabl"
2More

Fans Aren't Going To Pay For Music Anymore. And That's Ok. - Digital Music NewsDigital ... - 0 views

  •  
    "It's almost a rite of passage every artist goes through in the modern music industry. The moment he accepts that he will not be able to rely on music sales to sustain his career. That people are not buying music like they used to. And never will again."
  •  
    "It's almost a rite of passage every artist goes through in the modern music industry. The moment he accepts that he will not be able to rely on music sales to sustain his career. That people are not buying music like they used to. And never will again."
2More

In Memory Of The Liberties Lost In The War on Piracy | TorrentFreak - 0 views

  •  
    " Rick Falkvinge on February 2, 2015 C: 0 Opinion In order to prevent us from discussing and sharing interesting things, the copyright industry has successfully eliminated civil liberties online. But it was all down to a wrong and stupid business assumption in the first place."
  •  
    " Rick Falkvinge on February 2, 2015 C: 0 Opinion In order to prevent us from discussing and sharing interesting things, the copyright industry has successfully eliminated civil liberties online. But it was all down to a wrong and stupid business assumption in the first place."
2More

Piracy Is Just Another Copyright Industry Scapegoat | TorrentFreak - 0 views

  •  
    " Rick Falkvinge on March 16, 2015 C: 0 Opinion History repeats itself. Unlicensed home manufacturing of copies was never the cause of the copyright industry's business problems; they created those all on their own. It's not the first time they've appointed a scapegoat for their own failures to get public funding, either."
  •  
    " Rick Falkvinge on March 16, 2015 C: 0 Opinion History repeats itself. Unlicensed home manufacturing of copies was never the cause of the copyright industry's business problems; they created those all on their own. It's not the first time they've appointed a scapegoat for their own failures to get public funding, either."
2More

The File-Sharing Wars Are Anything But Over | TorrentFreak - 0 views

  •  
    " Rick Falkvinge on June 29, 2014 C: 7 Opinion The past year, the copyright industry appears to have calmed down a bit, thinking it won the file-sharing wars. At the same time, people sharing culture and knowledge have done the same thing. This conflict is far from over."
  •  
    " Rick Falkvinge on June 29, 2014 C: 7 Opinion The past year, the copyright industry appears to have calmed down a bit, thinking it won the file-sharing wars. At the same time, people sharing culture and knowledge have done the same thing. This conflict is far from over."
« First ‹ Previous 61 - 80 of 290 Next › Last »
Showing 20 items per page