Update
parent
df321dd3b1
commit
50e8d1106d
@ -1,3 +1,3 @@
|
||||
# Audiophilia
|
||||
|
||||
Audiophilia is a mental disease that makes one scared of low or normal quality audio.
|
||||
Audiophilia is a mental disease, similar to other diseases such as [distrohopping](distrohopping.md) and chronic [ricing](rice.md), that makes one scared of low or normal quality audio.
|
@ -0,0 +1,9 @@
|
||||
# "Cloud Computing"
|
||||
|
||||
*Cloud is just someone else's computer.*
|
||||
|
||||
Cloud computing, more accurately known as clown computing, means giving up an autonomous computer by storing one's data as well as running one's programs on someone else's (often a corporation's) [computer](computer.md), known as *the cloud*, through the [Internet](internet.md), becoming wholly [dependent](dependency.md) on *someone else* to which one gives all the power. While the general idea of [server computers](server.md) and remote [terminals](terminal.md) is not bad in itself and may be utilized in very good ways, the term *cloud computing* stands for abusing this idea e.g. by [capitalists](capitalism.md) or states to take away autonomous computers from the people as well as to restrict freedoms of people in other ways, for example by pushing [DRM](drm.md), making it impossible to truly own a copy of software or other data, to run computations privately, isolated from the Internet or run non-approved, [user-respecting](free_software.md) software. Moreover clown computing as applied nowadays is mostly a very bad engineering approach that wastes [bandwidth](bandwidth.md), introduces [lag](lag.md), requires complex and expensive infrastructure etc.
|
||||
|
||||
Despite all this "cloud" is the mainstream nowadays, it is the way of computing among [normies](normies.md), even despite regular leaks and losses of their personal data etc., simply because they're constantly being pushed to it by the [big tech](big_tech.md) ([Apple](apple.md), [Google](google.md), [Micro$ost](microsoft.md), ...) -- many times they don't even have a choice, they are simply supposed to SHUT UP AND CONSUME. And of course they wouldn't even have an idea about what's going on in the first place, all that matters to a normie is "[comfort](comfort.md)", "[everyone does it](everyone_does_it.md)", "I just need my [TikTok](tiktok.md)" etc. [Zoomers](zoomer.md) probably aren't even aware of the cloud, they simply have phones with apps that show their photos if Apple approves of it, they don't even care how shit works anymore.
|
||||
|
||||
In the [future](future.md) non-cloud computers will most likely become illegal. This will be justified by autonomous computers being "dangerous", only needed by [terrorists](terrorist.md), [pirates](piracy.md) and [pedophiles](pedophilia.md). An autonomous computer will be seen as a [gun](gun.md), the right to own it will be greatly limited.
|
@ -0,0 +1,48 @@
|
||||
# Free/Freedom-Friendly Hardware
|
||||
|
||||
Free (as in freedom) hardware is a form of ethical [hardware](hardware.md) aligned with the philosophy of [free (as in freedom) software](free_software.md), i.e. having a free [licensed](license.md) designed that allows anyone to study, use, modify and share such designs for any purpose and so prevent abuse of users by technology. Let us note the word *free* refers to user freedom, not price! Sometimes the term may be more broadly and not completely correctly used even for hardware that's just highly compatible with purely free software systems -- let us rather call these a **freedom friendly hardware** -- and sometimes people misunderstand the term *free* as meaning "gratis hardware"; to avoid misunderstandings [GNU](gnu.md) recommends using the term **free design hardware** or **libre hardware** for free hardware in the strict sense, i.e. hardware with free licensed design. Sometimes -- nowadays maybe even more often -- the term *"[open source](open_source.md)" hardware* or *open hardware* with very similar meaning is encountered, but that is of course a [harmful](harmful.md) terminology as open source is an inherently harmful [capitalist](capitalism.md) movement ignoring the ethical question of freedom -- hence it is recommended to prefer using the term free hardware. Sometimes the acronym FOSH (free and open source hardware) is used neutrally, similarly to [FOSS](foss.md).
|
||||
|
||||
[GNU](gnu.md), just like [us](lrs.md), highly advocates for free hardware, though, unlike with software, they don't completely reject using non-free hardware nowadays, not just for practical reasons (purely free hardware almost doesn't exist), but also because hardware is fundamentally different from software and it is possible to use *some* non-free hardware (usually the older one) relatively safely, without sacrificing freedom. The [FSF](fsf.md) issues so called **[Respects Your Freedom](ryf.md)** (RYF) certification for non-malicious hardware products, both free and non-free, that can be used with 100% free software (even though RYF has also been a target of some criticism of free software activists).
|
||||
|
||||
We, [LRS](lrs.md), advocate for more strict criteria than just a free-licensed hardware design, for example we prefer complete [public domain](public_domain.md) and advocate high [simplicity](kiss.md) which is a prerequisite of true freedom -- see [less retarded hardware](less_retarded_hardware.md) for more.
|
||||
|
||||
The topic of free hardware is a bit messy, free hardware definition is not as straightforward as that of free software because hardware, a physical thing, has some inherently different properties than software and it is also not as easy to design and create so it evolves more slowly than software. For example the very question of what even is hardware? There is a grey area between hardware and software, sometimes we see [firmware](firmware.md) as hardware, sometimes as software, sometimes pure software can be hardwired into a circuit so it basically behaves like hardware etc. Hardware design also has different levels, a higher level design may be free-licensed but its physical implementation may require existing lower level components that are non-free -- does such hardware count as free or not? We have to keep these things in mind. While in the software world it is usually quite easy to label a piece of software as free or not, with hardware we rather tend to speak of different levels of freedom, at least for now.
|
||||
|
||||
## Existing Free And Freedom-Friendly Hardware And Firmware
|
||||
|
||||
{ I'm not so much into hardware, this may be incomplete or have some huge errors, as always double check and please forgive :) Report any errors you find, thanks. ~drummyfish }
|
||||
|
||||
TODO, WORK IN PROGRESS, UNDER CONSTRUCTION
|
||||
|
||||
The following is a list of hardware whose design is **at least to some degree** free/open (i.e. for example free designs that however may be using a non-free CPU, this is an issue discussed above):
|
||||
|
||||
- **[Arduino](arduino.md)**: Extremely popular single board microcontrollers that can be easily used to make various devices. Designs and software tools are free, however the name Arduino is trademarked AND the hardware designs are using existing proprietary components, e.g. the [AVR](avr.md) MCUs, i.e. Arduino is not 100% free from the ground up, but the degree of freedom is high and the hardware is kind of simple, i.e. friendly to tinkering and hacking.
|
||||
- **[RISC-V](risc_v.md)**: Big project creating a free-licensed [instruction set architecture](isa.md), usable by anyone for anything etc. (however the RISC-V brand is [trademarked](trademark.md)). A number of free CPUs/SOC implementations exist (alongside many proprietary implementations), for example [PicoRV32](picorv32.md) or [Sodor](sodor.md).
|
||||
|
||||
The following is a list of some "freedom friendly" hardware, i.e. hardware that though partly or fully proprietary is not or can be made non-malicious to the user:
|
||||
|
||||
- **[Ben NanoNote](ben_nanonote.md)**: tiny [GNU](gnu.md)/[Linux](linux.md) laptop whose design is free, however it utilizes e.g. a proprietary CPU.
|
||||
- **[DragonBox Pyra](pyra.md)**: Upcoming small handheld computer running [GNU](gnu.md)/[Linux](linux.md) that *almost* meets the RYF criteria, schematics will be available, GPU drivers are sadly proprietary.
|
||||
- **[Librem 5](librem5.md)**: WARNING, this device has been criticized a lot. It's an "open"/privacy-friendly smartphone with free-licensed design running [GNU](gnu.md)/[Linux](linux.md), however it uses proprietary firmware (loaded from secondary CPU to sneakily comply with RYF) and the functionality is, according to reviews, horrible.
|
||||
- **[MNT Reform](mnt_reform.md)**: "Open hardware" (free-licensed design but using proprietary components) laptop with [NXP](nxp.md) [ARM](arm.md) CPU and [Vivante](vivante.md) GPU that can run with free drivers, has no camera or microphone. Pretty expensive.
|
||||
- **Old [Thinkpad](thinkpad.md) laptops**: Old thinkpads such as [X200](x200.md), [T400](t400.md) and [T500](t500.md) are construction-wise superior to maybe any other laptop ever made, however despite being proprietary they are compatible with [libreboot](libreboot.md) and can be purchased with [Intel ME](intel_me.md) CPU backdoor disabled, offering complete control over the device, plus they can be bought relatively cheap. Very popular.
|
||||
- **[Open consoles](open_console.md)** such as [Arduboy](arduboy.md), [Pokitto](pokitto.md) and [Gamebuino](gamebuino.md) usually utilize a lot of simple free hardware such as [Arduino](arduino.md), provide schematics, free libraries and encourage hacking.
|
||||
- **Other proprietary laptops**: many mostly older laptops are freedom friendly, e.g. Asus C201 Chromebook. You can usually find these in the libreboot compatibility list.
|
||||
- **[Pinephone](pinephone.md)**: Another "free/open" smartphone running GNU/Linux, probably better than Librem5, also uses some proprietary firmware (e.g. for Wifi), design is only source-available.
|
||||
- **[Ringo MakerPhone](ringo.md)**: Educational Arduino dumbphone running on free software, by [Circuitmess](circuitmess.md). { I own one, is a bit buggy but [works](just_werks.md) for calls and messages. ~drummyfish }
|
||||
|
||||
The following is a list of [firmware](firmware.md), [operating systems](os.md) and software tools that can be used to liberate freedom-friendly proprietary devices:
|
||||
|
||||
- **[coreboot](coreboot.md)**: "Open source" replacement for proprietary [BIOS](bios.md) in personal computers. For higher compatibility coreboot includes proprietary [binary blobs](binary_blob.md) for devices that require them, in a similar fashion to [Linux](linux.md), and so coreboot is not 100% free -- libreboot tries to fix this.
|
||||
- **[libreboot](libreboot.md)**: Completely free version of coreboot, with proprietary blobs removed. However this very much limits the list of libreboot compatible devices.
|
||||
- **[PostmarketOS](postmarketos.md)**: Mobile [GNU](gnu.md)/[Linux](linux.md) distribution that can be used to liberate smartphones.
|
||||
- **[Replicant](replicant.md)**: Fork of [Android](android.md) mobile OS that replaces proprietary components with free software, can be used to liberate smartphones, though it is still [bloat](bloat.md).
|
||||
- **[Rockbox](rockbox.md)**: Free firmware for digital audio players allowing replacement of the proprietary firmware and even improving on functionality and [GUI](gui.md).
|
||||
|
||||
|
||||
## See Also
|
||||
|
||||
- [free software](free_software.md)
|
||||
- [RYF](ryf.md)
|
||||
- [public domain computer](public_domain_computer.md)
|
||||
- [less retarded hardware](less_retarded_hardware.md)
|
@ -0,0 +1,5 @@
|
||||
# Furry
|
||||
|
||||
TODO
|
||||
|
||||
In the past we might have been wondering whether by 2020 we'd already have cured cancer, whether we'd have cities on Mars and flying cars. Well no, but you can sexually identify as a fox now.
|
@ -1,9 +1,14 @@
|
||||
# KISS
|
||||
|
||||
KISS (Keep It Simple, Stupid!) is a design philosophy that favors simplicity, solutions that are **as simple as possible** to achieve given task (but no more). This comes from the fact that higher [complexity](complexity.md) comes with increasingly negative effects such the cost of development, cost of [maintenance](maintenance.md), greater probability of bugs and security vulnerabilities. More about this in [minimalism](minimalism.md) article.
|
||||
KISS (Keep It Simple, Stupid!) is a design philosophy that favors simplicity, solutions that are **as simple as possible** to achieve given task (but no more). This comes from the fact that higher [complexity](complexity.md) comes with increasingly negative effects such the cost of development, cost of [maintenance](maintenance.md), greater probability of bugs and security vulnerabilities. More about this can be read in the article on [minimalism](minimalism.md).
|
||||
|
||||
Apparently the term originated in the US Army plane engineering: the planes needed to be repairable by *stupid* soldiers with limited tools under field conditions.
|
||||
Apparently the term *KISS* originated in the US Army plane engineering: the planes needed to be repairable by *stupid* soldiers with limited tools under field conditions.
|
||||
|
||||
Compared to [suckless](suckless.md), [unix philosophy](unix_philosophy.md) and [LRS](lrs.md), KISS is a more general term, it doesn't imply any specifics but rather the general overall idea of simplicity being an advantage ([less is more](less_is_more.md)).
|
||||
Compared to [suckless](suckless.md), [unix philosophy](unix_philosophy.md) and [LRS](lrs.md), KISS is a more general term and isn't tied to any specific group or movement, it doesn't imply any specifics but rather the general overall idea of simplicity being an advantage ([less is more](less_is_more.md)).
|
||||
|
||||
[KISS Linux](kiss_linux.md) is an example of software developed under this philosophy and adapting the term itself.
|
||||
[KISS Linux](kiss_linux.md) is an example of software developed under this philosophy and adapting the term itself.
|
||||
|
||||
## See Also
|
||||
|
||||
- [minimalism](minimalism.md)
|
||||
- [KILL](kill.md)
|
@ -0,0 +1,5 @@
|
||||
# Less Retarded Hardware
|
||||
|
||||
PLACEHOLDER :)
|
||||
|
||||
COMING SOON
|
@ -1,7 +1,7 @@
|
||||
# Pseudominimalism
|
||||
|
||||
Pseudominimalism is the property of technology of trying to appear [minimalist](minimalism.md) on the surface while being [bloated](bloat.md) on the inside. A typical example could be a website that has minimal look -- a blank white background with some fancy-font text perhaps -- which in the background uses dozens of [JavaScript](js.md) frameworks and libraries and requires a high end CPU to even appear responsive. [Apple](apple.md) is heavily practicing pseudominimalism.
|
||||
Pseudominimalism is the kind of technology design which aims to appear [minimalist](minimalism.md) on the outside while being [bloated](bloat.md) on the inside. Rather than trying to achieve a truly good, minimalist design from the ground up, with all its advantages, pseudominimalism just tries to hide the ugliness of its internals and appeal purely by the looks. A typical example could be a website that has a minimalist look -- a blank background with sans-serif font text and a few nice looking shapes -- which in the background uses dozens of [JavaScript](js.md) frameworks and libraries and requires a high end CPU to even appear responsive. Basically all [modern](modern.md) "retro" video [games](game.md) are pseudominimalist in design, they use pixelated graphics but are created in huge frameworks such as [Unity](unity.md) or [Godot](godot.md); even projects calling themselves "minimalist", such as many [fantasy consoles](fantasy_console.md), are in fact only pseudominimalist, written in extremely high level languages such as [JavaScript](javascript.md). [Apple](apple.md) is heavily practicing pseudominimalism.
|
||||
|
||||
Another example are many [modern](modern.md) [CLI](cli.md) programs that [code monkeys](coder.md) use to impress their [YouTube](youtube.md) viewers or to feel like matrix haxors. Some people think that anything running in the command line is minimalist which is less and less true as we progress into the future. A lot of [capitalist software](capitalist_software.md) add a CLI interface ex post **on top** of an already bloated program, often by simply disabling [GUI](gui.md) (but leaving all its dependencies in). An example may be the [gomux](gomux.md) chat client.
|
||||
Another example are many [modern](modern.md) [CLI](cli.md) programs that [code monkeys](coder.md) use to impress their [YouTube](youtube.md) viewers or to feel like matrix haxors. Some people think that anything running in the command line is minimalist which is less and less true as we progress into the [future](future.md). A lot of [capitalist software](capitalist_software.md) add a CLI interface ex post **on top** of an already bloated program, often by simply disabling [GUI](gui.md) (but leaving all its [dependencies](dependency.md) in). An example may be the [gomux](gomux.md) chat client.
|
||||
|
||||
Yet another kind of pseudominimalism appearing among the new generation of pseudoprogrammers is about writing very few LOC in some hugely bloated language and calling that "minimalism". Something like a *Minecraft clone in 100 LOC of Python using only Python standard library*, the catch of course being that [Python](python.md) itself is hugely bloated and its standard library is enormous, therefore they just hide all the complexity out of view. Such effort is of course completely useless and only serves for flexing in front of beginners who can't spot the trick.
|
||||
Yet another kind of pseudominimalism appearing among the new generation of pseudoprogrammers is all about writing very few LOC in some hugely bloated language and calling that "minimalism". Something like a *Minecraft clone in 100 LOC of Python using only Python standard library*, the catch of course being that [Python](python.md) itself is hugely bloated and its standard library is enormous, therefore they just hide all the complexity out of view. Such effort is of course completely useless and only serves for flexing in front of beginners who can't spot the trick. Even if obvious, it has to be noted that **minimalist software cannot be written in a bloated language**.
|
Loading…
Reference in New Issue