My biggest beef with NixOS is absolutely awful documentation.

You can find three different pages on the same topic and not one of them will answer your question on it

It recommends random guides that don't work, probably due to being outdated

Different pages and "recommended" guides reference completely different ways of doing the same thing so you often cannot use one to fix your issues with another without adopting different way of doing what you are doing

I also wanted to say smart thing a lot of people already said.

Fediverse will not “fail” or “not succeed” because of random reasons new people think it would. It may be damaged, intentionally or not, but it already succeeded as community driven project, because it has community that cares about it and it does not rely on a big companies to run everything. It succeeded as a social network, since community has it’s own friendships, enemies, love and hate, idiots and geniuses. It succeeded as a technology, because it works and it’s community uses it as a main social network.

Of course, Fediverse is not ideal, and we want it to be better, but it’s technical and specific UX issues, not some fundamental difference or backing of company.

So, I had 3 major errors building nix package were:
1 is nix changing CMake build location for it's own reasons
2 is dependencies not mentioned in Compilation guide for software

Currently I only need to fix symlinks in built software folder pointing in absolute paths of where stuff were during building

Idea how “post migration” could work:

- New server fetches all (or limited amount) of old account’s posts and, if possible, replies
- It doesn’t post them again, but just stores and puts in new account below new posts, with mark “migrated to @user@newserver.example.com” similar to how boosts shown
- Opening that posts works like for federated posts boosted by new account

This could help avoid federation issues related to old account replies, but drawback is that because how activityPub currently works, it will not federate futher than it already did if old server gets shut down.

I played random childrens' videogame that has multiplayer.

Room/server theme was roleplay about magical school or something, so I made quick Otome Game Villainess knockoff character to play as. Sometimes I stopped to write about specifics and limitations of ability my character just used. And someone played as child dragon my character adopted, and made cat noises.

Next morning, I found myself writing thought-out and serious lore about that villainess, writing her backstory, motivations, early life traumas, rewriting descriptions of all the stupid abilities with practical use-cases and even more thought out limitations...

Yet again post aimed at new users, this time really quick:

-

Instances or servers are basically separate websites owned by differemt people you can register on while being connected to the whole network. Usually users are shown as @user@website (or shown as just @user if you are on the same server or you use Mastodon, but keep in mind it is still actually @user@website)

-

Please read instance rules, and register on different one if you disagree with rules. Keep in mind non-freespeech servers usually block communicating with freespeech servers for reason later being filled with hatespeech and trolls.

-

Don’t be discouraged if you cannot understand something, ask other people about it.

-

I recommend using smaller instances, since they allow you to have a smaller local community around you that can help understanding what’s happening, but you still will be able to communicate to big instance users.