42 Matching Annotations
  1. Nov 2022
    1. Nowhere better to start getting one’s head around this distributed vision than with Mike Masnick’s epic explainer, Protocols, Not Platforms: A Technological Approach to Free Speech.

      Mike Masnick https://knightcolumbia.org/content/protocols-not-platforms-a-technological-approach-to-free-speech Aug 2019. n:: "Build protocols, not platforms" (reminds me of the convo's around Jabber/XMPP I listened into in the early '00s) Also, IndieWeb / ActivityPub

  2. Aug 2022
    1. By nature of running on a blockchain, Hyperstructures can run forever with no ability to stop them. They can continuously function without a maintainer or operator, and they can run for as long as the underlying blockchain is running

      Seems to me that the same can be said of internet protocols, which are unstoppable as long as the internet is running. Where's the difference? Also, the equation of "forever" with "at least a decade" is funny.

  3. May 2022
  4. Apr 2022
    1. Feature request (implement something that allows the following): 1. From any page containing a bookmarklet, invoke the user-stored bookmarklet בB 2. Click the bookmarklet on the page that you wish to be able to edit in the Bookmarklet Creator 3. From the window that opens up, navigate to a stored version of the Bookmarklet Creator 4. Invoke bookmarklet בB a second time from within the Bookmarklet Creator

      Expected results:

      The bookmarklet from step #2 is decoded and populates the Bookmarklet Creator's input.

      To discriminate between invocation type II (from step #2) and invocation type IV (from step #4), the Bookmarklet Creator can use an appropriate class (e.g. https://w3id.example.org/bookmarklets/protocol/#code-input) or a meta-based pragma or link relation.

  5. Nov 2021
  6. Aug 2021
  7. Jul 2021
  8. datatracker.ietf.org datatracker.ietf.org
    1. It is similarly intended to fail to establish a connection when data from other protocols, especially HTTP, is sent to a WebSocket server, for example, as might happen if an HTML "form" were submitted to a WebSocket server. This is primarily achieved by requiring that the server prove that it read the handshake, which it can only do if the handshake contains the appropriate parts, which can only be sent by a WebSocket client. In particular, at the time of writing of this specification, fields starting with |Sec-| cannot be set by an attacker from a web browser using only HTML and JavaScript APIs such as XMLHttpRequest [XMLHttpRequest].
    2. The WebSocket Protocol is designed on the principle that there should be minimal framing (the only framing that exists is to make the protocol frame-based instead of stream-based and to support a distinction between Unicode text and binary frames). It is expected that metadata would be layered on top of WebSocket by the application Fette & Melnikov Standards Track [Page 9] RFC 6455 The WebSocket Protocol December 2011 layer, in the same way that metadata is layered on top of TCP by the application layer (e.g., HTTP). Conceptually, WebSocket is really just a layer on top of TCP that does the following: o adds a web origin-based security model for browsers o adds an addressing and protocol naming mechanism to support multiple services on one port and multiple host names on one IP address o layers a framing mechanism on top of TCP to get back to the IP packet mechanism that TCP is built on, but without length limits o includes an additional closing handshake in-band that is designed to work in the presence of proxies and other intermediaries Other than that, WebSocket adds nothing. Basically it is intended to be as close to just exposing raw TCP to script as possible given the constraints of the Web. It's also designed in such a way that its servers can share a port with HTTP servers, by having its handshake be a valid HTTP Upgrade request. One could conceptually use other protocols to establish client-server messaging, but the intent of WebSockets is to provide a relatively simple protocol that can coexist with HTTP and deployed HTTP infrastructure (such as proxies) and that is as close to TCP as is safe for use with such infrastructure given security considerations, with targeted additions to simplify usage and keep simple things simple (such as the addition of message semantics).
  9. Jun 2021
    1. From a comment by Muneeb Ali:

      The original Internet protocols defined how data is delivered, but not how it's stored. This lead to centralization of data.

      The original Internet protocols also didn't provide end-to-end security. This lead to massive security breaches. (Other reasons for security breaches as well, but everything was based on a very weak security model to begin with.)

  10. Apr 2021
    1. Can we reconfigure growth to mean richness in difference? Flourishing interdependent diversity of networks, network protocols and forms of interaction? What does this mean for digital decay, and can the decay of files, applications and networks become some form of compost, or what might be the most dignified form of digital death and rebirth?

      Also see Apoptosis

  11. Mar 2021
  12. Feb 2021
    1. We were especially excited to see Dorsey cite Mike Masnick's excellent Protocols, Not Products paper.

      I don't think I've come across this paper before...

      Looking at the link, it's obvious I read it on December 11, 2019.

  13. Jan 2021
  14. Oct 2020
  15. Jul 2020
    1. Syncthing uses an open and documented protocol, and likewise the security mechanisms in use are well defined and visible in the source code. Resilio Sync uses an undocumented, closed protocol with unknown security properties.
  16. Jun 2020
    1. Syncthing uses an open and documented protocol, and likewise the security mechanisms in use are well defined and visible in the source code. Resilio Sync uses an undocumented, closed protocol with unknown security properties.
    1. Akhvlediani, T., Ali, S. M., Angus, D. C., Arabi, Y. M., Ashraf, S., Baillie, J. K., Bakamutumaho, B., Beane, A., Bozza, F., Brett, S. J., Bruzzone, R., Carson, G., Castle, L., Christian, M., Cobb, J. P., Cummings, M. J., D’Ortenzio, E., Jong, M. D. de, Denis, E., … Webb, S. (2020). Global outbreak research: Harmony not hegemony. The Lancet Infectious Diseases, 0(0). https://doi.org/10.1016/S1473-3099(20)30440-0

  17. May 2020
  18. Apr 2020
    1. During the first era of the internet — from the 1980s through the early 2000s — internet services were built on open protocols that were controlled by the internet community. This meant that people or organizations could grow their internet presence knowing the rules of the game wouldn’t change later on.
    2. During the first era of the internet — from the 1980s through the early 2000s — internet services were built on open protocols that were controlled by the internet community
  19. Sep 2017
  20. Aug 2017
    1. Focusing on the fundamentals of grammar is one approach to teaching writing.

      CUE ELA Protocols +UDL Research and background information that can be used to provide support for the use of the protocols

  21. Jun 2016
    1. dynamic documents

      A group of experts got together last year at Daghstuhl and wrote a white paper about this.

      Basically the idea is that the data, the code, the protocol/analysis/method, and the narrative should all exist as equal objects on the appropriate platform. Code in a code repository like Github, Data in a data repo that understands data formats, like Mendeley Data (my company) and Figshare, protocols somewhere like protocols.io and the narrative which ties it all together still at the publisher. Discussion and review can take the form of comments, or even better, annotations just like I'm doing now.