Fedi client app developers need to design fedi client apps in a holistic way to include a custom server (as with Mammoth’s moth.social) or create an account for the user on one of a curated selection of other servers, without forcing the user to choose one.

It’s a severe problem with trying to grow fedi that general users are expected to understand how servers work and make an informed decision about which one to join. General users don’t care about this topic and will quickly turn away when it is forced upon them. That’s why the client app needs to handle this for the user without making a fuss about it.

These apps also need good discovery features and feeds with posts that are trending generally and for specific topics. Then devs need to make money with those apps somehow, then they need to market those apps (at this point, it goes beyond just “devs” and expands into an organization with a marketing department, etc.).

Then, hopefully fedi’s inherent advantages of interoperability and resilience will naturally cause people to choose these user-friendly, effectively marketed fedi client apps over things like Instagram, Tiktok, etc. After all, if it can’t compete on its own merits with all other factors being equal, there’s no point to it for most people.

Nextcloud may be a bit overkill for your use case, but it does have a very good video chat function. It’s also pretty easy to deploy as a snap package or with the AIO docker image. A downside is that the other person has to have an account on your instance and log into it to join a call. However this is not necessarily difficult to arrange.

Jellyfin is ideal for privately sharing music. Plex is similar but not FOSS.

That’s funny, my phone is kinda small so I had to scroll that horizontal menu with the download button, over to the right to access that button 😆 Thanks for the screenshot

That’s awesome, nice work! I just tried out Tesseract and it seems to work quite well. Feel free to leave some links where people can try it or contribute to the project, if you like.

Agree, if you are running containers on a casual or “just for fun” basis then automatic updates are fine. But the more you or others depend on the service running, the more it makes sense to perform an update manually, when you have time to troubleshoot any problems that may arise. Or, even update on a test setup first to identify issues and then update on your production setup.

You know you can just request the desktop site on FB messenger and use it on your phone that way right?

https://www.makeuseof.com/how-to-view-desktop-version-of-any-site-on-mobile/

Traefik is powerful and versatile but has a steep learning curve. It also uses code to control its configuration which is a bonus for reliability and documentation as discussed elsewhere ITT. Nginx proxy manager is much simpler and easier to use, may be a good one to get started with, but lacks the advantages of traefik described above. Nginx proxy manager does support SSL cert automation.

Another suggestion for you, I highly recommend specifying a version for the docker image you are using for a container, in the compose file. For example, nextcloud:29.0.1. If you just use :latest, it will pull a new version whenever you redeploy which you may not have tested against your setup, and the version upgrade may even be irreversible, as in the case of nextcloud. This will give you a lot more control over your setup. Just don’t forget to update images at reasonable intervals.

Some examples of technologies which follow that paradigm are docker compose, ansible, nixOS and terraform. But it all depends on your workflow.

I use markdown text files which are synced to my nextcloud instance.

This is somewhat tangential to your post, but I think using infrastructure as code and declarative technologies is great for reliability because you aren’t just running a bunch of commands until something works, you have the code which tells you exactly how things are set up, and you can version control it to roll back to a working state. The code itself can be a form of documentation in that case.