Skip to main content

Home/ Future of the Web/ Group items tagged major

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Paul Merrell

Republicans seek fast-track repeal of net neutrality | Ars Technica - 0 views

arstechnica.com/...track-repeal-of-net-neutrality

net-neutrality legislation fast-track

shared by Paul Merrell on 26 Apr 15 - No Cached
  • Republicans in Congress yesterday unveiled a new plan to fast track repeal of the Federal Communications Commission's net neutrality rules. Introduced by Rep. Doug Collins (R-Ga.) and 14 Republican co-sponsors, the "Resolution of Disapproval" would use Congress' fast track powers under the Congressional Review Act to cancel the FCC's new rules.
  • Saying the resolution "would require only a simple Senate majority to pass under special procedural rules of the Congressional Review Act," Collins' announcement called it "the quickest way to stop heavy-handed agency regulations that would slow Internet speeds, increase consumer prices and hamper infrastructure development, especially in his Northeast Georgia district." Republicans can use this method to bypass Democratic opposition in the Senate by requiring just a simple majority rather than 60 votes to overcome a filibuster, but "it would still face an almost certain veto from President Obama," National Journal wrote. "Other attempts to fast-track repeals of regulations in the past have largely been unsuccessful." This isn't the only Republican effort to overturn the FCC's net neutrality rules. Another, titled the "Internet Freedom Act," would wipe out the new net neutrality regime. Other Republican proposals would enforce some form of net neutrality rules while limiting the FCC's power to regulate broadband.
  • The FCC's rules also face lawsuits from industry consortiums that represent broadband providers. USTelecom filed suit yesterday just after the publication of the rules in the Federal Register. Today, the CTIA Wireless Association, National Cable & Telecommunications Association (NCTA), and American Cable Association (ACA) all filed lawsuits to overturn the FCC's Open Internet Order. The CTIA and NCTA are the most prominent trade groups representing the cable and wireless industries. The ACA, which represents smaller providers, said it supports net neutrality rules but opposes the FCC's decision to reclassify broadband as a common carrier service. However, a previous court decision ruled that the FCC could not impose the rules without reclassifying broadband.
Gonzalo San Gil, PhD.

The Cloud vs. Open Source - Datamation - 0 views

www.datamation.com/...the-cloud-vs.-open-source.html

cloud open source

shared by Gonzalo San Gil, PhD. on 13 Jun 15 - No Cached
  • Gonzalo San Gil, PhD. on 13 Jun 15
     
    "For years, Linux and free software were perceived as threatened by cloud computing, the online storage of data. However, over the last few years, something ironic happened -- free software became a major player in cloud computing."
Gonzalo San Gil, PhD.

Ford, Toyota, Nissan, Microsoft 'Shamed' as Piracy Sponsors - TorrentFreak - 0 views

torrentfreak.com/amed-as-piracy-sponsors-151001

big companies sponsor piracy oh even certain politicians curious isn't it

shared by Gonzalo San Gil, PhD. on 01 Oct 15 - No Cached
  • Gonzalo San Gil, PhD. on 01 Oct 15
     
    " Andy on October 1, 2015 C: 32 Breaking Car manufacturers including Ford, Toyota, Nissan, Mazda and Volvo plus technology giant Microsoft are just a handful of the 100 major companies set to be outed as sponsors of piracy sites by the Russian government. The move is part of the growing "follow the money" campaign aimed at strangling the finances of 'pirate' sites."
Gonzalo San Gil, PhD.

Attacks on the Press: CPJ Risk List - Committee to Protect Journalists - 0 views

www.cpj.org/...on-the-press-cpj-risk-list.php

attacks press journalists free speech media

shared by Gonzalo San Gil, PhD. on 05 Nov 13 - No Cached
  • Gonzalo San Gil, PhD. on 05 Nov 13
     
    "By Karen Phillips Ecuadoran law forbids the presidential family to benefit from state contracts. But after Christian Zurita and Juan Carlos Calderón's book, Big Brother, revealed that President Rafael Correa's brother had obtained $600 million in government contracts, they were the ones in trouble with the law. Zurita and Calderón were found guilty of defaming the president and ordered to pay $1 million in damages apiece. Correa later pardoned the two, having accomplished his goal of intimidating the nation's press corps. "It was clear that no small or medium-sized media outlet was going to take on major critical reporting against the government," Zurita told CPJ."
Gary Edwards

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

quod.lib.umich.edu/...n-workflows-start-with-the-web

OpenWeb XML XHTML-CSS HTML5-CSS3-JavaScript IDML

shared by Gary Edwards on 07 Nov 13 - No Cached
  • 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
  • Gary Edwards on 07 Nov 13
     
    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
  • Gary Edwards on 07 Nov 13
     
    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
Gonzalo San Gil, PhD.

The Halloween Documents - 0 views

www.atm.damtp.cam.ac.uk/...halloween.html

halloween documents Microsoft vs opensource Linux

shared by Gonzalo San Gil, PhD. on 30 Aug 13 - No Cached
  • Gonzalo San Gil, PhD. on 30 Aug 13
     
    "Where will Microsoft try to drag you today? Do you really want to go there? In the last week of October 1998, a confidential Microsoft memorandum on Redmond's strategy against Linux and Open Source software was leaked to me by a source who shall remain nameless. I annotated this memorandum with explanation and commentary over Halloween Weekend and released it to the national press. Microsoft was forced to acknowledge its authenticity. The press rightly treated it as a major story and covered it (with varying degrees of cluefulness). "
Gonzalo San Gil, PhD.

Tested: How Flash destroys your browser's performance | ITworld - 1 views

www.itworld.com/...your-browsers-performance.html

tested Flash destroys Internet browser performance destruction

shared by Gonzalo San Gil, PhD. on 23 Aug 15 - No Cached
  • Gonzalo San Gil, PhD. on 23 Aug 15
     
    "We tested the effects of browsing with and without Flash on several major browsers. Enabling Flash is, in a word, catastrophic."
Gonzalo San Gil, PhD.

EU Starts Geo-Blocking Antitrust Case Against U.S Movie Studios - TorrentFreak - 0 views

torrentfreak.com/ainst-u-s-movie-studios-150723

EU starts geoblcking antitrust case against US movie studios intellectual property enforcers don't agree themselves

shared by Gonzalo San Gil, PhD. on 23 Jul 15 - No Cached
    • Gonzalo San Gil, PhD.
      Gonzalo San Gil, PhD. on 23 Jul 15
       
      # ! Oh, Oh: #IntellectualProperty 'Enforcers' # ! don't agree even among themselves...
  • Gonzalo San Gil, PhD. on 23 Jul 15
     
    [ By Ernesto on July 23, 2015 C: 41 Breaking The European Union has today launched an antitrust investigation against several large U.S. movie studios and Sky UK. The European Commission wants to abolish geographical restrictions and has sent a statement of objections over the geo-blocking practices of six major US film studios including Disney, Paramount Pictures and Warner Bros. ...]
Gonzalo San Gil, PhD.

How to Update Linux Kernel for Improved System Performance - 1 views

www.makeuseof.com/...el-improved-system-performance

how to update linux kernel improved system performance beyond current distro statte

shared by Gonzalo San Gil, PhD. on 26 Jul 15 - No Cached
  • Gonzalo San Gil, PhD. on 26 Jul 15
     
    " The rate of development for the Linux kernel is unprecedented, with a new major release approximately every two to three months. Each release offers several new features and improvements that a lot of people could take advantage of to make their computing experience faster, more efficient, or better in other ways."
Gonzalo San Gil, PhD.

Microsoft joins the Linux Foundation | It runs on Linux - 0 views

www.itrunsonlinux.com/...oft-joins-the-linux-foundation

microsoft joins Linux Foundation R Cosortium language for statistical data analysis

shared by Gonzalo San Gil, PhD. on 02 Jul 15 - No Cached
  • Gonzalo San Gil, PhD. on 02 Jul 15
     
    "The founding members of the R Consortium include other major corporations like Google, HP and Oracle. R is a rapidly evolving language for statistical data analysis that's driving innovation in the field of data sciences."
Gonzalo San Gil, PhD.

Studios Fed Up With Funding The MPAA: Changes May Be Coming | Techdirt - 0 views

www.techdirt.com/...aa-changes-may-be-coming.shtml

studios fed up funding MPAA so who they work for changes coming let's see

shared by Gonzalo San Gil, PhD. on 29 Jun 15 - No Cached
  • Gonzalo San Gil, PhD. on 29 Jun 15
     
    "from the about-time dept A few years ago, the major record labels finally started to realize that, perhaps, shoveling many millions of dollars to the RIAA was a waste of good money, and they severely cut back funds. You may have noticed that, while the RIAA had taken the lead on the copyright front in the first decade of the new century"
Gonzalo San Gil, PhD.

C: How cloud giants are joining forces against lock-in and fragmentation | ZDNet - 0 views

www.zdnet.com/...inst-lock-in-and-fragmentation

Open Container Project open containers project network cloud joint forces

shared by Gonzalo San Gil, PhD. on 06 Jul 15 - No Cached
  • Gonzalo San Gil, PhD. on 06 Jul 15
     
    "Announced today under the Linux Foundation banner, the Open Container Project has the backing of the major forces in cloud and containers, including Docker and appc."
Gonzalo San Gil, PhD.

David Guetta: Piracy Brings Fans to My Concerts | TorrentFreak - 0 views

torrentfreak.com/ngs-fans-to-my-concerts-150706

David Guetta DJ artist piracy brings fans concerts

shared by Gonzalo San Gil, PhD. on 06 Jul 15 - No Cached
  • Gonzalo San Gil, PhD. on 06 Jul 15
     
    " Ernesto on July 6, 2015 C: 17 News For more than a decade piracy has been a hot topic in the music industry. While some of the major labels have tried to eliminate the problem by taking pirates to court, others prefer a more positive approach. DJ and producer David Guetta says that the industry should embrace piracy, noting that it helps him to sell out concerts."
Gonzalo San Gil, PhD.

Mass protest against TTIP and CETA to take place in Berlin | EurActiv - 0 views

www.euractiv.com/...-ceta-take-place-berlin-317066

Mass protest against TTIP CETA place Berlin EurActiv

shared by Gonzalo San Gil, PhD. on 06 Sep 15 - No Cached
  • Gonzalo San Gil, PhD. on 06 Sep 15
     
    "More than 30 organisations are teaming up for a major demonstration against TTIP and CETA, with concerns ranging from the end of cultural diversity in Europe to devastating effects the deals could have in developing countries. EurActiv Germany reports."
Gonzalo San Gil, PhD.

Reasons Why Users Don't Like Ubuntu Software Center - Softpedia - 0 views

news.softpedia.com/...u-software-center-488541.shtml

reasons ubuntu users dislike software center

shared by Gonzalo San Gil, PhD. on 06 Aug 15 - No Cached
  • Gonzalo San Gil, PhD. on 06 Aug 15
     
    "Here is why people don't like Ubuntu Software Center The majority opinion in the Ubuntu community seems to be that the Ubuntu Software Center is a terrible piece of software and that it needs to be replaced or fixed urgently. We compiled a list of reasons why users don't like the application and why they think Canonical should really consider a change."
Paul Merrell

Activists send the Senate 6 million faxes to oppose cyber bill - CBS News - 0 views

www.cbsnews.com/...ion-faxes-to-oppose-cyber-bill

surveillance state CISA legislation faxes Obama

shared by Paul Merrell on 06 Aug 15 - No Cached
  • Activists worried about online privacy are sending Congress a message with some old-school technology: They're sending faxes -- more than 6.2 million, they claim -- to express opposition to the Cybersecurity Information Sharing Act (CISA).Why faxes? "Congress is stuck in 1984 and doesn't understand modern technology," according to the campaign Fax Big Brother. The week-long campaign was organized by the nonpartisan Electronic Frontier Foundation, the group Access and Fight for the Future, the activist group behind the major Internet protests that helped derail a pair of anti-piracy bills in 2012. It also has the backing of a dozen groups like the ACLU, the American Library Association, National Association of Criminal Defense Lawyers and others.
  • CISA aims to facilitate information sharing regarding cyberthreats between the government and the private sector. The bill gained more attention following the massive hack in which the records of nearly 22 million people were stolen from government computers."The ability to easily and quickly share cyber attack information, along with ways to counter attacks, is a key method to stop them from happening in the first place," Sen. Dianne Feinstein, D-California, who helped introduce CISA, said in a statement after the hack. Senate leadership had planned to vote on CISA this week before leaving for its August recess. However, the bill may be sidelined for the time being as the Republican-led Senate puts precedent on a legislative effort to defund Planned Parenthood.Even as the bill was put on the backburner, the grassroots campaign to stop it gained steam. Fight for the Future started sending faxes to all 100 Senate offices on Monday, but the campaign really took off after it garnered attention on the website Reddit and on social media. The faxed messages are generated by Internet users who visit faxbigbrother.com or stopcyberspying.com -- or who simply send a message via Twitter with the hashtag #faxbigbrother. To send all those faxes, Fight for the Future set up a dedicated server and a dozen phone lines and modems they say are capable of sending tens of thousands of faxes a day.
  • Fight for the Future told CBS News that it has so many faxes queued up at this point, that it may take months for Senate offices to receive them all, though the group is working on scaling up its capability to send them faster. They're also limited by the speed at which Senate offices can receive them.
  • Paul Merrell on 06 Aug 15
     
    From an Fight For the Future mailing: "Here's the deal: yesterday the Senate delayed its expected vote on CISA, the Cybersecurity Information Sharing Act that would let companies share your private information--like emails and medical records--with the government. "The delay is good news; but it's a delay, not a victory. "We just bought some precious extra time to fight CISA, but we need to use it to go big like we did with SOPA or this bill will still pass. Even if we stop it in September, they'll try again after that. "The truth is that right now, things are looking pretty grim. Democrats and Republicans have been holding closed-door meetings to work out a deal to pass CISA quickly when they return from recess. "Right before the expected Senate vote on CISA, the Obama Administration endorsed the bill, which means if Congress passes it, the White House will definitely sign it.  "We've stalled and delayed CISA and bills like it nearly half a dozen times, but this month could be our last chance to stop it for good." See also http://tumblr.fightforthefuture.org/post/125953876003/senate-fails-to-advance-cisa-before-recess-amid (;) http://www.cbsnews.com/news/activists-send-the-senate-6-million-faxes-to-oppose-cyber-bill/ (;) http://www.npr.org/2015/08/04/429386027/privacy-advocates-to-senate-cyber-security-bill (.)
Gonzalo San Gil, PhD.

Xfce: Seven Reasons It's Popular - Datamation - 1 views

www.datamation.com/...seven-reasons-its-popular.html

Xfce GNU_Linux desktop reasons rise popular ity

shared by Gonzalo San Gil, PhD. on 10 Aug 15 - No Cached
  • Gonzalo San Gil, PhD. on 10 Aug 15
     
    "Xfce has a long history of being the third most popular Linux desktop. For over a decade, it trailed behind GNOME and KDE. Then, a few years ago, during the revolts against GNOME and Unity, it became a major contender, "
Gonzalo San Gil, PhD.

The People Prevail: FCC Calls Off Closed-Door Meetings on Net Neutrality | Save the Int... - 0 views

www.savetheinternet.com/...d-door-meetings-net-neutrality

FCC Genachowski Net Neutrality Google Verizon closed-door meetings Called-Off people People's Rights prevail

shared by Gonzalo San Gil, PhD. on 08 Aug 10 - Cached
  • Gonzalo San Gil, PhD. on 08 Aug 10
     
    By Megan Tady, August 5, 2010 You called, you emailed and you signaled your outrage as the Federal Communications Commission continued to meet behind closed doors with Internet companies, and Google and Verizon hatched a side plan on how to manage the Internet. And then, you prevailed. Amidst a tidal wave of public pressure, FCC Chief of Staff Edward Lazarus called off closed-door negotiations with major ISPs and Internet companies, pledging "to seek broad input on this vital issue."
Paul Merrell

OpenSolaris Governance Board resigns - The H Open Source: News and Features - 0 views

www.h-online.com/...nce-Board-resigns-1064007.html

OpenSolaris Oracle Sun

shared by Paul Merrell on 31 Aug 10 - Cached
  • As it had previously threatened, the OpenSolaris Governance Board (OGB) has now resigned. The dissolution motion was proposed and passed unopposed in a fourteen minute long meeting of the OGB. The motion cited the fact that Oracle had ignored requests to see a liaison appointed to work with the OGB and had distributed an internal email terminating the OpenSolaris project. Another part of the dissolution motion stated, "The desire and enthusiasm for continuing open development of the OpenSolaris code base has clearly passed out of Oracle's (and thus this community's) hands into other communities" before resolving that the members of the OGB collectively resigned.
  • Paul Merrell on 31 Aug 10
     
    It's official now. OpenSolaris is abandonware, leaving OpenBSD as the major open Unix platform still supported.    
Gonzalo San Gil, PhD.

US consumers don't want web-enabled toasters * The Register - 4 views

www.theregister.co.uk/...web_connect_not

consumers don't embrace connected future technology marketers love

shared by Gonzalo San Gil, PhD. on 29 Sep 10 - No Cached
  • Gonzalo San Gil, PhD. on 29 Sep 10
     
    [And three-quarters downloaded nothing in last quarter By John Oates * Get more from this author Posted in Music and Media, 29th September 2010 11:31 GMT A survey of previous NPD research has found US consumers not fully embracing the connected future so beloved of tech marketeers. Researchers found that for most US users a PC, with email and web browsing, is enough. Although some are using games consoles and smartphones to get online the vast majority are not. ...]
« First ‹ Previous 81 - 100 of 242 Next › Last »
Showing 20▼ items per page