lime!

it has the potential to be both. until people running their own instance is commonplace, it won’t be either.

the main problem is that running an instance of the atproto stack is way complex, so nobody wants to do it.

bluesky is still not decentralised. just having a protocol does not mean anyone use will use it. if bluesky is down, there’s no bluesky.

it’s not really about the type of data, it’s more about how you get it. web browsers could open gopher URIs for a long time, it was just a separate access method.

but the thing is, it doesn’t really make a difference today, because we’ve decided that http is some sort of base protocol.

someone decided to try making a custom matrix:// scheme (it’s called a scheme btw) for matrix clients and it’s just been a nightmare. clients don’t know what to do with the url, servers block it, we had to patch it out to get it to properly encrypt messages to our local homeserver. and matrix just uses http on top anyway.

no, i think they should be reserved for protocols that are important enough to be in the <1000 range of ports. like SSH, or Doom multiplayer.

i’ve seen something like this before, where the kernel holds the file handle open for the process so that it thinks the file is still there. i think it’s related to how the program closes the file but i don’t remember the details. restarting qbittorent will most likely fix it.

jellyfin is a streaming server. get yourself a domain name and you can connect your apps to it from anywhere.

i’m glad you found it useful, best of luck :)

this is more focused for sure, but it lacks the enthusiasm of the original. if i was trying to do this for work, i would appreciate how quickly it gets to the point. however, it no longer reads like this is something you’re interested in. it reads a bit wooden. i get that would happen after you’ve been told to correct your style though.

to be clear, the original article doesn’t need to be rewritten. for the future though, when you want to tell the story of how you got something working, include your reasons for doing something a certain way. if you need a self-inflicted complication, that’s not really a part of it (unless it’s funny)

your writing overall is good! it’s just a matter of information priority.

here’s a tip, dunno how applicable it is but i use it when writing technical documentation:

for each step, explain to yourself why you’re doing it the way you are. if it turns out you caused the step to be needed, rather than it being required, you probably need to rethink, or at least add the explanation to the text.

this guide, and the previous one, have a lot of weird superfluous steps. like, why use a command that includes nvim and then ask people to change it instead of just saying “edit the file”? why symlink systemd stuff to your own home directory?

the info is good, but having to separate the actually useful stuff from things that are specific to your config makes it less useful.

if donations aren’t enough, scale down until they are. if that’s not an option, then we let those instances die and set up new ones.

this is a network for people. if someone is not enthusiastic about running an instance, they don’t have to.