I guess I understand correctly that in #Friendica you can 'Follow a thread', 'Ignore a thread' and 'Unignore a thread', in that order. These actions are all done from the 'More' menu on the top post in a thread, which may show as an icon with three dots. You can only ignore a thread you were following; unignore undoes that. When you like a post or reshare it, you automatically follow the thread.

What surprises me is that this influences the notifications you get, not so much the timelines. With regards to the network timeline, in the 'Latest post' setting you never get updates to threads whether you follow them or not, while in the 'Latest activity' you get updates, by everybody, for all threads even the ones you don't follow. There's no in between like 'Latest activity for followed threads' or 'Latest activity by people I follow'.

So if you like a post that consequently many people reply to, maybe because it is some good news story, you keep getting notifications on the bell icon from people you don't follow and that don't @-mention you. That takes a bit of getting used to.

Also I'm still trying to figure out the five different notification streams that exist in Friendica. Only one of those is attached to the notification bell and it's not the one I'm expecting.

People who buy NFTs are being duped. As far as I can tell the #NFT concept is like this:

There's a piece of art in some room. Everybody can visit that room and see that piece of art. You buy your exclusive NFT for that art because you like it and the technology makes sure only you can use that NFT. Everybody can still visit that room and see the piece of art.

You could sell the NFT to the art to someone else for money. You would still be able to see the art in the room. They can already see the art in the room. Everybody can.

But the NFT is not for the art, it's for the location of the art. So you bought an exclusive copy of the room number the art is in. But everybody can still see the art, because they also know what room the art is in.

But the NFT is not really the room number, it's the piece of paper the room number is written on. It's your piece of paper, you will not let anyone copy your piece of paper. Everybody can write down the same room number on their piece of paper and go see the art in that room. They can make copies of their pieces of paper and give them to others. They can make guide books of all the art in all the rooms and give these to others so everybody can go see all the art.

But the NFT is encrypted and you bought the exclusive rights the decrypt it. So you have a coded text on a piece of paper, which only you can decode and see what room the art is in. Everybody else just has the real room number on their piece of paper and they can go to see the art in that room.

But you need an external service to decode the number on your piece of paper. You didn't buy any guarantee this service will remain in operation. So the service stops working and you no longer can decode your number on your piece of paper. So you can no longer see the art. No hang on, you can, because everybody can see the art in that room. It's right there.

Then the art gets moved to another room. Everybody writes the new room number on their piece of paper. You can't. Your laminated piece of paper is immutable. You paid for that since you thought immutability was a good thing. Luckily you can still see the piece of art, since everybody can.

Running five applications and their database on a single host with only 465MiB RAM, well, works... but not so much.

The database crashes every few days, unsurprisingly, which causes the Friendica daemons to stop too. Rather than making these automatically restart too, I think I better do what I did for the Pleroma/Peertube host as well: move the database to a separate host.

It is better to share different applications on a host than to have an app and its db on the same host. My argument is that different applications are not busy at the same time, while an application and its database usually spike at the same moment (when you post something or a post comes in). It's also better to use two hosts rather than one with double the specs, because on AWS at least double the specs doubles the price, the RAM and the burst credits but not the CPUs while two hosts naturally have double the price, RAM, burst credits and CPUs.

I've first setup the second host with a db as replica. I've found this the easiest way to transfer a database: first setup a replica in the new location, then let them switch sides. The replication has been running fine for a while. The replication threads even survived yet another crash of the source db. With mariadb/mysql you don't have such a thing as a primary or replica role as you have with postgresql, so you don't have to switch roles for all apps at once. I guess I'll do the less important ones first...