💾 Archived View for gemlog.blue › users › Sardonyx › 1604709835.gmi captured on 2024-08-18 at 21:15:19. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Awhile ago I linked to a geminaut thinking about building a bridge to the web.
Link Round-Up: T-Files, Gemtext, Low Power Computing, Gem Site Ideas, Text Web
I love that idea. The following 2 links may help with that.
Readability algorithm only starts incrementing your readability score after the node contents hit 140 characters. After 140 characters, the score is increased with the logarithmic sqrt(textContentLength - 140) formula, so two paragraphs of ~150 characters is better than one paragraph of ~300 characters.
(WWW) How does Firefox's Reader View work?
rdrview was written by Ernesto A. Fernández, but it's mainly a transpilation done by hand of Mozilla's Readability.js; which was itself, in their own words, "heavily based on Arc90's readability.js".
(GitHub WWW) rdrview: Firefox Reader View as a command line tool
This blog post from an Erlang developer laments the features lost in the migration to a “simpler” workflow.
Any failure would in fact automatically crash and roll-back to the current version (in milliseconds) unless we marked a file on disk that greenlit the new version as being acceptable. It even had a small admin panel where you could do live upgrades across all versions for each device and see things change without interrupting a single data stream. This also got cancelled; Docker was being seen as simpler to deal with for the whole cloud part of things, and nowadays nobody can really deploy this live. Product requirements were changed to play with the adopted tech. Scheduled downtime more or less became a necessity in most cases, because you can't afford to blank out security coverage while you roll things out in critical systems.
(WWW) A Pipeline Made of Airbags
Dan Luu writes about hindsight, or after-action reports, or “postmortems”. Think of the TV show _Air Disasters_ but without any plane crashes; these are postmortems of processes. Victims are often just bits and bytes, or money.
In one case, someone told me that what I was telling them was obvious at pretty much the same time their company was having a global outage of a multi-billion dollar service, caused by the exact thing we were talking about. Just because something is obvious doesn't mean it's being done.
(Small Web) Dan Luu: Postmortem Lessons
In case you missed it in his post, he keeps a running list of post-mortems as a document hosted on Github. (That trend is surprising to me. Instead of having a blog post, with suggestions in the comments, then updating the blog post; people are keeping a document on Github and asking commenters to submit pull requests.)
I started a series of posts about what, in my opinion, has led to the downfall of Mac OS X. (Look in my post archives.) There are two more parts coming, I promise! The following link could maybe be a footnote or supporting argument in a future post. Mac developer Jeff Johnson lays out how difficult Apple has made it to run software that has not been blessed by Cupertino.
Some people claim that Mac users can "just right click" to run unsigned software. But what does that mean exactly?
(Small Web) Lapcat Software: Can't you just right click?
6 November 2020 by Sardonyx
File under: linkblog