IPv6 binds on wildcard addresses include binding to the IPv4 addresses.

What does ss -tlnp return? Does the process listen on any ports?

That should only affect ports below 1024.

Your two bind addresses might be in conflict with each other since [::]:5234 includes binding to the first one.

You want https://tabby.tabbyml.com/ instead of tabby.ml

Talking about PRs being broken and then bringing up email, just about the most broken technology still in wide-spread use, is sort of ironic.

Yeah, the whole commenting won’t work if the server where the repo is hosted fails or the server where the person has an account. There is no redundancy.

I could be up and running in like 10 minutes to install Forgejo or Gitea

You could maybe do that but only because you already know how unlike most developers and you completely dismiss any active maintenance like updates, moderation, debugging performance issues, resizing storage,…

The term “single point of failure” means that only that point has to fail for the entire system to become unusable. You can easily have more than one of those in a system though.

Forgefed seems to be ActivityPub based which, judging by Lemmy, doesn’t solve the redundancy issue at all, it just allows you to interact with the content hosted in a single place from your own single place, giving you two single points of failure and two points where you can be tracked instead of one. This is not really the same kind of distributed as git repositories.

Can you name an open platform that actually does distribute PRs and issues? I know there were a few that tried but I mean one that actually succeeded and is usable by people who just want to report a bug?

Also, your issues and pull requests are much more likely to be lost in your self-hosted one project instance than on GitHub if anything happens to you.

I can understand the argument against GitHub in two contexts, one is when people build features into their software that assume GitHub, e.g. when a programming language assumes it can just prepend github.com/ to your repo to find it and the other is the argument that losing GitHub would be a huge blow because so many projects are there and only there so a lot of things would have to be done at once if that ever happened.

Federation doesn’t really solve the issue that self-hosting takes effort away from working on the actual project.

Haven’t used it myself but you could give https://rustdesk.com/ a try.

If by “simple GUI app” you mean something that has an embedded web browser then no, otherwise pretty much all of them unless you count the kind of third party clients that might broken at any moment by the platform because they have just reverse engineered the protocol and are not taken into account by the platform at all when making changes.

Why not? There aren’t really any good alternatives out there if you want a chat without gifs and embedded images and videos and all that stuff that requires basically a whole web view to render it.

Self-hosting has some inherent downsides that will never make it so easy that it completely outclasses the competition by cheap mass-hosters hosting the exact same thing for most people. You or I might enjoy fiddling with technical things or keeping our computers running 24/7 or setting up some workaround CGNAT or DualStack Lite so that computer is even reachable from the outside (or even have a physically stationary computer in the first place, lots of people carry laptops around instead or don’t even have anything but a phone) but most people would much rather pay someone US$1 a month to do all that stuff for them.

SQL-to-API automatically Write SQL queries that automatically get exposed as API endpoints so you can easily integrate them with your frontend applications.

This sounds like such a horrible idea and I am convinced that this idea is responsible for the vast majority of data leaks through overly permissive APIs in recent years.

How do you suggest self-hosting should be made easier while at the same time making offering the same software as a service harder?

Basically the bits that are hard for people about self-hosting is that you need to learn about concepts you have no previous experience with. This can only be mitigated by abstracting those concepts away to some degree and automating more but those are exactly the same steps that make offering the software as a service easier too.

Not sure if these are reputable sources so make your own judgement on that but Google returns these two places when searching for the App identifier in the URL above

https://appteka.store/app/4e8r156105

https://www.openapk.net/food-expirations/com.lorenzovainigli.foodexpirationdates.foss/