parent
3b62fb4fcd
commit
e3d946b213
@ -1,3 +1,5 @@
|
||||
.secret/
|
||||
sitemap.gz
|
||||
sitemap.txt
|
||||
.wip/*
|
||||
blug.md
|
||||
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
|
After Width: | Height: | Size: 159 KiB |
|
After Width: | Height: | Size: 170 KiB |
@ -0,0 +1,37 @@
|
||||
Hacking on the Rose browser
|
||||
===========================
|
||||
|
||||
I recently spent a few days hacking on the [rose browser](https://github.com/mini-rose/rose). It's a minimalist browser for Linux machines which is easy to play with. I enjoyed the experience, and thought to leave some notes.
|
||||
|
||||
Rose is written in C, and uses the Webkit and GTK libraries. Webkit, which drives Safari, started out as a fork of some previous open-source libraries, [KHTML](https://en.wikipedia.org/wiki/KHTML) and [KJS](https://en.wikipedia.org/wiki/KJS_%28software%29). [GTK](https://en.wikipedia.org/wiki/GTK) is a library for creating graphical interfaces. You can use the two together using [WebKitGTK](https://webkitgtk.org/).
|
||||
|
||||
|
||||
*<br>Pictured: An earlier version of this blogpost in the rose browser.*
|
||||
|
||||
Personally, I find the simplicity of the code soothing. Still, to improve usability and for my own enjoyment, I've been adding some code to it. You can have a look at my tweaks [here](https://github.com/NunoSempere/rose-browser). These implement two main changes:
|
||||
|
||||
1. I've implemented a [reader mode](https://github.com/NunoSempere/rose-browser/tree/personal/plugins/readability)
|
||||
2. I've added [redirection functionality](https://github.com/NunoSempere/rose-browser/tree/personal/plugins/libre_redirect), which redirects users to open source frontends of otherwise annoying websites.
|
||||
|
||||
The reader mode, for instance, returns this beautiful to read page:
|
||||
|
||||
|
||||
|
||||
when fed the cluttered aesthetic abomination that is Matt Levine's newsletter:
|
||||
|
||||
|
||||
|
||||
I lifted the code for doing this from [Firefox](https://github.com/mozilla/readability), figured out how to integrate it with WebKit, and then made a few modifications.
|
||||
|
||||
As mentioned, I also wrote a version of [LibRedirect](https://libredirect.codeberg.page/) for the rose browser. It which direct annoying websites into better open-source versions:
|
||||
|
||||
|
||||
|
||||
Lastly, I've added some code for installing the Rose browser on [Ubuntu 20.04](https://github.com/NunoSempere/rose-browser/raw/personal/rose), which is what I'm personally using.
|
||||
|
||||
If you are a close friend using Linux feel free to reach out if you get stuck trying to install this.
|
||||
|
||||
|
||||
<p><section id="isso-thread">
|
||||
<noscript>Javascript needs to be activated to view comments.</noscript>
|
||||
</section></p>
|
||||
@ -1,37 +1,32 @@
|
||||
Hacking on the Rose browser
|
||||
===========================
|
||||
Hacking on rose
|
||||
===============
|
||||
|
||||
I recently spent a few days hacking on the [rose browser](https://github.com/mini-rose/rose). It's a minimalist browser for Linux machines which is easy to play with. I enjoyed the experience, and thought to leave some notes.
|
||||
The [rose browser](https://github.com/mini-rose/rose) is a minimal browser for Linux machines. I've immensely enjoyed hacking on it this last week, so I thought I'd leave some notes.
|
||||
|
||||
Rose is written in C, and uses the Webkit and GTK libraries. Webkit, which drives Safari, started out as a fork of some previous open-source libraries, [KHTML](https://en.wikipedia.org/wiki/KHTML) and [KJS](https://en.wikipedia.org/wiki/KJS_%28software%29). [GTK](https://en.wikipedia.org/wiki/GTK) is a library for creating graphical interfaces. You can use the two together using [WebKitGTK](https://webkitgtk.org/).
|
||||
Rose is written in C, and it's based on Webkit and GTK. Webkit is the engine that drives Safari, and a fork of some previous open-source libraries, [KHTML](https://en.wikipedia.org/wiki/KHTML) and [KJS](https://en.wikipedia.org/wiki/KJS_%28software%29). [GTK](https://en.wikipedia.org/wiki/GTK) is a library for creating graphical interfaces. You can conveniently use the two together using [WebKitGTK](https://webkitgtk.org/).
|
||||
|
||||
|
||||
*<br>Pictured: An earlier version of this blogpost in the rose browser.*
|
||||
|
||||
Personally, I find the simplicity of the code soothing. Still, to improve usability and for my own enjoyment, I've been adding some code to it. You can have a look at my tweaks [here](https://github.com/NunoSempere/rose-browser). These implement two main changes:
|
||||
Personally, I find the simplicity of the code soothing. At the same time, though, I've been adding some code to it, to make the browser more usable and for the fun of it. You can see my tweaks [here](https://github.com/NunoSempere/rose-browser).
|
||||
|
||||
1. I've implemented a [reader mode](https://github.com/NunoSempere/rose-browser/tree/personal/plugins/readability)
|
||||
2. I've added [redirection functionality](https://github.com/NunoSempere/rose-browser/tree/personal/plugins/libre_redirect), which redirects users to open source frontends of otherwise annoying websites.
|
||||
|
||||
The reader mode, for instance, returns this beautiful to read page:
|
||||
My first tweak was to add a [reader mode](https://github.com/NunoSempere/rose-browser/tree/personal/plugins/readability). It, for instance, returns this beautiful page:
|
||||
|
||||
|
||||
|
||||
when fed the cluttered aesthetic abomination that is Matt Levine's newsletter:
|
||||
when fed the aesthetic abomination that is Matt Levine's newsletter:
|
||||
|
||||
|
||||
|
||||
I lifted the code for doing this from [Firefox](https://github.com/mozilla/readability), figured out how to integrate it with WebKit, and then made a few modifications.
|
||||
I lifted the code for doing this from [Firefox](https://github.com/mozilla/readability), figured out how to integrate it with WebKit, and then improved it a bit.
|
||||
|
||||
As mentioned, I also wrote a version of [LibRedirect](https://libredirect.codeberg.page/) for the rose browser. It which direct annoying websites into better open-source versions:
|
||||
My second big tweak was to add [redirection functionality](https://github.com/NunoSempere/rose-browser/tree/personal/plugins/libre_redirect) from annoying websites to their open source frontends, in the style of [LibRedirect](https://libredirect.codeberg.page/):
|
||||
|
||||
|
||||
|
||||
Lastly, I've added some code for installing the Rose browser on [Ubuntu 20.04](https://github.com/NunoSempere/rose-browser/raw/personal/rose), which is what I'm personally using.
|
||||
|
||||
If you are a close friend using Linux feel free to reach out if you get stuck trying to install this.
|
||||
|
||||
And I've added some code for installing this browser on [Ubuntu 20.04](https://github.com/NunoSempere/rose-browser/raw/personal/rose), which is what I'm personally using. If you are a dear friend using Linux feel free to ask for help if you get stuck trying to install this.
|
||||
|
||||
<p><section id="isso-thread">
|
||||
<noscript>Javascript needs to be activated to view comments.</noscript>
|
||||
</section></p>
|
||||
|
||||
|
||||
@ -0,0 +1,43 @@
|
||||
A basic argument for AI risk
|
||||
============================
|
||||
|
||||
Rohin Shah [writes](https://www.lesswrong.com/posts/bkpZHXMJx3dG5waA7/ways-to-buy-time?commentId=jropYhtAW72zfHRBr) (referenced [here](https://forum.effectivealtruism.org/posts/2S3CHPwaJBE5h8umW/read-the-sequences)):
|
||||
|
||||
> Currently, I'd estimate there are ~50 people in the world who could make a case for working on AI alignment to me that I'd think wasn't clearly flawed. (I actually ran this experiment with ~20 people recently, 1 person succeeded. EDIT: I looked back and explicitly counted -- I ran it with at least 19 people, and 2 succeeded: one gave an argument for "AI risk is non-trivially likely", another gave an argument for "this is a speculative worry but worth investigating" which I wasn't previously counting but does meet my criterion above.)
|
||||
|
||||
I thought this was surprising, so here is an attempt, time-capped at 45 mins.
|
||||
|
||||
### 1. The concern is valid in the limit: An entity of arbitrary, God-like intelligence would be very scary.
|
||||
|
||||
An entity of arbitrary, God-like intelligence would be very scary. We already see that the most intelligent humans, like von Neumann and the other Hungarian Martians, were able to perform feats of science that steered humanity's fate.
|
||||
|
||||
If we had an artificial system that was as intelligent as von Neumann, this would be very scary, because it might be able to perform similar feats of science and engineering. Also, Moore's law is uncertain, but it seems likely that in a generation we could go from having just one artificial von Neuman to having many of it. This increases the stakes.
|
||||
|
||||
### 2. Year and year we are approaching the limit: What comes after Comprehensive AI Systems?
|
||||
|
||||
We can think about how the world would look like in 2030-2035 if many tasks are delegated to successors of GPT-3. In this world, interfaces between many services and AI systems exist, and these are used to affect real-world systems. For example, I might routinely use GPT-3 to edit my texts, translations might be performed in real time through speech recognition, or [automatic threat detection](https://www.lesswrong.com/posts/vDvKWdCCNo9moNcMr/us-military-global-information-dominance-experiments) and deployment might be used by the world's military.
|
||||
|
||||
Then we can think about, well, how does the world look like the decade after that one, and the decade after, and so forth. And it looks like ML systems generally acquiring more and resposability around managing human systems.
|
||||
|
||||
And in general, we might worry that as current systems become more and more capable, they might eventually exceed humans and start to manifest some of the dangers that a being of God-like intelligence would also display. Crucially, we think that the human brain is made out of human atoms and so in principle replicatable in silico.
|
||||
|
||||
### 3. Alignment proposals are uncertain, shaky and untested
|
||||
|
||||
In this situation, we would love to have some mathematical proof that these AI systems which might end up making important decisions are, in some sense, friendly to humans. We don't have that guarantee. We might hope that there might be a strong incentive to create systems that increase human flourishing rather than reduce it.
|
||||
|
||||
But on the other hand, if we look at e.g., the algorithms driving social media and reducing attention spans, this doesn't really inspire much confidence. We can also look at the organizing structure of society and notice that it alredy falls prey to Goodhart's law in that maximizing profit does not maximize flourishing. Some examples might be the [Sumangali system](https://en.wikipedia.org/wiki/Sumangali_%28child_labour%29), Nestlé [stealing water to bottle in a drought](https://www.theguardian.com/us-news/2021/apr/27/california-nestle-water-san-bernardino-forest-drought), or lobbying from weapon manufacturers making war more likely. We might worry that similar dynamics might exist if more and more decisions are put in the hands of AI systems and these are programmed to maximize something that at first looks like human flourishing but ultimately doesn't.
|
||||
|
||||
We could also worry about more speculative failure modes, in which very intelligent systems at first appear to be helpful but then stop being so as they become harder to stop. We see that these kinds of things happen with [reward hacking](https://docs.google.com/spreadsheets/d/e/2PACX-1vRPiprOaC3HsCf5Tuum8bRfzYUiKLRqJmbOoC-32JorNdfyTiRRsR7Ea5eWtvsWzuxo8bjOxCG84dAg/pubhtml) in curent models, and pop up in [models of very intelligent systems](https://www.lesswrong.com/posts/nyCHnY7T5PHPLjxmN/open-question-are-minimal-circuits-daemon-free).
|
||||
|
||||
### 4. Expected value calculations lead the way
|
||||
|
||||
Because we expect these systems to be tightly integrated with the human economy, we would like to have guarantees. But we don't have them. Given that we don't have guarantees that bad outcomes won't happen, they might in fact happen. This would be bad.
|
||||
|
||||
If we multiply the number of people who we would expect to be affected by future AI systems, this would be a large number. This is similar to how e.g., the US Federal Reserve sets monetary policy in the US, and so improving its decisions would reverberate across the US. But because AI systems will have a large scale impact, steering that impact would also be valuable. If we multiply out that impact (e.g., [here](https://www.beguide.org/hostile-artificial-intelligence.html)), the expected value turns out to be higher than other oportunities.
|
||||
|
||||
|
||||
---
|
||||
|
||||
<p><section id="isso-thread">
|
||||
<noscript>Javascript needs to be activated to view comments.</noscript>
|
||||
</section></p>
|
||||
@ -0,0 +1,85 @@
|
||||
Me in 2022
|
||||
==========
|
||||
|
||||
|
||||
|
||||
The above *.gif* shows a snapshot taken by my computer at 12:00 for a large number of days of the year. The below *.gif* shows a snapshot taken by my computer every five minutes on the 22/02/2022:
|
||||
|
||||
|
||||
|
||||
### To create such a *.gif* in Linux
|
||||
|
||||
**a. Create a script to take a photo from your webcam:**
|
||||
|
||||
```
|
||||
## Defs
|
||||
panopticonDir="~/.panopticon"
|
||||
|
||||
selfiesDir="$panopticonDir/selfies"
|
||||
today="$(date +"%Y%m%d")"
|
||||
timeNow="$(date +"%H%M%S")"
|
||||
|
||||
## Init
|
||||
mkdir -p "$selfiesDir/$today"
|
||||
|
||||
## Selfies
|
||||
|
||||
selfieFileName="webcam_$timeNow.jpg"
|
||||
/usr/bin/fswebcam -r 1280x720 "$selfiesDir/$today/$selfieFileName"
|
||||
# ^ works with pipewire
|
||||
|
||||
```
|
||||
|
||||
**b. Call the script from within crontab**
|
||||
|
||||
Call
|
||||
|
||||
```
|
||||
$ sudo crontab -e
|
||||
```
|
||||
|
||||
and then paste:
|
||||
|
||||
```
|
||||
*/5 * * * * /home/loki/.panopticon/shoot.sh
|
||||
```
|
||||
|
||||
**c. Put it all together into a gif**
|
||||
|
||||
One gif from snapshots taken at 12:00.
|
||||
|
||||
```
|
||||
summary_dir="~/.panopticon/summary-12"
|
||||
mkdir summary_dir
|
||||
for dir in ~/.panopticon/*/ ; do
|
||||
if [[ -d "$dir" && ! -L "$dir" ]]; then
|
||||
echo "Entering $dir";
|
||||
dirname_raw="$(echo "$dir" | sed 's#/##')"
|
||||
temp_photo_name="$(echo $dirname_raw/webcam_1200*)"
|
||||
echo "$temp_photo_name"
|
||||
cp $temp_photo_name temp.jpg
|
||||
mv temp.jpg $summary_dir/$dirname_raw.jpg
|
||||
fi;
|
||||
done
|
||||
|
||||
convert -delay 10 -loop 0 $summary_dir/*.jpg 12.gif
|
||||
|
||||
```
|
||||
|
||||
One for each day with something like:
|
||||
|
||||
```
|
||||
for dir in */ ; do
|
||||
if [[ -d "$dir" && ! -L "$dir" ]]; then
|
||||
echo "Entering $dir";
|
||||
dirname_raw="$(echo "$dir" | sed 's#/##')"
|
||||
convert -delay 10 -loop 0 $dirname_raw/*.jpg daily-gifs/$dirname_raw.gif
|
||||
echo "Created daily_gifs/$dirname_raw"
|
||||
fi;
|
||||
done
|
||||
|
||||
```
|
||||
|
||||
<p><section id="isso-thread">
|
||||
<noscript>Javascript needs to be activated to view comments.</noscript>
|
||||
</section></p>
|
||||
@ -1,15 +0,0 @@
|
||||
<form method="post" action="https://listmonk.nunosempere.com/subscription/form" class="listmonk-form">
|
||||
<div>
|
||||
<h3>Subscribe</h3>
|
||||
<input type="hidden" name="nonce" />
|
||||
<p><input type="email" name="email" required placeholder="E-mail" /></p>
|
||||
<p><input type="text" name="name" placeholder="Name (optional)" /></p>
|
||||
|
||||
<p>
|
||||
<input id="82ff8" type="checkbox" name="l" checked value="82ff889c-f9d9-4a45-bf9a-7e2696813021" />
|
||||
<label for="82ff8">nunosempere.com</label>
|
||||
</p>
|
||||
|
||||
<p><input type="submit" value="Subscribe" /></p>
|
||||
</div>
|
||||
</form>
|
||||
Loading…
Reference in new issue