<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>chromebook — LowEndSpirit</title>
        <link>https://lowendspirit.com/index.php?p=/</link>
        <pubDate>Sat, 06 Jun 2026 03:53:28 +0000</pubDate>
        <language>en</language>
            <description>chromebook — LowEndSpirit</description>
    <atom:link href="https://lowendspirit.com/index.php?p=/discussions/tagged/chromebook/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Manifest V2 was disabled on my Chromebook today! But I got it back temporarily!</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/9198/manifest-v2-was-disabled-on-my-chromebook-today-but-i-got-it-back-temporarily</link>
        <pubDate>Sat, 08 Mar 2025 01:41:55 +0000</pubDate>
        <category>Industry News</category>
        <dc:creator>Not_Oles</dc:creator>
        <guid isPermaLink="false">9198@/index.php?p=/discussions</guid>
        <description><![CDATA[<p><img src="https://lowendspirit.com/uploads/editor/ex/y4znzk619kng.png" alt="" title="" /></p>

<p><a rel="nofollow" href="https://developer.chrome.com/docs/extensions/mv2">Manifest V2</a> is a specification for Chrome browser extensions.</p>

<p>Chrome fans have known for a long time that <a rel="nofollow" href="https://blog.chromium.org/2024/05/manifest-v2-phase-out-begins.html">Manifest V2 was about to be replaced by Manifest V3,</a> and that V2's final day was approaching fast.</p>

<p>Four days ago, I learned on HN that <a rel="nofollow" href="https://news.ycombinator.com/item?id=43239774">V2's end had almost arrived.</a> And now, for my Chromebook, the beginning of the end for Manifest V2 actually happened today!</p>

<p>This afternoon I updated my Chromebook from Chrome OS version 133.0.6943.132 to Chrome OS version 133.0.6943.146. After rebooting, I saw the above screenshot.</p>

<p>For now, at least, it was easy to re-enable the V2 extensions I use all the time. All I had to do was click the Manage Extensions link shown in the above screenshot, go to the Manage Extensions page, and re-enable the extensions.</p>

<p>Apparently I didn't need it today, but, as <a rel="nofollow" href="https://github.com/uBlockOrigin/uBlock-issues/discussions/2977#discussioncomment-8134456">explained by Raymond Hill (gorhill, the author of uBlock Origin),</a> an alternative method to extend Manifest V2 to June 2025 is provided through <a rel="nofollow" href="https://chromeenterprise.google/policies/#ExtensionManifestV2Availability">this Chromium Enterprise policy.</a></p>

<p>The most common issue with the Manifest V2 to Manifest V3 transition probably is the disabling of uBlock<br />
Origin. But, for me, and for others also facing significant vision-related challenges, the end of Chrome's High Contrast Extension is a significant loss. I also will miss SwitchyOmega's ability to quickly enable my web proxy.</p>

<p>While reading the above linked HN discussion, I decided to try Brave browser on Android. For a while I have used Firefox Nightly as an alternative to Chrome. While there seems to be a lot of customization possible in Firefox's dark mode, the default seems to be lower contrast grey text, while Brave uses white text as the default in "night mode." Additionally, Brave's AI search page has two inputs, one to continue in context and the other for an unrelated aside. This double input approach seems handy to me. Firefox seems to want to keep the tab bar at the bottom, but Brave allows tab manipulation to be controlled in the top bar.</p>

<p>Another positive point for Brave is that the design of the Brave Lion logo somehow <a rel="nofollow" href="https://yetinode.com/">reminds me of a Yeti!</a> Having a Yeti or a Lion always standing guard, watching my back -- it makes me feel safe!</p>

<p>Besides trying Brave, another possibility for me is moving away from Chromebooks as my daily driver. Maybe I could do equally well running NetBSD or Alpine or Debian locally.</p>

<p>I hope this post is useful to others here who also have lost or might very soon lose Manifest V2.</p>
]]>
        </description>
    </item>
    <item>
        <title>Installing plan9port in my Chromebook's Linux Container</title>
        <link>https://lowendspirit.com/index.php?p=/discussion/8116/installing-plan9port-in-my-chromebooks-linux-container</link>
        <pubDate>Wed, 31 Jul 2024 06:26:05 +0000</pubDate>
        <category>General</category>
        <dc:creator>Not_Oles</dc:creator>
        <guid isPermaLink="false">8116@/index.php?p=/discussions</guid>
        <description><![CDATA[<p><a rel="nofollow" href="https://github.com/9fans/plan9port">plan9port</a> is a Unix/Linux user space implementation of <a rel="nofollow" href="https://en.wikipedia.org/wiki/Plan_9_from_Bell_Labs">Plan9 from Bell Labs,</a> The Plan 9 operating system was the successor to Unix at <a rel="nofollow" href="https://en.wikipedia.org/wiki/Bell_Labs">Bell Labs,</a> where Unix previously had been developed.</p>

<p>Today I had some fun installing plan9port on my Lenovo Duet 5 Chromebook. I like the Duet 5 because of its brilliant 13 inch OLED touchscreen. Also, the Duet 5 is small, light, and inexpensive compared to other OLED laptops. The Duet 5 will run Android apps. And built-in to Chrome OS is the ability to run Linux containers. Today's plan9port install was inside one of the containers.</p>

<p>Here is a list of the commands I ran to install plan9port on my Duet 5. If I were doing the install again, I probably would install the four additional, required <code>-dev</code> packages prior to running <code>/use/plan9/INSTALL</code>. Today, I re-ran <code>INSTALL</code> four times following successive failures caused by missing header files.</p>

<pre><code> 2042  cd /usr
 2048  sudo git clone https://github.com/9fans/plan9port plan9
 2050  cd plan9
 2052  sudo /usr/plan9/INSTALL
 2057  sudo apt-get install libx11-dev
 2068  sudo apt-get install libxt-dev
 2078  sudo apt-get install libfontconfig1-dev
 2090  sudo apt-get install libxext-dev
 * Add these to your profile environment.
        PLAN9=/usr/plan9 export PLAN9
        PATH=$PATH:$PLAN9/bin export PATH
</code></pre>

<p>Here are Plan 9's <code>rc</code> shell and the <code>sam</code> editor running after the successful install.</p>

<pre><code>chronos@penguin:~$ cat /etc/debian_version 
12.6
chronos@penguin:~$ which rc
/usr/plan9/bin/rc
chronos@penguin:~$ rc
% man sam
  [ . . . ]
% sam -d
 -. 
q
% 
</code></pre>

<p>Getting started with plan9port is easy. Please see the getting started tips on Github at <a rel="nofollow" href="https://github.com/9fans/plan9port/issues/97">Issue 97 in the plan9port repository.</a></p>

<p>Based on limited testing -- I fired it up once -- my Duet 5's plan9port graphical editor, <a rel="nofollow" href="https://en.wikipedia.org/wiki/Acme_(text_editor)">Acme,</a> seems to work too. For my use, I'm usually happy with the command line tools, but <a rel="nofollow" href="https://github.com/jinyangustc/acme-editor">here</a> is a good, brief introductory reference list for plan9port's Acme graphical editor.</p>
]]>
        </description>
    </item>
   </channel>
</rss>
