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

I also ran into that issue the other day. Did you file a feature request for that? If you didn't I will. In general though I really like Moshidon. The video player functionality I want is not available in any mastodon client app except for Fedilab technically, but its implementation is still very primitive for now.

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.

True. A lot of things could be improved with the design, this is really just to visualize the core concept. I was also thinking a play/pause button on the pinned player would be good.

Getting fancier, maybe double tap on the right of the pinned player to skip forward 15 seconds would be sweet for skipping ad spots, and when you go the original post, the video could be fixed to the top of the page while you scroll into the replies.

I think participating in communities which are centered around discussion of open source software is the ideal solution. That could be on Lemmy, Mastodon, GitHub, Reddit, Discord, wherever devs and users congregate (and, whatever platforms you find tolerable). I think the information you are seeking is too varied and in some cases subjective to be captured and parsed by an automated tool. And it would be great if you could help others by posting in those communities about changes that you are unhappy with, so others can make informed decisions.

It might be time for a rewatch of what will soon be "season 1". I liked PSG quite a bit when it came out. The animation is slick and creative, the soundtrack bumps and the humor is very irreverant. It was a pretty offensive and lizard-brained show but as far as I remember it was just kind of generally poking fun. I have a hard time picturing where they will take the new season though as the first one was kind of a hodgepodge with little direction.

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 can install, remove and update apps from Software Manager, so familiarizing yourself with that application is probably a good idea. You can customize the theme and behavior of the desktop in System Settings, which is fun.

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.

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.