Language Selection

English French German Italian Portuguese Spanish

Why the founder of Apache is all-in on blockchain

Filed under
OSS

As Behlendorf tells the story, Apache came out of an environment when "we might have had a more beneficent view of technology companies. We still thought of them as leading the fight for individual empowerment."

At the same time, Behlendorf adds, "there was still a concern that, as the web grew, it would lose its character and its soul as this kind of funky domain, very flat space, supportive of freedoms of speech, freedoms of thought, freedoms of association that were completely novel to us at the time, but now we take for granted—or even we have found weaponized against us."

This led him to want Apache to address concerns that were both pragmatic in nature and more idealistic.

The pragmatic aspect stemmed from the fact that "iteratively improving upon the NCSA web server was just easier and certainly a lot cheaper than buying Netscape's commercial web server or thinking about IIS or any of the other commercial options at the time." Behlendorf also acknowledges, "it's nice to have other people out there who can review my code and [to] work together with."

There was also an "idealistic notion that tapped into that zeitgeist in the '90s," Behlendorf says. "This is a printing press. We can help people publish their own blogs, help people publish their own websites, and get as much content liberated as possible and digitized as possible. That was kind of the web movement. In particular, we felt it would be important to make sure that the printing presses remained in the hands of the people."

Read more

More in Tux Machines

today's howtos

This week in KDE: fixing up Plasma 5.20

Okular’s editable forms are no longer mis-rendered when inertially scrolling (Kezi Olio, Okular 1.11.2) When your scanner can almost but not quite fit a particular page size, Skanlite will now display the option to scan to that page size anyway (e.g. 215mm wide scan beds now give you the option to scan using the US Letter page size) (Kåre Särs, libksane 20.12) The text of Elisa’s keyboard shortcuts are now translated properly (Nikunj Goyal, Elisa 20.12) Clearing the clipboard history on Wayland no longer crashes Plasma (David Edmundson, Plasma 5.20) Improved the Plasma SVG cache heuristics such that various things which might sometimes be invisible after upgrading Plasma now show up like they’re supposed to (Arjen Hiemstra, Plasma 5.20) On Wayland, clicking on a Task Manager entry while that entry’s tooltip is visible no longer crashes Plasma (Vlad Zahorodnii, Plasma 5.20) On Wayland, clicking on a Task Manager thumbnail now activates that window, as you would expect (Marco Martin, Plasma 5.20) Read more Also: KDE Plasma 5.20 Should Be Crashing A Lot Less Under Wayland

Legacy: Dennis Ritchie's Lost Dissertation and FTP Fadeout

  • Discovering Computer Legend Dennis Ritchie's Lost Dissertation
  • FTP Fadeout

    Here’s a small piece of news you may have missed while you were trying to rebuild your entire life to fit inside your tiny apartment at the beginning of the COVID crisis: Because of the way that the virus shook up just about everything, Google skipped the release of Chrome version 82. Who cares, you think? Well, users of FTP, or the File Transfer Protocol. During the pandemic, Google delayed its plan to kill FTP, and now that things have settled to some degree, Google recently announced that it is going back for the kill with Chrome version 86, which deprecates the support once again, and will kill it for good in Chrome 88. (Mozilla announced similar plans for Firefox, citing security reasons and the age of the underlying code.) It is one of the oldest protocols the mainstream [Internet] supports—it turns 50 next year—but those mainstream applications are about to leave it behind. Today’s Tedium talks about history of FTP, the networking protocol that has held on longer than pretty much any other.

virt-manager 3.0.0 released!

Yesterday I released virt-manager 3.0.0. Despite the major version number bump, things shouldn't look too different from the previous release. For me the major version number bump reflects certain feature removals (like dropping virt-convert), and the large amount of internal code changes that were done, though there's a few long awaited features sprinkled in like virt-install --cloud-init support which I plan to write more about later. Read more Also: virt-install --cloud-init support