Change felix's site to have the basic stuff for gayBSD
Erin A
3 years ago
parent
2d8b65567f
commit
e7ac155c24
@ -1,6 +1,6 @@
|
||||
- name: Home
|
||||
link: /
|
||||
- name: Packages
|
||||
link: /pkg/
|
||||
- name: Project
|
||||
link: /project/
|
||||
- name: About
|
||||
link: /about/
|
||||
|
||||
@ -1,6 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: hello, world
|
||||
---
|
||||
|
||||
If you can read this, i am able to deploy a webbed site.
|
||||
@ -1,78 +0,0 @@
|
||||
---
|
||||
layout: post
|
||||
title: "UwUI: Making the Most out of CLI and GUI"
|
||||
tags: tech
|
||||
---
|
||||
|
||||
The most common implementations of human-machine interaction are the CLI and GUI--two concepts with
|
||||
mutually exclusive core beliefs, having caused countless heated discussions over which one of them
|
||||
being superior. While the former focuses on brevity and efficiency, the latter excels at guiding
|
||||
(especially, but not only) unexperienced users by being more expressive than raw text. But is that
|
||||
everything there is to this story? Obviously not, otherwise this would be the end of the article.
|
||||
|
||||
Please note that this post is just the result of a spontaneous idea and definitely not thought
|
||||
through entirely, so it is absolutely possible that i am overseeing something critical here and the
|
||||
whole thing is garbage.
|
||||
|
||||
## Using CLIs is Programming
|
||||
|
||||
The command line came long before graphical interfaces for a reason--it is the least ambiguous and
|
||||
most simple way to receive user input, and CLI parameter parsing libraries can be reused with ease.
|
||||
In other words, using the CLI can be thought of as describing a collection of instructions that are
|
||||
precise enough to be executed by a computer to achieve a specific task. If that sounds familiar,
|
||||
it's probably because the standard industry term for this is _programming_. An incredibly high
|
||||
level form of programming, sure, but still programming nonetheless. The command line is, if you
|
||||
will, nothing but a language binding between natural (human) language and machine instructions.
|
||||
|
||||
## Everything is Programming
|
||||
|
||||
Continuing this train of thought will in turn lead to the conclusion that pretty much any human
|
||||
interaction with computers is technically a form of programming, even if an excessively obfuscated
|
||||
one. And this very fact is the fundamental flaw with GUIs--they are just too good at hiding that
|
||||
the machine you are interacting with is still just that: a machine, nothing more.
|
||||
|
||||
When we are subconsciously thinking of machines as something else, we automatically make certain
|
||||
assertions about their behavior, making situations where they can't keep up with them all all the
|
||||
more frustrating. By the way, this is also a reason why graphical programming languages probably
|
||||
aren't that good of an idea for anything other than educational purposes.
|
||||
|
||||
## Write Text, View Images
|
||||
|
||||
Even though graphical programming languages aren't exactly the smartest way of _writing_ programs,
|
||||
they are doing a pretty solid job of giving people _reading_ them an understanding of what is
|
||||
roughly going on. Why? Because meat bags are as good at image recognition as machines are at
|
||||
number crunching (people say "a single image conveys more than a thousand words" for a reason).
|
||||
Coincidentally, computers have become stupidly fast at rendering stuff. So fast, in fact, that we
|
||||
can afford fancy animations and whatnot without really impacting system performance that much.
|
||||
Why not make use of the meat bags' ability to parse images then?
|
||||
|
||||
In conclusion:
|
||||
|
||||
- text is the most efficient and least ambiguous way of commanding machines,
|
||||
- people are better at understanding images than reading text, and
|
||||
- machines have become pretty fast at rendering images.
|
||||
|
||||
With that in mind, the answer to the intial question seems quite obvious: commands should be input
|
||||
as plain text, while immediate feedback is given using fancy graphics. The best application
|
||||
scenario for this is managing files, which a GUI can visualize vividly using tree views and
|
||||
thumbnails and whatnot, while a shell prompt is going to require barely more than a few keystrokes
|
||||
to do any basic action, at least if you're using autocompletion.
|
||||
|
||||
I am calling this paradigm _UwU User Interface_, or **UwUI** for short, because i am imagining it
|
||||
being indeed very uwu to use (i am absolutely not open to alternate name suggestions btw, unless you
|
||||
manage to come up with an even worse one). I am probably going to publish a proof of concept app
|
||||
for this if i don't forget about or lose interest in it, which i would definitely write a follow-up
|
||||
article about and link it here.
|
||||
|
||||
## Why Stop There?
|
||||
|
||||
But that is not everything there is to it. If you ever wanted do do stuff like bulk deleting files
|
||||
using regular expressions but ended up moving them to a different directory first or specifying the
|
||||
`-i` flag because you were too scared of accidentally deleting something you didn't intend to, a GUI
|
||||
can help by displaying all files that would be affected by the operation that is only executed once
|
||||
you hit enter.
|
||||
|
||||
Another incredibly useful feature of most GUIs is the undo button. Why wouldn't shells want to make
|
||||
use of this as well? This could make them significantly more attractive, especially to new users
|
||||
who often are afraid of breaking something. Knowing they could make everything as before by simply
|
||||
writing `undo` would lower their threshold to wanting to experiment significantly.
|
||||
@ -0,0 +1,16 @@
|
||||
---
|
||||
layout: post
|
||||
title: "GayBSD First Post"
|
||||
tags: tech
|
||||
---
|
||||
|
||||
This is just a test post! Also it'll serve as an introduction to GayBSD and stuff.
|
||||
|
||||
## Website/Links
|
||||
Currently this website doesn't have much info on it, but we'll add more as the project progresses.
|
||||
The code is currently hosted on my (erin's) personal gitea, and we'll probably setup a gitea specifically for this project sometime.
|
||||
We will also probably setup emails specifically for this, e.g (support@bsd.gay, contact@bsd.gay, whatever).
|
||||
|
||||
## The Project
|
||||
We currently haven't really done much other than this website so far.
|
||||
We want to also provide stuff that makes this distibution unique, other than the license & atmosphere.
|
||||
@ -0,0 +1,160 @@
|
||||
$color-primary: #ffb3ff;
|
||||
$color-secondary: #B41EB2;
|
||||
$color-accent: #FFF;
|
||||
$color-bg: #1a001a;
|
||||
$content-width: 900px;
|
||||
|
||||
* {
|
||||
box-sizing: border-box; /* never gets old */
|
||||
}
|
||||
|
||||
html, body {
|
||||
background-color: $color-bg;
|
||||
margin: 0;
|
||||
min-height: 100vh;
|
||||
}
|
||||
|
||||
body {
|
||||
background-color: $color-bg;
|
||||
font-family: sans-serif;
|
||||
color: rgba(255, 255, 255, 0.8);
|
||||
margin: 0;
|
||||
}
|
||||
|
||||
footer {
|
||||
padding: 20px 0;
|
||||
border-top: thin solid $color-primary;
|
||||
|
||||
.container {
|
||||
max-width: $content-width;
|
||||
margin: 0 auto;
|
||||
display: flex;
|
||||
flex-direction: horizontal;
|
||||
}
|
||||
|
||||
.container > * {
|
||||
flex: 1;
|
||||
margin: 0 20px;
|
||||
}
|
||||
}
|
||||
|
||||
@media(max-width: 550px) {
|
||||
footer .container {
|
||||
display: block;
|
||||
}
|
||||
|
||||
footer ul {
|
||||
line-height: 2rem;
|
||||
}
|
||||
}
|
||||
|
||||
h1, h2, h3, h4, h5, h6 {
|
||||
color: $color-primary;
|
||||
}
|
||||
|
||||
.page-title {
|
||||
padding-bottom: 16px;
|
||||
border-bottom: thin solid rgba(255, 255, 255, 0.2);
|
||||
}
|
||||
|
||||
p, code, ul, ol {
|
||||
font-size: 1rem;
|
||||
line-height: 1.5rem;
|
||||
font-weight: 400;
|
||||
}
|
||||
|
||||
@media(min-width: $content-width) {
|
||||
main {
|
||||
p, code, ul, ol {
|
||||
font-size: 1.2rem;
|
||||
line-height: 1.8rem;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
code {
|
||||
background-color: rgba(0, 0, 0, 0.5);
|
||||
border-radius: 4px;
|
||||
}
|
||||
|
||||
pre {
|
||||
display: block;
|
||||
padding: 20px;
|
||||
border-radius: 4px;
|
||||
background-color: rgba(0, 0, 0, 0.5);
|
||||
overflow-x: auto;
|
||||
|
||||
code {
|
||||
background: none;
|
||||
}
|
||||
}
|
||||
|
||||
header {
|
||||
padding-top: 20px;
|
||||
|
||||
h1 {
|
||||
text-align: center;
|
||||
margin: 0;
|
||||
font-weight: 400;
|
||||
font-family: "Oleo Script", sans-serif;
|
||||
}
|
||||
}
|
||||
|
||||
main {
|
||||
max-width: $content-width;
|
||||
margin: 40px auto;
|
||||
padding: 0 20px;
|
||||
}
|
||||
|
||||
article.feed-item {
|
||||
margin: 0 0 20px;
|
||||
padding: 0 0 20px;
|
||||
border-bottom: thin solid rgba(255, 255, 255, 0.2);
|
||||
|
||||
:last-child {
|
||||
margin-bottom: 0;
|
||||
}
|
||||
}
|
||||
|
||||
article.feed-item:first-child {
|
||||
margin-top: 0;
|
||||
padding-top: 0;
|
||||
}
|
||||
|
||||
article.feed-item:last-child {
|
||||
border-bottom: 0;
|
||||
margin-bottom: 0;
|
||||
padding-bottom: 0;
|
||||
}
|
||||
|
||||
a {
|
||||
color: $color-primary;
|
||||
}
|
||||
|
||||
nav {
|
||||
border-bottom: thin solid $color-primary;
|
||||
overflow-x: auto;
|
||||
white-space: nowrap;
|
||||
|
||||
ul {
|
||||
list-style-type: none;
|
||||
padding: 0;
|
||||
margin: 0 auto;
|
||||
max-width: $content-width;
|
||||
|
||||
li {
|
||||
display: inline-block;
|
||||
|
||||
a {
|
||||
padding: 20px;
|
||||
display: inline-block;
|
||||
font-weight: 700;
|
||||
}
|
||||
}
|
||||
|
||||
li[aria-current] a {
|
||||
text-decoration: none;
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
@ -1,40 +0,0 @@
|
||||
---
|
||||
layout: default
|
||||
title: Package Mirrors
|
||||
permalink: /pkg/
|
||||
---
|
||||
|
||||
# Package Mirrors
|
||||
|
||||
I maintain a public mirror of selected software repositories which is free to
|
||||
use for everyone. The available bandwidth is "some", and you are guaranteed a
|
||||
yearly average uptime of at least "probably".
|
||||
|
||||
## Arch Linux
|
||||
|
||||
Official Arch Linux packages and ISOs for x86. <https://archlinux.org>
|
||||
|
||||
ISOs:
|
||||
[clearnet](https://pkg.fef.moe/archlinux/iso),
|
||||
[darknet](http://os5st7tudx7m5nqhce5zrmlqkfhsfgsj4z6gxhzl3lg7pgoxvfwrw3yd.onion/archlinux/iso)
|
||||
|
||||
```
|
||||
https://pkg.fef.moe/archlinux/$repo/os/$arch
|
||||
rsync://pkg.fef.moe/archlinux/$repo/os/$arch
|
||||
http://os5st7tudx7m5nqhce5zrmlqkfhsfgsj4z6gxhzl3lg7pgoxvfwrw3yd.onion/archlinux/$repo/os/$arch
|
||||
rsync://os5st7tudx7m5nqhce5zrmlqkfhsfgsj4z6gxhzl3lg7pgoxvfwrw3yd.onion/archlinux/$repo/os/$arch
|
||||
```
|
||||
|
||||
## Arch4edu
|
||||
|
||||
Community repository for Arch Linux providing prebuit software that is commonly
|
||||
used in education. Available for both x86 and ARM.
|
||||
<https://github.com/arch4edu/arch4edu/wiki>
|
||||
|
||||
```
|
||||
https://pkg.fef.moe/arch4edu/$arch
|
||||
rsync://pkg.fef.moe/arch4edu/$arch
|
||||
http://os5st7tudx7m5nqhce5zrmlqkfhsfgsj4z6gxhzl3lg7pgoxvfwrw3yd.onion/arch4edu/$arch
|
||||
rsync://os5st7tudx7m5nqhce5zrmlqkfhsfgsj4z6gxhzl3lg7pgoxvfwrw3yd.onion/arch4edu/$arch
|
||||
```
|
||||
|
||||
@ -0,0 +1,13 @@
|
||||
---
|
||||
layout: default
|
||||
title: Package Mirrors
|
||||
permalink: /project/
|
||||
---
|
||||
|
||||
# Basic Overview
|
||||
|
||||
So the basic idea is to fork FreeBSD and relicense it under the CNPL in order to scare away anyone who disregards basic human rights, hopefully resulting in a welcoming user base that is truly inclusive and anyone can feel safe in. GayBSD is going to be a project by and for the community, with absolutely zero corporate interference whatsoever.
|
||||
|
||||
## Goals
|
||||
|
||||
Unlike most *NIX operating systems out there, GayBSD is aimed primarily at desktops/laptops and small homeservers. Because abolishing any form of gatekeeping is part of the core philosophy, simpler implementations are generally favourable over better performing ones when adding new features in order to keep the code as easily understandable as possible. Reimplementations of userspace programs in "friendlier" languages than ANSI C are also possible, as long as it's not breaking stuff. Even though forking a Linux distro would lower the bar to entry even further because way more people are familiar with it, this unfortunately is probably not in the project's best interest because the GPL prohibits modifications under a different license. And it wouldn't piss off RMS nearly as much.
|
||||
Loading…
Reference in New Issue