1,647 Matching Annotations
  1. Last 7 days
  2. small-tech.org small-tech.org
    1. Personal Small Technology are everyday tools for everyday people. They are not tools for startups or enterprises. Easy to use Personal technology are everyday things that people use to improve the quality of their lives. As such, in addition to being functional, secure, and reliable, they must be convenient, easy to use, and inclusive. If possible, we should aim to make them delightful. Related aspects: inclusive Non-colonial Small technology is made by humans for humans. They are not built by designers and developers for users. They are not built by Western companies for people in African countries. If our tools specifically target a certain demographic, we must ensure that our development teams reflect that demographic. If not, we must ensure people from a different demographic can take what we make and specialise it for their needs. Related aspects: share alike, non-commercial, interoperable Private by default A tool respects your privacy only if it is private by default. Privacy is not an option. You do not opt into it. Privacy is the right to choose what you keep to yourself and what you share with others. “Private” (i.e., for you alone) is the default state of small technologies. From there, you can always choose who else you want to share things with. Related aspects: zero knowledge, peer to peer Zero knowledge Zero-knowledge tools have no knowledge of your data. They may store your data, but the people who make or host the tools cannot access your data if they wanted to. Examples of zero-knowledge designs are end-to-end encrypted systems where only you hold the secret key, and peer-to-peer systems where the data never touches the devices of the app maker or service provider (including combinations of end-to-end encrypted and peer-to-peer systems). Related aspects: private by default, peer to peer Peer to peer Peer-to-peer systems enable people to connect directly with one and another without a person (or more likely a corporation or a government) in the middle. They are the opposite of client/server systems, which are centralised (the servers are the centres). On peer to peer systems, your data – and the algorithms used to analyze and make use of your data – stay in spaces that you own and control. You do not have to beg some corporation to not abuse your data because they don’t have it to begin with. Related aspects: zero knowledge, private by default Share alike Most people’s eyes cloud over when technology licenses are mentioned but they’re crucial to protecting your freedom. Small Technology is licensed under Copyleft licenses. Copyleft licenses stipulate that if you benefit from technology that has been put into the commons, you must share back (“share alike”) any improvements, changes, or additions you make. If you think about it, it’s only fair: if you take from the commons, you should give back to the commons. That’s how we cultivate a healthy commons. Related aspects: interoperable, non-colonial, non-commercial Interoperable Interoperable systems can talk to one another using well-established protocols. They’re the opposite of silos. Interoperability ensures that different groups can take a technology and evolve it in ways that fit their needs while still staying compatible with other tools that implement the same protocols. Interoperability, coupled with share alike licensing, helps us to distribute power more equally as rich corporations cannot “embrace and extend” commons technology, thereby creating new silos. Interoperability also means we don’t have to resort to colonialism in design: we can design for ourselves and support other groups who design for themselves while allowing all of us to communicate with each other within the same global network. Related aspects: share alike, non-colonial Non-commercial The primary purpose for Small Technology is not to make a profit but to increase human welfare. As such, they are built by not-for-profit organisations. Eventually, we hope that small technologies will be recognised for their contribution to the common good and therefore supported from the commons (e.g., from our taxes). In the interim, some methods for monetising Small Technology include: Charging for hosting and maintenance services Sales on App Stores (for native apps) Donations and patronage Grants and awards Equity-based / Venture Capital investment is incompatible with Small Technology as the success criterion is the sale of the organisation (either to a larger organisation or to the public at large via an IPO). Small Technology is not about startups (temporary companies designed to either fail fast or grow exponentially and get sold), it’s about stayups (sustainable organisations that contribute to the common good). Related aspects: non-colonial, share alike, interoperable Inclusive Being inclusive in technology is ensuring people have equal rights and access to the tools we build and the communities who build them, with a particular focus on including people from traditionally marginalised groups. Accessibility is the degree to which technology is usable by as many people as possible, especially disabled people Small Technology is inclusive and accessible. With inclusive design, we must be careful not to assume we know what’s best for others, despite us having differing needs. Doing so often results in colonial design, creating patronising and incorrect solutions.

      Small Technology Small Technology are everyday tools for everyday people designed to increase human welfare, not corporate profits.

    1. 1476. These attacks were accomplished with bots (automated software applications) that“scraped” and harvested data from WorldCat.org and other WorldCat®-based research sites andthat called or pinged the server directly. These bots were initially masked to appear as legitimatesearch engine bots from Bing or Google.

      Bots initially masked themselves as search engine bots

    2. By hacking WorldCat.org, scraping and harvesting OCLC’s valuable WorldCat

      Complain equates “hacking” with “scraping and harvesting”

      This is a matter of some debate—notably the recent LLM web scraping cases.

  3. Mar 2024
  4. Feb 2024
  5. Jan 2024
    1. These institutions are designed to support individuals and their habitats, reversing the current dynamic where people and their environments appear to serve institutions.

      for - flipping the institutional web - Tools for the Commons - to create regenerative institutions

    1. There’s not much of a market for what I’m describing.

      There is, actually. Look at Google Docs, Office 365, etc. Those are all an end-run around the fact that webdevs are self-serving and haven't prioritized making desktop publishing for casual users a priority.

      The webdev industry subverts users' ability to publish to the Web natively, and Google, MS et al subvert native Web features in order to capture users.

      The users are there.

      • for: collaborative commons, rapid whole system change - governance, 3rd party, TPF, power2thepeople political power, criminal power

      -SUMMARY - A good article that - briefly traced the roots of the the major categories of power in modernity: - government - business - NGOs - and provides an argument for the emergence of a 4th power - the collaborative commons - it provide a model for the collaborative commons and a system diagram showing the various parts - I've critique I raise it that since it could only emerge within the technological mileau of the internet, it cannot be based upon an archaic, corporate and centralized power be structure. Even cryptocurrency is still centralized and there is generally a single point of failure. - When more important than decentralisation however, is that the current web id not people-centered and intertwingled with interpersonal - a necessary condition for a collaborative commons is their what we call a "flipped" web. - The indyweb and Indranet are being designed as an open function opens learning ecosystem for humanity at the level of trust networks - inter-operating with other larger systems, it can pay a role in creating the flipped web which can provide the human communication media for a collaborative commons

      • comment

        • There night also be a bother 4th category of power not me- criminal mentioned - criminal power
      • epiphany: new slogan

        • power2thepeople has a double meaning
          • political power
          • physical power
        • since modern society runs on physical power, we need the people too control it rather than serving a small group of financial elites
    1. Venkatesh Rao thinks that the Nazi bar analogy is “an example of a bad metaphor contagion effect” and points to a 2010 post of his about warren vs plaza architectures. He believes that Twitter, for example, is a plaza, whereas Substack is a warren: A warren is a social environment where no participant can see beyond their little corner of a larger maze. Warrens emerge through people personalizing and customizing their individual environments with some degree of emergent collaboration. A plaza is an environment where you can easily get to a global/big picture view of the whole thing. Plazas are created by central planners who believe they know what’s best for everyone.
    1. Associated individuals[edit] In a New York Times editorial, Bari Weiss listed individuals associated with the intellectual dark web, including Ayaan Hirsi Ali, Sam Harris, Heather Heying, Claire Lehmann, Bill Maher, Douglas Murray, Maajid Nawaz, Camille Paglia, Jordan Peterson, Steven Pinker, Joe Rogan, Dave Rubin, Ben Shapiro, Michael Shermer, Christina Hoff Sommers, Bret Weinstein, and Eric Weinstein.

      It's somewhat interesting and potentially non-coincidental that the entirety of this list aside from Sam Harris and Camille Paglia are highlighted as anti-trans (red) by the browser extension Shinigami Eyes.

    2. The intellectual dark web (IDW) is a term used to describe some commentators who oppose identity politics, political correctness, and cancel culture in higher education and the news media within Western countries.
  6. Dec 2023
  7. Nov 2023
    1. 尝试过 HUGO 和 Notion 等方式、研究了 obsidian publish,也实践用 Notion 维护了一年的博客,但一直没有找到比较理想的方案。

      想知道這些其他方案的缺點在哪。我自己用的是免費的Obsidian digital garden來Publish部落格。

    1. When can we expect the Web to stop pretending to be the old things, and start being what it really ought to be?

      The Web already is what it is, at least—and what that is is not an imitation of the old. If anything, it ought to be more like the old, cf Tschichold.

      Things like citability are crucial, not just generally, but in that they are fundamental to what the Web was supposed to have been, and modern Web practices overwhelmingly sabotage it.

    2. This conference imitating the old Providing papers for this conference is a choice between latex (which is a pre-web technology) or Word! There's a page limit! There's a styleguide on how references should be visually displayed! IT'S ALL ABOUT PAPER!
    1. I've highlighted the shit out of this because I believe it actually argues a fundamental truth: communicating electronically is, indeed, a better way of communicating.

      I don't think this friendship had to die, but the illusion of romance probably did. I'm going to do my best to choose to ignore the confirmation bias within me - could it be the absence of stigma that enabled these realizations? Is the stigma, itself, then, now a virtually all-powerful (beyond any measure of reflection) force which will never allow us to progress???

      Fuck hype, man.

  8. Oct 2023
    1. HTML had blown open document publishing on the internet

      ... which may have really happened, per se, but it didn't wholly incorporate (subsume/cannibalize) conventional desktop publishing, which is still in 2023 dominated by office suites (a la MS Word) or (perversely) browser-based facsimiles like Google Docs. Because the Web as it came to be used turned out to be as a sui generis medium, not exactly what TBL was aiming for, which was giving everything (everything—including every existing thing) its own URL.

    1. Let’s look at some of the attributes of the memex. Your machine is a library not a publication device. You have copies of documents is there that you control directly, that you can annotate, change, add links to, summarize, and this is because the memex is a tool to think with, not a tool to publish with.

      Alan Jacobs argues that the Memex is not a tool to publish with and is thus fundamentally different from the World Wide Web.

      Did Vannevar Bush suggest the Memex for writing or potentially publishing? [Open question to check] Would it have been presumed to have been for publishing if he suggests that it was for annotating, changing, linking and summarizing? Aren't these actions tantamount to publishing, even if they're just for oneself?

      Wouldn't academics have built the one functionality in as a precursor to the other?

    2. “A tool to think with, not a tool to publish with” — this seems to me essential. I feel that I spend a lot of time trying to think with tools meant for publishing.
    1. Rather than dealing with the invariably convoluted process of moving my content between systems — exporting it from one, importing it into another, fixing any incompatibilities, maybe removing some things that I can’t find a way to port over — I drop my Markdown files into the new website and it mostly Just Works.

      What if you just dropped your pre-rendered static assets into the new system?

    1. The important part, as is so often the case with technology, isn’t coming up with a solution to the post portability problem, but coming up with a solution together so that there is mutual buy-in and sustainability in the approach.

      The solution is to not create keep creating these fucking problems in the first place.

  9. Sep 2023
    1. permit streams to be transferred between workers, frames and anywhere else that postMessage() can be used. Chunks can be anything which is cloneable by postMessage(). Initially chunks enqueued in such a stream will always be cloned, ie. all data will be copied. Future work will extend the Streams APIs to support transferring objects (ie. zero copy).

      js const rs = new ReadableStream({ start(controller) { controller.enqueue('hello'); } }); const w = new Worker('worker.js'); w.postMessage(rs, [rs]);

      js onmessage = async (evt) => { const rs = evt.data; const reader = rs.getReader(); const {value, done} = await reader.read(); console.log(value); // logs 'hello'. };

    1. Mass electronic surveillance by governments revealed over the last several years has spurred a new movement to re-decentralize the web, a movement to empower individuals to be their own service providers again.
    1. A big problem with what's in this paper is that its logical paths reflect the déformation professionnelle of its author and the technologists' milieu.

      Links are Works Cited entries. Works Cited entries don't "break"; the works at the other end don't "change".

    1. There is one particular type of document in which the correct handling of the ordinal numbers of lists is paramount. A document type in which the ordinal numbers of the lists cannot be arbitrarily assigned by computer, dynamically, and in which the ordinal numbers of the lists are some of the most important content in the document.I'm referring of course to law.HTML, famously, was developed to represent scientific research papers, particularly physics papers. It should come as no surprise that it imagines documents to have things like headings and titles, but fails to imagine documents to have things like numbered clauses, the ordinal numbers of which were assigned by, for example, an act of the Congress of the United States of America.Of course this is not specific to any one body of law - pretty much all law is structured as nested ordered lists where the ordinal numbers are assigned by government body.It is just as true for every state in the Union, every country, every province, every municipality, every geopolitical subdivision in the world.HTML, from the first version right up to the present version, is fundamentally inimical to being used for marking up and serving legal codes as web pages. It can be done, of course - but you have to fight the HTML every step of the way. You have no access to any semantic markup for the task, because the only semantic markup for ordered lists is OL, which treats the ordinal numbers of ordered lists as presentation not content.
    1. To build HIPAA compliant software, developers need to be aware of and comply with several key requirements outlined in the HIPAA Privacy Rule and Security Rule. These requirements are designed to ensure the confidentiality, integrity, and availability of protected health information (PHI) and to prevent unauthorized access, use, or disclosure of PHI.

      Building software compliant with HIPAA standards necessitates a deep understanding of its Privacy and Security Rules to safeguard protected health information effectively.

    1. We will try to add two tests for response code in order to know that our request was successful. Another test we will add for response time <  2 sec in order to understand how fast request was processed by server. If it will be executed slower then for 2 seconds, our test will fail. In this case I use 2 seconds just for example it might be greater or lower number, but 7 seconds is usually a maximum time for request execution. So in order to add tests, go to “Tests” in request section of application and add this few lines : tests["Status code is 200"] = responseCode.code === 200; tests["Response time is less than 200ms"] = responseTime < 2000; When this is done hit on Send button again and execute your first test.

      Good case -- importance of adding tests to validate response codes and times, ensuring optimal server performance and response.

    1. Configuring PyCharm: Open PyCharm with ‘Pytest Web Framework’ Press Ctrl+Alt+S > Project Click ‘Project Interpreter’ Select Python 3.6 Click ‘OK’ Go to write over 100500 automated tests!!!

      This section provides a step-by-step guide on setting up PyCharm for automated testing using the 'Pytest Web Framework'.

    1. There are many reasons why you might want to migrate from one stack to another. Maybe you’re looking for a more robust solution, or perhaps you’re trying to simplify your development process. Whatever the reason, it’s important to know that it is possible to migrate from one stack to another.

      Migration between tech stacks can be driven by various motivations, including the need for enhanced capabilities or a desire for a more streamlined development workflow.

    1. It also simplifies Magento order management, providing a centralized dashboard for handling customer orders and inquiries. Efficient order management can lead to improved customer satisfaction and increased sales. For more insights, check out this Magento Commerce Resources page.

      Magento's order management system offers a unified platform, making it easier for businesses to manage customer interactions and orders, enhancing operational efficiency.

    1. Developers use tools like Postman for API test automation to create WMS system integration technologies that help you increase efficiency by automating manual processes. The WMS connects all of your warehouse locations so that you can easily access information about your inventory, orders, and shipments from any computer.

      Leveraging tools such as Postman, developers can automate API tests, leading to the creation of efficient Warehouse Management System (WMS) integrations that streamline operations.

    1. Additionally, they are at the forefront of sharing valid product ideas with their team since they have an expert understanding of coding best practices as well as mobile and web programming services.

      Developers play a pivotal role in product ideation due to their deep knowledge of coding standards and expertise in both mobile and web development.

    1. Time Required to Code: Every project comes with a deadline, and the time set out by your client to get the work done is a crucial part of your decision. If you have a tight deadline, you might be better off with the fastest front-end framework you can find. One that would work well with your team’s capabilities to ensure great results in the shortest time possible.

      The efficiency of a front-end framework can significantly impact project timelines. Choosing a framework that aligns with the project's deadline and the team's proficiency can ensure timely delivery.

    1. So now we have a file that you need to open in JMeter UI, configure number of threads that you want to execute and you are good to go.

      After converting the Postman test into a JMeter format, users can easily adjust the concurrency settings by configuring the number of threads in the JMeter UI, offering flexibility in load testing scenarios.

    1. Let’s add a test that will validate that number of results on a page is lower then total number of results.

      This code snippet in Postman ensures that the number of displayed results on a single page is always less than the total count of results, ensuring pagination is functioning correctly.

  10. Aug 2023
    1. In computing, the robustness principle is a design guideline for software that states: "be conservative in what you do, be liberal in what you accept from others". It is often reworded as: "be conservative in what you send, be liberal in what you accept". The principle is also known as Postel's law, after Jon Postel, who used the wording in an early specification of TCP.

      https://en.wikipedia.org/wiki/Robustness_principle

      Robustness principle: be conservative in what you do, be liberal in what you accept from others.

    1. We really f'ed up the web didn't we?
    2. I think I get what you're saying but I have some difficulty moving past the fact that you're claiming it doesn't need to be a website because it would be sufficient if it was a bunch of hosted markup documents that link to each other.
    1. One of the things I loved most about Twitter was the way it could throw things in front of me that I never would have even thought to go look for on my own.

      I'm afraid this is one of those sentiments that should absolutely be tossed in the because of lack of user control category

    2. Constantly being told I was somewhat dim because I didn’t understand how to do things or what the unwritten rules were.

      This, I particularly hate and hope desperately I did not contribute to.

    3. which I pulled out of the API as a JSON file by tweaking a bash script a nice stranger wrote up on the spot when I asked about JSON export

      This I would very much like to learn more details about... I've been unable to find comprehensive documentation of Bluesky's API thus far.

  11. Jul 2023
    1. we compiled all the species that we try and get a handle on and we then tried to 00:05:06 relate those species list to Manhattan Island through a new kind of science that we call muir webs and that kind of data it turns out that you can visualize and understand as a network
      • for: progress trap, species map, indra's net
    1. However, in many ofthese courses, the Web itself is treat-ed as a specific instantiation of moregeneral principals. In other cases, theWeb is treated primarily as a dynamiccontent mechanism that supports thesocial interactions among multiplebrowser users. Whether in CS studiesor in information-school courses, theWeb is often studied exclusively as thedelivery vehicle for content, technicalor social, rather than as an object ofstudy in its own right.

      I'd argue that this is a good thing. I think the tech industry's navelgazing does perhaps some of the worst harm wrt the problems articulated earlier.

  12. Jun 2023
    1. The soft power of Google Doc publishing

      See also:

      Google Docs is one of the best ways to make content to put on the Web.

      https://crussell.ichi.city/food/inauguration/

    1. Lost history ± the web is designed for society,but crucially it neglects one key area: its history.Information on the web is today's information.Yesterday's information is deleted or overwrit-ten

      It's my contention that this is a matter of people misusing the URL (and the Web, generally); Web pages should not be expected to "update" any more than you expect the pages of a book or magazine or a journal article to be self-updating.

      We have taken the original vision of the Web -- an elaborately cross-referenced information space whose references can be mechanically dereferenced -- and rather than treating the material as imbued with a more convenient digital access method and keeping in place the well-understood practices surrounding printed copies, we compromised the entire project by treating it as a sui generis medium. This was a huge mistake.

      This can be solved by re-centering our conception of what URLs really are: citations. The resources on the other sides of a list of citations should not change. To the extent that anything ever does appear to change, it happens in the form of new editions. When new editions come out, nobody goes around snapping up the old copies and replacing it for no charge with the most recent one while holding the older copies hostage for a price (or completely inaccessible no matter the price).

    1. A resource can map to the empty set, which allowsreferences to be made to a concept before any realization ofthat concept exist

      This is a very useful but underutilized property. It allows you to e.g. announce in advance that a resource will exist at some point in the future, and thereby effectively receive "updates" to the linking document without requiring changes to the document itself.

    2. how dowe ensure that its introduction does not adversely impact, oreven destroy, the architectural properties that have enabledthe Web to succeed?

      Another good jumping off point for why document mutability should be considered harmful. https://hypothes.is/a/N_gPAAmQEe6kvXNEm10s7w

    1. where theraw source could be directly modified and potentially read. Thiswas not widely implemented, and was subsequently removed. Thiseffectively limits WebDAV remote authoring to situations wherethere is a nearly direct correspondence

      I'll go further and say that, wrt the original goals of the Web—and the principles we should continue to strive for today, despite widespread practice otherwise—Modification (should be) Considered Harmful.

      Git has the right idea. Hypermedia collections should also be append-only (not different resources masquerading under the same name).

  13. May 2023
    1. If you doubt my claim that internet is broad but not deep, try this experiment. Pick any firm with a presence on the web. Measure the depth of the web at that point by simply counting the bytes in their web. Contrast this measurement with a back of the envelope estimate of the depth of information in the real firm. Include the information in their products, manuals, file cabinets, address books, notepads, databases, and in each employee's head.
    1. https://share-on-mastodon.social/

      A really neat customizable "Share on Mastodon" button for your pages or posts.

    1. https://ugmonk.com/

      Developed in a Kickstarter, ugmonk.com is where Jeff Sheldon now sells his Analog productivity system and refills as well as other related lifestyle brand products.

    1. Mastodon fans know that the network absolutely cannot compete on user friendliness and basic social functionality

      friendliness definitely needs to be explicitly defined here.

      Have you seen the goddamned art? lol

    2. Incidentally, when a straightforwardly “I’m a Nazi” Nazi showed up in the beta, people used the report function, and the Bluesky team labeled the account and banned it from the Bluesky app and restricted promotion of the account of the person who invited him. This changed exactly none of the tenor of the Nazi conversation on Mastodon, but it happened.

      Now just imagine the equivalent on the scale of an entire server and you've got the story of Mastodon's incredibly centralized, swift expulsion of Gab's influence. Here's The Verge's version for the moment.

    1. Circling back around to this after a mention by Tim Bushell at Dan Allosso's Book Club this morning. Nicole van der Hoeven has been using it for a while now and has several videos.

      Though called Napkin, which conjures the idea of (wastebook) notes scribbled on a napkin, is a card-based UI which has both manual and AI generated tags in a constellation-like UI. It allows creating "stacks" of notes which are savable and archivable in an outline-esque form (though the outline doesn't appear collapsible) as a means of composition.

      It's got a lot of web clipper tooling for saving and some dovetails for bringing in material from Readwise, but doesn't have great data export (JSON, CSV) at the moment. (Not great here means that one probably needs to do some reasonably heavy lifting to do the back and forth with other tools and may require programming skills.)

      At present, it looks like just another tool in the space but could be richer with better data dovetailing with other services.

    1. The Web does not yet meet its design goal as being a pool of knowledge that is as easy to update as to read. That level of immediacy of knowledge sharing waits for easy-to-use hypertext editors to be generally available on most platforms. Most information has in fact passed through publishers or system managers of one sort or another.

    1. The question I want everyone to leave with is which of these possible futures would you like to make happen? Or not make happen?
      1. Passing the reverse Turing test
      2. Higher standards, higher floors and ceilings
      3. Human centipede epistemology (ugh what an image)
      4. Meatspace premium
      5. Decentralised human authentication
      6. The filtered web

      Intuitively I think 1, 4, and 6 already de facto exist in the pre-generative AI web, and will get more important. Tech bros will go all in on 5, and I do see a role for it (e.g. to vouch that a certain agent acts on my behalf). I can see the floor raising of 2, and the ceiling raising too, but only if it is a temporary effect to a next 'stable' point (or it will be a race we'll loose), grow sideways not only up). Future 3 is def happening in essence, but it will make the web useless so there's a hard stop to this scenario, at high societal cost. Human K as such isn't dependent on the web or a single medium, and if it all turns to ashes, other pathways will come up (which may again be exposed to the same effect though)

    1. almost all beginners to RDF go through a sort of "identity crisis" phase, where they confuse people with their names, and documents with their titles. For example, it is common to see statements such as:- <http://example.org/> dc:creator "Bob" . However, Bob is just a literal string, so how can a literal string write a document?

      This could be trivially solved by extending the syntax to include some notation that has the semantics of a well-defined reference but the ergonomics of a quoted string. So if the notation used the sigil ~ (for example), then ~"Bob" could denote an implicitly defined entity that is, through some type-/class-specific mechanism associated with the string "Bob".

  14. Apr 2023
    1. they require the original server to provide a redirect and cannot migrate the user's previous data.

      This is... an extremely strange conclusion to come to regarding Social Web account migration, to say the least.

      Taking Mastodon as the handy example...

      The only reason to use the (extremely competent, bizarrely fast) process of redirection is that one... would like to have the "required" redirect on the original server. If a user intends to move to a different Mastodon instance and does not want to leave a redirect, that step is just... removed from the process.

    1. Responsive Image Gallery How to use CSS media queries to create a responsive image gallery that will look good on desktops, tablets and smart phones.
    1. These systems provide quite powerful tools for automaticreasoning, but encoding many kinds of knowledge using their rigid formal representations requiressignificant- -and often completely infeasible-amounts of effort.

    Tags

    Annotators

    1. There are a few obvious objections to this mechanism. The most serious objection is that duplicate information must be maintained consistently in two places. For example, if the conference organizers decide to change the abstracts deadline from 10 August to 15 August, they'll have to make that change both in the META element in the HEAD and in some human-readable area of the BODY.

      Microdata addresses this.

    1. And then, of course, browsers are themselves being likened to operating systems. Walled gardens, with no efficiency to speak of, with very little freedom, with too much leverage from the browser vendors. A perfect exploitation machine for keeping you within itself, all while it will do anything to harvest information about your activities, so it can show you some ads as soon as it can. An operating system alright. Yeah, just relax and no harm will come to you.
    1. Moreover, browsers are not the right way to be using web anyway. See my thought on this in the Data-Supplied Web article.
    2. he only advantage of building something in a web browser is that you can view websites right in them. If your task is not to display a webpage, or build a website, if CSS+HTML is not the limit of your imagination, then there's no reason to be building complex shit in the web browser! I can see hitching a web browser ride as a ubiquitous cross-platform graphical backend (over WebGL) if you are willing to deal with all the overhead and impact on speed. But with the libraries like SDL and Skia (which browsers use), that seems kind of pointless.
    1. something so ephemeral as a URL

      Well, they're not supposed to be ephemeral. They're supposed to be as durable as the title of whatever book you're talking about.

    1. Real Graph is a model which predicts the likelihood of engagement between two users. The higher the Real Graph score between you and the author of the Tweet, the more of their tweets we'll include.

      ...who thought this was a good idea??

    2. I realized after fully digesting this document that it effectively outlines a mechanism of anti-discovery.

  15. Mar 2023
    1. le regroupement des principaux acteurs du Web — et plus largement la concentration des producteurs des programmes (comme Google dont la moindre panne suffit à altérer une grande partie du fonctionnement des réseaux823) — fait courir le risque d’un Web à péages, où toute expérience serait anticipée et calculée

      Grand problème de la centralisation des programmes et des instances productrices de programmes: uniformisation des usages, comportements, et des programmes récursivement; dépendance à des structures tierces (aux intérêts commerciaux souvent conflictuels avec les besoins des usagers).

    1. Problem details for HTTP APIs HTTP status codes are sometimes not sufficient to convey enough information about an error to be helpful. The RFC 7807 defines simple JSON and XML document formats to inform the client about a problem in a HTTP API. It's a great start point for reporting errors in your API. It also defines the application/problem+json and application/problem+xml media types.
    1. ALIR - un manuel interactif pour l'algèbre linéaire produit avec PreTeXt  (présentation en français)  Lien vers la RELnorth_eastlien externe  fabriqueREL (2022-23)
    1. Streaming across worker threads

      ```js import { ReadableStream } from 'node:stream/web'; import { Worker } from 'node:worker_threads';

      const readable = new ReadableStream(getSomeSource());

      const worker = new Worker('/path/to/worker.js', { workerData: readable, transferList: [readable], }); ```

      ```js const { workerData: stream } = require('worker_threads');

      const reader = stream.getReader(); reader.read().then(console.log); ```

    1. The common perception of the Web as a sui generis medium is also harmful. Conceptually, the most applicable relevant standard for Web content are just the classic standards of written works, generally. But because it's embodied in a computer people end up applying the standards of have in mind for e.g. apps.

      You check out a book from the library. You read it and have a conversation about it. Your conversation partner later asks you to tell them the name of the book, so you do. Then they go to the library and try to check it out, but the book they find under that name has completely different content from what you read.

  16. Feb 2023
  17. tantek.com tantek.com
    Five years ago last Monday, the @W3C Social Web Working Group officially closed^1. Operating for less than four years, it standardized several foundations of the #fediverse & #IndieWeb: #Webmention #Micropub #ActivityStreams2 #ActivityPub Each of these has numerous interoperable implementations which are in active use by anywhere from thousands to millions of users. Two additional specifications also had several implementations as of the time of their publication as W3C Recommendations (which you can find from their Implementation Reports linked near the top of each spec). However today they’re both fairly invisible "plumbing" (as most specs should be) or they haven’t picked up widespread use like the others: #LinkedDataNotifications (LDN) #WebSub To be fair, LDN was only one building block in what eventually became SoLiD^2, the basis of Tim Berners–Lee’s startup Inrupt. However, in the post Elon-acquisition of Twitter and subsequent Twexodus, as Anil Dash noted^3, “nobody ran to the ’web3’ platforms”, and nobody ran to SoLiD either. The other spec, WebSub, was roughly interoperably implemented as PubSubHubbub before it was brought to the Social Web Working Group. Yet despite that implementation experience, a more rigorous specification that fixed a lot of bugs, and a test suite^4, WebSub’s adoption hasn’t really noticeably grown since. Existing implementations & services are still functioning though. My own blog supports WebSub notifications for example, for anyone that wants to receive/read my posts in real time. One of the biggest challenges the Social Web Working Group faced was with so many approaches being brought to the group, which approach should we choose? As one of the co-chairs of the group, with the other co-chairs, and our staff contacts over time, we realized that if we as chairs & facilitators tried to pick any one approach, we would almost certainly alienate and lose more than half of the working group who had already built or were actively interested in developing other approaches. We (as chairs) decided to do something which very few standards groups do, and for that matter, have ever done successfully. From 15+ different approaches, or projects, or efforts that were brought^5 to the working group, we narrowed them down to about 2.5 which I can summarize as: 1. #IndieWeb building blocks, many of which were already implemented, deployed, and showing rough interoperability across numerous independent websites 2. ActivityStreams based approaches, which also demonstrated implementability, interoperability, and real user value as part of the OStatus suite, implemented in StatusNet, Identica, etc. 2.5 "something with Linked Data (LD)" — expressed as a 0.5 because there wasn’t anything user-visible “social web” with LD working at the start of the Working Group, however there was a very passionate set of participants insisting that everything be done with RDF/LD, despite the fact that it was less of a proven social web approach than the other two. As chairs we figured out that if we were able to help facilitate the development of these 2.5 approaches in parallel, nearly everyone who was active in the Working Group would have something they would feel like they could direct their positive energy into, instead of spending time fighting or tearing down someone else’s approach. It was a very difficult social-technical balance to maintain, and we hit more than a few bumps along the way. However we also had many moments of alignment, where two (or all) of the various approaches found common problems, and either identical or at least compatible solutions. I saw many examples where the discoveries of one approach helped inform and improve another approach. Developing more than one approach in the same working group was not only possible, it actually worked. I also saw examples of different problems being solved by different approaches, and I found that aspect particularly fascinating and hopeful. Multiple approaches were able to choose & priortize different subsets of social web use-cases and problems to solve from the larger space of decentralized social web challenges. By doing so, different approaches often explored and mapped out different areas of the larger social web space. I’m still a bit amazed we were able to complete all of those Recommendations in less than four years, and everyone who participated in the working group should be proud of that accomplishment, beyond any one specification they may have worked on. With hindsight, we can see the positive practical benefits from allowing & facilitating multiple approaches to move forward. Today there is both a very healthy & growing set of folks who want simple personal sites to do with as they please (#IndieWeb), and we also have a growing network of Mastodon instances and other software & services that interoperate with them, like Bridgy Fed^6. Millions of users are posting & interacting with each other daily, without depending on any large central corporate site or service, whether on their own personal domain & site they fully control, or with an account on a trusted community server, using different software & services. Choosing to go from 15+ down to 2.5, but not down to 1 approach turned out to be the right answer, to both allow a wide variety^7 of decentralized social web efforts to grow, interoperate via bridges, and frankly, socially to provide something positive for everyone to contribute to, instead of wasting weeks, possibly months in heated debates about which one approach was the one true way. There’s lots more to be written about the history of the Social Web Working Group, which perhaps I will do some day. For now, if you’re curious for more, I strongly recommend diving into the group’s wiki https://www.w3.org/wiki/Socialwg and its subpages for more historical details. All the minutes of our meetings are there. All the research we conducted is there. If you’re interested in contributing to the specifications we developed, find the place where that work is being done, the people actively implementing those specs, and even better, actively using their own implementations^8. You can find the various IndieWeb building blocks living specifications here: * https://spec.indieweb.org/ And discussions thereof in the development chat channel: * https://chat.indieweb.org/dev If you’re not sure, pop by the indieweb-dev chat and ask anyway! The IndieWeb community has grown only larger and more diverse in approaches & implementations in the past five years, and we regularly have discussions about most of the specifications that were developed in the Social Web Working Group. This is day 33 of #100DaysOfIndieWeb #100Days ← Day 32: https://tantek.com/2023/047/t1/nineteen-years-microformats → 🔮 Post Glossary: ActivityPub https://www.w3.org/TR/activitypub/ ActivityStreams2 https://www.w3.org/TR/activitystreams-core/ https://www.w3.org/TR/activitystreams-vocabulary/ Linked Data Notifications https://www.w3.org/TR/ldn/ Micropub https://micropub.spec.indieweb.org/ Webmention https://webmention.net/draft/ WebSub https://www.w3.org/TR/websub/ References: ^1 https://www.w3.org/wiki/Socialwg ^2 https://www.w3.org/wiki/Socialwg/2015-03-18-minutes#solid ^3 https://mastodon.cloud/@anildash/109299991009836007 ^4 https://websub.rocks/ ^5 https://indieweb.org/Social_Web_Working_Group#History ^6 https://tantek.com/2023/008/t7/bridgy-indieweb-posse-backfeed ^7 https://indieweb.org/plurality ^8 https://indieweb.org/use_what_you_make - Tantek
    1
    1. debían estarprotagonizados por extranjeros y tratar de cosas con las que no podía identificarme. Puesbien, la situación cambió cuando descubrí los libros africanos.No había muchos disponibles, y no eran tan fáciles de encontrar como los extranjeros.Pero gracias a escritores como Chinua Achebe y Camara Laye, mi percepción de laliteratura cambió. Comprendí que en la literatura también podía existir gente como yo,chicas con la piel de color chocolate cuyo pelo rizado no caía en colas de caballo.Empecé a escribir sobre asuntos que reconocía.5

      texto pdf

    1. My Fifth Year as a Bootstrapped Founder

      My Fifth Year as a Bootstrapped Founder February 10, 2023 12-minute read annual review • tinypilot Five years ago, I quit my job as a developer at Google to create my own bootstrapped software company.

      For the first few years, all of my businesses flopped. None of them earned more than a few hundred dollars per month in revenue, and they all had negative profits.

      Halfway through my third year, I created a device called TinyPilot. It allows users to control their computers remotely without installing any software. The product quickly caught on, and it’s been my main focus ever since.

      In 2022, TinyPilot generated $812k in revenue, a 76% increase from 2021.

      In this post, I’ll share what I’ve learned about being a bootstrapped founder from my fifth year at it.

      Previous updates My First Year as a Solo Developer My Second Year as a Solo Developer My Third Year as a Solo Developer My Fourth Year as a Bootstrapped Founder Highlights from the year TinyPilot grew annual revenue to $812k Income/Expense 2021 2022 Change Sales $459,529 $807,459 +$347,930 (+76%) Credit card rewards $2,241 $4,327 +$2,086 (+93%) Raw materials -$224,046 -$333,656 +$109,610 (+49%) Payroll -$142,744 -$206,187 +$63,443 (+44%) Electrical engineering consulting -$28,662 -$124,643 +$95,981 (+335%) Advertising -$3,873 -$51,764 +$47,891 (+1,237%) Web design / branding -$15,931 -$30,215 +$14,284 (+90%) Postage -$24,227 -$30,779 +$6,552 (+27%) Cloud services -$5,553 -$7,865 +$2,312 (+42%) Office space -$4,400 -$6,600 +$2,200 (+50%) Equipment -$2,083 -$5,915 +$3,832 (+184%) Everything else -$4,902 -$8,183 +$3,281 (+67%) Net profit $5,349 $5,979 +$630 (+12%) While it sounds impressive to grow revenue by $350k, it’s a little less exciting that I’m only walking away with $6k in profit. I don’t pay myself a salary, so $6k is the full amount I earned from the business in 2022. Still, I’m excited about these numbers and what they mean for 2023.

      One of the major cost increases was electrical engineering. Throughout 2021, TinyPilot’s electrical engineering vendor was struggling to keep up with TinyPilot’s growth. In late 2021, I switched to a new vendor that fits our needs better, but they cost three times as much.

      The ongoing chip shortage forced us into frequent redesigns, which bloated costs in engineering hours and raw materials. We were often in a race to redesign a circuit board before we ran out of our existing version, so we repeatedly paid a premium to expedite the process.

      We finally escaped the redesign treadmill in September. I’m hopeful that our fourth quarter results will reflect the coming year. Our profit was $28.6k for the quarter, so if we average $9.5k per month in 2023, I’ll be happy.

      TinyPilot got a new website When I launched TinyPilot in 2020, I told myself the website and logo were just placeholders. Then, things took off so quickly that I never had time to replace them.

      In 2022, I finally hired a design agency to create a new logo and redesign the website.

      Screenshot of old landing page Screenshot of new landing page Before and after the TinyPilot website redesign

      I wrote previously about how frustrating and expensive it was working with the design agency, but I’m pleased with the result. My old website looked like a hobby project, and the new design looks like a real company. I suspect that at least a portion of my increased sales resulted from the new design.

      The TinyPilot team grew from six people to seven At the end of 2021, the TinyPilot team was:

      Me, the sole founder Three part-time software developers Two part-time local staff who handle assembling devices and fulfilling orders One of whom also handled customer service By the end of 2022, we had added two support engineers and adjusted responsibilities, so the team is now:

      Me, the sole founder Two part-time software developers Two part-time local staff who handle assembling devices and fulfilling orders Both now work on customer service Two part-time support engineers Adding the support engineers felt like finding the missing piece of the puzzle. Before they joined, I was the only person handling technical support, and it occupied about 20% of my time. Now, I spend less than 5% of my time on support requests, and customers receive faster support.

      The support engineers also do things I didn’t have time for, like investigating complex bugs, writing documentation, and improving our diagnostic tools.

      Growing the team stretched my skills as a manager. In 2021, TinyPilot’s workflows were fairly simple. Almost everyone did their work as a single-person unit. The results either went directly to me or to a customer. When employees needed to coordinate with each other, it was always among teammates of the same role.

      Integrating support engineers meant figuring out how different teams work together. How do support requests work when they require cooperation between fulfillment staff and support engineers? What’s the feedback loop between the support engineers and the dev team?

      PicoShare became my fastest-growing project One of my pet peeves in the last few years is how difficult it is to share a single file with cloud storage providers like Google Drive or Dropbox. They won’t give you a direct link to your file — just a link to their web interface, where they pressure your recipient to sign up for an account. If you upload a video to Google Drive, they make you wait 15+ minutes while they re-encode it, even if it was already optimized to play in the browser.

      As an alternative to the existing cloud storage options, I made a minimalist file-sharing app called PicoShare. You just upload a file, and it gives you a direct link that you can share. Easy! No re-encoding, no prompts to sign up for anything.

      Animated demo of uploading a video file to PicoShare and streaming it in another browser window Demo of PicoShare There are a few open-source tools that offer similar functionality, but PicoShare is unique in not requiring a database server. That means you can run it in a single Docker container, whereas other solutions require more complicated orchestration.

      PicoShare became the fastest-growing open-source project I ever published. It received 600 Github stars within two weeks of its release. As of this writing, PicoShare has over 100k installs.

      Lessons learned Don’t become anyone’s smallest client I made many mistakes throughout the whole TinyPilot website redesign fiasco, but the core problem was that the design agency was a fundamental mismatch for TinyPilot.

      The agency’s other clients had 5-20x TinyPilot’s budget. At first, I thought that was such a gift — this fancy agency with expensive clients was betting on a little company like mine.

      The reality was that TinyPilot was the agency’s lowest priority. They managed the project poorly, which drove up costs, bloated scope, and stretched out timelines.

      Now, when I work with new vendors, I ask them how my company compares to their other clients. If I’m an outlier in any important dimension like size, revenue, or industry, I look elsewhere.

      Run at 50% capacity Wouldn’t it be wonderful if your business’ capacity perfectly matched your customers’ needs? Your employees would fulfill every order and satisfy every support request while working exactly 40 hours per week. They’d never feel overworked nor underworked, and there’d be no idle time.

      In practice, that would be a terrible system. Running at 100% utilization would mean you have no margin for error. Ordinary occurences like a bump in sales or an employee taking a vacation would immediately overwhelm you.

      I aim for everyone at TinyPilot to run at around 50% capacity. That is, a balance of 50% reactive work and 50% proactive work. For some roles, the balance isn’t quite 50/50, but it’s a good rule of thumb.

      The technical support team is the clearest example of a 50/50 split: they spend half of their time responding to support requests and the other half finding ways to save users from needing support. The proactive tasks include fixing bugs in the product, writing documentation, and improving our diagnostic tools.

      Every TinyPilot team comprises two people. When one person is unavailable, the other can suspend their proactive work and handle time-sensitive tasks without feeling overwhelmed. If we get a rush of orders because a popular YouTube channel mentions us, we have spare capacity to absorb it.

      Team Reactive tasks Proactive tasks Founder Team management Vendor management Reviewing work Filling gaps in responsibilities Marketing Sales Re-evaluating strategy Hiring and training Support engineers Answering technical support questions Writing documentation Writing tutorials Investigating difficult bugs Software developers Fixing urgent bugs Releasing new features Improving dev experience Creating automated tests Fixing non-urgent bugs Fulfillment staff Assembling devices Fulfilling orders Customer service Creating support playbooks Assisting in marketing Ansible and git are not software distribution tools When I started working on TinyPilot, I didn’t know how to distribute Linux software.

      To publish the prototype of TinyPilot, I used the tools I knew: bash scripts, Ansible, and git. The bash script bootstrapped an Ansible environment and executed an Ansible playbook. Ansible installed dependencies, made necessary changes to the operating system, and cloned the TinyPilot git repository.

      The installation process was okay, not great. It was slow but reliable and didn’t require the user to configure anything manually.

      Two years later, TinyPilot’s update process was a mess. It still relied on the same shaky foundations from the prototype, except now there was a complex web of interdependencies. Ansible roles depended on Git repositories, which depended on other Ansible roles, which depended on parameters in a bunch of YAML files. Minor changes swallowed weeks of development time.

      All this because I never bothered to learn standard Linux packaging tools.

      This year, the TinyPilot team learned to use Debian packages. It was far less painful than I’d feared. I thought we’d have to deploy all sorts of package servers and key servers, but it turns out we didn’t need any of that. The process was relatively easy once we found the right guides.

      Debian packages have accelerated our development. The tooling catches expensive mistakes earlier, and we can deploy pre-release versions to our test devices easily, whereas our previous installation system made that process prohibitively complex.

      Grading last year’s goals Last year, I set three high-level goals that I wanted to achieve during the year. Here’s how I did against those goals:

      Grow TinyPilot to $1M in annual revenue Result: Grew TinyPilot’s revenue by 76% to $812k Grade: B I always knew that $1M was an aggressive goal. We fell short, but I’m still impressed at how close we came.

      Manage TinyPilot on 20 hours per week Result: I spent more time managing TinyPilot in 2022 than in 2021. Grade: D I was hoping to automate and delegate away enough of my job to reduce my management time to 20 hours per week, but it didn’t happen. Between growing sales, spinning up the support engineering team, and putting out fires due to the chip shortage, my management time increased.

      Ship TinyPilot Voyager 3 Result: We never even completed the design phase Grade: F TinyPilot has always used the Raspberry Pi 4B as the core hardware. There’s a wonderful ecosystem around the Pi 4B, but the hardware is relatively expensive and difficult to integrate with custom chips.

      My plan for 2022 was to create a custom circuit board for the slimmer, less expensive Raspberry Pi Compute Module 4. That could cut our manufacturing costs by up to 60% and simplify our hardware design.

      Instead, all of our hardware engineering time went to chasing down manufacturing issues and supply shortages, so we made no progress on a new product.

      Goals for year six Manage TinyPilot on 20 hours per week I failed miserably at reducing my hours last year, but it’s now my top priority. I’m hopeful about my chances this year. A lot of my 2022 work laid the groundwork to remove me from the critical path in 2023.

      Earn $100k in profit For TinyPilot’s first two and a half years, I focused on growth. I pay the same in hardware and software engineering costs whether I’m selling 20 devices per month or 2,000, so I needed to reach a certain scale to make the business viable.

      For most of 2023, TinyPilot’s production will be constrained by supply. It was disappointing to find out I’d have no chance at growing sales, but the silver lining is that I can slow down and focus on profit rather than growth.

      TinyPilot has always roughly broken even, but I think I can reach $100k in profit this year if I avoid further hardware redesigns. Without the hardware redesigns in 2022, I would have saved around $100k on engineering and $20k on materials. If I keep sales steady and run leaner on the hardware side, 2023 should be a profitable year.

      Close the TinyPilot office I’ve leased an office for TinyPilot since early 2021. We use it for assembling devices, fulfilling orders, and storing inventory.

      Having our own local office has helped us adapt quickly to changes in our hardware and processes, but it’s a lot of extra overhead. This year, I hope to transition assembly to China, where all of our parts originate. I’m also in the process of moving our fulfillment to a third-party logistics warehouse.

      Eliminating the TinyPilot office would spare us the work of maintaining a physical space, managing inventory, and tracking in-person shifts. Outsourcing manufacturing and fulfillment will also give the team more flexibility in time and location.

      Do I still love it? Every year, when I write these blog posts, I ask myself whether I still love what I’m doing.

      2022 was a hard year — certainly my hardest since going off on my own. I wasn’t miserable, but I can’t say I loved it.

      The global chip shortage meant we could never manufacture a batch of products the same way twice. There was always some missing component or manufacturing issue, so we were constantly racing to fix issues and adapt our processes before we ran out of stock. We got through it, and there were only a handful of days that I had to mark any product as sold out, but it was stressful.

      That said, there were certainly many things to appreciate about the year. I had a relatively small amount of time for writing and software development, but I’m proud of what I produced. Expanding the TinyPilot organization and figuring out how teams work together grew my skills as a manager. It’s been gratifying to see the team grow in their roles and expand their skills as the company evolves.

      I still prefer working for myself to having an employer. I still feel grateful for the freedom to have my own company. And I still want to do it forever.

  18. Jan 2023
    1. Mailgun is primarily a developer’s tool so the best way use Mailgun is through our APIs.

      developers first API first

    1. the most significant Web 2.0 creation to harness a massaudience and engage a mass audience in knowledge production and dissemination isWikipedia

      Wikipedia really is an excellent example of why and how Web 2.0 was so impactful to online society. Unlike Web 1.0, where content consumers were mostly limited to read-only, Web 2.0 allowed content consumers to produce their own consumable content for the first time.

    1. Example 2 HTTP/1.1 200 OK Content-Type: application/ld+json; profile="http://www.w3.org/ns/anno.jsonld" Link: <http://www.w3.org/ns/ldp#Resource>; rel="type" ETag: "_87e52ce126126" Allow: PUT,GET,OPTIONS,HEAD,DELETE,PATCH Vary: Accept Content-Length: 287 { "@context": "http://www.w3.org/ns/anno.jsonld", "id": "http://example.org/annotations/anno1", "type": "Annotation", "created": "2015-01-31T12:03:45Z", "body": { "type": "TextualBody", "value": "I like this page!" }, "target": "http://www.example.com/index.html" }
  19. Dec 2022
    1. Tom MacWright, a software developer in Brooklyn, has firsthand experience with the pitfalls of ActivityPub. As an experiment, he tried to turn his photo blog into an actor that could be followed by users via their Mastodon accounts. It worked in the end—and you can search for @photos@macwright.com from your Mastodon instance to follow his photography—but it wasn't easy.

      Example of how ActivityPub standards don't work in practice, in part because Mastodon is an 800 pound gorilla which actively flauts or adds their own "standards".

    2. "Queer people built the Fediverse," she said, adding that four of the five authors of the ActivityPub standard identify as queer. As a result, protections against undesired interaction are built into ActivityPub and the various front ends. Systems for blocking entire instances with a culture of trolling can save users the exhausting process of blocking one troll at a time. If a post includes a “summary” field, Mastodon uses that summary as a content warning.
    1. Spend some time with Arc, the new browser from The Browser Company of New York.

      https://arc.net/

      First I've heard of this.

    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
  20. Nov 2022