New post: Workaround for external keyboards to make special characters in KOReader
This commit is contained in:
parent
1a73474b6e
commit
ab1a8afcf2
GPG key ID:
21A3DA3DE29CB63C
15 changed files with 102 additions and 18 deletions
|
|
@ -29,7 +29,7 @@
|
|||
<p>You mean... onboarding hasn't been made easy for non-technical people? The same people all these grand overtures of "escaping from MEGACORP" are supposed to save? Or is this one of those "citadel" projects where all the benefit is for the early adopters safe inside and the masses are supposed to be locked outside to suffer whatever computing apocalypse will come?</p>
|
||||
<p>Urbit has a free version of an identity called a "comet", but apparently <a href="https://archive.ph/pOszH#selection-293.184-293.206">it can't download any apps or interact with much of the network</a>,<!-- https://urbit.org/getting-started/desktop -->
|
||||
which is confusingly later <a href="https://web.archive.org/web/20220805172516/https://urbit.org/getting-started/cli#boot-your-planet">contradicted in the CLI install instructions: "There are currently few differences between using a comet-level identity and a planet-level one."</a> To do anything of substance, you'll "need a to get a planet". Because I already had my Urbit passport from three years ago, the post doesn't end here, and I was able to continue my research without spending any money. Otherwise, judging from the <a href="https://web.archive.org/web/20220730150142/https://urbit.org/getting-started/get-planet">recommended planet resellers</a> that were functional, prices for a Layer 2 planet range from about $15 to $50, which isn't an "I am now destitute and living on the streets" amount of money... but still, that's a lot of groceries.</p>
|
||||
<p>The desktop GUI, according to the documentation, requires <code>snap</code> to be installed, but some digging reveals <a href="https://github.com/urbit/port/releases">there are also <code>.dpkg</code> packages and raw binaries</a>... which, par for the course of web3 bullshit, are written in Node.js. However, these seem to only be available for x86_64, unless you're using a Mac, in which case you also get <code>arm64</code>, or a Raspberry Pi, in which case you get shunted to a <a href="https://web.archive.org/web/20220730152509/https://github.com/OdysLam/home-urbit">a third-party solution</a>. You could also attempt to compile it yourself, but given the aforementioned Node.js dependency, you're more likely to see the sun explode tomorrow than <a href="../../2020/february/32bit.html">get the damn thing to compile properly</a>.</p>
|
||||
<p>The desktop GUI, according to the documentation, requires <code>snap</code> to be installed, but some digging reveals <a href="https://github.com/urbit/port/releases">there are also <code>.dpkg</code> packages and raw binaries</a>... which, par for the course of web3 bullshit, are written in Node.js. However, these seem to only be available for x86_64, unless you're using a Mac, in which case you also get <code>arm64</code>, or a Raspberry Pi, in which case you get shunted to <a href="https://web.archive.org/web/20220730152509/https://github.com/OdysLam/home-urbit">a third-party solution</a>. You could also attempt to compile it yourself, but given the aforementioned Node.js dependency, you're more likely to see the sun explode tomorrow than <a href="../../2020/february/32bit.html">get the damn thing to compile properly</a>.</p>
|
||||
<p>Because I wasn't sure how much bandwidth Urbit would use, even though I have a Wi-Fi repeater in my bedroom now and thus an actually decent connection, I instead opted for the server install, which entails <a href="https://urbit.org/getting-started/server#install-urbit-via-the-command-line">downloading a shady-looking CLI binary</a> and feeding it a keyfile... which supposedly comes with the passport, but mine didn't have one, and the setup instructions make it too easy to accidentally skip over the part where you can redownload said keyfile at <a href="https://bridge.urbit.org">bridge.urbit.org</a> in the "OS" menu at the bottom of the page.</p>
|
||||
<p>It took what felt like forever (at least ten minutes; I timed it) to get to a prompt after running <code>~/urbit/urbit -p 57323 -w socleb-fosrut -k ./socleb-fosrut.key</code>. The web interface, the port to run on specified with the <code>-p</code> option, completely ignored this argument and instead decided to run on port 8081, which thankfully wasn't claimed by any other process at the time. You still need the CLI running in a separate window, though, because you'll need to run <code>+code</code> in the "dojo" (Urbit speak for the CLI) to generate a code to log in to the web interface.</p>
|
||||
<p>On first run, there are only three options in the web UI: "Terminal", "Groups", and "Bitcoin". I tried Terminal first. It appeared that whatever I typed into it was immediately mirrored in the CLI window. I typed <code>help</code> thinking it would give me a list of commands like it does in Bash, but instead I got the nonsensical string <code><1.lqz [* <232.hhi 51.qbt 123.ppa 46.hgz 1.pnw %140>]></code>. (At least it has an angel number...?)</p>
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@
|
|||
</div>
|
||||
<hr>
|
||||
<div class="box">
|
||||
<p>The nice thing about being the admin of Let's Decentralize is that, whenever I wish there was a way to do something on the Internet anonymously, I already have a mental record of which of those things I can do simply by hopping onto Tor Browser. Need to look at a public Twitter feed? <a href="http://xanthexikes7btjqlkakrxjf546rze2n4ftnqzth6qk52jdgrf6jwpqd.onion/rollcall/tor.html#nitter">Peep that shit using a Nitter instance</a>. Need to look up a weird health symptom or something potentially incriminating (like if it's spelled sodium <em>nitrite</em> with an I or <em>nitrate</em> with an A)? <a href="http://xanthexikes7btjqlkakrxjf546rze2n4ftnqzth6qk52jdgrf6jwpqd.onion/rollcall/tor.html#searx">Searx instances</a> have an awfully hard time tracking <code>127.0.0.1</code>. Publishing code for a project that enables the user to do something illegal, like <a href="https://web.archive.org/web/20221022233636/https://deemix.app/">download massive amounts of music off Deezer</a>? Codeberg and Notabug are pretty Tor-friendly, but you can do one better by <a href="https://letsdecentralize.org/rollcall/gits.md">using a hidden service</a>.</p>
|
||||
<p>The nice thing about being the admin of Let's Decentralize is that, whenever I wish there was a way to do something on the Internet anonymously, I already have a mental record of which of those things I can do simply by hopping onto Tor Browser. Need to look at a public Twitter feed? <a href="http://hikariu7kodaqrmvu3c3y422r6jc7gqtpvvbry6u7ajvranukx6gszqd.onion/rollcall/tor.html#nitter">Peep that shit using a Nitter instance</a>. Need to look up a weird health symptom or something potentially incriminating (like if it's spelled sodium <em>nitrite</em> with an I or <em>nitrate</em> with an A)? <a href="http://hikariu7kodaqrmvu3c3y422r6jc7gqtpvvbry6u7ajvranukx6gszqd.onion/rollcall/tor.html#searx">Searx instances</a> have an awfully hard time tracking <code>127.0.0.1</code>. Publishing code for a project that enables the user to do something illegal, like <a href="https://web.archive.org/web/20221022233636/https://deemix.app/">download massive amounts of music off Deezer</a>? Codeberg and Notabug are pretty Tor-friendly, but you can do one better by <a href="https://letsdecentralize.org/rollcall/gits.md">using a hidden service</a>.</p>
|
||||
<p>Unfortunately I also have a bad habit of <a href="../september/browsers.html">giving moids on the Internet the time of day</a> and falling victim to <a href="https://web.archive.org/web/20221022234415/https://lifehacker.com/what-cunninghams-law-really-tells-us-about-how-we-inter-1848733445">Cunningham's law</a>. So when I booted up <a href="https://codeberg.org/lethe/beres">Beres</a>, the worst RSS feed reader in existence (I should know; I made the damn thing), and saw that our (formerly-)favorite moid was <a href="https://archive.ph/S4Q8R">failing at technology <em>yet</em> again</a>, naturally I felt the urgent need to respond. Thankfully I managed to calm myself before sitting down to write this post. I decided to not make you slog through a misandrist rant. You're welcome!</p>
|
||||
<p>The argument of the aforementioned article is twofold:</p>
|
||||
<ol>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue