Imitar los artículos y documentos académicos

From the homepage:

Repla is a macOS app that can[...]

That's like the complete opposite of "just give me a document that I can double click to open from disk and view in my browser"...

A substantial subset of the personal homepage contingency associated with blogging advocacy "movement" doesn't understand this.

Understanding it now and fighting all its supporters is for sure more productive than simply being forced to deal with it later.

This is a nightmare, and it would possibly be capitalism's final victory.

Climate Fiction - Tallest story - JMo web article

• source/reference/inspiredfrom: https://www.economist.com/books-and-arts/2019/04/04/can-the-novel-handle-a-subject-as-cataclysmic-as-climate-change

ReconfigBehSci on Twitter: ‘RT @bhrenton: Preliminary look into the visitor locations to https://t.co/j5ei0O4u1e mapped with new COVID-19 cases shows some overlaps, bu…’ / Twitter. (n.d.). Retrieved 13 February 2022, from https://twitter.com/SciBeh/status/1483697294373531652

Semantic Web Tool: Hypothes.is

Internet bis Web 3.0 (semantic web)

Forschungsbereich: Corporate Semantic Web Ziel: Innovative Konzepte und Lösung für die Gewinnung, Verwaltung und Nutzung von Wissen auf Basis von semantischen Technologien im Unternehmenskontext

Unterschied zwischen Semantic Web und semantische Technologien

„Spatial Web“

Web 3.0

Leitidee von Linked Data

SPARQL = Abfragesprache von RDF

OWL = Instrument zur Modellierung der Wissensrepräsentationen

Ontologie = Zieldefiniton von Semantic Web

Titel: A knowledge representation practionary Autor: Michael K. Bergman

But maybe you don't need to do that. Maybe it would be instructive to take lessons from the traditional (pre-digital) publishing industry and consider how things like "print runs" and "reissues" factored in.

If you write a blog post in 2017 and the page is acceptable*, and then five years later you're publishing a new post today in 2022 under new design norms and trying to retrofit that design onto your content from 2017, then that sounds a lot like a reprint. If that makes sense and you want to go ahead and do that, then fair enough, but perhaps first consider whether it does make sense. Again, that's what you're doing—every time you go for a visual refresh, it's akin to doing a new run for your entire corpus. In the print industry (even the glossy ones where striking a chord visually was and is something considered to merit a lot of attention), publishers didn't run around snapping up old copies and replacing them with new ones. "The Web is different", you might say, but is it? Perhaps the friction experienced here—involved with the purported need to pick up a static site generator and set your content consistently with templates—is actually the result of fighting against the natural state of even the digital medium?

* ... and if you wrote a blog post in 2017 and the page is not acceptable now in 2022, maybe it's worth considering whether it was ever really acceptable—and whether the design decisions you're making in 2022 will prove to be similarly unacceptable in time (and whether you should just figure out the thing where that wouldn't be the case, and instead start doing that immediately).

This is a common enough feeling (not about Publii, specifically; just the general concern for flexibility and control in static site generators), but when you pull back and think in terms of normalcy and import, it's another example of how most of what you read on the internet is written by insane people.

Almost no one submitting a paper for an assignment or to a conference cares about styling the way that the users of static site generators (or other web content publishing pipelines) do. Almost no one sending an email worries about that sort of thing, either. (The people sending emails who do care a lot about it are usually doing email campaigns, and not normal people carrying out normal correspondence.) No one publishing a comment in the thread here—or a comment or post to Reddit—cares about these things like this, nor does anyone care as much when they're posting on Facebook.

Somehow, though, when it comes to personal Web sites, including blogs, it's MySpace all over again. Visual accoutrement gets pushed to the foreground, with emphasis on the form of expression itself, often with little relative care for the actual content (e.g. whether they're actually expressing anything interesting, or whether they're being held back from expressing something worthwhile by these meta-concerns that wouldn't even register if happening over a different medium).

When it comes to the Web, most instances of concern for the visual aesthetic of one's own work are distractions. It might even be prudent to consider those concerns to be a trap.

semantic web will fail because businesses are not working together

on top stacked laying flat on the left side, next to a potted plant on the right two other books to the right of the plant, spines not visible

tools for thought rheingold MIT Press logo concept design: the essence of software jackson designing constructionist futures nathan holbert, matthew berland, and yasmin b. kafai, editors MIT Press logo structure and interpretation of computer programs second edition abelson and sussman MIT Press Indroduction to the theory of computation

top shelf ordinary orientation: books upright, spines facing out tops leaning to the left

toward a theory of instruction bruner belknap / harvard tools for conviviality ivan illich harper & row the human interface raskin addison wesley the design of everyday things don norman basic books changing minds disessa MIT Press logo mindstorms seymour papert unknown logo understanding computers and cognition winograd and flores addison wesley software abstraction jackson revised edition MIT Press logo living with complexity norman MIT Press logo the art of doing science and engineering—learning to learn richard w. hamming stripe press logo the computer boys take over ensmenger recoding gender abbate MIT Press logo weaving the web tim berners-lee harper dealers of lightning: xerox parc and the dawn of the computer age michael a hiltik harper the dream machine m. mitchell waldrop stripe press logo from counterculture to cyberculture fred turner chicago the innovators walter isaacson simon & schuster paperbacks a people's history of computing in the united states joy lisi rankin harvard the media lab stewart brand penguin logo

bottom shelf ordinary orientation: books upright, spines facing out tops leaning to the right

about face: the essentials of interaction design cooper, reimann, cronin, noessel 4th edition wiley the new media reader wardrip, fruin, and montfort, editors designing interactions bill moggridge includes DVD MIT Press logo interactive programming environments barstow, shrobe, sanderwall mcgraw hill visual programming shu software visualization editors: stasko, domingue, brown, price MIT Press logo types and programming languages pierce MIT Press logo smalltalk-80: the interactive programming environment goldberg addison wesley constructing the user... statecharts qa 76.9 .u83 h66 1999 the human use of human beings: cybernetics and society wiener da capo pasteur's quadrant stokes brookings scientific freedom: the elixir of civilization donald w. braben stripe press logo a pattern language alexander, ishikawa, silverstein, jacobson, fiksdahl-king, angel oxford the timeless way of building alexander oxford

Not accessible.

https://www.codica.com/blog/how-much-does-it-cost-to-build-website/

https://www.codica.com/blog/how-much-does-it-cost-to-build-website/

Yeah, but...

Keeping your website's look 'up to date' requires changes, but keeping your website up does not require "keeping its look 'up to date'".

The problem almost certainly starts with the conception of what we're doing as "building websites".

When we do so, we mindset of working on systems

If your systems work compromises the artifacts then it's not good work

This is part of a broader phenomenon, which is that when computers are involved with absolutely anything people seem to lose their minds good sensibilities just go out the window

low expectations from everyone everyone is so used to excusing bad work

sui generis medium

violates the principle of least power

what we should be doing when grappling with the online publishing problem—which is what this is; that's all it is—is, instead of thinking in terms of working on systems, thinking about this stuff in such a way that we never lose sight of the basics; the thing that we aspire to do when we want to put together a website is to deal in

documents and their issuing authority

That is, a piece of content and its name (the name is a qualified name that we recognize as valid only when the publisher has the relevant authority for that name, determined by its prefix; URLs)

that's it that's all a Web site is

anything else is auxiliary

really not a lot different from what goes on when you publish a book take a manuscript through final revisions for publication and then get an ISBN issued for it

so the problem comes from the industry

people "building websites" like politicians doing bad work and then their constituents not holding them accountable because that's not how politics works you don't get held accountable for doing bad work

so the thing to do is to recognize that if we're thinking about "websites" from any other position things that technical people try to steer us in the direction of like selecting a particular system and then propping it up and how to interact with a given system to convince it to do the thing we want it to do— then we're doing it wrong

we're creating content and then giving it a name

See also: Web page that parses and explains the label on a bike tire

HN comments: https://news.ycombinator.com/item?id=30137984

Good stuff about big modular javascript program, Home Assistant.

A note on setting worker-loader’s publicPath with webpack 5

Webpack 5 introduced a mechanism to detect the publicPath that should be used automatically

[...]

Webpack 5 exposes a global variable called __webpack_public_path__ that allows you to do that.

// Updates the `publicPath` at runtime, overriding whatever was set in the
// webpack's `output` section.
__webpack_public_path__ = "/workers/";

const myWorker = new Worker(
  new URL("/workers/worker.js");
);

// Eventually, restore the `publicPath` to whatever was set in output.
__webpack_public_path__ = "https://my-static-cdn/";

https://www.codica.com/blog/latest-ui-ux-design-trends/

https://github.com/joshbuchea/HEAD

Web 4.0 : The Internet of Things en AI Web 4.0 article Web_4.0 comes after Web 3.0, Web 2.0 and Web 1.0. What does it mean and what can we expect from it? The new web 4.0 has the following internet features....

https://blog.jim-nielsen.com/2022/a-web-for-all/

• 20 years waiting from Semantic Web promises!!!
• Conclusions:
• • competition vs cooperation (reinventing the wheel again and again)
• • minority interested in knowledge vs majority targeted to consume

• GREAT IDEA: VIDEOS (VISUAL+AUDIO) ++ TRANSCRIPTION (FULL TEXT), permits searches!!!

• REINVENT THE WHEEL!
• SADLY, DO IT YOURSELF IS OFTEN THE ONLY ALTERNATIVE!

• OK: tools for register, but NEED "THE TOOL" for searching and RECOVER these data!

One's lifetime of notes could be thought of as a hypertext work in progress that is designed to be open-ended.

https://maya.land/responses/2021/09/17/altweb-indieweb-squabble.html

This week on soap operas in the small web....

• SEE [citation needed]
• EXPLORE
• ok! "these painstaking efforts to encode knowledge"

• not designed for Semantic Web!!!

• "parallel" web???
• bots??? explore and pass

• Semantic Web: an utopia???
• I have been waiting for it for 20 years, and counting...
• Instead "plain text": "triplets"; properties and wikidata-Qs

Web Workers

As of webpack 5, you can use Web Workers without worker-loader.

Syntax

new Worker(new URL('./worker.js', import.meta.url));

// main.js
const { RemoteReadableStream, RemoteWritableStream } = RemoteWebStreams;
(async () => {
  const worker = new Worker('./worker.js');
  // create a stream to send the input to the worker
  const { writable, readablePort } = new RemoteWritableStream();
  // create a stream to receive the output from the worker
  const { readable, writablePort } = new RemoteReadableStream();
  // transfer the other ends to the worker
  worker.postMessage({ readablePort, writablePort }, [readablePort, writablePort]);

  const response = await fetch('./some-data.txt');
  await response.body
    // send the downloaded data to the worker
    // and receive the results back
    .pipeThrough({ readable, writable })
    // show the results as they come in
    .pipeTo(new WritableStream({
      write(chunk) {
        const results = document.getElementById('results');
        results.appendChild(document.createTextNode(chunk)); // tadaa!
      }
    }));
})();

// worker.js
const { fromReadablePort, fromWritablePort } = RemoteWebStreams;
self.onmessage = async (event) => {
  // create the input and output streams from the transferred ports
  const { readablePort, writablePort } = event.data;
  const readable = fromReadablePort(readablePort);
  const writable = fromWritablePort(writablePort);

  // process data
  await readable
    .pipeThrough(new TransformStream({
      transform(chunk, controller) {
        controller.enqueue(process(chunk)); // do the actual work
      }
    }))
    .pipeTo(writable); // send the results back to main thread
};

WARC Format

The WARC format is the raw data from the crawl, providing a direct mapping to the crawl process. Not only does the format store the HTTP response from the websites it contacts (WARC-Type: response), it also stores information about how that information was requested (WARC-Type: request) and metadata on the crawl process itself (WARC-Type: metadata).

For the HTTP responses themselves, the raw response is stored. This not only includes the response itself, what you would get if you downloaded the file, but also the HTTP header information, which can be used to glean a number of interesting insights.

In the example below, we can see the crawler contacted http://102jamzorlando.cbslocal.com/tag/nba/page/2/ and received a HTML page in response. We can also see the page was served from the nginx web server and that a special header has been added, X-hacker, purely for the purposes of advertising to a very specific audience of programmers who might look at the HTTP headers!

WARC/1.0
WARC-Type: response
WARC-Date: 2013-12-04T16:47:32Z
WARC-Record-ID: 
Content-Length: 73873
Content-Type: application/http; msgtype=response
WARC-Warcinfo-ID: 
WARC-Concurrent-To: 
WARC-IP-Address: 23.0.160.82
WARC-Target-URI: http://102jamzorlando.cbslocal.com/tag/nba/page/2/
WARC-Payload-Digest: sha1:FXV2BZKHT6SQ4RZWNMIMP7KMFUNZMZFB
WARC-Block-Digest: sha1:GMYFZYSACNBEGHVP3YFQNOSTV5LPXNAU

HTTP/1.0 200 OK
Server: nginx
Content-Type: text/html; charset=UTF-8
Vary: Accept-Encoding
Vary: Cookie
X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.
Content-Encoding: gzip
Date: Wed, 04 Dec 2013 16:47:32 GMT
Content-Length: 18953
Connection: close


...HTML Content...

https://iconmap.io/

An awesome map of 400,000+ favicons.

Desired workflow:

1. I navigate to the APL login page https://austin.bibliocommons.com/user/login
2. I invoke a bookmarklet on the login page that opens a new browser window/tab
3. In the second tab, I navigate here—to a locally saved copy of (a facsimile of) my library card
4. I invoke a bookmarklet on my library card to send the relevant details to the APL login page using window.postMessage
5. The bookmarklet set up in step 2 receives the details, fills in the login form, and automatically "garbage collects" the second tab

Some other thoughts: We can maintain a personal watchlist/readlist similarly. This document (patron ID "page") itself is probably not a good place for this. It is, however, a good place to reproduce a convenient copy of the necessary bookmarklets. (With this design, only one browser-managed bookmarklet would be necessary; with both bookmarklets being part of the document contents, the second bookmarklet used for step 4 can just be invoked directly from the page itself—no need to follow through on actually bookmarking it.)

https://write.as/matt/what-would-a-real-web3-look-like

This roughly reflects my own thoughts about the "next web".

An absolutely beautiful design for short notes.

This is the sort of theme that will appeal to zettelkasten users who are building digital gardens. A bit of the old mixed in with the new.

<small><cite class='h-cite via'>ᔥ <span class='p-author h-card'>Pete Moor </span> in // pimoore.ca (<time class='dt-published'>12/24/2021 18:02:15</time>)</cite></small>

https://pimoore.ca/2021/12/22/aegirs-site-is.html

scalable web app

Social security numbers, often thought of as important personally identifying keys, are relatively inexpensive according to this website.

What the actual fuck are y’all doing on your phones that this is such a consideration for you? Like… Is the web just for porn for you or something???

This is the first time I've seen a paper refer to the client side rendering of pages as a factor

https://dev.to/chrisaldrich

In 2020, the split is about %16 mobile vs 84% fixed access.

You might not use these for the web tho, as so much computer to computer transfer is only fixed to fixed

Over the same period solar has come down in price at around 20% per year

For the last twenty years we have had almost 10x differences in expected energy use figures

If your site has multiple URLs for the same content, share the page's canonical URL instead of the current URL. Instead of sharing document.location.href, you would check for a canonical URL <meta> tag in the page's <head> and share that. This will provide a better experience to the user. Not only does it avoid redirects, but it also ensures that a shared URL serves the correct user experience for a particular client. For example, if a friend shares a mobile URL and you look at it on a desktop computer, you should see a desktop version:

let url = document.location.href;
const canonicalElement = document.querySelector('link[rel=canonical]');
if (canonicalElement !== null) {
    url = canonicalElement.href;
}
navigator.share({url});

None of this is really relevant. Of all the apps listed, none are especially relevant to the Web. They'd best be classified as internet apps. Granted, they might be dealing in HTTP(S) at some point as a bodge, but then again, almost everything else does, too, whether it's part of the Web or not.

(re @eric_young_1 https://twitter.com/eric_young_1/status/1470524708730851328—not sure how well the twitter.com client and Hypothesis interact)

The dream is still alive among semweb people (incl. Tim Berners-Lee himself).

The sad state of current norms re webapps created by professional devs leads to what probably seems like a paradox but isn't, which is that the alternate future outlined in this tweet is closer to the ideal of the Web than the "Modern Web".

The subtext here is, "that's why i created BeachfrontDigital". But this shows how "apps" (and systems) have poisoned how we conceptualize problems and their solutions.

The simplest solution to the problem described is a document, not a never-finished/never-production-ready app. Bespoke apps have lots of cost overhead. Documents, on the other hand—even documents with rich structure—are cheap.

Must publicly disclose

Holy balls - anyone sellling to SFDC agree to a month month kill clause if they're caught doing stuff that would have a material impact on SFDC's reputation?

Ahhh! So this, if you squint, is a bit like the "publish the license" aspect of OSS licenses like MIT, Apache 2 and the rest.

This sustainability score card:

corporate social responsibility assessment report prepared by a reputable provider

Ah, so this is the cascading mechanism in effect here. This is what we tried back in 2011 with AMEE, but we didn't think about using contract law as a lever in this way - ours all about implicit pressure from the big supplier we were working with

LOL, this is basically what we asked for when they got in touch with us. If the language here is in the TCLP clauses, then it might be worth adopting in our T's and C's too

Wow, so this shifts the carbon neutralitry burden to the supplier, so SFDC can reasonably expect their scope 3 emissions from this supplier to be zero?

Ahh… this is interesting - it's essentially compelling the supplier to make a statement that that they're not breaking any environmental laws

Note to follow up - these plans might not be public, but this implies that they might used as for inter-org comms

So a 100k project amounts to a 500 fee for non compliance

This is a new term for me, and I wonder if it's in the TCLP clauses or coming from SFDC

I've noted elsewhere that despite the reputation of WYSIWYG editors' tendencies for handling HTML, modern mainstream Web development practices are so bad today that just typing a bunch of junk into LibreOffice and saving as HTML results in one of the most economical ways to do painless authoring of Web content...

// To know the maximum numbers of thread that can be used
// on user’s system, use

window.navigator.hardwareConcurrency property.

author.fullName}. (n.d.). Fake covid-19 vaccine certificates are being sold on the dark web. New Scientist. Retrieved December 7, 2021, from https://institutions.newscientist.com/article/2299962-fake-covid-19-vaccine-certificates-are-being-sold-on-the-dark-web

Nice! These are the underlying sources of data for the image shared on twitter

According to the Startup Genome Report, over 90% of startups fail after launch. There can be different reasons like skipping the market research, hiring wrong specialists, too early scaling, and so on.

However, one of the most important elements of startup success is the product you provide. Neglecting estimates, avoiding the MVP stage, designing unnecessary functionality, and saving time on testing may become fatal errors that can result in a complete failure.

In this article, we will tell you about the most costly mistakes you should avoid during web app development to succeed after product launch.

Do you have a high-quality and almost irresistible application in your bag? Your potential customers will not enjoy your app to the full if they cannot access it easily and quickly. That is why you need to consider how to choose the right SaaS hosting provider carefully.

In this article, we will review different SaaS cloud hosting options and their strengths and weaknesses. Read on to find out how to make hosting for your SaaS application reliable, cost-effective, and scalable.

Did you know that payment solutions for online marketplaces can shape your e-commerce business and its success? Thus, Uber succeeded in its global expansion right after it switched to Braintree.

In early Uber’s scaling, even a dollar-euro currency conversion wasn’t available. Now, with Braintree, it processes mobile payments in 130 currencies in 80+ countries.

Of course, each marketplace faces its own payment challenges. So, you should rely on a payment solution with the features vital right for your e-commerce platform. To identify them, let’s dig deeper into two-sided marketplace payment processing, and analyze the best payment gateways for marketplaces.

The hype around Amazon and eBay has driven up the demand for marketplace development services. Business owners turn to software consultancies to launch a thriving e-commerce website. Here comes a question: what do they need to get the most successful online marketplace website?

We believe that a profitable e-commerce project starts with the right tech stack. The main qualities that a modern marketplace should possess are scalability, easy customizations, and flexibility. Therefore, it’s important to choose the technologies that will help these qualities.

Trying to consolidate [[SGML]]'s lack of key-value paid & arrays vs [[JSON]]'s lack of attributes and spanning extents.

Here it is an typicall article mocking everybody not respecting HTML semantics that i didn't even know existed - but it had a point!

[2020] Basics of Module Bundlers for web development

• Provides a number of uses, most commonly used to compile multiple .js files into a single file for browser to load when users visit a website
• Terms: Code Splitting, Loaders, Plugins, Dev Server
• Bundlers: Webpack, Rollup, Parcel, Snowpack
• Snowpack - only rebuilds files that have changed vs. rebuilding the entire project

This implies uniformity in how you report it. If you have an attributional approach for measuring impact at an organisational level, you'll need a way to convert between the two if you are using a consequential method for a project.

Web Browser Engineering by Pavel Panchekha & Chris Harrelson https://browser.engineering/

A Web Browser Built for Me by Robin Rendle https://www.robinrendle.com/notes/a-web-browser-built-for-me/

I love the phrase "a web that your read instead of one that tries so very hard to read you."

OK, so this suggests they're intending to eventually replace the extended environmental input output models that are the defaults in most carbon accounting tools with their own models.

My guess is this would be their moat in many cases.

Bristly pop cultural misuse of the term "algorithm" notwithstanding, a better solution that I haven't come across anyone else mention: make them explicit, not hidden.

When it look like Dat might've had enough steam to take off (ca. 2017–2018), I wrote a draft straw proposal for how to solve the "discovery problem" with e.g. Fritter—i.e. the problem that because you only "receive" replies and other messages by checking the feeds of the people you're following, you'll be unable to reply engage with strangers who appear (or have a stranger engage with you in their thread) unless something happens like a mutual acquaintance alerting you out of band ("hey, did you see @foo's reply dat://foo.example.net/posts/ukifxdgbh.json?").

The idea is that there is a special kind of feed operated by some service provider that specializes in doing exactly that. If you find Facebook valuable, for example, then you are free to opt in and subscribe to the Facebook analog that pays attention to all feeds and works to surface interesting content for you. Under this model, unlike the Facebook regime, "leaving" is as simple as unsubscribing to that feed (and going with a different provider if you want).

THIS is it - web 3 is making consumers mutiplicitous - opens marketts WITHIN games, subworlds that can be exploited / marketed to / fashion trends will sweep games, online subcultures (maybe) - people have markeable personas on and off the web, new context for targeted advertising / commerce.

Will cannabalize physical economies?

Accessorize for a zoom meeting - digital suits, etc digital costumes. Something to wear at digital concerts, in games; your Perona will not be birthed into the metaverse clothed, accessorized...

Assets will be portable across platforms.

There - opens up GIGANTIC barter economy possibilities - will shut out old middle men & create new ones - swap airline tickets / hotel reservations for concert tickets or memorabilia

Progressive web applications are considered one of the most important web development trends for 2021. PWAs are easy to launch and maintain, being a great alternative for native apps due to their cost-efficiency.

In this article, we will discuss the main points of choosing the software provider for building your progressive web app.