1,755 Matching Annotations
  1. Jul 2016
  2. Jun 2016
    1. These modes on online engagement have been described as Resident in that they involve the individual being present, or residing, to a certain extent online. This is in contrast to Visitor modes of engagement where the individual leaves no online social trace. These new, Resident, forms of agency and online participation are repositioning institutions within a larger, more open, knowledge production landscape. Individuals are increasingly aware, via the opportunities provided by Resident practices on the web, that they do not have to sacrifice as much personal agency to the institution to gain professional credibility as they might have done in a pre-Web era.
    1. il y a passage d’une version du web horizontale, où la catégorisation est mise à plat (par exemple, le hashtag [déf1]), à une version hiérarchisée et informée, où le relief de la structuration met en évidence auprès des autres systèmes sémantiques la nature du contenu diffusé

      distinction entre web 2.0 au web 3.0

  3. May 2016
    1. doesn't provide developers with the means to import such modules of code in a clean, organized manner. It's one of the concerns with specifications that haven't required great thought until more recent years where the need for more organized JavaScript applications became apparent.
  4. Apr 2016
    1. But I think there is power in the notion of a book, its thingness, and the Web can perhaps learn how to encapsulate, in the way a book does, a discrete thing, a bounded set of ideas.

      I really like the notion, especially from a poetic perspective. But I can't stop dwelling on all that is lost if the web is "bounded." That's the huge advantage of the web over an object/book. It is not about the content, it's about the conversation and the community. It's about process over product.

    1. Reasons Facebook, Twitter, and Instagram have dominated the Web over blogs and independent sites:

      • People prefer a single interface that makes it easy to flip or scroll through the new stuff. They don't like visiting a dozen different sites with different interfaces.
      • Most people don't want to deal with site structure or complex editors, let alone markup languages or servers.
      • Facebook quickly became a friends-and-family network, which pulled in more of the same.
      • Following and unfollowing should only require a single click.
      • Retweets and mentions introduce new people to follow, even if you aren't looking for them.
      • Reposting should be easy, include obvious attribution, and comments should be attached.
      • RSS readers had the potential to offer these things, but standard ways of using it were not widely adopted. Then Google Reader pushed out other readers, but was nevertheless shut down.

      Let go of the idea of people reading your stuff on your site, and develop or support interfaces that put your readers in control of how they view the web instead of giving the control to the people with the servers.

    1. People want to own their data and their namespace but they don’t want to run servers to do it. What’s the solution? Separate the elements. Treat your personal server as a BDS (Big Dumb Server), there to answer API calls and file requests.  Move the admin interfaces up towards the client, and maintain them centrally the way apps are maintained. Eventually, move the presentation layer towards the client too, allowing readers power over how they consume the data on your server.
      • Database:
        • provided by host
        • general purpose
        • accessible by http or https API
      • Database administration:
        • Native app or Web interface making privileged API calls.
        • GUI file browser for web server folders and files.
      • Presentation Layer
        • Pull pages (or other data) from multiple databases.
        • Customizable: the data you want, in the way you want to display it or otherwise use it.
    1. Reste à savoir maintenant si Hypothes.is va finir par être davantage connu, dans les milieux académiques par exemple

      Il y a de belles expériences open qui sont en cours, dont celle de la revue Vertigo (tu les as peut-être vues avec le tutoriel) : open peer review avec hypothes.is

      https://hypothes.is/blog/annotating-to-extract-findings-from-scientific-papers/

      https://via.hypothes.is/http://vertigo.hypotheses.org/1891

      et chez hypothes.is, ils travaillent avec des éditeurs scientifiques https://hypothes.is/blog/a-coalition-of-over-40-scholarly-publishers/

      On en discute sur le facebook de HackYourPhD, si ça t'intéresse.

    1. "connected copies" - multiple copies of pages and other files stored across the Web, accessed by name rather than just a single address.

      Some examples already exist: git, torrents, federated wiki, various named data networking projects, and the Interplanetary File System.

      Distributed copies fight link rot and reduce Internet traffic congestion. More importantly, if the files are freely licensed, easy to copy, and easy to edit, the concept reaches toward the full peer-to-peer potential of the Web.

    1. We should have control of the algorithms and data that guide our experiences online, and increasingly offline. Under our guidance, they can be powerful personal assistants.

      Big business has been very militant about protecting their "intellectual property". Yet they regard every detail of our personal lives as theirs to collect and sell at whim. What a bunch of little darlings they are.

    1. JavaScript creator Brendan Eich is working on a browser that blocks tracking, and replaces ads with less obtrusive ones. Websites can sign up to get a cut of the income from those ads. They'll also have a way for users to pay to visit sites ad-free.

      http://brave.com/<br> https://github.com/brave<br> https://twitter.com/brave

      It will be interesting to see how this plays out. Naturally, those obtrusive advertisers won't like it. I'd love it if sites I visit often could give me ads for stuff I might actually buy, especially if they received a generous cut of each sale.

    1. What he outlined for the tools in 1990 is not only still relevant, but more crucial to business and society than ever, and shockingly still largely missing in the prevailing technology

      need to look into these links further

    2. interactive computing was about interacting with computers, and more importantly, interacting with the people and with the knowledge needed

      relates to Berners-Lee's quote - the web was always about connecting people. More people sharing more knowledge, ideas and information more widely and more efficiently = more and better advances

  5. Mar 2016
    1. it's going to influence whether they think of the internet as a tool or a place.

      or both .. hmmm I got used to making a distinction between the internet and the Web. I think here the "internet" is used to mean "the web". to me the internet is more of a tool the infrastructure for the Web which mostly a huge place full of places and paces of all sizes and privacy levels as well as tools

      I'll read this again later but this is how I feel about it right now.

  6. Feb 2016
    1. This is a good short overview of how change detection works in Angular 2.

      It fixes the fundamental algorithmic complexity problem that change detection has in Angular 1.x by making it possible to prune parts of the component tree from change detection if the inputs have not changed.

      Unfortunately the zone.js implementation involves some horrifying monkey-patching of various DOM APIs.

    1. Educators

      Just got to think about our roles, in view of annotation. Using “curation” as a term for collecting URLs sounds like usurping the title of “curator”. But there’s something to be said about the role involved. From the whole “guide on the side” angle to the issue with finding appropriate resources based on a wealth of expertise.

  7. Jan 2016
    1. While there are some features shared between a university repository and us we are distinctly different for the following reasons: We offer DOIs to all content published on The Winnower All content is automatically typeset on The Winnower Content published on the winnower is not restricted to one university but is published amongst work from peers at different institutions around the world Work is published from around the world it is more discoverable We offer Altmetrics to content  Our site is much more visually appealing than a typical repository  Work can be openly reviewed on The Winnower but often times not even commented on in repositories. This is not to say that repositories have no place, but that we should focus on offering authors choices not restricting them to products developed in house.

      Over this tension/complementary between in house and external publishing platforms I wonder where is the place for indie web self hosted publishing, like the one impulsed by grafoscopio.

      A reproducible structured interactive grafoscopio notebook is self contained in software and data and holds all its history by design. Will in-house solutions and open journals like The Winnower, RIO Journal or the Self Journal of Science, support such kinds of publishing artifacts?

      Technically there is not a big barrier (it's mostly about hosting fossil repositories, which is pretty easy, and adding a discoverability and author layer on top), but it seems that the only option now is going to big DVCS and data platforms now like GitHub or datahub alike for storing other research artifacts like software and data, so it is more about centralized-mostly instead of p2p-also. This other p2p alternatives seem outside the radar for most alternative Open Access and Open Science publishers now.

    1. 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.

    1. 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.

    1. 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?

    1. 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.

  8. Dec 2015
    1. 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
    1. 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."

      https://github.com/bbc/html5-video-compositor

    1. 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.
    1. Some of the reasons we need to keep the Internet free and open:

      • free and open education
      • spreading of good ideas
      • participatory democracy
      • cooperation and collaboration
      • diversification of news sources
      • connections among citizens everywhere

      (This article already has 324 responses.)

    1. 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.

    1. 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.

  9. gridlex.devlint.fr gridlex.devlint.fr
    1. 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.
    1. 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.

  10. Nov 2015
    1. 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?

    1. 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.
    1. 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.
  11. Oct 2015
    1. 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.

  12. Sep 2015
    1. 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

    1. 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.
    1. 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.

    1. 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.

    1. 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.

    1. 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...)

    1. 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.

    1. 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.
    2. 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.
    3. 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.
    4. 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.
    1. 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.
  13. Aug 2015
    1. 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.

  14. Jul 2015
    1. 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.

    1. 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.
    1. 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.
  15. Jun 2015
    1. “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.

    1. 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

  16. May 2015
  17. Apr 2015
  18. Mar 2015
    1. 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.
  19. Feb 2015
    1. 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.
  20. Jan 2015
    1. 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!

  21. Nov 2014
  22. Oct 2014
    1. 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.
    1. 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...

  23. Sep 2014
    1. 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.
  24. Jan 2014
  25. Oct 2013