1,683 Matching Annotations
  1. Dec 2022
    1. The modern internet was born out of an epic struggled between "Bellheads" (who believed centralized powers should decide how you used networks) and "Netheads" (who believed that services should be provided and consumed "at the edge"): https://www.wired.com/1996/10/atm-3/
    1. Note: it is not possible to apply a boolean scope with just the query param being present, e.g. ?active, that's not considered a "true" value (the param value will be nil), and thus the scope will be called with false as argument. In order for the scope to receive a true argument the param value must be set to one of the "true" values above, e.g. ?active=true or ?active=1.

      Is this behavior/limitation part of the web standard or a Rails-specific thing?

    1. This brings interesting questions back up like what happens to your online "presence" after you die (for lack of a better turn of phrase)?

      Aaron Swartz famously left instructions predating (by years IIRC) the decision that ended his life for the way that unpublished and in-progress works should be licensed and who should become stewards/executors for the personal infrastructure he managed.

      The chrisseaton.com landing page has three social networking CTAs ("Email me", etc.) Eventually, the chrisseaton.com domain will lapse, I imagine, and the registrar or someone else will snap it up to squat it, as is their wont. And while in theory chrisseaton.github.io will retain all the same potential it had last week for much longer, no one will be able to effect any changes in the absence of an overseer empowered to act.

    1. This document is a companion to the IIIF Content Search API Specification, Version 2.0. It describes the changes to the API specification made in this major release, including ones that are backwards incompatible with version 1.0, the previous version.
    1. You can filter the resource using criteria specified as query[*]. You can provide multiple criteria, to use AND logic. You can sort the resource using parameters specified as sort[*]. You can specify multiple fields to sort by.
    2. Enum:"add" "delete" An additional flag parameter with the value add will add masks provided in the request body to the list. A flag value delete will delete masks from the list. If there's no parameter provided, masks are replaced.
    1. API TypeMailgun API NamePostmark API NameSending EmailsMessagesEmailManaging SuppressionsSuppressionsSuppressionsManaging TemplatesTemplatesTemplatesManaging Sending SettingsServerManaging ServersServersManaging Sent EmailsEventsMessagesManaging Inbound EmailsMessages, EventsMessagesManage Inbound Processing SettingsRoutesManage email domains you can send fromDomainsDomains
  2. Nov 2022
    1. dealised utopia

      Possibly, besides web monetization, there can be donation basket like ko-fi beside curation, as well as cleatly linking back to the original that can have a donation basket as well. The options are complementary.

    1. From a technical point of view, the IndieWeb people have worked on a number of simple, easy to implement protocols, which provide the ability for web services to interact openly with each other, but in a way that allows for a website owner to define policy over what content they will accept.

      Thought you might like Web Monetization.

    1. partnerships, networking, and revenue generation such as donations, memberships, pay what you want, and crowdfunding

      I have thought long about the same issue and beyond. The triple (wiki, Hypothesis, donations) could be a working way to search for OER, form a social group processing them, and optionally support the creators.

      I imagine that as follows: a person wants to learn about X. They can head to the wiki site about X and look into its Hypothesis annotations, where relevant OER with their preferred donation method can be linked. Also, study groups interested in the respective resource or topic can list virtual or live meetups there. The date of the meetups could be listed in a format that Hypothesis could search and display on a calendar.

      Wiki is integral as it categorizes knowledge, is comprehensive, and strives to address biases. Hypothesis stitches websites together for the benefit of the site owners and the collective wisdom that emerges from the discussions. Donations support the creators so they can dedicate their time to creating high-quality resources.

      Main inspirations:

      Deschooling Society - Learning Webs

      Building the Global Knowledge Graph

      Schoolhouse calendar

    1. locally-based staff and carries out its programs in conjunction with local partners. Teams of international instructors and volunteers support the programs through projects year-round.

      So many good features in your project!

      Employing local staff that know the setting and can be role models for the kids.

      Supporting mentoring by volunteers to scale.

      Working with bodies to get a visceral experience that change is possible.

      Mentoring in groups to build a community.

      Spotlighting diversity and building bridges beyond the local community.

      Some related resources: Ballet dancer from Kibera

      Fighting poverty and gang violence in Rio's favelas with ballet

    1. Publishers can create interactive stories on the platform and incorporate them in their website.

      I love this! It is similar to Prezi or VoiceThread.

      Do you also support collaborative editing (public or with invited collaborators)? If yes, a high-resolution world map could be used for collaborative pinning of local events, meetups, news, videos, and so on, such as radio.garden or YouTube Geofind.

    1. Localisation ≠ Translation To start with, we have been researching, publishing, and producing articles on the topics of localisation to gain a wider understanding for implementing it. Here's some of what we published with @sophie authoring:

      Have you thought about crowdsourcing localization via weblate? It includes DeepL and can also be a learning ground, such as Duolingo Immersion.

    1. Creating video tutorials has been hard when things are so in flux. We've been reluctant to invest time - and especially volunteer time - in producing videos while our hybrid content and delivery strategy is still changing and developing. The past two years have been a time of experimentation and iteration. We're still prototyping!

      Have you thought about opening the project setting and the remixing to educators or even kids? That could create additional momentum.

      A few related resources you might want to check out for inspiration: Science Buddies, Seesaw, Exploratorium

    1. 11/30 Youth Collaborative

      I went through some of the pieces in the collection. It is important to give a platform to the voices that are missing from the conversation usually.

      Just a few similar initiatives that you might want to check out:

      Storycorps - people can record their stories via an app

      Project Voice - spoken word poetry

      Living Library - sharing one's story

      Freedom Writers - book and curriculum based on real-life stories

    1. not really about the content of the sessions. Or anything you take from it. The most important thing are the relationships, the connections you gain from sharing the things you're passionate about with the people who are interested in it, the momentum you build from working on your project in preparation for a session

      I somewhat disagree - I think this community building is successful precisely because there is a shared interest or goal. It goes hand in hand. If there is no connecting theme or goal, the groups fall apart.

    1. Donations

      To add some other intermediary services:

      To add a service for groups:

      To add a service that enables fans to support the creators directly and anonymously via microdonations or small donations by pre-charging their Coil account to spend on content streaming or tipping the creators' wallets via a layer containing JS script following the Interledger Protocol proposed to W3C:

      If you want to know more, head to Web Monetization or Community or Explainer

      Disclaimer: I am a recipient of a grant from the Interledger Foundation, so there would be a Conflict of Interest if I edited directly. Plus, sharing on Hypothesis allows other users to chime in.

    1. All at once, billions of people saw themselves as celebrities, pundits, and tastemakers.

      ...but what if some of them...didn't.

    1. The JFK assassination episode of Mad Men. In one long single shot near the beginning of the episode, a character arrives late to his job and finds the office in disarray, desks empty and scattered with suddenly-abandoned papers, and every phone ringing unanswered. Down the hallway at the end of the room, where a TV is blaring just out of sight, we can make out a rising chatter of worried voices, and someone starting to cry. It is— we suddenly remember— a November morning in 1963. The bustling office has collapsed into one anxious body, huddled together around a TV, ignoring the ringing phones, to share in a collective crisis.

      May I just miss the core of this bit entirely and mention coming home to Betty on the couch, letting the kids watch, unsure of what to do.

      And the fucking Campbells, dressed up for a wedding in front of the TV, unsure of what to do.

      Though, if I might add, comparing Twitter to the abstract of television, itself, would be unfortunate, if unfortunately accurate, considering how much more granular the consumptive controls are to the user. Use Twitter Lists, you godforsaken human beings.

    1. Digital Initiatives and Web Services team

      I somehow missed changing this to Web Technologies

    2. Beginning in August 2019, all new content will meet or exceed WCAG 2.0 AA standards.

      Needs to be updated to reflect the fact that it is now past 2019 :)

  3. tantek.com tantek.com
    #TwitterMigration, first time? Have posted notes to https://tantek.com/ since 2010, POSSEd tweets & #AtomFeed. Added one .htaccess line today, and thanks to #BridgyFed, #Mastodon users can follow my #IndieWeb site @tantek.com@tantek.com No Mastodon install or account needed. Just one line in .htaccess: RewriteRule ^.well-known/(host-meta|webfinger).* https://fed.brid.gy/$0 [redirect=302,last] is enough for Mastodon users to search for and follow that @tantek.com@tantek.com username. Took a little more work to setup Bridgy Fed to push new posts to followers. Note by the way both the redundancy & awkwardness (it’s not a clickable URL) of such @-@ (AT-AT) usernames when you’re already using your own domain. Why can’t Mastodon follow a username of “@tantek.com”? Or just “tantek.com”? And either way expanding it internally if need be to the AT-AT syntax. Why this regression from what we had with classic feed readers where a domain was enough to discover & follow a feed? Also, why does following show a blank result? Contrast that with classic feed readers which immediately show you the most recent items in a feed you subscribed to. Lastly (for now), I asked around and no one knew of a simple public way to “preview” or “validate” that @tantek.com@tantek.com actually “worked”. You have to be *logged-in* to a Mastodon instance and search for a username to check to see if it works. Contrast that with https://validator.w3.org/feed/ which you can use without any log-in to validate your classic feed file. Why these regressions from the days of feed readers? - Tantek
    1
    1. the platform’s reliability is entirely dependent on which one you sign up for.

      It's been fine for years! I understand the intention behind informing readers of what the onboarding experience is like at this very moment, but if you're going to be part of this absurdly latent, dense wave of folks suddenly giving Mastodon a try, I think it's important you be very explicit about your lack of experience before the most intense influx of users in the history of the Fediverse.

    2. Joining Mastodon is undoubtably more complicated than starting a Twitter account.

      Are you sure about this argument, Janus? Are you sure you comprehensively tried all methods of onboarding?

    1. Page recommended by @wfinck. Seems @karlicoss is the author. This project seems similar to what I've been trying to do with Hypothes.is, Obsidian, Anki, Zotero, and PowerToys Run but goes beyond the scope of my endeavors to just quickly access whatever resource comes to mind (without creating duplicates). The things that Promnesia adds beyond my PKM stack is the following: - prioritize new info - keeping track of which device things were read and how long

    1. layers of wat are essentially hacks to build something resembling a UI toolkit on top of a document markup language

      So make your application document-driven (i.e. actually RESTful).

      It's interesting that we have Web forms and that we call them that and yet very few people seem to have grokked the significance of the term and connected it to, you know, actual forms—that you fill out on paper and hand over to someone to process, etc. The "application" lies in that latter part—the process; it is not the visual representation of any on-screen controls. So start with something like that, and then build a specialized user agent for it if you can (and if you want to). If you find that you can't? No big deal! It's not what the Web was meant for.

    2. There is no good way to develop a UI in HTML/CSS/JS

      So don't.

    1. Clean code examples (YouTube)Why Are You Still Creating CRUD APIs?Remove Your If-Else and Switch CasesWhy Cognitive and Cyclomatic Complexity Matters in Software DevelopmentWriting Cleaner Code (With Examples)Resources for the curious📚 Source Code (GitHub) by Nicklas Millard, the authorRESTful API Design by MicrosoftArchitectural Styles and the Design of Network-based Software Architectures by R.T. FieldingWhat is REST by codeacademyIs Crud Bad For Rest? by Boris LublinskyHATEOAS Driven REST APIs by restfulapi.netHATEOAS — a simple explanation by Bartosz JedrzejewskiWhy HATEOAS is useless and what it means for REST by Andreas ReiserRESTful Considered Harmful by Tomasz NurkiewiczTask-Based UI on cqrs.wordpress.comCRUD is an antipattern by Mathias VerraesWhy REST sucks by Troy A. Griffitts

      Useful links for Web & generic programming.

    2. RPC-like but still REST-full is way more preferred than those rotten CRUD designs.

  4. Oct 2022
    1. Supabase is an open source Firebase alternative. Start your project with a Postgres database, Authentication, instant APIs, Edge Functions, Realtime subscriptions, and Storage.

      https://supabase.com/


      Found as presumably it's being used by https://www.explainpaper.com/ with improper configurations

    1. PolyScale is an intelligent, serverless database caching engine which allows low-latency reads from Supabase globally, no coding required
    1. @1:10:20

      With HTML you have, broadly speaking, an experience and you have content and CSS and a browser and a server and it all comes together at a particular moment in time, and the end user sitting at a desktop or holding their phone they get to see something. That includes dynamic content, or an ad was served, or whatever it is—it's an experience. PDF on the otherhand is a record. It persists, and I can share it with you. I can deliver it to you [...]

      NB: I agree with the distinction being made here, but I disagree that the former description is inherent to HTML. It's not inherent to anything, really, so much as it is emergent—the result of people acting as if they're dealing in live systems when they shouldn't.

  5. Sep 2022
    1. "detail": [ { "loc": [ "body", "name" ], "message": "Field required" }, { "loc": [ "body", "email" ], "message": "'not-email' is not an 'email'" } ]

      not complient with Problem Details, which requires details to be a string

    1. For example, let’s consider the type property. For most of the projects I am working on, it isn’t practical to have a webpage dedicated to each type of possible error.

      That's not required. The standard doesn't require this to be a URL locator — merely a URI! So you can just make up a URI and use it even if it's not resolvable. ... like you did for the URN below.

    2. For the instance property, the most practical way I’ve found of implementing this is to define a URN that encapsulates additional information regarding the error. Here is an example URN for reference. urn:companyname:api:error:protocol:badRequest:f29f57d7-e1f8-4643-b226-fa18f15e9b71
    1. Ever tried to look up some news from 12 years ago? Back in library days you were able to do that. On news portals, most articles are deleted after a year, and on newspaper web sites you hardly ever get access to the archives – even with a subscription.

      This is a massive failure of infrastructure (and education/"professionalism"—by and large, most people whose careers are in operating or maintaining Web infrastructure don't haven't been inculcated into or adopted the sort of "code of ethics" that sees this as a failure).

      The thing might just be for something like the Internet Archive to get into training or selling professional services for handling companies' "Web presence, done the right way". (This is def. take some organizational restructuring, however.) I'd like to see, for example, IA-certified partner organizations that uphold the principles described here and the original vision for the Web, and professional associations that work hard at making sure the status quo improves a lot over what's common today (and doesn't slide back).

    1. ErrorResponse: description: Container object for one or more errors returned by the API. type: object required: - errors properties: errors: type: array items: $ref: '#/definitions/Error'
    1. FetchErrorResponse: type: object properties: meta: $ref: '#/definitions/FetchMetaResponse' errors: $ref: '#/definitions/Error' example: { "meta": { "req_id": "d07c8b12-c95e-4a06-8424-92aac94bb445" }, "errors": [{ "code": "Unauthorized", "detail": "A valid bearer token is required", "status":"401" } ] }
    1. Mais la justice fait face à un autre problème bien plus difficile à régler. Le blocage par les FAI n'est en effet efficace que si les internautes se servent des réglages DNS de base de leur fournisseur. Une simple modification permet donc de les contourner et de retrouver par conséquent un accès à la Z-Lib. Le seul moyen d'en couper définitivement l'accès serait donc d'en trouver les serveurs et de les désactiver. Une mission particulièrement ardue : ceux-ci sont disséminés dans de nombreux pays… dont la Russie, qui n'est peut-être pas encline à suivre les recommandations de la justice française actuellement.

      Contourner blocage FAI

    1. However, links between resources need not be format specific; it can be useful to have typed links that are independent of their serialisation, especially when a resource has representations in multiple formats.
    1. CTO services

      CTO services, or CTOaaS, stands for part-time tech and business advisory of the Chief Technology Officer to assist Small and Medium-sized Enterprises (SMEs).

      The core benefit of a startup fractional CTO compared to an in-house CTO is the price effectiveness of such a service as a company only pays for the services needed.

  6. Aug 2022
    1. I can't get behind the call to anger here, even if I don't approve of Apple's stance on being the gatekeeper for the software that runs on your phone.

      Elsewhere (in the comments by the author on HN), he or she writes:

      The biggest problem I try to convey is that you have no way of knowing you'll get the rejection

      No, I think there were pretty good odds that before even submitting the first iteration it would have been rejected, based purely on the concept alone. This is not an app. It's a set of pages—only implemented with the iOS SDK (and without any of the affordances, therefore, that you'd get if you were visiting in a Web browser. For whatever reason, the author both thought this was a good idea and didn't review the App Store guidelines and decided to proceed anyway.

      Then comes the part where Apple sends the rejection and tells the author that it's no different from a Web page and doesn't belong on the App Store.

      Here's where the problem lies: at the point where you're - getting rejections, and then - trying to add arbitrary complexity to the non-app for no reason other than to try to get around the rejection

      ... that's the point where you know you're wasting your time, if it wasn't already clear before—and, once again, it should have been. This is a series of Web pages. It belongs on the Web. (Or dumped into a ZIP and passed around via email.) It is not an app.

      The author in the same HN comment says to another user:

      So you, like me, wasted probably days (if not weeks) to create a fully functional app, spent much of that time on user-facing functions that you would have probably not needed

      In other words, the author is solely responsible for wasting his or her own time.

      To top it off, they finish their HN comment with this lament:

      It's not like on Android where you can just share an APK with your friends.

      Yeah. Know what else allows you to "just" share your work...? (No APK required, even!)

      Suppose you were taking classes and wanted to know the rubric and midterm schedule. Only rather than pointing you to the appropriate course Web page or sharing a PDF or Word document with that information, the professor tells you to download an executable which you are expected to run on your computer and which will paint that information on the screen. You (and everyone else) would hate them—and you wouldn't be wrong to.

      I'm actually baffled why an experienced iOS developer is surprised by any of the events that unfolded here.

    1. The “work around” was to detect users in an IAB and display a message on first navigation attempt to prompt them to click the “open in browser” button early.

      That's a pretty deficient workaround, given the obvious downsides. A more robust workaround would be to make the cart stateless, as far as the server is concerned, for non-logged-in users; don't depend on cookies. A page request instead amounts to a request for the form that has this and this and this pre-selected ("in the cart"). Like with paper.

    1. Historical Hypermedia: An Alternative History of the Semantic Web and Web 2.0 and Implications for e-Research. .mp3. Berkeley School of Information Regents’ Lecture. UC Berkeley School of Information, 2010. https://archive.org/details/podcast_uc-berkeley-school-informat_historical-hypermedia-an-alte_1000088371512. archive.org.

      https://www.ischool.berkeley.edu/events/2010/historical-hypermedia-alternative-history-semantic-web-and-web-20-and-implications-e.

      https://www.ischool.berkeley.edu/sites/default/files/audio/2010-10-20-vandenheuvel_0.mp3

      headshot of Charles van den Heuvel

      Interface as Thing - book on Paul Otlet (not released, though he said he was working on it)

      • W. Boyd Rayward 1994 expert on Otlet
      • Otlet on annotation, visualization, of text
      • TBL married internet and hypertext (ideas have sex)
      • V. Bush As We May Think - crosslinks between microfilms, not in a computer context
      • Ted Nelson 1965, hypermedia

      t=540

      • Michael Buckland book about machine developed by Emanuel Goldberg antecedent to memex
      • Emanuel Goldberg and His Knowledge Machine: Information, Invention, and Political Forces (New Directions in Information Management) by Michael Buckland (Libraries Unlimited, (March 31, 2006)
      • Otlet and Goldsmith were precursors as well

      four figures in his research: - Patrick Gattis - biologist, architect, diagrams of knowledge, metaphorical use of architecture; classification - Paul Otlet, Brussels born - Wilhelm Ostwalt - nobel prize in chemistry - Otto Neurath, philosophher, designer of isotype

      Paul Otlet

      Otlet was interested in both the physical as well as the intangible aspects of the Mundaneum including as an idea, an institution, method, body of work, building, and as a network.<br /> (#t=1020)

      Early iPhone diagram?!?

      (roughly) armchair to do the things in the web of life (Nelson quote) (get full quote and source for use) (circa 19:30)

      compares Otlet to TBL


      Michael Buckland 1991 <s>internet of things</s> coinage - did I hear this correctly? https://en.wikipedia.org/wiki/Internet_of_things lists different coinages

      Turns out it was "information as thing"<br /> See: https://hypothes.is/a/kXIjaBaOEe2MEi8Fav6QsA


      sugane brierre and otlet<br /> "everything can be in a document"<br /> importance of evidence


      The idea of evidence implies a passiveness. For evidence to be useful then, one has to actively do something with it, use it for comparison or analysis with other facts, knowledge, or evidence for it to become useful.


      transformation of sound into writing<br /> movement of pieces at will to create a new combination of facts - combinatorial creativity idea here. (circa 27:30 and again at 29:00)<br /> not just efficiency but improvement and purification of humanity

      put things on system cards and put them into new orders<br /> breaking things down into smaller pieces, whether books or index cards....

      Otlet doesn't use the word interfaces, but makes these with language and annotations that existed at the time. (32:00)

      Otlet created diagrams and images to expand his ideas

      Otlet used octagonal index cards to create extra edges to connect them together by topic. This created more complex trees of knowledge beyond the four sides of standard index cards. (diagram referenced, but not contained in the lecture)

      Otlet is interested in the "materialization of knowledge": how to transfer idea into an object. (How does this related to mnemonic devices for daily use? How does it relate to broader material culture?)

      Otlet inspired by work of Herbert Spencer

      space an time are forms of thought, I hold myself that they are forms of things. (get full quote and source) from spencer influence of Plato's forms here?

      Otlet visualization of information (38:20)

      S. R. Ranganathan may have had these ideas about visualization too

      atomization of knowledge; atomist approach 19th century examples:S. R. Ranganathan, Wilson, Otlet, Richardson, (atomic notes are NOT new either...) (39:40)

      Otlet creates interfaces to the world - time with cyclic representation - space - moving cube along time and space axes as well as levels of detail - comparison to Ted Nelson and zoomable screens even though Ted Nelson didn't have screens, but simulated them in paper - globes

      Katie Berner - semantic web; claims that reporting a scholarly result won't be a paper, but a nugget of information that links to other portions of the network of knowledge.<br /> (so not just one's own system, but the global commons system)

      Mention of Open Annotation (Consortium) Collaboration:<br /> - Jane Hunter, University of Australia Brisbane & Queensland<br /> - Tim Cole, University of Urbana Champaign<br /> - Herbert Van de Sompel, Los Alamos National Laboratory annotations of various media<br /> see:<br /> - https://www.researchgate.net/publication/311366469_The_Open_Annotation_Collaboration_A_Data_Model_to_Support_Sharing_and_Interoperability_of_Scholarly_Annotations - http://www.openannotation.org/spec/core/20130205/index.html - http://www.openannotation.org/PhaseIII_Team.html

      trust must be put into the system for it to work

      coloration of the provenance of links goes back to Otlet (~52:00)

      Creativity is the friction of the attention space at the moments when the structural blocks are grinding against one another the hardest. —Randall Collins (1998) The sociology of philosophers. Cambridge, MA: Harvard University Press (p.76)

    1. The management plugin is included in the RabbitMQ distribution. Like any other plugin, it must be enabled before it can be used. That's done using rabbitmq-plugins:

      rabbitmq的web界面需要先enable

    1. I feel those implications are very intellectually liberating and are far more cognitively organic than the print paradigm which currently shapes our intellectual mindset

      There's a lot to be gained by reflecting on pre-Web paradigms and hewing to similar approaches—electing to be bound by the constraints. Print is a discipline, and the practices surrounding the print-based publishing industry comprises a form of technology itself.

      Related: lineality is a virtue.

  7. Jul 2022
    1. List management TweetDeck allows you to manage your Lists easily in one centralized place for all your accounts. You can create Lists in TweetDeck filtered by by your interests or by particular accounts. Any List that you have set up or followed previously can also be added as separate columns in TweetDeck.   To create a List on TweetDeck: From the navigation bar, click on the plus icon  to select Add column, then click on Lists  .Click the Create List button.Select the Twitter account you would like to create the List for.Name the List and give it a description then select if you would like the List to be publicly visible or not (other people can follow your public Lists).Click Save.Add suggested accounts or search for users to add members to your List, then click Done.   To edit a List on TweetDeck: Click on Lists  from the plus icon  in the navigation bar.Select the List you would like to edit.Click Edit.Add or remove List members or click Edit Details to change the List name, description, or account. You can also click Delete List.When you're finished making changes, click Done.     To designate a List to a column: Click on the plus icon  to select Add column.Click on the Lists option from the menu.Select which List you would like to make into a column.Click Add Column.   To use a particular List in search: Add a search column, then click the filter icon  to open the column filter options.Click the  icon to open the User filter. Select By members of List and type the account name followed by the List name. You can only search across your own Lists, or others’ public Lists.

      While you still can, I'd highly encourage you to use TweetDeck's "Export" List function to save plain text lists of the @ names in your... Lists.

  8. www.mojeek.com www.mojeek.com
    1. Mojeek

      Mojeek is the 4th largest English lang. web search engine after Google, Bing and Yandex which has it's own index, crawler and algo. Index has passed 5.7 billion pages. Growing. Privacy based.

      It uses it's own index with no backfill from others.

    1. The Human Takeover: A Call for a Venture into anExistential Opportunity
      • Title: The Human Takeover: A Call for a Venture into an Existential Opportunity
      • Author: Marta Lenartowicz, David R. Weinbaum, Francis Heylighen, Kate Kingsbury and Tjorven Harmsen
      • Date: 5 April, 2018
    2. e moment of transition of the Internet—from mediating information to mediating distributeddirect governance in the sense of self-organization.
      • With proper design, the internet can play a more proactive role
      • From passive to active, sensemaking to action
      • Cosmolocal production: https://clreader.net
      • Web 3 technology
      • Indyweb
    1. But both of these issues are trivially solved if we simply begin with today's lightly hyperlinked documents, and let the reader's computer generate links on-demand. When I'm reading something and don't understand a particular word or want to know more about a quote, when I select it, my computer should search across everything I've read and some small high-quality subset of the Web to bring me 5-10 links about what I've highlighted that are the most relevant to what I'm reading now. Boom. Everything is a hyperlink.
    1. the Web has lost a sense of place that it used to have. Today’s Web is a condition of being – being online, being connected, being subject to the flow of the feeds. A sense of place is what allows humans to gather and meet and have conversations, and with fewer places on the Web feeling like real spaces we can enjoy, I think we find our conversations pushed out into the few places that retain that metaphor of place.
    1. I knew if I wanted this website – which is an extension of my consciousness – to truly thrive, I needed to work on it in a sustainable manner. Bit by bit I slowly transformed the way I thought about it. Previously I would only work on it if I had the energy to make wholesale, dramatic changes. These days I am glad if I made one small change.

      Winnie later goes on to point out that this is much like gardening: it is a slow process, and the process has its seasons which wax and wane, expanding and contracting. You sow. You seed. You water. You fertilize. You wait. You pick weeds. You water. Pick some more weeds. You might prune. You flick off the japanese beetles. And because of the cyclical nature of the planet we inhabit, we also have periods where nothing grows, and the soil lies dormant. Waiting. Resting. This, too, can be embraced as we carve out our little corners of the web, and really all aspects of our lives. I know I'm nearly as tender to myself as I should be.

    1. just to give you a feel for how powerful these systems are just think of the bitcoin energy consumption and realize that that 00:09:48 just drops out of two components in bitcoin one is the block reward impact evaluator and two the price of bitcoin so those two things yield this tremendous energy 00:10:00 consum consuming system this was kind of an accident this was a an accident of nobody quite intended this this device to um consume this this amount of energy and waste this amount of energy uh but 00:10:13 this gives you a sense of the power of these these uh systems first off we should fix this and you know get out get to uh better systems that that actually uh make this this um energy use uh useful 00:10:25 uh but this i use as an example to give you a sense of like the level of power that comes from these incentive structures and their operation at scale in falcon we're very familiar with these kinds of structures we use the same component and we've gotten a feel for how powerful 00:10:38 this stuff is um in just a couple of years we ended up organizing the build out of a massive hardware infrastructure for providing storage to the world um with again just using one 00:10:51 core incentive structure a block reward uh so all of this makes me really really hopeful um that we'll be able to build um these kinds of incentive structures that can scale to solve extremely large planetary scale 00:11:03 problems um by designing incentive structures and structures warping the incentive fields and getting us to little by little problem by problem scale by scale um solve challenges 00:11:17 and so i think i greatly encourage you if you aren't already in this uh world to try it out to try creating some smart contracts and deploying them um to try uh working with other projects and so on 00:11:29 to get a feel for how powerful these these systems are um i i'm very hopeful that things like this will have a huge impact on planetary scale problems like uh climate change um i've become very hopeful that 00:11:41 these systems will let us coordinate massive action again millions of people billions of people whole industries by letting us have the full power of law and economics and so on in a fully 00:11:55 programmable environment i'm also very hopeful that we can get to accelerate science and technology development by using these kinds of structures to create instruments to incentivize areas of the innovation chasm that are 00:12:08 underserved areas where it's extremely difficult to get funding for certain projects or where it's extremely difficult to get long-term rewards or long-term success many of you have probably heard me talk 00:12:21 about this science and technology translation problem and the lack of incentive structures in that in that period in the castle in the middle and i think a lot of that just comes from the lack of reward structures there that make it impossible for 00:12:34 groups building groups building building projects there to raise capital um because there's no good incentive for capital uh to to deploy there so uh what brought us to so knowing all 00:12:46 of this knowing that this is a critical century knowing that um this critical decade and year um and knowing that crypticon is extremely powerful um why are we here why are we in funding commons so we thought about this problem last year and 00:12:59 we saw that the scale of problem of um of blockchains and the kind of rapid pace of development in industry and the emergence of things like defy and dials and nfts and so on 00:13:10 and especially the the broad adoption by hundreds of thousands of people or millions of people of these tools gave us a very promising um landscape to be able to solve these kinds of problems 00:13:23 and so we have the potential to solve all these massive coordination problems but we're lacking good mechanisms we need way better governance structures we need way better funding mechanisms and uh and so on we need to study these things with much 00:13:36 deeper theory and much deeper experimental analysis and so on

      Bitcoin, in spite of its unintended consequences, does demonstrate the power and potential of these kinds of systems to scale.

    1. resulting HTML

      Imagine if this were just the format that the source document itself used...

    1. I recently started building a website that lives at wesleyac.com, and one of the things that made me procrastinate for years on putting it up was not being sure if I was ready to commit to it. I solved that conundrum with a page outlining my thoughts on its stability and permanence:

      It's worth introspecting on why any given person might hesitate to feel that they can commit. This is almost always comes down to "maintainability"—websites are, like many computer-based endeavors, thought of as projects that have to be maintained. This is a failure of the native Web formats to appreciably make inroads as a viable alternative to traditional document formats like PDF and Word's .doc/.docx (or even the ODF black sheep). Many people involved with Web tech have difficulty themselves conceptualizing Web documents in these terms, which is unfortunate.

      If you can be confident that you can, today, bang out something in LibreOffice, optionally export to PDF, and then dump the result at a stable URL, then you should feel similarly confident about HTML. Too many people have mental guardrails preventing them from grappling with the relevant tech in this way.

    1. https://www.zylstra.org/blog/2022/06/spring-83/

      I've been thinking about this sort of thing off and on myself.

      I too almost immediately thought of Fraidyc.at and its nudge at shifting the importance of content based on time and recency. I'd love to have a social reader with additional affordances for both this time shifting and Ton's idea of reading based on social distance.

      I'm struck by the seemingly related idea of @peterhagen's LindyLearn platform and annotations: https://annotations.lindylearn.io/new/ which focuses on taking some of the longer term interesting ideas as the basis for browsing and chewing on. Though even here, one needs some of the odd, the cutting edge, and the avant garde in their balanced internet diet. Would Spring '83 provide some of this?

      I'm also struck by some similarities this has with the idea of Derek Siver's /now page movement. I see some updating regularly while others have let it slip by the wayside. Still the "board" of users exists, though one must click through a sea of mostly smiling and welcoming faces to get to it the individual pieces of content. (The smiling faces are more inviting and personal than the cacophony of yelling and chaos I see in models for Spring '83.) This reminds me of Stanley Meyers' frequent assertion that he attempted to design a certain "sense of quiet" into the early television show Dragnet to balance the seeming loudness of the everyday as well as the noise of other contemporaneous television programming.

      The form reminds me a bit of the signature pages of one's high school year book. But here, instead of the goal being timeless scribbles, one has the opportunity to change the message over time. Does the potential commercialization of the form (you know it will happen in a VC world crazed with surveillance capitalism) follow the same trajectory of the old college paper facebook? Next up, Yearbook.com!

      Beyond the thing as a standard, I wondered what the actual form of Spring '83 adds to a broader conversation? What does it add to the diversity of voices that we don't already see in other spaces. How might it be abused? Would people come back to it regularly? What might be its emergent properties?

      It definitely seems quirky and fun in and old school web sort of way, but it also stresses me out looking at the zany busyness of some of the examples of magazine stands. The general form reminds me of the bargain bins at book stores which have the promise of finding valuable hidden gems and at an excellent price, but often the ideas and quality of what I find usually isn't worth the discounted price and the return on investment is rarely worth the effort. How might this get beyond these forms?

      It also brings up the idea of what other online forms we may have had with this same sort of raw experimentation? How might the internet have looked if there had been a bigger rise of the wiki before that of the blog? What would the world be like if Webmention had existed before social media rose to prominence? Did we somehow miss some interesting digital animals because the web rose so quickly to prominence without more early experimentation before its "Cambrian explosion"?

      I've been thinking about distilled note taking forms recently and what a network of atomic ideas on index cards look like and what emerges from them. What if the standard were digital index cards that linked and cross linked to each other, particularly in a world without adherence to time based orders and streams? What does a new story look like if I can pull out a card either at random or based on a single topic and only see it or perhaps some short linked chain of ideas (mine or others) which come along with it? Does the choice of a random "Markov monkey" change my thinking or perspective? What comes out of this jar of Pandora? Is it just a new form of cadavre exquis?

      This standard has been out for a bit and presumably folks are experimenting with it. What do the early results look like? How are they using it? Do they like it? Does it need more scale? What do small changes make to the overall form?


      For more on these related ideas, see: https://hypothes.is/search?q=tag%3A%22spring+%2783%22

  9. Jun 2022
    1. Is it just me or is there something quirky with the rel="canonical" links for docdrop so that there isn't URL parity for the annotations on docdrop and the equivalent youtube videos. I thought it used to work, but when I visit the youtube version, there are no annotations on the page. I thought this used to work the way one would expect. What changed?

      I'm noticing that in this particular case there are two rel-canonical links when one might expect only one:

      <link rel="canonical" href="https://www.youtube.com/watch?v=XgMh6iuFbT4"><br /> <link rel="canonical" href="http://docdrop.org/video/XgMh6iuFbT4/">

      Maybe the docdrop link should be a rel="alternate" instead?

      cc: @dwhly

    1. This podcast is also available on Spotify, Apple Podcasts and Anchor. Please subscribe on your favoured podcast provider and leave a review.

      There are actually seven different services that this podcaster has done a huge amount of work to put their content on, ostensibly for the widest discovery, but not a single one of them has a link to the raw audio file to make it easy for one to bookmark and listen to later. Apparently the podcasting silo services have managed to win out over the open web.

      Do we really need to make podcasting this hard on individual publishers? Why can't the publisher just have one location and tell all the aggregators, here's a link to my feed, copy it if you will and want to help distribute my content? In some sense, this is part of what is happening as all seven services are using the same findable source, they're just making it more difficult to jump through all the hoops, which means the small guys end up paying more to do the extra work and potentially lose everything if that one source disappears, closes down, or gets acquired and goes away.

      These sorts of artificial hurdles and problems are what make it so hard to get up and running.

    1. https://briansunter.com/graph/#/page/logseq-social

      Brian Sunter (twitter) using Logseq as a social network platform.

      What simple standards exist here? Could this more broadly and potentially be used to connect personal wikis, digital gardens, zettelkasten, etc?

      Note that in this thread Dave Winer asks about how it can be tied into other standardized pieces to interconnect?

      How can I hook my outlines into your net if I’m not running Logseq?

      — dave.rss (@davewiner) June 13, 2022
      <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
    1. We still imagine the web as a series of paper documents with text and images presented on them.

      I don't know if this is true for anyone. It certainly seems like most people who are digital natives (or immigrants) rarely make the connection and end up missing out on some lessons from print that would actually be helpful.

  10. May 2022
    1. the skills to tweak an app or website into what they need

      Does "what they need" here implicitly mean "a design that no one really benefits from but you can bill a client for $40+/hr for"? Because that's how Glitch comes off to me—more vocational (and even less academic) than a bootcamp without the structure.

      What was that part about home-cooked meals?

    2. Building and sharing an app should be as easy as creating and sharing a video.

      This is where I think Glitch goes wrong. Why such a focus on apps (and esp. pushing the same practices and overcomplicated architecture as people on GitHub trying to emulate the trendiest devops shovelware)?

      "Web" is a red herring here. Make the Web more accessible for app creation, sure, but what about making it more accessible (and therefore simpler) for sharing simple stuff (like documents comprising the written word), too? Glitch doesn't do well at this at all. It feels less like a place for the uninitiated and more like a place for the cool kids who are already slinging/pushing Modern Best Practices hang out—not unlike societal elites who feign to tether themself to the mast of helping the downtrodden but really use the whole charade as machine for converting attention into prestige and personal wealth. Their prices, for example, reflect that. Where's the "give us, like 20 bucks a year and we'll give you better alternative to emailing Microsoft Office documents around (that isn't Google Sheets)" plan?

    1. Text file You can provide a simple text file that contains one URL per line. The text file must follow these guidelines: The text file must have one URL per line. The URLs cannot contain embedded new lines. You must fully specify URLs, including the http. Each text file can contain a maximum of 50,000 URLs and must be no larger than 50MB (52,428,800 bytes). If you site includes more than 50,000 URLs, you can separate the list into multiple text files and add each one separately. The text file must use UTF-8 encoding. You can specify this when you save the file (for instance, in Notepad, this is listed in the Encoding menu of the Save As dialog box). The text file should contain no information other than the list of URLs. The text file should contain no header or footer information. If you would like, you may compress your Sitemap text file using gzip to reduce your bandwidth requirement. You can name the text file anything you wish. Please check to make sure that your URLs follow the RFC-3986 standard for URIs, the RFC-3987 standard for IRIs You should upload the text file to the highest-level directory you want search engines to crawl and make sure that you don't list URLs in the text file that are located in a higher-level directory. Sample text file entries are shown below. http://www.example.com/catalog?item=1 http://www.example.com/catalog?item=11

      There's been a plaintext sitemap standard this whole time??? Lmao I'm an idiot.

    1. the decentralised and open source nature of these systems, where anyone can host an instance, may protect their communities from the kinds of losses experienced by users of the many commercial platforms that have gone out of business over the last decades (e.g. Geocities, Wikispaces or Google + to name just a few).

      https://indieweb.org/site-deaths names a large number of others

    1. On the other hand, the notion of the “document” that is intrinsic to web development today is overdetermined by the legacy of print media.

      I dunno. I think all the things about dynamism and liveness that follow this claim are true in the minds of most people. The rarity is for people to conceive of content on the Web (or elsewhere rendered to a computer screen) as capable of being imbued with the fixity of print. Everything feels transient and rests on a shaky, fleeting foundation..

    1. it's not as simple as copying homepage.php to homepagenew.php, hacking on it until it works, and then renaming homepagenew.php to homepage.php

      It actually can be easier than that if the only reason PHP is involved is for templating and you don't want CGI. (NB: This is admittedly contra "the mildly dynamic website" described in the article).

      If you're Alice of alice.example.com, then you open up your local copy of e.g. https://alice.example.com/sop/pub.app.htm, proceed to start "hacking on it until it works", then rsync the output.

    1. Are you limited to PHP?

      No, but further: the question (about being "limited") presupposes something that isn't true.

      If you're doing PHP here, you're doing it wrong—unless the PHP application is written with great care (i.e. unidiomatically) and has some way to reveal its own program text (as first-class content). Otherwise, that's a complete failure to avoid the "elsewhere"-ness that we're trying to eradicate.

    2. who hosts that?

      Answer: it's hosted under the same auspices as the main content. The "editor" is first-class content (in the vein of ANPD); it's really just another document describing detailed procedures for how the site gets updated.

    1. Perhaps each page load shows a different, randomly chosen header image.

      That makes them constitute separate editions. It makes things messy.

    1. My argument for the use of the Web as a medium for publishing the procedures by which the documents from a given authority are themselves published shares something in common with the argument for exploiting Lisp's homoiconicity to represent a program as a data structure that is expressed like any other list.

      There are traces here as well from the influence of the von Neumann computational model, where programs and data are not "typed" such that they belong to different "classes" of storage—they are one and the same.

    1. However when you look UNDERNEATH these cloud services, you get a KERNEL and a SHELL. That is the "timeless API" I'm writing to.

      It's not nearly as timeless as a person might have themselves believe, though. (That's the "predilection" for certain technologies and doing things in a certain way creeping in and exerting its influence over what should otherwise be clear and sober unbiased thought.)

      There's basically one timeless API, and that means written procedures capable of being carried out by a human if/when everything else inevitably fails. The best format that we have for conveying the content comprising those procedures are the formats native to the Web browser—esp. HTML. Really. Nothing else even comes close. (NB: pixel-perfect reproduction à la PDF is out of scope, and PDF makes a bunch of tradeoffs to try to achieve that kind of fidelity which turns out to make it unsuitable/unacceptable in a way that HTML is not, if you're being honest with your criteria, which is something that most people who advocate for PDF's benefits are not—usually having deceived even themselves.)

      Given that Web browsers also expose a programming environment, the next logical step involves making sure these procedures are written to exploit that environment as a means of automation—for doing the drudge work in the here and now (i.e., in the meantime, when things haven't yet fallen apart).

    1. copying and pasting into an online html  editor, then hitting the clean up button?   Copy this cleaned up html into one of your  posts, save it, and view.

      This could/should be part of Zonelets itself.

    1. Updating the script

      This is less than ideal. Besides non-technical people needing to wade into the middle of (what very well might appear to them to be a blob of) JS to update their site, here are some things that Zonelets depends on JS for:

      1. The entire contents of the post archives page
      2. The footer
      3. The page title

      This has real consequences for e.g. the archivability for a Zonelets site.

      The JS-editing problem itself could be partially ameliorated by with something like the polyglot trick used on flems.io and/or the way triple scripts do runtime feature detection using shunting. When the script is sourced via script element from another page, it behaves as JS, but when visited directly as the browser destination it is treated like HTML and has its own DOM tree for the script itself to make the necessary modifications easier. Instead of requiring the user to edit it as freeform text, provide a structured editing interface, so e.g. adding a new post is as simple as clicking the synthesized "+" button in the list of posts, copying the URL of the post in question, and then pasting it in—to a form field. The Zonelets script itself should take care of munging it into the appropriate format upon form "submission". It can also, right there, take care of the escaping issue described in the FAQ—allow the user to preview the generated post title and fix it up if need be.

      Additionally, the archives page need not by dynamically generated by the client—or rather, it can be dynamically filled in exactly once per update—on the author's machine, and then be reified into static HTML, with the user being instructed to save it and overwrite the served version. This gets too unwieldy for next/prev links in the footer, but (a) those are non-essential, and don't even get displayed for no-JS users right now, anyway; and (b) can be seen to violate the entire "UNPROFESSIONAL" etthos.

      Alternatively, the entire editing experience can be complimented with bookmarklets.

    1. it’s hard to look at recent subscription newsletter darling, Substack, without thinking about the increasingly unpredictable paywalls of yesteryear’s blogging darling, Medium. In theory you can simply replatform every five or six years, but cool URIs don’t change and replatforming significantly harms content discovery and distribution.