The prohibition on reporting bugs in systems with DRM makes those bugs last longer, and get exploited harder before they're patched. Last summer, the US Copyright Office collected evidence about DRM interfering with reporting bugs in tractors, cars, medical implants, and critical national infrastructure.
https://www.eff.org/document/library-congress-2015-dmca-1201-rules
DRM exists to stop users from doing things they want to do and to stop innovative companies from helping users do things they want to do -- or would want to do, if they had the option. Your cable box, for example, will be designed to stop you from recording your favorite shows for long-term storage and viewing on the go.
The World Wide Web Consortium (W3C), the nonprofit body that maintains the Web's core standards, made a terrible mistake in 2013: they decided to add DRM
https://www.eff.org/deeplinks/2013/10/lowering-your-standards
The Internet is like sensation. The World Wide Web is like thinking.
I like this simple explanation.
does anyone not use Chrome?
I think that plenty of users, perhaps especially those keen on open source, prefer Firefox.
by Michael Nielsen on August 10, 2012 More precisely, I crawled 250,113,669 pages for just under 580 dollars in 39 hours and 25 minutes, using 20 Amazon EC2 machine instances.
Incredible that the "screenshort" hack is now getting integrated into Twitter itself. But it's still not web annotation!
Comparison of AngularJS 2 and ReactJS.
Angular is a full framework. React is a library. The latter involves more decisions about other packages, and more differences among projects.
React uses JSX, an HTML-like syntax that compiles to JavaScript. It can tell you where your mistakes are. With Angular, you have to guess.
Set Semantics¶ This tool is used to set semantics in EPUB files. Semantics are simply, links in the OPF file that identify certain locations in the book as having special meaning. You can use them to identify the foreword, dedication, cover, table of contents, etc. Simply choose the type of semantic information you want to specify and then select the location in the book the link should point to. This tool can be accessed via Tools->Set semantics.
Though it’s described in such a simple way, there might be hidden power in adding these tags, especially when we bring eBooks to the Semantic Web. Though books are the prime example of a “Web of Documents”, they can also contribute to the “Web of Data”, if we enable them. It might take long, but it could happen.
export books as apps
On top of the whole debate between native apps and the Open Web, there’s a debate between apps and books. We might not reach the “Write Once, Publish Everywhere” dream, but there’s something to be said about having building blocks which are easy to adapt to different contexts.
online commerce sites wanted customers to write in credit card numbers, mailing addresses, product reviews, and so on.
So the active readership of web 2.0 is directly linked to the consumerism of the commercial web?...
I'm so interested in the implications here: the democratization of the web, the breakdown of author/reader, producer/consumer (of knowledge), is rooted in capitalism?
One of the great things about the new Web is that you can manipulate text, but the iPad treats you like a child.
Everything we do to make it harder to create a website or edit a web page, and harder to learn to code by viewing source, promotes that consumerist vision of the web. Pretending that one needs a team of professionals to put simple articles online will become a self-fulfilling prophecy.
Humorous talk on website bloat by Maciej Cegłowski, creator of the Pinboard bookmarking service.
Streaming torrent client for browsers and NodeJS, implemented completely in JavaScript with WebRTC.
Video discussion of the Babel JavaScript transpiler.
Pamela Fox on careers that involve both coding and teaching.
A personal API builds on the domain concept—students store information on their site, whether it’s class assignments, financial aid information or personal blogs, and then decide how they want to share that data with other applications and services. The idea is to give students autonomy in how they develop and manage their digital identities at the university and well into their professional lives
The core set of functionality we've tried to capture in the HTML5 video compositor is the timing and synchronisation of the playback of videos and other media sources. The library allows you to cut together two separate videos near seamlessly, synchronise the playback of multiple videos in parallel and manage the pre-loading of videos in a just-in-time fashion.
The BBC is open sourcing their experimental HTML5 Video Compositor. "This is an experimental JavaScript library for playing back dynamically modifiable edit decision lists (EDLs), and applying WebGL shader based effects."
At a fundamental level, URLs have been there right from the start and are a key ingredient of the web. Once you know the name of something, you can pass it around, write it down, or send it in an email. Now someone has access to that exact point within an application or document. That's pretty big. That's where native platforms are trying to compete with the web. They're trying to get what the web already has.
Some of the reasons we need to keep the Internet free and open:
(This article already has 324 responses.)
personal note taking, peer review, copy editing, post publication discussion, journal clubs, classroom uses, automated classification, deep linking
Useful list, almost a roadmap or set of scenarios. The last two might be especially intriguing, in view of the Semantic Web.
deep linking
Ah, yes! It may sound technical to some, but there’s something very useful about deep linking which can help fulfill Berners-Lee’s Semantic Web idea much more appropriately than what is currently available. Despite so many advances in Web publishing (and the growing interest in Linked Open Data), it’s often difficult to link directly to an online item of interest. In a way, Hypothesis almost allows readers to add anchor tags to an element so it can be used in a direct link.
Good overview of how the Web works: client-server, url, http, dns, tcp/ip, packets, dom. Preethi Kasireddy Also here
Ethereum is 'a decentralized platform that runs smart contracts.' ... Here, we're sharing some simple instructions on how to get started with Ethereum
https://ethereum.org/<br> https://en.wikipedia.org/wiki/Ethereum
add tags for categorization and search
Well-structured annotations can pave the way towards Linked Open Data.
on top of the Web
Funny how this layering stacks up. What’s “under” the Web is probably the backend. But there’s depth in annotation and the structure created is more complex than a simple superposition.
distributed curation
While “web curation” is well-established as a practice, there’s still a lot of work to do on what it represents, conceptually and epistemologically.
tout enregistrement MLR conforme au profil Normetic 2.0 est automatiquement conforme au profil d’application MLR de base.
L’interopérabilité est essentielle à l’avènement du Web des données liées (en éducation comme ailleurs).
In Application Shell Architecture, the shell is served up by the Service Worker and then the content is delivered—often cached by the Service Worker—dynamically from its source through API requests.
"Progressive Web Apps", an idea for better mobile performance using HTML5 Service Workers.
Based on Flexbox (CSS Flexible Box Layout Module), Gridlex is a very simple css grid system to quickly create modern layouts and submodules.
easy grid system fo web sites and apps
It is important to note that the path attribute does not protect against unauthorized reading of the cookie from a different path. It can be easily bypassed using the DOM, for example by creating a hidden iframe element with the path of the cookie, then accessing this iframe's contentDocument.cookie property. The only way to protect the cookie is by using a different domain or subdomain, due to the same origin policy.
Anyone can say Anything
The “Open World Assumption” is central to this post and to the actual shift in paradigm when it comes to moving from documents to data. People/institutions have an alleged interest in protecting the way their assets are described. Even libraries. The Open World Assumption makes it sound quite chaotic, to some ears. And claims that machine learning will solve everything tend not to help the unconvinced too much. Something to note is that this ability to say something about a third party’s resource connects really well with Web annotations (which do more than “add metadata” to those resources) and with the fact that no-cost access to some item of content isn’t the end of the openness.
Les représentants de la Bibliothèque nationale de France (BnF) annoncèrent leur objectif de ramener le délai de traitement des documents à six semaines en moyenne
C’était long, en 2002! Où en est la BnF, aujourd’hui? D’une certaine façon, ce résumé semble prédire la venue des données, la fédération des catalogues, etc. Pourtant, il semble demeurer de nombreux obstacles, malgré tout ce temps. Et si on pouvait annoter le Web directement?
Strong arguments for abandoning icon fonts in favor of SVG icons, with plenty of links to supporting material.<br> Tyler Sticka
Font Awesome is an SVG and CSS icon library designed for Bootstrap.
Seeking easier ways for people to publish on the Web and control their own data. http://sandstorm.io/ https://www.kuberdock.com/
Join Darin Fisher, VP of Chrome as he talks the past, present and future of the web.
RAIL - Reaction (<100ms), Animation (<16ms), Idle (<50ms), Load (<1000ms)
In the latest version of Known, we shipped experimental support for Accelerated Mobile Pages. This is an answer to something called Facebook Instant Pages, which caches website content inside a mobile app so it can be displayed immediately. While Instant Pages content must be negotiated with Facebook, anyone can publish AMP content. So far, so good.Unfortunately, AMP redefines the HTML standard with some custom tags. That’s not great. It also requires that we load JavaScript from a specific source, which radically centralizes website content. We assume this is a shim until these features are more widely supported, so we can live with that. What’s less impressive is that AMP whitelists ad networks that participating pages can be a part of. If you’re not generating ad revenue from one of A9, AdReactor, AdSense, AdTech or Doubleclick and want to have your websites load swiftly inside social mobile apps, you’re out of luck.
entity called “comment,”
Post, comment, annotation… All different, but can all have the same predicate.
Worse is that Mark Zuckerberg proves not to be a fan of links, or hyperlinks. On Facebook, he doesn’t encourage you to link. On Instagram, he has simply forbidden them. He is quashing the hyperlink, thereby killing the interconnected, decentralized, outward network of text known as the World Wide Web.Facebook likes you to stay within it. Videos are now embedded in Facebook, and soon the outside articles will be embedded, too, with its Instant Articles project. Mr. Zuckerberg’s vision is of an insular space that gets all our attention — and he gets to sell it to advertisers.
e-learning technologies and standards: SCORM, LOM, IMS-LD, IMS-CC, IMS-QTI, IMS-CP, LDL, SLD
Standards matter.
some kind of curated library
Which is where OER catalogues (tied to the Semantic Web) may shine. Sure, they can require a lot of work. But this is precisely why they matter.
It’s known that Angular becomes slower with around 2,000 bindings due to the process behind dirty-checking. The less we can add to this limit the better, as bindings can add up without us really noticing it!
From some preliminary testing it looks like we get close to hitting the 2000 watch count on the /stream view - which explains the lag.
why not annotate, say, the Eiffel Tower itself
As long as it has some URI, it can be annotated. Any object in the world can be described through the Semantic Web. Especially with Linked Open Data.
machine-readable, ‘semantic’ annotations.
Waiting for those to be promoted, through Hypothesis and other Open Annotations platforms.
a web so conceptually consistent, socially relevant and technically expandable
We've done relatively well with the first two. "Technically expandable" is the one in danger.
If we continue to build "social networks" as singular dead end cul-de-sacs, we leave no exit available to those who follow.
The Web we want is expandable beyond the reaches of what we currently know, the economies we operate within, and the future we can currently conceive.
20 browser alter natives.
Here are a few handy tips on measuring your project’s performance profile:
In particular, see this section on recommendations for setting up tests that reasonably simulate "real world" conditions.
Web performance article from a couple of the Chrome team developers / (developer advocates). Mentioned on Twitter - https://twitter.com/aerotwist/status/649877465079390209
Some interesting slides on CSS styling performance on GitHub, particularly focusing on their diff pages.
Several slides have direct references to WebKit internals explaining the impact on rule resolution performance.
Mentions a useful tool for understanding CSS selector performance implications, css explain
This is the main reason we end up with bloated code bases, full of legacy and unknown CSS that we daren't touch. We lack the confidence to be able to work with and modify existing styles because we fear the consequences of CSS' globally operating and leaky nature. Almost all problems with CSS at scale boil down to confidence (or lack thereof): People don't know what things do any more. People daren't make changes because they don't know how far reaching the effects will be.
If your timeline graph is dominated with the color green after recording
Green is used to denote time spent painting
there does not seem to be a general rule for how many workers to spawn. Some developers claim that 8 is a good number, but use an online calculator and suit yourself
Web workers are very heavy objects as they include an entire JS VM instance. 8 sounds like a lot.
This is an interesting history of web app and specifically component / styling development at Yandex and the evolution of the BEM methodology.
The W3C Annotation Working Group has a joint deliverable with the W3C Web Application Working Group called “Robust Anchoring”. This deliverable will provide a general framework for anchoring; and, although defined within the framework of annotations, the specification can also be used for other fragment identification use cases. Similarly, the W3C Media Fragments specification [media-frags] may prove useful to address some of the use cases. Finally, the Streamable Package Format draft, mentioned above, also includes a fragment identification mechanism. Would that package format be adopted for EPUB+WEB, that fragment identification may also come to the fore as an important mechanism to consider.
Anchors are a key issue. Hope that deliverable will suffice.
This is an interesting dive into the challenges of creating a good language to describe the structure and functionality of a UI.
It advocates using a declarative structure to lay out the components and then using imperative logic within the components.
The $digest loop keeps iterating until the model stabilizes
cf. React where an event triggers an event handler, which can trigger state changes and calls to React.render(). These are then batched together resulting in a single re-render, a DOM-diff and the application of the result to the DOM. Consequently you can't have an infinite state update loop. The exception is if a state change happens asynchronously, and that state change triggers another async state change (and so on...)
The debugger allows you to access the currently selected element in the console as $0 variable.
The value function should return the value which is being watched. AngularJS can then check the value returned against the value the watch function returned the last time
Ah, so since the input is a scope, this means that Angular needs to call every watch value fn that might be affected by a change. Should look into whether it has any optimizations to avoid that for common watch expressions.
Both accessibility and performance are invisible aspects of an experience and should be considered even if they aren’t explicit goals of the project.
all representations have essentially the same information content. And what we mean by "essentially" allows in fact some wriggle room, and in the end it rests on a common understanding between publisher of the information and quoter of the URI. The sameness we are after is the sameness of information content. That is what is identified by the URI. That is why we say that the URI identifies that conceptual information content, irrespective of its particular representation: the conceptual work. Without that common understanding, the web does not work. Some people have said, "If we say that URIs identify people, nothing breaks". But all the time they, day to day, rely on sameness of the information things on the web, and use URIs with that implicit assumption. As we formalize how the web works, we have to make that assumption explicit.
I'm sticking with the machine-processable languages as examples because human-processable ones like HTML have a level of ambiguity traditional in human natural language but quite out of place in the WWW infrastructure -- or the Semantic Web.
we must either distinguish or be hopelessly fuzzy. And is this bad, is it an inhibition to have to work our way though documents before we can talk about whatever we desire? I would argue not, because it is very important not to lose track of the reasons for our taking and processing any piece of information. The process of publishing and reading is a real social process between social entities, not mechanical agents. To be socially responsible, to be able to handle trust, and so on, we must be aware of these operations. The difference between a car and what some web page says about it is crucial - not only when you are buying a car. Some have opined that the abstraction of the document is nonsense, and all that exists, when a web page describes a car, is the car and various representations of it, the HTML, PNG and GIF bit streams. This is however very weak in my opinion. The various representations have much more in common than simply the car. And the relationship to the car can be many and varied: home page, picture, catalog entry, invoice, remote control panel, weblog, and so on. The document itself is an important part of society - to dismiss its existence is to prevent us being aware of human and aspects of information without which we are impoverished. By contrast, the difference between different representations of the document (GIF or PNG image for example) is very small, and the relationship between versions of a document which changes through time a very strong one.
It demonstrates the ambiguity of natural language that no significant problem had been noticed over the past decade, even though the original author or HTTP , and later co-author of HTTP 1.1 who also did his PhD thesis on an analysis of the web, and both of whom have worked with Web protocols ever since, had had conflicting ideas of what the various terms actually mean.
an HTTP URI may identify something with a vagueness as to the dimensions above, but it still must be used to refer to a unique conceptual object whose various representations have a very large a mount in common. Formally, it is the publisher which defines the what an HTTP URI identifies, and so one should look to the publisher for a commitment as to the exact nature of the identity along these axes.
So instead we introduced the loading spinner on each widget. Nothing is actually any faster, but the whole experience feels more responsive
Simply reducing some CSS transition times from 500ms to 250ms, and cutting others out entirely, made the whole dashboard feel snappier and more responsive.
This means content is served from the nearest possible geographic location to the user, cutting down request latency from as high as 2500ms (in places such as Singapore) to tens of milliseconds
We eventually came up with a compromise solution based on Addy Osmani’s basket.js, using a combination of server-side script concatenation and localStorage for caching. In a nutshell, the page includes a lightweight loader script, which figures out which JS and CSS it has already cached and which needs to be fetched. The loader then requests all the resources it needs from the server in one request, and saves all the resources into localStorage under individual keys. This gives us a great compromise between cutting down the number of HTTP requests while still being able to maintain cacheability, and not re-downloading code unnecessarily when it hasn’t changed. Addtionally, after running a few benchmarks, we found that localStorage is (sometimes) actually faster than the native HTTP cache, especially on mobile browsers.
While these features have connected untold millions and created new forms of social organization, they also come at a cost. Material seems to vanish almost as quickly as it is created, disappearing amid broken links or into the constant flow of the social media “stream.” It can be hard to distinguish fact from falsehood. Corporations have stepped into this confusion, organizing our browsing and data in decidedly closed, non-transparent ways. Did it really have to turn out this way?
La web, utopía y distopía en simultánea.
The promise of OA lies more in prospects for social success than in the model's descriptive power.
Fine by me.
I feel that there is a great benefit to fixing this question at the spec level. Otherwise, what happens? I read a web page, I like it and I am going to annotate it as being a great one -- but first I have to find out whether the URI my browser is used, conceptually by the author of the page, to represent some abstract idea?
The Training and Learning Architecture (TLA) encompasses a set of standardized Web service specifications and Open Source Software (OSS) designed to create a rich environment for connected training and learning.
It was all envisioned by Sir Tim Berners-Lee 25 years ago
It's amazing how hard the implementation bit is... :(
Love the idea. Making it a reality is still ongoing, as I'm sure TimBL knows all too well...
We strongly urge you to reconsider your business tactic here and again respect people’s right to choice and control of their online experience by making it easier, more obvious and intuitive for people to maintain the choices they have already made through the upgrade experience.
Completely agree!
Now...how do I change my Reader View settings to use something besides Pocket for social bookmarking?
...can't seem to find that setting...anywhere.
Let me be very clear: I do not care what the “top highlight” is. In fact, I actively do not want to know what the top highlight is. That kind of information encourages the meme-ification of the web, a world where we care more about pushing one sentence over the “tipping point” into virality than in carrying on a global conversation. It’s American Idol for pull quotes.
Davis, Allison P. "Sheila Heti on Drinking Her Way to a Child's-Eye View" from Department of Corrections in The Cut July 16, 2015 annotation as a correction to existing online resources such as Wikipedia
European Bureau of Libraries in Europe Public libraries- statistics
To these basic citations, the annotated bibliography adds descriptive and evaluative comments (i.e., an annotation), assessing the nature and value of the cited works. The addition of commentary provides the future reader or researcher essential critical information and a foundation for further research.
Google Annotations Gallery
what is this resource? what does it do?
The Google Annotations Gallery is an exciting new Java open source library that provides a rich set of annotations for developers to express themselves. Do you find the standard Java annotations dry and lackluster? Have you ever resorted to leaving messages to fellow developers with the @Deprecated annotation? Wouldn't you rather leave a @LOL or @Facepalm instead? If so, then this is the gallery for you.
“People form first impressions about web pages in 17 milliseconds.”
“the process through which a person becomes capable of taking what was learned in one situation and applying it to new situations; in other words, learning for ‘transfer . ’”
What better way to do this than taking a skill- or content-based lesson and applying it to the web as a practice through annotation.
If you want a DIY version of this, try ImageMagick's compare command: compare bag_frame1.gif bag_frame2.gif compare.gif Documentation: http://www.imagemagick.org/Usage/compare/ reply no_gravity 2 hours ago Interesting. And to render the html you can use cutycapt. Which is in the Debian repos too. I just tried it, and this rendered a nice diff of two pages for me: cutycapt --url=http://www.xyz.com/1 --out=1.png cutycapt --url=http://www.xyz.com/2 --out=2.png compare 1.png 2.png diff.png reply easytiger 2 hours ago Now make it a webservice and charge $200/month! reply programmernews3 1 hour ago First part already done: http://archive.is/ reply prottmann 1 hour ago apt-get install the services and use them on my server ;-) reply
Plain and simple way to report visual degradation of website or webapp
Top 5 Free Node.js Hosting Services
Ücretsiz web uygulaması ve nodejs barındırılabilecek hizmet sağlayıcılar
WebODF is a JavaScript library that makes it easy to add Open Document Format (ODF) support to your website and to your mobile or desktop application. It uses HTML and CSS to display ODF documents.
Axiom: Opacity of URIs The only thing you can use an identifier for is to refer to an object. When you are not dereferencing, you should not look at the contents of the URI string to gain other information.
Here’s a presentation at the 2013 Personal Democracy Forum that provides a little more context for our project.
This is an inspiring talk.
You can expect to pay 50 cents a day. Or try DIY. This is where you will own your content.
Rent to own?
There is no ownership while we rent.
We either own or increase our freedom of movement in and out of rental environments...or both.
Although people weren’t used to scrolling in the mid-nineties, nowadays it’s absolutely natural to scroll. For a continuous and lengthy content, like an article or a tutorial, scrolling provides even better usability than slicing up the text to several separate screens or pages.
I BM GroupTalk
Anyone remember what this was?
There was a point many years ago now when the web looked like it would be for documents. It would be structured and organized, and everything could be linkable.
...and I want this Web back...
while e-mail dissolves barriers to the exchange of data, we need another solvent to dissolve the barriers to collaborative use of that data. Applied in the right ways, that solvent creates what I like to call the “universal canvas” -- an environment in which data and applications flow freely on the Web.
How interesting! It's the same in my family. Certain members will take as gospel, the opinions of the people they deem to have credibility, but eschew - and even satirically cauterize - the wisdom and factual evidence of people with the authority and knowledge.
It's most frustrating. As for me, I try not to read comments. They just make me so angry!
Web-App »Orte jüdischer Geschichte«
Beschreibung der App in der DARIAH-DE Infrastruktur.
Ebenfalls eingebaut ist der naheliegende Zugang über eine Kartenvisualisierung (Google Maps).
Die verwendete Methode mittels KML-Datei wird jedoch vom Anbieter Google ab Februar 2015 nicht mehr unterstützt. Hier wird eine andere Visualisierung gebraucht.
There’s a certain amount of snobbery about PHP, but I’ve no truck for such snark. PHP is the Web’s BASIC. It’s everywhere, beginner-friendly, and I like it.
Yeah. I think this describes things perfectly. ^_^
Clients are browsers
== or === ?
Maybe the driver for semantic web data is humans trying to programmatically consume human-readable information, rather than the other way around?
What really needs to happen is for somebody to take a few of the huge publicly available triplestores and write some really compelling reasoning systems on them and demonstrate almost effortless merging across the datasets. Outside of fairly trivial examples, almost all of which are similarly or outperformed by near-enough technologies, really complex reasoners haven't happened.
observational metadata is far more reliable than the stuff that human beings create for the purposes of having their documents found. It cuts through the marketing bullshit, the self-delusion, and the vocabulary collisions
Read the whole essay it is worth the while...
Kartik Prabhu on marginalia on the Web.
it echos messages to all the participants using Web Sockets
ENQUIRE
As featured in "Weaving the Web" by Tim Berners-Lee
The cacophony of the crowd erases the past and affirms the present. It started with search and now its accelerated with the now web. I dont know where it leads but I almost want a remember button — like the like or favorite. Something that registers something as a memory — as an salient fact that I for one can draw out of the stream at a later time.
The process of tying two items together is the important thing.
Annotations are at the Web’s core.
Internet
Curiously, while net access is fast and painless at most cafes in the city, access at the conference hotel is convoluted and very limited.