There is also writefreely. It is fairly basic, but says it supports “publish[ing] to multiple blogs from one account”. Haven’t really used it, but it looks kinda cool imo

https://github.com/writefreely/writefreely

I’m not an expert on btrfs, but I assume the inconsistencies come from deduplication, metadata, and maybe compression. I think some of them just count raw block storage, and some include the cost of metadata.

Traditional du assumes that each file takes up it’s full space on disk which isn’t always the case on btrfs. When using btrfs backed oci images, storage can easily appear multiple times higher.

I use btrfs filesystem usage /. I’m not sure that it is the “correct” way, but it works fairly well.

Standard forgejo shoutout. It is a fork of gitea with more features following the foss philosophy. It is codeberg’s backend https://forgejo.org/2024-02-monthly-update/

You can still compile infinity from source with your own api key

I run stable diffusion in a docker container. Most kernels ships the required drivers, and you can install the rocm libraries inside a docker container to keep them from poluting the host.

Here’s my docker image, feel free to take a look. I won’t guarantee it’ll work for you, but hopefully it will give you some hints in the right direction. https://codeberg.org/it-a-me/auto1111-webui_rocm

“real” bedrock modding is still in its infancy, but there is progress. LeviLamina is a framework that allows for a lot of server features that were previously more or less impossible. https://github.com/LiteLDev/LeviLamina

Bedrock modding at the moment is focused more on serverside software because, unlike java, the core game code runs natively rather than in a java virtual machine. That means client modifications are a lot harder and require duplicated effort for each platform. That’s without mentioning that the linux version of the bedrock server comes with debug symbols that aid decompilation.

Some client mods do exist though. We have onix, a dll injector that adds a lot of useful features. Unfortunatly it is not open source and it doesn’t support linux so I can’t speak for the quality or legality. People have also prematurely figured out shaders for render dragon(minecraft’s new universal rendering engine). Useless shaders adds redstone level indicators and better chunk borders. https://github.com/OEOTYAN/useless-shaders/releases

Some missing plugins people often want for bedrock are carpetmod and litimatica. Trapdoor tries to act similar to carpetmod and Sructura can also can more or less replace litimatica for simple usecases.
https://github.com/bedrock-dev/trapdoor-ll https://github.com/RavinMaddHatter/Structura/releases

For world modification and analysis, the most complete solution is rbedrock. It is very useful for world trimming, village cleanup, and creating fake structures, and other things https://github.com/reedacartwright/rbedrock

Finally, redstone and mob farms. For redstone, the biggest problems people have are missunderstanding the differences from java. The main one being that redstone processing happens in two distinct parts(producer tick and consumer tick). Pticks happen every game tick but cticks only happen on odd game ticks(like javas redstone ticks). During a ptick, redstone consumers are just added to an unsorted list to get powered on the next ctick. That leads to the random result that is often complained about.

Mob farms are limited primarily by our miniscule 24 mob cap(8 surface 16 cave). Recent advancements have allowed the use of split density(abusing the fact that bedrock mob caps only check 4 chunks in each direction) to help reduce the issue. The other two weird quirks are that structure spawning is screwy(I can go to more detail if desired) and mobs spawn on the northwest corder of the spawnable block.

Technical bedrock does exist, it is just a less developed field than java. Lmk if you have any questions, I can try to answer them or link to some discords that I’ve lurked in to learn this stuff

Slint has fairly decent docs and has worked fairly well for my small projects

I’ve gotten tired of weird regex stuff in awk, sed, and grep, so I’ve moved to perl -E for all but the most basic of things.

1. Codeberg is fully open source(forgejo) while gitlab has an open source core+community edition but a source available propietary enterprize edition.

2. Codeberg is a nonprofit with no ulterior motives. Gitlab is a publicly traded for profit entity with a goal to make profit

3. This could just be me, but codeberg feels a lot more transparent. When they have outages, they explain why.

4. Super minor, but the codeberg team “self-hosts” their own servers so you only need to trust the one entity rather than additionally trusting the server provider.

Primary code editor: helix

Graphical debugger and certain IDE features: vscodium

Lots of open source language servers: clangd, rust-analyzer, perl-navigator, …

Makefile to compile-comands.json: bear

TUI file manager: yazi

Better Grep:ripgrep

Debugger: gdb(gnu debugger)

The main advantage of having a /home partition is that you can easily preserve it during reinstalls or during a distro hop. Reinstalls used to be more common in the past when some distros didn’t allow full distro upgrades without reinstalling. See this result which is still ranked #1 on duckduckgo

I personally use a @home btrfs subvolume which has most of the same advantages to me, and additionally allows @home and @root to share the same partition. It also allows me to use luks on everthing without bothering with lvm.

I also don’t believe it’s even fully source availiable. There are no build instructions, and you can’t clone all the submodules without signing in to their closed application gitlab instance. If anyone has sucessfully built it from source, please lmk.

Nevermind they did add build instructions since I last checked. Still lmk if anyone’s tested them.

Section 4 is what gets me. Your rights are temporary and revokable meaning the the rest of the license doesn’t matter in the long term

## Section 4: Termination, suspension and variation
1. We may suspend, terminate or vary the terms of this license and any access to the code at any time, without notice, for any reason or no reason, in respect of any licensee, group of licensees or all licensees including as may be applicable any sub-licensees.