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.

While it might be reasonable to expect a web page to behave the way you describe, for anything more in web application territory the expectation that everything you ever loaded will stay visible somehow and available without cooperation of the code implementing the website is ridiculous.

Python packaging and stability is a total mess. It has gotten to the point where I just look for alternative tools when I find out something new I found is written in Python.

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

But that is the point. Most people do not use VPNs, you harm very few legitimate customers and save yourself the headache of dealing with all those who use VPNs for scams, attacks, exploits,…

The trade-off is entirely different from dynamic IPs.

Also, the admins running those things don’t do stuff to look like they are doing things, they wouldn’t care if you use a VPN if there was no downside to treating VPN IPs like any other.

No, they are literally not. Blocking VPN users is literally the low effort thing to do because the rate of problematic attacks and similar high effort issues coming from those IPs is much higher than the few legitimate users using VPNs are worth.

the info required was there already, just you needed to put effort in

Not really. This is mostly what this is all about. The companies are insisting that open source projects should do analysis of security impacts in addition to fixing the bugs whenever some “security researcher” runs some low effort fuzzing or static analysis thing that produces large numbers of bug reports and assigns CVEs to them without the consent of the project. The problem is that such an impact analysis is significant effort (often orders of magnitude more than the fix itself) by people with deep knowledge about the code bases and only really useful to the customers of those companies who want to selectively update instead of just applying all the latest fixes.

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.

Probably doesn’t happen as much on Windows because Windows has issues replacing files that are open.

Safari is also just one of the forks of the KHTML/WebKit/Blink codebase Chrome is based on. Admittedly they probably implement some of the stuff they do implement themselves too because the common ancestor version is quite a long time ago now.

While true essentially forking the latest stable version of the kernel to make an LTS branch or a vendor version only multiplies the problem, it also does not contribute to solving it.

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.

One of the last browsers out of the two that exist (ignoring those that don’t really develop any of those features themselves)?

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.